Intelligent Relay Node Role Switching for Flexible 5G Coverage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Integrated Access and Backhaul (IAB) systems for 5G networks face limitations such as the need for a donor gNB, increased costs due to DU integration, inefficient spectrum usage, and lack of self-organizing capabilities, which hinder flexible deployment and coverage extension.
Innovation Solution
An intelligent relay system (IRS) node with configurable modules (FT, MT, FW, AP, DU) that can autonomously adapt to different roles and deploy flexibly, assisted by a central management module for optimized deployment and routing, enabling dynamic network integration with fixed or mobile networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Area of stationary object
If IAB nodes are deployed with fixed DU integration, then network coverage is extended, but deployment flexibility is reduced
Solution Approach 1:
The IAB node is segmented into separate CU and DU functional units that can be deployed independently. The DU can be deployed at remote locations to extend coverage while the CU remains at the donor gNB, allowing flexible geographic distribution of network functions without requiring fixed integration.
Solution Approach 2:
The IAB node design allows the same hardware platform to perform multiple functions - it can operate as a relay node, provide access to UEs, and extend backhaul connectivity. This multi-functionality enables a single deployment to address multiple network requirements simultaneously, improving both coverage and flexibility.
2Reliability
If DU is integrated in each IAB node, then network functionality is improved, but cost increases
Solution Approach 1:
The DU functionality is extracted from the donor gNB and placed in the IAB node, while the CU remains centralized. This extraction allows the expensive DU hardware to be shared across multiple IAB nodes through virtualization, reducing the total quantity of physical DU units needed while maintaining full network functionality.
Solution Approach 2:
Instead of deploying physical DU hardware in each IAB node, virtual copies of the DU function are instantiated on available hardware platforms. This copying approach maintains complete network functionality while significantly reducing hardware costs through software-based virtualization.
3Device complexity
If MT is used for CU-DU connection, then system integration is achieved, but spectrum usage efficiency is reduced
Solution Approach 1:
The F1 interface acts as an intermediary between CU and DU, providing standardized protocols for communication. This intermediary layer enables system integration through well-defined interfaces while allowing spectrum-efficient designs by separating control plane (CU) and user plane (DU) functions, enabling independent optimization of each.
4Ease of manufacture
If IAB nodes are deployed without self-organizing capability, then deployment is simpler, but adaptability to network conditions is reduced
Solution Approach 1:
The IAB node incorporates self-service capabilities including automatic neighbor discovery, autonomous parameter configuration, and self-optimization of radio resources. These self-organizing functions allow the node to adapt to changing network conditions automatically while maintaining simple initial deployment procedures.
Solution Approach 2:
The IAB node implements feedback mechanisms that continuously monitor network conditions such as signal quality, traffic load, and interference levels. Based on this feedback, the node automatically adjusts its operating parameters including transmission power, resource allocation, and neighbor relationships, enabling adaptive self-organization without complex manual configuration.
Data Source
Figure 1~3
Figure 4
Figure 5~6
AI summary
Examples relate to an Intelligent Relay System, IRS, node, and a managing apparatus, a computer program and a method thereof. The IRS node (40, 510 to 530, 610 to 630) comprises a management and control module (41, 517 to 537, 617 to 637), a routing module (42, 518 to 538, 618 to 638), one or more interfaces (43) and one or more communication modules (44). The management and control module (41, 517 to 537, 617 to 637) is configured to deploy the IRS node to a position. The routing module (42, 518 to 538, 618 to 638) is configured to obtain a routing table for forwarding packets. The one or more interfaces (43) is configured to communicate with a central IRS management module (80). The one or more communication modules (44) is configured to enable network connectivity of the IRS node in an IRS. As the IRS node may have different communication modules, it may flexibly work in different roles in the IRS, so that making the IRS to be flexible to deploy and modify according to the needs for network access by UEs.