# Patent

## Title
Method for supporting post browsing in moving rights object of digital rights management and terminal thereof

## Abstract

Disclosed is a digital rights management (DRM), and more particularly, a transfer of a rights object (RO) to a second user in consideration of requirements of a movement of a rights object of a first user (a terminal, an equipment), charge, etc., by providing a post browsing session when the rights object occupied by the first user is transferred to a second user via a server.

## Background
This application is the National Phase of PCT/KR2008/005076 filed on Aug. 29, 2008, which claims priority under 35 U.S.C. 119(e) to U.S. Provisional Application No. 60/969,382 filed on Aug. 31, 2007 and under 35 U.S.C. 119(a) to Patent Application Nos. 10-2008-0000364 and 10-2008-0079644 filed in Korea on Jan. 2, 2008 and Aug. 13, 2008, all of which are hereby expressly incorporated by reference into the present application.


TECHNICAL FIELD
The present invention relates to a digital rights management (DRM), and more particularly, to transferring a rights object (RO) to a second user by considering a requirement of a first user (a terminal, an equipment) when the rights object occupied by the first user is transferred to a second user via a server.
BACKGROUND ART
A Digital Rights Management (DRM) system is a technology for securely protecting and systematically managing a rights object of digital contents, and provides a series of protection and management systems related to the prevention of illegal copy of digital contents and acquisition of rights object of the digital contents, generation and circulation of the digital contents, and procedures of use of the digital contents. The DRM has been applied to a variety of applications, such as a media player, an audio player, an image viewer, and the like.
FIG. 1 is a schematic view of a digital rights management system. The digital rights management system controls digital contents provided from a contents provider to a user such that the user is able to use the digital contents as much as rights object granted to the user. Here, the contents provider is an entity corresponding to a Contents Issuer (CI) and/or a Rights Issuer (RI).
The Contents Issuer (CI) issues contents (i.e., DRM contents) protected using a specific encoding key so as to protect the DRM contents from users having no access rights, and the Rights Issuer (RI) issues Rights Object (RO) required to use the protected contents.
A DRM agent installed in a terminal receives the protected contents and rights object, and controls a use of the contents by analyzing a license included in the rights object and converting the protected contents into a form suitable for being used in a corresponding terminal.
FIG. 2 is a signal flowchart illustrating a related art method for moving, by a first terminal (a terminal of a first user), a rights object occupied by the first terminal to a second terminal (a terminal of a second user) through an RI. The first terminal is a source terminal which desires to move a rights object, while the second terminal is a target terminal which receives the rights object. In the related art shown in FIG. 2, after receiving a trigger message for moving a rights object from an RI (S1), the first terminal sends a request message (MoveRightsRequest) for moving a rights object (e.g., RO1, RO2 and RO3) occupied by (belonging to) the first terminal (S2). The RI sends to the first terminal a message (MoveRightsResponse) in response to the request message (S3), and moves the rights object (i.e., RO1, RO2 and RO3) requested by the first terminal to the second terminal (S4).
In the related art as shown in FIG. 2, the source terminal moves the rights object occupied by the source terminal to the target terminal through the RI, however, requirements for moving the rights object of the source terminal, etc. are not considered.
DISCLOSURE OF THE INVENTION
Therefore, it is an object of the present invention to provide a method for considering requirements for moving a rights object desired by a source terminal and/or a target terminal, when the source terminal wants to move a rights object occupied by the source terminal through a server (e.g., an RI).
To achieve this object, there is provided a method for supporting a post browsing in moving a rights object in digital rights management according to the present invention, including:
(A) transferring, by a first terminal, a request message to a server so as to move a rights object occupied by the first terminal to a second terminal;
(B) receiving, by the first terminal, a response message including address information (e.g., a PR-URL) from the server;
(C) checking, by the first terminal, whether or not the address information is included in the response message; and
(D) connecting, by the first terminal, to a server managing charge and payment information by using the address information, and performing a browsing session.
Preferably, the step (D) includes: checking, by the first terminal, charge and payment information of a rights object to be moved to the second terminal; and changing or modifying, by the first terminal, the rights object to be moved to the second terminal.
Preferably, there is further included a step of moving, by the server, the changed or modified rights object to the second terminal.
Preferably, there are further included steps of inquiring and answering, by the server in cooperation with the second terminal, about charge/payment information or charge/payment condition of the changed or modified rights object; and moving, by the server, the rights object to the second terminal based on the inquiry and answer.
Preferably, there is further included a step of disabling, by the first terminal, the rights object.
Preferably, there is further included a step of deleting, by the first terminal, the rights object.
To achieve this object, in a method for moving a rights object between terminals through a server, there is provided a method for moving a rights object in digital rights management according to the present invention, including:
receiving, by a first terminal, a response message in response to a request for moving at least one or more rights objects from a server; checking, by the first terminal, whether or not address information (e.g., a PR-URL) is included in the response message; performing, by the first terminal, a browsing session by using the address information; and changing, by the first terminal, the rights objects through the browsing session.
Preferably, there is further included a step of moving, by the server, the changed rights objects to a second terminal.
In addition, to achieve this object, there is provided a terminal according to the present invention, including: a receiver configured to receive a response message including address information (e.g., PR-URL) with respect to a request for moving a rights object; and a controller configured to check whether or not the address information is included in the received response message, perform a browsing session by using the address information, and change the rights object to be moved.
EFFECT
First, from a perspective of a terminal user, the present invention may consider a variety of requirements of the terminal user (viewing charge information, adding/removing a rights object to be moved, or the like) when a terminal moves a rights object to another terminal, even after the terminal transferred the rights object to the server (RI).
Second, from a perspective of a service provider, the present invention allows the service provider to develop a variety of business scenarios as well as to provide a flexible digital contents service to a user, since the terminal can view charge information of the rights object or modify (e.g., addition, deletion, etc.) the rights object to be moved even after the terminal transferred the rights object to be moved to another terminal to the server.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a schematic view of a digital rights management system;
FIG. 2 is a signal flowchart illustrating a related art method for moving, by a first terminal (a terminal of a first user), a rights object occupied by the first terminal to a second terminal (a terminal of a second user) through an RI;
FIG. 3 is a signal flowchart illustrating a method for supporting a post browsing in moving a rights object in digital rights management according to one embodiment of the present invention;
FIG. 4 is a signal flowchart illustrating a method for supporting a post browsing in moving a rights object in digital rights management according to another embodiment of the present invention; and
FIG. 5 is a schematic view of a terminal according to the present invention.



MODES FOR CARRYING OUT THE PREFERRED EMBODIMENTS
The present invention is applied to a Digital Rights Management (DRM) system. However, the present invention is not limited to the DRM system, and may also be applied to all communication systems and methods thereof to which the technical scope of the present invention may be applied, and other rights related system and method thereof.
Various modifications and embodiments can be made in the present invention, and reference will be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. However, it should also be understood that embodiments are not limited by any of the details of the foregoing description, but rather should be construed broadly within its spirit and scope and it is intended that the present invention cover modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
Though terms including ordinal numbers such as a first, a second, etc. may be used to explain various components, the components are not limited to the terms. The terms are used only for the purposed of distinguishing one component from another component. For instance, a first component may be referred to as a second component, or similarly, the second component may be referred to as the first component, without departing from the scope of the present invention. A term ‘and/or’ is used to include a combination of a plurality of disclosed items or one of the items.
In case it is mentioned that a certain component is “connected” or “accessed” to another component, it may be understood that the certain component is directly connected or accessed to the another component or that a component is interposed between the components. On the contrary, in case it is mentioned that a certain component is “directly connected” or “directly accessed” to another component, it should be understood that there is no component therebetween.
Terms used in the present invention is to merely explain specific embodiments, thus it is not meant to be limiting. A singular expression includes a plural expression except that two expressions are contextually different from each other. In the present invention, a term “include” or “have” is intended to indicate that characteristics, figures, steps, operations, components, elements disclosed on the specification or combinations thereof exist. Rather, the term “include” or “have” should be understood so as not to pre-exclude existence of one or more other characteristics, figures, steps, operations, components, elements or combinations thereof or additional possibility.
Except that they are not differently defined, all terms used in the present invention including technical or scientific terms have the same meanings with terms that are generally understood by those skilled in the art related to the field of the present invention. The terms same as those of which are defined in a general dictionary should be understood that the terms have meanings same as contextual meanings of the related art. And, as long as the terms are not definitely defined in the present invention, the terms are not interpreted as ideal or excessively formal meanings.
Reference will now be given in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts, and the same descriptions thereof are omitted.
The present invention conceptually relates to considering requirements (e.g., charge information, payment information, and the like) of a source terminal and/or a target terminal when a rights object is moved between terminals (i.e., the source terminal and the target terminal) through a specific server (e.g., an RI). That is, first, if the source terminal requests to move the rights object, the server sends a response message by including a parameter indicating a specific address (also referred to as ‘specific address information’) therein, second, the source terminal connects to a server of the specific address (e.g., a web address of a server, an address of a server in responsible for charge and additional information, or the like) included in the response message and thereby to check or modify the charge information and/or additional information of the rights objects to be moved, and third, the server moves the rights objects to the target terminal based on the checked or modified charge information and/or additional information. In particular, in order to describe exemplary embodiments of the present invention, the parameter indicating the specific address (or specific address information) included in the response message is defined as the ‘Post Response Uniform Resource Locator (URL)’ (in short, PR-URL). However, the technical scope of the present invention is not limited to a formal meaning of the defined term, and may also be applied to all terms to which the technical characteristic of the present invention is implemented.
A Rights Object Acquisition Protocol (ROAP) is a protocol used to move a rights object between terminals through a server. Hereinafter, descriptions of parameters included in a request message (MoveRightsRequest) of a ROAP for moving a rights object and a response message (MoveRightsResponse) according to the present invention will be given.
Table 1 shows parameters included in a request message for moving a rights object. The message is a message sent from the source terminal (first terminal) to the server. In Table 1, the parameter M (Mandatory) indicates a parameter which should be mandatorily included, and the parameter O (Optional) indicates a parameter which may be optionally included.










TABLE 1







Parameter
ROAP-MoveRightsRequest









Device ID
M



RI ID
M



Device Nonce
M



Request Time
M



Recipient Device ID
O



Rights Info
M



Certificate Chain
O



Extnesions
O



Signature
M










In Table 1, the “Device ID” is a parameter indicating an ID (identification) of a source terminal. The “RI ID” is a parameter indicating an ID of a server (RI) receiving a request message (MoveRightsRequest) which is sent from the source terminal. The “Device Nonce,” as a random number, is a parameter included in a response message (MoveRightsResponse) to be sent by the server and used to check whether it is a response to the request message. The “Request Time” is a parameter indicating a transmission time of the request message. The “Recipient Device ID” is a parameter indicating an ID of a receiving terminal to which the source terminal desires to move (transfer) the rights object, that is, an ID of a target terminal. The “Rights Info” is a parameter including information related to a rights object transferred from the source terminal to the server. The “Certificate Chain” is a parameter indicating a certificate chain of the source terminal transmitting the request message. The “Signature,” as a digital signature for the entire request message, is a parameter indicating a digital signature value generated by the source terminal.
Table 2 shows parameters included in a response message with respect to the request message in Table 1. The response message is a message sent to the source terminal (first terminal) from the server. In Table 2, the parameter M (Mandatory) indicates a parameter which should be mandatorily included, and the parameter O (Optional) indicates a parameter which may be optionally included.










TABLE 2









ROAP-MoveRightsResponse












Parameter
Status = Success
Status ≠ Success







Status
M
M



Device ID
M
M



RI ID
M
M



Device Nonce
M
M



Certificate Chain
O
—



OCSP Response
O
—



Post Response URL
O
—



Extensions
O
—



Signature
M
M










In Table 2, the “Status” is a parameter indicating a processing state of the request message. The “Device ID” is a parameter indicating an ID of a source terminal receiving the response message. The “RI ID” is a parameter indicating an ID of a server (RI) sending the response message. The “Device Nonce” should have the same value as that of the “Device Nonce” included in the request message. The “Certificate Chain” is a parameter indicating a certificate chain of the server. The “OCSP Response” is a parameter including information indicating whether or not a certificate of a server is discarded if the source terminal requests an OCSP Response in the request message. The “Signature” is a parameter indicating, by the server, a digital signature value for the entire response message. The “Post Response URL,” as a parameter newly defined in the present invention, includes address-related information of a server (a web server) capable of inputting charge information or additional information related to moving a rights object.
The present invention relates to supporting a Post Browsing by connecting to a server of an address included in the parameter “Post Response URL” (or ‘address information’). Here, the post browsing refers to changing, modifying, inquiring, etc. additional information with respect to the rights object to be moved, after messages for moving a rights object are exchanged between the server (RI) and the terminal (a source terminal) in relation to the movement of the rights object.
FIG. 3 is a signal flowchart illustrating a method for supporting a post browsing in moving a rights object in digital rights management according to one embodiment of the present invention. In FIG. 3, a first terminal 201 is a source terminal for moving (transferring) a rights object of the first terminal 201 through a server 100, and a second terminal 202 is a target terminal for receiving the rights object transferred by the first terminal 201 through the server 100. In addition, in FIG. 3, the server 100 is assumed to be a Rights Issuer (RI), however, the server 100 may also be an entity, other than the RI.
Referring to FIG. 3, a protocol (e.g., a 2-way ROAP Acquisition) for moving a rights object between the server 100 and the first terminal 201 is proceeded. That is, the first terminal 201 receives a trigger message from the server 100 indicating a start of the movement of the rights object (S11). Here, the trigger message is an optional message which can be selectively received from the server 100 so as to move the rights object of digital contents in the first terminal 201.
The first terminal 201 transmits, to the server 100, a request message (MoveRightsRequest) for moving rights objects (e.g., RO1, RO2 and RO3) occupied by the first terminal 201 to the second terminal 202 (S12). Here, the first terminal 201 may disable the rights objects. Here, the disablement of the rights objects signifies a state that the rights objects cannot be used. And, the request message (MoveRightsRequest) may include the parameters as shown in Table 1.
In response to the request message in step (S12), the server 100 transmits a response message (MoveRightsResponse) to the first terminal 201 (S13). Here, the response message includes a PR-URL parameter. The PR-URL parameter includes an address of the server 100 capable of performing the post browsing procedure (e.g., an address of a web server: here, the address of the server in FIG. 3 is the address of the RI.). The first terminal 201 receives the response message, and checks whether or not the PR-URL parameter is included in the response message (S14).
And, the first terminal uses an address indicated by the PR-URL so as to connect to a corresponding server of the address and initiate (start) a post browsing session with the server 100 (S15). For instance, a user of the first terminal 201 may inquire, by using the post browsing session, about a cost required to move the rights object having been transferred to the server 100 to the second terminal 202, and pay the inquired cost according to a determination of the user. As another example, it is assumed that the first terminal 201 moves (transfers) rights objects (e.g., RO1, RO2 and RO3) occupied by the first terminal 201 to the second terminal 202. Here, through the post browsing session in step (S15), the first terminal 201 may check, for instance, charge-related information of the rights objects to be transferred to the second terminal 202 (e.g., the cost for moving RO1 or RO3 is “1,000” and the cost of moving RO2 is “3,000”), and accordingly, the user of the first terminal 201 may intend to move the rights object only which requires an inexpensive moving cost. Here, the user of the first terminal 201 may select rights objects only (e.g., RO1 and RO3 only) which are desired to actually move to the second terminal among the rights objects (i.e., RO1, RO2 and RO3). That is, the first terminal 201 may change and modify a list of rights objects desired to transfer by performing the post browsing session with the server 100. Consequently, the first terminal 201 deletes a portion (i.e., RO2) of its rights objects in the post browsing session due to a reason including a transmission cost, or the like.
Based on the post browsing performed in step (S15), the server 100 transmits, to the second terminal 202, the rights objects (i.e., RO1 and RO3) requested by the first terminal 201 (S16).
In step (S14), the first terminal may consider the response message (MoveRightsResponse) as an acknowledgement of the request message (MoveRightsRequest) in step (S12), and delete the rights objects (e.g., RO1 ̃RO3) to be moved.
FIG. 4 is a signal flowchart illustrating a method for supporting a post browsing in moving a rights object in digital rights management according to another embodiment of the present invention. In the embodiment in FIG. 4, signal flows in FIG. 4, which have the same reference numerals as those in the embodiment shown in FIG. 3, are the same as the corresponding signal flows in FIG. 3 in operations and functions thereof. Therefore, descriptions of the signal flows in FIG. 4 will refer to those of the respective signal flows in FIG. 3.
The embodiment in FIG. 4, when compared to that in FIG. 3, may further include inquiring and answering about charge/payment condition of a rights object to be transferred between the server 100 and the second terminal 202 after the post browsing session (S15). That is, the server 100 inquires of the second terminal 202 whether or not the rights object changed in step (S15) (i.e., transferring the RO1 and RO3 only, instead of transferring the RO1 ̃RO3) should be received. In response to this, the second terminal 202 may inquire about charge/payment condition of the rights objects to be transferred, or may send a response which will check charge/payment condition for the rights objects to be transferred provided by the server 100 and then receive the rights objects.
FIG. 5 is a schematic view of a terminal according to the present invention.
Hereinafter, description of a structure and an operation of a terminal according to the present invention will be given with reference to FIG. 5.
The terminal 300 according to the present invention comprehensively includes all types of devices capable of using contents in DRM, such as all terminals for mobile communications (e.g., User Equipments (UEs), mobile phones, cellular phones, Digital Multimedia Broadcasting (DMB) phones, DVB-H phones, Personal Digital Assistant (PDA) phones, and PTT phones, and the like), digital TVs, GPS navigations, portable game players, MP3, other home appliances, and the like.
The terminal 300 according to the present invention may include a receiver 301 configured to receive a response message including a PR-URL with respect to a request for moving a rights object; and a controller 302 configured to check whether or not the PR-URL is included in the received response message, perform a browsing session by using the PR-URL, and change (or modify) the rights object to be moved in the browsing session or view charge/payment information. Here, the controller may also be referred to as a DRM agent.
In addition to the basic components as shown in FIG. 7, the terminal 300 according to the present invention may include all essential components of an equipment (terminal) necessary to use DRM contents. Here, other components in FIG. 7 are apparent to those skilled in the art, therefore detailed explanations thereof are omitted. The operations and functions of each component of the terminal 300 according to the present invention will be equally applied to the respective portions described in FIGS. 3 and 4.
As the present invention may be embodied in several forms without departing from the characteristics thereof, it should also be understood that the above-described embodiments are not limited by any of the details of the foregoing description, unless otherwise specified, but rather should be construed broadly within its scope as defined in the appended claims, and therefore all changes and modifications that fall within the metes and bounds of the claims, or equivalents of such metes and bounds are therefore intended to be embraced by the appended claims.

## Claims

1. A method for supporting a post browsing in moving a rights object in digital rights management, the method comprising:
receiving, by a first user equipment (UE) which is able to consume a content, at least one rights object for allowing the content to be consumed from a server, wherein the rights object is owned by the first UE after the rights object is issued by the server;
if the rights object is to be moved via the server to a second UE which is able to consume a content, disabling, by the first UE, the rights object such that the rights object is unusable;
transmitting, by the first UE and to the same server, a request message to move the rights object to the second UE, wherein the request message includes information on the rights object to be moved;
receiving, by the first UE, a response message including address information from the server;
checking, by the first UE, whether or not the address information is included in the response message;
connecting, by the first UE, to a server based on the address information thereby enabling a browsing session to select or deselect the rights object to be moved and to manage charge and payment required to move the rights object; and
deleting, by the first UE, the rights object.

2. The method of claim 1, wherein the connecting step comprises:
checking, by the first UE, charge and payment information of a rights object to be moved to the second UE; and
changing or modifying, by the first UE, the rights object to be moved to the second UE.

3. The method of claim 2, further comprising:
moving, by the server, the changed or modified rights object to the second UE.

4. The method of claim 2, further comprising:
inquiring and answering, by the server in cooperation with the second UE, about charge/payment information or charge/payment condition of the changed or modified rights object; and
moving, by the server, the rights object to the second UE based on the inquiry and answer.

5. The method of claim 1, wherein the address information is included in a Post Response (PR)-URL parameter, and the address information is a parameter including an address of a server managing the charge/payment information.

6. A method for moving a rights object between user equipments (UEs), the method performed by a server and comprising:
transmitting, by the server, to a first user equipment (UE) which is able to consume a content, at least one rights object for allowing the content to be consumed, wherein the rights object is owned by the first UE after the rights object is issued by the server;
receiving, by the server and from the first UE, a request message to move the rights object to a second UE, and
wherein the request message includes information on the rights object to be moved, and
wherein the rights object to be moved is in a disable state within the first UE such that the rights object is unusable by the first UE;
transmitting, by the server and to the first UE, a response message including address information;
connecting, by the server, a browsing session with the first UE such that the rights object is selected to be moved or deselected and that charge and payment required to move the rights object is managed; and
transmitting, by the server, the rights object to the second UE,
wherein the rights object is deleted in the first UE.

7. The method of claim 6, further comprising:
moving, by the server, the changed rights objects to a second UE.

8. The method of claim 6, wherein the address information is included in a Post Response (PR)-URL parameter, and the address information is a parameter in which the first UE indicates an address of a server performing the browsing session.

9. A user equipment which is able to consume a content, the user equipment comprising:
a transceiver configured to receive at least one rights object to allow the content to be consumed from a server, wherein the rights object is owned by the first UE after the rights object is issued by the server; and
a controller configured to disable the rights object such that the rights object is unusable if the rights object is to be moved to a second UE via the server,
wherein the controller is further configured to control the transceiver to transmit to the same server a request message to move the rights object to the second UE, the request message including information on the rights object to be moved,
wherein the controller is further configured to check whether or not the address information is included in the response message,
wherein the controller is further configured to control the transceiver to connect to a server based on the address information thereby to perform a browsing session enabling to select or deselect the rights object to be moved and to manage charge and payment required to move the rights object, and
wherein the controller is further configured to delete the rights object.

10. The terminal of claim 9, wherein the address information is included in a Post Response (PR)-URL parameter, and the address information is a parameter indicating an address of a server performing the browsing session.