Method and system for unified mobile content protection

• US 9,047,446 B2
• Filed: 07/26/2013
• Issued: 06/02/2015
• Est. Priority Date: 08/14/2009
• Status: Active Grant

• Current Assignee: Ericsson AB (Telefonaktiebolaget LM Ericsson)
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Nair, Raj, Mikhailov, Mikhail
• Primary Examiner(s): SIMITOSKI, MICHAEL J
• Application Number:
  US13/952,075
• Publication Number:
  US 20130311775A1
• Time in Patent Office: 676 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 2221/2107 File encryption
• CPC Class Codes: G06Q 50/184 Intellectual property management
• CPC Class Codes: H04L 2209/603 Digital right managament [DRM]
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 9/0631 Substitution permutation network [SPN], i.e. cipher composed of a number of stages or rounds each involving linear and nonlinear transformations, e.g. AES algorithms
• CPC Class Codes: H04L 9/0656 Pseudorandom key sequence combined element-for-element with data sequence, e.g. one-time-pad [OTP] or Vernam's cipher
• CPC Class Codes: H04L 9/0838 Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these network architectures or network communication protocols for key exchange in a packet data network H04L63/061
• CPC Class Codes: H04L 9/0866 involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics
• CPC Class Codes: H04L 9/30 Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
• CPC Class Codes: H04N 21/2347 involving video stream encryption
• CPC Class Codes: H04N 21/2351 involving encryption of additional data arrangements using cryptography for the use of broadcast information or broadcast-related information H04H60/23
• CPC Class Codes: H04N 21/25816 involving client authentication restricting access to computer systems by authenticating users using a predetermined code G06F21/33; cryptographic authentication protocols H04L9/32; networks authentication protocols H04L63/08; authentication in wireless network security H04W12/06
• CPC Class Codes: H04N 21/26613 for generating or managing keys in general key distribution for secret or secure communication involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP] H04L9/083; network support of key management H04L63/06; key management for network security in communication control or processing H04W12/04
• CPC Class Codes: H04N 21/41407 embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop constructional details of equipment or arrangements specially adapted for portable computer application G06F1/1626; arrangements specially adapted for mobile receivers in broadcast systems H04H20/57
• CPC Class Codes: H04N 21/42684 Client identification by a unique number or address, e.g. serial number, MAC address, socket ID network arrangements, protocols or services for addressing or naming H04L61/00
• CPC Class Codes: H04N 21/4353 involving decryption of additional data arrangements using cryptography for the use of broadcast information or broadcast-related information H04H60/23
• CPC Class Codes: H04N 21/4405 : involving video stream decryption
• CPC Class Codes: H04N 21/4627 : Rights management associated to the content security in data switching network management H04L41/28; security management or policies for network security H04L63/20; access security in wireless networks H04W12/08
• CPC Class Codes: H04N 21/6125 : involving transmission via Internet transmission by internet of broadcast information H04H60/82
• CPC Class Codes: H04N 21/63345 : by transmitting keys key distribution for secret or secure communication H04L9/08; network support of key management H04L63/06
• CPC Class Codes: H04N 21/6582 : Data stored in the client, e.g. viewing habits, hardware capabilities, credit card number arrangements where receivers interact with the broadcast H04H20/38
• CPC Class Codes: H04N 21/835 : Generation of protective data, e.g. certificates protecting software against unauthorised usage in a vending or licensing environment G06F21/10
• CPC Class Codes: H04N 21/8456 : by decomposing the content in the time domain, e.g. in time segments
• CPC Class Codes: H04N 7/1675 : Providing digital key or authorisation information for generation or regeneration of the scrambling sequence pseudo-random number generators in general G06F7/58
• CPC Class Codes: H04N 7/17318 : Direct or substantially direct transmission and handling of requests

Abstract

Media content is delivered to a variety of mobile devices in a protected manner based on client-server architecture with a symmetric (private-key) encryption scheme. A media preparation server (MPS) encrypts media content and publishes and stores it on a content delivery server (CDS), such as a server in a content distribution network (CDN). Client devices can freely obtain the media content from the CDS and can also freely distribute the media content further. They cannot, however, play the content without first obtaining a decryption key and license. Access to decryption keys is via a centralized rights manager, providing a desired level of DRM control.

Claims

1. A method for protecting media items delivered over the Internet to mobile devices wherein a license to each media item for a given mobile device is individualized to the given mobile device, the method including:

engaging in a device registration process with a digital rights management (DRM) agent on a mobile device, the registration process including receiving device information encrypted with a secret domain key built-in to the device from the DRM agent and establishing a device-specific secure communications channel as well as a device-specific rights encryption key, the device-specific rights encryption key being shared with the mobile device and generated using the device information and the domain key;

receiving a media rights request from the DRM agent, the media rights request being encrypted with the domain key and being received via the device-specific secure communications channel; and

in response to the media rights request, generating a media rights object and returning it to the mobile device via the device-specific secure communications channel, the media rights object being encrypted with the device-specific rights encryption key and including media location information and a media decryption key, the media location information identifying a location in a content distribution network from which an encrypted media item is to be downloaded for playback, and the media decryption key being usable by the mobile device to decrypt the encrypted media item upon being downloaded by the mobile device.

2. The method of claim 1 wherein delivery of a media item to a mobile device is via segmented files over a hypertext transfer protocol.

3. The method of claim 1 wherein the license is also individualized to a specific user.

4. The method of claim 1 wherein a media item has a plurality of representations for delivery at different bitrates.

5. The method of claim 4 wherein delivery switches arbitrarily between the different bitrates.

6. The method of claim 1 wherein the content is played offline.

7. The method of claim 1, further comprising:

creating a media encryption key on a per-media basis during ingestion of media;

encrypting the media using the media encryption key;

pushing the encrypted media to the content delivery network for later delivery to mobile devices.

8. A method according to claim 7, further including per-media configuration of specific distinct encryption ciphers on a per-media basis.

9. A method according to claim 7, wherein the encryption ciphers include one or more stream ciphers for which a final key length is also per-media configurable.

10. A method according to claim 7, wherein encrypting the media uses one or more encryption ciphers selected from advanced encryption standard (AES), RC4, HC-128 and XOR.

11. A method according to claim 10, wherein encrypting the media includes performing an XOR operation using a key of a certain length L combined with data of protected content, the XOR operation comprising:

exclusive-OR′

ing the key with L content bytes starting at a selected position of the content file;

exclusive-OR′

ing the key with subsequent sets of L content bytes of the content file until all content bytes have been XOR′

ed with the key.

12. A method according to claim 11, wherein the selected position is a predetermined position at or near a beginning of the content file.

13. A method according to claim 11, wherein the selected position in a beginning portion of the content file and chosen just prior to encrypting the content file.

14. A method according to claim 11, further including:

downloading an encrypted media item to a mobile device;

decrypting the encrypted media item only during playback and only in small quantities necessary for immediate playback, each small quantity spanning a range of content bytes determined by operation of a video player performing the playback and also by user scrubbing actions during playback, the scrubbing actions including rewinding and fast forwarding, the decrypting further including receiving a byte range and an offset of a first byte in the byte range from the beginning of the encrypted media item, and computing a mapping between the key and content bytes which need to be decrypted.

15. A method according to claim 10, wherein encrypting the media includes performing an HC-128 operation using a key of a certain length combined with data of protected content, the HC-128 operation comprising:

initializing an HC-128 stream cipher algorithm and generating a stream of bytes of a preconfigured length, the length being configured on a per-media basis, the initialization including setting the value of an initialization vector employed by the HC-128 stream cipher algorithm to zero;

for a first set of content bytes of the preconfigured length, exclusive-OR′

ing the stream of bytes with the set of content bytes;

for subsequent sets of the content bytes, (1) incrementing the initialization vector, (2) re-initializing the HC-128 stream cipher algorithm with the incremented initialization vector, and (3) repeating the generating of the stream of bytes and the exclusive OR′

ing the stream of bytes with the subsequent sets of content bytes until the entire content file is fully encrypted.

16. A method according to claim 15, further including:

downloading an encrypted media item to a mobile device;

decrypting the encrypted media item only during playback and only in small quantities immediately necessary for playback, each small quantity spanning a range of content bytes determined by operation of a video player performing the playback and also by user scrubbing actions during playback, the scrubbing actions including rewinding and fast forwarding, the decrypting further including (1) receiving a range of bytes located anywhere within the media item along with an offset from the beginning of the media item, (2) identifying one or more initialization vectors needed to decrypt the bytes, (3) initializing the HC-128 algorithm using one of the identified initialization vectors, (4) generates a key stream, (5) exclusive-OR′

ing the key stream with the bytes, and (6) repeating the above steps (3), (4) and (5) using distinct other ones of the initialization vectors for subsequent ranges of content bytes as necessary until the media item is fully decrypted.

17. A method according to claim 10, wherein encrypting the media includes performing an RC4 operation using a key of a certain length combined with data of protected content, the RC4 operation comprising:

initializing an RC4 stream cipher algorithm and generating a stream of bytes of a preconfigured length, the length being configured on a per-media basis, the initialization including setting the value of an initialization vector employed by the RC4 stream cipher algorithm to zero;

for a first set of content bytes of the preconfigured length, exclusive-OR′

ing the stream of bytes with the set of content bytes;

for subsequent sets of the content bytes, (1) incrementing the initialization vector, (2) re-initializing the RC4 stream cipher algorithm with the incremented initialization vector, and (3) repeating the generating of the stream of bytes and the exclusive OR′

ing the stream of bytes with the subsequent sets of content bytes until the entire content file is fully encrypted.

18. A method according to claim 17, further including:

downloading an encrypted media item to a mobile device;

decrypting the encrypted media item only during playback and only in small quantities immediately necessary for playback, each small quantity spanning a range of content bytes determined by operation of a video player performing the playback and also by user scrubbing actions during playback, the scrubbing actions including rewinding and fast forwarding, the decrypting further including (1) receiving a range of bytes located anywhere within the media item along with an offset from the beginning of the media item, (2) identifying one or more initialization vectors needed to decrypt the bytes, (3) initializing the RC4 algorithm using one of the identified initialization vectors, (4) generates a key stream, (5) exclusive-OR′

ing the key stream with the bytes, and (6) repeating the above steps (3), (4) and (5) using distinct other ones of the initialization vectors for subsequent ranges of content bytes as necessary until the media item is fully decrypted.

19. A method according to claim 10, wherein encrypting the media includes performing an AES operation using a key of a certain length combined with data of protected content, the AES operation comprising:

randomly generating AES encryption keys on a per-media basis at the time of ingestion of the media;

representing the media as multiple segments having corresponding sequence numbers;

establishing distinct initialization vectors for the segments;

performing an AES encryption algorithm on each segment using the respective initialization vector, the AES encryption algorithm including cipher block chaining within each segment and not spanning multiple segments.

20. A method according to claim 19, further including:

downloading an encrypted media item to a mobile device;

decrypting the encrypted media item using a native player of the mobile device, the native player having access to a playlist specifying a content decryption key, the playlist being served from a local HTTP server executing on the mobile device, the key being delivered to the mobile device from a digital rights management server via an encrypted message.

21. The method of claim 1, wherein the device-specific rights encryption key includes additional individualization parameters beyond an identification of the mobile device.

22. The method of claim 21, wherein the other individualization parameters include unique user information and/or unique application information for an application program executing on the mobile device and containing the DRM agent.

23. The method of claim 22, wherein the unique application information includes an application name or identifier.

24. A method for obtaining and playing protected content on a client device, comprising:

registering the client device by engaging in a device registration process with a digital rights management (DRM) server, the registration process including sending device identification information encrypted with a secret domain key built-in to the device to the DRM server and establishing a device-specific secure communications channel with the DRM server as well as a device-specific rights encryption key, the device-specific rights encryption key being shared with the DRM server and generated using the device information and the domain key;

obtaining the license for use of the protected content by sending a media rights request to the DRM server via the device-specific secure communications channel and receiving a media rights object via the device-specific secure communications channel in response to the media rights request, the media rights request being encrypted with the domain key, the media rights object being encrypted with the device-specific rights encryption key and including media location information and a media decryption key, the media location information identifying a location in a content distribution network from which the protected content is to be downloaded for playback, and the media decryption key being usable by the mobile device to decrypt the encrypted media item upon being downloaded by the mobile device;

decrypting the received media rights object using the device-specific rights encryption key to access the media location information and media decryption key;

obtaining the protected content from the content distribution network using the media location information and decrypting the protected content using the media decryption key; and

playing the decrypted content using a player of the client device.

25. The method of claim 24, further including detecting clock roll-back by use of a DRM agent executing on the client device to:

monitor a local clock to ensure that a time reported by the local clock is continuously incrementing;

at a time of starting a playback application, sampling the time and comparing it to a last known time stored in an encrypted rights file on the client device; and

employing a separate thread which wakes up at regular intervals as playback proceeds and (1) keeps track of elapsed playback time, (2) adding the elapsed playback time to the previously sampled local time on the client device, and (3) writing the result to the encrypted file.

26. The method of claim 24, further including detecting content expiration by:

maintaining rights information including an expiration time and/or maximum play count in association with each media item, the right information being received from a digital rights management (DRM) server in an encrypted form, and storing the rights information in an encrypted file on the client device;

upon initiating playback of the media item, employing a DRM agent on the client device to determine whether the media item has expired by comparing a current time on the client device to the expiration time of the media, and/or comparing the maximum play count to a stored actual play count, the DRM Agent ensuring that clock rollbacks on the client device are detected and disallowing media playback if time is not steadily incrementing, the DRM Agent executing a separate thread, in parallel with a thread performing playback such that the media item can expire not only upon initiating playback but also during playback.

27. The method of claim 24, wherein the device registration process includes establishing device specificity by:

uniquely identifying the client device using a unique physical device identifier, the unique physical device identifier being obtained from the client device using an application programming interface offered by an execution environment of the client device, the unique physical device identifier being encrypted with a domain secret and stored in an encrypted file on the client device and also sent to a digital rights management (DRM) server via an encrypted message, the encrypted unique physical device identifier being stored by the DRM server in a database of registered client devices and being mapped to a unique logical device identifier representing a user of the client device, the unique logical device identifier being sent encrypted with the domain secret.

28. The method of claim 27, wherein the unique physical device identifier is selected from an IMEI number, an MEID, an ESN and a UDID.

29. The method of claim 27, further comprising:

combining the unique physical device identifier with a domain key to generate the device-specific rights encryption key.