IP Library Granted Patent US 12,317,147
Granted Patent B2
US 12,317,147 · App. 18/011,761 · Granted May 27, 2025

Handling of buffered traffic during inter-CU migration of an integrated access backhaul (IAB) node

Inventors: Oumer Teyeb (Montréal, CA); Filip Barac (Huddinge, SE); Marco Belleschi (Solna, SE)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04W36/08H04W36/0235
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,317,147
App. No.
18/011,761
Granted
May 27, 2025
Kind
B2
Abstract

Embodiments include methods for an integrated access backhaul (IAB) node in a wireless network to migrate from a first centralized unit (CU) to a second CU. Such methods include receiving a handover command from the first CU via a source parent IAB node. The handover command includes an identifier of a target cell for the handover. Such methods include determining that the handover command is for an inter-CU migration of the IAB node to the second CU and, based on determining that the handover command is for an inter-CU migration, performing modified handling of uplink and/or downlink data buffered at the IAB node until execution of the handover command. Embodiments also include complementary methods for handling migration of a child IAB node from a first CU to a second CU, as well as IAB nodes configured to perform such methods.

Claims (100)

1. A method for an integrated access backhaul (IAB) node in a wireless network to migrate from a first centralized unit (CU) to a second CU, the method comprising:

receiving instructions for modified handling of uplink (UL) and/or downlink (DL) data buffered at the IAB node, wherein the instructions for modified handling of buffered UL data and/or buffered DL data include one or more of the following:

one or more first criteria related to amounts of DL data buffered at the IAB node;

one or more second criteria related to whether DL data buffered at the IAB node should be deleted or forwarded to respective descendant nodes;

one or more third criteria related to amounts of UL data buffered at the IAB node; and

one or more fourth criteria related to whether buffer status reports (BSRs) should be transmitted, to a parent node, for UL data buffered at the IAB node;

receiving a handover (HO) command from the first CU via a source parent IAB node, wherein the HO command includes an identifier of a target cell for the handover;

determining that the HO command is for an inter-CU migration of the IAB node to the second CU; and

based on determining that the HO command is for an inter-CU migration, performing modified handling of the UL and/or DL data buffered at the IAB node until execution of the HO command, in accordance with the instructions.

2. The method of claim 1 , wherein performing the modified handling of UL and/or DL data buffered at the IAB node includes one or more of the following:

forwarding at least a portion of the DL data buffered at the IAB node,

forwarding at least a portion of the UL data buffered at the IAB node,

deleting at least a portion of the DL data buffered at the IAB node, and

deleting at least a portion of the UL data buffered at the IAB node.

3. The method of claim 1 , wherein determining that the HO command is for an inter-CU migration is based on one or more of the following:

the target cell identifier does not match any identifiers associated with current serving cells for the IAB node;

a target base station identifier, within the target cell identifier, does not match a base station identifier associated with the first CU; and

an explicit indication, within the HO command, that the HO is an inter-CU migration.

4. The method of claim 1 , further comprising determining that one or more descendant nodes of the IAB node are also subject to an inter-CU migration to the second CU.

5. The method of claim 4 , wherein determining that the one or more descendant nodes are also subject to the inter-CU migration is based on one or more of the following:

determining that the HO command is for an inter-CU migration of the IAB node to the second CU;

an explicit indication, within the HO command, that the one or more descendant nodes are also subject to the inter-CU migration; and

a second HO command for a child node of the IAB node, sent from the first CU to the child node via the IAB node.

6. The method of claim 1 , wherein the second criteria include one or more of the following:

an indicator that all types of buffered DL data should be deleted or forwarded;

list of backhaul radio link control (BH RLC) channels whose buffered DL data should be forwarded;

list of BH RLC channels whose buffered DL data should be deleted;

list of access RLC channels whose buffered DL data should be forwarded;

list of access RLC channels whose buffered DL data should be deleted;

list of QoS profiles and/or priorities for which buffered DL data should be forwarded;

list of QoS profiles and/or priorities for which buffered DL data should be deleted;

list of backhaul adaptation protocol (BAP) routing identifiers for which buffered DL data should be forwarded; and

list of BAP routing identifiers for which buffered DL data should be deleted.

7. The method of claim 1 , wherein each of the first and third criteria identify amounts according to one or more of the following: all buffered data; an explicit amount of buffered data; a percentage of buffered data; and a duration.

8. The method of claim 1 , wherein the fourth criteria include one or more of the following:

an indicator that BSRs should be transmitted for all types of buffered UL data;

list of backhaul radio link control (BH RLC) channels for which BSRs should be transmitted;

list of access RLC channels for which BSRs should be transmitted;

list of QoS profiles and/or priorities for which BSRs should be transmitted; and

list of backhaul adaptation protocol (BAP) routing identifiers for which BSRs should be transmitted.

9. The method of claim 1 , wherein:

the instructions for modified handling of buffered UL and/or buffered DL data include instructions for modified handling of UL data buffered at one or more descendant nodes of the IAB node; and

the method further comprises, based on determining that the HO command is for an inter-CU migration, performing modified handling of UL data buffered at the one or more descendant nodes, according to the instructions and until execution of the HO command.

10. The method of claim 9 , wherein performing the modified handling of UL data buffered at the one of more downstream nodes includes one or more of the following:

providing UL grants for at least a portion of the UL data buffered at one or more child nodes of the IAB node;

refraining from providing UL grants for at least a portion of the UL data buffered at the one or more child nodes; and

providing, to the one or more child nodes, instructions for handling UL data buffered at descendant nodes of the one or more child nodes.

11. The method of claim 9 , wherein the instructions for modified handling of UL data buffered at the one or more descendant nodes include one or more of the following:

a first configuration for handling UL data buffered at a first child node of the IAB node;

a second configuration for handling UL data buffered at a second child node of the IAB node; and

a third configuration for handling UL data buffered at both the first and second child nodes.

12. The method of claim 9 , wherein instructions for modified handling of UL data buffered at one or more descendant nodes include:

one or more fifth criteria related to amounts of UL data buffered at one or more descendant nodes; and

one or more sixth criteria related to whether UL grants should be provided for UL data buffered at the one or more descendant nodes.

13. The method of claim 12 , wherein the sixth criteria include one or more of the following:

an indicator that UL grants should be provided for all buffered UL data;

list of backhaul radio link control (BH RLC) channels for which UL grants should be provided;

list of access RLC channels for which UL grants should be provided;

list of QoS profiles and/or priorities for which UL grants should be provided; and

list of backhaul adaptation protocol (BAP) routing identifiers for which UL grants should be provided.

14. An integrated access backhaul (IAB) node, configured to migrate from a first centralized unit (CU) to a second CU in a wireless network, the IAB node comprising:

radio interface circuitry and processing circuitry configured as a mobile terminal and a distributed unit, wherein the processing circuitry and radio interface circuitry are further configured to:

receive instructions for modified handling of uplink (UL) and/or downlink (DL) data buffered at the IAB node, wherein the instructions for modified handling of buffered UL data and/or buffered DL data include one or more of the following:

one or more first criteria related to amounts of DL data buffered at the IAB node;

one or more second criteria related to whether DL data buffered at the IAB node should be deleted or forwarded to respective descendant nodes;

one or more third criteria related to amounts of UL data buffered at the IAB node; and

one or more fourth criteria related to whether buffer status reports (BSRs) should be transmitted, to a parent node, for UL data buffered at the IAB node;

receive a handover (HO) command from the first CU via a source parent IAB node, wherein the HO command includes an identifier of a target cell for the handover;

determine that the HO command is for an inter-CU migration of the IAB node to the second CU; and

based on determining that the HO command is for an inter-CU migration, perform modified handling of the UL and/or DL data buffered at the IAB node until execution of the HO command, in accordance with the instructions.

15. The IAB node of claim 14 , wherein the processing circuitry and radio interface circuitry are configured to perform the modified handling of UL and/or DL data buffered at the IAB node based on one or more of the following:

forwarding at least a portion of the DL data buffered at the IAB node,

forwarding at least a portion of the UL data buffered at the IAB node,

deleting at least a portion of the DL data buffered at the IAB node, and

deleting at least a portion of the UL data buffered at the IAB node.

16. The IAB node of claim 14 , wherein the processing circuitry and radio interface circuitry are configured to determine that the HO command is for an inter-CU migration based on one or more of the following:

the target cell identifier does not match any identifiers associated with current serving cells for the IAB node;

a target base station identifier, within the target cell identifier, does not match a base station identifier associated with the first CU; and

an explicit indication, within the HO command, that the HO is an inter-CU migration.

17. The IAB node of claim 14 , wherein the processing circuitry and radio interface circuitry are further configured to determine that one or more descendant nodes of the IAB node are also subject to an inter-CU migration to the second CU, based on one or more of the following:

determining that the HO command is for an inter-CU migration of the IAB node to the second CU;

an explicit indication, within the HO command, that the one or more descendant nodes are also subject to the inter-CU migration; and

a second HO command for a child node of the IAB node, sent from the first CU to the child node via the IAB node.

18. The IAB node of claim 14 , wherein the second criteria include one or more of the following:

an indicator that all types of buffered DL data should be deleted or forwarded;

list of backhaul radio link control (BH RLC) channels whose buffered DL data should be forwarded;

list of BH RLC channels whose buffered DL data should be deleted;

list of access RLC channels whose buffered DL data should be forwarded;

list of access RLC channels whose buffered DL data should be deleted;

list of QoS profiles and/or priorities for which buffered DL data should be forwarded;

list of QoS profiles and/or priorities for which buffered DL data should be deleted;

list of backhaul adaptation protocol (BAP) routing identifiers for which buffered DL data should be forwarded; and

list of BAP routing identifiers for which buffered DL data should be deleted.

19. The IAB node of claim 14 , wherein each of the first and third criteria identify amounts according to one or more of the following: all buffered data; an explicit amount of buffered data; a percentage of buffered data; and a duration.

20. The IAB node of claim 14 , wherein the fourth criteria include one or more of the following:

an indicator that BSRs should be transmitted for all types of buffered UL data;

list of backhaul radio link control (BH RLC) channels for which BSRs should be transmitted;

list of access RLC channels for which BSRs should be transmitted;

list of QoS profiles and/or priorities for which BSRs should be transmitted; and

list of backhaul adaptation protocol (BAP) routing identifiers for which BSRs should be transmitted.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 20, 2022
From: TEYEB, OUMER; BARAC, FILIP; BELLESCHI, MARCO
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 062162/0208 →
Continuity (2)
Provisional Application 63055977 · Jul 24, 2020
Related Publication 20230232294A1 · Jul 20, 2023
References Cited (32)
US 20210051558A1 · Abedini · 2021 [cited by examiner]
US 20220312287A1 · Koskinen · 2022 [cited by examiner]
EP 3806542A1 · 2021 [cited by applicant]
WO 2019242683A1 · 2019 [cited by applicant]
WO 2019246446A1 · 2019 [cited by applicant]
“3GPP TS 29.281 V15.6.0”, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U) (Release 15), Sep. 2019… [cited by applicant]
“3GPP TS 36.300 V16.2.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Networ… [cited by applicant]
“3GPP TS 36.321 V16.0.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (… [cited by applicant]
“3GPP TS 36.331 V16.2.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification… [cited by applicant]
“3GPP TS 36.423 V16.2.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 16)… [cited by applicant]
“3GPP TS 38.321 V16.6.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 16), Sep. 2021, pp. 1-158. [cited by applicant]
“3GPP TS 38.331 V16.2.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16), Sep. 2020, pp. 1-921. [cited by applicant]
“3GPP TS 38.340 V16.2.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Backhaul Adaptation Protocol (BAP) specification (Release 16), Sep. 2020, pp. 1-22. [cited by applicant]
“3GPP TS 38.401 V16.2.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description (Release 16), Jul. 2020, pp. 1-77. [cited by applicant]
“3GPP TS 38.423 V16.2.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 16), Jul. 2020, pp. 1-447. [cited by applicant]
“3GPP TS 38.425 V15.6.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NR user plane protocol (Release 15), Jul. 2019, pp. 1-22. [cited by applicant]
“3GPP TS 38.463 V15.4.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; E1 Application Protocol (E1AP) (Release 15), Jul. 2019, pp. 1-177. [cited by applicant]
“3GPP TS 38.473 V16.2.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 16), Jul. 2020, pp. 1-363. [cited by applicant]
“3GPP TR 38.874 V16.0.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on Integrated Access and Backhaul; (Release 16), Dec. 2018, pp. 1-111. [cited by applicant]
“Enhancements to IAB for NR—overview of Rel-17 WI”, 3GPP TSG-RAN WG1 Meeting #102-e, R1-2006905, e-Meeting, Aug. 17-28, 2020, pp. 1-5. [cited by applicant]
“ETSI TS 138 300 V16.2.0”, 5G; NR; NR and NG-RAN Overall description; Stage-2 (3GPP TS 38.300 version 16.2.0 Release 16), Jul. 2020, pp. 1-150. [cited by applicant]
“3GPP TS 38.322 V15.4.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Link Control (RLC) protocol specification (Release 15), Dec. 2018, pp. 1-33. [cited by applicant]
“3GPP TS 37.340 V16.1.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 16), Mar… [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, pp. 1-46. [cited by applicant]
“3GPP TS 38.473 V15.6.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15), Jul. 2019, pp. 1-220. [cited by applicant]
“3GPP TR 38.806 V15.0.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study of separation of NR Control Plane (CP) and User Plane (UP) for split option 2; (Release 15), Dec. 2… [cited by applicant]
“3GPP TR 38.874 V0.2.1”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Integrated Access and Backhaul; (Release 15) The present, , May 2018, pp. 1-19. [cited by applicant]
“3GPP TR 38.801 V14.0.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on new radio access technology: Radio access architecture and interfaces (Release 14), Mar. 2017, p… [cited by applicant]
“3GPP TS 33.401 V15.8.0”, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture (Release 15), Jun. 2019, pp. 1-163. [cited by applicant]
“New WID on Enhancements to Integrated Access and Backhaul”, 3GPP TSG RAN Meeting #86, RP-193251, (revision of RP-193145), Sitges, Spain, Dec. 9-12, 2019, pp. 1-5. [cited by applicant]
“3GPP TS 23.501 V15.5.0”, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15), Mar. 2019, pp. 1-241. [cited by applicant]
“Discussion on network-controlled IAB migration handling”, 3GPP TSG RAN WG3 Meeting #104, R3-192519, Reno, USA, May 13-17, 2019, pp. 1-5. [cited by applicant]