MBMS Carrier Allocation for LTE-A Data Loss Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In LTE-A wireless communication systems, data loss occurs when UEs enabled for carrier aggregation receive multimedia broadcast multicast service (MBMS) allocations on extension carriers, and there are challenges in managing resources for UEs of different system versions, leading to issues with unicast data transmission and reception.
Innovation Solution
Enabling multiple component carriers for MBMS transmission and reception, applying MBSFN allocation on a first enabled carrier, and configuring component carriers to support both MBMS and unicast data exchange, while allowing simultaneous communication with UEs of varying system versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MBSFN allocation is applied on extension carrier, then MBMS service reception is enabled, but unicast data transmission is blocked causing data loss
Solution Approach 1:
The patent segments the component carriers into different functional roles: extension carriers are dedicated to MBMS services with MBSFN allocation, while anchor carriers handle unicast data transmission. This segmentation allows the UE to receive MBMS services on extension carriers without blocking unicast data, as the unicast data is transmitted on anchor carriers where MBSFN allocation does not apply.
Solution Approach 2:
The patent introduces anchor carriers as intermediary components that mediate between MBMS service reception and unicast data transmission. The anchor carriers provide a dedicated pathway for unicast data, ensuring that MBMS activities on extension carriers do not interfere with unicast communication reliability.
2Device complexity
If single carrier MBMS allocation is used, then system complexity is reduced, but data loss occurs in carrier aggregation scenarios
Solution Approach 1:
The patent applies local quality by making MBSFN allocation carrier-specific rather than system-wide. The network configures MBSFN allocation parameters individually for each component carrier, allowing extension carriers to have MBSFN allocation for MBMS services while anchor carriers maintain normal unicast transmission without MBSFN allocation. This localized approach prevents data loss in carrier aggregation scenarios without unnecessarily increasing overall system complexity.
3Area of stationary object
If extension carrier is used for MBMS, then MBMS service coverage is improved, but unicast data access is blocked
Solution Approach 1:
The patent segments carrier functions to resolve the conflict between MBMS coverage and unicast access. Extension carriers are dedicated to MBMS services, providing enhanced MBMS coverage, while anchor carriers are reserved for unicast data transmission, ensuring continuous unicast access. The UE is configured to monitor both carrier types, allowing simultaneous MBMS reception and unicast communication without interference.
4Productivity
If MBSFN allocation is applied on all component carriers, then MBMS service is maximized, but unicast data transmission is interrupted
Solution Approach 1:
The patent implements local quality by applying MBSFN allocation selectively only on extension carriers rather than uniformly on all component carriers. This allows MBMS service to be maximized on extension carriers where it is needed, while anchor carriers maintain normal unicast transmission patterns without MBSFN allocation, preventing unicast data transmission interruptions. The network configures each carrier's MBSFN parameters based on its specific role in the carrier aggregation setup.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of handling multimedia broadcast and multicast service (MBMS) transmission and reception for a mobile device in a wireless communication system is disclosed. The method includes enabling a plurality of component carriers, and applying a multi-media broadcast over a single frequency network (MBSFN) allocation on a first enabled component carrier and not on the rest of the enabled component carriers when the mobile device receives the MBSFN allocation on the first enabled component carrier.