Multi-Hop IAB Packet Delay Budget Enforcement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for enforcing packet delay budgets in multi-hop integrated access and backhaul (IAB) networks face challenges in efficiently managing packet delay budgets across multiple hops, leading to potential packet drops and resource wastage due to unclear latency and delay budget information.

Innovation Solution

Implementing a system where IAB nodes and WTRUs receive configuration information about buffer thresholds and packet delay budgets, allowing them to select appropriate buffer thresholds based on remaining packet delay budgets and transmit packets via the most available link, with options to duplicate packets or send status reports if resources are not available, thereby optimizing packet routing and reducing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If packet delay budgets are not enforced in multi-hop IAB networks, then network complexity is reduced, but packet delivery reliability deteriorates due to potential packet drops

Engineering Contradiction:
Improvepacket delivery reliabilityVSAvoidnetwork complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary configuration of buffer thresholds and packet delay budgets before packet transmission. Each IAB node is pre-configured with buffer thresholds associated with different remaining PDB ranges, enabling proactive packet management decisions based on predicted delay requirements rather than reactive responses to packet drops

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the packet delay budget management into discrete ranges with associated buffer thresholds. Instead of treating all packets uniformly, the system divides the remaining PDB into multiple ranges (e.g., first remaining PDB range below a value, second remaining PDB range above the value) and applies different buffer management strategies to each segment, enabling精细化 control over packet prioritization

Inventive Principle:
Principle #1Segmentation

2Loss of time

If buffer thresholds are not configured based on remaining PDB ranges, then device operation is simplified, but time management of packets deteriorates leading to increased latency

Engineering Contradiction:
Improvepacket latencyVSAvoiddevice operation complexity
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The system dynamically changes buffer threshold parameters based on the remaining packet delay budget ranges. Configuration information indicates different buffer thresholds (first buffer threshold, second buffer threshold) associated with different remaining PDB ranges, allowing the device to adapt buffer management parameters according to the urgency of packet delivery requirements

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The buffer threshold configuration is made dynamic rather than static. The device selects which buffer threshold to apply based on the determined remaining PDB of each packet, creating a dynamic adaptation mechanism that responds to real-time packet delay requirements while maintaining systematic operation through pre-defined threshold ranges

Inventive Principle:
Principle #15Dynamics

3Reliability

If packets are not transmitted via multiple available links, then device complexity is reduced, but network reliability worsens due to lack of redundancy

Engineering Contradiction:
Improvenetwork redundancyVSAvoidtransmission management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements partial packet duplication by selecting packets with remaining PDB below a threshold for transmission via both default and secondary links. Not all packets are duplicated - only those with urgent delay requirements - thereby providing redundancy where needed while avoiding the full complexity of transmitting all packets through multiple paths

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20240196262A1Enforcing packet delay budgets associated with multi-hop iab
Publication Date: 2024.06.13 INTERDIGITAL PATENT HOLDINGS INC
  • US20240196262A1 patent drawing
  • US20240196262A1 patent drawing
  • US20240196262A1 patent drawing

AI summary

A device may transmit data to a first parent node via a first link and to a second parent node via a second link. The device may receive configuration information indicating at least one of: a first buffer threshold associated with a first remaining packet delay budget (PDB), a second buffer threshold associated with a second remaining PDB, or a remaining PDB threshold. The device may receive a packet and may determine a remaining PDB. The device may select a buffer threshold based on the configuration information and the determined remaining PDB. If an amount of data in an uplink (UL) buffer is equal to or above the selected buffer threshold, the device may transmit the packet via a first available link. If the determined remaining PDB is less than the remaining PDB threshold, the device may transmit the packet via both the first link and the second link.