Apparatus and method for moving rights object from one device to another device via server

Abstract

An apparatus and method for transferring a Rights Object (RO)for a content between devices via a server, wherein a sending device converts a first RO taken by itself to encode into a second RO, and sends an RO move request message including the second RO to the server, whereas the server converts the second RO included in the RO move request message into a third RO and transfers the third RO to a receiving device, whereby the receiving device receives the third RO from the server for installation, wherein the sending device deletes or modifies the first RO at an appropriate time point.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a configuration of a system for moving a rights object among devices via a server in accordance with the present invention;

FIG. 2 illustrates an embodiment of a method for moving a rights object from one device to another device via a server in accordance with the present invention;

FIG. 3 illustrates an exemplary text describing a syntax of an RO move trigger in accordance with the present invention;

FIG. 4 illustrates parameters of an RO move request message in accordance with the present invention;

FIG. 5 illustrates am exemplary syntax of an RO move request message in accordance with the present invention;

FIG. 6 illustrates a schema fragment of a redirect identifier extension parameter included in an RO move request message in accordance with the present invention;

FIG. 7 illustrates a structure of an RO move request message in accordance with the present invention;

FIG. 8 illustrates an exemplary text indicating a syntax of an RO move request message in accordance with the present invention;

FIG. 9 illustrates an exemplary XML document indicating “move” permission included in an RO.

Claims

1. A method for transferring a rights object between devices via a server comprising: converting, by a sending device, a first rights object to generate a second rights object;sending from the sending device to the server a rights object move request message for requesting a transfer of the second rights object to a receiving device via the server;receiving a response message from the server with respect to the rights object move request message; anddeleting the first rights object or modifying state information related to the first rights object.

2. The method of claim 1, wherein the generating the second rights object comprises: decoding the first rights object using a private key of the sending device; andencoding the decoded first rights object using a public key of the server or a secret key shared with the server.

3. The method of claim 1, wherein the generating the second rights object comprises: encoding, by the sending device, a Contents Encryption Key (CEK) included in the first rights object using the public key of the server or the secret key shared with the server;including, as parameters, permissions, constraints and a digital signature each of which is the same as those of the first rights object;encoding a Rights Object Encryption Key (REK) and a MAC key using the public key of the server or the secret key shared with the server; andgenerating a mac value by calculating the MAC key or a new MAC key.

4. The method of claim 1, wherein the rights object move request message includes, as mandatory parameters, an ID of the sending device, a server ID, a device nonce, a request time, the second rights object to be transferred and a digital signature, and includes, as optional parameters, a trigger nonce, an ID Of the receiving device, a state information object, a certificate chain, and an extensions parameter.

5. The method of claim 1, wherein the response message includes, as mandatory parameters, a status of processing the rights object move request message, an ID of a device to receive the response message, the server ID, a server nonce and a digital signature for the response message, and includes, as optional parameters, a URI parameter for acquiring a rights object bound to the receiving device, and an extensions parameter.

6. The method of claim 1, wherein if all of the first rights object is transferred to the receiving device via the server, the sending device deletes the first rights object.

7. The method of claim 1, wherein if part of the first rights object is transferred to the receiving device via the server, the sending device modifies state information related to the first rights object.

8. The method of claim 1, wherein the first and second rights objects include one of a device rights object and a user domain rights object.

9. The method of claim 1, wherein the first and second rights objects have at least move constraint.

10. A method for transferring a rights object between devices via a server comprising: receiving from a sending device a rights object move request message;sending a response message to the sending device with respect to the rights object move request message;converting a first rights object included in the rights object move request message into a second rights object; andtransferring the second rights object to a receiving device.

11. The method of claim 10, wherein the converting the first rights object into the second rights object comprises: decoding the first rights object using a private key of the server or a secret key shared with the sending device; andencoding the decoded first rights object using a public key of the receiving device or a secret key previously shared with the receiving device.

12. The method of claim 10, wherein the converting the first rights object into the second rights object comprises: encoding, by the server, a Contents Encryption Key (CEK) included in the first rights object using a public key of the receiving device or a secret key previously shared with the receiving device;modifying a move count constraint value included in the first rights object;generating a digital signature value;encoding a Rights Encryption Key (REK) and a MAC key using the public key of the receiving device or the secret key previously shared with the receiving device; andgenerating a mac value.

13. The method of claim 10, wherein the rights object move request message includes, as mandatory parameters, an ID of the sending device, a server ID, a device nonce, a request time, the first rights object to be transferred and a digital signature, and includes, as optional parameters, a trigger nonce, an ID Of the receiving device, a state information object, a certificate chain, and an extensions parameter.

14. The method of claim 10, wherein the response message includes, as mandatory parameters, a processed state of the rights object move request message, an ID of a device to receive the response message, the server ID, a server nonce and a digital signature for the response message, and includes, as optional parameters, a URI parameter for acquiring the third rights object, and an extensions parameter.

15. The method of claim 10, wherein the rights object move request message comprises at least the first rights object, and wherein the first rights object is converted from a rights object issued for the sending device.

16. The method of claim 15, wherein the first rights object is converted from the rights object by the sending device or by the server.

17. The method of claim 10, further comprising: sending a ROAP trigger for indicating the sending device to start transferring the rights object to the server, to the sending device.

18. The method of claim 10, wherein the second rights object is transferred from the server to the receiving device and installed in the receiving device.

19. A sending device in an, apparatus for transferring a rights object between devices comprising: a Digital Rights Management (DRM) agent which encodes a rights object to be transferred to a receiving device via a server and sends a rights object move request message including the encoded rights object to the server; anda communication module which communicates with the server.

20. The sending device of claim 19, wherein the encoded rights object comprises a Contents Encryption Key (CEK) encoded using a public key of the server or a secret key shared with the server.

21. The sending device of claim 20, wherein the encoded rights object comprises permissions, constraints and a digital signature each of which is the same as those of the rights object owned by the DRM agent.

22. The sending device of claim 21, wherein the encoded rights object comprises a Rights Encryption Key (REK) and a MAC key each encoded using a public key of the server or a secret key previously shared with the server.

23. The sending device of claim 22, wherein the encoded rights object comprises a mac value generated by calculating the MAC key or a new MAC key.

24. The sending device of claim 19, wherein the rights object move request message is a message for requesting the server to transfer the rights object to the receiving device via the server.

25. The sending device of claim 19, wherein the rights object move request message includes, as mandatory parameters, an ID of the sending device, a server ID, a device nonce, a request time, the second rights object to be transferred and a digital signature, and includes, as optional parameters, a trigger nonce, an ID Of the receiving device, a state information object, a certificate chain, and an extensions parameter.

26. A server in an apparatus for transferring a rights object between devices comprising: a Rights issuer (RI) which receives from a sending device a rights object move request message including a rights object to be transferred to a receiving device, sends a response message to the sending device with respect to the rights object move request message, converts the rights object included in the rights object move request message, and transfers the converted rights object to the receiving device; anda communication module which communicates with the sending device and the receiving device.

27. The server of claim 26, wherein the rights issuer decodes the rights object included in the rights object move request message using a private key the rights issuer or a secret key previously shared with the sending device has or a shared secret key, and encodes the decoded rights object using a public key of the receiving device or a secret key previously shared with the receiving device.

28. The server of claim 26, wherein the rights issuer modifies a move count constraint value when the rights object included in the rights object move request message has the move count constraint.

29. The server of claim 26, wherein the rights object move request message includes, as mandatory parameters, an ID of the sending device, an ID of the rights issuer, a device nonce, a request time, the rights object to be transferred and a digital signature, and includes, as optional parameters, a trigger nonce, an ID Of the receiving device, a state information object, a certificate chain, and an extensions parameter.

30. The server of claim 26, wherein the response message includes, as mandatory parameters, a processed state of the rights object move request message, an ID of a device to receive the response message, the server ID, a server nonce and a digital signature for the response message, and includes, as optional parameters, a rights object URI parameter for acquiring the rights object, and an extensions parameter.

31. A system for transferring a rights object between devices via server comprising: a sending device which sends a rights object move request message including a second rights object converted from a first rights object;a server which converts the second rights object included in the rights object move request message into a third rights object and transfers the third rights object to a receiving device; anda receiving device which receives the third rights object from the server and installs the third rights object.

32. The system of claim 31, wherein the second rights object includes a Rights Encryption Key (REK) and a MAC key each encoded using a public key of the server or a secret key previously shared between the server and the sending device.

33. The system of claim 31, wherein the third rights object includes a Rights Encryption Key (REK) and a MAC key each encoded using a public key of the receiving device or a secret key previously shared between the server and the receiving device.

34. A method for transferring a rights object between devices via a server comprising: sending, by a sending device, a rights object move request message including a rights object identifier;checking, by the server, a rights object corresponding to the rights object identifier;receiving, by the sending device, a rights object move response message from the server; anddeleting, by the sending device, the rights object corresponding to the rights object identifier or modifying state information related to the rights object.

35. The method of claim 34, further comprising: converting, by the server, the checked rights object into a rights object for a receiving device; andtransferring, by the server, the converted rights object to the receiving device.

36. The method of claim 35, wherein the converting of the rights object comprises: decoding, by the server, the checked rights object using a public key of the server or a secret key previously shared with the sending device; and encoding the decoded rights object using a public key of the receiving device or a secret key previously shared with the receiving device.

37. The method of claim 34, wherein the rights object move request message includes, as mandatory parameters, an ID of the sending device, a server ID, a device nonce, a request time, a rights object identifier and a digital signature, and includes, as optional parameters, a trigger nonce, an ID Of the receiving device, a state information object, a certificate chain, and an extensions parameter.

38. The method of claim 34, wherein the rights object response message includes, as mandatory parameters, a processed state of the rights object move request message, an ID of a device to receive the response message, the server ID, a server nonce and a digital signature for the response message, and includes, as optional parameters, a URI parameter for acquiring a rights object bound to the receiving device, and an extensions parameter.

39. The method of claim 34, wherein when all of the rights object is transferred to the receiving device via the server, the sending device deletes the rights object.

40. The method of claim 34, wherein when a part of the rights object is transferred to the receiving device via the server, the sending device modifies state information related to the rights object.

41. The method of claim 34, wherein the rights object includes one of a device rights object and a domain rights object.

42. The method of claim 34, wherein the rights object has at least move constraint.