IP Library › Granted Patent US 12,200,806
Granted Patent B2
US 12,200,806 · App. 18/231,068 · Granted Jan 14, 2025

Handling of inactive parameters upon release and re-suspend

Inventors: Gunnar Mildh (Sollentuna, SE); Icaro L. J. Da Silva (Solna, SE)
Assignee: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
H04W76/27H04W68/005H04W76/11H04W76/19H04W76/30
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,200,806
App. No.
18/231,068
Granted
Jan 14, 2025
Kind
B2
Abstract

Systems and methods are disclosed herein for updating stored User Equipment (UE) context information upon re-suspend of the UE in response to a resume request from the UE. In some embodiments, a method in a UE comprises transmitting a Radio Resource Control (RRC) resume request message and, in response to the RRC resume request message, receiving an RRC connection release message with an indication for suspend. The method further comprises, in response to receiving the RRC connection release message with an indication for suspend, replacing information in a stored Access Stratum (AS) context of the UE with new information.

Claims (43)

1. A method, implemented by a User Equipment (UE) or network node, the method comprising:

exchanging Radio Resource Control (RRC) messaging between the UE and the network node, the RRC messaging comprising an RRC connection release message comprising a suspend indication; and

replacing information in a stored Access Stratum (AS) context of the UE with new information comprised in the RRC connection release message.

2. The method of claim 1 , wherein replacing the information comprises replacing:

a stored cell identity with a cell identity of a cell in which the UE received the RRC connection release message;

a stored physical cell identity with a physical cell identity of the cell in which the UE received the RRC connection release message; and

a stored Cell Radio Network Temporary Identifier (C-RNTI) with a C-RNTI obtained by the UE for the cell in which the UE received the RRC connection release message.

3. The method of claim 1 , wherein:

replacing the information comprises replacing stored security context information with security context information comprised in the RRC connection release message; and

the security context information comprises a next hop chaining count.

4. The method of claim 1 , wherein replacing the information comprises replacing a stored Inactive Radio Network Temporary Identifier (I-RNTI) with an I-RNTI comprised in the RRC connection release message.

5. The method of claim 1 , wherein replacing the information comprises replacing a stored C-RNTI with a C-RNTI obtained by the UE for a cell in which the UE received the RRC connection release message.

6. The method of claim 5 , wherein the C-RNTI is a temporary C-RNTI.

7. The method of claim 1 , wherein replacing the information comprises replacing a stored cell identity with a cell identity of a cell in which the UE received the RRC connection release message.

8. The method of claim 1 , wherein:

replacing the information provides an updated AS context of the UE; and

the RRC messaging further comprises a subsequent RRC resume request that uses the updated AS context of the UE, wherein the subsequent RRC resume request is from the UE to the network node.

9. The method of claim 8 , wherein the subsequent RRC resume request comprises a security integrity token derived from the updated AS context of the UE.

10. The method of claim 1 , wherein replacing the information comprises replacing a stored physical cell identity with a physical cell identity of a cell in which the UE received the RRC connection release message.

11. A network device, wherein the network device is either a User Equipment (UE) or a network node, the network device comprising:

a radio interface; and

processing circuitry associated with the radio interface, wherein the processing circuitry is configured to cause the network device to:

exchange Radio Resource Control (RRC) messaging between the UE and the network node, the RRC messaging comprising an RRC connection release message comprising a suspend indication; and

replace information in a stored Access Stratum (AS) context of the UE with new information comprised in the RRC connection release message.

12. The network device of claim 11 , wherein to replace the information in the stored AS context of the UE, the network device is configured to replace:

a stored cell identity with a cell identity of a cell in which the UE received the RRC connection release message;

a stored physical cell identity with a physical cell identity of the cell in which the UE received the RRC connection release message; and

a stored Cell Radio Network Temporary Identifier (C-RNTI) with a C-RNTI obtained by the UE for the cell in which the UE received the RRC connection release message.

13. The network device of claim 11 , wherein:

to replace the information in the stored AS context of the UE, the network device is configured to replace stored security context information with security context information comprised in the RRC connection release message; and

the security context information comprises a next hop chaining count.

14. The network device of claim 11 , wherein to replace the information in the stored AS context of the UE, the network device is configured to replace a stored Inactive Radio Network Temporary Identifier (I-RNTI) with an I-RNTI comprised in the RRC connection release message.

15. The network device of claim 11 , wherein to replace the information in the stored AS context of the UE, the network device is configured to replace a stored C-RNTI with the C-RNTI obtained by the UE for a cell in which the UE received the RRC connection release message.

16. The network device of claim 15 , wherein the C-RNTI is a temporary C-RNTI.

17. The network device of claim 11 , wherein to replace the information in the stored AS context of the UE, the network device is configured to replace a stored cell identity with a cell identity of a cell in which the UE received the RRC connection release message.

18. The network device of claim 11 , wherein:

replacing the information provides an updated AS context of the UE; and

the RRC messaging further comprises a subsequent RRC resume request that uses the updated AS context of the UE, wherein the subsequent RRC resume request is from the UE to the network node.

19. The network device of claim 18 , wherein the subsequent RRC resume request comprises a security integrity token derived from the updated AS context of the UE.

20. The network node of claim 11 , wherein to replace the information in the stored AS context of the UE, the network device is configured to replace a stored physical cell identity with a physical cell identity of a cell in which the UE received the RRC connection release message.

21. A non-transitory computer readable medium storing a computer program product for controlling a network device in a wireless communication network, the network device being a User Equipment (UE) or network node and the computer program product comprising software instructions that, when run on the network device, cause the network device to:

exchange Radio Resource Control (RRC) messaging between the UE and the network node, the RRC messaging comprising an RRC connection release message comprising a suspend indication; and

replace information in a stored Access Stratum (AS) context of the UE with new information comprised in the RRC connection release message.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 8, 2023
From: DA SILVA, ICARO L. J.; MILDH, GUNNAR
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 064521/0395 →
Continuity (5)
Continuation 17409662 · Aug 23, 2021
Continuation 16657296 · Oct 18, 2019
Continuation 16386148 · Apr 16, 2019
Provisional Application 62657974 · Apr 16, 2018
Related Publication 20230413373A1 · Dec 21, 2023
References Cited (16)
US 10485051B2 · Mildh et al. · 2019 [cited by applicant]
US 11116031B2 · Mildh · 2021 [cited by applicant]
US 20120276913A1 · Lim · 2012 [cited by examiner]
US 20140226568A1 · Jeong · 2014 [cited by examiner]
US 20150092688A1 · Jeong et al. · 2015 [cited by applicant]
US 20170202051A1 · Hwang · 2017 [cited by examiner]
US 20170325282A1 · Hong et al. · 2017 [cited by applicant]
US 20180270894A1 · Park et al. · 2018 [cited by applicant]
US 20190357105A1 · Zhang et al. · 2019 [cited by applicant]
EP 2645803A1 · 2013 [cited by applicant]
EP 3073649A1 · 2016 [cited by applicant]
WO 2013144606A1 · 2013 [cited by applicant]
Intel, “Stage 3 RRC TP on RRC_Inactive state for E-UTRA connected to 5GC”, 3GPP TSG-RAN2 Meeting #1010bis, Sanya, China, Apr. 16-20, 2018, pp. 1-60, R2-1805051, 3GPP. [cited by applicant]
Oppo, “Left issues for Inactive security framework”, 3GPP TSG-RAN2 #101bis, Sanya, China, Apr. 16-20, 2018, pp. 1-8, R2-1804551, 3GPP. [cited by applicant]
HTC, “Network controlled mobility to 5GC or EPC”, 3GPP TSG-RAN WG2 #101bis, Sanya, China, Apr. 16-20, 2018, pp. 1-17, R2-1805950, 3GPP. [cited by applicant]
3rd Generation Partnership Project, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14)”, Technical Report, 3GPP … [cited by applicant]