A standard data packaging and distribution schema for interactive narrative content

Abstract

This invention discloses a standard data encapsulation and distribution format for interactive narrative content. This format includes: a standardized branch topology metadata data structure, physically separated from media material files, containing node identifiers, trigger conditions, and material reference hash values; a standardized dynamic authorization communication protocol for defining the interaction between the player and the server to achieve the distribution of encrypted metadata subsets according to authorization status; and the material distribution part is compatible with the HLS / DASH standard streaming media protocol. This format provides a unified interconnection architecture and distribution method for interactive narrative content, and supports authorization transaction records based on distributed ledgers, serving as a reference implementation scheme in the field of interactive content distribution.

Description

Technical Field

[0001] This invention belongs to the field of data encapsulation and communication protocol technology, specifically relating to a standard data encapsulation format and dynamic authorization communication protocol for interactive narrative content that is cross-platform interoperable. Background Technology

[0002] Currently, interactive narrative content (such as interactive movies, VR narrative games, and branching stories) is in a period of rapid development, but the industry lacks a unified standard format. Different platforms (such as Netflix, Bilibili, and Tencent Video) use their own proprietary formats for storing and distributing branching logic, resulting in content that cannot be shared across platforms. Creators need to repeatedly create content for different platforms, which greatly wastes creative resources.

[0003] Furthermore, the lack of a unified dynamic licensing protocol in existing data encapsulation formats hinders the efficient, standardized, and automated paid distribution and commercialization of interactive narrative content. Therefore, there is an urgent need for a standard data format and communication protocol that can define interactive narrative content to achieve interoperability and secure distribution. Summary of the Invention

[0004] To overcome the above-mentioned shortcomings, this invention proposes a technical standard for interactive narrative content, the core of which is: A standard data encapsulation and distribution format for interactive narrative content, characterized by comprising: • Standardized branch topology metadata data structure: Physically separated from media source files, it defines a set of encapsulation formats independent of physical frame carrying, including unique node identifiers, node types, parent and child node indices, branch triggering conditions, and reference hash values ​​pointing to source files.

[0005] • Standardized dynamic authorization communication protocol: used to define the standard interaction method between the player and the distribution server, so as to dynamically distribute a subset of encrypted metadata that matches the user's permissions and conforms to the above standard format based on the user permission verification status.

[0006] • Compatibility with existing streaming protocols: The media distribution portion of the format is compatible with existing streaming protocols such as HLS / DASH.

[0007] The beneficial effects of this invention are: 1. A unified data structure for interactive narrative content is defined to enable cross-platform interoperability and reduce costs for creators.

[0008] 2. A standardized dynamic authorization communication protocol is defined to enable mutually trusted and standardized content distribution and monetization.

[0009] 3. It is compatible with existing streaming media protocols, reducing the cost of technology migration and implementation. (iv) Description of the attached drawings Figure 1 : Data structure definition diagram of standard branch topology meta data packets; Figure 2 : Interaction flowchart of the standard dynamic authorization communication protocol; Figure 3 : Compatibility architecture diagram between the standard and existing streaming media protocols; Figure 4 Flowchart of authorized transactions and automatic ledger sharing based on distributed ledger. (V) Detailed Implementation Methods Example 1: Data structure definition of standard branch topology meta data packets This standard defines a standard, media-independent branch topology metadata data packet format. This data packet is a lightweight, independent data file, physically separate from the source files, and its core data structure is defined as follows: 1. Self-describing metadata header: Located in the packet header, it contains information describing the standard itself, and includes at least: 2. Standard version number: Identifies the version of this standard, facilitating future evolution and compatibility assessment.

[0010] 3. Standard Identifier: A unique identifier for this standard worldwide.

[0011] 4. Compatibility List: Lists the streaming media protocols (such as HLS, DASH) that this data packet is compatible with.

[0012] 5. Encryption Algorithm: Identifies the algorithm used to encrypt the data packet (e.g., AES-256-GCM).

[0013] 6. Signature Algorithm: Identifies the digital signature algorithm used to verify the integrity of data packets (such as ECDSA-P256).

[0014] 7. Content Data: The main body of the data packet, containing a list of nodes. Each node must contain at least the following core attributes: 8. Node Identifier: The unique ID of this node within the entire narrative structure.

[0015] 9. Node type: Identifies whether the node is a main node, a branch node, or another type.

[0016] 10. Spatial coordinates: The location information of this node in three-dimensional space (such as x, y, z coordinates).

[0017] 11. Material Reference Hash Value: A reference to the specific material file (such as video or audio) associated with this node. This reference is generated based on the SHA-256 hash algorithm.

[0018] 12. Triggering condition: A logical expression used to define the conditions for entering this node from its parent node.

[0019] 13. Optional extended fields: These are used to support future feature expansions, such as multimodal sensory data fields, AI agent call interface definitions, and external metadata fields related to blockchain records.

[0020] Example 2: Definition of Standard Dynamic Authorization Communication Protocol This standard defines a set of standard interaction protocols, and all players conforming to this standard must follow the following request / response process with the distribution server: 1. Standard Authorization Request Format: The player sends an HTTPS POST request to the server at the URL / api / v1 / authorize. The request body must contain a standard JSON object, which must include at least: the user's identity identifier, the project ID, and the player's unique fingerprint information.

[0021] 2. Standard Authorization Response Format (Success): After successful server verification, an HTTP 200 OK status code is returned. The response body contains a standard JSON object, which includes at least: the authorization status (approved), a list of authorized branch node IDs, an encrypted subset of branch topology metadata (base64 encoded), and a dynamic session key for decrypting this subset.

[0022] 3. Standard Authorization Response Format (Failure): Server verification fails, returning an HTTP 403 Forbidden status code. The response body contains a standard JSON object, which includes at least: the authorization status (denied), a list of branch nodes that the user can unlock, and their corresponding prices.

[0023] Example 3: Compatibility with existing streaming media protocols The media distribution portion of this standard is designed to be backward compatible with existing mainstream streaming media protocols such as HLS / DASH. The implementation of a standard-compatible player includes the following steps: 1. Obtaining Metadata References: The player obtains the reference URL of the branch topology metadata data package from a standard HLS / DASH manifest file (such as M3U8 or MPD) through a preset extended tag or field.

[0024] 2. Download and parse metadata: The player downloads the corresponding metadata based on the obtained URL and parses its content.

[0025] 3. Integrity Verification: The player performs integrity verification on the downloaded metadata to ensure that it has not been tampered with during transmission.

[0026] 4. Streaming playback: After successful verification, the player can load and play the media streams referenced in the playlist file.

[0027] Example 4: Authorization Records and Automatic Revenue Sharing Method Based on Distributed Ledger This standard further expands its standard authorized communication protocol, providing a foundational standard for the future decentralized economy. The specific process is as follows: 1. Generate an authorization transaction record: The player sends an authorization request to the cloud; after the cloud verifies the request, it generates an "authorization transaction record" containing the user ID, project ID, branch node ID, timestamp, and authorization price (optional).

[0028] 2. Hash Calculation and Broadcasting: The cloud broadcasts the hash value of the transaction record to a blockchain network that conforms to this standard.

[0029] 3. Consensus Confirmation: Distributed nodes in the blockchain network complete consensus confirmation and generate an immutable transaction ID.

[0030] 4. Credential Return: The transaction ID is written as metadata into the dynamic session key or response body of the authorization response and returned to the player.

[0031] 5. Automated Revenue Sharing: Revenue sharing for this authorization (e.g., among creators, the platform, and the agent) can be automatically executed based on on-chain records, without the need for third-party arbitration. Each authorization operation generates a verifiable and traceable unique hash certificate on the blockchain.

[0032] (vi) Software Environment and Feasibility Statement It should be noted that all the functions of this invention can be implemented in general, existing computer software and hardware environments, without relying on any specific or proprietary operating system, framework or middleware.

[0033] Those skilled in the art, such as an engineer with more than 5 years of software development experience, after reading this specification, will be able to implement a standardized player and distribution server conforming to this standard based on the JSON Schema definition, communication protocol and interaction process disclosed in this invention, using existing mature programming languages ​​(such as Python, JavaScript, Java or C++) and general frameworks (such as Node.js, Flask, Spring Boot), without any creative effort.

[0034] The standard data structures and communication protocols defined in this manual are fully provided, and their engineering implementation can be achieved by combining them with conventional computer technology.

Claims

1. A standard data encapsulation and distribution format for interactive narrative content, characterized in that, include: • A standardized branch topology metadata data structure, physically separated from the media source file, the data structure including at least: a unique node identifier, node type, parent and child node indexes, branch triggering conditions, and a reference hash value pointing to the source file; • A standardized dynamic authorization communication protocol is used to define a two-way interaction method between the player and the distribution server. The method includes: the player sending an identity verification request to the server, and the server dynamically sending a subset of encrypted metadata that conforms to the above standard format based on the user's permission verification status. • A media distribution scheme compatible with existing streaming media protocols, wherein the media distribution portion of the standard format can be carried within the existing HLS / DASH protocol.

2. The standard according to claim 1, characterized in that, The standardized dynamic authorization communication protocol is implemented based on HTTPS / RESTful API and defines a set of standardized request / response message formats.

3. The standard according to claim 1, characterized in that, The standardized branch topology metadata data structure is compatible with multimodal sensory data extensions, including but not limited to tactile feedback data, olfactory data, and balance data.

4. The standard according to claim 1, characterized in that, The standardized branch topology metadata data package has a data structure compatible with AI agent discovery and invocation, including additional metadata field definitions and authorization information.

5. The standard according to claim 1, characterized in that, The standardized branch topology metadata is verified for integrity using a Merkle tree structure to ensure that its content is not tampered with during transmission.

6. The standard according to claim 1, characterized in that, The standardized dynamic authorization communication protocol enables player devices to play content offline based on authorization tokens and a subset of encrypted metadata cached in local secure storage.

7. The standard according to claim 1, characterized in that, The standardized dynamic authorization communication protocol also includes an authorization transaction record module based on a distributed ledger, which generates a verifiable and traceable unique hash certificate for each authorization operation and stores it in the blockchain network.

8. The standard according to claim 1, characterized in that, The standardized branch topology metadata data package includes a standard "AI agent discovery and invocation interface" definition. This interface defines the methods and data structures for external AI agents to discover, query, and invoke the metadata, price lists, and content summaries of specific branch nodes through a standardized API without explicit user intervention.

9. The standard according to claim 1, characterized in that, The standardized dynamic authorization communication protocol is further configured to support authorization verification based on decentralized identity (DID). In the authorization request, the user identity identifier can be a distributed identity identifier conforming to the W3C DID specification. The server verifies the user's identity by verifying the signature of this DID, without relying on a centralized account system.

10. The standard according to claim 1, characterized in that, The encryption algorithm field of the data structure of the standardized branch topology metadata packet is configured to support post-quantum cryptography (PQC) algorithms. When the standard evolves to the PQC era, the header field of the packet can directly indicate the post-quantum algorithm used for encryption and signing, ensuring the security of the standard in the quantum computing era.

Images