IP Library › Granted Patent US 12,641,426
Granted Patent B2
US 12,641,426 · App. 18/800,762 · Granted May 26, 2026

Radio link recovery for user equipment

Inventor: Suresh P. Nair (Whippany, NJ)
Assignee: NOKIA TECHNOLOGIES OY
H04W12/08H04L9/0866H04L9/0894H04L9/3226H04L63/0428H04L41/0654H04L2209/80H04W8/02H04W76/19
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,641,426
App. No.
18/800,762
Granted
May 26, 2026
Kind
B2
Abstract

Following radio link failure (RLF) of a radio link between a cellular internet-of-things (CIoT) user equipment (UE) and a source access node (nodeB) during a data transfer operation over a control plane between a mobility management entity (MME) of a narrow-band IoT (NB-IoT), a radio link is recovered by transmitting an RLF message from the CIoT UE to the MME of the NB-IoT network via a target nodeB, the target nodeB being different from the source nodeB. The RLF message is protected using a key associated with a non-access stratum (NAS) security context previously established between the CIoT UE and the MME of the NB-IoT network. The MME of the NB-IoT network can retrieve data that failed to be delivered to the CIoT UE due to the RLF during the data transfer operation over the control plane and provide said data to the UE via target nodeB.

Claims (44)

1 . A mobility management entity (MME) in a communication system, the MME being operable to recover a radio link, the MME comprising:

at least one processor; and

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

after a non-access stratum (NAS) security context has been established for communication between the MME and a user equipment (UE) in a communication system, during a data transfer operation over a control plane and in response to a radio link failure between the UE and a source access node of the communication system, receiving, from the UE, via a target access node of the communication system, a message indicating that the radio link failure has occurred, the target access node being different than the source access node, the message received via the target access node being protected using a first key associated with the NAS security context previously established between the UE and the MME;

verifying the UE using the first key associated with the NAS security context previously established between the UE and the MME;

retrieving, from the source access node, data that previously failed to be delivered to the UE when the radio link failure occurred during the data transfer operation over the control plane between the MME and the UE;

initiating set-up of a signaling interface with the target access node;

recovering a radio link for the UE by sending a second message to the target access node, the second message being protected using a second key associated with the NAS security context previously established between the UE and the MME, the second message comprising the data that previously failed to be delivered to the UE when the radio link failure occurred during the data transfer operation over the control plane between the MME and the UE.

2 . The MME of claim 1 , wherein the instructions stored on the at least one memory, when executed by the at least one processor, further cause the MME to perform at least:

establishing the NAS security context for communication between the MME and the UE;

generating the first and second keys associated with the NAS security context established between the MME and the UE; and

providing the first and second keys to the UE.

3 . The MME of claim 1 , wherein the second key is a cryptographic key associated with the NAS security context previously established between the UE and the MME, and wherein the second message is protected using the cryptographic key associated with the NAS security context previously established between the UE and the MME.

4 . The MME of claim 1 , wherein the first key is an integrity key associated with the NAS security context previously established between the UE and the MME.

5 . The MME of claim 4 , wherein the verifying the UE is carried out using the integrity key associated with the NAS security context previously established between the UE and the MME.

6 . The MME of claim 4 , wherein the integrity key is generated using at least an uplink message count or a downlink message count.

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

verifying, using the integrity key, the message received from the UE.

8 . The MME of claim 1 , wherein the second key is an encryption key created during establishment of the NAS security context previously established between the UE and the MME.

9 . The MME of claim 1 , wherein the communication system comprises a Narrow Band Internet of Things (NB-IoT) network and the UE comprises a cellular IoT UE.

10 . A user equipment (UE) comprising:

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:

during a data transfer operation over a control plane between a mobility management entity (MME) of a communication system and the UE, in response to a radio link failure occurring between the apparatus and a source access node, generating a first message indicating that the radio link failure has occurred between the UE and the source access node of the communication system, the first message being protected using a first key associated with a non-access stratum (NAS) security context previously established between the UE and the MME of the communication system, the first message indicating that the radio link failure has occurred;

transmitting, to the MME, via a target access node, the first message indicating that the radio link failure has occurred between the UE and the source access node to initiate recovery of a radio link for the UE, the target access node being different than the source access node; and

receiving, in response to the first message, from the MME, via the target access node, a second message protected using a second key associated with the NAS security context previously established between the UE and the MME, the second message comprising data that previously failed to be delivered to the UE when the radio link failure occurred during the data transfer operation over the control plane between the MME and the UE.

11 . The UE of claim 10 , wherein the receiving the second message comprises receiving, in the second message, from the MME, via the target access node, the data that previously failed to be delivered to the UE when the radio link failure occurred during the data transfer operation over the control plane between the MME and the UE.

12 . The UE of claim 10 , wherein the first key is an integrity key associated with the NAS security context previously established between the UE and the MME.

13 . The UE of claim 10 , wherein the first message comprises information regarding a NAS count.

14 . The UE of claim 10 , wherein the instructions stored on the at least one memory, when executed by the at least one processor, further cause the UE to perform at least:

requesting establishment of the NAS security context between the UE and the MME in the communication system; and

receiving, from the MME, via the source access node, with an indication that the NAS security context has been established between the UE and the MME in the communication system, at least one key associated with the NAS security context established between the UE and the MME.

15 . The UE of claim 10 , wherein the radio link failure is detected by the UE.

16 . The UE of claim 10 , wherein the radio link failure is detected by the source access node.

17 . The UE of claim 10 , wherein an access stratum (AS) security context is not established between the UE and the source access node.

18 . The UE of claim 10 , wherein the communication system comprises a Narrow Band Internet of Things (NB-IoT) network, and wherein the UE comprises cellular IoT (CIOT) UE.

19 . The UE of claim 10 , wherein the source access node comprises a first base station and the target access node comprises a second base station, the first and second base stations being distinct from each other and distinct from the MME of the communication system.

20 . A Cellular Internet-of-Things (CIOT) user equipment configured for receiving data in a Narrow Band IoT (NB-IoT) network via a radio link, the CIOT user equipment comprising:

at least one processor; and

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

requesting establishment of a non-access stratum (NAS) security context between the user equipment and a mobility management entity (MME) of the communication system;

receiving, from the MME, with an indication that the NAS security context has been established between the user equipment and the MME, an integrity key or information regarding the integrity key, the integrity key being created during establishment of the NAS security context between the user equipment and the MME;

in response to a radio link failure (RLF) occurring between the user equipment and a source access node of the communication system during a data transfer operation over a control plane between the MME and the user equipment, initiating recovery of the radio link by sending a first message to the MME through a target access node of the communication system, without using the source access node to relay the first message, while maintaining the NAS security context previously established between the user equipment and the MME, wherein the first message is integrity protected using the integrity key created during establishment of the NAS security context between the user equipment and the MME, and wherein the target access node is different from the source access node; and

receiving, from the target access node, a second message protected using the integrity key associated with the NAS security context previously established between the user equipment and the MME, the second message comprising data that previously failed to be delivered to the user equipment when the RLF occurred during the data transfer operation over the control plane between the MME and the user equipment.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2025
From: NAIR, SURESH P.
To: ALCATEL-LUCENT USA INC.
Reel/Frame 071108/0802 →
MERGER AND CHANGE OF NAME Recorded May 14, 2025
From: ALCATEL-LUCENT USA INC.; NOKIA SOLUTIONS AND NETWORKS US LLC
To: NOKIA OF AMERICA CORPORATION
Reel/Frame 071109/0071 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2025
From: NOKIA OF AMERICA CORPORATION
To: NOKIA TECHNOLOGIES OY
Reel/Frame 071109/0330 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 12, 2024
From: NAIR, SURESH P.
To: ALCATEL-LUCENT USA INC.
Reel/Frame 068252/0280 →
Continuity (5)
Continuation 17976047 · Oct 28, 2022
Continuation 16953933 · Nov 20, 2020
Continuation 15700940 · Sep 11, 2017
Provisional Application 62488179 · Apr 21, 2017
Related Publication 20240406728A1 · Dec 5, 2024
References Cited (158)
US 9049698B2 · Johansson et al. · 2015 [cited by applicant]
US 9867226B2 · Kubota et al. · 2018 [cited by applicant]
US 9918262B2 · Xu et al. · 2018 [cited by applicant]
US 10034208B2 · Moon et al. · 2018 [cited by applicant]
US 10462837B2 · Escott et al. · 2019 [cited by applicant]
US 10623990B2 · Chun et al. · 2020 [cited by applicant]
US 10694383B2 · Cho et al. · 2020 [cited by applicant]
US 10917789B2 · Nair · 2021 [cited by applicant]
US 11523280B2 · Nair · 2022 [cited by applicant]
US 12063507B2 · Nair · 2024 [cited by examiner]
US 20080102843A1 · Todd et al. · 2008 [cited by applicant]
US 20080242292A1 · Koskela et al. · 2008 [cited by applicant]
US 20100166184A1 · Wu · 2010 [cited by applicant]
US 20110092236A1 · Iwamura et al. · 2011 [cited by applicant]
US 20110110227A1 · Yang et al. · 2011 [cited by applicant]
US 20110159841A1 · Escott et al. · 2011 [cited by applicant]
US 20120197801A1 · Jimenez · 2012 [cited by applicant]
US 20130035056A1 · Prasad et al. · 2013 [cited by applicant]
US 20140064065A1 · Rogers et al. · 2014 [cited by applicant]
US 20150223106A1 · Van Phan et al. · 2015 [cited by applicant]
US 20150269028A1 · Horn et al. · 2015 [cited by applicant]
US 20160050604A1 · Lee et al. · 2016 [cited by applicant]
US 20160366571A1 · Payne et al. · 2016 [cited by applicant]
US 20170099621A1 · Michaelsen et al. · 2017 [cited by applicant]
US 20170099682A1 · Priyanto et al. · 2017 [cited by applicant]
US 20170332440A1 · Xu et al. · 2017 [cited by applicant]
US 20180132293A1 · Escott et al. · 2018 [cited by applicant]
US 20180270891A1 · Kim et al. · 2018 [cited by applicant]
US 20180309575A1 · Nair · 2018 [cited by applicant]
US 20190021023A1 · Byun et al. · 2019 [cited by applicant]
US 20190045349A1 · Kim et al. · 2019 [cited by applicant]
CA 3038129 · 2018 [cited by applicant]
CN 101835156A · 2010 [cited by applicant]
CN 102075938A · 2011 [cited by applicant]
CN 105191479A · 2015 [cited by applicant]
CO 6781508A2 · 2013 [cited by applicant]
EP 2645804A1 · 2013 [cited by applicant]
GB 455827 · 1936 [cited by applicant]
GB 2455707A · 2009 [cited by applicant]
JP 2021106406A · 2021 [cited by applicant]
RU 2461990C2 · 2012 [cited by applicant]
RU 2492596C2 · 2013 [cited by applicant]
WO WO2009075341A1 · 2009 [cited by applicant]
WO WO2013166679A1 · 2013 [cited by applicant]
WO WO2016140403A1 · 2016 [cited by applicant]
WO WO2016164808A1 · 2016 [cited by applicant]
WO WO2018194809A1 · 2018 [cited by applicant]
Extended Hearing Notice for Indian Application No. 201947045113 dated Mar. 4, 2025, 2 pages. [cited by applicant]
Notice of Grant for Colombian Application No. NC2019/0012011 dated Feb. 25, 2025, 18 pages. [cited by applicant]
Office Action for Indonesian Application No. P00201909835 dated Feb. 14, 2025, 4 pages. [cited by applicant]
Office Action for Philippine Application No. 1/2019/502372 dated Jul. 28, 2025, 4 pages. [cited by applicant]
Notice of Allowance for Vietnamese Application No. 1-2019-06524 dated Sep. 24, 2025, 2 pages. [cited by applicant]
Office Action for Canadian Application No. 3,060,420 dated Oct. 21, 2025, 3 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (Release 14)”, 3GPP TS 24.301 v14.4.0, (Jun. 2017… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture (Release 14)”, 3GPP TS 33.401 v14.4.0, (Sep. 2017), 153 pag… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture (Release 16)”, 3GPP TS 33.401 v16.3.0, (Jul. 2020), 170 pag… [cited by applicant]
“LTE; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall Description; Stage 2”, 3GPP TS 36.300 v14.2.0, (Apr. 2017), 346 pages. [cited by applicant]
“Reply LS on Mobility Enhancements for eNB-IoT”, 3GPP TSG-RAN WG3 Meeting #95, R3-170881, (Feb. 13-17, 2017), 1 page. [cited by applicant]
3GPP RAN2, “Security Aspects of RRC Connection Re-Establishment for NB-IoT (DoNAS)”, 3GPP TSG SA WG3 (Security) Meeting #85, S3-161934, (Nov. 7-11, 2016), 1 page. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) Related Interfaces … [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access Stratum (NAS) Protocol for Evolved Packet System (EPS); Stage 3 (Release 14), ” 3GPP TS 24.301, V14.2.0, De… [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overal… [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 14),” 3GPP TS 36.413, … [cited by applicant]
3GPP, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security Architecture (Release 14), 3GPP TS 33.401, V14.1.0, Dec. 2016, 152 … [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Acc… [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15),” 3GPP TS 23.502, V0.1.0, Jan. 2017, 44 pages. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on the Security Aspects of the Next Generation System (Release 14), ” 3GPP TR 33.899, V1.1.0, Mar. 2017, 491 pa… [cited by applicant]
3GPP, “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, V0.4.0, Apr. 2017, 124 pages. [cited by applicant]
3GPP, “A Solution for RLF in CP NB-IoT”; Ericsson; NB-IOT / Rel 14; 3GPP TSG-SA WG3 Meeting #86, dated Feb. 6-10, 2017, 5 pages. [cited by applicant]
3GPP, “Connected Mode Mobility For NB-IOT UE Using CP CloT EPS Optimisation”; Intel Corporation, Agenda Item 3.11.3; TSG-RAN WG2 #95bis; R2-166683; dated Oct. 10-14, 2016, 6 pages. [cited by applicant]
3GPP, “Protecting the RLF Procedure for NB-IoT UEs using the NAS Security Context”; Qualcomm Incorporated; 3GPP TSG SA WG3 (Security) Meeting #86, dated Feb. 6-10, 2017, 3 pages. [cited by applicant]
3GPP, “Reply LS on Security Aspects of RRC Connection Re-Establishment for NB-IoT (DoNAS)”; Rel-14; NB_IOTenh; 3GPP TSG SA WG3 (Security) Meeting #85, dated Nov. 7-11, 2017, 2 pages. [cited by applicant]
3GPP, “RLF Situation for Control Plane CIoT EPS Optimizations Solution”; HW; S3-170332; 3GPP TSG SA WG3 (Security) Meeting #86, dated Feb. 6-10, 2017, 4 pages. [cited by applicant]
3GPP, “Security for the RLFs for UEs Doing User Plane Over Control Plane Using NAS Level Security,” Qualcomm Incorporated; S3-171997, TEI14 (Release 14), 3GPP TSG-SA WG3 Meeting #88, Aug. 2017, 2 pages. [cited by applicant]
3GPP, “Security for the RLFs for UEs Doing User Plane Over Control Plane Using NAS Level Security,” Qualcomm Incorporated; S3-172137, TEI14 (Release 14), 3GPP TSG-SA WG3 Meeting #88, Aug. 2017, 2 pages. [cited by applicant]
3GPP, “Security of RRC Connection Re-establishment of NB-IOT for CP Solution”; Intel Corporation, NB-IOT/Rel-14; 3GPP TSG SA WG3 (Security) Meeting #86, dated Feb. 6-10, 2017, 6 pages. [cited by applicant]
3GPP, “Security Solution to Support CIoT Optimization for Large File Transfer”; Nokia; NB-IOT/Rel-14; 3GPP TSG SA WG3 (Security) Meeting #86, dated Feb. 6-10, 2017, 6 pages. [cited by applicant]
Decision to Grant a Patent for an Invention for Russian Patent Application No. 2019134998/07, dated Dec. 11, 2020, with English translation, 24 pages. [cited by applicant]
Decision to Grant for Japanese Application No. 2021-059583 dated Jun. 1, 2022, 6 pages. [cited by applicant]
Decision to Grant for Japanese Application No. 2021-209119 dated Jun. 3, 2024, 4 pages. [cited by applicant]
Ericsson et al., “Updated solution for RLF in CP CIoT EPS optimizations”, 3GPP TSG-SA WG3 Meeting #xx, S3A0007, (May 2, 2017), 4 pages. [cited by applicant]
Ericsson, “A Solution for RLF in CP NB-IoT”, 3GPP TSG-SA WG3 Meeting #86, S3-170254, (Feb. 6-10, 2017), 5 pages. [cited by applicant]
Ericsson, “Response to R3-162761-R3-162764”, 3GPP TSG-RAN WG3 Meeting #94, R3-163075, (Nov. 14-18, 2016), 2 pages. [cited by applicant]
Examination Report No. 1 for Standard Patent Application for Australian Patent Application No. 2018254323 dated Dec. 23, 2020, 5 pages. [cited by applicant]
Form 21 Decision to Grant for Kenya Application No. AP/P/2019/011935 dated May 10, 2021, 5 pages. [cited by applicant]
Huawei (Rapporteur), “Offline discussion on CP mobility”, 3GPP TSG-RAN Meeting #95, R3-170425, (Feb. 13-17, 2017), 3 pages. [cited by applicant]
Huawei et al., “NAS Security Solution for DoNAS RLF”, 3GPP TSG SA WG3 (Security) eMeeting on DoNAS (NB-IoT), S3A0008, (May 2, 2017), 3 pages. [cited by applicant]
Huawei et al., “RRC impact of RRC connection Re-establishment based on NAS solution A”, 3GPP TSG-RAN WG2 Meeting #98, R2-1705394, (Feb. 15-29, 2017), 5 pages. [cited by applicant]
Huawei, “Details on NAS Message Handling During X2 Handover”, 3GPP TSG RAN WG3 Meeting #57bis, R3-071944, (Oct. 8-11, 2007), 8 pages. [cited by applicant]
Intel Corporation, “Security of RRC Connection re-establishment of NB-IOT for CP Solution”, 3GPP TSG SA WG3 (Security) Meeting #86, S3-170162, (Feb. 6-10, 2017), 6 pages. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2018/025008 dated Jul. 3, 2018, 9 pages. [cited by applicant]
MediaTek Inc., “Feasibility of Lossless Mobility for the CP Solution”, 3GPP TSG-RAN3 #96 Meeting, R3-163067, (Nov. 14-18, 2016), 3 pages. [cited by applicant]
Nokia, “Solution for RLF in CP NB-IoT using NAS context and NAS keys”, 3GPP TSG-SA WG3 Meeting #xx, S3A0003, (May 2, 2017), 3 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/953,933 dated Jan. 14, 2022. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/976,047 dated Dec. 18, 2023. [cited by applicant]
Notice of Acceptance for Australian Application No. 2018254323 dated Jun. 23, 2021, 3 pages. [cited by applicant]
Notice of Acceptance for Nigeria Application No. NG/PT/C/2019/4097 dated Nov. 2020, 2 pages. [cited by applicant]
Notice of Acceptance for South Africa Application No. 2019/07516 dated Apr. 14, 2021, 1 page. [cited by applicant]
Notice of Allowance for Chinese Application No. 201880037225.0 dated Jun. 12, 2023, 4 pages. [cited by applicant]
Notice of Allowance for Korean Application No. 10-2019-7034413 dated Apr. 12, 2021, 3 pages. [cited by applicant]
Notice of Allowance for Singapore Application No. 11201909741U dated Jun. 9, 2023, 6 pages. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 15/700,940 dated Jul. 6, 2020. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 15/700,940 dated Oct. 22, 2020. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 16/953,933 dated Jul. 29, 2022. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 16/953,933 dated May 20, 2022. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/976,047 dated Apr. 10, 2024. [cited by applicant]
NTT Docomo, “GBR Bearer Termination at Radio Link Failure”, 3GPP TSG SA WG2 Meeting #75, S2-095242, (Aug. 31-Sep. 4, 2009), 3 pages. [cited by applicant]
Office Action for Canadian Application No. 3,060,420 dated Feb. 3, 2023, 4 pages. [cited by applicant]
Office Action for Canadian Application No. 3,060,420 dated Jul. 5, 2022, 4 pages. [cited by applicant]
Office Action for Canadian Application No. 3,060,420 dated Nov. 21, 2023, 4 pages. [cited by applicant]
Office Action for Canadian Application No. 3060420 dated Aug. 26, 2021, 3 pages. [cited by applicant]
Office Action for Canadian Patent Application No. 3,060,420 dated Dec. 3, 2020, 4 pages. [cited by applicant]
Office Action for Chinese Application No. 201880037225.0 dated Mar. 18, 2023, 9 pages. [cited by applicant]
Office Action for Chinese Application No. 201880037225.0 dated Sep. 19, 2022, 11 pages. [cited by applicant]
Office Action for Colombian Application No. NC2019/0012011 dated Apr. 17, 2024, 12 pages. [cited by applicant]
Office Action for Colombian Application No. NC2019/0012011 dated May 9, 2022, 15 pages. [cited by applicant]
Office Action for European Application No. 18720686.7 dated Jan. 15, 2024, 7 pages. [cited by applicant]
Office Action for European Application No. 18720686.7 dated Mar. 1, 2023, 7 pages. [cited by applicant]
Office Action for European Application No. 18720686.7 dated Mar. 11, 2021, 7 pages. [cited by applicant]
Office Action for Japanese Application No. 2019-556832 dated Aug. 23, 2021, 8 pages. [cited by applicant]
Office Action for Japanese Application No. 2019-556832 dated Aug. 3, 2022, 7 pages. [cited by applicant]
Office Action for Japanese Application No. 2021-209119 dated Apr. 3, 2023, 11 pages. [cited by applicant]
Office Action for Japanese Application No. 2021-209119 dated Nov. 1, 2023, 3 pages. [cited by applicant]
Office Action for Japanese Application No. 2022-107180 dated May 30, 2024, 12 pages. [cited by applicant]
Office Action for Japanese Application No. 2022-107180 dated Sep. 14, 2023, 13 pages. [cited by applicant]
Office Action for Japanese Patent Application No. 2019-556832, dated Nov. 9, 2020, with English translation, 5 pages. [cited by applicant]
Office Action for Kenya Application No. AP/P/2019/011935 dated Oct. 30, 2020, 4 pages. [cited by applicant]
Office Action for Korean Application No. 10-2019-7034413 dated Nov. 9, 2020, 7 pages. [cited by applicant]
Office Action for Malaysian Application No. PI2019006176 dated Apr. 2, 2024, 3 pages. [cited by applicant]
Office Action for Mexican Application No. MX/a/2019/012533 dated Sep. 12, 2023, 10 pages. [cited by applicant]
Office Action for Mexico Application No. MX/a/2019/012533 dated Dec. 6, 2022, 10 pages. [cited by applicant]
Office Action for Mexico Application No. MX/a/2019/012533 dated Mar. 28, 2023, 8 pages. [cited by applicant]
Office Action for Russian Application No. 2019134998/07 dated May 14, 2020, 8 pages. [cited by applicant]
Office Action for Russian Application No. 2019134998/07 dated Sep. 3, 2020. [cited by applicant]
Office Action for Singapore Application No. 11201909741U dated Mar. 7, 2022, 7 pages. [cited by applicant]
Office Action for U.S. Appl. No. 15/700,940 dated Apr. 16, 2020. [cited by applicant]
Office Action for U.S. Appl. No. 15/700,940 dated Jan. 7, 2020. [cited by applicant]
Office Action for U.S. Appl. No. 15/700,940 dated Jun. 3, 2019. [cited by applicant]
Office Action for U.S. Appl. No. 15/700,940 dated Sep. 12, 2019. [cited by applicant]
Qualcomm Incorporated, “Introduction of RRC connection re-establishment for NB-IoT control plane”, 3GPP TSG-RAN WG2 Meeting #98, 36.331 Change Request 2823, R2-1704707, (May 15-19, 2017), 7 pages. [cited by applicant]
Qualcomm Incorporated, “On Mobility in CP-CIoT”, 3GPP TSG-RAN WG3 Meeting #95, R3-170655, (Feb. 13-17, 2017), 4 pages. [cited by applicant]
Qualcomm Incorporated, “Protecting the RLF Procedure for NB-IoT Ues Using the NAS Security Context”, 3GPP TSG SA WG3 (Security) Meeting #86, S3-170302, (Feb. 6-10, 2017), 4 pages. [cited by applicant]
Qualcomm Incorporated, “RRC Re-Establishment for CP”, 3GPP TSG RAN WG2 #98, R2-1704709, (May 15-19, 2017), 4 pages. [cited by applicant]
RAN2, “Reply LS on security for RLF for DoNAS UEs”, 3GPP TSG RAN WG2 #98, R2-1705939, (May 15-19, 2017), 1 page. [cited by applicant]
SA WG3, “Reply LS on Security aspects of RRC Connection Re-Establishment for NB-IoT (DoNAS)”, 3GPP TSG SA WG3 (Security) Meeting #85, S3- 162088, (Nov. 7-11, 2016), 2 pages. [cited by applicant]
SA3, “LS to RAN2 and RAN3 on security for RLFs for DoNAS UEs”, 3GPP TSG SA WG3 (Security) eMeeting on DoNAS (NB-IoT), Tdoc S3A0009, (May 2, 2017), 1 page. [cited by applicant]
Search Report and Written Opinion for Singapore Patent Application No. 11201909741U dated Jan. 12, 2021, 8 pages. [cited by applicant]
Supplemental Notice of Allowability for U.S. Appl. No. 15/700,940, filed Sep. 11, 2017. [cited by applicant]
Trial and Appeal Decision for Japanese Application No. 2019-556832 dated Feb. 20, 2023, 4 pages. [cited by applicant]
ZTE, “Discussion on Security Method of Mobility Enhancement for NBIoT CP Solution”, 3GPP TSG SA WG3 (Security) Meeting #86, S3-170077, (Feb. 6-10, 2017), 5 pages. [cited by applicant]
ZTE, “The CP solution for NB IoT mobility enhancement”, 3GPP TSG RAN WG3 Meeting #95, R3-170600, (Feb. 13-17, 2017), 3 pages. [cited by applicant]
Decision to Grant for Japanese Application No. 2022-107180 dated Jan. 27, 2025, 4 pages. [cited by applicant]
Hearing Notice for Indian Application No. 201947045113 dated Dec. 4, 2024, 3 pages. [cited by applicant]
Notice of Allowance for Mexican Application No. MX/a/2019/012533 dated Mar. 22, 2024, 6 pages. [cited by applicant]
Office Action for Malaysian Application No. PI2019006176 dated Nov. 5, 2024, 1 page. [cited by applicant]
Office Action for Philippine Application No. Jan. 2019/502372 dated Jun. 20, 2024, 5 pages. [cited by applicant]
Notice of Allowance for Philippine Application No. 1/2019/502372 dated Feb. 26, 2026, 2 pages. [cited by applicant]
Notice of Reasons for Refusal for Japanese Application No. 2025-028855 dated Feb. 19, 2026, 13 pages. [cited by applicant]