Hosted DRM Library APIs for Stateless Media Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing digital rights management (DRM) systems require direct communication between client and server modules, often relying on underlying communication schemes and persisting databases, which complicates integration and media delivery in existing ecosystems.

Innovation Solution

The implementation of a DRM system that allows for integration without replicating underlying communication schemes and does not require a persistent database on the server, using client and server library components to provide DRM services through APIs, enabling proactive license issuance and content key derivation for secure media playback.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If DRM systems use direct client-server communication with persistent databases, then DRM functionality is achieved, but system complexity and integration difficulty increase

Engineering Contradiction:
ImproveDRM functionalityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the persistent database requirement from the server component, allowing the server to operate statelessly. The database persistence function is removed from the server, simplifying its architecture while maintaining DRM functionality through transient in-memory state management.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The DRM library is designed to work within existing communication schemes and ecosystems, making it universal rather than requiring proprietary communication protocols. This allows the DRM system to integrate with various hosting applications and communication infrastructures without replication.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If DRM systems replicate underlying communication schemes, then DRM security is maintained, but integration ease decreases

Engineering Contradiction:
ImproveDRM securityVSAvoidintegration ease
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The DRM library acts as an intermediary layer that works within existing communication schemes without requiring them to be replicated. It mediates between the hosting application's communication infrastructure and the DRM functionality, maintaining security while adapting to various ecosystems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The DRM system is segmented into a standalone library component that can be integrated into different hosting applications. This modular approach allows the DRM functionality to be separated from the communication scheme replication, enabling integration into existing ecosystems while maintaining security.

Inventive Principle:
Principle #1Segmentation

3Reliability

If servers persist databases for DRM transactions, then transaction state is maintained, but resource consumption increases

Engineering Contradiction:
Improvetransaction state maintenanceVSAvoidserver resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent removes the persistent database requirement from the server, extracting this function entirely. The server operates without persistent storage for DRM transactions, reducing resource consumption while maintaining transaction state through in-memory mechanisms and client-side license storage.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The server uses transient in-memory state instead of persistent database storage, treating transaction state as temporary and disposable. This approach reduces server resource requirements while maintaining functionality through client-side license persistence and serverless state management.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS10162944B2Library style media DRM APIs in a hosted architecture
Publication Date: 2018.12.25 BISON PATENT LICENSING LLC
  • US10162944B2 patent drawing
  • US10162944B2 patent drawing
  • US10162944B2 patent drawing

AI summary

Systems and methods are provided for digital rights management of licensed media content. Client library components and server library components provide digital rights management services. A client-side hosting application accesses client library functionality through invocation of client application programming interfaces (APIs). A server-side hosting application accesses server library functionality through invocation of server APIs. Licenses for specific media content can be requested and issued, and appropriately licensed media content can be played. Client and server library components can function essentially absent direct communication, such as that employing a transport layer. Communications between client and server library components can be carried by the hosting applications.