IP Library Granted Patent US 12,563,386
Granted Patent B2
US 12,563,386 · App. 18/534,077 · Granted Feb 24, 2026

Method and apparatus for security realization of connections over heterogeneous access networks

Inventor: Jennifer Liu (Plano, TX)
Assignee: NOKIA TECHNOLOGIES OY
H04W12/037H04W8/02H04W12/06H04W12/08H04W12/086H04W12/60H04W60/00H04W76/11H04W88/06
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,563,386
App. No.
18/534,077
Granted
Feb 24, 2026
Kind
B2
Abstract

This application relates to session establishment by user equipment over a plurality of heterogenous access networks. In one aspect, the heterogenous access networks may include 3GPP and non-3GPP access networks ( 106 ). The non-3GPP access networks ( 106 ) may include one or more non-3GPP trusted access networks ( 108 ) or one or more non-3GPP, non-trusted access networks ( 110 ).

Claims (81)

1 . A user equipment (UE) comprising:

one or more transceivers configured to access a serving network over a plurality of access networks;

at least one processor; and

at least one memory storing instructions thereon that, when executed by the at least one processor, cause the UE to perform at least:

generating a request for registration and transmitting the request for registration to the serving network over an access network from among the plurality of access networks;

receiving a registration reject message, wherein the registration reject message indicates that the serving network is not authorized; and

in response to receiving the registration reject message indicating that the serving network is not authorized, entering a 5GMM-DEREGISTERED·PLMN-SEARCH state,

wherein the registration reject message includes a cause information element, and

wherein the cause information element includes a value indicating that the serving network is not authorized.

2 . The UE of claim 1 , wherein the instructions, when executed by the at least one processor, are further configured to cause the UE to perform:

aborting registration with the serving network; and

storing an identity of the serving network in a list of unauthorized serving networks.

3 . The UE of claim 2 , wherein the instructions, when executed by the at least one processor, are further configured to cause the UE to perform:

selecting another serving network for registration; and

requesting registration to said another serving network.

4 . The UE of claim 1 , wherein the registration reject message indicates that the serving network is not authorized for third generation partnership project (3GPP) access to the serving network.

5 . The UE of claim 1 , wherein the instructions, when executed by the at least one processor, are further configured to cause the UE to perform:

in response to receiving the registration reject message indicating that the serving network is not authorized by the home network of the UE, setting a fifth generation system (5GS) update status to 5U2 NOT UPDATED.

6 . An element or function configured for communication in a serving network, the element or function comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the element or function to perform at least:

receiving an authentication request for a user equipment requesting access to a serving network, wherein the authentication request includes an identifier of the serving network and a subscriber identity associated with the user equipment;

determining whether the serving network is authorized; and

in an instance in which the serving network is not authorized, generating an authentication response, wherein the authentication response indicates that the serving network is not authorized,

wherein the authentication response is configured to cause the user equipment to enter a 5GMM-DEREGISTERED·PLMN-SEARCH state,

wherein the authentication response includes a cause information element, and

wherein the cause information element includes a value indicating that the serving network is not authorized.

7 . The element or function of claim 6 , wherein the instructions stored on the at least one memory, when executed by the at least one processor, further cause the element or function to perform at least:

causing transmission of the authentication response towards the UE.

8 . A method comprising:

generating, using a user equipment (UE), a request for registration, the UE being configured to access a serving network over one or more of a plurality of access networks;

transmitting, from the UE, towards the serving network, over an access network from among the plurality of access networks, the request for registration;

receiving, at the UE, a registration reject message, wherein the registration reject message indicates that the serving network is not authorized; and

in response to receiving the registration reject message indicating that the serving network is not authorized, causing the UE to enter a 5GMM-DEREGISTERED·PLMN-SEARCH state,

wherein the registration reject message includes a cause information element, and

wherein the cause information element includes a value indicating that the serving network is not authorized.

9 . The method of claim 8 , further comprising:

causing the UE to abort registration with the serving network; and

adding, using the UE, an identity of the serving network to a list of unauthorized serving networks stored at the UE.

10 . The method of claim 9 , further comprising:

selecting, using the UE, another serving network for registration, the another serving network being different from said serving network; and

causing the UE to request registration to said another serving network.

11 . The method of claim 8 , wherein the registration reject message indicates that the serving network is not authorized for third generation partnership project (3GPP) access to the serving network.

12 . The method of claim 8 , further comprising:

in response to receiving, at the UE, the registration reject message indicating that the serving network is not authorized by the home network of the UE, causing the UE to set a fifth generation system (5GS) update status at the UE to 5U2 NOT UPDATED.

13 . A method comprising:

receiving, at an element or function of a serving network, an authentication request for a user equipment (UE) requesting access to the serving network, wherein the authentication request includes an identifier of the serving network and a subscriber identity associated with the UE;

determining, using the element or function of the serving network, whether the serving network is authorized; and

in an instance in which the serving network is not authorized, generating, using the element or function of the serving network, an authentication response,

wherein the authentication response indicates that the serving network is not authorized,

wherein the authentication response is configured to cause the UE to enter a 5GMM-DEREGISTERED·PLMN-SEARCH state,

wherein the authentication response includes a cause information element, and

wherein the cause information element includes a value indicating that the serving network is not authorized.

14 . The method of claim 13 , further comprising:

causing transmission, using the element or function of the serving network, of the authentication response towards the UE.

15 . A non-transitory computer readable storage medium storing instructions thereon that, when executed by a processor, cause at least the following:

generating, using a user equipment (UE), a request for registration, the UE being configured to access a serving network over one or more of a plurality of access networks;

transmitting, from the UE, towards the serving network, over an access network from among the plurality of access networks, the request for registration;

receiving, at the UE, a registration reject message, wherein the registration reject message indicates that the serving network is not authorized; and

in response to receiving the registration reject message indicating that the serving network is not authorized, causing the UE to enter a 5GMM-DEREGISTERED·PLMN-SEARCH state,

wherein the registration reject message includes a cause information element, and

wherein the cause information element includes a value indicating that the serving network is not authorized.

16 . The non-transitory computer readable storage medium of claim 15 , wherein the instructions stored on the non-transitory computer readable storage medium, when executed by the processor, further cause at least the following:

causing the UE to abort registration with the serving network; and

adding, using the UE, an identity of the serving network to a list of unauthorized serving networks stored at the UE.

17 . The non-transitory computer readable storage medium of claim 16 , wherein the instructions stored on the non-transitory computer readable storage medium, when executed by the processor, further cause at least the following:

selecting, using the UE, another serving network for registration, the another serving network being different from said serving network; and

causing the UE to request registration to said another serving network.

18 . The non-transitory computer readable storage medium of claim 15 , wherein the registration reject message indicates that the serving network is not authorized for third generation partnership project (3GPP) access to the serving network.

19 . The non-transitory computer readable storage medium of claim 15 , wherein the instructions stored on the non-transitory computer readable storage medium, when executed by the processor, further cause at least the following:

in response to receiving, at the UE, the registration reject message indicating that the serving network is not authorized by the home network of the UE, causing the UE to set a fifth generation system (5GS) update status at the UE to 5U2 NOT UPDATED.

20 . A non-transitory computer readable storage medium storing instructions thereon that, when executed by a processor, cause at least the following:

receiving, at an element or function of a serving network, an authentication request for a user equipment (UE) requesting access to the serving network, wherein the authentication request includes an identifier of the serving network and a subscriber identity associated with the UE;

determining, using the element or function of the serving network, whether the serving network is authorized; and

in an instance in which the serving network is not authorized, generating, using the element or function of the serving network, an authentication response,

wherein the authentication response indicates that the serving network is not authorized,

wherein the authentication response is configured to cause the UE to enter a 5GMM-DEREGISTERED·PLMN-SEARCH state,

wherein the authentication response includes a cause information element, and

wherein the cause information element includes a value indicating that the serving network is not authorized.

21 . The non-transitory computer readable storage medium of claim 20 , wherein the instructions stored on the non-transitory computer readable storage medium, when executed by the processor, further cause at least the following:

causing transmission, using the element or function of the serving network, of the authentication response towards the UE.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 8, 2023
From: LIU, JENNIFER
To: NOKIA TECHNOLOGIES OY
Reel/Frame 065816/0638 →
Continuity (3)
Division 17266295
Provisional Application 62716887 · Aug 9, 2018
Related Publication 20250193672A1 · Jun 12, 2025
References Cited (159)
US 20100203888A1 · Gunaratnam et al. · 2010 [cited by applicant]
US 20160105780A1 · Hooker et al. · 2016 [cited by applicant]
US 20170048702A1 · Barrett et al. · 2017 [cited by applicant]
US 20180020417A1 · Catovic et al. · 2018 [cited by applicant]
US 20180027414A1 · Li et al. · 2018 [cited by applicant]
US 20180220364A1 · Li et al. · 2018 [cited by applicant]
US 20190021064A1 · Ryu et al. · 2019 [cited by applicant]
US 20190253885A1 · Bykampadi et al. · 2019 [cited by applicant]
US 20190320381A1 · Niemi · 2019 [cited by examiner]
US 20190364428A1 · Torvinen et al. · 2019 [cited by applicant]
US 20200068391A1 · Liu et al. · 2020 [cited by applicant]
US 20200229206A1 · Badic · 2020 [cited by examiner]
US 20200296660A1 · Wang et al. · 2020 [cited by applicant]
US 20200344601A1 · Baskaran et al. · 2020 [cited by applicant]
US 20200359195A1 · Nakarmi · 2020 [cited by examiner]
US 20210092603A1 · Yang · 2021 [cited by examiner]
US 20210153010A1 · Torvinen · 2021 [cited by examiner]
US 20210160809A1 · Venkataraman · 2021 [cited by examiner]
US 20210195409A1 · Zhang · 2021 [cited by examiner]
US 20210314857A1 · Wang · 2021 [cited by examiner]
US 20210314899A1 · Shan · 2021 [cited by examiner]
US 20210368345A1 · Nakarmi · 2021 [cited by examiner]
US 20220174480A1 · Baskaran · 2022 [cited by examiner]
US 20220242534A1 · Peng et al. · 2022 [cited by applicant]
US 20220272534A1 · Torvinen · 2022 [cited by examiner]
US 20230164559A1 · Yang · 2023 [cited by examiner]
US 20230413166A1 · Basu Mallick · 2023 [cited by examiner]
CN 107683591A · 2018 [cited by applicant]
CN 107925879A · 2018 [cited by applicant]
EP 4093093A1 · 2022 [cited by applicant]
JP 2020527002A · 2020 [cited by applicant]
KR 20060130429A · 2006 [cited by applicant]
KR 1020170132273A · 2017 [cited by applicant]
KR 1020180022565A · 2018 [cited by applicant]
KR 1020180057665A · 2018 [cited by applicant]
WO WO2018008944A1 · 2018 [cited by applicant]
WO WO2018197601A1 · 2018 [cited by applicant]
WO WO2018208949A1 · 2018 [cited by applicant]
WO WO2019098496A1 · 2019 [cited by applicant]
WO WO2019139033A1 · 2019 [cited by applicant]
U.S. Appl. No. 17/266,295, filed Feb. 5, 2021, US-2021/0306849, Pending. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/266,295 dated Aug. 28, 2024. [cited by applicant]
Extended European Search Report for European Application No. 24165791.5 dated Jun. 27, 2024, 13 pages. [cited by applicant]
Interdigital, “Discussion Paper on the need and ways to make SUPI protection opaque to IMSI sniffers”, 3GPP TSG SA WG3 (Security) Meeting #90-Bis, S3-180505, (Feb. 26-Mar. 2, 2018), 9 pages. [cited by applicant]
CATT, “SUCI structure and SUCI generation conditions”, 3GPP TSG SA WG3 (Security) Meeting #90-Bis, S3-180594, (Feb. 26-Mar. 2, 2018), 2 pages. [cited by applicant]
Ericsson et al., “Subscription privacy: proposed content to clause 6.8.1 (SUPI)”, 3GPP TSG SA WG3 (Security) Meeting #88, S3-171782, (Aug. 7-11, 2017), 1 page. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Access to the 3GPP 5G Core Network (5GCN) via Non-3GPP Access Networks (N3AN); Stage 3 (Release 16)”, 3GPP TS 24.502 V16.3.0… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 15)”, 24.501 v15.1.0, (Sep. 2018), 398 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 15)”, 3GPP TS 24.501 v15.7.0, (Jun. 2022), 491 page… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 15)”, 3GPP 24.501 v15.3.0, (Mar. 2019), 470 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 15)”, 3GPP TS 24.501 v15.2.0, (Dec. 2018), 455 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 15)”, 3GPP TS 24.501 v15.2.1, (Jan. 2019), 455 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 15)”, 3GPP TS 24.501 v15.4.0, (Jun. 2019), 480 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 15)”, 3GPP TS 24.501 v15.5.0, (Sep. 2019), 480 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 15)”, 3GPP TS 24.501 v15.6.0, (Dec. 2019), 478 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 16)”, 3GPP TS 24.501 v16.4.1, (Mar. 2020), 666 page… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) Protocol for 5G Systems (5GS); Stage 3 (Release 15)”, 3GPP TS 24.501 v15.0.0 (Jun. 2018), 338 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification (Release 15)”, 3GPP TS 23.003 v15.4.0 (Jun. 2018), 120 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 16)”, 3GPP TS 23.003 V16.2.0, (Mar. 2020), 140 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15)”, 3GPP TS 38.300 v2.0.0 (Dec. 2017), 68 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for Non-3GPP Accesses”, 3GPP TS 23.402 v14.2.0 (Dec. 2016), 307 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and Charging Control Framework for the 5G System; Stage 2 (Release 15)”, 3GPP TS 23.503 v15.0.0 (Dec. 2017), 56 page… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15)”, 3GPP TS 23.502 v15.0.0 (Dec. 2017), 258 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15)”, 3GPP TS 23.502 v15.2.0, (Jun. 2018), 308 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system (Release 15)”, 3GPP TS 33.501 v15.0.0 (Mar. 26. 2018), 128 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security Architecture and Procedures for 5G System (Release 15)”, 3GPP TS 33.501 v15.1.0 (Jun. 2018), 152 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system (Release 15)”, 3GPP TS 33.501 v15.8.0, (Mar. 2020), 191 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.501 v16.4.0, (Mar. 2020), 430 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)”, 3GPP TS 23.501 v15.2.0 (Jun. 2018), 217 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)”, 3GPP TS 23.501 v15.0.0 (Dec. 2017), 181 pages. [cited by applicant]
“5G; Non-Access-Stratum (NAS) Protocol for 5G System (5GS); Stage 3 (3GPP TS 24.501 version 16.5.1 Release 16)”, ETSI TS 124 501 v16.5.1, (Aug. 2020), 729 pages. [cited by applicant]
“5G; System Architecture for the 5G System (5GS) (3GPP TS 23.501 version 16.6.0 Release 16)”, ETSI TS 123 501 v16.6.0, (Oct. 2020), 450 pages. [cited by applicant]
Arkko et al., “Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA′)”, Internet Draft, Network Working Group [online] [Retrieved Apr. 8, 2021]. Retrieved from … [cited by applicant]
BlackBerry UK Ltd., “Increment the Registration Attempt Counter”, 3GPP TSG-CT WG1 Meeting #111, C1-183739, (May 21-25, 2018), 5 pages. [cited by applicant]
CATT, “Clause 6.1.2—Clarification to Authentication Method Selection-Based On Living CR S3-181465”, 3GPP TSG-SA WG3 Meeting #91-bis, S33-181719, Change Request 33.501 CR 0084 Rev 2, (May 21-25, 2018), 3 pages. [cited by applicant]
China Mobile, “Clarification on Deriving SUPI from SUCI”, 3GPP TSG-CT WG4 Meeting #90, CR 0530, C4-191270, (Apr. 8-12, 2019), 4 pages. [cited by applicant]
Decision to Grant for Japanese Application No. 2021-506706 dated Jun. 22, 2023, 5 pages. [cited by applicant]
Ericsson, “SUCI—Readiness to Protection Schemes Update in Future”, 3GPP TSG-SA WG3 Meeting #91, Belgrade, Serbia, Apr. 16, 2018, pp. 1-3, S3-181393, 3GPP. [cited by applicant]
Ericsson, “SUPI and SUCI for Wireline Access”, SA WG2 Temporary Document, SA WG2 Meeting #131, S2-1902321, (Feb. 25-Mar. 1, 2019), 3 pages. [cited by applicant]
Extended European Search Report for European Application No. 19846960.3 dated Nov. 10, 2022, 19 pages. [cited by applicant]
Final Office Action for U.S. Appl. No. 17/266,295 dated May 8, 2023. [cited by applicant]
First Examination Report for Indian Application No. 202127009623 dated Feb. 23, 2022, 10 pages. [cited by applicant]
Huawei et al., “Authentication Failure Scenarios”, 3GPP TSG CT WG4 Meeting #89, CR 0044, C4-190587, (Feb. 25-Mar. 2, 2019), 7 pages. [cited by applicant]
Intel, “Clarification on SUCI Scheme-Output Format”, 3GPP TSG-CT4 Meeting #91, CR 0532, C4-192184, (May 13-17, 2019), 4 pages. [cited by applicant]
International Search Report and Written Opinion for Patent Cooperation Treaty Application No. PCT/FI2019/050573 dated Oct. 24, 2019, 16 pages. [cited by applicant]
Kaufman et al., “Internet Engineering Task Force (IETF) Request for Comments: 7296; Internet Key Exchange Protocol Version 2 (IKEv2)”, [online] [Retrieved Apr. 8, 2021]. Retrieved from the Internet: <URL: https://tools.… [cited by applicant]
LG Electronics, “TS 23.501 P-CR Update to Registration Management”, SA WG2 Meeting #120, S2-172411, (Mar. 27-31, 2017), 4 pages. [cited by applicant]
MediaTek Inc., “Correction to UE Actions When Receiving 5GMM Cause 11”, 3GPP TSG-CT WG1 Meeting #111bis, C1-184504, Change Request 24.501 CR 0211, (Jul. 9-13, 2018), 5 pages. [cited by applicant]
MediaTek Inc., “SUCI Value IE in Registration Reject Message”, 3GPP TSG-CT WG1 Meeting #117, CR 1252, C1-193425, (May 13-17, 2019), 9 pages. [cited by applicant]
NEC, “Structure of SUPI and SUCI”, 3GPP TSG CT WG4 Meeting #85, CR 0504, C4-184201, (May 21-25, 2018), 8 pages. [cited by applicant]
Nokia et al., “Initial Registration Not Accepted Due to Serving Network Not Authorized”, 3GPP TSG-CT WG1 Meeting #112, Change Request 0301, C1-185268, (Aug. 20-24, 2018), 6 pages. [cited by applicant]
Nokia et al., “Non-3GPP Access to 5GCN Not Allowed”, 3GPP TSG-CT WG1 Meeting #111bis, Change Request 0080, C1-184875, (Jul. 9-13, 2018), 3 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/266,295 dated Jan. 10, 2023. [cited by applicant]
Notice of Acceptance for Australian Application No. 2019319095 dated Jul. 1, 2022, 3 pages. [cited by applicant]
Notice of Acceptance for Australian Application No. 2022252749 dated Oct. 6, 2023, 3 pages. [cited by applicant]
Notice of Acceptance for Chilean Application No. 2021-000337 dated Mar. 21, 2023, 6 pages. [cited by applicant]
Notice of Allowance for ARIPO Application No. AP/P/2021/012934 dated Nov. 22, 2023, 5 pages. [cited by applicant]
Notice of Allowance for Chilean Application No. 2021-000335 dated Sep. 15, 2022, 2 pages. [cited by applicant]
Notice of Allowance for Korean Application No. 10-2021-7004763 dated Apr. 28, 2022, 3 pages. [cited by applicant]
Notice of Allowance for Korean Application No. 10-2023-7028554 dated Apr. 3, 2024, 5 pages. [cited by applicant]
Office Action for Algerian Application No. DZ/P/2021/000051 dated Jan. 20, 2022, 2 pages. [cited by applicant]
Office Action for ARIPO Application No. AP/P/2021/012934 dated Oct. 25, 2022, 6 pages. [cited by applicant]
Office Action for Australian Application No. 2019319095 dated May 20, 2022, 4 pages. [cited by applicant]
Office Action for Australian Application No. 2019319095 dated Oct. 27, 2021, 8 pages. [cited by applicant]
Office Action for Canadian Application No. 3,106,505 dated Dec. 5, 2022, 5 pages. [cited by applicant]
Office Action for Canadian Application No. 3,106,505 dated Feb. 25, 2022, 4 pages. [cited by applicant]
Office Action for Canadian Application No. 3,106,505 dated Nov. 21, 2023, 3 pages. [cited by applicant]
Office Action for Chilean Application No. 202100335 dated May 4, 2022, 10 pages. [cited by applicant]
Office Action for Chilean Application No. 202100337 dated Aug. 16, 2022, 18 pages. [cited by applicant]
Office Action for Chilean Application No. 202100337 dated May 4, 2022, 18 pages. [cited by applicant]
Office Action for Chilean Application No. 202100337 dated May 4, 2022, 9 pages. [cited by applicant]
Office Action for Chinese Application No. 201980053388.2 dated Dec. 28, 2023, 20 pages. [cited by applicant]
Office Action for Colombian Application No. NC2021/0002942 dated Nov. 22, 2023, 16 pages. [cited by applicant]
Office Action for European Application No. 19846960.3 dated Apr. 11, 2022, 3 pages. [cited by applicant]
Office Action for Indonesian Application No. P00202101642 dated Jan. 10, 2024, 6 pages. [cited by applicant]
Office Action for Japanese Application No. 2021-506706 dated Apr. 11, 2022, 7 pages. [cited by applicant]
Office Action for Japanese Application No. 2021-506706 dated Jan. 30, 2023, 7 pages. [cited by applicant]
Office Action for Korean Application No. 10-2021-7004763 dated Oct. 28, 2021, 3 pages. [cited by applicant]
Office Action for Korean Application No. 10-2021-7004962 dated Oct. 28, 2022, 10 pages. [cited by applicant]
Office Action for Saudi Arabia Application No. 521421213 dated May 10, 2023. [cited by applicant]
Office Action for Saudi Arabia Application No. 521421213 dated Sep. 20, 2023, 11 pages. [cited by applicant]
Office Action for Singapore Application No. 11202100720P dated Nov. 2, 2022, 13 pages. [cited by applicant]
Partial Supplementary European Search Report for European Application No. 19846960.3 dated Aug. 10, 2022, 22 pages. [cited by applicant]
Qualcomm Incorporated, “Stopping T3519 and Deleting SUCI when Receiving Authentication Reject”, 3GPP TSG-CT WG1 Meeting #116, CR 1039, C1-192290, (Apr. 8-12, 2019), 4 pages. [cited by applicant]
Qualcomm Incorporated, “TS 23.501: De-Registration Procedure for the UE”, SA WG2 Meeting #S2-122, S2-174449, (Jun. 26-30, 2017), 4 pages. [cited by applicant]
Notice of Allowance for Korean Application No. 10-2021-7004962 dated May 23, 2023, 5 pages. [cited by applicant]
Notice of Allowance for Korean Application No. 10-2023-7028554 dated Feb. 24, 2025, 5 pages. [cited by applicant]
Notice of Eligibility of Grant for Singapore Application No. 11202100720P dated Jun. 7, 2023, 6 pages. [cited by applicant]
Office Action for Colombian Application No. NC2024/0004397 dated May 17, 2024, 16 pages. [cited by applicant]
Office Action for Korean Application No. 10-2023-7028554 dated Aug. 1, 2024, 4 pages. [cited by applicant]
CATT, “Discussion on routing registration request using SUCI”, 3GPP TSG-CT WG1 Meeting #111, C1-183437, (May 21-25, 2018), 4 pages. [cited by applicant]
Examination Report for Australian Application No. 2024200276 dated Feb. 20, 2025, 4 pages. [cited by applicant]
Examination Report for Australian Application No. 2024200276 dated Sep. 19, 2024, 3 pages. [cited by applicant]
Nokia et al., “Add Realm part in NAI”, 3GPP TSG-SA WG3 Meeting #91, S3-181472, (Apr. 16-20, 2018), 4 pages. [cited by applicant]
Office Action for Chinese Application No. 201980053388.2 dated Dec. 31, 2024, 13 pages. [cited by applicant]
Office Action for Colombian Application No. NC2021/0002942 dated Sep. 4, 2024, 18 pages. [cited by applicant]
Office Action for Colombian Application No. NC2024/0004397 dated Nov. 29, 2024, 16 pages. [cited by applicant]
Office Action for Japanese Application No. 2023-087590 dated Jan. 20, 2025, 6 pages. [cited by applicant]
Office Action for Japanese Application No. 2023-087590 dated May 1, 2024, 9 pages. [cited by applicant]
Office Action for Japanese Application No. 2024-046265 dated Jan. 20, 2025, 8 pages. [cited by applicant]
Office Action for Malaysian Application No. PI2021000644 dated Jan. 14, 2025, 5 pages. [cited by applicant]
Office Action for Mexican Application No. MX/a/2021/001601 dated Dec. 11, 2023, 12 pages. [cited by applicant]
Office Action for Mexican Application No. MX/a/2021/001601 dated Dec. 12, 2024, 12 pages. [cited by applicant]
Office Action for Mexican Application No. MX/a/2021/001601 dated Jul. 4, 2024, 15 pages. [cited by applicant]
Decision to Grant for Japanese Application No. 2024-046265 dated Jul. 3, 2025, 4 pages. [cited by applicant]
Intention to Grant for European Application No. 19846960.3 dated Mar. 26, 2025, 7 pages. [cited by applicant]
Notice of Acceptance for Australian Application No. 2024200276 dated Jul. 3, 2025, 3 pages. [cited by applicant]
Notice of Acceptance for South African Application No. 2021/01446 dated Jan. 29, 2025, 2 pages. [cited by applicant]
Notice of Grant for Colombian Application No. NC2021/0002942 dated Jan. 27, 2025, 8 pages. [cited by applicant]
Office Action for Brazilian Application No. BR112021002402-6 dated Apr. 8, 2025, 7 pages. [cited by applicant]
Office Action for Chinese Application No. 201980053388.2 dated Apr. 27, 2025, 11 pages. [cited by applicant]
Decision of Refusal for Japanese Application No. 2023-087590 dated Jul. 28, 2025, 4 pages. [cited by applicant]
Notice of Allowance for Mexican Application No. MX/a/2021/001601 dated Jul. 23, 2025, 6 pages. [cited by applicant]
Notice of Allowance for Canadian Application No. 3,106,505 dated Aug. 21, 2025, 1 page. [cited by applicant]
Office Action for ARIPO Application No. AP/P/2024/015569 dated Oct. 9, 2025, 5 pages. [cited by applicant]
Office Action for Vietnamese Application No. 1-2021-01210 dated Sep. 16, 2025, 4 pages. [cited by applicant]
Decision to Grant for Japanese Application No. 2023-087590 dated Dec. 22, 2025, 4 pages. [cited by applicant]
Office Action for Indonesian Application No. P00202101642 dated Dec. 10, 2025, 8 pages. [cited by applicant]
Office Action for Thailand Application No. 2101000732 dated Nov. 25, 2025, 8 pages. [cited by applicant]