IAB-Node Configuration Update During Inter-Donor Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face challenges in efficiently updating configuration information for IAB nodes during inter-donor migration in 5G NR wireless communication, leading to time delays and performance issues.

Innovation Solution

The method involves using dedicated RRC messages and F1-AP/F1 setup failure messages to update configuration information for migrating IAB nodes, including gNB-DU ID, NR PCI, NR CGI, and PLMN ID, thereby reducing migration time delays and improving system performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If traditional configuration update methods are used during inter-donor migration, then system compatibility is maintained, but migration time delays increase and performance deteriorates

Engineering Contradiction:
Improvemigration time delayVSAvoidconfiguration update complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The target IAB-donor CU allocates and prepares configuration information for the migrating IAB-node DU in advance, before the migration is completed. This preliminary allocation of gNB-DU ID, NR PCI, NR CGI, and PLMN ID allows the configuration to be ready when needed, reducing migration time delays while maintaining manageable complexity through structured pre-preparation

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces the F1 setup failure message as an intermediary mechanism to transmit configuration information from the target IAB-donor CU to the migrating IAB-node DU. This intermediary message type enables efficient configuration delivery during migration without requiring complete system reconfiguration, thus reducing time delays while keeping the update process organized

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If configuration information is updated during inter-donor migration, then migration performance improves, but system reliability may be compromised due to potential configuration conflicts

Engineering Contradiction:
Improvemigration efficiencyVSAvoidconfiguration consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The F1 setup failure message serves as a safe intermediary channel that is specifically designed to carry configuration information during migration without interfering with normal system operations. This dedicated message path ensures configuration updates are delivered reliably while maintaining system stability, as the message type is recognized and handled appropriately by the IAB-node DU

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent systematically updates multiple configuration parameters (gNB-DU ID, NR PCI, NR CGI, PLMN ID) in a coordinated manner through the F1 setup failure message. By changing these parameters together in a controlled sequence, the system ensures configuration consistency across all elements, improving migration efficiency while maintaining reliability through synchronized parameter updates

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12610291B2Methods and devices for updating IAB-node configuration information during inter-donor migration
Publication Date: 2026.04.21 ZTE CORP
  • US12610291B2 patent drawing
  • US12610291B2 patent drawing
  • US12610291B2 patent drawing

AI summary

The present disclosure describes methods, systems, and devices for updating configuration information for a migrating integrated access backhaul node (IAB-node) during an inter-donor migration from a source IAB-donor to a target IAB-donor. One method includes providing, by a target IAB-donor central unit (CU), configuration information for a migrating IAB-node distributed unit (DU) in a dedicated radio resource control (RRC) message during handover preparation. The method further includes sending, by the target IAB-donor CU, a XnAP message to a source IAB-donor CU, the XnAP message comprising the configuration information as an RRC transparent container, and then the source IAB-donor CU sends the dedicated RRC message to a migrating IAB-node mobile termination (MT), the dedicated RRC message comprising the configuration information.