IAB Donor DU RLC Channel Mapping Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Integrated Access and Backhaul (IAB) networks, ensuring that data packets are mapped to appropriate RLC channels is crucial for meeting Quality of Service (QoS) requirements, but the complex topology often leads to inappropriate channel mapping, resulting in reduced user experience.
Innovation Solution
A configuration method where a donor DU determines an appropriate RLC channel for mapping data packets by using pre-configured mapping rules, which can be based on specific fields in the data packet or the quantity of RLC channels available, ensuring accurate QoS fulfillment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple RLC channels are established to meet QoS requirements of different data packets, then QoS performance is improved, but the complex IAB network topology makes it difficult to determine the appropriate RLC channel for mapping, leading to reduced user experience
Solution Approach 1:
The patent applies preliminary action by pre-configuring mapping rules at the donor CU before data transmission. The donor CU determines and configures mapping rules that associate data packets with specific RLC channels based on QoS requirements, topology information, and packet characteristics. This advance configuration enables the donor DU to efficiently map data packets to appropriate RLC channels without complex real-time decision-making, thus resolving the contradiction between maintaining high QoS performance and simplifying channel mapping determination in complex IAB network topology
Solution Approach 2:
The patent introduces mapping rules as an intermediary mechanism between data packets and RLC channels. These mapping rules act as a mediator that translates packet characteristics and QoS requirements into appropriate RLC channel selections. The mapping rules are configured by the donor CU and stored at the donor DU, serving as a lookup table or decision framework that simplifies the mapping process while ensuring QoS compliance, thereby resolving the difficulty of determining appropriate RLC channels in complex topologies
2Reliability
If flexible mapping rules are configured for each data packet, then QoS requirements are met and user experience is improved, but the configuration complexity and signaling overhead increase
Solution Approach 1:
The patent applies local quality by configuring mapping rules with specific granularity tailored to different data packet types and QoS requirements. Instead of using a single uniform mapping rule for all packets, the system configures different mapping rules locally for different QoS flows, data packet characteristics, or network conditions. This allows flexible and precise QoS fulfillment for each data packet while managing configuration complexity through targeted, context-specific rule sets rather than universal complexity
Solution Approach 2:
The patent achieves universality by designing mapping rules that can serve multiple functions simultaneously. A single mapping rule configuration can handle various data packet types, QoS requirements, and network scenarios. The mapping rules are designed to be multi-functional, capable of adapting to different situations while being configured through a unified mechanism at the donor CU. This reduces overall configuration complexity by using versatile rules rather than requiring separate specialized rules for each scenario
Data Source
Figure 1~3
Figure 4~5
Figure 6
AI summary
Embodiments of this application disclose a configuration method. A donor CU may configure a mapping rule of a data packet in advance, and then send the mapping rule to a donor DU. The donor DU maps, based on the mapping rule, a subsequently received data packet to a corresponding RLC channel for transmission. In a method in the embodiments of this application, the donor DU may configure mapping rules of two mapping processes for the donor CU. In the 1st mapping process, one or more mapping fields are first determined based on a value of one or more fields (where these fields are referred to as reference fields below for ease of description) in the data packet. In the 2nd mapping process, the RLC channel is determined based on a value of the one or more mapping fields.