IP Library › Granted Patent US 12,732,262
Granted Patent B2
US 12,732,262 · App. 18/553,887 · Granted Sep 8, 2026

Signaling for simultaneous operation in integrated access backhaul (IAB) node

Inventors: Magnus Åström (Lund, SE); Lei Bao (Gothenburg, SE); Behrooz Makki (Pixbo, SE)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04B7/15528H04B7/0697
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,732,262
App. No.
18/553,887
Granted
Sep 8, 2026
Kind
B2
Abstract

Embodiments include methods for an integrated access backhaul (IAB) node serving a cell in a wireless network. The IAB node can include an IAB distributed unit (IAB-DU) and an IAB mobile terminal (IAB-MT). Such methods include sending, to an IAB donor centralized unit (CU) in the wireless network, an indication of one or more simultaneous operation capabilities of the IAB-DU and the IAB-MIT and receiving from the IAB donor CU a multiplexing configuration based on the simultaneous operation capabilities. Such methods also include configuring one or more of the following for operation in the cell according to the received multiplexing configuration: one or more child IAB nodes; and one or more user equipment (UEs). Other embodiments include complementary methods for an IAB donor CU and a parent IAB node of the IAB node, as well as IAB nodes and IAB donor CUs configured to perform such methods.

Claims (79)

1 . A method for an integrated access backhaul (IAB) node configured to operate in a wireless network, the IAB node comprising an IAB distributed unit (IAB-DU) and an IAB mobile terminal (IAB-MT), the method comprising:

receiving the following from an IAB donor centralized unit (CU) in the wireless network:

a first configuration of the IAB-MT for operation in a first cell served by a parent IAB node of the IAB node; and

a second configuration of the IAB-DU for serving a second cell;

sending, to the IAB donor CU, an indication of one or more capability for simultaneous operation of the IAB-DU and the IAB-MT, in accordance with the received first and second configurations;

receiving, from the IAB donor CU, a multiplexing configuration for each timeslot based on the indicated one or more capability; and

configuring one or more of the following for operation in the second cell according to the received multiplexing configuration: one or more child IAB nodes; and one or more user equipment (UEs).

2 . The method of claim 1 , wherein one or more of the following applies:

the first configuration includes an indication of one of the following resource types for each timeslot of the link between the IAB-MT and the parent IAB node: uplink-only, downlink-only, flexible uplink-downlink, and not available; and

the second configuration includes an indication of one of the following frequency-domain resource configurations for the second cell: Hard (H), Soft (S), and Not Available (NA).

3 . The method of claim 2 , wherein the second configuration also includes a time-domain resource configuration for the second cell.

4 . The method of claim 1 , wherein configuring for operation in the second cell is further based on the second configuration.

5 . The method of claim 1 , further comprising transmitting, to the parent IAB node, an indication of the second configuration of the IAB-DU for serving the second cell.

6 . The method of claim 5 , further comprising:

in response to a change in operation conditions related to the second cell or the IAB-MT, sending to the parent IAB node a request to update the multiplexing configuration in accordance with the change in operation conditions;

receiving from the parent IAB node an updated multiplexing configuration or an indication to use a previously received updated multiplexing configuration; and

configuring one or more of the following for operation in the second cell according to the updated multiplexing configuration indicated by the parent IAB node: the one or more child IAB nodes, and the one or more UEs.

7 . The method of claim 6 , wherein:

the updated multiplexing configuration is received from the IAB donor CU together with the multiplexing configuration; and

the indication to use the updated multiplexing configuration is received from the parent IAB node.

8 . The method of claim 6 , further comprising sending one of the following to the IAB donor CU: the updated multiplexing configuration or an indication that the updated multiplexing configuration is being used.

9 . The method of claim 1 , wherein the indicated one or more capability includes any of the following:

time domain multiplexing (TDM) capability;

frequency domain multiplexing (FDM) capability;

spatial domain multiplexing (SDM) capability;

supported timing modes;

supported synchronization procedures;

supported power control dynamic range;

power control configurations supported for simultaneous operation; and

one or more preferred modes for multiplexing between IAB-DU and IAB-MT.

10 . The method of claim 1 , wherein the multiplexing configuration includes indications of one or more of the following for each of a plurality of timeslots:

one or more types of multiplexing between IAB-DU and IAB-MT allowed during the timeslot, including one or more of the following:

IAB-MT Transmission (TX)/IAB-DU TX;

IAB-MT TX/IAB-DU Reception (RX);

IAB-MT RX/IAB-DU TX; and

IAB-MT RX/IAB-DU RX;

one or more types of traffic allowed during the timeslot, including one or more of the following types: access traffic, and backhaul traffic; and

a type of time resource available for the IAB-DU during the timeslot, the type of time resource being one of the following: a downlink time resource, an uplink time resource, and a flexible uplink-downlink time resource.

11 . The method of claim 10 , wherein time domain multiplexing (TDM) or frequency domain multiplexing (FDM) is allowed during each of the timeslots.

12 . The method of claim 11 , wherein for each of the timeslots:

when TDM is indicated as allowed for the timeslot, the multiplexing configuration also includes an indication of one of the following for the timeslot:

the timeslot is always available for the IAB-DU,

the availability of the timeslot for the IAB-DU is controlled by the parent IAB node, or

the timeslot is not available for the IAB-DU; and

when FDM is indicated as allowed for the timeslot, the multiplexing configuration also includes an indication of one of the following for each of a plurality of frequency resources during the timeslot:

the frequency resource is always available during the timeslot for the IAB-DU,

the availability of the frequency resource for the IAB-DU during the timeslot is controlled by the parent IAB node, or

the frequency resource is not available for the IAB-DU during the timeslot.

13 . A non-transitory, computer-readable medium storing computer-executable instructions the execution of which causes the method of claim 1 to be performed by the IAB node.

14 . A method for an integrated access backhaul (IAB) donor centralized unit (CU) configured to operate in a wireless network, the method comprising:

sending the following to an IAB node that comprises an IAB distributed unit (IAB-DU) and an IAB mobile terminal (IAB-MT):

a first configuration of the IAB-MT for operation in a first cell served by a parent IAB node of the IAB node; and

a second configuration of the IAB-DU for serving a second cell;

receiving, from the IAB node, an indication of one or more capability for simultaneous operation of the IAB-DU and the IAB-MT, in accordance with the first and second configurations;

determining a multiplexing configuration for each timeslot for the IAB node based on the indicated one or more capability; and

sending the multiplexing configuration to the IAB node.

15 . The method of claim 14 , further comprising receiving one of the following from the IAB node: an updated multiplexing configuration being used by the IAB node, or an indication that a previously received updated multiplexing configuration is being used by the IAB node.

16 . The method of claim 15 , wherein the indication is received from the IAB node and pertains to an updated multiplexing configuration sent to the IAB node together with the multiplexing configuration.

17 . The method of claim 14 , wherein determining the multiplexing configuration for the IAB node is further based on one or more of the following:

radio resource management (RRM) or radio link monitoring (RLM) configurations associated with one or more of the following: the IAB node, the parent IAB node, and one or more child IAB nodes of the IAB node; and

RRM or RLM measurements received from one or more of the following: the IAB node, the parent IAB node, and the one or more child IAB nodes.

18 . The method of claim 14 , further comprising sending the multiplexing configuration to the parent IAB node.

19 . A non-transitory, computer-readable medium storing computer-executable instructions, the execution of which causes the method of claim 14 to be performed by the IAB donor CU.

20 . An integrated access backhaul (IAB) node configured to operate in a wireless network, the IAB node comprising:

processing circuitry and communication interface circuitry configured as an IAB mobile terminal (IAB-MT) and an IAB distributed unit (IAB-DU), wherein the processing circuitry and the communication interface circuitry are further configured to:

receive the following from an IAB donor centralized unit (CU) in the wireless network:

a first configuration of the IAB-MT for operation in a first cell served by a parent IAB node of the IAB node; and

a second configuration of the IAB-DU for serving a second cell;

send, to the IAB donor CU, an indication of one or more capability for simultaneous operation of the IAB-DU and the IAB-MT, in accordance with the received first and second configurations;

receive, from the IAB donor CU, a multiplexing configuration for each timeslot based on the indicated one or more capability; and

configure one or more of the following for operation in the second cell according to the received multiplexing configuration: one or more child IAB nodes; and one or more user equipment (UEs).

21 . An integrated access backhaul (IAB) donor centralized unit (CU) configured to operate in a wireless network, the IAB donor CU comprising communication interface circuitry and processing circuitry that are operably coupled and are configured to:

send the following to an IAB node that comprises an IAB distributed unit (IAB-DU) and an IAB mobile terminal (IAB-MT):

a first configuration of the IAB-MT for operation in a first cell served by a parent IAB node of the IAB node; and

a second configuration of the IAB-DU for serving a second cell;

receive, from the IAB node, an indication of one or more capability for simultaneous operation of the IAB-DU and the IAB-MT, in accordance with the first and second configurations;

determine a multiplexing configuration for each timeslot for the IAB node based on the indicated one or more capability; and

send the multiplexing configuration to the IAB node.

22 . The IAB donor CU of claim 21 , wherein the processing circuitry and the communication interface circuitry are further configured to receive one of the following from the IAB node: an updated multiplexing configuration being used by the IAB node, or an indication that a previously received updated multiplexing configuration is being used by the IAB node.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 5, 2023
From: ÅSTRÖM, MAGNUS; BAO, LEI; MAKKI, BEHROOZ
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 065131/0825 →
Continuity (2)
Provisional Application 63171486 · Apr 6, 2021
Related Publication 20240259084A1 · Aug 1, 2024
References Cited (68)
US 11082979B2 · Seo et al. · 2021 [cited by applicant]
US 11303349B2 · Jo · 2022 [cited by examiner]
US 12267813B2 · Zhang · 2025 [cited by examiner]
US 20200336890A1 · Abedini · 2020 [cited by examiner]
US 20210100012A1 · Miao · 2021 [cited by applicant]
US 20210168852A1 · Panteleev et al. · 2021 [cited by applicant]
US 20210243782A1 · Miao · 2021 [cited by applicant]
US 20210289421A1 · Akl et al. · 2021 [cited by applicant]
US 20210368360A1 · Akl et al. · 2021 [cited by applicant]
US 20210368481A1 · Jo · 2021 [cited by examiner]
US 20220217661A1 · Yokomakura · 2022 [cited by examiner]
US 20220287123A1 · Tiirola et al. · 2022 [cited by applicant]
US 20220361174A1 · Liu · 2022 [cited by examiner]
US 20230108413A1 · You et al. · 2023 [cited by applicant]
US 20230117298A1 · Park et al. · 2023 [cited by applicant]
US 20230164747A1 · You · 2023 [cited by examiner]
US 20230164793A1 · Ghanbarinejad · 2023 [cited by examiner]
US 20230345553A1 · Maya et al. · 2023 [cited by applicant]
US 20230412250A1 · Huang · 2023 [cited by examiner]
CN 110278610B · 2022 [cited by applicant]
EP 4096326A1 · 2022 [cited by applicant]
EP 4117387A1 · 2023 [cited by applicant]
WO 2017014572A1 · 2017 [cited by applicant]
WO 2018143702A1 · 2018 [cited by applicant]
WO 2020010613A1 · 2020 [cited by applicant]
WO 2020032578A1 · 2020 [cited by applicant]
WO 2020145358A1 · 2020 [cited by applicant]
WO 2020239042A1 · 2020 [cited by applicant]
WO 2021028785A1 · 2021 [cited by applicant]
WO 2021178788A1 · 2021 [cited by applicant]
WO 2021205343A1 · 2021 [cited by applicant]
WO 2022084301A1 · 2022 [cited by applicant]
WO 2022214528A1 · 2022 [cited by applicant]
CEWIT: “Discussions on enhancements to resource multiplexing between child and parent links of an IAB node”, 3GPP Draft; R1-2006329, vol. RAN WG1, No. e-Meeting; Aug. 17, 2020-Aug. 28, 2020 (Aug. 8, 2020). [cited by examiner]
“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 38.331 V16.4.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16), Mar. 2021, pp. 1-949. [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]
“Discussions on enhancements to resource multiplexing between child and parent links of an IAB node”, 3GPP TSG RAN WG 1 Meeting #102-e, R1-2006329, e-Meeting, Aug. 17-28, 2020, pp. 1-7. [cited by applicant]
“New WID on Enhancements to Integrated Access and Backhaul”, 3GPP TSG RAN Meeting #88e, RP-201293, Electronic Meeting, (revision of RP-193251), Jun. 29-Jul. 3, 2020, pp. 1-5. [cited by applicant]
“Resource multiplexing and DC in enhanced IAB”, 3GPP TSG-RAN WG1 Meeting #104-bis-e, R1-2103712, eMeeting, Apr. 12-20, 2021, pp. 1-15. [cited by applicant]
“Resource multiplexing and DC in enhanced IAB”, 3GPP TSG-RAN WG1 Meeting #104-e, R1-2101695, eMeeting, Jan. 25-Feb. 5, 2021, pp. 1-14. [cited by applicant]
“Resource multiplexing and DC in enhanced IAB”, 3GPP TSG-RAN WGI Meeting #105-e; Online, R1-2105852, May 10-27, 2021, pp. 1-17. [cited by applicant]
“Resource multiplexing and dual connectivity in enhanced IAB”, 3GPP TSG-RAN WG1 Meeting #106-e, R1-2108107, Online, Aug. 16-27, 2021, pp. 1-20. [cited by applicant]
“Resource multiplexing and dual connectivity in enhanced IAB”, 3GPP TSG-RAN WG1 Meeting #106bis-e, R1-2110331, Online, Oct. 11-19, 2021, pp. 1-20. [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 TS 38.473 V16.4.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 16), Jan. 2021, pp. 1-461. [cited by applicant]
“3GPP TS 38.213 V16.5.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 16), Mar. 2021, pp. 1-183. [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), 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]
“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]
“3GPP TS 38.321 V15.2.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15), Jun. 2018, pp. 1-73. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on Integrated Access and Backhaul; (Release 16)”, 3GPP TR 38.874 V16.0.0, Dec. 2018, pp. 1-111. [cited by applicant]
“CB:# 45_Email045-IAB_PHYlayer_param_F1 Ap”, 3GPP TSG-RAN WG3 Meeting #107-e, R3-201144, Electronic Meeting, Feb. 24-Mar. 6, 2020, pp. 1-6. [cited by applicant]
“Corrections on integrated access and backhaul”, 3GPP TSG-RAN WG1 Meeting #100-e, R1-2001452, e-Meeting, Feb. 24-Mar. 6, 2020, pp. 1-5. [cited by applicant]
“Discussion on IAB resource multiplexing enhancements”, 3GPP TSG RAN WG1 Meeting #102-e, R1-2006361, e-Meeting, Aug. 17-28, 2020, pp. 1-8. [cited by applicant]
“Enhancement to resource multiplexing between child and parent links”, 3GPP TSG RAN WG1 #104b-e, R1-2102538, e-Meeting, Apr. 12-20, 2021, pp. 1-8. [cited by applicant]
“IAB Resource Management Framework”, 3GPP TSG RAN WG1 Meeting #96, R1-1902992, Athens, Greece, Feb. 25-Mar. 1, 2019, pp. 1-8. [cited by applicant]
“Mechanisms for resource coordination and radio-aware scheduling for IAB”, 3GPP TSG RAN WG1 #96, R1-1901894, Athens, Greece, Feb. 25-Mar. 1, 2019, pp. 1-6. [cited by applicant]
“Mechanisms for resource multiplexing among backhaul and access links”, 3GPP TSG RAN WG1 Meeting #98, R1-1908987, Prague, Czech Republic, Aug. 26-30, 2019, pp. 1-20. [cited by applicant]
“Remaining issues on IAB resource configuration and multiplexing”, 3GPP TSG-RAN WG1 Meeting #99, R1-1912133, Reno, U.S., Nov. 18-22, 2019, pp. 1-5. [cited by applicant]
“Summary #2 of 7.2.3.3—Mechanisms for resource multiplexing among backhaul and access links”, 3GPP TSG-RAN WG1 Meeting #100-e, R1-2001160, e-Meeting, Feb. 24-Mar. 6, 2020, pp. 1-19. [cited by applicant]
“3GPP Ts 38.473 V15.4.0”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15), Dec. 2018, pp. 1-192. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 16)”, 3GPP TS 38.473 V16.6.0, Jul. 2021, pp. 1-463. [cited by applicant]
Qualcomm, “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]