IAB Multi-Hop Configuration Forwarding for Lower Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face significant configuration latency issues in Integrated Access and Backhaul (IAB) networks due to the sequential processing of RRCReconfiguration messages for each hop, which is exacerbated by network events like radio link failures and node overloads, impacting applications requiring ultra-reliable low-latency communication.
Innovation Solution
Implement architectural changes such as network node grouping, BAP header modifications, configuration forwarding, and configuration multicasting to reduce latency by using a single RRCReconfiguration message for multiple nodes, and fast activation of backup links through Layer 1 and Layer 2 stacks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If sequential processing of RRCReconfiguration messages is used for each hop in IAB networks, then configuration reliability is maintained through individual acknowledgment, but configuration latency increases significantly
Solution Approach 1:
The patent combines multiple individual RRCReconfiguration messages into a single multicast message that can configure multiple IAB nodes simultaneously. The donor node sends one multicast RRCReconfiguration message that contains configuration information for multiple hops, eliminating the need for sequential unicast messages and reducing overall configuration latency while maintaining reliability through individual acknowledgment mechanisms for each node.
Solution Approach 2:
The patent implements preliminary action by having IAB nodes send configuration acknowledgments in advance through the BAP protocol before the complete configuration process finishes. Nodes acknowledge receipt of the multicast RRCReconfiguration message immediately, allowing the donor node to track configuration status proactively rather than waiting for sequential completions.
2Manufacturing precision
If individual RRCReconfiguration messages are sent to each IAB node, then configuration accuracy is ensured through node-specific settings, but message quantity and processing overhead increase
Solution Approach 1:
The patent makes the single RRCReconfiguration message universal by designing it to contain configuration information that can apply to multiple IAB nodes simultaneously. The multicast message includes node-specific configuration parameters embedded within a single message structure, allowing one message to serve multiple functions and configure different nodes with their respective settings without requiring separate messages for each node.
Solution Approach 2:
The patent uses copying by creating template-based configuration data that can be replicated and distributed to multiple nodes. The donor node prepares a standardized configuration template in the multicast message that each IAB node can copy and apply locally, reducing the need to transmit identical configuration data multiple times while ensuring each node receives the appropriate settings.
3Reliability
If backup links are activated through traditional layers, then link reliability is achieved, but activation latency is too high for ultra-reliable low-latency communication
Solution Approach 1:
The patent implements preliminary action by pre-configuring backup links through the multicast RRCReconfiguration message before failures occur. The configuration information for backup links is prepared and distributed in advance, so when a failure happens, the activation process is already partially complete, significantly reducing the time needed to switch to backup links compared to traditional on-demand configuration.
Solution Approach 2:
The patent applies skipping by bypassing traditional sequential activation procedures and using direct BAP-layer mechanisms to rapidly activate backup links. The system skips intermediate configuration steps by utilizing pre-established configuration data in the multicast message and activating backup paths through optimized BAP routing decisions, rushing through the activation process to meet ultra-low latency requirements.
Data Source
AI summary
Multi-hop configurations in Integrated Access and Backhaul (IAB) networks are provided for reduced latency. For example, modifications to a backhaul adaptation protocol (BAP) header supports faster data radio bearer (DRB) transmissions. Or, for both signaling radio bearer (SRB) and DRB flows, configuration forwarding may be used to reduce configuration latency wherein a single RRCReconfiguration message is forwarded to intermediate nodes that process the configuration and respond back independently. Alternatively, for both SRB and DRB flows, configuration multi-casting may be used for simultaneous IAB node and backup configurations. Methods are provided for fast activation of backup links in IAB nodes.