DRM Key Cache Synchronization Across Data Centers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Inconsistent encryption key data across different data centers can cause issues with displaying content at user devices, leading to potential outages when a switch is made between data centers.
Innovation Solution
A system for synchronizing Digital Rights Management (DRM) data across multiple computing devices by using a primary and secondary computing device with caches that communicate directly, ensuring consistent encryption key data is available for seamless content display.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If duplicate streams of content are packaged in separate data centers to prevent outages, then system reliability is improved, but encryption key data consistency deteriorates
Solution Approach 1:
The system performs preliminary synchronization of encryption key data from the primary data center to the secondary data center before any failover event occurs. This ensures that when a switch is made between data centers, the encryption key data is already consistent and ready for immediate use, preventing content display issues during failover
Solution Approach 2:
The system introduces an intermediary synchronization mechanism that mediates between the primary and secondary data centers. This intermediary process ensures that encryption key data is consistently propagated from the primary to the secondary data center, resolving the consistency issue while maintaining the reliability benefits of duplicate streams
2Speed
If encryption key data is stored locally at each data center for fast access, then access speed is improved, but data synchronization complexity increases
Solution Approach 1:
The system pre-synchronizes encryption key data to the secondary data center before any failover event, so that when the switch occurs, the data is already available locally without requiring complex real-time synchronization protocols. This reduces both access latency and synchronization complexity
Solution Approach 2:
The system creates a copy of the encryption key data from the primary data center and stores it in the secondary data center's cache. This copying approach allows fast local access at the secondary data center while simplifying the synchronization mechanism to a straightforward data replication process rather than complex real-time coordination
Data Source
AI summary
A computing device (e.g., a content packager) may receive a request for content (e.g., video, audio, games, applications, data). The computing device may send a second request for the requested content to an encoder. In response to the second request, the computing device (e.g., the content packager) may receive the requested content and a content manifest associated with the requested content. The computing device may determine that encryption key data (e.g., an encryption key and/or key metadata) for the requested content is not in a cache associated with the computing device. The computing device (e.g., the content packager or a cache associated with the content packager) may send a request for the encryption key data associated with the requested content to a cache associated with a second computing device, based on the determination that the encryption key data is not in the cache associated with the computing device.