DASH Content URL Authentication via Digital Signatures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Dynamic Adaptive Streaming over HTTP (DASH) systems face challenges in ensuring content integrity and authenticity, particularly in wireless communication networks, where incorrect URL mappings can lead to unintended data streams, affecting user experience and content delivery accuracy.
Innovation Solution
The implementation of a content URL authentication framework using digital signatures and digests within the DASH standard, which allows clients to verify the origin and authenticity of media segments, ensuring that only intended content is delivered by binding URLs to their respective content sources through validation keys and authentication mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If DASH systems use standard HTTP streaming without URL authentication, then ease of operation and system simplicity are maintained, but content integrity and delivery accuracy deteriorate due to incorrect URL mappings
Solution Approach 1:
The patent applies preliminary action by embedding authentication data (signatures and digests) into the Media Presentation Description (MPD) metadata before content delivery. The client device verifies URL authenticity by checking these pre-provided authentication elements against the requested media segments, preventing incorrect URL mappings before they can cause content integrity issues.
Solution Approach 2:
The patent introduces an intermediary authentication mechanism that acts as a mediator between the content delivery system and the client. The authentication framework uses signatures and digests as intermediary elements to verify URL validity, creating a trust layer that ensures content integrity without requiring complex end-to-end encryption or manual verification.
2Reliability
If DASH systems implement URL authentication mechanisms, then content authenticity is improved, but processing time and system complexity increase
Solution Approach 1:
Authentication data is prepared in advance and embedded in the MPD metadata, allowing clients to verify URL authenticity without real-time computational overhead. The signatures and digests are pre-calculated by the server, shifting the computational burden from the client device to the server side and minimizing authentication processing time during content delivery.
3Object-affected harmful factors
If no authentication framework is used, then system simplicity is maintained, but susceptibility to network intrusions and content theft increases
Solution Approach 1:
The authentication framework introduces signatures and digests as intermediary verification elements between the content source and the client. These intermediaries provide cryptographic proof of content authenticity and URL validity, protecting against network intrusions and content theft while maintaining a relatively simple implementation based on standard cryptographic functions.
Solution Approach 2:
The client device performs self-verification of content authenticity by checking the signatures and digests provided in the MPD metadata against the requested media segments. This self-service authentication mechanism enables each client to independently verify content integrity without requiring continuous server validation, reducing network overhead and improving security.
Data Source
AI summary
Technology for content uniform resource locator (URL) authentication for dynamic adaptive streaming over hypertext transfer protocol (HTTP) (DASH) is disclosed. In an example, a client device can include computer circuitry configured to: Receive a URL authentication key indicator and a content URL signature indicator from a server; generate a calculated URL signature for a URL in a DASH media presentation description (MPD) from the URL authentication key indicator; request the DASH segment when the calculated URL signature matches the received content URL signature, thereby authenticating content URL; and receive a DASH segment using the authenticated content URL. The received content URL signature is derived at the server from the content URL contained within the DASH segment URL.