Synchronized IAB Resource Activation via Delay Compensation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-hop Integrated Access and Backhaul (IAB) networks, timing misalignment of semi-static resource configurations between parent IAB-nodes can lead to configuration conflicts and interference due to varying packet arrival times, which complicates centralized coordination and resource management.

Innovation Solution

The proposed solution involves estimating packet delay information between IAB-donor-CU and IAB-nodes to synchronize the activation timing of semi-static configurations, ensuring that all parent IAB-nodes execute updates simultaneously, using mechanisms like Level 2 Medium Access Control-Control Element (L2 MAC CE) or Downlink Control Indicator (DCI) commands, to prevent conflicts and interference.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If configuration updates are applied immediately upon receipt at each IAB-node, then configuration responsiveness is improved, but timing misalignment and configuration conflicts occur between parent IAB-nodes

Engineering Contradiction:
Improveconfiguration update speedVSAvoidconfiguration consistency
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The IAB-donor-CU performs preliminary actions by determining the packet delay for each parent IAB-node before transmitting configuration updates. Based on these delay measurements, the IAB-donor-CU calculates and embeds appropriate delay values in the F1 messages, enabling each parent IAB-node to apply configurations at synchronized times despite different transmission delays

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where parent IAB-nodes report their configuration application status and timing information back to the IAB-donor-CU. This feedback loop allows the IAB-donor-CU to monitor and adjust configuration timing, ensuring synchronized application across all parent nodes and resolving timing misalignment issues

Inventive Principle:
Principle #23Feedback

2Reliability

If centralized coordination is implemented to ensure configuration alignment, then configuration consistency is improved, but system complexity increases

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidcoordination system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The IAB-donor-CU acts as an intermediary that centralizes coordination functions. It measures packet delays to each parent IAB-node, calculates appropriate delay values, embeds these in F1 messages, and monitors configuration application. This intermediary approach ensures configuration consistency while managing complexity at a single point rather than requiring complex distributed coordination protocols

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the timing parameter of configuration application by introducing delay values that are dynamically calculated based on measured packet delays. Instead of applying configurations at fixed intervals or immediately, the IAB-donor-CU adjusts the application timing parameter for each parent node to compensate for transmission delays, achieving synchronization through parameter optimization

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20240340656A1Synchronized Activation of Semi-Static Resource Configurations for Integrated Access and Backhaul Multi-Parent Nodes
Publication Date: 2024.10.10 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20240340656A1 patent drawing
  • US20240340656A1 patent drawing
  • US20240340656A1 patent drawing

AI summary

A method performed by an integrated access and backhaul (IAB) donor node (102, 802a, 802b) for synchronized activation of a resource configuration. The method includes determining (906), by the IAB-donor node, a synchronized update time for performing a synchronized configuration update in a plurality of parent IAB-nodes (804a, 804b) and/or a child IAB-node (806). The child IAB-node is dual-connected to the plurality of parent IAB-nodes. The method additionally includes transmitting (908), by the IAB-donor node, the synchronized update time to at least each parent IAB-node and/or the child IAB-node.