IAB Network BAP Layer Data Duplication Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Integrated Access and Backhaul (IAB) network faces challenges in ensuring the reliability and resilience of backhaul links, particularly in 5G New Radio (NR) networks, where data duplication and de-duplication at the Backhaul Adaptation Protocol (BAP) layer are not effectively managed, leading to potential data loss and reduced network performance.

Innovation Solution

The solution involves a network device and central device configuration that receives and transmits messages with configuration information for packet duplication and de-duplication at the BAP layer, enabling data duplication detection and discard across IAB network devices, thereby enhancing the reliability and resilience of backhaul links by merging duplicated data flows.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data duplication is implemented at BAP layer for backhaul link reliability, then reliability is improved, but device complexity increases due to additional duplication and de-duplication processing

Engineering Contradiction:
Improvebackhaul link reliabilityVSAvoidBAP layer processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The IAB donor CU performs data duplication preparation in advance by configuring duplication parameters and establishing duplication contexts before actual data transmission occurs. This preliminary configuration enables the IAB nodes to automatically handle duplication and de-duplication without complex real-time decision-making, thereby improving reliability while controlling processing complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where IAB nodes report duplication status and de-duplication results back to the IAB donor CU. This feedback loop enables dynamic adjustment of duplication parameters and ensures reliable data transmission by allowing the central controller to monitor and manage the duplication process, balancing reliability improvement with complexity control.

Inventive Principle:
Principle #23Feedback

2Reliability

If duplication and de-duplication processing is added at BAP layer, then data loss is reduced, but processing time increases

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidpacket processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Duplication parameters and de-duplication contexts are established in advance before data transmission. This preliminary setup eliminates the need for complex real-time analysis during packet processing, allowing IAB nodes to quickly apply pre-configured duplication strategies and maintain low processing latency while ensuring data reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts duplication parameters such as duplication factor, selection criteria, and timing based on network conditions. By optimizing these parameters, the system achieves reliable data transmission with minimal processing time, balancing the trade-off between reliability improvement and processing speed.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If BAP layer duplication is implemented for URLLC services, then service reliability is improved, but network overhead increases

Engineering Contradiction:
ImproveURLLC service reliabilityVSAvoidnetwork overhead
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system applies data duplication selectively based on local network conditions and service requirements rather than uniformly across all traffic. IAB nodes evaluate local factors such as link quality, traffic type, and URLLC service needs to determine where duplication is most beneficial, thereby improving URLLC reliability while minimizing unnecessary overhead in other parts of the network.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements partial duplication where only a portion of data packets are duplicated based on configured parameters and network conditions. This partial approach ensures sufficient redundancy for URLLC services while avoiding excessive duplication that would waste network resources and increase overhead, achieving an optimal balance between reliability and efficiency.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20240349161A1Enhancement on integrated access and backhaul network
Publication Date: 2024.10.17 NOKIA TECHNOLOGIES OY
  • US20240349161A1 patent drawing
  • US20240349161A1 patent drawing
  • US20240349161A1 patent drawing

AI summary

Example embodiments of the present disclosure relate to devices, methods, apparatuses and computer readable storage media for enhancement on the IAB network. The method comprises: receiving, at a first network device and from a first central device for controlling the first network device, a first message comprising configuration information about at least one of duplication and de-duplication for a packet at backhaul adaptation protocol, BAP, layer; and communicating, based on the configuration information, the packet with a group of second network devices and the first central device in an integrated access and backhaul, IAB, network. By duplicating uplink and downlink data associated with terminal devices in the IAB network at BAP level, the reliability and resiliency of backhaul links can be improved.