FLUTE Notification Transport via FDT Extension
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing method for transporting notification messages in mobile video broadcasting systems using the BCAST protocol is complex and unreliable due to the need for terminals to access both UDP and FLUTE protocols, leading to slow message retrieval and unreliable data transfer.
Innovation Solution
A method is introduced to transport notification messages via the FLUTE protocol by pre-adding a Notification type in the Content-Type attribute of the FDT and carrying notification related information in a Notifi element, allowing the server to send notification content and related information in a FLUTE session, which the terminal can receive directly, leveraging FLUTE's forward error correction for reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If notification messages are transported using the BCAST protocol requiring access to both UDP and FLUTE protocols, then notification delivery can be achieved, but the transport procedure becomes complex and message retrieval becomes slow
Solution Approach 1:
The patent merges the notification message transport entirely within the FLUTE protocol by extending the FDT structure. Instead of using separate UDP and FLUTE protocols as in the prior art, the notification messages are packaged as transport objects with TOI values and described in the FDT, allowing the terminal to receive all notification components through a single FLUTE session access.
Solution Approach 2:
The FDT structure is extended to serve multiple functions: it continues to describe regular transport objects while also describing notification transport objects. The Notification element in the FDT can describe both the notification message itself and associated transport objects, making the FDT a universal description mechanism for both types of content.
2Reliability
If notification messages are transported using the BCAST protocol requiring access to both UDP and FLUTE protocols, then notification delivery can be achieved, but message retrieval becomes slow
Solution Approach 1:
The notification message components are prepared and packaged in advance as transport objects with assigned TOI values before the FLUTE session begins. The FDT is pre-configured with Notification elements that contain all necessary information about the notification transport objects, allowing the terminal to immediately identify and retrieve notification messages upon accessing the FLUTE session without delays from protocol switching.
3Productivity
If notification messages are transported using UDP protocol, then message transmission can be achieved, but data transfer reliability becomes unreliable
Solution Approach 1:
The FLUTE protocol acts as an intermediary between the notification message source and the terminal. Instead of using unreliable UDP directly for notification transport, the notification messages are encapsulated as transport objects within the FLUTE framework, which provides reliable unidirectional transfer with forward error correction capabilities, thereby ensuring data integrity while maintaining transmission efficiency.
Data Source
Figure 1~2
Figure 3~5
Figure 6
AI summary
A method for transporting/receiving notification messages via File Delivery over Unidirectional Transport (FLUTE) includes: At the transmitting end, a server carries a notification content in a transport object and carries notification related information and a transport object identifier (TOI) of the transport object carrying the notification content in a first file description table (FDT), and then sends the first FDT and the transport object carrying the notification content in a FLUTE session; the receiving end obtains the notification related information and the TOI of the transport object charring the notification content from the first FDT, and receives the transport object charring the notification content according to the obtained related information and the TOI. A server for transporting notification messages via FLUTE, a FLUTE server, a content server and a terminal are also disclosed. With the present invention, the notification transport procedure is simpler and the reliability of notification transport is better.