DRM Concurrency Validation for OTT Streaming Data Segments

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing streaming video delivery systems lack robust digital rights management (DRM) protection, allowing unauthorized access when DRM keys are intercepted and shared, as validation of user devices occurs only before providing the manifest, enabling piracy and unauthorized viewing.

Innovation Solution

Implement a concurrency service to validate user device requests and DRM requests, using one-time use URLs and multiple checks to ensure authorized access, including a manifest generator, concurrency service, and DRM service to manage and validate user device credentials and access policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If DRM keys are provided to user devices for decrypting data segments, then authorized users can access streaming video, but intercepted DRM keys enable unauthorized users to gain access

Engineering Contradiction:

ImproveDRM protectionVSAvoidunauthorized access

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system segments the video content into multiple data segments and provides different encryption keys for different segments. Each DRM request is validated independently against the original streaming request, creating segmented protection points throughout the playback process rather than a single point of vulnerability

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary validation by comparing DRM request parameters against the stored streaming request parameters before providing decryption keys. This preliminary check prevents unauthorized users from successfully requesting DRM keys even if they intercept communication, as their requests will not match the validated parameters

Inventive Principle:

Principle #10Preliminary action

2Ease of operation

If validation of user device occurs before providing manifest, then initial access control is established, but subsequent DRM requests can be intercepted and shared

Engineering Contradiction:

Improveaccess controlVSAvoidpiracy prevention

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The validation process continues throughout the streaming session rather than occurring only once at the beginning. Each DRM request triggers a validation check against the original streaming request, maintaining continuous protection throughout the playback process and preventing piracy attempts at any point

Inventive Principle:

Principle #20Continuity of useful action

3Loss of information

If DRM requests include identifiers for user device and data segments, then key distribution can be tracked, but validation complexity increases

Engineering Contradiction:

Improverequest trackingVSAvoidvalidation process

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The system creates a copy of the validated streaming request parameters and stores them for comparison against subsequent DRM requests. This copying approach enables tracking and validation without requiring complex real-time analysis, as the pre-stored parameters serve as a simple reference for comparison

Inventive Principle:

Principle #26Copying

Data Source

PatentUS20250328606A1DRM and ott data and streaming concurrency validation

Publication Date: 2025.10.23 DISH NETWORK TECHNOLOGIES INDIA PTE LTD

AI summary

A method may include receiving a request for streaming video data from a user device. The request may include an identifier associated with the user device. The method may include validating the request. The method may include storing the identifier associated with the user device, and/or a property associated with the request. The method may include transmitting a playlist to the user device, identifying one or more data segments. The method may include receiving a DRM request. The DRM request may include the identifier associated with the user device and an identifier corresponding to a first data segment of the playlist. The method may include validating the DRM request. The method may include providing a key to the user device such that the user device may decrypt the first data segment.