DASH Content URL Authentication Using MPD Signature Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multimedia delivery technologies face challenges in ensuring accurate content delivery and authentication over HTTP-based streaming protocols, particularly in dynamic adaptive streaming over HTTP (DASH), where incorrect URL mappings can lead to unexpected data streams and compromised content integrity.
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 through HTTP or HTTPS, ensuring that only authorized users access intended content by generating and validating URL signatures based on media presentation description metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If HTTP-based streaming protocols are used for multimedia delivery, then ease of operation and deployment are improved, but content integrity and authentication are compromised due to incorrect URL mappings
Solution Approach 1:
The patent applies preliminary action by generating and attaching digital signatures to URL mappings in the Media Presentation Description (MPD) metadata before content delivery. These signatures are created in advance using the content owner's private key, allowing the client to verify URL authenticity before accessing media segments, thus preventing incorrect URL mappings while maintaining HTTP deployment simplicity
Solution Approach 2:
The patent introduces digital signatures as an intermediary mechanism between the content owner and the client. The signature acts as a trusted mediator that verifies the authenticity of URL mappings without requiring direct trust between the client and content delivery network, resolving the contradiction by enabling verification while maintaining HTTP-based delivery
2Reliability
If URL authentication mechanisms are implemented to ensure content integrity, then content protection is improved, but system complexity increases
Solution Approach 1:
The patent applies self-service by enabling the client to autonomously verify URL signatures using the content owner's public key without requiring complex authentication servers or manual verification processes. The client independently performs cryptographic verification of URL mappings, reducing system complexity while maintaining strong content protection
Solution Approach 2:
The patent replaces complex mechanical authentication systems with cryptographic digital signatures. Instead of requiring intricate access control mechanisms or manual URL verification, the system uses public key infrastructure to provide automated, mathematically secure verification, reducing system complexity while enhancing content protection
3Measurement precision
If digital signatures are generated for each URL mapping, then authentication accuracy is improved, but processing time and computational overhead increase
Solution Approach 1:
The patent applies partial action by generating digital signatures only for the URL mappings in the MPD metadata rather than for every individual media segment or the entire content stream. This selective signing approach maintains authentication accuracy for all content references while significantly reducing the total number of signature operations required, thus minimizing processing time overhead
Data Source
Figure 1
Figure 2
Figure 3
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.