Master RNC Synchronization for MBSFN Resource Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In MBSFN, the synchronization of MBMS configuration information between RNCs is challenging, particularly when multiple MBMS services are mapped to Secondary Common Control Physical Channels (S-CCPCHs), leading to failures in soft combining and air interface combining, and dynamic synchronization of MCCH configuration information is difficult to implement.
Innovation Solution
A method where one RNC acts as a master RNC to generate and send MBMS configuration information messages to slave RNCs, establishing point-to-multipoint control channels, ensuring dynamic synchronization through IUR interfaces and IP multicasting, thereby maintaining consistency in mapping relationships and scheduling information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each RNC independently determines its own MBMS configuration information, then configuration flexibility is improved, but consistency between RNCs deteriorates
Solution Approach 1:
The system divides RNCs into a master RNC and slave RNCs. The master RNC is responsible for generating and distributing MBMS configuration information to all slave RNCs, while slave RNCs execute the received configuration. This segmentation of responsibilities ensures that all RNCs use consistent configuration information while maintaining the ability to adapt to different network conditions through the master RNC's centralized control.
2Reliability
If MBMS configuration information is synchronized statically through OM, then initial consistency is improved, but dynamic synchronization capability deteriorates
Solution Approach 1:
The system implements dynamic synchronization by enabling the master RNC to generate and distribute MBMS configuration information messages to slave RNCs in real-time. When configuration changes are needed, the master RNC can update all slave RNCs dynamically through the IUR interface, ensuring all RNCs remain synchronized without requiring static pre-configuration through OM.
3Adaptability or versatility
If multiple RNCs independently map MBMS services to S-CCPCHs, then service mapping flexibility is improved, but mapping consistency deteriorates
Solution Approach 1:
The master RNC generates the MBMS service to S-CCPCH mapping relationship and distributes this mapping information to all slave RNCs through configuration information messages. This feedback mechanism ensures that all RNCs use the same mapping relationship, maintaining consistency while allowing the master RNC to optimize the mapping based on network conditions.
4Reliability
If a master-slave RNC architecture is implemented, then configuration synchronization is improved, but network complexity deteriorates
Solution Approach 1:
The system merges the configuration management functions of all RNCs into a single master RNC. Instead of each RNC independently determining configuration information, the master RNC consolidates this responsibility and distributes configuration to slave RNCs. This merging reduces the overall network complexity by eliminating redundant configuration management while ensuring consistent synchronization across all RNCs.
Data Source
AI summary
In the field of mobile communication, a method, device, and system for configuring multicast broadcast single frequency network (MBSFN) resources are provided, so as to solve the problem that configuration information of each radio network controller (RNC) in an MBSFN cannot be dynamically synchronized. With the coordination of a master RNC, a multimedia broadcast multicast service (MBMS) configuration information message is transferred through IUR interface connection, and MBMS configuration information of the master RNC and each slave RNC is synchronized. In this way, the problem that configuration information of each RNC in an MBSFN cannot be dynamically synchronized is solved, thereby satisfying the demands of soft combing and air interface combining.