Inter-system Mobility Load Balancing via Event-triggered SON Reports
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems lack support for inter-system mobility load balancing, which is essential for evenly distributing traffic load among cells and areas, particularly when dealing with mixed deployments of different radio access technologies (RATs) like LTE and NR.
Innovation Solution
The implementation of inter-system and event-triggered mobility load balancing (MLB) methods, where nodes from different RATs, such as E-UTRA and NR, exchange load information through enhanced self-organizing network (SON) information reports, allowing for periodic and event-triggered load reporting, enabling efficient load distribution across cells, beams, or slices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If inter-system load balancing is implemented between different RATs, then traffic load distribution is improved, but system complexity increases due to enhanced information reporting requirements
Solution Approach 1:
The SON information report message structure is designed to be universal and multi-functional, capable of carrying both periodic and event-triggered load reporting IEs. This allows a single message format to handle multiple reporting scenarios between different RATs, reducing the need for separate complex reporting mechanisms for each scenario.
Solution Approach 2:
The system implements dynamic reporting by allowing nodes to switch between periodic and event-triggered reporting modes based on current network conditions. The event-triggered reporting activates only when specific load threshold events occur, dynamically adjusting the reporting behavior to balance information freshness with signaling overhead.
2Loss of energy
If event-triggered load reporting is implemented, then reporting overhead is reduced, but measurement precision requirements increase
Solution Approach 1:
The event-triggered reporting mechanism uses feedback thresholds to determine when reporting should occur. Nodes monitor their load levels and trigger reports only when load crosses predefined thresholds, providing feedback-based control that reduces unnecessary reporting while maintaining adequate load information for MLB decisions.
Solution Approach 2:
The system changes the reporting parameter from continuous periodic reporting to discrete event-triggered reporting based on load threshold crossings. This parameter change transforms the reporting behavior from time-driven to condition-driven, reducing overall reporting overhead while maintaining measurement precision at critical load levels.
3Loss of information
If periodic load reporting is used, then load information availability is improved, but signaling overhead increases
Solution Approach 1:
The system implements periodic load reporting as one of two complementary modes, where nodes report load information at regular intervals. This periodic action ensures load information remains available and up-to-date, providing a baseline reporting mechanism that works alongside event-triggered reporting to maintain information availability without excessive overhead.
Data Source
AI summary
Methods, systems, and devices for wireless communications are described. Some wireless communications system may utilize an inter-system information report message (e.g., a self-organizing network (SON) information report message) to support inter-system mobility load balancing (MLB). For example, a first node, operating in accordance with a first radio access technology (RAT), may receive an information report message from a second node operating in accordance with a second RAT. The information report message may include a periodic load reporting request information element (IE) or an event-triggered load reporting request IE. In response, the first node may determine a traffic load based on the load reporting request and transmit, to the second node, an information report message which includes one or more IEs for reporting the determined traffic load. The exchange of the load information via the IEs may enable for MLB between nodes of different RAT.