KR20090003420A - A method and an apparatus for obtaining right objects of contents in a mobile terminal - Google Patents

Abstract

A contents right object acquiring method of a portable terminal and an apparatus thereof are provided to maximize the profit of a DRM contents provider and to improve the convenience of contents purchase according to acquiring the right object about the DRM contents. A portable terminal(200) generates ROAP-trigger request about specific DRM contents to an RI server(S910). The ROAP trigger request message includes the contents ID of one or more contents. The RI server(250) receiving the ROAP trigger request message transmits to the personal terminal(S920). The controller produces an RO request message requesting the RO of one or more DRM contents(S930).

Description

Method and device for acquiring content rights object of mobile terminal {A METHOD AND AN APPARATUS FOR OBTAINING RIGHT OBJECTS OF CONTENTS IN A MOBILE TERMINAL}

Figure 1a and 1b is a configuration diagram of a conventional OMA-DRM RO purchasing system.

2 is a block diagram of a mobile terminal according to an embodiment of the present invention.

3A is a flowchart of a method for acquiring a content rights object of a mobile terminal according to an embodiment of the present invention.

3B is a structural diagram schematically showing a data structure of an integrated right object permission message according to an embodiment of the present invention;

4 is a flowchart illustrating a method for obtaining a content rights object on a system according to an exemplary embodiment of the present invention.

5 is a flowchart illustrating a procedure of generating a list of DRM contents to be collectively acquired by a mobile terminal according to an exemplary embodiment of the present invention.

6 is a flowchart illustrating a procedure for generating a list of DRM contents to be collectively acquired on a system according to an embodiment of the present invention.

7 is a flowchart illustrating a procedure for generating a list of DRM contents to be collectively acquired by a mobile terminal according to another embodiment of the present invention.

8 is a flowchart illustrating a procedure for generating a list of DRM contents to be collectively acquired on a system according to another embodiment of the present invention.

9 is a flowchart illustrating a method for acquiring a content right object of a mobile terminal according to another embodiment of the present invention.

10 is a flowchart of a method for acquiring a content right object of a mobile terminal according to another embodiment of the present invention.

11A illustrates an example of a list of DRM contents to be collectively acquired according to an embodiment of the present invention.

11B illustrates an example of an information field structure of a list of DRM contents to be collectively acquired according to an embodiment of the present invention.

12 is a flowchart illustrating a procedure of a method for acquiring a content right object of a mobile terminal according to another embodiment of the present invention.

13 is a structural diagram showing a DCF structure of the DRM content proposed in the present invention.

14 is a flowchart illustrating a procedure of a method for acquiring a content rights object of a mobile terminal according to another embodiment of the present invention.

The present invention relates to a method and apparatus for acquiring a content right object of a mobile terminal, and more particularly, to a method and apparatus for acquiring a content right object of a mobile terminal for collectively acquiring rights objects for a plurality of encrypted contents.

With the recent digital convergence, portable terminals have various complex functions. For example, the portable terminal is provided with an MP3 module and a digital broadcast receiving module, so that a user can listen to music and watch a broadcast using the portable terminal. In addition, services such as online games, MOD (Music On Demand), and VOD (Video On Demand) can be used using the wireless Internet. Various digital contents are produced to utilize the functions of the mobile terminal. In particular, a lot of multimedia content such as ringtones, videos, games, etc. are produced and distributed, most of which is paid content that the user has to pay.

On the other hand, in order to prevent unauthorized copying or redistribution of the paid digital content, a technology called digital rights management (hereinafter referred to as 'DRM') has been proposed. The DRM is a technology that enables the protection of the rights of copyright holders by applying strong encryption technology to contents such as documents, voices, mp3 files, ringtones, videos, and games. The process until digital content is generated, published, distributed and used Provide a set of protection and management mechanisms for In addition, DRM ensures that only the authorized user can decrypt and use the content because the digital content always exists in an encrypted state, and even if the content is copied, the right object (Right Object, RO) is required. You can prevent piracy by controlling users who are not authorized by a specific license.

The rights object (RO) is special information used in the OMA-DRM (Open Mobile Alliance DRM) scheme. The OMA-DRM is a digital rights protection (DRM) specification set by the Open Mobile Alliance, an application standardization organization for mobile phones. The rights object (RO) is generated in a rights issuer server called a RI (Right Issuer) and sold to a DRM user, and is also separated from digital content and stored in a user device to limit the execution of the content. Generally, the right object RO includes a count method, an interval method, a time-count method, an accumulate method, and the like.

In addition, the rights object (RO) includes a constraint (constraint), which is information that restricts the use of DRM-protected content is stored in a specific field in the rights object.

For example, if a purchase of an mp3 file is possible to play a total of 10 times, 10 constraints are set in the counted rights object. In this case, each time the mp3 file is played, the count decreases by one. If the count reaches '0' in accordance with the tenth playback, the playback of this file is no longer possible, and the file playback is possible only by purchasing an additional rights object RO. Such additional purchase of the rights object is referred to as a 'RO update'.

1a and 1b is a block diagram of a conventional OMA-DRM RO purchasing system.

The mobile terminal 101 transmits a message 105 requesting the content desired by the user to the content server 102. The content server 102 transmits the DRM-applied content 106 to the mobile terminal 101. The application of DRM means that the content has been encrypted using the encryption key and encryption format specified in the DRM, and the usage restriction information (Usage Rule, the number of times that can be played, the playable period, etc.) of the content according to the format specified in the DRM. Is recorded. Subsequently, the mobile terminal 101 transmits a message 107 requesting a license for the received content 106 to the license server 103. The license is a certificate of granting a right to use a predetermined content, and includes a decryption key and usage restriction information used to decrypt the received content 106. Thus, for example, if the content is DRM applied, the mobile terminal 101 can play the content 106 to which the DRM has been applied only after receiving a license defined in the DRM system. The license server 103 checks whether the user is a legitimate user, and if it is a legitimate user, generates a license 108 for the content 106 to which the DRM is applied and transmits it to the mobile terminal 101. The license 108 includes decryption keys and usage restriction information used in the DRM. The mobile terminal 101 plays the received content 106 using the license 108. That is, the DRM client program installed in the mobile terminal 101 extracts a decryption key and restriction information used for decrypting content from the license 108, and checks the number of times of reproduction and reproduction period included in the extracted usage restriction information. After checking whether the use of the content 106 does not violate the usage restriction information, if the violation does not violate, the content 106 is decrypted and reproduced using the decryption key.

The OMA-DRM RO purchasing system shown in FIG. 1A is OMA-DRM 1.0 version, and the DRM-RO including the unencrypted Content Encryption Key (CEK) is executed by the mobile terminal 101 from the rights issuing server (RI) 103. Is delivered. Therefore, in OMA-DRM 1.0 version, when a fraudulent user who does not have a right to use DRM content simultaneously acquires DCM (DRM Content Format) and RO (Right Object, license of DRM content), information of content is randomly acquired and distributed. As a result, the copyright of the DRM content may be infringed.

The OMA-DRM RO purchasing system shown in FIG. 1B is an OMA-DRM 2.0 version, which is CEK (encrypted by public key method) by any authorized authority 104 (eg, Content Management License Administrator (CMLA)). Content Encryption Keys 109 and 110 are transmitted to the mobile terminal 101 and the rights issuing server (RI) 103, respectively. Accordingly, the DRM-RO including the encrypted content encryption key (CEK) 110 is transferred from the rights issuing server (RI) 103 to the mobile terminal 101. Therefore, in the OMA-DRM 2.0 version, even if an unauthorized user such as a hacker acquires both a DCF (DRM Content Format) and RO (Right Object, license for DRM content) at the same time, only a specific user (a specific subscriber or a specific mobile terminal user) has CEK. Since the information is additionally processed so that the information can be decrypted, the copyright of the DRM content is protected.

However, in the case of purchasing DRM content to which the OMA-DRM 2.0 version is applied or obtaining RO (free acquisition, purchase or renewal), the rights object (RO) for DRM content should be purchased one for each content. There is this. In other words, if the constraint of any mp3 file, video file, or game file is exhausted and cannot be executed, the mobile terminal executes a purchase process of the rights object for each of the contents in order to execute the files. There is a problem that the DRM content purchase process is inconvenient because it must be performed separately for each content.

Accordingly, an object of the present invention is to provide a method and apparatus for acquiring a content rights object of a mobile terminal, which enables to collectively acquire rights objects for a plurality of DRM contents.

Another object of the present invention is to improve the convenience of purchasing content according to the collective acquisition of rights objects for DRM content, and to maximize the profits of DRM content providers and to expand the discount benefits of DRM content buyers. The present invention provides a method and apparatus for acquiring a content right object.

It is still another object of the present invention to provide a method and apparatus for acquiring a content rights object of a mobile terminal capable of proposing a standard technique for collectively acquiring the rights objects of a plurality of DRM contents.

In the present invention for achieving the above object, the content rights object acquisition method of the mobile terminal, the process of transmitting the integration rights object request information for a plurality of content, and the integration rights corresponding to the integration rights object request information Transmitting an integrated right object request message for the plurality of contents upon receiving object permission information; and receiving the integrated right object permission message corresponding to the integrated right object request message from the integrated right object allowed message to the plurality of contents. This may include the process of acquiring the rights objects for a batch.

In addition, in the present invention for achieving the above object, the method for obtaining a content rights object of the mobile terminal, the process of generating a content list to be obtained collectively when inputting a selection command for a plurality of encrypted content, and the generated Generating and transmitting an integrated rights object request message to the rights issuing server for the collective acquisition request of the content list; and receiving the integrated right object permission message corresponding to the integrated rights object request message from the rights issuing server. It may include a process of collectively obtaining the rights object for the selected content from the object permission message.

In addition, in the present invention for achieving the above object, the method for acquiring the content rights object of the mobile terminal, if it is required to acquire the RO for at least one DRM content, ROAP (Right Object Acquisition Protocol) for the DRM content Generating and transmitting a trigger request message (ROAP-trigger Request) to a right issuer (RI) server; When a ROAP trigger corresponding to the ROAP trigger request message is received from the RI server, an RO request message for requesting a right object (RO) of at least one DRM content according to a user's setting is received. Generating and transmitting to the RI server; If an RO response message corresponding to the RO request message is received, the method may include collectively acquiring at least one RO included in the RO response message.

In addition, in the present invention for achieving the above object, the content rights object acquisition apparatus of the mobile terminal, the memory for storing data including the content; An input unit configured to input a selection command of a mobile terminal user for a plurality of contents; A display unit for displaying a list of the plurality of contents and a message inviting collective acquisition of the selected content rights object; An RF processor for transmitting and receiving a data signal with a rights object server for arbitrary content through a wired or wireless communication network; Generating the integrated right object request information of the plurality of selected contents from the list of the plurality of contents, generating an integrated right object request message for the collective acquisition request of the selected plurality of contents, and corresponding to the integrated right object request information; And a control unit which collectively obtains rights objects for the selected plurality of contents upon receiving the integrated rights object permission information and the integrated rights object permission message corresponding to the integrated right object request message.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Table 1 shows terms used in one embodiment of the present invention.

OMA Open Mobile Alliance DRM Digital Rights Management DCF DRM Content Format RO Right Object (= License) ROAP Right Object Acqusition Protocol FL Forward lock CD Combined Delivery SD Separate Delivery CEK Content Encryption Key RI Right Issuer CI Content Issuer (= Content Server) CA Certificate Authority OCSP Online Certificate Status Protocol CMLA Content Management License Administrator

2 is a block diagram of a mobile terminal 200 according to an embodiment of the present invention. Referring to FIG. 2, the mobile terminal 200 includes a control unit 201, an audio processing unit 204, an input unit 205, an RF (Radio Frequency) processing unit 206, a data processing unit 207, and a memory 208. , A camera module 209, an image processor 210, and a display 211.

The controller 201 performs a function of controlling the overall operation of the portable terminal and the signal flow between internal blocks of the portable terminal. In addition, the controller 201 may include a function of the data processor 207. In addition, the control unit 201 is a signal between the audio processing unit 204, the input unit 205, the data processing unit 207, the memory 208, the camera unit 209, the image processing unit 210, and the display unit 211. You can control the flow.

In addition, when inputting a content playback command, the control unit 201 checks the format of the content stored in the memory 208 to determine whether the content is a DRM content (eg, a DCF file), and a series of related to decoding and playback of the DRM content. It is in charge of the processing.

In addition, when the access to the specific DRM content is made or when the constraint of the specific DRM content is exhausted by a predetermined reference or more, the control unit 201 may determine the reproduction authority (for example, RO) of the DRM content stored in the memory 208. You can check for existence. When the playing right for the DRM content is provided, the DRM content may be played.

The audio processor 204 converts the audio data into an audible sound through the speaker SPK under the control of the controller 201, and outputs the audio signal such as a voice received from the microphone MIC. .

The input unit 205 may be a keypad or a touch panel, and includes a plurality of numeric, character and / or function keys for inputting numeric and character information and setting various functions. In addition, the input unit 205 is a device that receives information related to user setting and control, and generates and outputs an input signal according to an input from a user to the control unit 201. The controller 201 may perform a function designated in a corresponding menu (or mode) based on the input signal.

The RF processor 206 is responsible for a series of communication related to the transmission and reception of content (contents) via a mobile communication network or a wired or wireless Internet network. The RF processor 206 may include an RF transmitter for upconverting and amplifying a frequency of a transmitted signal, and an RF receiver for low noise amplifying and downconverting a received signal.

The data processor 207 may include a transmitter configured to encode and modulate a signal transmitted through the RF processor 206, a receiver configured to demodulate and decode a signal received through the RF processor 206.

The memory 208 may largely include a program memory area and a data memory area. The program memory area stores an operating system for booting the portable terminal and a program for configuring a standby screen of the portable terminal. The data memory area is an area in which data generated according to the use of a mobile terminal is stored. At least one other data is stored through data communication such as DRM content moving or copying through an external memory or a hard disk and wired / wireless internet or short-range wireless communication. The DRM content received from the device (including the server and other terminals) may be stored.

The camera unit 209 photographs a subject under the control of the controller 201 to receive an optical signal, converts the input optical signal into a digital signal, and outputs the digital signal. The image processor 210 converts a digital signal output from the camera unit 209 into an image signal to generate screen data.

The display unit 211 displays screen data output from the image processor 210. The display unit 211 may include a liquid crystal display (LCD) or the like. When the LCD has a touch screen function, the display unit 211 may perform a data input function. Can be. In addition, the display unit 211 may display, by the control unit 201, a collective acquisition invitation message for the DRM content that has been exhausted by a predetermined criterion or more in the DRM content execution mode.

According to various modifications to the configuration of the mobile terminal, at least one of the units may be excluded from the configuration of the mobile terminal 200 according to the present invention or replaced by another unit within the scope of not disturbing the intention of the present invention. It will be readily understood by one of ordinary skill in the art that additional units, not mentioned above, may further be included.

For example, the portable terminal 200 according to an embodiment of the present invention may include a storage medium insertion unit for inserting an external storage medium such as a memory card to store data, a short-range communication module such as IrDA or Bluetooth, or an MP3 module. Units with additional functions such as digital sound playback module, electronic payment module such as mobile banking chip or transportation card chip, broadcast receiving module, connection terminal for data exchange with external digital device, battery module and charging terminal It may be configured to include more.

3A is a flowchart illustrating a method for acquiring a content right object of a mobile terminal according to an exemplary embodiment of the present invention.

In step S301, the mobile terminal 200 is in a standby state.

In step S303, the controller 201 checks whether the mobile terminal 200 is in the DRM content execution mode. The DRM content execution mode may operate when a mobile terminal user accesses (executes, charges or purchases) any DRM content.

In step S305, the control unit 201 generates a list of DRM contents to be collectively acquired according to the DRM-RO acquisition request for any DRM contents. The DRM content is an encrypted multimedia file, which may be DRM content previously stored in the mobile terminal 200 and having no RO or a constraint exhausted by a predetermined reference or more.

Looking at the process of generating a list of DRM content to be collectively acquired, the control unit 201 generates integrated rights object request information (ROAP-trigger request) for at least one content selected or allowed by a user. do.

The integrated rights object request information includes a content ID of the at least one content. The integrated right object request information includes a device ID (DeID: Device ID) of the mobile terminal 200, a constraint defining a right scope of the right object of the at least one content, and permission to use the corresponding content. It may further optionally include at least one of the permission (permission) indicating the level. Permission indicates the level of permission of the content, that is, what rights it is allowed to use. For example, content that only contains the permission "display" can only be displayed. Content that includes the permissions "and" print "can be printed as well as displayed.

3B is a structural diagram schematically showing a data structure of the integrated right object grant message according to an embodiment of the present invention. Referring to FIG. 3B, the integrated rights object permission message includes "protectedRO" for each DRM content, and each "protectedRO" includes at least one "permission" (the permission level indicating the permission level of the corresponding content). Permission), and at least one "constraint" (constraint), which is information on usage restriction of the corresponding DRM content, is included in each "permission". For example, in the case of an integrated rights object permission message for a specific MP3 file and an image file, it may include at least two "protectedRO", and the "protectedRO" for the MP3 file may include a play type "permission". have. In addition, the "permission" of the reproduction type may include at least one "constraint" such as "monthly" or "one week and seven times." In the case of “one week and seven times,” it means that the MP3 file can be played only seven times in one week. Also, the "protectedRO" for an image file may include a display type of "permission", which includes a "permission" of "one month" or "ten times" or "one month or ten times". The same at least one "constraint" may be included. That is, the "constraint" may be included depending on the "permission".

The "permission" may be at least one of "play", "display", "execute", "print" and "export". The "constraint" may be at least one of "count", "timed-count", "datetime", "interval", "individual", and "system".

The generated integrated rights object request information is transmitted to a rights issuer (RI) server. In the present invention, the mobile terminal 200 may be connected to the RI server through a wired or wireless communication network.

The RI server generates integrated rights object allowance information (ROAP-trigger) corresponding to the integrated rights object request information based on an ID (contentID) of the content included in the integrated right object request information to the mobile terminal 200. send. In this case, the purchase cost of the contents may be calculated and the purchase cost information may be transmitted together. The integrated rights object permission information includes a rights object ID (roID) assigned to each content. In addition, the integrated rights object allowance information may include rights object address (roapURL), RI ID, RI Alias, Domain ID, Domain Alias, and Nonce of the content. At least one of may optionally further include. The nonce refers to a randomly generated disposable random number having a length of 32 bits or 64 bits, as designated by the RI server.

The controller 201 receives the integrated rights object permission information and generates a list of DRM contents to be collectively acquired. In this case, the control unit 201 may display the purchase cost information received together for the user's confirmation on the display unit 211 and receive a selection of whether to approve the purchase cost from the mobile terminal user.

In the present invention, the RI server should make one integrated rights object allowance information (ROAP-trigger) for a plurality of content and deliver it to the mobile terminal (200). To this end, the mobile terminal 200 may inform the RI server through the ROAP-trigger request that one piece of integrated object rights information is required for a plurality of contents.

Subsequently, in step S 307, the controller 201 generates an integrated rights object request message (roRequest) for requesting DRM-RO acquisition for the DRM content of the generated DRM content list. The integrated rights object request message includes a rights object ID (roID) for content to be obtained. The rights object ID may be extracted based on the integrated rights object permission information. In addition, the integrated right object request message includes a device ID, a domain ID, a RI ID, a nonce, a request time, and RO information of the mobile terminal 200. The method may further include at least one of parameters such as RO Info, a certificate chain, a signature, and extensions.

[Table 2] shows roap (Right Object Acquisition Protocol) data display of the unified right object request message in one embodiment of the present invention. For example, the mobile terminal user selects three pieces of content to be obtained, and a rights object ID (roID) assigned to each of the selected contents received from the rights object server is ro11, ro53. In the case of ro97, the control unit 201 reads the integrated right object permission information and generates an integrated right object request message including the right object IDs ro11 (ro53. ro97) of each selected content. In this case, when a nonce is included in the integrated right object allowed information, the same nonce as the nonce included in the integrated right object allowed information may be allocated.

<roap: roRequest xmlns: roap "urn: oma: bac: dldrm: roap-1.0" triggernonce = uPjd / olB1SkflpSrkhf / <roID> ro11; ro53; ro97 </ roID>

In step S309, the controller 201 transmits the generated integrated right object request message to the RI server through a wired or wireless communication network.

The RI server may verify the integrated right object request message (roRequest). If the verification is successful, the RI server may authenticate the portable terminal device, generate an integrated right object allowed message (roResponse), and deliver the integrated right object request message to the mobile terminal 200.

The integrated rights object permission message includes a plurality of protected rights objects called 'protectedRO'. The structure of the <roap: protectedRO> message format does not matter if multiple values are included in a single permission object (roResponse). In addition, since the rights object input value is reduced to a fixed length by using a hash algorithm when generating the integrated rights object allowance message, there is no significant increase in the amount of computation.

In step S 311, the control unit 201 checks whether an integrated right object permission message corresponding to the integrated right object request message is received. The integrated rights object permission message (roResponse) includes a rights object (RO) of the DRM contents requested by the integrated rights object request message.

[Table 3] is a roap (Right Object Acquisition Protocol) data display of the integrated right object allowance message in one embodiment of the present invention. As shown in [Table 3], the integrated rights object permission message includes rights object IDs ro11 and ro53. ro97 may be included.

<roap: roResponse xmlns: roap "urn: oma: bac: dldrm: roap-1.0" status = "Success" <nonce> uPjd / olB1SkflpSrkhf / <roID> ro11; ro53; ro97 </ roID>

In addition, the integrated rights object allowance message may include status, device ID, RI ID, protected ROs, certificate chain, and online certificate status protocol. It may further include at least one of parameters such as an OCSP Response, an OCSP Response, a Signature, an Extensions, and the like.

In addition, a nonce may be additionally included as necessary. The nonce included in this case is the same as the nonce included in the integrated right object permission information and the integrated right object request message. That is, when a nonce is included in the integrated right object permission information and the integrated right object request message, the same nonce is included in the integrated right object permission message.

In step S 313, the control unit 201 acquires the rights object of the DRM contents included in the received integrated rights object permission message. That is, the DRM-RO (DRM Content Rights Object) for each of the DRM contents is extracted from the integrated right object permission message.

The controller 201 may update the DRM-RO by allocating the obtained DRM content right object RO for each DRM content. Here, the meaning of 'update' includes the concept of extending (or charging) the usage rights of the DRM contents or initial purchase of the usage rights of the DRM contents.

4 is a flowchart illustrating a method for obtaining a content rights object on a system according to an exemplary embodiment of the present invention. Referring to FIG. 4, the RI server 250 connected to the mobile terminal 200 through the mobile terminal user 150, the mobile terminal 200, and a wired / wireless communication network may include the DRM-RO acquisition method of the mobile terminal illustrated in FIG. 3A. Look through the system is configured to include.

In step S401 the control unit 201 of the mobile terminal 200 is the DRM content execution mode. When the DRM content execution mode is in operation, the control unit 201 outputs a DRM content list through the display unit 211 or a message inviting batch acquisition including the DRM content list in step S 403. 11A is a diagram illustrating an example of a list of DRM contents to be collectively acquired according to an embodiment of the present invention, and FIG. 11B is a diagram illustrating an example of an information field structure of a list of DRM contents to be collectively acquired according to an embodiment of the present invention.

Referring to FIG. 11A, the DRM content list is a DRM content list that needs to be filled with a constraint, that is, RO acquisition is required, and the control unit 201 is provided from a DRM content database stored in the memory 208. Extract.

In operation S 405, the mobile terminal user 150 selects at least one DRM content for RO acquisition from the output DRM content list, and sets a constraint on the corresponding content. That is, a desired period of use, a frequency of use, etc. are set for the corresponding content.

In step S407, the control unit 201 generates the integrated right object request information (ROAP-trigger request) of the selected DRM content and transmits it to the RI server 250 through a wired or wireless communication network.

In S 409. The RI server 250 calculates the integrated right object permission information of the content corresponding to the integrated right object request information and transmits it to the mobile terminal 200. In this case, as described above, the cost for acquiring the selected contents, that is, the purchase cost information may be transmitted together. When the purchase cost information is transmitted together, the control unit 201 transmits the received purchase cost information in step S 411. Is output through the display unit 211. When the controller 150 receives the purchase cost information for collectively acquiring the DRM-RO from the RI server 250 through the RF processor 206, the controller 150 transmits the purchase cost to the user 150 along with the purchase cost on the display unit 211. A message asking for a purchase intention is displayed to allow the user to check how much the purchase cost is and to pay or cancel the purchase cost.

In operation S 413, the mobile terminal user 150 determines whether to approve the output purchase cost. If the purchase cost is not approved, the process returns to the DRM content selection process of step S405, and steps S405 to S411 are repeated.

If the purchase cost is approved, in step S 415, the controller 201 generates an integrated rights object request message (roRequest) for requesting the rights object for the approved DRM content and transmits it to the RI server 250.

When the control unit 201 receives a signal for paying the purchase cost according to the collective acquisition of the DRM-RO through the input unit 205, the mutual authentication process with the RI server 250 through the RF processing unit 206. Or through the payment process such as mobile banking to pay the costs for the collective acquisition of the DRM-RO. To this end, the mobile terminal 200 may be configured to include a module for electronic commerce or mobile banking.

In step S417, the RI server 250 generates an integrated rights object permission message (roResponse) including the requested DRM-RO and transmits it to the mobile terminal 200.

In step S419, the control unit 201 of the mobile terminal 200 collectively obtains the rights object (RO) for the selected DRM content from the received received rights object permission message.

Meanwhile, in the case of RO acquisition of free content or content according to a postpaid payment method, purchase related procedures such as transmission / reception of purchase cost information, determination of approval of purchase cost, and payment process may be omitted.

5 is a flowchart illustrating a procedure of generating a list of DRM contents to be collectively acquired by a mobile terminal according to an embodiment of the present invention, and FIG. 6 is a flowchart of a procedure to generate a list of DRM contents to be collectively acquired on a system according to an embodiment of the present invention. 5 and 6, a description will be given of a procedure for generating a batch purchase DRM content list when arbitrary DRM content is stored in the memory 208 of the mobile terminal 200 in step S305.

6, 8, and 10, the system for collective acquisition of the DRM-RO according to the present invention, the mobile terminal for requesting the collective acquisition of the rights object (RO) for a plurality of content ( 200) and the RI server 250 for generating the DRM-RO of the corresponding content in accordance with the request and collectively transmitting the DRM-RO to the mobile terminal 200 through a wired or wireless communication network. According to the request, the RI server 250 may transmit additional information such as the number of constraint charges or the purchase cost of the corresponding DRM content to the mobile terminal 200.

In step S501, the mobile terminal 200 is in the DRM content execution mode (step S601). In step S503, the controller 201 determines whether a constraint criterion of the DRM content is set. That is, it is checked whether a limit criterion for the remaining number of executions or the period of use in which any DRM content stored in the mobile terminal 200 can be executed is set. For example, the number of times of remaining use of DRM content or one day of remaining use period may be set as a limit. If the constraint reference is not set, the control unit 201 outputs a constraint reference setting recommendation message through the display unit 211 in operation S 505. When the mobile terminal user 150 inputs an affirmative command for the constraint reference setting with respect to the invitation message, a menu for selecting the remaining number of times or the remaining period of use is output and the command is input by the user of the portable terminal user 150. Strain criteria are set.

In step S509, the controller 201 determines whether there is DRM content that falls below the constraint criterion. That is, it is determined whether DRM contents corresponding to the constraint limit criteria exist among the DRM contents stored in the memory 208 of the mobile terminal 200. As a result of the determination, if all of the DRM contents stored in the mobile terminal 200 memory 208 do not correspond to the limit criteria and there is still a sufficient number of times of use or period of use, the DRM contents execution mode is activated in step S517. When the terminal user 150 selects the DRM content and inputs an execution command, the DRM content is executed.

However, if there is a DRM content that does not meet the limit as a result of the determination, in step S511 the control unit 201 outputs the DRM content list and file information that does not meet the limit through the display unit 211 (S 603). process). The file information includes the number or duration of remaining usage rights of the DRM content as shown in FIGS. 11A and 11B.

In step S 513, the controller 201 determines whether a selection command of the mobile terminal user 150 is input to the output DRM content list and file information (step S 605). The mobile terminal user 150 may acquire (or purchase) the rights object RO of the DRM content in which the constraint is exhausted.

When the selection command is input, as shown in FIG. 11A, the controller 201 may display whether or not to mark the DRM content selected by the user 150 in the DRM content list by checking a check box or the like.

The DRM content list has a field structure as shown in FIG. 11B. As shown in FIG. 11B, the DRM content list is divided into a serial number, a content name, a residual constraint, and other items (or fields), and other items may display information for identifying the type of content. In addition, the DRM content list may include information received through communication with the RI server 250. For example, through communication with the RI server 250, information such as the number of obtainable constraint charges or purchase cost may be received and added to the information field of the DRM content list. The DRM content list may be included in the batch acquisition recommendation message for convenience of the user and displayed together with the batch acquisition invitation message, or may be displayed for re-confirmation or final confirmation after the user selects the collective acquisition.

If it is determined that the selection command of the mobile terminal user 150 has not been input, that is, if the user ignores the collective acquisition recommendation message and goes over, the control unit 201 in step S 515 controls the DRM corresponding to the limit criteria. It is determined whether there is DRM content (eg, content with one remaining use count) remaining with constraints among the contents. As a result of the determination, if there is DRM content remaining in the constraint, the DRM content execution mode is activated in step S517 to allow the user to execute the DRM content in which the constraint remains. In addition, when the selection command is not input as a result of the determination and there is no DRM content remaining in the constraint, the DRM content execution mode is terminated.

On the other hand, if a selection command according to the step S 513 is input, in step S 519 the control unit 201 generates the integrated rights object request information (ROAP-trigger request) (ROAP) of the at least one selected DRM content. (S 607 course).

The integrated rights object request information includes a content ID of content of selection. In addition, as described above, a mobile terminal ID (DeID) of the mobile terminal 200, a constraint limiting the range of rights of the rights object of the selected content, and a permission indicating the permission level of the corresponding content ( At least one of the permissions) may be further included.

The constraint (that is, the right scope (charge information) of the license for the DRM content to be collectively acquired) may be determined by the mobile terminal user 150 for each DRM content or the same number of times or the same for all the DRM content. It can also be set collectively as a period. In addition, when the user sets the constraint of the DRM content through the web page of the RI server 250, the RI server 250 and the mobile terminal 200 are connected through a wired / wireless communication network to connect the DRM of the mobile terminal 200. The constraint of the content can be set.

In step S 521, the mobile terminal 200 control unit 201 transmits the integrated right object request information of the selected content to the RI server 250 connected to the mobile terminal 200 through a wired or wireless communication network.

The RI server 250 calculates the integrated right object allowance information (ROAP-trigger) of the selected content corresponding to the integrated right object request information and the purchase cost of the selected content and transmits the purchased cost to the mobile terminal 200 (S609). ).

The integrated rights object permission information includes a rights object ID (roID) assigned to each of the selected contents. The integrated rights object permission information may further include a collective acquisition rights object address (roapURL) of the selected content. In addition, the integrated right object allowance information may further include at least one of RI ID, RI Alias, Domain ID, and Domain Alias.

The RI server 250 may apply one nonce value to the mobile terminal 200 to transmit to the mobile terminal 200 when necessary (that is, when security is required). .

In step S 523, the controller 201 determines whether to receive the integrated right object permission information and the purchase cost.

In step S525 the control unit 201 outputs the received purchase cost to the display unit 211 (step S611). For example, a message informing the purchase cost of the DRM content rights object (DRM-RO), such as "The payment amount is 2500 won. Do you want to purchase the DRM content collectively?" May be output to the display unit 211.

In step S527, the control unit 201 determines whether the portable terminal user 150 inputs the approval command for the purchase cost (that is, in step S613, the portable terminal user 150 receives the approval command for the purchase cost). If it is determined that the output cost is not suitable, the process returns to step S605 to reselect DRM content to be obtained). If the approval command is not input, the control unit 201 returns to step S 513 and repeats steps S 513 to S 525. However, when the approval command is input, in step S529, the control unit 201 generates a list of DRM contents to be collectively acquired (step S615).

When the list of DRM contents to be acquired in a batch is generated, the control unit 201 returns to step S307 to perform a subsequent process.

7 is a flowchart illustrating a procedure of generating a list of DRM contents to be collectively acquired by a mobile terminal according to another embodiment of the present invention, and FIG. 8 is a flowchart of a procedure to generate a list of DRM contents to be collectively acquired on a system according to another embodiment of the present invention.

7 and 8, a description will be given of a process of generating a list of DRM contents to be collectively acquired when the mobile terminal 200 controller 201 accesses the RI server 250 and receives price information of the DRM contents.

In step S701 the mobile terminal 200 is in the DRM content execution mode (step S801). In step S703, the controller 201 checks whether the DRM content is stored in the memory 208. If the DRM content is not stored, the mobile terminal 200 maintains the standby state. If it is determined that the DRM content is stored in step S705, the control unit 201 accesses the rights issuing server (RI server 250) through the wired / wireless communication network and transmits the stored DRM content list to the RI server 250 (S). Course 803). In operation S 707, the controller 201 receives the price information of the stored DRM content from the RI server 250 (operation S 805).

In step S709, the controller 201 determines whether a constraint criterion of the DRM content is set.

If the constraint criterion is not set, the controller 201 outputs a message recommending to set the constraint criterion in step S 711 and receives a predetermined input from the user in step S 713. Can be set.

In step S 715, the controller 201 determines whether there is DRM content that does not meet the set constraint criteria. As a result of the determination, when all of the DRM contents stored in the memory 208 of the mobile terminal 200 do not correspond to the limit criteria and still have sufficient number of times of use or duration of use, the DRM content execution mode may be activated in step S 723. .

However, when the determination result that the DRM content does not meet the limit criteria, the control unit 201 outputs the DRM content list and file information that does not meet the limit criteria through the display unit 211 (S 807). process). The file information includes the number or duration of remaining usage rights of the DRM content as shown in FIGS. 11A and 11B.

In step S719, the controller 201 determines whether a selection command of the portable terminal user 150 is input to the output file list and file information (step S809). If it is determined that the selection command of the portable terminal user 150 is not input, the controller 201 determines whether there is a DRM content remaining of the constraint among the DRM contents corresponding to the limit criteria in step S 721. As a result of the determination, if there is DRM content remaining in the constraint, the DRM content execution mode is activated in step S 723 so that the user can execute the DRM content in which the constraint remains. In addition, when the selection command is not input as a result of the determination and there is no DRM content remaining in the constraint, the DRM content execution mode is terminated.

On the other hand, when a selection command according to the step S 719 is input, the control unit 201 generates a right object acquisition protocol (ROAP) -trigger request (ROAP) of the selected content (S 811). process).

In step S 727, the control unit 201 calculates a DRM-RO purchase cost of the selected DRM content based on the price information received from the RI server 250 in step S 707 (step S 813). As described above, according to an exemplary embodiment of FIGS. 7 and 8, the price of the DRM content may be calculated in the mobile terminal 200.

In step S729, the controller 201 outputs the calculated DRM content purchase cost to the display unit 211 (step S815).

In step S 731, the controller 201 determines whether the mobile terminal user 150 inputs an approval command for the purchase cost (step S 817). If the approval command is not input, the control unit 201 returns to step S719 (step S809) and performs steps S719 to S731 (steps S809 to S815). On the other hand, if the approval command is input in step S 733 the control unit 201 generates a list of DRM content to be obtained collectively (step S 819).

When the list of DRM contents to be acquired in a batch is generated, the control unit 201 returns to step S307 to perform a subsequent process.

9 is a flowchart illustrating a procedure of a method for acquiring a content right object of a mobile terminal according to another embodiment of the present invention.

Referring to FIG. 9, when RO acquisition for at least one DRM content is requested, the mobile terminal 200 generates a ROAP-trigger request for the corresponding DRM content in step S910 by using an RI server ( 250). The ROAP trigger request message may include a content ID of the at least one selected content. The ROAP trigger request message may further optionally include at least one of a mobile terminal ID (DeID) of the mobile terminal 200 and a constraint defining a range of rights of the rights object of the selected content. have.

The ROAP trigger request message may further include license request information of a higher layer when there are licenses of a higher layer of at least two licenses. For example, in the case of acquiring ROs for music files of tracks 1 and 3 of the same album A, since the same higher layer of A album exists, the mobile terminal 200 displays track 1 music file in a ROAP trigger request message. In addition to the RO request information of track music file No.3 and the content ID, the identification value of album A is further included in the ROAP trigger request message so that only the license of album A is requested when obtaining RO in the future. It is possible to obtain the RO of the track's music file. In such a case, the constraint may be subordinated to the upper album A album, so that music files of tracks 1 and 3, which are lower layers of the A album, may be freely used within the total constraint limit of the A album. This will allow users to use their favorite content more conveniently without being restricted by the content.

It is also possible to use a higher layer that is not the same. For example, a user may designate his or her own content list (eg, My List, Favorite List, or Favorite) for each subscriber. In this case, the constraint may be dependent on the upper layer arbitrarily designated by the user.

The at least one DRM content may be a DRM content received from at least one other device (eg, a terminal or a server) or having no RO or a certain amount of constraint exhausted.

Here, the controller 201 selects an RI to purchase RO of the DRM content by referring to URL (Uniform Resource Location) information of the RI included in the header information of the at least one DRM content, and requests a ROAP trigger using the selected RI URL. You can send a message.

Meanwhile, to this end, the present invention has a structure in which a field indicating address information of an RI (or RI server 250) for collectively acquiring a plurality of ROs such as BatchRIURL 1310 is added to a DCF structure as shown in FIG. 13. Suggest. 13 is a structural diagram showing the DCF structure of the DRM content proposed in the present invention. The BatchRIURL 1310 is address information of RI for collective acquisition of ROs of a plurality of contents, and the BatchRIURLLength 1320 is information indicating the length of the BatchRIURL. Since the BatchRIURLLength is auxiliary information, it may or may not be included in the DCF structure as necessary.

At least one BatchRIURL is included in one DCF structure, and the larger the number of BatchRIURLs included, the better the batch acquisition of ROs of more content.

For example, if the content of A includes BatchRIURLs of A 'and the content of B includes only BatchRIURLs of B', it is difficult to collectively acquire ROs of the two contents, but the content of A 'and B' If two BatchRIURLs are included, B ', which is a common RI address for acquiring the rights objects of both contents, exists, thereby enabling collective acquisition of ROs of the two contents.

If there is at least two common BatchRIURLs in the contents for which the rights object is to be collectively obtained, the control unit 201 may have a higher quality or more reliable BatchRIURL (eg, a faster address or an excellent carrier). Address), and for this purpose, the controller 201 may manage BatchRIURLs or equivalent level information included in contents by listing or database.

A field indicating URL information of RI for collectively acquiring the plurality of ROs may be included in a predetermined region of the DCF structure. For example, a field indicating a URL may be newly added as a mandatory field in the common header part. It may be included in an extended header field which is one of the required fields included in the common header.

Alternatively, the controller 201 may select an RI to collectively acquire ROs of the at least one DRM content with reference to an RI URL address previously stored in the memory 208, and transmit a ROAP trigger request message to the selected RI URL. . Alternatively, the controller 201 may request and receive an RI URL address for collectively acquiring ROs of the at least one DRM content from the RI server 250, and transmit a ROAP trigger request message to the received RI URL. The received RI URL may be stored in the memory 208 and used for batch acquisition of future ROs.

Upon receiving the ROAP trigger request message, the RI server 250 generates a ROAP trigger message and transmits the ROAP trigger message to the mobile terminal 200 in step S920. The ROAP trigger message may include RO purchase cost information of the at least one selected content. In addition, the ROAP trigger message may include a rights object ID (roID) assigned to each of the selected contents. The ROAP trigger message may include a rights object address (roapURL), an RI ID, an RI alias, a domain ID, a domain alias, and a nonce of the at least one selected content. nonce) may optionally further include at least one.

The ROAP trigger request message and the ROAP trigger message may be transmitted according to at least one of an HTTP GET or an HTTP POST scheme (see RO acquisition mechanism of OMA-DRM v2.0) proposed by OMA-DRM. In order to collectively acquire ROs of a plurality of DRM contents proposed by the present invention, since the message length may be longer than a message when purchasing a single RO, an HTTP POST method is expected to be more preferable.

The mobile terminal 200 may receive the ROAP trigger message and output the purchase cost to the display unit 211.

Subsequently, in step S930, the controller 201 generates an RO request message (RO Request) for requesting RO of at least one DRM content and transmits it to the RI server 250. At this time, the DRM content may be the same as or different from the DRM content for which RO acquisition is required for the first time. That is, it can be adjusted by the user.

The RI server 250 receiving the RO request message generates the ROs specified in the RO request message in step S940 and includes the RO request message in the RO response message and transmits the RO request message to the mobile terminal 200.

The mobile terminal 200 receiving the RO response message may collectively obtain the RO portion of the corresponding DRM content by extracting the ROs included in the RO response message.

The above processes (S910 to S940) can be applied even if not general. That is, when the DCF structure as shown in FIG. 13 includes an abnormal header such as a silent header or a preview header, that is, user participation such as payment and purchase selection In the case of unneeded content (eg, free content), the mobile terminal 200 (control unit 201) cooperates with the RI server 250 to perform the steps of 910 to S940 in the background so that a user does not recognize it. can do. In this case, the unusual header may include address information for collectively acquiring a rights object of at least one DCF file, such as a silent-group-url. The mobile terminal 200 ) Can access and obtain the DCF files, that is, request the rights object (RO) of the DRM content in a batch. In this case, in order to automatically execute in the background, the DCF structure may further include at least one of permission, constraint, and purchase information in addition to the silent header. The permission may be at least one of "play", "display", "execute", "print", and "export". The constraint may be at least one of "count", "timed-count", "datetime", "interval", "individual", and "system". The constraint may be included depending on the permission. The purchase information may be price of a corresponding content or information for a specific contract method (eg, metering information in consideration of a subscription or post-payment method).

The silent group UEL, permission, constraint, and purchase information may be included in an area in which the user can be arbitrarily manipulated for the convenience of the user in the DCF structure, or cannot be arbitrarily manipulated by the user to prevent improper manipulation. May be included in the area.

The RO response message may further include a session ID for establishing a session between the RI server and the mobile terminal so as to confirm whether RO acquisition has been successfully performed. This will be described with reference to FIG. 10.

10 is a flowchart illustrating a procedure of a method for acquiring a content right object of a mobile terminal according to another embodiment of the present invention.

Referring to FIG. 10, when RO acquisition for a plurality of DRM contents is requested, the mobile terminal 200 generates a ROAP-trigger request for the corresponding DRM contents in step S1010 and then the RI server 250. To send).

As described above, the ROAP trigger request message may include content IDs of the selected plurality of DRM contents. The ROAP trigger request message may further optionally include at least one of a mobile terminal ID (DeID) of the mobile terminal 200 and a constraint defining a range of rights of the rights object of the selected content. have. The plurality of DRM contents may be DRM contents received from at least one other device (eg, a terminal or a server) or having no RO or exhausted for a predetermined level.

Herein, the controller 201 selects an RI to purchase RO of the corresponding DRM content by referring to URL (Uniform Resource Location) information of the RI included in the header information of the plurality of DRM contents, and uses the selected RI URL to request a ROAP trigger request message. Can be transmitted.

In response to the ROAP trigger request message, the RI server 250 generates a ROAP trigger message and transmits the ROAP trigger message to the mobile terminal 200 in step S1020. The ROAP trigger message may include RO purchase cost information of the selected plurality of contents. In addition, the ROAP trigger message may include a rights object ID (roID) assigned to each of the selected contents. The ROAP trigger message may further include a rights object address (roapURL) of the selected contents. The ROAP trigger message may further include at least one of an RI ID, a RI alias, a domain ID, a domain alias, and a nonce.

Subsequently, in step S1030, the mobile terminal 200 generates an RO request message (RO Request) for requesting RO of a plurality of DRM contents and transmits it to the RI server 250.

The RI server 250 receiving the RO request message generates the ROs specified in the RO request message in step S1040 and includes the RO request message in the RO response message and transmits the RO request message to the mobile terminal 200. The message may further include a session ID. The RI server 250 may include the session ID in the RO response message when it is necessary to confirm whether RO acquisition of the mobile terminal has been successfully performed.

The mobile terminal 200 receiving the RO response message acquires ROs included in an RO response message. When the RO response message includes a session ID, the mobile terminal 200 performs a session with the RI server 250 based on the session ID. In step S1050, an RO confirmation request message (RO Confirm Request) is transmitted to the RI server 250 through the established session. The RO confirmation request message may indicate whether RO has been normally acquired by including a parameter such as RO Confirm Info.

The RI server 250 receiving the RO confirmation request message may terminate the RO acquisition process or retransmit the ROs based on the information included in the RO confirmation request message. Transmits an RO confirmation response message (RO Confirm Response) to the mobile terminal 200.

Meanwhile, even if BatchRIURL is not included in the DRM content (the DCF structure of the DRM content), the present invention can be implemented, which will be described with reference to FIG. 12.

FIG. 12 is a flowchart illustrating a procedure of a method for acquiring a content rights object of a mobile terminal according to another embodiment of the present invention. In the case where DRM content does not include a BatchRIURL, that is, only the URL of the RI of the corresponding content for each content is shown. Indicates the case of inclusion.

Referring to FIG. 12, when the rights object acquisition for a plurality of DRM contents selected by the portable terminal user 150 is requested, the mobile terminal 200 determines a content ID of the selected plurality of DRM contents in step S1210. ) Generates a ROAP trigger request message including only) and transmits it to the RI server 250. The controller 201 transmits the ROAP trigger request message to the corresponding RI server 250 by referring to the RI URL of one of the plurality of DRM contents.

In response to the ROAP trigger request message, the RI server 250 may not perform the batch transfer of the rights objects of the corresponding contents, in step S1220, the RI server 250 may perform the batch transfer of the rights objects of the contents. The mobile station 200 transmits a redirection message indicating that the redirection to the new address of the mobile station is performed. As the redirection message, one of an HTTP 302, an HTTP 303, and an HTTP 307 message suggested by OMA-DRM may be used.

The mobile terminal 200 receiving the redirect message sends a ROAP trigger request message back to the corresponding RI server 300 by referring to the RI URL address included in the redirect message, as shown in FIGS. 9 to 10. A batch acquisition process of a plurality of contents can be performed.

As described above, the ROAP trigger request message and the ROAP trigger message may be transmitted according to at least one of the HTTP GET or HTTP POST scheme proposed by OMA-DRM. In addition, the ROAP trigger request message and the ROAP trigger message may be transmitted according to a method specified by the RI server at the time of redirection among the HTTP GET or HTTP POST methods.

14 is a flowchart illustrating a procedure of a method for acquiring a content right object of a mobile terminal according to another embodiment of the present invention.

Referring to FIG. 14, when the rights object acquisition for a plurality of DRM contents selected by the portable terminal user 150 is requested, the mobile terminal 200 determines a content ID of the selected plurality of DRM contents in step S1410. ) Generates a ROAP trigger request message including only) and transmits it to the RI server 250.

After the ROAP trigger request message is transmitted, in step S1420, the mobile terminal 200 and the RI server 250 perform a web transaction on the web. In this case, the user 150 has permission to acquire content. ) And contrast can be set. For example, when the RI server 250 posts information such as a purchase price based on the content ID included in the trigger request message, the mobile terminal 200 is finally approved according to a signal from the user 150. Information about a plurality of contents to be obtained is transmitted to the RI server 250.

When the web transaction process is terminated according to the user's final approval, in step S1430, the RI server 250 generates a ROAP trigger message for the plurality of contents to be finally approved and transmits the generated ROAP trigger message to the mobile terminal 200.

When the ROAP trigger message is received, the mobile terminal 200 generates an RO request message (RO Request) for requesting RO of the plurality of DRM contents to be transmitted to the RI server 250 in step S1440.

The RI server 250 receiving the RO request message generates the ROs specified in the RO request message in step S1450 and includes the RO request message in the RO response message and transmits the RO request message to the mobile terminal 200.

The mobile terminal 200 receiving the RO response message may collectively obtain ROs included in the RO response message.

In the above embodiment, the web transaction process S1420 is described as being performed after the ROAP trigger request message is transmitted. However, it will be readily understood by those skilled in the art that the web transaction process S1420 may be performed at any time desired by the user and may be performed not only once but also several times. For example, before the ROAP trigger request message is transmitted, the web transaction process may be performed so that the mobile terminal 200 may transmit the ROAP trigger request message after the user completes all payment related operations. Alternatively, the payment may be changed by performing at least one web transaction process before and after the ROAP trigger request message is transmitted.

In the above, specific preferred embodiments of the present invention have been illustrated and described. However, the present invention is not limited to the above-described embodiment, and various modifications can be made by those skilled in the art without departing from the gist of the present invention attached to the claims. will be. For example, the present invention can be applied to collectively acquiring a plurality of DRM contents between a terminal such as a personal computer and a server or between a server and a server. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

As described above, the method and apparatus for acquiring the content rights object of the mobile terminal according to the present invention can improve the user's convenience by enabling the rights objects of a plurality of contents to be collectively acquired. In addition, by applying a discount rate according to the collective purchase, the user can benefit from the collective purchase and at the same time, improve the sales of the contents provider, thereby improving the related industry.

In addition, the present invention proposes a DCF structure for acquiring a plurality of rights objects collectively, thereby presenting an improved DRM related technology and contributing to the standardization work.

Claims (33)

Transmitting the integrated rights object request information for a plurality of contents; Transmitting an integrated rights object request message for the plurality of contents upon receiving the integrated right object permission information corresponding to the integrated right object request information; And a step of collectively acquiring rights objects for the plurality of contents from the integrated rights object allowance message upon receiving the integrated rights object allowance message corresponding to the integrated rights object request message. How to get an object. The method of claim 1, wherein the plurality of content An encrypted multimedia file, comprising: at least one of a file stored in a mobile terminal and a file stored in a content server of a wired / wireless communication network connected to the mobile terminal. The method of claim 1, wherein the integrated right object request information of the selected content is: And a content ID of the selected content. The method of claim 1, wherein the integrated rights object permission information of the selected content, And a rights object ID (roID) assigned to each of the plurality of contents. The method of claim 1, wherein the unified rights object request message, And a rights object ID (roID) of a plurality of contents included in the integrated rights object allowance information. The method of claim 1, wherein the unified rights object permission message (roResponse), And a rights object (RO) assigned to each of the plurality of contents. In the method for acquiring a content rights object of a mobile terminal using a content server and a rights issuing server, Generating a list of contents to be collectively acquired when inputting a selection command for a plurality of encrypted contents; Generating an integrated rights object request message for the collective acquisition request of the generated content list and transmitting the generated rights object request message to the rights issuing server; And a step of collectively acquiring a rights object for the selected contents from the integrated rights object permission message when receiving an integrated rights object permission message corresponding to the integrated rights object request message from the rights issuing server. How to obtain a content rights object. The method of claim 7, wherein the process of generating a list of contents to be collectively acquired, Searching for and outputting a list of content that does not meet any predetermined constraint criteria; Generating integrated rights object request information for the selected content upon inputting a selection command for any of the contents in the output list; Transmitting the generated integrated right object request information to the rights issuing server (RI); Outputting a content purchase cost upon receiving the integrated rights object permission information and the content purchase cost corresponding to the integrated right object request information from the rights issuing server (RI); And generating a list of contents to be collectively acquired consisting of the selected contents upon inputting an approval command for the output purchase cost. The method of claim 8, wherein the integrated rights object request information of the selected content, And a content ID of the selected content. The method of claim 8, wherein the integrated rights object permission information of the selected content, And a rights object ID (roID) assigned to each of the selected contents. The method of claim 8, wherein the unified rights object request message, And a selected content right object ID (roID) included in the integrated right object permission information of the selected content. The method of claim 8, wherein the unified rights object permission message, And a rights object required by the integrated rights object request message. The method of claim 7, wherein the process of generating a list of contents to be collectively acquired, Receiving price information of the content stored in the mobile terminal by accessing the right issuing server; Retrieving and outputting a content list that falls below a predetermined predetermined constraint criterion among contents stored in the mobile terminal; Calculating and outputting a purchase cost of the selected content upon inputting a selection command for any content in the output list; And generating a list of contents to be collectively acquired for the selected contents upon inputting an approval command for the output purchase cost. A memory for storing data including content; An input unit configured to input a selection command of a mobile terminal user for a plurality of contents; A display unit for displaying a list of the plurality of contents and a message inviting collective acquisition of the selected content rights object; An RF processor for transmitting and receiving a data signal with a rights object server for arbitrary content through a wired or wireless communication network; Generating the integrated right object request information of the plurality of selected contents from the list of the plurality of contents, generating an integrated right object request message for the collective acquisition request of the selected plurality of contents, and corresponding to the integrated right object request information; And a control unit which collectively obtains rights objects for the selected plurality of contents upon receiving the integrated right object permission information and the integrated right object permission message corresponding to the integrated right object request message. Object Acquisition Device. 15. The method of claim 14, wherein the plurality of content Apparatus for acquiring a content rights object of a mobile terminal comprising at least one of a DRM-protected content in which a constraint is exhausted by a predetermined criterion or more, and content having no RO received from another device. . The method of claim 14, wherein the unified rights object permission message, And a plurality of rights objects allocated to each of the arbitrary contents. When RO acquisition is required for at least one DRM content, generating a right object acquisition protocol (ROAP) trigger request message (ROAP-trigger request) for the DRM content and transmitting the same to a right issuer server; When a ROAP trigger corresponding to the ROAP trigger request message is received from the RI server, an RO request message for requesting a right object (RO) of at least one DRM content according to a user's setting is received. Generating and transmitting to the RI server; Acquiring at least one RO included in the RO response message when the RO response message corresponding to the RO request message is received. Way. 18. The method of claim 17, wherein the ROAP trigger request message is And a content ID of the selected content. 18. The method of claim 17, wherein the at least one DRM content is And at least one of contents stored in a mobile terminal and contents stored in a content server of a wired / wireless communication network connected to the portable terminal. 18. The method of claim 17, wherein transmitting the ROAP trigger request message The RI requesting the RO of the DRM content is selected by referring to the address information of the RI for collectively acquiring a plurality of ROs included in the header information of the at least one DRM content, and a ROAP trigger request message is sent to the selected RI address. And a method for acquiring the content rights object of the mobile terminal. 21. The method of claim 20, wherein URL information of the RI for collective purchase of the plurality of ROs is A method for acquiring a content rights object of a mobile terminal, comprising a BatchRIURL and optionally further including a BatchRIURLLength, and further included in a predetermined area of the DCF structure of the corresponding DRM content. 18. The method of claim 17, wherein transmitting the ROAP trigger request message Transmitting the ROAP trigger request message to a corresponding RI server by referring to an RI URL of one of the at least one DRM contents; Receiving an address to be redirected from the RI server; And retransmitting the ROAP trigger request message to the redirection address. 18. The method of claim 17, wherein transmitting the ROAP trigger request message Selecting an RI for collectively acquiring ROs of the at least one DRM content by referring to an RI URL address previously stored in the portable terminal, and transmitting a ROAP trigger request message to the URL of the selected RI; How to obtain a rights object. 18. The method of claim 17, wherein transmitting the ROAP trigger request message The mobile terminal requests a RI URL address for collectively acquiring ROs of the at least one DRM content to an RI server, and transmits a ROAP trigger request message to the received RI URL. Acquisition method. The method of claim 24, wherein the received RI URL is And storing the content rights object of the mobile terminal for collectively acquiring the ROs. 18. The method of claim 17, after the step of transmitting the ROAP trigger request message, A method for acquiring a content right object of a mobile terminal, characterized by further comprising performing a web transaction for setting a permission and a constraint of the content to be acquired. 18. The method of claim 17, wherein the ROAP trigger request message and the ROAP trigger message are transmitted according to one of an HTTP GET method and an HTTP POST method. 18. The method of claim 17, wherein the ROAP trigger message And a rights object ID (roID) assigned to each of the at least one content. 18. The method of claim 17, wherein the at least one DRM content is A method for acquiring a content rights object of a mobile terminal, characterized by including information for automatic rights object acquisition in the background in a DCF structure. 30. The method of claim 29, wherein said information is A method for acquiring a content right object of a mobile terminal, comprising one of a silent header and a preview header. The method of claim 30, wherein the information is The method of claim 1, further comprising at least one of permission, constraint, and purchase information. The method of claim 30, wherein the silent header and preview header is A method for acquiring a content rights object of a mobile terminal, comprising address information for collectively acquiring at least one content object. 19. The method of claim 18, wherein the ROAP trigger request message is If there is at least two upper layers of the license, the content rights object acquisition method of a mobile terminal, characterized in that it further comprises information for requesting a license of the upper layer.

Images