Inter-Donor Routing in IAB Networks via IP Header Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Integrated Access and Backhaul (IAB) networks face challenges in inter-donor routing, particularly in handling IP address reconfiguration and ensuring end-to-end security during inter-donor migration, leading to service interruptions and increased signaling load due to conflicting requirements in IP addressing and security tunneling.
Innovation Solution
A method involving the addition of an additional IP header to IP packets for inter-donor routing, allowing the target donor to build a Backhaul Adaptation Protocol (BAP) header based on this header, and modifying packets at the migrating IAB node to maintain transparent handover of UEs and avoid IP address reconfiguration of descendant nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IP address reconfiguration is performed during inter-donor migration, then routing can be updated to reflect new network topology, but service interruptions occur and signaling load increases
Solution Approach 1:
The patent performs IP header modification in advance during the migration preparation phase. The source donor updates the IP header with the target donor's address before the actual handover, so that when the handover occurs, the routing is already correct and no additional reconfiguration signaling is needed during the critical transition moment.
Solution Approach 2:
The patent introduces an intermediary IP header modification mechanism that acts as a bridge between source and target donors. The IP header serves as an intermediary carrier that encapsulates routing information, allowing the target donor address to be transmitted through the source donor without requiring direct reconfiguration signaling between all network elements during handover.
2Reliability
If security tunnels are reconfigured during inter-donor migration, then end-to-end security can be maintained with new donor, but service interruptions occur and signaling load increases
Solution Approach 1:
The patent performs security tunnel reconfiguration in advance by updating the IP header with the target donor's address before the actual handover. This preliminary action ensures that security associations are already established with the correct endpoint, eliminating the need for time-consuming security renegotiation during the critical handover moment.
Solution Approach 2:
The patent maintains continuous security protection by ensuring that the IP header always contains the current valid donor address. The security tunnel remains active and functional throughout the migration process because the routing information in the IP header is updated in advance, allowing data to flow continuously through the appropriate security context without interruption.
3Adaptability or versatility
If additional IP header is added for inter-donor routing, then transparent handover and load balancing are enabled, but packet size increases and processing complexity increases
Solution Approach 1:
The patent makes the IP header multi-functional by using it both for its traditional routing purpose and as a carrier for inter-donor migration information. The IP header's destination address field serves dual purposes: normal packet routing and indicating the target donor for migration scenarios. This eliminates the need for separate signaling messages or additional data structures, reducing overall system complexity despite the header's extended functionality.
Data Source
AI summary
A method, system and apparatus are disclosed. A first integrated access and backhaul, IAB, node in communication with a second IAB node, a first network node, and a second network node is provided. The first IAB node receives an instruction from at least one of the first and second network nodes, the instruction being associated with a traffic migration of traffic routed via the first IAB node, the traffic migration being from the first network node to the second network node. The first IAB node receives an uplink, UL, packet from the second IAB node, where the UL packet includes a first address indicator, and modifies the UL packet, including adding a second address indicator associated with the first IAB node to the UL packet, the modifying being based on the instruction. The first IAB node transmits the UL packet to the second network node.