Secure Media Casting via Key Server Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems, such as Google Chromecast, cannot transfer a playback session of streaming media content protected using non-native content protection technologies like SecureMedia without adding a client for the non-native DRM or resorting to screen mirroring, which limits workload distribution for retrieving, decrypting, and decoding protected media.
Innovation Solution
A method involving a key server on a mobile device to generate a URL based on its IP address, using a custom DNS server to extract and transmit the IP address, and accessing a content server to obtain and decrypt protected media for display on a digital media player, thereby enabling secure and efficient media casting without native DRM client installation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If screen mirroring is used to transfer media playback session, then compatibility with non-native DRM technologies is achieved, but system performance and efficiency deteriorate
Solution Approach 1:
A key server acts as an intermediary between the mobile device and the Google Cast device. The key server receives content keys from the mobile device and delivers them to the Cast device, enabling secure media playback without requiring screen mirroring. This intermediary solution maintains compatibility with non-native DRM technologies while preserving system performance.
2Adaptability or versatility
If a client for non-native DRM is added to the Google Cast device, then support for additional DRM technologies is enabled, but device complexity and installation requirements increase
Solution Approach 1:
The DRM client functionality is extracted from the Google Cast device and relocated to the mobile device. The mobile device maintains the non-native DRM client locally, while the Cast device receives only the decrypted media content and content keys through the key server intermediary. This extraction eliminates the need to install additional DRM clients on the Cast device.
Solution Approach 2:
The key server serves as an intermediary that bridges the mobile device (with DRM client) and the Cast device (without DRM client). It receives encrypted content keys from the mobile device, processes them appropriately, and delivers them to the Cast device, enabling DRM-protected content playback without requiring the Cast device to have native support for non-native DRM technologies.
3Ease of operation
If content keys are delivered directly to the Google Cast device, then media playback is enabled, but security against unauthorized access is compromised
Solution Approach 1:
The key server acts as a secure intermediary in the content key delivery process. It receives content keys from the mobile device through secure communication channels and relays them to the Google Cast device. This intermediary layer maintains security by controlling the key distribution process and ensuring that only authorized devices can receive the keys needed for playback.
Solution Approach 2:
The system segments the content key delivery process into distinct stages: key generation on the mobile device, key transmission to the key server, and key delivery to the Cast device. This segmentation allows for targeted security measures at each stage, with the key server implementing security protocols to prevent unauthorized access while enabling legitimate playback.
Data Source
AI summary
A method is provided for secure and direct delivery of digital media content directly from a content server to a casting digital media player. In the method, the digital media player is provided with a custom URL that contains concatenated information related to the IP address associate with the location of a key on a mobile device used to commence a casting session.