Manifest File Muxing With Blockchain Media Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing digital service providers lack an efficient mechanism to store encrypted multiplexed media streams as manifest files for easy access and validate their authenticity, and there is a need for a comprehensive system to verify the legitimacy of media streams and locate rightful owners.
Innovation Solution
A system and method for muxing and storing a manifest file in a storage server using a blockchain platform, such as Ethereum, which embeds metadata including codec parameters to determine stream authenticity and origin, and uses a muxer to multiplex livestream data with embedded metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If digital service providers use traditional storage methods for media streams, then storage simplicity is maintained, but authentication capability and media legitimacy verification are insufficient
Solution Approach 1:
The patent introduces a blockchain as an intermediary layer between traditional storage systems and authentication requirements. The blockchain serves as a mediator that stores hashed manifest files and metadata, enabling authentication without requiring complex verification systems in the traditional storage architecture. This intermediary approach allows simple storage while adding powerful authentication capabilities through the blockchain's immutable ledger.
Solution Approach 2:
The patent replaces traditional mechanical storage and verification mechanisms with a blockchain-based cryptographic system. Instead of using complex access control lists, digital signatures, and centralized authentication servers, the system uses blockchain's inherent cryptographic hashing and chaining mechanisms to provide authentication. This substitution simplifies the overall system architecture while enhancing reliability.
2Reliability
If comprehensive database of media is maintained for tracking and verification, then media legitimacy verification improves, but system complexity and data management burden increase
Solution Approach 1:
The patent extracts only the essential authentication information from comprehensive media databases and stores it in the blockchain. Instead of maintaining complete media metadata and tracking information in complex databases, the system extracts and stores only the critical authentication data (hashed manifest files, ownership information, and verification metadata) in the blockchain. This extraction approach reduces data management complexity while preserving verification capability.
Solution Approach 2:
The patent creates cryptographic copies of media authentication data in the blockchain rather than maintaining original comprehensive databases. The blockchain stores hashed versions of manifest files and key metadata, creating immutable copies that can be verified without requiring access to or management of the complete original media databases. This copying approach simplifies data management while enabling comprehensive verification.
3Ease of operation
If encrypted multiplexed media streams are stored for easy access, then media accessibility improves, but authentication and origin tracking capabilities are lost
Solution Approach 1:
The patent performs preliminary authentication actions by storing hashed manifest files and metadata in the blockchain before media access is required. The blockchain pre-contains the authentication data needed to verify media legitimacy, so when media is accessed, the verification process is rapid and straightforward. This preliminary action approach enables both easy access and strong authentication without requiring complex verification at access time.
Data Source
AI summary
The disclosed system (110) and method (500) enables muxing and storing a manifest file in a storage server (122). The method (500) includes receiving (502) one or more input streams from at least one streaming service. The input streams are received by an authorization unit communicatively coupled to a streaming server. The received one or more input streams are encoded (504) by an encoder using one or more predefined codec configurations to generate corresponding one or more encoded streams. The generated one or more encoded streams are multiplexed (506) by a muxer into at least one muxing. The muxing includes livestream data and embedded metadata. Further, at least one of the muxing and one or more input/output (I/O) services are linked (508) into a manifest file that is stored in a storage server.