DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claim Objections
Claims 1 and 10 are objected to because of the following informalities:
a) On line 3 of claim 1, the abbreviation, "USIM" should be presented for what it stands for. It is same for claim 10.
b) On line 7 of claim 1, the phrase, "a device profile", seems refer back “a device profile” recited on line 4 of claim 1. If it is true, It is suggested to change “a device profile” to “the device profile”. It is same for claim 10.
c) On line 5 of claim 1, the phrase, "in in" should be change to “in”. It is same for claim 10.
d) On line 7 of claim 1, the word, "on" should be change to “one”. It is same for claim 10.
Appropriate correction is required.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 1-6, 8-15 and 17-18 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Hentschel (US Pat Pub. No. 2018/0054517).
Regarding claim 1, Hentschel discloses a computer-implemented method of providing a virtual SIM-based card pool, the method comprising steps of:
downloading a USIM profile and associated information, the associated information including a device profile, a cryptographic signature corresponding to the USIM profile, or both (See at least paragraphs 36 and 42 discloses wherein SIM activation equipment download and store SIM profiles and related information; SIM profile including personal identifier (PIN) is downloaded; verify the UE for cellular communication system associated with the SIM profiles; further paragraph 31 shows SIM profile includes information specifies a cellular network phone number, authentication procedure which includes IMSI, key, PIN and PUK);
storing the USIM profile in in a profile information database, the profile information database including a plurality of USIM profiles (See at least paragraph 36 discloses wherein SIM activation equipment download and store SIM profiles and related information; paragraph 39 discloses SIM profiles stores in the SIM profile database);
wherein a device profile includes one or more indications of mobile device types,
on or more indications of telecommunication carriers, one or more indications of Application Programmiong Interfaces (APIs), or combinations thereof (paragraph 8 and 53 discloses a smart phone can be activated and verified of the SIM profile loaded into the eSIM for the UE; paragraph 38 further discloses a network provider of cellular system for which the UE being configured), and
wherein the steps are performed by a computing device including one or more processors coupled to one or more hardware memories (See at least paragraphs 40 and 43 discloses eSIM activation device having controller which performs the functions).
Regarding claim 2, Hentschel discloses downloading the USIM profile comprises: receiving a triggering instruction; establishing a data connection with a remote server; downloading the USIM profile and the associated information from the remote server using the data connection (See at least paragraphs 42 and 53 discloses eSIM activation device to establish data connection to download the eSIM profile).
Regarding claim 3, Hentschel discloses downloading the USIM profile is performed in response to receiving an activation code through a user interface (See at least paragraph 42).
Regarding claim 4, Hentschel discloses downloading the USIM profile comprises: establishing a data connection with a first remote server; receiving a routing instruction from the first remote server, downloading the USIM profile and the associated information from a second remote server determined using the routing instruction; and verifying the source of the USIM profile using the cryptographic signature (See at least paragraphs 42 and 53 discloses eSIM activation device to establish data connection to download the eSIM profile).
Regarding claim 5, Hentschel discloses generating, based on the USIM profile stored in the profile information database and the associated information, a USIM instance stored as software in a virtual SIM container of a virtual card pool, the virtual card pool including a plurality of virtual SIM containers (See at least paragraphs 37-38); receiving an external SIM authentication request generated by a mobile device; generating, using the USIM instance, a response to the external SIM authentication request; and causing the response to be transmitted to the mobile device (See at least paragraphs 38-39).
Regarding claim 6, Hentschel discloses generating the USIM instance comprises verifying the source of the USIM profile using the cryptographic signature included in the associated information (See at least paragraph 42).
Regarding claim 8, Hentschel discloses causing the USIM profile and the cryptographic signature included in the associated information to be transmitted to an external application, wherein the cryptographic signature is configured to enable the mobile device to verifying the source of the USIM profile (See at least paragraph 42).
Regarding claim 9, Hentschel discloses causing the USIM profile and the device profile included in the associated information to be transmitted to an external application, wherein the device profile is configured to enable the external application to determine the capabilities of the USIM profile, the capabilities including one or more device types the USIM profile is configured for use in, one or more telecommunication carriers the USIM profile is configured to communication with, one or more APIs the USIM profile is configured to use, or combinations thereof (See at least paragraphs 42 and 53 discloses verification of the SIM profile).
Regarding claim 10, Hentschel discloses a non-transitory computer-readable media (CRM) comprising computer programming instructions which, when executed by a processor of a device (See at least paragraphs 40 and 43 discloses eSIM activation device having a memory and a controller which performs the functions), cause the device to perform steps comprising:
downloading a USIM profile and associated information, the associated information including a device profile, a cryptographic signature corresponding to the USIM profile, or both (See at least paragraphs 36 and 42 discloses wherein SIM activation equipment download and store SIM profiles and related information; SIM profile including personal identifier (PIN) is downloaded; verify the UE for cellular communication system associated with the SIM profiles; further paragraph 31 shows SIM profile includes information specifies a cellular network phone number, authentication procedure which includes IMSI, key, PIN and PUK);
storing the USIM profile in in a profile information database, the profile information database including a plurality of USIM profiles (See at least paragraph 36 discloses wherein SIM activation equipment download and store SIM profiles and related information; paragraph 39 discloses SIM profiles stores in the SIM profile database);
wherein a device profile includes one or more indications of mobile device types, on or more indications of telecommunication carriers, one or more indications of Application Programming Interface (APIs), or combinations thereof (See at least paragraph 8 and 53 discloses a smart phone can be activated and verified of the SIM profile loaded into the eSIM for the UE; paragraph 38 further discloses a network provider of cellular system for which the UE being configured), and
wherein the steps are performed by a computing device including one or more processors coupled to one or more hardware memories (See at least paragraphs 40 and 43 discloses eSIM activation device having controller which performs the functions).
Regarding claim 11, Hentschel discloses downloading the USIM profile comprises: receiving a triggering instruction; establishing a data connection with a remote server; downloading the USIM profile and the associated information from the remote server using the data connection (See at least paragraphs 42 and 53 discloses eSIM activation device to establish data connection to download the eSIM profile).
Regarding claim 12, Hentschel discloses downloading the USIM profile is performed in response to receiving an activation code through a user interface (See at least paragraph 42).
Regarding claim 13, Hentschel discloses downloading the USIM profile comprises: establishing a data connection with a first remote server; receiving a routing instruction from the first remote server, downloading the USIM profile and the associated information from a second remote server determined using the routing instruction; and verifying the source of the USIM profile using the cryptographic signature (See at least paragraphs 42 and 53 discloses eSIM activation device to establish data connection to download the eSIM profile).
Regarding claim 14, Hentschel discloses the steps further comprise: generating, based on the USIM profile stored in the profile information database and the associated information, a USIM instance stored as software in a virtual SIM container of a virtual card pool, the virtual card pool including a plurality of virtual SIM containers (See at least paragraphs 37-38); receiving an external SIM authentication request generated by a mobile device; generating, using the USIM instance, a response to the external SIM authentication request; and causing the response to be transmitted to the mobile device (See at least paragraphs 38-39).
Regarding claim 15, Hentschel discloses generating the USIM instance comprises verifying the source of the USIM profile using the cryptographic signature included in the associated information (See at least paragraph 42).
Regarding claim 17, Hentschel discloses the steps further comprise: causing the USIM profile and the cryptographic signature included in the associated information to be transmitted to an external application, wherein the cryptographic signature is configured to enable the mobile device to verifying the source of the USIM profile (See at least paragraph 42).
Regarding claim 18, Hentschel discloses causing the USIM profile and the device profile included in the associated information to be transmitted to an external application, wherein the device profile is configured to enable the external application to determine the capabilities of the USIM profile, the capabilities including one or more device types the USIM profile is configured for use in, one or more telecommunication carriers the USIM profile is configured to communication with, one or more APIs the USIM profile is configured to use, or combinations thereof (See at least paragraphs 42 and 53 discloses verification of the SIM profile).
Allowable Subject Matter
Claims 7 and 16 objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Park et al (US Pat. Pub. No. 2019/0104401) are cited to show an electronic device for downloading a profile for service provision.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to LITON MIAH whose telephone number is (571)270-3124. The examiner can normally be reached on Mon - Fri 7:30am -5:00pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Rafael Perez-Gutierrez can be reached on 571-272-7915. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/LITON MIAH/Primary Examiner, Art Unit 2642
Prosecution Insights