Dynamic Load Reporting in Wireless Backhaul

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless communication systems face inefficiencies in load reporting between network entities, relying on periodic reporting criteria that lead to high energy consumption and inefficient use of communication resources.

Innovation Solution

The implementation of enhanced load reporting methods that allow network entities, such as distributed units (DUs) and centralized units (CUs), to initiate load reports based on triggering events or autonomously, without relying on periodic criteria, thereby optimizing resource utilization and reducing energy consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If periodic reporting criteria are used for load reports between network entities, then the reporting mechanism is simple and reliable, but energy consumption increases and communication resources are wasted

Engineering Contradiction:
Improveenergy consumptionVSAvoidreporting mechanism complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent implements dynamic load reporting where the reporting behavior changes from static periodic intervals to dynamic event-driven transmissions. The DU monitors load conditions and triggers reports only when threshold conditions are met, making the reporting mechanism adaptive to actual network needs rather than following a fixed schedule.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The DU autonomously determines when to send load reports by monitoring its own load conditions against configured thresholds. The self-triggering mechanism eliminates the need for continuous CU-initiated requests, allowing the DU to self-manage reporting based on its operational state.

Inventive Principle:
Principle #25Self-service

2Productivity

If periodic load reporting is implemented, then network entities maintain continuous awareness of load conditions, but communication resources are inefficiently used

Engineering Contradiction:
Improvecommunication resource efficiencyVSAvoidload condition awareness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent establishes a feedback mechanism where the CU provides threshold configurations to the DU, and the DU responds with load reports only when conditions change. This selective feedback loop maintains reliability by triggering reports at critical moments while improving efficiency by avoiding unnecessary periodic transmissions.

Inventive Principle:
Principle #23Feedback

3Use of energy by stationary object

If triggering events are provided to the DU for initiating load reports, then energy consumption is reduced, but the system requires additional configuration and control signaling

Engineering Contradiction:
Improveenergy consumptionVSAvoidsystem configuration complexity
Core Design Contradiction:
Use of energy by stationary objectVSDevice complexity

Solution Approach 1:

The CU performs preliminary action by configuring threshold values and reporting criteria before the DU needs to initiate reports. This advance configuration eliminates the need for complex real-time decision-making at the DU, reducing processing overhead while enabling energy-efficient event-driven reporting.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12267723B2Load reporting in backhaul communications
Publication Date: 2025.04.01 QUALCOMM INC
  • US12267723B2 patent drawing
  • US12267723B2 patent drawing
  • US12267723B2 patent drawing

AI summary

Methods, systems, and devices for wireless communications are described. Aspects of the disclosure relate to enhanced load reporting between network entities (e.g., provided by a distributed unit (DU) to a centralized unit (CU) or by a CU to another CU). In some examples, the CU may provide one or more triggering events which may be used by the DU (or a second CU) to trigger the provisioning of a load report to the CU. Accordingly, the DU (or second CU) may be able to initiate a load report without relying on periodic reporting criteria. In some examples, the DU may initiate a load report to the CU without being configured with triggering events. In some examples, a DU may report measurements made associated with a communications load involving communications with both a parent network entity (e.g., a CU) and at least one child network entity (e.g., a user equipment).