IAB BAP Header Rewriting for Multi-Hop 5G Routing Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge of extending coverage and improving reliability in high-frequency wireless communication systems, particularly in 5G networks, is exacerbated by the limited coverage and poor propagation characteristics of high-frequency carriers, necessitating efficient multi-hop relaying solutions in integrated access and backhaul (IAB) networks.

Innovation Solution

Implementing a network node with a transceiver configured to perform BAP header rewriting based on a header rewriting configuration, and base stations capable of rerouting and rerouting BAP routing IDs, along with inter-topology routing and BAP header rewriting procedures to manage multi-hop connections and ensure reliable data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Area of stationary object

If multi-hop relaying is implemented in IAB networks, then coverage extension is improved, but network complexity increases

Engineering Contradiction:
Improvecoverage areaVSAvoidnetwork complexity
Core Design Contradiction:
Area of stationary objectVSDevice complexity

Solution Approach 1:

The patent segments the network into IAB nodes that can independently perform BAP header rewriting operations. Each node is divided into functional components (receiver, processor, transmitter) that handle specific tasks in the multi-hop relay process, enabling distributed intelligence that reduces overall network complexity while extending coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The BAP header rewriting mechanism acts as an intermediary process between different network segments. The header rewriting configuration and processing enable seamless data transmission across multiple hops by mediating the routing decisions and protocol conversions at each IAB node, thereby simplifying the multi-hop relay operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If header rewriting configuration is implemented, then routing reliability is improved, but processing complexity increases

Engineering Contradiction:
Improverouting reliabilityVSAvoidprocessing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-configuring header rewriting rules and routing information at IAB nodes before actual data transmission occurs. The header rewriting configuration is established in advance, allowing nodes to simply match and rewrite headers during operation without complex real-time decision-making, thus improving routing reliability while limiting processing complexity to configuration management.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If backup BAP routing IDs are used, then network reliability is improved, but control signaling complexity increases

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidcontrol signaling complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses copying by creating backup BAP routing IDs as copies of the primary routing configuration. These backup routing IDs are pre-established and stored at IAB nodes, allowing for rapid switching to alternative routes during failures without complex control signaling. The backup routing information is copied and cached, enabling simple retrieval and application when needed.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250344130A1Method and apparatus for communication in an IAB network
Publication Date: 2025.11.06 LENOVO (BEIJING) LTD
  • US20250344130A1 patent drawing
  • US20250344130A1 patent drawing
  • US20250344130A1 patent drawing

AI summary

Embodiments of the present disclosure relate to wireless communication in an integrated access and backhaul (IAB) network. According to some embodiments of the disclosure, a method performed by a network node may include: receiving a header rewriting configuration, wherein each entry of the header rewriting configuration indicates an ingress BAP routing ID, an egress BAP routing ID, and a next hop BAP address for the egress BAP routing ID; and performing a BAP header rewriting procedure based on the header rewriting configuration.