FLUTE FDT Delivery via OMA Push for Roaming MBMS Clients
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multimedia broadcast multicast services (MBMS) face challenges in seamless handover between broadcast/multicast and unicast modes, particularly in areas without MBMS coverage, where unicast delivery is required, and there is a lack of standardized signaling for efficient content distribution using unicast bearers.
Innovation Solution
The proposed solution involves delivering the FLUTE File Delivery Table (FDT) via an OMA Push message, allowing MBMS UEs to request files using various HTTP GET request formats, including single, pipelined, and serialized requests, and enabling the serviceID to be delivered separately in the OMA Push message, reducing network resource wastage and improving flexibility and efficiency in unicast file retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If unicast delivery is used for MBMS content distribution in areas without MBMS coverage, then service availability is improved, but network resource efficiency deteriorates
Solution Approach 1:
The patent segments the file delivery process into multiple individual HTTP GET requests, allowing the UE to request only specific files or portions of content rather than receiving complete files. This segmentation enables more efficient use of unicast bearers by reducing unnecessary data transmission while maintaining service availability in areas without MBMS coverage.
2Adaptability or versatility
If multiple individual HTTP GET requests are made for file retrieval, then file selection flexibility is improved, but signaling overhead increases
Solution Approach 1:
The patent merges multiple file requests into a single HTTP GET request by utilizing the FLUTE FDT structure. The FDT contains information about multiple files and their groupings, allowing the UE to request multiple files or logical groups of files in one signaling operation, thereby reducing signaling overhead while maintaining file selection flexibility.
Solution Approach 2:
The patent performs preliminary action by delivering the FLUTE FDT (File Delivery Table) in advance via OMA Push message. The FDT contains pre-organized information about available files, their groupings, and metadata. This preliminary delivery of file information allows subsequent HTTP GET requests to be more efficient, as the UE already has the necessary file descriptors and can make informed selection decisions without additional signaling overhead.
3Loss of information
If serviceID is included in FLUTE FDT, then file delivery information is improved, but network resource wastage increases
Solution Approach 1:
The patent extracts the serviceID from the FLUTE FDT and delivers it separately through the OMA Push message mechanism. This separation allows the FDT to contain only the essential file delivery information needed for content retrieval, while the serviceID is transmitted through a more efficient channel. This extraction reduces network resource wastage by avoiding redundant transmission of service identification data that can be obtained through OMA Push signaling.
4Reliability
If seamless handover between broadcast/multicast and unicast modes is implemented, then service continuity is improved, but system complexity increases
Solution Approach 1:
The patent introduces the OMA Push message as an intermediary mechanism that bridges broadcast/multicast and unicast delivery modes. The OMA Push delivers the FLUTE FDT and serviceID information that enables the UE to seamlessly transition from broadcast/multicast to unicast mode. This intermediary approach simplifies the handover process by providing a standardized signaling mechanism that carries all necessary information for mode transition, reducing system complexity while maintaining service continuity.
Data Source
AI summary
A system and method for providing MBMS content distribution using unicast bearers. According to various embodiments, MBMS download user services are delivered to pieces of user equipment by delivering a FLUTE file delivery table via an OMA Push message. One of a number of different additional actions may be used in the delivery of the MBMS download user services. These actions include (1) making a single HTTP GET request using simple URL-encoding format to retrieve all files of the FDT; (2) making a single HTTP GET request using “group” field of FDT in URL-encoding to retrieve a logical group of files of the FDT; (3) making pipelined HTTP GET requests where each HTTP GET request retrieves at least one file of the FDT; (4) making serialized HTTP GET requests where each HTTP GET request retrieves at least one file of the FDT; (5) making pipelined HTTP GET requests where each HTTP GET request retrieves at least one logical group of files of the FDT; (6) making serialized HTTP GET requests where each HTTP GET request retrieves at least one logical group of files of the FDT; (7) delivering the serviceID of the MBMS user service in the above mentioned OMA PUSH message but not including the serviceID in the FLUTE FDT; (8) an HTTP request to de-register the MBMS UE from the BM-SC for stopping the unicast delivery of the MBMS download user service; and (9) delivering the FDT Instance ID of the FDT Instance in an OMA Push message.