IAB Multi-Parent Resource Coordination Across Donor Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless communication systems in Integrated Access and Backhaul (IAB) networks face challenges in coordinating resource configurations between parent nodes controlled by different donor nodes, leading to potential resource conflicts and inefficiencies in inter-donor dual-connectivity scenarios.

Innovation Solution

A method is provided for resource coordination between parent nodes connected to different IAB donor nodes, involving information exchange and coordination between reference and peer network functions to determine and manage resource configurations, ensuring compatibility and avoiding conflicts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If IAB-nodes are connected to multiple parent nodes under different donor control, then network robustness and load balancing are improved, but resource conflicts and coordination complexity increase

Engineering Contradiction:
Improvenetwork robustnessVSAvoidresource coordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a resource coordination mechanism where donor nodes act as intermediaries to exchange resource configuration information. The reference donor node receives resource configuration requests from peer donor nodes, determines compatible resource configurations, and provides coordinated configurations to avoid conflicts while enabling multi-parent connectivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary resource configuration determination before actual data transmission. The reference donor node determines resource configurations in advance by receiving requests from peer donor nodes and pre-establishing compatible time-domain resource allocations, preventing conflicts before they occur.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If resource configurations are independently managed by different donor nodes, then operational autonomy is maintained, but resource conflicts occur

Engineering Contradiction:
Improvedonor node autonomyVSAvoidresource configuration compatibility
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent establishes a feedback mechanism where peer donor nodes send resource configuration requests to the reference donor node. The reference donor node processes these requests and provides feedback with determined resource configurations, ensuring compatibility while maintaining the operational autonomy of individual donor nodes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent segments the resource coordination function by designating one donor node as the reference donor node that manages F1-AP connections to IAB-DUs, while allowing other donor nodes to independently manage their own resources. This segmentation enables autonomous operation with coordinated resource allocation through standardized request-response protocols.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12490283B2Methods and nodes for IAB inter-donor multi-parent resource coordination
Publication Date: 2025.12.02 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US12490283B2 patent drawing
  • US12490283B2 patent drawing
  • US12490283B2 patent drawing

AI summary

There is provided a method for resource coordination in a first donor Integrated Access Backhaul (IAB) node connected to a first parent IAB node which is connected to an IAB node, the IAB node further being connected to a second parent IAB node which is connected to a second donor IAB node. The method comprises: sending, to the second donor IAB node, an indication of a first resource configuration for the IAB node, the first resource configuration determined by the first donor IAB node; receiving, from the second donor IAB node, a request for a second resource configuration for the IAB node; and determining a resource configuration for the IAB node based at least on one of the first resource configuration and the second resource configuration.