IAB Backhaul Routing With BAP Header Rewriting for Fast Path Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integrated access and backhaul (IAB) network faces challenges in adapting to rapid changes in link quality due to centralized routing management by the donor node, leading to packet loss and node congestion, which the IAB node congestion, due to the donor node's centralized routing management of backhaul adaptation protocol (BAP) packets, resulting in latency and failure to adapt to node mobility.
Innovation Solution
The IAB node autonomously selects a next-hop BAP address and path based on channel quality, rewriting the BAP data PDU header to adapt to channel changes without waiting for donor node intervention, reducing packet loss and congestion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the donor node performs centralized routing management on BAP packets, then routing control is centralized and manageable, but path switching latency increases causing packet loss and node congestion
Solution Approach 1:
The IAB node autonomously performs path selection and BAP header rewriting based on channel quality measurements, without waiting for donor node intervention. The node monitors its own link conditions and independently switches paths when degradation is detected, enabling self-service adaptation that eliminates centralized routing latency.
Solution Approach 2:
The IAB node pre-configures multiple BAP routing entries with different next-hop addresses and path identifiers before channel degradation occurs. When link quality deteriorates, the node can immediately switch to a pre-configured alternative path without waiting for donor node instructions, performing the path switching action in advance preparation.
2Adaptability or versatility
If the donor node performs centralized routing management, then routing decisions are controlled centrally, but adaptation to rapid channel changes fails due to latency
Solution Approach 1:
The IAB node dynamically monitors channel quality metrics and continuously adjusts path selection based on real-time conditions. The node can switch between multiple pre-configured BAP routing entries depending on current link quality, enabling dynamic adaptation to rapid channel changes rather than static centralized routing decisions.
Solution Approach 2:
The IAB node implements a feedback mechanism where channel quality measurements trigger automatic path switching decisions. When the node detects degradation in link quality through continuous monitoring, it feeds this information back to its routing logic and autonomously switches to an alternative path, creating a closed-loop adaptive system.
3Reliability
If the IAB node waits for donor node path switching, then centralized control is maintained, but packet loss occurs due to long latency
Solution Approach 1:
The IAB node autonomously performs path switching and BAP header rewriting when channel degradation is detected, without waiting for donor node instructions. This self-service capability allows the node to immediately switch to alternative paths, preventing packet loss that would occur during centralized path switching latency.
Solution Approach 2:
The IAB node takes preliminary protective action by pre-configuring multiple BAP routing entries and continuously monitoring channel quality. When degradation is detected, the node preemptively switches to alternative paths before packet loss can occur, counteracting potential harm in advance rather than reacting after damage occurs.
Data Source
AI summary
This application provides a communication method and apparatus. Including: receiving a backhaul adaptation protocol (BAP) data protocol data unit (PDU) and backhaul (BH) routing configuration information, where a BAP data PDU header includes a first destination address field and a first path field, the BH routing configuration information includes at least one entry, each of the at least one entry includes a BAP address, a next-hop BAP address, and a BAP path identifier, and the BAP address of each of the at least one entry matches the first destination address field; selecting a first entry from the at least one entry, and selecting a link corresponding to a next-hop BAP address in the first entry as an egress link; and rewriting the BAP data PDU header, and sending the BAP data PDU to the egress link.