IAB-Node F1-C Reorientation During Inter-Donor Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IAB systems struggle with efficient migration of IAB-nodes between different donors, as they cannot effectively manage F1-C connections and payload balance during inter-donor migration, leading to inefficient signaling and forwarding paths.
Innovation Solution
A group migrating method and apparatus that enables IAB-nodes to update or configure Transmission Network Layer (TNL) addresses for F1-C connections, allowing seamless migration and reorientation of F1-C connections between donors, optimizing forwarding paths and achieving payload balance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IAB-nodes migrate between different donors, then network flexibility and adaptability are improved, but the complexity of managing topology changes and routing adaptations increases
Solution Approach 1:
The patent segments the F1-C connection management by introducing distinct indication mechanisms for different migration scenarios (intra-donor vs inter-donor). The donor device separately indicates whether the IAB-node is migrating within the same donor or to a different donor, allowing differentiated handling of connection setup and reorientation procedures.
Solution Approach 2:
The patent uses indication information as an intermediary mechanism transmitted from the donor device to the IAB-node. This indication carries critical migration context (whether the IAB-node is migrating to a different donor) that enables the IAB-node to appropriately configure new F1-C connections or reorient existing ones, simplifying the overall migration management.
2Reliability
If new F1-C connections are set up during inter-donor migration, then connectivity is maintained, but signaling overhead and setup time increase
Solution Approach 1:
The patent applies preliminary action by having the donor device provide indication information about the IAB-node's migration status before the actual migration executes. This allows the IAB-node to prepare appropriate connection configuration in advance, reducing the time required during the actual migration process.
Solution Approach 2:
The patent introduces dynamic connection management where the F1-C connection configuration adapts based on the migration scenario. The system dynamically determines whether to setup new connections or reorient existing ones based on the indication received from the donor device, optimizing the balance between connectivity reliability and setup time.
3Productivity
If existing F1-C connections are reoriented during migration, then transmission path optimization is achieved, but connection stability may be affected
Solution Approach 1:
The patent applies local quality by differentiating the handling of F1-C connections based on the specific migration scenario. For intra-donor migrations, the system reorients existing connections to optimize paths, while for inter-donor migrations, it setups new connections to maintain stability. This localized approach optimizes transmission paths where safe and maintains stability where needed.
Solution Approach 2:
The patent uses feedback from the donor device's indication information to determine the appropriate connection management strategy. The indication provides feedback about the migration context, enabling the IAB-node to make informed decisions about whether to reorient or setup connections, thus balancing optimization and stability.
Data Source
AI summary
A group migrating apparatus, configured in a second donor device, wherein the apparatus includes processor circuitry configured to, when a migrating IAB-node moves from a first donor device to the second donor device, perform at least one of the following processing enabling the migrating IAB-node to update a first TNL address used for a first F1-C connection to a second TNL address, enabling the migrating IAB-node to update a third TNL address used for a second F1-C connection to a fourth TNL address, configuring the migrating IAB-node with a fourth TNL address used for setting up a second F1-C connection, adding for the migrating IAB-node a second TNL address used for a first F1-C connection, configuring the migrating IAB-node with a third TNL address used for setting up a second F1-C connection, and adding for the migrating IAB-node a fourth TNL address used for a second F1-C connection.