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 .
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 04/14/2025 and was filed after the mailing date of the 09/16/2024. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Allowable Subject Matter
Claims 14-16 are 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.
Claim Rejections - 35 USC § 102
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)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 1-2, 4-7, and 9-12 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Zhang (US 2020/0280341 A1).
Regarding claim 1, A method for ambiguity resolution for access to a particular application, the method
comprising:
by a contactless multiplexer; Zhang, Fig. 1 NFC controller 10:
receiving, from a near-field communication (NFC) reader, a message to access an application indicated
by an application identifier (AID) value; Zhang [0044], NFC reader sends a request carrying AID to the
NFC controller;
determining, based on an AID registry accessible by the contactless multiplexer, at least two distinct
applications are associated with the AID value indicated in the message from the NFC reader ;Zhang
[0048],NFC controller determines a AID conflict, AID3; [0042] both UICC1_APP_3 and
UICC2_APP_6 have an AID of AID3;
sending, to an applications processor (AP), a request message to determine particular application of the
at least two distinct applications for the NFC reader to access ; Zhang [0048] NFC controller sends a
request to the Host OS 30;
receiving, from the AP, a response message indicating the particular application for the NFC reader to
access Zhang, NFC controller receives a response, UICC1; and
sending, to a secure processor associated with the particular application, the message from the NEC
reader to initiate a contactless transaction between the particular application and the NEC reader
Zhang [0049], NFC controller directs NFC reader request to UICC1 .
Regarding claim 2, The method of claim 1, wherein the particular application is identified by an identifier for the secure processor on which the application resides.
Zhang [0003]; The SEs provide secure storage for sensitive information as well as a secure execution environment for transactions. NFC applications (APPs) reside on the SEs, and each NFC Application has an Application ID (AID).
Regarding claim 4, The method of claim 1, wherein the particular application is further determined based on a current location.
Zhang [0045] In a case where the AID carried in the request is AID1 or AID2, the route for the AID can be found in the routing table, so the NFC controller sends the request to the host operating system according to the found route (current location) to be further processed by an HCE module in the host operating system.
Regarding claim 5, The method of claim 1, wherein the AID registry includes one or more AID values associated with one or more applications installed in one or more secure processors.
Zhang [0048] In a case where the request carries AID3, both the UICC1_APP_3 in UICC1 and the UICC2_APP_6 in UICC2 will perform processing and return a positive response. After detecting that two SEs, that is, UICC1 and UICC2, have returned positive responses, the NFC controller encapsulates the request (including identifiers of UICC1 and UICC2) and notifies the host operating system that there is an AID conflict.
Regarding claim 6, The method of claim 5, wherein the AID registry further includes, for at least one AID value of the one or more AID values, additional logical data.
Zhang [0048]; In a case where the request carries AID3, both the UICC1_APP_3 in UICC1 and the UICC2_APP_6 in UICC2 will perform processing and return a positive response. After detecting that two SEs, that is, UICC1 and UICC2, have returned positive responses, the NFC controller encapsulates the request (including identifiers of UICC1 and UICC2) and notifies the host operating system that there is an AID conflict.
Regarding claim 7, The method of claim 6, wherein the additional logical data comprises an indication, for each application of the at least two distinct applications, on which secure processor of the one or more secure processors the associated application resides.
Zhang [0048] In a case where the request carries AID3, both the UICC1_APP_3 in UICC1 and the UICC2_APP_6 in UICC2 will perform processing and return a positive response. After detecting that two SEs, that is, UICC1 and UICC2, have returned positive responses, the NFC controller encapsulates the request (including identifiers of UICC1 and UICC2) and notifies the host operating system that there is an AID conflict.
Regarding claim 9, The method of claim 1, wherein the AID registry comprises AID values for one or more applications usable with NFC communication with the NFC reader.
Zhang [0048], NFC controller determines a AID conflict, AID3; [0042] both UICC1_APP_3 and
UICC2_APP_6 have an AID of AID3);
Regarding claim 10, The method of claim 1, wherein the AID registry comprises information for determining a target application to initiate to participate in an NFC transaction.
Zhang [0049], NFC controller directs NFC reader request to UICC1.
Regarding claim 11, A method for ambiguity resolution for access to a particular application, the method comprising, the method comprising: by an applications processor (AP): receiving, from a contactless multiplexer, a request message to determine the particular application of at least two distinct applications for an NFC reader to access;
Zhang [0048] NFC controller sends a request to the Host OS 30;
determining, based on one or more rules associated with the at least two distinct applications and on a current location, the particular application for the NFC reader to access;
Zhang [0048], NFC controller determines a AID conflict, AID3; [0042] both UICC1_APP_3 and
UICC2_APP_6 have an AID of AID3);
Zhang [0048]; The host operating system prompts, via a user interface, the user to select one of UICC1 and UICC2, and notifies the UICC (herein assumed to be UICC1) selected by the user to the NFC controller.
Zhang [0045] In a case where the AID carried in the request is AID1 or AID2, the route for the AID can be found in the routing table, so the NFC controller sends the request to the host operating system according to the found route (current location) to be further processed by an HCE module in the host operating system.
and sending, to the contactless multiplexer, a response message indicating the particular application for the NFC reader to access. Zhang; NFC controller receives a response, UICC1
Regarding claim 12, The method of claim 11, wherein the AP maintains a set of rules to select which application from a plurality of applications to allow the NFC reader to access.
Zhang [0048]; The host operating system prompts, via a user interface, the user to select one of UICC1 and UICC2, and notifies the UICC (herein assumed to be UICC1) selected by the user to the NFC controller.
[0045] In a case where the AID carried in the request is AID1 or AID2, the route for the AID can be found in the routing table, so the NFC controller sends the request to the host operating system according to the found route (current location) to be further processed by an HCE module in the host operating system.
Regarding claim 17, A contactless multiplexer comprising at least one processor configured to:
Zhang [0014]; The NFC controller includes a memory, a processor.
receive, from an external near-field communication (NFC) reader, a message to access an application
indicated by an application identifier (AID) value; Zhang [0044], NFC reader sends a request carrying
AID to the NFC controller;
Zhang [0015]; receiving a request from an external device for accessing an NFC application;
determine, based on an AID registry accessible by the contactless multiplexer, at least two distinct
applications are associated with the AID value indicated in the message from the NFC reader ;Zhang
[0048],NFC controller determines a AID conflict, AID3; [0042] both UICC1_APP_3 and
UICC2_APP_6 have an AID of AID3;
send, to an applications processor (AP), a request message to determine particular application of the
at least two distinct applications for the NFC reader to access ; Zhang [0048] NFC controller sends a
request to the Host OS 30;
receive, from the AP, a response message indicating the particular application for the NFC reader to
access Zhang, NFC controller receives a response, UICC1; and
send, to a secure processor associated with the particular application, the message from the NEC
reader to initiate a contactless transaction between the particular application and the NEC reader
Zhang [0049], NFC controller directs NFC reader request to UICC1 .
Regarding claim 18, The contactless multiplexer of claim 17, wherein the particular application is identified by an identifier for the secure processor on which the application resides.
Zhang [0003]; The SEs provide secure storage for sensitive information as well as a secure execution environment for transactions. NFC applications (APPs) reside on the SEs, and each NFC Application has an Application ID (AID).
Regarding claim 20, The contactless multiplexer of claim 17, wherein the particular application is further determined based on a current location.
Zhang [0045] In a case where the AID carried in the request is AID1 or AID2, the route for the AID can be found in the routing table, so the NFC controller sends the request to the host operating system according to the found route (current location) to be further processed by an HCE module in the host operating system.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 3,8, 19 are rejected under 35 U.S.C. 103 as being unpatentable over Zhang in view of Li et al. (US 2017/0013442)(“Li”).
Regarding claim 3, The method of claim 1, wherein the particular application is identified by an identifier for an electronic subscriber identity module (eSIM) profile in which the application resides.
Li [0054] FIG. 3B illustrates a block diagram 350 of an eUICC 352 that stores multiple eSIMs 216, which are represented in FIG. 3B as eSIM_1 354 and eSIM_2 356. In this embodiment, the applications (not illustrated in FIG. 2B) associated with the eSIM_1 354 and the eSIM_2 356 are identified by the same application identifier, AID_1 307.
In view of Li, Zhang is modified such that the particular application is identified by an identifier for an electronic subscriber identity module (eSIM) profile in which the application resides.
Zhang and Li are analogous art to the claimed invention because they are in the same field of endeavor,
determining application based on AIDs.
It would be obvious before the effective filing date of claimed invention, to a person ordinary skill in the
art to modify Zhang in a manner describe above to define a unique identifier in which the application resides to identify the particular application to avoid AID conflict (Li [0031]).
Regarding claim 8, The method of claim 7, wherein the additional logical data for the AID value comprises a unique identifier for an electronic subscriber identity module (eSIM) profile in which the associated application resides.
Li [0054] FIG. 3B illustrates a block diagram 350 of an eUICC 352 that stores multiple eSIMs 216, which are represented in FIG. 3B as eSIM_1 354 and eSIM_2 356.
In view of Li, Zhang is modified such that the additional logical data for the AID value is a unique identifier for an electronic subscriber identity module (eSIM) profile in which the associated application resides.
Zhang and Li are analogous art to the claimed invention because they are in the same field of endeavor,
determining application based on AIDs.
It would be obvious before the effective filing date of claimed invention, to a person ordinary skill in the
art to modify Zhang in a manner describe above to define a unique identifier in which the application resides to identify the particular application to avoid AID conflict (Li [0031]).
Regarding claim 19, The contactless multiplexer of claim 17, wherein the particular application is identified by an identifier for an electronic subscriber identity module (eSIM) profile in which the application resides.
Li [0054] FIG. 3B illustrates a block diagram 350 of an eUICC 352 that stores multiple eSIMs 216, which are represented in FIG. 3B as eSIM_1 354 and eSIM_2 356. In this embodiment, the applications (not illustrated in FIG. 2B) associated with the eSIM_1 354 and the eSIM_2 356 are identified by the same application identifier, AID_1 307.
In view of Li, Zhang is modified such that the particular application is identified by an identifier for an electronic subscriber identity module (eSIM) profile in which the application resides.
Zhang and Li are analogous art to the claimed invention because they are in the same field of endeavor,
determining application based on AIDs.
It would be obvious before the effective filing date of claimed invention, to a person ordinary skill in the
art to modify Zhang in a manner describe above to define a unique identifier in which the application resides to identify the particular application to avoid AID conflict (Li [0031]).
Claim 13 is rejected under 35 U.S.C. 103 as being unpatentable over Zhang in view of Nquyen (US 2016/0309287 A1).
Regarding claim 13, The method of claim 12, wherein the set of rules include one or more associations between particular applications and particular geographic locations.
Nguyen [0043]; If the applications reside in different locations, some on the DH 203, 204, as well as some on the plurality of SEs 205, 206, 207, the NFCC 201 is not able to determine the right destination, i.e. the DH 203, 204 or the SEs 205, 206, 207, to set up the right communication channel 214, 215, 216, 217, and to route the RF traffic accordingly.
In view of Nguyen, Zhang is modified such the set of rules include one or more associations between particular applications and particular geographic locations.
Nguyen and Zhang are analogous art to the claimed invention because they are in the same field of
endeavor, determining application based on AIDs.
It would be obvious before the effective filing date of claimed invention, to a person ordinary skill in the
art to modify Zhang in a manner describe above to allow one or more associations between particular applications and particular geographic locations identify the particular application.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be
directed to Maryam Emadi whose email is Maryam.emadi1@uspto.gov with telephone number of 703-
756-1834.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Joseph
Avellino can be reached on 571-272-3905.
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-directuspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic
Business Center (EBC) at 866-217-9197 (toll-free).
/M.E./Examiner, Art Unit 2478
/JOSEPH E AVELLINO/Supervisory Patent Examiner, Art Unit 2478
Prosecution Insights