IP Library Granted Patent US 12,336,039
Granted Patent B2
US 12,336,039 · App. 17/855,166 · Granted Jun 17, 2025

Context management method and apparatus

Inventors: Xiaoying Xu (Shenzhen, CN); Chunhua You (Shanghai, CN); Qinghai Zeng (Shanghai, CN); Qufang Huang (Shenzhen, CN); Chong Lou (Shanghai, CN)
Assignee: Huawei Technologies Co., Ltd.
H04W76/27H04W76/32H04W36/0033
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,336,039
App. No.
17/855,166
Granted
Jun 17, 2025
Kind
B2
Abstract

A context management method includes: when a distributed unit (DU) of a network side device receives a first message from a centralized unit (CU) of the network side device, the DU of the network side device may store a context of the terminal side device in an inactive state. The first message includes a second message, and the second message is used to indicate the terminal side device to enter the inactive state and release a connection to the network side device.

Claims (60)

1. A context management method, comprising:

receiving, by a distributed unit (DU) of a network side device, a first message from a centralized unit (CU) of the network side device, wherein the first message comprises a second message, and the second message indicates that a terminal side device is to enter an inactive state and release a connection to the network side device;

storing, by the DU of the network side device, a context of the terminal side device in the inactive state, wherein the stored context is for the DU to receive uplink data from the terminal side device while the terminal side device is in the inactive state; and

receiving, by the DU, based on the stored context of the terminal side device, uplink data from the terminal side device while the terminal side device is in the inactive state;

wherein the first message comprises first information, and the first information indicates that the DU of the network side device is to store an air interface context in the context of the terminal side device; and

wherein storing the context of the terminal side device includes storing the air interface context of the terminal side device based on the first information.

2. The method according to claim 1 , wherein the first information further indicates that the DU of the network side device is to store an F1 context in the context of the terminal side device;

wherein the F1 context comprises a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface-dedicated transmission tunnel corresponding to data radio bearer (DRB) data of the terminal side device.

3. The method according to claim 1 , wherein the first message is an interface message between the CU of the network side device and the DU of the network side device, but does not include a user equipment (UE) context release command message.

4. The method according to claim 1 , wherein the context comprises one or more of the following:

a configured grant configured for the terminal side device;

configuration information of a physical downlink control channel (PDCCH) configured for the terminal side device;

a temporary identity for scrambling the PDCCH; or

configuration information of a radio link control (RLC) layer of a radio bearer configured for the terminal side device.

5. A context management method, comprising:

generating, by a centralized unit (CU) of a network side device, a first message based on determining that a terminal side device is to enter an inactive state, wherein the first message comprises a second message, and the second message indicates that the terminal side device is to enter the inactive state and release a connection to the network side device; and

sending, by the CU of the network side device, the first message to a distributed unit (DU) of the network side device, wherein the first message indicates that the DU of the network side device is to store a context of the terminal side device in the inactive state, wherein the stored context is for the DU to receive uplink data from the terminal side device while the terminal side device is in the inactive state;

wherein the first message comprises first information, and the first information indicates that the DU of the network side device is to store an air interface context in the context of the terminal side device.

6. The method according to claim 5 , wherein the first information further indicates that the DU of the network side device is to store an F1 context in the context of the terminal side device;

wherein the F1 context comprises a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface-dedicated transmission tunnel corresponding to data radio bearer (DRB) data of the terminal side device.

7. The method according to claim 5 , wherein the first message is an interface message between the CU of the network side device and the DU of the network side device, but does not include a user equipment (UE) context release command message.

8. The method according to claim 5 , wherein the context comprises one or more of the following:

a configured grant configured for the terminal side device;

configuration information of a physical downlink control channel (PDCCH) configured for the terminal side device;

a temporary identity for scrambling the PDCCH; or

configuration information of a radio link control (RLC) layer of a radio bearer configured for the terminal side device.

9. An apparatus comprising:

at least one processor; and

at least one memory storing instructions;

wherein the at least one processor is configured to execute the instructions to facilitate performance of the following operations by a distributed unit (DU) of a network side device;

receiving a first message from a centralized unit (CU) of the network side device, wherein the first message comprises a second message, and the second message indicates that a terminal side device is to enter an inactive state and release a connection to the network side device;

storing a context of the terminal side device in the inactive state, wherein the stored context is for the DU to receive uplink data from the terminal side device while the terminal side device is in the inactive state; and

receiving, by the DU, based on the stored context of the terminal side device, uplink data from the terminal side device while the terminal side device is in the inactive state;

wherein the first message comprises first information, and the first information indicates that the DU of the network side device is to store an air interface context in the context of the terminal side device; and

wherein storing the context of the terminal side device includes storing the air interface context of the terminal side device based on the first information.

10. The apparatus according to claim 9 , wherein the first information further indicates that the DU of the network side device is to store an F1 context in the context of the terminal side device;

wherein the F1 context comprises a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface-dedicated transmission tunnel corresponding to data radio bearer (DRB) data of the terminal side device.

11. The apparatus according to claim 9 , wherein the first message is an interface message between the CU of the network side device and the DU of the network side device, but does not include a user equipment (UE) context release command message in the interface message.

12. The apparatus according to claim 9 , wherein the context comprises one or more of the following:

a configured grant configured for the terminal side device;

configuration information of a physical downlink control channel (PDCCH) configured for the terminal side device;

a temporary identity for scrambling the PDCCH; or

configuration information of a radio link control (RLC) layer of a radio bearer configured for the terminal side device.

13. An apparatus, comprising:

at least one processor; and

at least one memory storing instructions;

wherein the at least one processor is configured to execute the instructions to facilitate performance of the following operations by a centralized unit (CU) of a network side device:

generating a first message based on determining that a terminal side device is to enter an inactive state, wherein the first message comprises a second message, and the second message indicates that the terminal side device is to enter the inactive state and release a connection to the network side device; and

sending the first message to a distributed unit (DU) of the network side device, wherein the first message indicates that the DU of the network side device is to store a context of the terminal side device in the inactive state, wherein the stored context is for the DU to receive uplink data from the terminal side device while the terminal side device is in the inactive state;

wherein the first message comprises first information, and the first information indicates that the DU of the network side device is to store an air interface context in the context of the terminal side device.

14. The apparatus according to claim 13 , wherein the first information further indicates that the DU of the network side device is to store an F1 context in the context of the terminal side device;

wherein the F1 context comprises a data transmission channel of the terminal side device, and the data transmission channel is an F1 interface-dedicated transmission tunnel corresponding to data radio bearer (DRB) data of the terminal side device.

15. The apparatus according to claim 13 , wherein the first message is an interface message between the CU of the network side device and the DU of the network side device, but does not include a user equipment (UE) context release command message.

16. The apparatus according to claim 13 , wherein the context comprises one or more of the following:

a configured grant configured for the terminal side device;

configuration information of a physical downlink control channel (PDCCH) configured for the terminal side device;

a temporary identity for scrambling the PDCCH; or

configuration information of a radio link control (RLC) layer of a radio bearer configured for the terminal side device.

17. The apparatus according to claim 13 , wherein the apparatus is a chip of the CU.

18. The apparatus according to claim 9 , wherein the apparatus is a chip of the DU.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2025
From: XU, XIAOYING; YOU, CHUNHUA; ZENG, QINGHAI; LOU, CHONG
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 071103/0819 →
EMPLOYEE AGREEMENT Recorded May 13, 2025
From: HUANG, QUFANG
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 071263/0728 →
Continuity (2)
Continuation PCTCN2019130987 · Dec 31, 2019
Related Publication 20220338298A1 · Oct 20, 2022
References Cited (30)
US 11510175B2 · Zeng · 2022 [cited by examiner]
US 11582828B2 · Yang · 2023 [cited by examiner]
US 20180227851A1 · Kubota · 2018 [cited by examiner]
US 20180302914A1 · da Silva · 2018 [cited by examiner]
US 20190327647A1 · Ozturk · 2019 [cited by examiner]
US 20190327711A1 · Zhang · 2019 [cited by examiner]
US 20190342936A1 · Wu · 2019 [cited by examiner]
US 20200137564A1 · Liu · 2020 [cited by examiner]
US 20200229049A1 · Wu · 2020 [cited by examiner]
US 20200374947A1 · Jin · 2020 [cited by examiner]
US 20200383164A1 · Kim · 2020 [cited by examiner]
US 20210007170A1 · Liu · 2021 [cited by examiner]
US 20210185755A1 · Kim · 2021 [cited by examiner]
US 20220030489A1 · Sharma · 2022 [cited by examiner]
US 20220086944A1 · Kim · 2022 [cited by examiner]
US 20220232669A1 · Yang · 2022 [cited by examiner]
US 20220264392A1 · Chen · 2022 [cited by examiner]
US 20220279345A1 · Kim · 2022 [cited by examiner]
US 20220342028A1 · Sun · 2022 [cited by examiner]
US 20220346179A1 · Yang · 2022 [cited by examiner]
CN 104255056A · 2014 [cited by applicant]
CN 107635271A · 2018 [cited by applicant]
CN 110139386A · 2019 [cited by applicant]
CN 110139387A · 2019 [cited by applicant]
EP 3595363A1 · 2020 [cited by applicant]
WO 2018171518A1 · 2018 [cited by applicant]
WO 2019098900A1 · 2019 [cited by applicant]
WO 2019242756A1 · 2019 [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 15),” 3GPP TS 38.401 V15.6.0, total 46 pages, 3rd Generation Partnership Project, Valbon… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15),” 3GPP TS 38.473 V15.7.0, total 221 pages, 3rd Generation Partnership Project,… [cited by applicant]