ISO Base Media File Format Message Box for Secure Asynchronous Event Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current adaptive streaming technologies, such as DASH, face issues with handling asynchronous events like advertisements and emergency messaging, leading to network congestion, scalability limitations, and security vulnerabilities due to frequent MPD reloads and lack of event type differentiation.
Innovation Solution
The proposed solution extends the 'mesg' box in the ISO file format with uniform encryption, scheduling, and argument interfaces, enabling rich REST APIs and secure event handling without explicit client knowledge of message types or schemes, allowing for generic asynchronous stream event handling and enhanced security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If frequent MPD reloads are performed to handle asynchronous events, then event responsiveness is improved, but network congestion increases
Solution Approach 1:
The patent embeds event notification messages directly within media segment files, allowing clients to receive event information proactively during normal media playback without needing to initiate separate MPD reload requests. This preliminary embedding of event data eliminates the need for frequent reactive MPD reloads, thus maintaining event responsiveness while preventing network congestion.
Solution Approach 2:
The patent introduces an event notification message structure that acts as an intermediary between the media content and the client application. This message structure, embedded in segment files, carries event information and triggers client-side event handling without requiring direct client-server communication for each event, thereby reducing network traffic while maintaining responsive event handling.
2Device complexity
If generic event handling is implemented without event type differentiation, then system complexity is reduced, but handling precision deteriorates
Solution Approach 1:
The patent introduces an event type field within the notification message structure that provides local differentiation for different event types (e.g., advertisement events, content events, emergency alerts). This allows the system to maintain a generic overall architecture while enabling precise, type-specific event handling through localized identification within the message structure, thus resolving the contradiction between simplicity and precision.
3Power
If client-side event handling is implemented, then server processing load is reduced, but client processing complexity increases
Solution Approach 1:
The patent extracts event handling logic from the server side and embeds it directly in the media segment files as notification messages. Clients simply need to parse these embedded messages and execute predefined event handling actions, which significantly reduces server processing load while keeping client complexity minimal through straightforward message parsing and action execution.
4Adaptability or versatility
If standard ISO file format is used without extensions, then compatibility is improved, but functionality deteriorates
Solution Approach 1:
The patent nests event notification messages within the existing ISO base media file format structure by embedding them in segment files. This nested approach allows the system to maintain full compatibility with standard ISO file formats and existing playback infrastructure while adding rich event handling functionality through the embedded message structure, thus resolving the contradiction between compatibility and functionality.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
System and method embodiments are provided for asynchronous event notification and message handling in dynamic adaptive streaming over hypertext transfer protocol (DASH). The embodiments includes sending in a segment file, from a network server to a client, a message box that is configurable for encryption, for scheduling a callback from the client, and with one or more arguments according to a messaging scheme of the message box. The network server further sends a message handling descriptor to the client for reloading a media presentation description (MPD) for obtaining a DASH event. The client then configures a universal resource locator (URL) for the MPD using the message box and the message handling descriptor, and sends the URL back to the network server. After receiving the URL, the network server sends the MPD to the client, which then uses the MPD to request segments of an asynchronous event.