IP Library Granted Patent US 12,382,533
Granted Patent B2
US 12,382,533 · App. 17/400,832 · Granted Aug 5, 2025

Method for controlling wireless backhaul link and apparatus

Inventors: Yuanping Zhu (Shanghai, CN); Mingzeng Dai (Shenzhen, CN); Jing Liu (Shanghai, CN); Zhenzhen Cao (Beijing, CN); Yibin Zhuo (Shenzhen, CN)
Assignee: Huawei Technologies Co., Ltd.
H04W76/25H04B7/15528H04W72/20H04W92/16
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,382,533
App. No.
17/400,832
Granted
Aug 5, 2025
Kind
B2
Abstract

The present disclosure relates to methods and apparatus for controlling wireless backhaul link. In one example method, a first device determines to manage a first radio link control (RLC) bearer on a wireless backhaul link between a first backhaul node and a second device, where the second device is a parent node of the first backhaul node, the first device is a centralized unit (CU) of a donor base station, and the second device is a distributed unit (DU) of the donor base station; the second device is a second backhaul node, and the first device is a donor base station; or the first device is a CU of a donor base station, and the second device is a second backhaul node. The first device sends a backhaul type indicator and management information of the first RLC bearer to the first backhaul node.

Claims (42)

1. A method, comprising:

determining, by a first device, to manage a first radio link control (RLC) bearer on a wireless backhaul link between a first backhaul node and a second device, wherein the second device is a parent node of the first backhaul node, and wherein:

the first device is a centralized unit (CU) of a donor base station, and the second device is a distributed unit (DU) of the donor base station;

the second device is a second backhaul node, and the first device is the donor base station; or

the first device is the CU, and the second device is the second backhaul node;

sending, by the first device, a backhaul type indicator and management information of the first RLC bearer to the first backhaul node, wherein the backhaul type indicator is used to indicate that a type of the first RLC bearer is a backhaul type, and the management information of the first RLC bearer is used to determine a radio bearer of a terminal mapped to the first RLC bearer or the management information of the first RLC bearer is used to determine an RLC bearer or a logical channel between the first backhaul node and a child node of the first backhaul node mapped to the first RLC bearer;

sending, by the first device, the backhaul type indicator and the management information of the first RLC bearer to the second device; and

in response to sending the backhaul type indicator and the management information of the first RLC bearer to the second device, receiving, by the first device from the second device, an identifier of a logical channel corresponding to the first RLC bearer or identification information of the first RLC bearer.

2. The method according to claim 1 , wherein the first device is the CU, the second device is the DU, and the management information of the first RLC bearer comprises:

description information of a traffic flow that is mapped to the first RLC bearer, wherein the description information comprises any one or more of the following information at an IP layer that is peered to the CU and the DU: differentiated services code point (DSCP) information or a flow label.

3. The method according to claim 1 , wherein determining, by the first device, to manage the RLC bearer on the wireless backhaul link between the first backhaul node and the second device comprises:

when managing the radio bearer of the terminal, determining, by the first device, to manage the first RLC bearer on the wireless backhaul link between the first backhaul node and the second device; or

when the first backhaul node accesses the first device, determining, by the first device, to manage the first RLC bearer on the wireless backhaul link between the first backhaul node and the second device.

4. The method according to claim 3 , wherein there is also a default radio bearer, between the first backhaul node and the second device, used to transmit traffic of the first backhaul node, and wherein the method further comprises:

sending, by the first device to at least one of the first backhaul node or the second device, indication information used to indicate that the first RLC bearer is the default radio bearer.

5. The method according to claim 3 , wherein the second device is the second backhaul node, and wherein the method further comprises:

sending, by the first device to the second device, identification information of a third RLC bearer that is mapped to the first RLC bearer or an identifier of a logical channel corresponding to the third RLC bearer, wherein the third RLC bearer is an RLC bearer on a wireless backhaul link between the second backhaul node and a fourth device, and wherein the fourth device is a parent node of the second device.

6. The method according to claim 1 , wherein the backhaul type indicator and the management information of the first RLC bearer are sent in a same message.

7. The method according to claim 1 , wherein an RLC entity corresponding to the first RLC bearer is associated with an upper-layer Adapt layer entity.

8. The method according to claim 1 , wherein receiving, by the first device from the second device, the identifier of the logical channel corresponding to the first RLC bearer or the identification information of the first RLC bearer comprises:

receiving, by the first device from the second device, the identifier of the logical channel corresponding to the first RLC bearer.

9. A first device, comprising:

at least one processor; and

at least one memory storing instructions for execution by the at least one processor to cause the first device to perform operations comprising:

determining to manage a first radio link control (RLC) bearer on a wireless backhaul link between a first backhaul node and a second device, wherein the second device is a parent node of the first backhaul node, and wherein:

the first device is a centralized unit (CU) of a donor base station, and the second device is a distributed unit (DU) of the donor base station;

the second device is a second backhaul node, and the first device is the donor base station; or

the first device is the CU, and the second device is the second backhaul node;

sending a backhaul type indicator and management information of the first RLC bearer to the first backhaul node, wherein the backhaul type indicator is used to indicate that a type of the first RLC bearer is a backhaul type, and the management information of the first RLC bearer is used to determine a radio bearer of a terminal mapped to the first RLC bearer or the management information of the first RLC bearer is used to determine an RLC bearer or a logical channel between the first backhaul node and a child node of the first backhaul node mapped to the first RLC bearer;

sending the backhaul type indicator and the management information of the first RLC bearer to the second device; and

in response to sending the backhaul type indicator and the management information of the first RLC bearer to the second device, receiving, from the second device, an identifier of a logical channel corresponding to the first RLC bearer or identification information of the first RLC bearer.

10. The first device according to claim 9 , wherein the first device is the CU, the second device is the DU, and the management information of the first RLC bearer comprises:

description information of a traffic flow that is mapped to the first RLC bearer, wherein the description information comprises any one or more of the following information at an IP layer that is peered to the CU and the DU: differentiated services code point (DSCP) information or a flow label.

11. The first device according to claim 9 , wherein determining to manage the RLC bearer on the wireless backhaul link between the first backhaul node and the second device comprises:

when managing the radio bearer of the terminal, determining to manage the first RLC bearer on the wireless backhaul link between the first backhaul node and the second device; or

when the first backhaul node accesses the first device, determining to manage the first RLC bearer on the wireless backhaul link between the first backhaul node and the second device.

12. The first device according to claim 11 , wherein there is also a default radio bearer, between the first backhaul node and the second device, used to transmit traffic of the first backhaul node, and wherein the operations further comprise:

sending, to at least one of the first backhaul node or the second device, indication information used to indicate that the first RLC bearer is the default radio bearer.

13. The first device according to claim 11 , wherein the second device is the second backhaul node, and wherein the operations further comprise:

sending, to the second device, identification information of a third RLC bearer that is mapped to the first RLC bearer or an identifier of a logical channel corresponding to the third RLC bearer, wherein the third RLC bearer is an RLC bearer on a wireless backhaul link between the second backhaul node and a fourth device, and wherein the fourth device is a parent node of the second device.

14. The first device according to claim 9 , wherein receiving, from the second device, the identifier of the logical channel corresponding to the first RLC bearer or the identification information of the first RLC bearer comprises:

receiving, from the second device, the identifier of the logical channel corresponding to the first RLC bearer.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2025
From: ZHU, YUANPING; DAI, MINGZENG; LIU, JING; CAO, ZHENZHEN; ZHUO, YIBIN
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 071154/0951 →
Priority Claims (1)
CN 201910118065.9 · Feb 15, 2019 · national
Continuity (2)
Continuation PCTCN2020074919 · Feb 12, 2020
Related Publication 20210378044A1 · Dec 2, 2021
References Cited (93)
US 8514756B1 · Ramachandra · 2013 [cited by examiner]
US 9930634B1 · Sevindik · 2018 [cited by examiner]
US 10470136B1 · Ghosh · 2019 [cited by examiner]
US 10869353B2 · Byun · 2020 [cited by examiner]
US 12101791B2 · Wu · 2024 [cited by examiner]
US 20060183475A1 · Willey · 2006 [cited by examiner]
US 20100260096A1 · Ulupinar · 2010 [cited by examiner]
US 20110044249A1 · Wu · 2011 [cited by examiner]
US 20140160940A1 · Maehara · 2014 [cited by examiner]
US 20140169299A1 · Wang · 2014 [cited by examiner]
US 20140219248A1 · Reddiboyana · 2014 [cited by examiner]
US 20170064731A1 · Wang et al. · 2017 [cited by applicant]
US 20170347307A1 · Mehta · 2017 [cited by examiner]
US 20180109972A1 · Kim · 2018 [cited by examiner]
US 20180295556A1 · Baek · 2018 [cited by examiner]
US 20180332516A1 · Oak · 2018 [cited by examiner]
US 20180337846A1 · Lee · 2018 [cited by examiner]
US 20180368205A1 · Park · 2018 [cited by examiner]
US 20180376457A1 · Tseng · 2018 [cited by examiner]
US 20190053301A1 · Hampel · 2019 [cited by examiner]
US 20190053317A1 · Hampel · 2019 [cited by examiner]
US 20190159072A1 · Zhu · 2019 [cited by examiner]
US 20190159277A1 · Zhu · 2019 [cited by examiner]
US 20190215055A1 · Majmundar · 2019 [cited by examiner]
US 20190297555A1 · Hampel · 2019 [cited by examiner]
US 20190313433A1 · Abedini · 2019 [cited by examiner]
US 20190349036A1 · Wang · 2019 [cited by examiner]
US 20190349079A1 · Novlan · 2019 [cited by examiner]
US 20190387444A1 · Byun · 2019 [cited by examiner]
US 20200045548A1 · Dowlatkhah · 2020 [cited by examiner]
US 20200267617A1 · Larsen · 2020 [cited by examiner]
US 20200413457A1 · Hong · 2020 [cited by examiner]
US 20210014768A1 · Hong · 2021 [cited by examiner]
US 20210076368A1 · Malkamäki · 2021 [cited by examiner]
US 20210258244A1 · Xu · 2021 [cited by examiner]
US 20210409328A1 · Xu · 2021 [cited by examiner]
US 20220078674A1 · Wu · 2022 [cited by examiner]
US 20220078680A1 · Wu · 2022 [cited by examiner]
CA 3067279A1 · 2018 [cited by examiner]
CN 1846420A · 2006 [cited by examiner]
CN 104685930A · 2015 [cited by applicant]
CN 109257212A · 2019 [cited by applicant]
CN 110351700A · 2019 [cited by examiner]
CN 110351836A · 2019 [cited by examiner]
CN 110475351A · 2019 [cited by examiner]
CN 110475368A · 2019 [cited by examiner]
CN 110536350A · 2019 [cited by examiner]
CN 110636561A · 2019 [cited by examiner]
CN 110636584A · 2019 [cited by examiner]
CN 110636636A · 2019 [cited by examiner]
CN 110649997A · 2020 [cited by examiner]
CN 110662297A · 2020 [cited by examiner]
CN 110971349A · 2020 [cited by examiner]
CN 112567796A · 2021 [cited by examiner]
CN 112740758A · 2021 [cited by examiner]
CN 112997576A · 2021 [cited by examiner]
CN 113455051A · 2021 [cited by examiner]
CN 110636555B · 2022 [cited by examiner]
CN 110351700B · 2022 [cited by examiner]
EP 1581014A1 · 2005 [cited by examiner]
EP 1703678A1 · 2006 [cited by examiner]
EP 2409515B1 · 2015 [cited by applicant]
JP 6680797B2 · 2020 [cited by examiner]
KR 20150090213A · 2015 [cited by examiner]
WO WO2005067325A1 · 2005 [cited by examiner]
WO 2014022769A1 · 2014 [cited by applicant]
WO 2016065645A1 · 2016 [cited by applicant]
WO 2018031170A1 · 2018 [cited by applicant]
WO WO2018080218A1 · 2018 [cited by examiner]
WO WO2018164469A1 · 2018 [cited by examiner]
WO WO2019137285A1 · 2019 [cited by examiner]
WO WO2019139524A1 · 2019 [cited by examiner]
WO WO2019160282A1 · 2019 [cited by examiner]
WO WO2019184482A1 · 2019 [cited by examiner]
WO WO2019192605A1 · 2019 [cited by examiner]
WO WO2019216717A1 · 2019 [cited by examiner]
WO WO2020030109A1 · 2020 [cited by examiner]
WO WO2020057732A1 · 2020 [cited by examiner]
WO WO2020062079A1 · 2020 [cited by examiner]
WO WO2020095459A1 · 2020 [cited by examiner]
WO WO2020108737A1 · 2020 [cited by examiner]
WO WO2020164697A1 · 2020 [cited by examiner]
ZTE. “Discussion on backhaul bearer setup in IAB network.” Nov. 12, 2018, Spokane, USA, R2-1817411. [cited by examiner]
Office Action issued in Indian Application No. 202147037312 on Apr. 21, 2022, 7 pages. [cited by applicant]
ZTE et al., “Discussion on backhaul bearer setup in IAB network,” 3GPP TSG-RAN WG2#104, R2-1817411, Spokane, USA, Nov. 12-16, 2018, 6 pages. [cited by applicant]
ZTE et al., “Discussion on backhaul bearer setup in IAB network,” 3GPP TSG-RAN WG3#102, R3-186419, Spokane, USA, Nov. 12-16, 2018, 6 pages. [cited by applicant]
Office Action in Chinese Application No. 201910118065.9, dated Sep. 2, 2021, 37 pages. [cited by applicant]
PCT International Search Report and Written Opinion in International Application No. PCT/CN2020/074919, dated Apr. 26, 2020, 13 pages. [cited by applicant]
3GPP TS 38.331 V15.4.0 (Dec. 2018), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15),” Dec. 2018, 474 pages. [cited by applicant]
3GPP TS 36.331 V15.4.0 (Dec. 2018), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol sp… [cited by applicant]
3GPP TS 38.473 V15.4.1 (Jan. 2019), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP)(Release 15),” Jan. 2019, 192 pages. [cited by applicant]
3GPP TR 38.874 V16.0.0 (Dec. 2018), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on Integrated Access and Backhaul; (Release 16),” Dec. 2018, 112 pages. [cited by applicant]
Extended European Search Report issued in European Application No. 20755102.9 on Mar. 3, 2022, 7 pages. [cited by applicant]
Cited By (1)
US 12,610,303