Downloadable DRM Plug-in for Android Secure Video Rendering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Digital Rights Management (DRM) solutions for Android devices are inefficient in securing and rendering premium HD content, requiring hardware-based Trusted Execution Environments and Protected Video Paths, but are costly and time-consuming for DRM vendors due to chip-specific implementations and OEM integrations.
Innovation Solution
A downloadable Trustonic DRM Plug-in and Protected Video Path (PVP) system based on the Android 4.3 Framework, allowing DRM vendors to use standard APIs for secure video rendering, with components like Media Codec, Media Crypto, and Media DRM interfaces, enabling decryption and rendering of encrypted content using Trustonic TEE framework.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hardware-based Trusted Execution Environments and Protected Video Paths are implemented, then security for HD content is improved, but device complexity and integration costs increase
Solution Approach 1:
The patent introduces an intermediary layer (DRM plugin and PVP interface) that sits between the standard Android API and the hardware-based TEE/PVP components. This intermediary translates standard DRM operations into hardware-specific operations, allowing security to be enhanced without requiring applications or higher-level systems to deal with hardware complexity directly.
Solution Approach 2:
The patent creates a universal interface layer that works across different hardware implementations. The DRM plugin and PVP interface are designed to be platform-agnostic, allowing the same software stack to work with various hardware configurations from different manufacturers, thereby reducing integration complexity while maintaining security.
2Reliability
If chip-specific implementations of t-play API are used, then secure codec functionality is achieved, but DRM vendor integration time and costs increase
Solution Approach 1:
The DRM plugin acts as an intermediary that handles chip-specific variations. Instead of each DRM vendor needing to integrate with every chip manufacturer's specific t-play API implementation, the plugin provides a standardized interface that translates vendor-specific requirements into hardware-specific operations, dramatically reducing integration time.
Solution Approach 2:
The patent segments the DRM implementation into distinct layers: the hardware-specific PVP/TEE layer, the chip-specific t-play API layer, and the vendor-agnostic DRM plugin layer. This segmentation allows each layer to be developed and tested independently, reducing the overall integration complexity and time for DRM vendors.
3Ease of manufacture
If downloadable DRM components are implemented, then ease of deployment is improved, but system complexity increases
Solution Approach 1:
The downloadable DRM plugin serves as an intermediary that can be independently distributed and installed. It provides the necessary translation layer between standard Android DRM APIs and hardware-specific implementations, allowing deployment without requiring complex system-wide modifications or hardware changes.
Solution Approach 2:
The system enables self-service deployment through downloadable DRM components. Devices can automatically download and install the appropriate DRM plugin based on their hardware capabilities, without requiring manual configuration or complex installation procedures. The plugin self-configures to work with the device's specific TEE and PVP implementation.
Data Source
AI summary
A Trustonic DRM Plug-in is provided that can be downloaded and operate in conjunction with an Android framework. The solution also includes a PVP with the downloadable DRM. The system includes components that can be added by Trustonic based on the Android 4.3 Framework in addition to current t-base 300 that can be used by any DRM vendor. The system enables the DRM to be downloaded in the field since all DRMs could use the standard API services of the Android 4.3 OS. With a codec component employed like H.264 or HEVC that can use the PVP with the downloaded DRM component, the Android video player can use the component to satisfy HD content security requirements.