eMBMS MCCH Update Synchronization in Distributed MCE
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP standards do not completely support MCCH update signaling synchronization for distributed MCE architectures in eMBMS, leading to inefficiencies in network resource management and user experience during multimedia broadcasts.
Innovation Solution
A method is introduced to calculate and synchronize MCCH update times across eNBs in both standalone and distributed MCE architectures, ensuring that MCCH update signaling is synchronized by using parameters like 'Time of MBMS Data Transfer' and 'Time of MBMS Data Stop' in session requests, and employing MCCH modification periods to align data transmission and stop signals.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If distributed MCE architecture is used in eMBMS, then network flexibility and deployment ease are improved, but MCCH update signaling synchronization cannot be completely supported
Solution Approach 1:
The patent segments the synchronization function by introducing separate synchronization indication messages that carry timing information for MCCH updates. This allows the distributed MCE architecture to maintain synchronization by dividing the control functions across multiple eNBs while using standardized signaling mechanisms to coordinate updates, thus resolving the contradiction between deployment flexibility and synchronization reliability.
Solution Approach 2:
The patent introduces an intermediary synchronization mechanism where synchronization indication messages act as mediators between different eNBs in the distributed MCE architecture. These messages carry necessary timing and synchronization information, enabling coordinated MCCH updates across multiple eNBs without requiring a centralized controller, thus maintaining both architectural flexibility and synchronization reliability.
2Productivity
If MCCH update signaling is synchronized across all eNBs, then network resource management efficiency is improved, but complexity of coordination and timing alignment increases
Solution Approach 1:
The patent implements periodic MCCH update signaling with standardized timing relationships. By defining fixed periodic intervals and synchronization points for MCCH updates across all eNBs, the system achieves efficient resource management through regular, predictable updates while reducing coordination complexity by eliminating the need for complex real-time negotiation between eNBs.
Solution Approach 2:
The patent uses parameter changes in synchronization indication messages to control MCCH update timing. By encoding timing information and synchronization parameters in standardized message fields, the system enables efficient coordinated updates across eNBs while keeping implementation complexity manageable through well-defined parameter specifications rather than complex procedural coordination.
3Ease of operation
If MCCH update timing is aligned across multiple eNBs, then user experience during MBMS reception is improved, but precision requirements for timing alignment increase
Solution Approach 1:
The patent applies preliminary action by sending synchronization indication messages before actual MCCH updates occur. These advance notifications allow user equipment to prepare for upcoming updates and perform necessary timing adjustments, improving user experience through seamless transitions while reducing the precision burden on eNBs by providing a buffer period for synchronization alignment.
Solution Approach 2:
The patent ensures continuity of useful action by maintaining ongoing synchronization indication messaging between eNBs and to user equipment. This continuous exchange of timing information allows for gradual drift compensation and maintains aligned MCCH updates across the network over time, improving user experience without requiring extremely high initial timing precision.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The embodiments herein relates to a method in an eNB (401) for handling MBSFN area configuration information. The eNB (401) receives (501, 801), from a MME (410), a MBMS session start request. Based on the received request, the eNB (401) computes a first time for a start of the MBMS session. The first time is a first MCC, update time. The eNB periodically sends (504, 804), from the first time, the configuration information to a user equipment (405). The eNB (401) stops (507, 807) the sending of the configuration information to the user equipment (405) when the MBMS session is a last MBMS session. The eNB (401) sends (508, 808) updated configuration information to the user equipment (405) when the MBMS session is not the last MBMS session. The updated configuration information is updated MBSFN area configuration information.