IP Library › Granted Patent US 12,628,049
Granted Patent B2
US 12,628,049 · App. 17/773,122 · Granted May 12, 2026

Method for coordination of control plane traffic management during device reconfigurations and related apparatus

Inventors: Angelo Centonza (Torrenueva Costa, ES); Thomas Walldeen (Linköping, SE); Fredrik Hultin (Vikingstad, SE); Ioanna Pappa (Stockholm, SE)
Assignee: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
H04W36/0033H04L1/1642H04W36/087H04W76/19H04W36/0011H04W92/24
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,628,049
App. No.
17/773,122
Granted
May 12, 2026
Kind
B2
Abstract

The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes for control plane traffic management. Among other things, the disclosure presents a method performed by a central unit (CU) of a network node for coordination of control plane traffic management during a communication device reconfiguration in a telecommunications network. The method may, e.g., comprise receiving information from a distributed unit (DU) of the network node alerting the CU to reset a packet data convergence protocol (PDCP) sequence number of control plane traffic signaled from the communication device as a consequence of an event in the telecommunications network; and responsive to receiving the information, resetting the PDCP sequence number of the control plane traffic signaled from the communication device.

Claims (36)

1 . A method performed by a central unit (“CU”) of a source network node for coordination of control plane traffic management during a communication device reconfiguration in a telecommunications network, the method comprising:

receiving information from a distributed unit (“DU”) of the source network node alerting the CU to reset a packet data convergence protocol (“PDCP”) sequence number of control plane traffic signaled from the communication device as a consequence of an event in the telecommunications network; and

responsive to receiving the information, resetting the PDCP sequence number of the control plane traffic signaled from the communication device,

wherein receiving the information comprises receiving from the DU an uplink message from a target cell and an indicator that the uplink message is a first message sent from the target cell.

2 . The method of claim 1 , wherein the uplink message comprises a radio resource control (“RRC”) message from the target cell.

3 . The method of claim 1 , wherein the indicator comprises a flag indicating that the uplink message is the first message sent from the target cell.

4 . The method of claim 3 , wherein the flag comprises a re-established signaling radio bearer (“SRB”) flag indicating that the RRC message is the first message on a re-established SRB flow.

5 . The method of claim 1 , wherein the uplink message is received from the DU over an F1 interface.

6 . The method of claim 1 , wherein the uplink message comprises an uplink RRC message transfer message.

7 . The method of claim 1 , further comprising:

receiving from the DU an other message comprising an indication that the DU supports sending one or more messages that include the indicator; and

responsive to receiving the other message, waiting to reset the PDCP sequence number of the control plane traffic signaled from the UE until the CU receives the uplink message including the indicator.

8 . A source network node in a telecommunications network, the source network node configured to provide a central unit (“CU”), the source network node comprising:

processing circuitry; and

memory coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the CU to perform operations comprising:

receiving information from a distributed unit (“DU”) of the source network node alerting the CU to reset a packet data convergence protocol (“PDCP”) sequence number of control plane traffic signaled from the communication device as a consequence of an event in the telecommunications network; and

responsive to receiving the information, resetting the PDCP sequence number of the control plane traffic signaled from the communication device,

wherein receiving the information comprises receiving from the DU an uplink message from a target cell and an indicator that the uplink message is a first message sent from the target cell.

9 . The source network node of claim 8 , wherein the uplink message comprises a radio resource control (“RRC”) message from the target cell.

10 . The source network node of claim 8 , wherein the indicator comprises a flag indicating that the uplink message is the first message sent from the target cell.

11 . The source network node of claim 10 , wherein the flag comprises a re-established signaling radio bearer (“SRB”) flag indicating that the RRC message is the first message on a re-established SRB flow.

12 . A method performed by a distributed unit (“DU”) of a source network node for coordination of control plane traffic management during a communication device reconfiguration in a telecommunications network, the method comprising:

signaling a message to a central unit (“CU”) of the source network node comprising an indicator of timing of a packet data convergence protocol (“PDCP”) sequence number for control plane traffic signaled from the communication device for an event in the telecommunications network,

wherein signaling the message to the CU comprises signaling an uplink message from a target cell and the indicator that the uplink message is a first message sent from the target cell.

13 . The method of claim 12 , wherein the uplink message comprises a radio resource control (“RRC”) message from the target cell.

14 . The method of claim 12 , wherein the indicator comprises a flag indicating that the uplink message is the first message sent from the target cell.

15 . The method of claim 14 , wherein the flag comprises a re-established signaling radio bearer (“SRB”) flag indicating that the RRC message is the first message on a re-established SRB flow.

16 . The method of claim 12 , wherein the message is signaled by the DU to the CU over an F1 interface.

17 . The method of claim 12 , wherein the message comprises an uplink RRC message transfer message.

18 . A source network node of a telecommunications network, the source network node configured to provide a distributed unit (“DU”), the source network node comprising:

processing circuitry; and

memory coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the DU to perform operations comprising:

signaling a message to a central unit (“CU”) of the source network node comprising an indicator of timing of a packet data convergence protocol (“PDCP”) sequence number for control plane traffic signaled from the communication device for an event in the telecommunications network,

wherein signaling the message to the CU comprises signaling an uplink message from a target cell and the indicator that the uplink message is a first message sent from the target cell.

19 . The source network node of claim 18 , wherein the indicator comprises a flag indicating that the uplink message is the first message sent from the target cell.

20 . The DU source network node of claim 19 , wherein the flag comprises a re-established signaling radio bearer (“SRB”) flag indicating that the RRC message is the first message on a re-established RB flow.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 29, 2022
From: CENTONZA, ANGELO; WALLDEEN, THOMAS; HULTIN, FREDRIK; PAPPA, IOANNA
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 059774/0177 →
Continuity (2)
Provisional Application 62933335 · Nov 8, 2019
Related Publication 20220369174A1 · Nov 17, 2022
References Cited (24)
US 11533775B2 · Liu · 2022 [cited by examiner]
US 20160183221A1 · Yi · 2016 [cited by examiner]
US 20200068639A1 · Kim · 2020 [cited by examiner]
US 20200154333A1 · Paladugu · 2020 [cited by examiner]
WO 2018203702A1 · 2018 [cited by applicant]
Extended European Search Report for European Patent Application No. 20884515.6 dated Dec. 6, 2022. [cited by applicant]
Ericsson, “Intra-gNB-CU mobility procedures,” R3-173967, 3GPP TSG-RAN WG3 #97bis, Prague, Sep. 2017, 6 pages. [cited by applicant]
Huawei, “Support of eMBB handover on E1,” R3-195571, 3GPP TSG-RAN3 Meeting #105bis, Chongqing, China, Oct. 14-18, 2019, 3 pages. [cited by applicant]
Ericsson, “Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity,” R3-195326, 3GPP TSG-RAN WG3 Meeting #105bis, Chongqing, P.R. China, Oct. 14-18, 2019, 25 pages. [cited by applicant]
He Huang et al., “Mechanism of Fast Data Retransmission in CU-DU Split Architecture of 5G NR,” Research Paper, ZTE Communications, vol. 16, No. 3, Sep. 2018, pp. 40-44. [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority for PCT International Application No. PCT/SE2020/051042 dated Feb. 22, 2021. [cited by applicant]
CATT, “Correction on intra-DU handover,” R3-181072, 3GPP TSG-RAN WG3#99, Athens, Greece, Feb. 26-Mar. 2, 2018, 3 pages. [cited by applicant]
Intel Corporation, “Correction for correct DDDS for retransmitted packets, ” R3-186937, 3GPP TSG-RAN WG3 Meeting #102, Spokane, Washington, USA, Nov. 12-16, 2018, 6 pages. [cited by applicant]
Ericsson, “Considerations regarding intra-DU HO,” R3-197347, 3GPP TSG-RAN3 Meeting #106, Reno, Nevada, USA, Nov. 18-22, 2019, 2 pages. [cited by applicant]
Ericsson, “Considerations regarding intra-DU HO,” R3-200930, 3GPP TSG-RAN3 #107e, Feb. 24-Mar. 6, 2020, 3 pages. [cited by applicant]
3GPP TS 38.401 V15.6.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 15),” Jul. 2019, 46 pages. [cited by applicant]
3GPP TS 38.423 V15.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 15),” Sep. 2019, 311 pages. [cited by applicant]
3GPP TS 38.470 V15.6.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 general aspects and principles (Release 15),” Jul. 2019, 13 pages. [cited by applicant]
3GPP TS 38.473 V15.7.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15),” Sep. 2019, 221 pages. [cited by applicant]
3GPP TS 23.501 V15.6.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15),” Jun. 2019, 243 pages. [cited by applicant]
3GPP TS 36.300 V15.7.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network… [cited by applicant]
3GPP TS 36.413 V15.7.1, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 15),… [cited by applicant]
3GPP TS 36.423 V15.7.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 15),… [cited by applicant]
3GPP TS 38.331 V15.7.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15),” Sep. 2019, 527 pages. [cited by applicant]