IAB Relay Node Identification to Prevent BAP Address Conflicts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In an integrated access and backhaul (IAB) network, when a distributed unit (DU) of a network node is migrated but the mobile termination (MT) is not, a conflict arises between backhaul adaptation protocol (BAP) addresses due to the target donor-CU not being aware of the existing BAP address allocation, leading to communication errors.
Innovation Solution
The DU includes identification information of the MT and/or itself in a message to the target donor-CU, allowing the donor-CU to manage the relay node accurately without relying on the BAP address, thus resolving conflicts and reducing resource overheads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the DU uses the BAP address allocated by the source donor-CU in the F1 SETUP REQUEST message to the target donor-CU, then the DU can maintain backward compatibility with the source topology, but BAP address conflict occurs with other IAB-nodes served by the target donor-CU
Solution Approach 1:
The patent introduces identification information of the MT as an intermediary element in the F1 SETUP REQUEST message. This intermediary allows the target donor-CU to distinguish between different IAB-nodes based on their MT identity rather than relying solely on BAP addresses, thereby preventing address conflicts while maintaining compatibility
Solution Approach 2:
The patent adds a new dimension of identification by incorporating MT identification information into the F1 SETUP REQUEST message. This extends the addressing mechanism from solely BAP address-based identification to a multi-dimensional identification system that combines BAP address with MT identity, enabling unambiguous node distinction
2Measurement precision
If the DU includes both BAP address and MT identification information in the F1 SETUP REQUEST message, then the target donor-CU can accurately identify the relay node, but the message complexity increases
Solution Approach 1:
The patent segments the identification function into separate components: BAP address for topology-based identification and MT identification information for node-based identification. This segmentation allows each component to serve its specific purpose while working together to achieve comprehensive node identification without unnecessary complexity
3Reliability
If the target donor-CU allocates a new BAP address for the migrated DU, then BAP address conflict is avoided, but the topology management complexity increases due to coordination between donor-CUs
Solution Approach 1:
The patent enables the DU to self-identify using its MT identification information in the F1 SETUP REQUEST message. This self-service mechanism allows the target donor-CU to automatically recognize the DU's identity and manage the topology without requiring complex coordination or negotiation with the source donor-CU, simplifying the overall system management
Data Source
AI summary
This application provides a communication method, wherein an mIAB-DU sends a third message to a CU, where the third message includes ULI of the mIAB-MT; the CU sends a fourth message to an AMF, where the fourth message includes ULI of UE and indication information indicating the ULI of the mIAB-MT.