DETAILED ACTION
Notice of Pre-AIA or AIA Status
I. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Response to Amendment
II. This action is in response to applicants amendment/arguments filed on June 3, 2026. This action is made FINAL.
Allowable Subject Matter
III. The following is a statement of reasons for the indication of allowable subject matter:
Claims 1 and 10 contain allowable subject matter based on the amendments (see Amendments to the Claims, pages 2-6) and for the reasons given in applicant arguments/remarks (see Remarks, pages 13-16) received in the June 3, 2026 response to the Non-Final Office action dated March 9, 2026.
Claims 2-9 contain allowable subject matter based on their dependence on independent claim 1.
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.
IV. Claims 11-12, 14-17, and 19-20 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Chen et al. (US 2020/0163009 A1).
Regarding claim 11 3GPP TR 33.864 teaches an apparatus, of a third network device, for performing a network function, the apparatus comprising: at least one memory (60, Fig. 8); and at least one processor (58, Fig. 8) coupled with the at least one memory and configured to cause (645, Fig. 8) the apparatus to: receive a request message at a third network device comprising a target access and mobility function (AMF), a target security anchor function (SEAF), or a combination thereof (see paragraph [0080] and Fig. 6, The initial AMF determines to forward the NAS message to the target AMF, the initial AMF sends a Reroute NAS message to the target AMF. This reads on receive a request message at a third network device comprising a target access and mobility function (AMF), a target security anchor function (SEAF), or a combination thereof); determine, at the third device, whether to obtain security context information from a fourth network device; and in response to determining to obtain the security context information, transmitting a request for the security context information to the fourth network device (see paragraph [0082] and Fig. 6, The target AMF may decide to invoke an AUSF. In that case, the target AMF selects an AUSF and initiates authentication. The AMF passes security data back and forth so the AUSF can check the user's details with the Unified Data Management (UDM) (see step 414). This reads on determine, at the third device, whether to obtain security context information from a fourth network device; and in response to determining to obtain the security context information, transmitting a request for the security context information to the fourth network device).
Regarding claim 12 Chen teaches causing the apparatus to determine whether to obtain the security context information from the fourth network device based on a local policy, receive authentication information, receive reroute information due to slicing, or a combination thereof (see paragraphs [0081] & [0082] and Fig. 6, The RAN sends a message to the target AMF (see 410b, Fig. 6) indicating reroute due to slicing. The target AMF may thendecide to invoke an AUSF. In that case, the target AMF selects an AUSF and initiates authentication. The AMF passes security data back and forth so the AUSF can check the user's details with the Unified Data Management (UDM) (see step 414). This reads on causing the apparatus to determine whether to obtain the security context information from the fourth network device based on a local policy, receive authentication information, receive reroute information due to slicing, or a combination thereof).
Regarding claim 14 Chen teaches wherein the request message comprises a reroute non-access stratum (NAS) message or a registration request message (see paragraph [0080] and Fig. 6, The initial AMF sends a reroute NAS message to the target AMF in step 408a. This reads on wherein the request message comprises a reroute non-access stratum (NAS) message or a registration request message).
Regarding claim 15 Chen teaches wherein the fourth network device comprises an authentication server function (AUSF) or an old access and mobility management function (AMF) (see paragraph [0082] and Fig. 6, The target AMF may decide to invoke an AUSF. In that case, the target AMF selects an AUSF and initiates authentication. This reads on wherein the fourth network device comprises an authentication server function (AUSF) or an old access and mobility management function (AMF)).
Regarding claim 16 Chen teaches receiving a request message at a third network device comprising a target access and mobility function (AMF), a target security anchor function (SEAF), or a combination thereof (see paragraph [0080] and Fig. 6, The initial AMF determines to forward the NAS message to the target AMF, the initial AMF sends a Reroute NAS message to the target AMF. This reads on receiving a request message at a third network device comprising a target access and mobility function (AMF), a target security anchor function (SEAF), or a combination thereof); determining, at the third device, whether to obtain security context information from a fourth network device; and in response to determining to obtain the security context information, transmitting a request for the security context information to the fourth network device (see paragraph [0082] and Fig. 6, The target AMF may decide to invoke an AUSF. In that case, the target AMF selects an AUSF and initiates authentication. The AMF passes security data back and forth so the AUSF can check the user's details with the Unified Data Management (UDM) (see step 414). This reads on determining, at the third device, whether to obtain security context information from a fourth network device; and in response to determining to obtain the security context information, transmitting a request for the security context information to the fourth network device).
Regarding claim 17 Chen teaches causing the apparatus to determine whether to obtain the security context information from the fourth network device based on a local policy, receive authentication information, receive reroute information due to slicing, or a combination thereof (see paragraphs [0081] & [0082] and Fig. 6, The RAN sends a message to the target AMF (see 410b, Fig. 6) indicating reroute due to slicing. The target AMF may thendecide to invoke an AUSF. In that case, the target AMF selects an AUSF and initiates authentication. The AMF passes security data back and forth so the AUSF can check the user's details with the Unified Data Management (UDM) (see step 414). This reads on causing the apparatus to determine whether to obtain the security context information from the fourth network device based on a local policy, receive authentication information, receive reroute information due to slicing, or a combination thereof).
Regarding claim 19 3GPP TR 33.864 teaches wherein the request message comprises a reroute non-access stratum (NAS) message or a registration request message (see paragraph [0080] and Fig. 6, The initial AMF sends a reroute NAS message to the target AMF in step 408a. wherein the request message comprises a reroute non-access stratum (NAS) message or a registration request message).
Regarding claim 20 3GPP TR 33.864 teaches wherein the fourth network device comprises an authentication server function (AUSF) or an old access and mobility management function (AMF) (see paragraph [0082] and Fig. 6, The target AMF may decide to invoke an AUSF. In that case, the target AMF selects an AUSF and initiates authentication. This reads on wherein the fourth network device comprises an authentication server function (AUSF) or an old access and mobility management function (AMF)).
Response to Arguments
VI. Applicant’s arguments with respect to claims 11-12, 14-17, and 19-20 have been considered but are moot in view of the new grounds of rejection.
Conclusion
VII. The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Gan et al. Pub. NO.: US 2020/0260525 A1 discloses secondary authorization at PDU session establishment at home routed roaming including delaying an authentication procedure related to the PDU session (see paragraph [0232]).
Applicant's amendment “determine, at the third device whether to obtain security context information from a fourth network device” necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to BRANDON J MILLER whose telephone number is (571)272-7869. The examiner can normally be reached M-F.
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, Alison Slater can be reached at 571-270-0375. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/BRANDON J MILLER/Primary Examiner, Art Unit 2647
August 19, 2026
Prosecution Insights