IAB Capability Indication for Wireless Node Connection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems lack effective methods for indicating Integrated Access and Backhaul (IAB) capability between nodes, leading to unutilized IAB operations due to a lack of information about supported capabilities, particularly between Control-Plane Central Units (CU-CP) and Distributed Units (DU) or User-Plane Central Units (CU-UP) and CU-CP.
Innovation Solution
A method where nodes, such as DU and CU-CP or CU-UP, exchange messages to indicate their IAB capabilities, allowing for the establishment of IAB capable connections by activating IAB functionality and configuring communications based on these indications, using messages like F1 setup or configuration update procedures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If nodes exchange detailed capability information messages, then IAB capability utilization is improved, but signaling overhead and message complexity increase
Solution Approach 1:
The patent extracts only the essential IAB capability information from complex capability messages and transmits only these extracted key elements. This selective extraction reduces signaling overhead while maintaining the ability to establish IAB capable connections, resolving the contradiction between comprehensive capability utilization and minimal signaling overhead.
Solution Approach 2:
The patent performs preliminary capability indication by including IAB capability flags in initial setup messages (such as F1 SETUP REQUEST) before detailed capability negotiation. This preliminary action allows nodes to quickly identify IAB-capable partners without exchanging extensive capability information at the outset, reducing overall signaling overhead.
2Area of stationary object
If IAB functionality is activated between all node pairs, then network coverage extension is improved, but system complexity and configuration overhead increase
Solution Approach 1:
The patent enables preliminary identification of IAB-capable node pairs through capability indication messages exchanged during network setup. By pre-identifying compatible nodes before full configuration, the system can selectively activate IAB functionality only where needed and feasible, extending coverage without proportionally increasing system complexity.
Solution Approach 2:
The patent implements self-service mechanisms where nodes automatically detect IAB capability compatibility through exchanged messages and autonomously establish IAB connections without extensive manual configuration. This self-configuration capability reduces system complexity while enabling widespread IAB functionality activation for coverage extension.
3Reliability
If comprehensive capability negotiation is performed during connection establishment, then connection reliability is improved, but connection setup time increases
Solution Approach 1:
The patent performs preliminary IAB capability indication in early setup messages (F1 SETUP REQUEST/RESPONSE) before detailed connection negotiation. This preliminary action ensures that only IAB-capable nodes proceed with full capability negotiation, maintaining connection reliability while reducing the time required for nodes without IAB capability to establish connections.
Solution Approach 2:
The patent segments the capability negotiation process into two phases: a quick preliminary capability indication phase using minimal messages, and a detailed capability negotiation phase only for IAB-capable nodes. This segmentation allows non-IAB nodes to establish connections quickly while IAB nodes undergo comprehensive negotiation, balancing overall connection setup time with reliability.
Data Source
AI summary
Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a first node may transmit, to a second node, a first message providing a first indication of integrated access and backhaul (IAB) capability. The first node may receive, from the second node and in response to the first message, a second message providing a second indication of IAB capability. The first node may establish an IAB capable connection with the second node based at least in part on the first message and the second message. Numerous other aspects are provided.