AIR Power Pooling via Scheduling Entity Dropping Across Carriers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing radio resource management (RRM) systems in active antenna systems face challenges in coordinating among multiple carriers and radio access technologies due to increased latency and complexity, especially in multi-carrier and multi-RAT scenarios, which complicates efficient power allocation and increases energy consumption.
Innovation Solution
Implementing a method in the Antenna Integrated Radio (AIR) to receive scheduling attributes from Distributed Units (DUs), drop low-priority SEs based on power requirements, and send information to DUs to manage power pooling dynamically, allowing indirect RRM coordination without direct communication between RRM instances.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If RRM instances execute in unique subsets of cores allocated to single carriers, then time-critical RRM functions execute efficiently for each carrier, but RRM coordination among different carriers becomes difficult and increases latency
Solution Approach 1:
The system segments RRM functions into two categories: time-critical functions that execute locally in distributed RRM instances on specific cores, and non-time-critical coordination functions that execute centrally in a centralized RRM instance. This segmentation allows time-critical functions to maintain high execution speed while coordination tasks are handled centrally to avoid latency
Solution Approach 2:
The centralized RRM instance acts as an intermediary between distributed RRM instances, receiving scheduling decisions from distributed instances and returning coordinated decisions. This intermediary approach enables coordination among carriers without requiring direct communication between distributed instances, thus reducing latency while maintaining coordination effectiveness
2Adaptability or versatility
If multiple RATs and frequency bands are deployed across multiple devices, then network capacity and coverage are enhanced, but RRM coordination becomes even more complicated
Solution Approach 1:
The centralized RRM instance serves as a universal intermediary that handles coordination across multiple RATs (LTE, NR) and frequency bands. It receives scheduling decisions from distributed instances supporting different RATs and bands, performs centralized coordination considering all constraints, and returns coordinated decisions. This approach manages the complexity of multi-RAT and multi-band coordination without requiring complex direct interactions between distributed instances
Solution Approach 2:
The centralized RRM instance is designed to handle multiple RATs and frequency bands universally. It can process scheduling decisions from distributed instances supporting different RATs (LTE, NR) and coordinate resources across multiple frequency bands, making the system adaptable to diverse deployment scenarios without increasing coordination complexity
3Productivity
If RRM coordination is implemented among different carriers, then multiplexing gain is achieved, but coordination introduces dependency and increases latency
Solution Approach 1:
The centralized RRM instance acts as an intermediary that manages coordination dependency. Distributed RRM instances send their scheduling decisions to the centralized instance, which coordinates resource allocation across carriers and returns coordinated decisions. This intermediary approach achieves multiplexing gain by enabling cross-carrier coordination while managing dependency in a controlled manner, avoiding the need for complex direct peer-to-peer coordination between distributed instances
Data Source
AI summary
A Distributed Unit (DU) or vDU of a wireless network node operates to send, to an Antenna Integrated Radio (AIR) or ORAN Radio of the wireless network node, scheduling attributes associated with each one of a plurality of Scheduling Entities (SEs) among multiple carriers. The scheduling attributes include an indication of a priority of the associated SE and whether or not the associated SE can be dropped. The AIR receives the scheduling attributes and drops one or more low priority droppable SEs based on a total power requirement and a target power level of the AIR. The AIR sends, to the DU, information identifying the dropped SEs of the corresponding carriers and DU or vDU. The DU reschedules at least a subset of the dropped SEs for transmission in a subsequent transmission time interval (TTI).


