Relay Node Routing Restrictions to Prevent IAB Loop-Back Loops
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communication networks, particularly in 5G IAB architectures, the introduction of loop-back routes can lead to routing loops due to independent re-routing decisions by IAB nodes, which is not addressed by current standards that allow unrestricted packet forwarding based on Destination and Path fields, leading to inefficiencies and potential network failures.
Innovation Solution
Implementing restrictions on packet forwarding by modifying the BAP PDU headers to indicate specific routes and restrict re-routing, ensuring that packets follow designated paths and avoiding loop-back routes, thereby preventing routing loops.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IAB nodes are allowed to make independent re-routing decisions based on Destination and Path fields, then packet forwarding flexibility is improved, but routing loops occur leading to network reliability degradation
Solution Approach 1:
The patent introduces a feedback mechanism where IAB nodes exchange routing information and status details with their neighbors. Each node uses this feedback to make informed re-routing decisions, avoiding loops by knowing the current network state. The feedback includes routing information, status details, and path information that enables nodes to detect and prevent routing loops while maintaining flexible packet forwarding.
Solution Approach 2:
The patent implements preliminary action by having IAB nodes prepare and validate routing paths before actual packet forwarding occurs. Nodes perform path validation and loop detection in advance using the routing configuration and status information exchanged during the setup phase, ensuring that only loop-free paths are activated for data transmission.
2Ease of operation
If unrestricted packet forwarding is allowed based on Destination and Path fields, then routing simplicity is improved, but routing loops cause data transmission failures
Solution Approach 1:
The feedback mechanism provides routing status information to IAB nodes, enabling them to make informed decisions about packet forwarding. This feedback includes information about active paths, node status, and routing configurations, allowing nodes to maintain simple forwarding rules while avoiding loops through intelligent decision-making based on network state awareness.
3Reliability
If loop-back routes are introduced for recovery, then network robustness is improved, but routing complexity increases due to independent re-routing decisions
Solution Approach 1:
The patent merges the routing decision-making process into a coordinated system where IAB nodes share routing information and status details. Instead of independent re-routing decisions, nodes combine their routing configurations with feedback from neighbors to create cohesive, loop-free paths. This merging approach maintains robustness through coordinated recovery while reducing complexity through shared decision-making.
Solution Approach 2:
The feedback mechanism provides routing status information that enables IAB nodes to make coordinated re-routing decisions. Nodes use this feedback to understand the current network state and select appropriate paths, reducing the complexity of independent decision-making while maintaining network robustness through unified routing management.
Data Source
AI summary
Apparatuses and methods in a communication system are disclosed. A relay node in a network is disclosed. The network comprises a set of nodes operationally connected to the relay node. The relay node receives (500) a routing configuration, receives (502) a packet to be routed, reads (504) at least one header field of the packet, selects (506) a route for forwarding the packet based on the at least one header field and the routing configuration, applies (508) at least one restriction related to the packet based on at least one of the routing configuration and the at least one header field, and forwards (510) the packet to the selected route.