WO2005010762A1 - データ処理装置 - Google Patents
データ処理装置 Download PDFInfo
- Publication number
- WO2005010762A1 WO2005010762A1 PCT/JP2004/010882 JP2004010882W WO2005010762A1 WO 2005010762 A1 WO2005010762 A1 WO 2005010762A1 JP 2004010882 W JP2004010882 W JP 2004010882W WO 2005010762 A1 WO2005010762 A1 WO 2005010762A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- usage
- export
- permission information
- information
- restriction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
Definitions
- the present invention relates to a data processing device that processes data including rights data regarding the handling of digital content in electronic devices such as portable information terminals and portable telephone devices, and recording media such as memory cards.
- data processing device that processes data including rights data regarding the handling of digital content in electronic devices such as portable information terminals and portable telephone devices, and recording media such as memory cards.
- DRM Digital Rights Management
- a recording medium such as a memory card.
- the audio and video are integrated into the player software, when it is integrated into the transmission / reception and transfer software, and combinations thereof.
- content downloaded for a mobile information terminal is managed by a specific DRM system that manages the mobile information terminal, and recorded on a memory card managed by a different DRM system and used by other devices. I could't do it.
- Converting and outputting data so that it can be used between recording media and devices managed by such different DRM systems (hereinafter referred to as “export”) is the content user. It is convenient if it can be arbitrarily executed in such as.
- the usage right related to the acquired content has expired or the trial period has expired, it is also possible to obtain only the right data and update the usage right etc. to make the content available. ing. When updating such rights data, it has not been possible to handle exports between different DRM systems. Disclosure of the invention
- An object of the present invention is to provide a data processing apparatus capable of updating content overnight and making content available.
- the data processing device is a data processing device that processes data including right data relating to handling of digital content, and the data processing device obtains the right data corresponding to the digital content.
- Content handling means for handling the content data of the corresponding digital content according to the right data wherein the content handling means, when exporting the digital content, sends the corresponding right Convert the content handling and management system to fit Based on the distribution source information, the rights data corresponding to the content content obtained from the distribution source is acquired.
- FIG. 1 is a diagram showing a configuration of a content distribution system according to Embodiment 1 of the present invention
- FIG. 2 is a diagram showing an internal configuration of the mobile terminal device and the memory card according to the first embodiment
- FIG. 3 is a diagram showing the internal configuration of the server according to the first embodiment
- FIG. 4A is a diagram schematically showing an example of a data flow in the content distribution system according to the first embodiment
- FIG. 4B is a diagram schematically showing an example of a data flow in the content distribution system according to the first embodiment.
- FIG. 5A is a diagram schematically illustrating an example of a data flow in the content distribution system according to the first embodiment.
- FIG. 5B is a diagram illustrating a data flow in the content distribution system according to the first embodiment.
- FIG. 6 is a flowchart showing an operation procedure when updating the content rights information 1 according to the first embodiment
- FIG. 7 is a flowchart showing an operation procedure when updating right data of content according to Embodiment 2 of the present invention.
- FIG. 8 is a flowchart showing a rights-to-night conversion process employing the conversion rule of Case 1-1 according to Embodiment 3 of the present invention.
- FIG. 9 is a flowchart illustrating rights data conversion processing employing the conversion rules of Cases 1-2 according to Embodiment 3 of the present invention.
- FIG. 10 is a flowchart showing rights-to-night conversion processing employing the conversion rules of Cases 1-3 according to Embodiment 3.
- FIG. 11 is a flowchart showing rights-to-evening conversion processing employing the conversion rules of cases 1-4 according to the third embodiment.
- FIG. 12 is a flowchart showing rights-to-night conversion processing employing the conversion rules of cases 115 according to the third embodiment.
- FIG. 13 is a flowchart showing rights-to-night conversion processing employing the conversion rules of Cases 1 to 6 according to Embodiment 3.
- FIG. 14 is a flowchart showing rights-to-night conversion processing employing the conversion rule of Case 1- ⁇ according to Embodiment 3.
- FIG. 15 is a flowchart showing rights-to-night conversion processing according to the third embodiment, which employs the conversion rules of Cases 1 to 8.
- FIG. 16 is a flowchart showing rights-to-night conversion processing employing the conversion rule of case 119 according to the third embodiment.
- FIG. 17 is a flowchart showing a part of the rights-to-night conversion process employing the conversion rules of Cases 2-5 3 according to Embodiment 3.
- FIG. 18 is a flowchart showing a part of the rights data conversion process employing the conversion rules of Cases 2-5 3 according to Embodiment 3;
- FIG. 19 is a flowchart showing a part of the rights data conversion process employing the conversion rules of Cases 2-5 3 according to Embodiment 3;
- FIG. 20 is a flowchart showing a part of a rights-data conversion process employing the conversion rule of Cases 2-5 3 according to Embodiment 3;
- FIG. 21 is a flowchart showing a part of a rights data conversion process employing the conversion rules of Cases 2-5 3 according to Embodiment 3;
- FIG. 22 is a flowchart showing a part of a right-to-night conversion process employing the conversion rules of Cases 2-5 3 according to Embodiment 3;
- FIG. 23 is a flowchart showing a part of the rights-to-night conversion process employing the conversion rules of Cases 2-5 3 according to Embodiment 3.
- FIG. 24 is a flowchart showing a part of the right-to-night conversion process employing the conversion rule of Cases 2-57 according to Embodiment 3;
- FIG. 25 is a flowchart showing a part of the rights data conversion process employing the conversion rules of Cases 2-57 according to Embodiment 3;
- FIG. 26 is a flowchart showing a part of the rights data conversion process employing the conversion rule of Cases 2-57 according to Embodiment 3;
- Figure 27 shows the right to adopt the conversion rules of Cases 2-57 according to Embodiment 3.
- FIG. 28 is a flowchart showing a part of the rights data conversion process employing the conversion rules of Cases 2-57 according to Embodiment 3;
- FIG. 29 is a flowchart showing a part of the rights data conversion process employing the conversion rules of Cases 2 to 57 according to Embodiment 3, and the right data conversion process employing the conversion rules of Cases 2 to 57. Flowchart showing a part of
- FIG. 30 is a flowchart showing a part of the rights data conversion process employing the conversion rules of cases 2-57 according to the third embodiment.
- a mobile terminal device and a memory card are assumed to handle digital contents, and a digital rights management system (DRM system) that is different from the mobile terminal device and the memory card as a content handling management system is used.
- DRM system digital rights management system
- An example of managing the use of digital content in the environment in which it is used will be described.
- the rights data related to the handling of digital contents set for digital contents includes copyright information in the DRM system.
- rights rights include information indicating how to handle the content, information for protecting the copyright of the content, information on the copyright of the content, information on the use of the content, distribution and use of the content. It refers to information for management (restriction). '
- FIG. 1 is a diagram showing a configuration of a content distribution system according to Embodiment 1 of the present invention.
- content distribution is performed by a mobile terminal device such as a mobile phone device. Download content data from the source by downloading it and export it to a memory card (so that it can be used with different recording media and devices, and different DRM systems).
- a mobile terminal device such as a mobile phone device.
- Download content data from the source by downloading it and export it to a memory card (so that it can be used with different recording media and devices, and different DRM systems).
- the server of the content distribution source corresponds to the data distribution device
- the portable terminal device corresponds to the data processing device.
- the content distribution system includes a mobile terminal device 11 for downloading content, a server 12 as a content distribution source, a memory card 13 to which content is exported from the mobile terminal device 11, It is configured to have a communication network 14 that connects the terminal device 11 and the server 12.
- the portable terminal device 11 downloads the content data and the rights data distributed from the server 12 and downloads the contents data and the rights data in accordance with the first DRM system used in the mobile terminal device 11. It has the function of a data processing device that processes overnight.
- content can be used in accordance with content handling management by the first DRM system.
- examples of the content data include various data such as music, images, and characters, or a combination thereof.
- the use of content includes playing music content and displaying images and text content.
- the portable terminal device 11 is compatible with the second DRM system in order to export content data to media and devices under a different second DRM system environment such as a memory card 13. It has a function to convert the rights data as needed.
- “Compliant with the DRM system” means that usage (playback, recording, transfer, etc.) in accordance with the rules of the DRM system is possible.
- the portable terminal device 11 reacquires the rights related to the content that has already been downloaded and the like, and updates the usage rights of the content. It has a function to perform. By updating the rights data, the content can be used when the usage right has expired or the trial period has expired.
- Rights data includes, for example, information describing usage conditions including usage permission information and restriction information on content usage, such as the number of times the content can be used, the expiration date, and whether or not it can be exported to other DRM systems. It is.
- the server 12 has a function of a data distribution device that distributes content data and rights data to the portable terminal device 11.
- the server 12 in response to a request from the mobile terminal device 11, content data and right data relating to the content are prepared, provided to the mobile terminal device 11, and distributed.
- the rights data includes copyright information that describes usage conditions, including permissions and restrictions on the use of content for copyright protection, and usage rights.
- the content data is provided in a format suitable for the portable terminal device 11 of the distribution destination and the D'R'M system used therein.
- the memory card 13 is a recording medium for storing content data and rights data in a second DRM system different from the first DRM system used in the portable terminal device 11. is there.
- the communication network 14 is configured to include any of various communication means such as a mobile communication network, a telephone network, and an Internet connection network.
- FIG. 2 is a diagram showing an internal configuration of the portable terminal device 11 and the memory card 13 in the present embodiment.
- the portable terminal device 11 has a memory card 13 which can be detachably built in or can be inserted therein.
- the control unit 61, the transmitting / receiving unit 62, the memory 63, the memory card interface (I / F) unit 6 It has four.
- the control unit 61 is a block that centrally controls the operation of the entire portable terminal device 11, and includes a download unit 65 that downloads content data and rights data from the server 12 and rights data that is downloaded from the server 12. Content management unit that performs processing based on the content The content conversion unit 67 converts the content data and the rights data so as to correspond to the second DRM system in the memory system 13.
- the download unit 65 has a function of an acquisition unit described in the claims, and the content management unit 66 and the content conversion unit 67 are functions of the content handling unit described in the claims. The function is realized.
- the control unit 61 includes a processor that operates according to a predetermined program, and a software module that implements the functions of the above-described units.
- the content conversion section 67 may be provided in another device outside the portable terminal device 11.
- control unit 61 has a function of accessing the server 12 of the rights data distribution source that distributes the rights data by executing the application program stored in the memory 63.
- application program for accessing the server 12 browser software or the like that acquires and displays distribution information of the server 12 is used.
- the memory 63 has a function of a data storage unit described in the claims, and realizes a function as a data storage unit by storing content data and right data.
- the memory 63 specifies a content storage area 68 storing the downloaded content data, a rights storage area 69 storing the rights data, and a distribution source of the rights data. And a distribution source information storage area 70 for storing distribution source information.
- the transmission / reception unit 62 is a block for transmitting / receiving data to / from the server 12 via the communication network 14 using a known wireless communication device.
- the memory card interface section 64 is configured to have a force slot or the like for mounting and connecting the memory card 13.
- the memory card 13 has a function as a data holding unit for storing the content and the right data exported from the mobile terminal device 11.
- This memory card 13 has a content data holding area 71 for holding the exported contents data and a rights data holding area 7 2 for holding the rights data overnight.
- a distribution source information holding area for storing distribution source information for specifying a distribution source of the rights data.
- FIG. 3 is a diagram showing the internal configuration of the server 12 in the present embodiment.
- the server 12 includes a control unit 81, a transmission / reception unit 82, a memory 83, and a data storage unit .84.
- the control unit 81 is a block that controls the overall operation of the server 12, and distributes content and rights data in response to a content distribution request and a rights distribution request from the mobile terminal device 11.
- Means include a content data providing unit 85 for providing content data overnight, a rights data providing unit 86 for providing rights data, a content data providing unit and a distribution unit 87 for delivering rights data overnight.
- the control unit 81 is configured to include a processor that operates according to a predetermined program, and a software module that implements the functions of the above units.
- the control unit 81 acquires the terminal information of the accessed portable terminal device 11 and accesses the data storage unit 84 for storing information such as content data and rights information as needed. To obtain distribution information. Further, the control unit 81 provides the distribution source information for specifying the distribution source of the rights distribution to the distribution destination portable terminal device 11 when distributing the contents distribution. Server as distribution source information
- URL Uniform Resource Locator
- the data storage unit 84 stores the contents of various formats according to the device and medium of the content distribution destination, and various rights data corresponding to the DRM system of the content distribution destination.
- the content data distributed from the server 12 is prepared in advance by preparing a plurality of format contents in advance so as to be compatible with a plurality of devices, media, and a plurality of DRM systems. And may be provided by selecting from these, or preparing basic format content data, and converting the data each time according to the content distribution destination based on this data. It is also possible to provide.
- the rights A plurality of rights data may be prepared in advance to suit the number of DRM systems, stored in the data storage unit 84, and selected from these and provided. It can be generated or converted each time according to the destination or other distribution conditions and provided.
- the provider of content data (issuer) and the provider of rights data (issuer) may be the same or different, and the server 12 is appropriately configured according to the form of the provider. do it.
- the server 12 is represented by one device, but the server 12 may be constituted by a plurality of server devices having these functions.
- different server devices may be provided for the content data providing source and the rights data providing source, and the content data distribution server and the rights data distribution server may be configured separately.
- the transmission / reception unit 82 is a block for transmitting and receiving data to and from the mobile terminal device '11 via the communication network 14, and uses a known communication device.
- the memory 83 stores:-distribution information to the mobile terminal device 11;
- FIGS. 4 and 5 are diagrams schematically showing an example of a data flow in the present embodiment.
- Fig. 4A When acquiring and updating rights data, there are a total of four ways shown in Fig. 4A, Fig. 4B, Fig. 5A, and Fig. 5B to maintain the distribution source information and the content data. Conceivable. That is, when both the distribution source information 93 and the content data 91 are held in the mobile terminal device 11 under the first DRM system environment as shown in FIG. 4A, the distribution source information 93 as shown in FIG. 9A is stored in the mobile terminal device 11 under the first DRM system environment, and the content data 91 is stored in the memory card 13 under the second DRM system environment. As shown in FIG.
- the distribution source information 93 is stored in the second DRM system environment as shown in FIG. D RM
- the content data 91 is stored in the memory card 13 under the system environment
- the content data 91 is stored in the portable terminal device 11 under the first DRM system environment.
- Embodiment 1 an operation in the case where the distribution source information 93 is held in the portable terminal device 11 in the first DRM system environment as shown in FIGS. 4A and 4B will be described.
- the mobile terminal device 1 In the case where the rights data relating to the retained content data is acquired and the content is used in the memory card 13 in accordance with the content handling management by the second DRM system, first, the mobile terminal device 1 ⁇ Based on 93, the server accesses the server 12 which is the distribution source of the rights data and obtains the rights data overnight. Then, the acquired rights data is appropriately converted so as to be compatible with the second DRM system, and the converted rights data 92 is exported to the memory card 13. If the portable terminal device 11 holds the content data 91, the content data 91 is decrypted and encrypted, and in some cases, the data format is converted, and the encrypted content data is encrypted in accordance with the second DRM system. E 91 Export A to memory card 13.
- the rights data includes the conditions of use at the export destination, it must be compatible with the first DRM system used in the mobile terminal device 11 and handled in the mobile terminal device 11. Therefore, when the content is downloaded from the server 12 to the portable terminal device 11, it is provided as information corresponding to the first DRM system.
- conversion of rights and rights is required to conform to the second DRM system used in the memory card 13.
- FIG. 6 is a flowchart showing an operation procedure when updating the content right data in the first embodiment.
- the usage right of the right data such as the number of times of use of the content is consumed and disappears
- the reissued right data is acquired in order to obtain the additional usage right.
- the content management unit 66 determines from the memory 63 the distribution source information of the corresponding rights data. Information is obtained (step S601).
- the download unit 65 accesses the server 12 holding the rights data based on the obtained distribution source information, and requests the rights data—evening distribution (step S602).
- the control unit 81 of the server 12 receives the right data distribution request via the transmission / reception unit 82 (step S603). Then, the rights data providing unit 86 of the control unit 81 specifies the content for which the distribution request has been made, and if it can be reissued, reissues the rights data corresponding to the content and prepares it. (Step S604). Next, the distribution unit 87 distributes the right data to the portable terminal device 11 (step S605).
- the download unit 65 of the mobile terminal device 11 receives the distributed rights data (step S606) and stores it in the memory 63 of the mobile terminal device 11.
- Content- ⁇ ⁇ management unit 6 6 Obtains the rights data stored in the memory 63 (step S607), and manages the handling of the content based on the rights data. In such cases, after the acquired rights data and content data are decrypted, the content is used based on the rights data, and processing such as playback is performed.
- the content management unit 66 decrypts the obtained right data (step S608).
- the rights data is encrypted in conformity with the first DRM system used in the mobile terminal device 11 when downloading from the server 12. Therefore, decryption is performed using the encryption key of the first DRM system. If the right data has already been decrypted for use of the content, this step is omitted.
- the contents conversion section 67 converts the decrypted raw data overnight right data so as to be compatible with the DRM system of the memory card 13 as the export destination (step S609).
- the content conversion section 67 performs conversion such that the usage right based on the copyright in the right-hand data is equal to or smaller than the range before conversion.
- the handling permission information in the right is converted to a direction in which the content of the permission is reduced if there is no corresponding one in both the DRM system of the portable terminal device 11 and the memory card 13.
- the restriction information in the right is converted to the direction in which the restriction contents are increased. .
- a predetermined conversion rule is set in advance.
- use conditions related to permissions and restrictions that cannot be described in either the export source or export destination DRM system must be set in advance and converted according to the settings (default values are applied. Yes, etc., may be set as appropriate within a range that does not unduly expand the usage conditions.
- a consensus has been formed between the two DRM systems regarding the specifications, functions, capabilities, etc. of the usable content data format, etc., and a consensus has also been established regarding the rules for rewriting rights data. Keep it.
- Examples of rights data conversion rules are: (1) Convert the handling permission information supported by the export destination DRM system, (2) Handle the handling permission information not exported by the export destination DRM system Is deleted without conversion. (3) When restriction information is added to the handling permission information supported by the export destination DRM system, the restriction is not supported by the export destination DRM system. If there is information, the original handling permission information is (4) If the handling permission information supported by the export destination DRM system includes only the restriction information supported by the export destination DRM system, the handling permission information and the restriction information shall be deleted. Conversion, (5) Do not convert handling permission information that does not exist in the conversion source rights data, (6) Convert without ignoring restriction information that exists in the conversion source rights data, etc. Things.
- the content conversion section 67 encrypts the converted right data with the encryption key in the second DRM system used in the memory card 13 (step S610).
- the content management unit 66 obtains the content data subject to the rights data from the memory 63 and decrypts the content data. Do (Step S 6 1
- the content data is stored in the portable terminal device 11, the content data is encrypted in conformity with the first DRM system. Therefore, the content data is decrypted with the encryption key in the first DRM system. Then, the content conversion section 67 encrypts the content data of the decrypted raw data with the encryption key in the second DRM system used in the memory card 13 (step S61).
- steps S611 and S612 are omitted.
- the rights data re-issued and distributed from the server 12 in this way, downloaded by the mobile terminal device 11 and converted to conform to the second DRM system are the contents of the control unit 61.
- the output from the converter 567 is exported to the memory card 13 via the memory card interface section 64 (step S613), and stored and recorded in a storage area in the card.
- exporting content data export it in the same way as rights data.
- the usage rights and the like are updated by the right data acquired as described above, and the exported content can be used. Expiration of the playback permission date and time, the number of permitted playbacks, etc., expired, and the usage right expired The contents can be used again by re-acquiring and updating the rights.
- the rights data on the memory card 13 is updated in order to update the rights data in the mobile terminal device 11.
- the terminal device 11 needs to perform the right data update operation.
- Fig. 4B when the content data subject to the rights data is stored in the memory card 13, there is no need to perform the content export process, and the second DRM system in the memory card 13 is not required.
- the content data encrypted with can be used as it is.
- Embodiment 2 an operation in the case where the distribution source information 93 is stored in the memory card 13 in the second DRM system environment as shown in FIGS. 5A and 5B will be described. I do. Acquiring the rights data relating to the held content.-When using the content in the memory card 13 in accordance with the content handling management by the second DRM system, first, the portable terminal device 11 must The distribution source information 93 is obtained from the server 13, and based on the distribution source information 93, the right data is accessed by accessing the server 12 which is the distribution source in the evening. Then, the acquired rights data is appropriately converted so as to be compatible with the second DRM system, and the converted rights data 92 is exported to the memory card 13.
- FIG. 7 is a flowchart showing an operation procedure when updating the right of content in Embodiment 2.
- the usage right of the right data such as the number of times of use of the content is consumed and disappears, the reissued right data is acquired in order to obtain the additional usage right.
- the content management section 66 accesses the memory card 13 via the memory card interface section 6 4 to request the distribution source information of the rights data (step S701), and the memory card
- the distribution source information of the relevant right data is obtained from 13 (step S702).
- the download unit 65 accesses the server 12 that holds the rights information based on the acquired distribution source information, and requests distribution of the rights data (step S703).
- the control unit 81 of the server 12 receives the distribution request for the rights right via the transmission / reception unit 82 (step S704). Then, the rights data providing unit 86 of the control unit 81 identifies the content requested to be distributed and, if re-issueable, re-issues the rights data corresponding to the content and prepares it. (Step S705). Next, the distribution unit 87 distributes the rights data to the portable terminal device 11 (step S 706) 0
- the download unit 65 of the portable terminal device 11 receives the distributed rights data (step S707) and stores it in the memory 63 of the portable terminal device 11.
- the content management unit 66 acquires the rights data stored in the memory 63 (step S708), and manages the handling of the content based on the rights data.
- the portable terminal device 11 reproduces the content data, etc., it decrypts the acquired rights data and the contents data, and then executes the use of the content based on the rights data and reproduces the contents. And so on.
- the content management unit 66 decrypts the obtained right data (step S709). This step is omitted if the right data has already been decrypted for use of the content. Then, the content conversion section 67 converts the decrypted raw data overnight right data so as to be compatible with the DRM system of the memory card 13 as the export destination (step S710).
- the content conversion section 67 encrypts the converted rights data with an encryption key in the second DRM system used in the memory card 13 (step).
- the content management unit 66 obtains the content data subject to the right data from the memory 63 and decrypts it. Perform the conversion.
- the content conversion section 67 encrypts the decrypted raw data content data with an encryption key in the second DRM system used in the memory card 13. Note that when the content data is stored in the memory card 13 as shown in FIG. 5A, the above steps are omitted.
- the rights data re-issued and distributed from the server 12, downloaded by the mobile terminal device 11, and converted to be compatible with the second DRM system are converted to the content of the control unit 61.
- the data is output from the unit 67 and is exported to the memory card 13 via the memory card interface —face unit 64 (step S712), and is stored and recorded in the storage area in the card.
- exporting content evening, export it in the same way as right data.
- the usage rights and the like are updated by the right data acquired as described above, and the exported content data can be used.
- the distribution source information of the right data is stored in the memory card 13, when updating the right data, not only the portable terminal device from which the content is exported, but also other The right data update operation can be executed even by the portable terminal device of the above.
- the memory card itself holds the distribution source information of the right data, the right data can be updated regardless of which device the memory card is attached to.
- Fig. 5A if the content that is the subject of the rights data is stored on the memory card 13, there is no need to perform the content export process, and the second DRM on the memory card 13 is not necessary. Content data encrypted by the system can be used as is.
- the rights data does not necessarily have to be the same as the previously distributed rights data.
- the server may be set to change the usage conditions of the redistributed rights data.
- the rights data may be reset based on the information of the distribution destination such as the portable terminal device and the memory card at the time of re-delivery.
- the rights data is not limited to one type corresponding to the content, and a plurality of rights data can be provided for one content data. .
- different usage conditions can be set for each DRM system. For example, when charging for the updating of rights data, detailed pricing can be set according to the usage conditions classified in detail. In addition, distribution of usage fees can be set in detail according to complicated usage conditions such as the export destination and the number of permitted exports. Also, in the case of composite content, it is possible to provide a plurality of handling permission information in one piece of right data, for example, in relation to the playback of music content and the display of lyrics.
- the content export destination is not limited to a memory card, but a recording medium that records content data, a device that uses content playback, and a content playback program that runs on a computer. Any program that conforms to other DRM systems, such as content usage programs, can be applied.
- the export destination may be an external device or recording medium connected by wireless or wired communication means.
- the content data and rights data can be applied not only when downloading from a server using a portable terminal device, but also when acquiring data that has been pushed (sent) by e-mail or the like.
- the end user when the content is downloaded from the server by the mobile terminal device and exported to the memory card, the end user, such as the user of the content, uses the distribution source information of the rights Based on the rights data, the rights data can be acquired as appropriate, such as acquiring the rights data separately from the content overnight, or re-acquiring the rights data when the previously acquired usage right has expired. Can be updated at the destination. For this reason, it is necessary to acquire rights data in response to user requests, etc., and make the exported content available for use. Can do.
- rights information includes copyright information that describes usage conditions and permissions, including permissions and restrictions on the use of content for copyright protection.
- details of the conversion rules when converting rights data using handling permission information that specifically describes permissions and restrictions on the use of content.
- use restriction information is set as the above-described restriction information for restricting the use period and the number of times of use related to the method of using the content set in the handling permission information.
- the content distribution system of the third embodiment has the same configuration as the portable terminal device 11, the server 12, and the memory card 13 shown in FIGS. 1 to 3, and thus the illustration and description of the configuration are omitted. .
- the handling permission information is information for setting the usage method of the content and the usage permission and non-permission corresponding to the usage method, and is included in the right data.
- the content conversion unit 67 performs the processing permission included in the rights data decrypted by the content management unit 66.
- the rights data is converted based on the information settings.
- digital content can be broadly classified into the following two types.
- the DRM rights description model is roughly classified into the following three types: be able to.
- Rights-granting model Describes "how to use”. "Permission” and “No” for all handling permission information, such as "Reproduction (No) Permission” & “Display (No) Permission” & “Print (No) Permission” & “Execution (No) Permission” Described under the AND condition.
- Usage restriction model Describe “what restrictions (how) usage methods are allowed”. It can be reduced to all "rights and usage restriction models" as in the following example.
- 2-L Usage Restriction Model (Supports only one of two types of usage, 2-120)
- 2-K Usage Restriction Model
- 2- ⁇ ⁇ Rights Grant Model (Two types of usages are 2-121 (both types of usages are both supported separately)
- handling permission information is “permitted” at the export source, the rights data is converted and exported to the export destination so that the contents of the handling permission information are inherited. All other permission information above is set to "Not allowed”.
- the handling permission information is “permitted” at the export source
- the rights data is changed so that the export destination inherits the handling permission information. And export.
- all the usage restriction information for the relevant handling permission information at the export destination is set to “no restriction”. If “no limit” cannot be set, set the state with the least limit that can be set (however, set “non-permitted” for all other handling permission information at the export destination).
- handling permission information is "Permitted” at the export source 1-1-1. If the usage restriction information for the handling permission information of the exporter is all "no restrictions", the rights are delegated to the export destination so that the contents of the handling permission information are inherited. Convert and export (However, all other handling permission information at the export destination is set to "Not allowed”).
- the rights data should be inherited to the export destination and the equivalent use restrictions should be set. (However, all other handling permission information at the export destination is set to “Disallowed”).
- handling permission information of usage method X is “permitted” at the export source, convert and export the rights data so that the export destination inherits the handling permission information of usage method X ( However, for all other export permission information at the export destination, "Disable” is set.)
- the following conversion rule will be applied: 1. At the export source, only one of the two usage methods (X, Y) If at least one is “permitted”, the rights data is converted and exported so that the export destination inherits the two handling permission information contents. At that time, the usage restriction information for the relevant handling permission information at the export destination is set to “no restriction”. If "no limit" cannot be set, set the state that has the least limit that can be set (however, set "not allowed” for all other handling permission information at the export destination).
- the following conversion rule will be applied: 1. If the handling permission information indicating the two usages (X, Y) at the export source is “permitted”, the contents of the handling permission information indicating the two usages (X, Y) to the export destination Converts and exports the rights data so that is set to "permitted” (however, all other handling permission information at the export destination is set to "not permitted”). 2. If the handling permission information indicating the two methods of use (X, Y) at the export source is “not allowed”, the entire rights data is not exported.
- handling and permission information indicating the two methods of use (X, Y) at the export source are "permitted"
- the handling permission information content of method of use X is set to "permitted” for the export destination. Convert and export the rights as described above (However, all other handling permission information at the export destination is set to “Disallowed”).
- the following conversion rule will be applied: 1. If the handling permission information indicating the two usages (X, Y) at the export source is “permitted”, the contents of the handling permission information indicating the two usages (X, Y) to the export destination Convert and export rights data so that is set to “permitted”. At this time, all the usage restriction information for the relevant handling permission information at the export destination is set to “no restriction”. If “no limit” cannot be set, set the state that has the least limit that can be set (however, set “non-permitted” for all other handling permission reports at the export destination).
- the following conversion rule will be applied: 1. If the handling permission information indicating the two methods of use (X, Y) at the export source is “permitted”, the contents of the handling permission information indicating the two methods of use (X, Y) to the export destination Convert and export rights rights so that is set to "Allowed.” At this time, all the usage restriction information for the relevant handling permission information at the export destination is set to “no restriction”. If “No limit” cannot be set, set the state with the least limit that can be set (however, set “Disallow” for all other handling permission information at the export destination).
- handling permission information indicating the two methods of use (X, Y) at the export source is "Permitted”
- the handling permission of the method of use X is set to "Permitted” for the export destination. Convert and export the rights as set.
- all the usage restriction information for the relevant handling permission information at the export destination is set to “no restriction”. If “no limit” cannot be set, set the state with the fewest restrictions that can be set (however, set “not allowed” for all other handling permission information at the export destination).
- the following conversion rule will be applied: 1. If the handling permission information indicating the two methods of use (X, Y) at the export source is "permitted”, set the handling permission information content of method of use Y to "permitted” for the export destination. Then convert and export the rights. At this time, all the usage restriction information for the relevant handling permission information at the export destination is set to “no restriction”. If “no limit” cannot be set, set the state with the fewest restrictions that can be set (however, set “not allowed” for all other handling permission information at the export destination). 2. If the handling permission information indicating the two methods of use (X, Y) at the export source is “Disallowed”, the entire right is not exported.
- handling permission information of the method of use X is "permitted" at the export source, 'convert and export the right data so that the export destination inherits the handling permission information of the method of use X. (However, "Disable” is set for all other handling permission information at the export destination.) ' 1
- handling permission information of usage method X is “permitted” at the export source, convert and export the rights data so that the export destination inherits the handling permission information of usage method X ( However, for all other export permission information at the export destination, "Disable” is set.)
- the following conversion rule will be applied: 1. If the handling permission information of usage method X is "Permitted" at the export source, Convert and export the rights so that the export destination inherits the handling permission information of usage method X. At this time, all usage restriction information for the handling permission information at the export destination is set to “no restriction”. If “no restrictions” cannot be set, set the state with the least restrictions that can be set (however, set “disallowed” for all other handling permission information at the export destination).
- handling permission information of usage method X is "Permitted:
- all usage restriction information for the handling permission information at the export destination is set to “no restriction”. If “no restrictions” cannot be set, set the state with the least restrictions that can be set (however, set “disallowed” for all other handling permission information at the export destination).
- handling permission information of usage method ⁇ is “permitted” at the export source, convert and export the rights and rights so that the contents of the handling permission information of usage method ⁇ ⁇ ⁇ ⁇ will be inherited to the export destination. I do.
- all usage restriction information for the handling permission information at the export destination is set to “no restriction”. If “no restrictions” cannot be set, set the state with the least restrictions that can be set (however, set “not allowed” for all other handling permission information at the export destination).
- handling permission information of the method of use Y is "permitted" at the export source, convert the rights and export it so that the export destination inherits the handling permission information of the method of use Y. I do.
- all usage restriction information for the handling permission information at the export destination is set to “no restriction”. If “no restrictions” cannot be set, set the state with the least restrictions that can be set (however, set “disallowed” for all other handling permission information at the export destination).
- the export destination is set to “no restriction” for all the use restriction information of the method of use Y. Convert and export. If "no limit" cannot be set, set the status to the lowest limit that can be set.
- All the usage restriction information for the handling permission information of the method of use X at the export source is “no restriction” and at least one of the usage restriction information for the handling permission information of the usage method Y of the export source is “restricted”. If there is something other than "None”, convert and export the rights data so that the handling permission information of usage method X is set to "Permitted” for the export destination (however, other handling of the export destination) All permission information is set to "not allowed”).
- All usage restriction information for the handling permission information of the method of use Y at the export source is "no restriction", and at least one of the usage restriction information for the handling permission information of the method of use X at the export source is “restricted”. If there is anything other than "None”, convert and export the rights data so that the handling permission information of usage method ⁇ ⁇ ⁇ ⁇ is set to "Permitted” for the export destination. For all the handling permission information, set “Not allowed”.)
- the contents of the handling permission information for both usage methods X and Y should be changed to " Convert and export the rights data so that it is set to "permitted” and set the same usage restrictions. (However, all other handling permission information at the export destination is set to "disallowed.” ).
- the usage restriction of the handling permission information of X can realize the same usage restriction as that of the export source, and the usage restriction of the handling method of Y at the export destination Cannot achieve the same usage restrictions as the export source
- handling of usage method Y Convert and export the rights data so that only the permission information is set to "permitted” and the usage restriction information of the handling information for usage method Y is set to the same usage restrictions as the export source. (However, all other handling permission information at the export destination is set to “Disallowed”).
- the use restriction of the handling permission information of X can be described in a direction in which the use restriction is stricter than that of the export source. If it is not possible to describe in a direction that makes the usage restrictions stricter than the export source due to the usage restrictions of handling information and permission information, set only the handling permission information content of usage method X to “permitted” and use Method X Handling Convert the rights data and export it so that the usage restriction information content of the permission information is set as close as possible to the export source with stricter usage restrictions. For all other handling permission information, set “Not allowed”). : '
- the usage restriction of the handling permission information of Y can be described in a direction that makes the usage restriction stricter than the export source, and the use of the export destination DRM If it is not possible to use a method that restricts the use of the handling permission information in Method X so that it is more restrictive than the export source, set only the handling permission information in Method Y to “permitted”, and Handling of usage method Y Convert the rights information and export it so that the contents of the usage restriction information of the permission information are set as close as possible to the export source with the stricter usage restrictions. All other handling permission information at the export destination is set to “Disallowed”).
- the destination DRM usage method The usage limitation of the handling permission information of Y is the same as the export source. If it can be realized, set the handling permission information content of usage method Y to "Allow”, and set the usage constraint information content of handling permission information of usage method Y at the export destination equivalent to that at the export source. In this way, the rights are converted and exported (however, all other handling permission information at the export destination is set to “not permitted”).
- the handling permission information of usage method ⁇ Set the content to "Permitted” and set the usage restriction information of the handling permission information of the method of use at the export destination ⁇ so that the usage restriction is set as close as possible to the export source. Convert the data and export it (except that all other permission information at the export destination is set to “Disallowed”).
- the handling permission information on usage method X can be described in a direction that makes the usage restriction stricter than the export source, the handling permission information on usage method X Set the content to "Permitted” and set the usage restriction information of the handling permission information of the export destination X to the usage restriction information as close as possible to the export source. Convert the data and export it (however, set “Disallowed” for all other handling permission information at the export destination).
- the content of the usage restriction information for usage Y is Set the same usage restrictions as the export source, and set the usage restrictions information content of usage method X so that the usage restrictions are stricter for the export source. To convert and export.
- the usage restriction of the export destination DRM usage method Y can achieve the same usage restriction as the export source, the usage restriction of the export destination usage method Y will have the same usage restrictions as the export source. Convert and export the rights as set.
- the usage restrictions information of the export destination X is converted and exported so that the usage restrictions are set to the same usage restrictions as the export source.
- the usage method of the export destination DRM can be described in a direction that makes the usage restriction stricter than the export source using the usage restriction of Y
- the content of the usage restriction information of the usage method Y of the export destination is Convert and export rights data so that the usage restrictions are set as close as possible to the export source.
- handling permission information indicating the two methods of use (X, Y) at the export source is “not permitted”, the entire right data is not exported. .
- the contents of the handling permission information on both the usage methods X and Y should be changed to " Convert and export the rights data so that it is set to "permitted” and the equivalent usage restrictions are set (however, all other handling permission information at the export destination is set to "not permitted”).
- the usage of usage X Convert and export the rights data so that only the permission information is set to “permitted” and the usage restriction information of the handling permission information for usage method X is set to the same usage restrictions as the export source. (However, all other handling permission information at the export destination is set to “Disallowed”).
- the usage restriction of the handling permission information of Y can realize the same usage restriction as the export source, and the usage restriction of the usage of the handling method of the export destination DRM X When the same usage restrictions as the export source cannot be achieved
- the export destination DRM usage method X cannot be described in a direction that makes the usage restriction stricter than the export source due to the usage restriction of X
- the usage restriction information content of usage method Y is the same as the export source Convert and export rights data so that usage restrictions are set.
- Usage method of export destination DRM The usage restriction of X can be described in a direction that makes the usage restriction stricter than that of the export source, and the usage restriction of export destination DRM Y If it is not possible to describe in a direction that tightens the usage restrictions, the right to use the usage restriction information of usage method X should be set as close as possible to the export source. Convert and export data.
- the method of using the DRM at the export destination The use restriction of Y can be described in a direction in which the use restriction is stricter than that of the export source. If it is not possible to describe in a direction that makes the usage restrictions stricter than the export source due to the restrictions, the usage restriction information content of usage method X shall use the usage restrictions that are as strict as possible for the export source. Convert and export rights data as configured.
- the rights data is set so that the handling permission information of usage method X is set to “permitted” for the export destination. Is converted and exported (however, all other handling permission information at the export destination is set to “Disallowed”).
- handling permission information indicating the method of use X at the export source is “not permitted”, the entire rights data is not exported.
- the usage restriction of the usage method X of the export destination DRM can be described in a direction that makes the usage restriction stricter than that of the export source
- the content of the usage restriction information of usage method X is exported to the export source. Convert and export rights rights so that the usage restrictions are stricter and the usage restrictions are set as close as possible o
- handling permission information indicating the method of use Y at the export source is “not permitted”, the entire rights data is not exported.
- handling permission information indicating the method of use Y at the export source is “not permitted”, the entire rights data is not exported.
- the usage method ⁇ Set the content of the handling permission information to “permitted” and set the content of the usage restriction information of the handling permission information to Convert and export (However, all other handling permission information at the export destination is set to “Disallowed”).
- the usage restriction of the usage method Y of the export destination DRM can be described in a direction that makes the usage restriction stricter than that of the export source
- the content of the usage restriction information of usage method Y is exported to the export source. Convert and export the rights data so that the usage restrictions are set as tightly as possible.
- the following conversion rule will be applied: 1.
- the usage constraint information on the method of use X exists at the export source 1-1. If the usage constraint information on the method of use X at the export source is all "no restrictions", the method of use X for the export destination Convert and export the rights data so that the contents of the handling permission information regarding the information are set to “permitted” (however, set “not allowed” for all other handling permission information at the export destination).
- both usage methods X and ⁇ Set the handling permission information content to “permitted” and set the usage constraint information content of usage permission information of usage method X to be the same usage constraint as the export source.
- Use restriction information of handling permission information of usage method ⁇ Content Converts and exports the rights data so that the usage restrictions are set as close as possible to the export source (however, all other handling permission information at the export destination is not ⁇ : Allowed ”).
- both usage methods X and Y Set the handling permission information content to "permitted” and set the usage constraint information content of usage permission information of usage method Y to be the same usage constraint as the export source, and use the usage constraint information of usage permission information of usage method X
- the contents are converted and exported so that the usage restrictions are set as close as possible to the export source so that the usage restrictions are set as strict as possible. (However, all other handling permission information at the export destination is " "Disallowed").
- the usage method for Y Convert and export the rights information so that only the permissible information content is set to “permitted” and the usage restriction information content of the handling permission information for usage method Y is set to the same usage restrictions as the export source. (However, all other handling permission information at the export destination is set to “Disallowed”). 1 — 4. How to use DRM at the export destination When the usage restrictions on the handling permission information for both X and Y cannot be used to achieve the same usage restrictions as at the export source
- the usage permission of the handling permission information of the export destination DRM can achieve the same usage restriction as the export source, the usage permission of the usage method ⁇ Set the permission information to "permitted” and convert the rights data so that the usage restrictions of the handling permission information for the method of use Y at the export destination are set to the same restrictions as those at the export source. (However, all other handling permission information at the export destination is set to “Disallowed”). .
- the export destination DRM can describe the usage restriction information more strictly than the usage restriction information for the two handling permission information at the export source, the content of the handling permission information for the export destination Is set to ⁇ Allow, '' and the content of the usage restriction information of the handling permission information at the export destination is converted so that the usage restrictions are set as close as possible to the export source. And export (however, all other handling permission information at the export destination is set to “Disallowed”).
- usage constraint information on usage method X exists at the export source 1-1.
- Usage X Handling permission Set the information content to "Allow” and export the usage restriction information of the handling permission information of Usage X at the export destination by setting the usage restrictions equivalent to the export source. (However, all other handling permission information at the export destination is set to "Not allowed”).
- the usage restriction of the export source X can realize the same usage restriction as the export source, and the usage restriction of the export destination DRM Y can use the same usage restriction as the export source. Cannot be realized
- the usage restriction of the DRM can be described in a direction that makes the usage restriction stricter than that of the export source, the usage restriction information of the usage method Y of the export destination The content is converted and exported so that the usage restrictions are set as close as possible to the export source. .
- the usage of usage X Convert and export the rights data so that only the permission information is set to “permitted” and the usage restriction information of the handling permission information for usage method X is set to the same usage restrictions as the export source. (However, all other handling permission information at the export destination is set to “Disallowed”).
- Usage method of export destination DRM The usage restriction of the handling permission information of Y can realize the same usage restriction as the export source, and the usage restriction of the usage method of the export destination DRM X When the same usage restrictions cannot be realized
- the use restriction of the handling permission information of X can be described in a direction that makes the use restriction stricter than the export source, and the use of the export destination DRM If it is not possible to describe the usage restriction information in a direction that makes the usage restriction stricter than the export source due to the usage restriction of the handling permission information of Y. If the handling permission information of usage method X alone is set to ⁇ permitted, '' and How to use X Handling The usage restriction information of the permission information is converted and exported so that the usage restriction contents of the export source are set as close as possible to the export source (however, the export destination is All other handling permission information is set to “Not allowed”.) -1-4-3.
- the usage restriction of the handling permission information of the usage method Y of the export destination DRM can achieve the same usage restriction as the export source, set the handling permission information content of the usage method Y to "Permitted”. Convert and export the rights and rights so that the same usage restrictions are set (however, set all the other handling permission information at the export destination to “permitted”).
- Usage method of export destination DRM The usage restriction of Y can be described in a direction that makes the usage restriction stricter than that of the export source, and the usage restriction of export destination DRM X If it is not possible to describe the usage restriction in a direction that makes the usage restriction stricter than the source, use the usage restriction information of usage method Y so that the usage restriction is set as close as possible to the export source. Convert and export rights data.
- usage constraint information on usage method X exists at the export source 1-1. If all the usage constraint information on the handling permission information at the export source is "no restrictions", the usage method X is used at the export destination Convert and export rights rights so that the handling permission information content of the export is set to "permitted” (however, set “not permitted” for all other handling permission information at the export destination) .
- usage constraint information on usage method X exists at the export source 1- 1. If all the usage constraint information on the handling permission information at the export source is "no restrictions", use method X at the export destination Convert and export the rights data so that the content of the handling permission information is set to “permitted” (however, set “non-permitted” for all other handling permission information at the export destination). -1-2. If there is at least one usage restriction information for the handling permission information of the export source other than "no restriction", the entire right data will not be exported.
- usage constraint information on usage method X exists at the export source 1-1. If the usage constraint of usage method X at the export destination DRM can achieve the same usage constraint as the export source, the equivalent Converts and exports rights as if setting usage restrictions.
- usage constraint information on usage method X exists at the export source 1— 1. If the usage constraint on usage method X at the export destination DRM can achieve the same usage constraint as the export source, the equivalent usage constraint Convert and export the rights data as if you set
- the method of use at the export destination Convert and export the rights data so that the handling permission information content of Y is set to “permitted” (however, set “non-permitted” for all other handling permission information at the export destination) ).
- the usage restriction information content of the usage method ⁇ is exported to the export source.
- the rights data is converted and exported so that the usage restrictions are set as tightly as possible.
- usage constraint information on usage method Y exists at the export source 1-1. If the usage constraint on usage method Y of the export destination DRM can achieve the same usage constraint as the board source, the equivalent usage constraint Convert and export the rights data as if you set
- both the export source DRM and the export destination DRM adopt “1—A: Rights Permission Model” in Table 1 above, and both the export source DRM and the export destination DRM use “
- An example is shown in which the handling permission information for "reproduction” can be applied. More specifically, in the example of Table 3, the export source DRM is applicable to three types of handling permission information, "execute”, “print”, and “playback”, and the handling permission information related to "display” is not applicable.
- the export destination DRM is an example of rights data conversion processing when the handling permission information is “execute”, “display”, and “play”, and the handling permission information related to “printing” is a DRM that cannot be applied.
- the conversion rule for converting the rights data is to apply the above case 1-1 and (“Digital to be exported” ⁇ Only one type of usage is available for content '' and ⁇ Only handling permission information is applicable at the export source DRM, and only handling permission information is applicable at the export destination DRM '' Yes,) "1. If the handling permission information on the method of use related to the content exists in both the export source and the export destination, 1-1. If so, convert and export the rights data so that the export destination inherits the handling permission information. Dyed other handling permission information on the export destination is set all "not permitted"), 1- 2. The handling permission information if it is "not permitted" in E-click Sport source, does not perform the export of the right data. "
- FIG. 8 shows the rights data conversion process in case 11-11 executed based on the settings of the handling permission information in the export source DRM in the matrix table shown in Table 3 above. This will be described with reference to FIG.
- This right data conversion processing is executed in the content conversion section 67.
- the content conversion section 67 first determines whether or not the handling permission information of the usage method (playback) related to the audio content exists in both the export source DRM and the export destination DRM (step S8001). ). If the content conversion unit 67 determines that the handling permission information of the method of use (playback) does not exist in both (step S801: NO), the process proceeds to step S802, This process ends without exporting the rights data.
- step S800 determines whether the handling permission information is set to "permitted” at the export source.
- the handling permission information for the usage method “playback” related to the audio content is set to “ ⁇ : usage permission”. Therefore, the content conversion unit 67 determines that the handling permission information is set to “permitted” at the export source (step S803: YES), and proceeds to step S804.
- the rights data is converted and exported so that the settings of the handling permission information are inherited to the export destination, and all other handling permission information at the export destination is set to be disallowed.
- the processing ends.
- the handling permission information for the usage method “playback” related to the audio content is set to “X: use not allowed”. Therefore, the content conversion section 67 determines that the handling permission information is not set to “permitted” in the export source DRM (step S803: NO), and proceeds to step S802. Then, the processing is terminated without exporting the right data.
- the handling permission information on the usage corresponding to the digital content is applicable in DRM
- the handling permission at the export source is related to the usage corresponding to one type of digital content.
- the export destination DRM has the same effect as the export source DRM.
- Rights data can be converted to use rights and the resulting exported digital Content to use how of, it is possible to perform a proper export UNA'll be limited according to the permitted usage in export original D RM.
- the conversion rules for converting the rights data are as described in “1. If the handling permission information of the related usage method exists in both the export source and the export destination, ("Only one type of usage method is available for the digital content to be exported" is displayed. Only the handling permission information can be applied in the DRM, and both the handling permission information and the restriction information on the handling permission information can be applied in the export destination DRM. ")" 1-1. If the permission information is "permitted” at the export source, the rights data is converted so that the export destination inherits the attacking permission information. And export. At this time, all the usage restriction information for the handling permission information at the export destination is set to “no restriction”.
- the content conversion unit 67 stores the handling permission information of the usage (playback) related to the audio content in both the export source and the export destination. It is determined whether or not it exists (step S901). If the content conversion unit 67 determines that the handling permission information of the method of use (playback) does not exist in both the export source and the export destination (step S901: O), the process proceeds to step S902. This process ends without exporting the rights data. If the content conversion unit 67 determines that the handling permission information of the method of use (playback) exists in both the export source and the export destination (step S901: YES), the process proceeds to step S903. Then, it is determined whether or not the handling permission information is set to “permitted” at the export source.
- step S904 the content conversion section 67 determines whether or not “unlimited” is set as the usage restriction information related to the handling permission information at the export destination. If it is determined that “no limit” can be set (step S904: YES), the content conversion section 67 proceeds to step S905.
- step S905 the content conversion section 67 inherits the setting contents of the handling permission information for the export destination, and sets all the usage restriction information related to the handling permission information to “no restriction”. Then, the rights data is converted and exported so that all other handling permission information at the export destination is set to "not permitted", and this processing ends.
- step S904 determines that “no restriction” cannot be set for the usage restriction information related to the handling permission information at the export destination (step S904: NO)
- the process proceeds to step S906.
- the rights data is converted so that the export destination inherits the setting contents of the handling permission information and sets the usage restriction information related to the handling permission information to a state where it can be set but the number of restrictions is small. And export. Also, in step S906, the content conversion section 67 sets “X: use prohibited” for all handling permission information of the export destination other than the handling permission information. If the content conversion unit 67 determines in step S903 that the handling permission information is set to “not permitted” at the export source (step S903: NO), Proceeding to step S902, the export of the rights is not performed, and the process ends.
- the export source and export destination are the DRM models as described above, by performing the above-mentioned determination, it is possible to appropriately determine whether or not to export, and In this case, it is possible to rationally convert the rights data at the export destination DRM so that the usage rights are the same as those at the export source or the usage rights are such that the rights are reduced.
- the export source DRM adopts “1—A: license model” in Table 1 above
- the export destination DRM adopts “1—C: Usage restriction model” in Table 1 above.
- the handling permission information can be applied by the export source DRM
- the export destination DRM can be used for the content. 2 shows an example in which usage restriction information can be applied.
- the export source DRM is a DRM to which four of "execute”, “display”, “print”, and “playback” can be applied as handling permission information
- the export destination DRM is This is an example of rights-to-evening conversion processing in the case of a DRM in which “use count” is applicable as usage restriction information.
- the number of uses as “unlimited” as the “number of uses” as the use restriction information of the expo one-stop DRM in this case.
- the conversion rule for converting the rights data is to apply the above cases 1-3 and (“Export ⁇ Only one type of usage that can be used in the target digital content '', ⁇ Only the handling permission information can be applied at the export source DRM, and only the usage restriction information applies at the export destination DRM '' Yes, it is possible.) "1. If the handling permission information of the usage related to the content exists at the export source, If the handling permission information on the usage related to the content is "permitted" at the export source, the rights data should be set so that all usage restriction information on the usage related to the content at the export destination is set to "no restriction". Convert and export.
- FIG. 10 shows the rights-to-data conversion process in case 13 to 13 executed based on the setting contents of the handling permission information in the export source DRM of the matrix table shown in Table 4 above. This will be described with reference to the flowchart shown in FIG. This right data conversion processing is executed in the content conversion section 67.
- the content conversion section 67 first determines whether or not the handling permission information of the usage method (playback) related to the audio content exists in the export source DRM (step S1001). If the content conversion unit 67 determines that the handling permission information of the method of use (playback) does not exist at the export source (step S1001: NO), the process proceeds to step S1002. Then, the rights data is not exported, and the process ends.
- step S1003 If the content conversion section 67 determines that the handling permission information of the method of use (playback) exists at the export source (step S1001: YES), the content conversion section 67 performs step S1003. Then, it is determined whether or not the handling permission information is set to “permitted” at the export source. In Table 1 in Table 4, the handling permission information for the usage method “Reproduction” related to the audio content is set to “ ⁇ : Usage permission”. Therefore, the content conversion section 67 determines that the handling permission information is set to “permitted” at the export source (step S 10). 0 3: YES), proceeding to step S 1004, and judging whether or not the use restriction information of the use method related to the handling permission information can be set to “no restriction” for the export destination I do.
- Pattern 1 in Table 4 considers a case where the number of times “unlimited” can be set as the usage restriction information “number of uses” of the usage method “reproduction” related to the handling permission information. Therefore, the content conversion section 67 determines that it is possible to set “no limit” (step S 1004: Y E S), and shifts to step S 1005.
- step S1005 the content conversion section 67 sets all the usage constraint information of the usage method related to the audio content to "unlimited” for the export destination, and sets other usage constraints.
- the rights data is converted and exported so that the information is set to a content meaning “unavailable”, and the process ends.
- step S104 the content conversion unit 67 sets, for the export destination, the usage restriction information of the usage method "reproduction” related to the handling permission information to "no restriction". If it is determined that the content cannot be used (step S1004: NO), the process proceeds to step S106, and the export destination is set with respect to the usage restriction of the usage method related to the content.
- the rights data is converted and exported so as to set the state with the least restrictions possible, and this processing ends.
- step S103 determines in step S103 that the handling permission information is set to "not permitted” at the export source, that is, in the case of pattern 2 in Table 4, Then, the process proceeds to step S102, where the rights data is exported, and the process ends.
- the usage method is to export one type of digital content
- the export source DRM adopts the rights permission model
- the export destination DRM adopts the use restriction model And expo -
- the usage method is Export is performed by executing rights data conversion processing based on the conversion rules shown in Cases 13 and 13 based on the settings of handling permission information at the export source related to the usage method corresponding to one type of digital content.
- the rights data can be converted so that the usage rights are the same as in the export source DRM, or the rights are reduced, but the usage rights are as close as possible.
- the export source DRM adopts “1—B: Rights permission + use restriction model” in Table 1 above
- the export destination DRM is A specific example of rights data conversion processing when employing “1—A: rights permission model” in Table 1 will be described with reference to the flowchart shown in FIG.
- the conversion rule for converting the rights data is to apply the above case 14 to (“Export Only one type of usage is available for the target digital content '', and both the handling permission information and the restriction information on the handling permission information can be applied at the export source DRM, and the export Only the handling permission information is applicable in the destination DRM ”, and“ 1.
- the handling permission information of the usage related to the content exists in both the export source and the export destination, 1-1. If the handling permission information is "permitted” at the export source, 1-1-1. All the usage restriction information for the relevant handling permission information at the export source is " If the limit without ", to inherit the handling permission information content for the E-click Sport destination, export to convert the right de Isseki (However, other handling permission information on the export destination All are set to "Disallowed”). 1—1—2. If there is at least one usage restriction information other than “no restriction” for the relevant handling permission information at the export source, the right data will not be exported. If the handling permission information is "not permitted” at the export source, the right data will not be exported. 2. If there is no usage permission information on the usage related to the content at the export destination, the right data will not be exported. 3. If the handling permission information of the usage related to the content does not exist at the source of the export, the right data will not be exported. "
- the content conversion section 67 determines whether or not the handling permission information of the usage method (playback) associated with the audio content exists in both the export source and the export destination (step S111). ). If the content conversion unit 67 determines that the handling permission information of the method of use (playback) does not exist in both the export source and the export destination (step S111: NO), the step S1 The process proceeds to 102, and the right data is not exported, and the process ends.
- step S111 it is determined whether or not the handling permission information is set to "permitted” at the export source. If the content conversion unit 67 determines that the handling permission information is set to “permitted” at the export source (step S 1103: Y E S), the process proceeds to step S 110.
- step S111 the content conversion section 67 determines whether or not all of the usage restriction information related to the handling permission information of the export source is "no restriction”. Is determined. If the content conversion unit 67 determines that all are set to “no limit” (step S1104: YES), the process proceeds to step S1105.
- step S1105 the content conversion section 67 inherits the setting contents of the handling permission information for the export destination, and sets "non-permission" for all other handling permission information. Then, the rights data is converted and reported, and the process ends.
- step S113 determines in step S113 that the handling permission information is not set to "permitted” at the export source (step S1103: NO).
- step S1102 the process ends without exporting the rights data.
- step S1104 determines in step S1104 that all the usage restriction information related to the handling permission information of the export source is not set to "no restriction”
- the content conversion unit 67 (S111: NO)
- the process proceeds to step S1102, and the right data is not exported, and the process ends.
- the export source and export destination are such a DRM model
- the rights When exporting data, rationally convert the rights so that the rights at the export destination DRM are the same as those at the export source or the rights are reduced. It becomes possible.
- the conversion rules for converting the rights data are as follows: Applying the above cases 1-5, ("Only one type of usage is available for the digital content to be exported” and "Permission to handle both the export source DRM and the export destination DRM Both the information and the restriction information on the handling permission information are applicable.) 1) If the handling permission information on the usage related to the content exists in both the export source and the export destination, 1-1 If the handling permission information is “permitted” at the export source, 1-1-1. If the same usage restrictions can be realized in the export destination DRM, the contents of the handling permission information are inherited to the export destination. And change the rights so that the same usage restrictions are set. (However, all other handling permission information below "). 1—1
- the content conversion section 67 It is determined whether the handling permission information of the method (playback) exists in both the export source and the export destination (step S1201). When the content conversion unit 67 determines that the handling permission information of the method of use (playback) does not exist in both the export source and the export destination (step S1201: .NO), the process proceeds to step S Proceeding to 1 202, the rights data is not exported and this process ends.
- step S1221 determines that the handling permission information of the usage (playback) exists in both the export source and the export destination (step S1221: YES). Proceeding to step S123, it is determined whether the handling permission information is set to "permitted” at the export source. If the content conversion unit 67 determines that the handling permission information is set to “permitted” at the export source (step S1203: YES), the content conversion unit 67 proceeds to step S1204. Transition.
- step S124 the content conversion section 67 determines whether or not the export destination can realize the same usage restriction as the export source with respect to the usage restriction information related to the handling permission information. If the content conversion unit 67 determines that the export destination cannot realize the same usage restriction as the export source (step S1204: NO), the process proceeds to step S125.
- step S125 the content conversion section 67 determines whether or not the export destination can realize a stricter usage constraint than the export source with respect to the usage constraint information related to the handling permission information. If the content conversion unit 67 determines that the use of the export destination can be more restricted than the export source (step S125: YES), the process proceeds to step S122.
- step S122 the content conversion unit 67 sets the export destination to the content that inherits the setting of the handling permission information, and sets the usage constraint information related to the handling permission information to the export destination.
- Set usage restrictions that are stricter but closer to the export source, and other handling at the export destination The rights data is converted and exported so that all the permission information is set to "not permitted", and the process ends.
- step S1204 determines The process moves to S122.
- step S 1207 the content conversion section 67 sets the export destination to the content that inherits the setting content of the handling permission information, and sets the usage constraint information related to the handling permission information.
- the rights data is converted and exported so that the usage restrictions are set to be equivalent to those of the export source, and all other handling permission information at the export destination is set to “disallowed”, and this processing ends. .
- step 1203 determines in step 1203 that the handling permission information is not set to “permitted” at the export source (step 1203: NO)
- step 1203 determines in step 1203 that the handling permission information is not set to “permitted” at the export source (step 1203: NO)
- the content conversion unit 67 performs step 1203. The process proceeds to 1 202 and exits without performing export of rights.
- step S125 determines in step S125 that a stricter usage restriction cannot be realized at the export destination than at the export source (step S1205: NO). The process proceeds to 122, and the process is terminated without exporting the rights data.
- the export source and export destination are such a DRM model
- the rights data may be rationally converted so that the usage rights at the export destination DRM are the same as those used at the exporter or the rights are reduced. It becomes possible. '
- the export source DRM adopts “1—B: Rights permission + use restriction model” in Table 1 above
- the export destination DRM uses “ 11C: Rights data changes when adopting the “use restriction model”
- the conversion rule for converting the rights rights is to apply Case 1-6 above, ⁇ Only one type of usage is available for the content '', and both the handling permission information in the export source DRM and the restriction information for the handling permission information are applicable, and the restriction information in the export destination DRM "1.
- the handling permission information of the usage related to the content exists at the export source, 1-1.
- the handling permission information is" permitted "at the export source.
- the rights data is set so that the same usage restrictions are set. Convert and export. 1—1— 2. If the same usage restrictions cannot be realized in the export destination DRM, and it is possible to write in the direction of tightening the usage restrictions, set the usage restrictions as close as possible with the tightened usage restrictions. Convert and export the rights data as if to 1—1—3.
- Export destination If the same usage restrictions cannot be realized in the DRM, and it is not possible to describe in a direction to tighten the usage restrictions, the rights will not be exported overnight. 1-2. If the handling permission information is “not permitted” at the export source, export of the rights will not be performed. 2. If the handling permission information of the usage related to the content does not exist at the source of the export, the rights export will not be performed. "
- the content conversion section 67 determines whether or not the handling permission information of the usage method (playback) related to the audio content exists in the export source (step S1301). If the content conversion unit 67 determines that the permission information for handling (playback) does not exist at the export source (step S (1301: NO), the flow shifts to step S1302, the right data is not exported, and the process ends.
- step S1301: YES If the content conversion section 67 determines that the handling permission information exists at the export source (step S1301: YES), the content conversion section 67 shifts to step S1303, and proceeds to step S133. It is determined whether the information is set to “permitted” at the export source or not. When the content conversion unit 67 determines that the handling permission information is set to “permitted” at the export source (step S 13 03: YES), the processing proceeds to step S 13 04 .
- step S1304 the content conversion section 67 determines whether or not the export destination can realize the same usage restriction as the export source with respect to the usage restriction information related to the handling permission information. If the content conversion unit 67 determines that the use restriction equivalent to the export source cannot be realized at the export destination (step S1304: NO), the process proceeds to step S1305.
- step S135 the content conversion section 67 determines whether the export destination can realize a stricter usage constraint than the export source with respect to the usage constraint information related to the handling permission information. If the content conversion unit 67 determines that the export destination can realize a stricter usage restriction than the export source (step S135: YES), the process proceeds to step S136. In step S1306, the content conversion unit 67 sets the use restriction on the method of use related to the digital content to the export destination so as to be stricter than the export source but as close as possible. The rights are converted, the export is performed, and the process ends.
- step S1307 the content conversion section 67 sets the export destination in the same way as the export source regarding the usage restrictions related to the digital content. Convert and export the rights data so as to set usage restrictions such as, and terminate this processing.
- step 1303 determines in step 1303 that the handling permission information is not set to “permitted” at the export source (step 1303: NO), Proceeding to step 1302, this process ends without exporting the rights data.
- step S1305 NO
- the content conversion unit 67 determines that the export destination cannot realize a stricter usage restriction than the export source in step S135 (step S1305: NO)
- the content conversion unit 67 performs step S1
- the process proceeds to 302, and the process is terminated without exporting the rights data.
- the export source DRM adopts “1-1 C: Use Restriction Model” in Table 1 above, and the export destination DRM adopts “1— ⁇ : Rights Permission Model” in Table 1 above.
- An example is shown in which the export source DRM can use the usage restriction information for the usage method “playback”, and the export destination DRM can apply the handling permission information for the usage method “playback”. More specifically, in the example of Table 5, the export source DRM is a DRM to which “reproduction count” and “reproduction period” can be applied as usage restriction information, and the export destination DRM is “execute” as handling permission information. This is an example of rights-to-night conversion processing in the case where four of “display”, “print”, and “playback” are applicable DR ⁇ .
- the usage restriction information for the usage “play” is set to “playback count: unlimited” and “playback period: unlimited” in the export source DRM, and the usage method “playback” related to the relevant audio content is set. Since the handling permission information exists in the export destination DRM, the setting content of the handling permission information is set to “Permitted”. This indicates that the right data is exported, that is, the export process is “ ⁇ : Possible”. Here, “X” in the table indicates that “X: use is not permitted”.
- the usage restriction information for the usage method "playback” is set in the export source DRM to "playback times: 3 times (limited)” and “playback period: 3 days (limited)”.
- Export is "X: Not possible”. Also, here, “1” in the table means that the export permission is not set and the handling permission information of the export destination DRM is not set.
- the conversion rules for converting the rights are applied by applying the above cases 1-7 and (“ There is only one type of usage that can be used in a certain digital content. ⁇ Only the restriction information can be applied at the export source DRM, and only the handling permission information can be applied at the export destination DRM. If “1. The export source and all of the usage restriction information related to the content is“ No restriction ”,“ 1. 1. The handling permission information of the usage related to the content is the destination of the export. If present Converts and exports the rights data so that the content of the handling permission information is set to “permitted”. 1-2. Handling of usage related to the content If the permission information does not exist at the export destination, the export of rights will not be performed. 2. If there is at least one usage restriction information at the export source other than "no restriction", the right data is not exported. "
- the content conversion section 67 determines whether or not all the usage constraint information of the usage method related to the audio content is set to "no limit" at the export source (step S140) 1).
- the “reproduction count” and “reproduction period rush”, which are the usage restriction information of the export source DRM, are all set to “unlimited”. Therefore, the content conversion section 67 determines that all of the usage restriction information-is set to "no restriction” (step S1401: YES), and shifts to step S1403.
- step S144 the content conversion section 67 determines whether or not the handling permission information of the usage method (playback) related to the audio content exists in the export destination (step S140). 3).
- the content conversion unit 67 determines that the handling permission information exists at the export destination. It is determined (step S1403: YES), and the process proceeds to step S1404.
- step S144 the content conversion section 67 converts and exports the right data so that the setting content of the handling permission information related to the audio content is set to “permitted” for the export destination. Then, the processing ends. Therefore, in pattern 1 of Table 5, the setting contents of the handling permission information related to the relevant audio content are set to “permitted” for the export destination, and all other handling permission information is set to “disallowed”. " Convert rights data and perform export.
- the usage restriction information of the usage method related to the audio content is “playback times: 3 times (limited)” or “playback period: 3 days (limited)”. Is set to For this reason, the long conversion unit 67 determines in step S1401 that all the usage constraint information related to the audio content is not set to "unlimited” at the export source (step S1). (401: NO), the flow shifts to step S1402, and the process is terminated without exporting the rights.
- the content conversion unit 67 determines in step S1403 that the handling permission information of the usage method (playback) related to the audio content does not exist in the export destination (step S1403). 3: NO), the process proceeds to step S1402, the right data is not exported, and the process ends.
- the export source and the export destination are such DRM models, by performing the above-described determination, it is appropriately determined whether to export or not.
- the rights data is rationally changed so that the usage rights at the export destination DRM are the same as those at the export source or the rights are reduced. Can be changed.
- the handling permission information of the usage method related to the content exists in the export destination DRM, 1-1.
- Equivalent use in the export destination DRM If restrictions can be realized, convert the rights and export them so that the handling permission information is set to “permitted” for the export destination and the same usage restrictions are set. All other handling permission information at the destination is set to “not allowed”).
- Export destination If the equivalent usage restrictions cannot be realized with DRM, and if it is possible to write in the direction of tightening the usage restrictions, set the handling permission information to “Permitted” for the export destination. Convert and export rights rights so that the usage restrictions are set as close as possible with stricter usage restrictions. (All other handling permission information at the export destination is set to ⁇ Disallowed. '' Do).
- the content conversion section 67 determines whether or not the handling permission information of the usage method (playback) related to the audio content exists in the export destination (step S1501). If the content conversion unit 67 determines that the handling permission information for the method of use (playback) does not exist at the export destination (step S1501: O), the process proceeds to step S1502, and the rights export is performed. Is not performed, and this process ends.
- step S1501 determines that the handling permission information of the method of use (playback) exists at the export destination (step S1501: YES)
- step S1503 it is determined whether or not the export destination can realize the same usage restriction as the export source with respect to the usage restriction information related to the handling permission information. If the content conversion unit 67 determines that the export destination cannot achieve the same usage restriction as the export source (step S.1503: NO), the process proceeds to step S1504.
- step S1504 the content conversion section 67 determines whether the export destination can realize a stricter usage constraint than the export source with respect to the usage constraint information related to the handling permission information. If the content conversion unit 67 determines that the export destination can realize a stricter usage restriction than the export source (step S1504: NO), the process proceeds to step S1505. In step S 1505, the content conversion section 67 sets the handling permission information related to the audio content to “permitted” for the export destination, and sets the usage related to the handling permission information. The restriction information is set to be stricter than the export source but set as close as possible, and all other handling permission information at the export destination is set to "not permitted". Export and end this process.
- step S1503 determines in step S1503 that the usage restriction information related to the handling permission information can realize the same usage restriction as the export source at the export destination (step S1503). 1503: YES), and proceeds to step S1506.
- step S1506 the content conversion section 67 sets the setting of the handling permission information related to the audio content to “permitted” for the export destination, and uses the content related to the handling permission information. Convert and export the rights data so that the same usage restrictions as the export source are set for the restriction information, and all other handling permission information at the export destination is set to "not permitted”. This processing ends.
- step S1504. When it is determined that the use restriction information related to the permission information cannot realize a use restriction better than the export source at the export destination (step S1504: NO), the process proceeds to step S1502. Then, the right is not exported and the process ends.
- the conversion rules for converting the rights data apply the above cases 1-9 and (“ “Only one type of usage is available” and “Only the restriction information can be applied to both the export source DRM and the export destination DRM”.) "1. If usage constraint information on the usage method related to the content exists, 1–1. If the same usage constraint can be realized in the export destination DRM, convert the rights data so that the same usage constraint is set.
- the content conversion section 67 determines whether or not the usage constraint information on the usage method (playback) related to the audio content exists in the export source (step S 1601). If the content conversion unit 67 determines that the usage limit information of the method of use (playback) does not exist at the export source (step S1601: NO), the process proceeds to step S1662. Then, the right is not exported and the process ends. ''
- step S1601: YES If the content conversion unit 67 determines that the usage constraint information on the method of use (playback) exists at the export source (step S1601: YES), then the content conversion unit 67 performs step S160. Proceed to 3 to determine whether the export destination can achieve the same usage restriction as the export source with regard to the usage restriction information on the usage method related to the content. If the content conversion unit 67 determines that the export destination cannot realize the same usage restriction as the export source (step S1603: YES), the process proceeds to step S1604.
- step S164 the content conversion unit 67 determines whether the export destination can realize a stricter usage constraint than the export source with respect to the usage constraint information of the usage method related to the content. If the content conversion unit 67 determines that the export destination can realize a stricter usage restriction than the export source (step S164: YES), the process proceeds to step S165.
- step S165 the content conversion section 67 sends the export destination the usage constraint information on the usage method related to the content. Convert and export the rights data so that the usage restrictions are as strict as possible but set as close as possible to the port source, and end this processing.
- step S1663 the content conversion unit 67 determines that the usage restriction information of the usage method related to the content can be realized at the export destination at the same usage restriction as the export source. In this case (step S1663: YES), the flow shifts to step S166.
- step S166 the content conversion unit 67 sets the right data to the export destination so that the usage constraint information on the usage method related to the content is set to the same usage constraint as the export source. Is converted and exported, and the process ends.
- Step S1604 NO
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Multimedia (AREA)
- Technology Law (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Storage Device Security (AREA)
Abstract
Description
Claims
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2005512091A JPWO2005010762A1 (ja) | 2003-07-25 | 2004-07-23 | データ処理装置 |
| EP04748090A EP1557762A1 (en) | 2003-07-25 | 2004-07-23 | Data processing apparatus |
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2003-280257 | 2003-07-25 | ||
| JP2003280257 | 2003-07-25 | ||
| JP2004085795 | 2004-03-23 | ||
| JP2004-085795 | 2004-03-23 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2005010762A1 true WO2005010762A1 (ja) | 2005-02-03 |
Family
ID=34082398
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/JP2004/010882 Ceased WO2005010762A1 (ja) | 2003-07-25 | 2004-07-23 | データ処理装置 |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US20050021556A1 (ja) |
| EP (1) | EP1557762A1 (ja) |
| JP (1) | JPWO2005010762A1 (ja) |
| WO (1) | WO2005010762A1 (ja) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010503083A (ja) * | 2006-10-17 | 2010-01-28 | 華為技術有限公司 | ライセンスをエクスポートするためのシステム及び方法 |
| WO2011161898A1 (ja) * | 2010-06-21 | 2011-12-29 | パナソニック株式会社 | コンテンツ複製システム、コンテンツ利用装置、管理サーバ、コンテンツ利用方法、コンテンツ利用プログラム及び集積回路 |
Families Citing this family (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7721111B2 (en) * | 2003-12-14 | 2010-05-18 | Realnetworks, Inc. | Auto-negotiation of content output formats using a secure component model |
| FR2867582B1 (fr) * | 2004-03-10 | 2006-05-05 | Michel Koenig | Unite electronique portative comportant dans un microcircuit un processeur numerique a capacite de cryptographie, une me oire flash de grande capacite et un processeur de traitement du signal |
| KR100636169B1 (ko) * | 2004-07-29 | 2006-10-18 | 삼성전자주식회사 | 서로 다른 drm이 적용된 콘텐츠의 전송 및 재생 방법 |
| KR100628655B1 (ko) * | 2004-10-20 | 2006-09-26 | 한국전자통신연구원 | 상이한 디지털 저작권 관리 도메인간의 콘텐츠 교환을 위한방법 및 시스템 |
| CN100454207C (zh) * | 2005-06-24 | 2009-01-21 | 北京振戎融通通信技术有限公司 | 一种面向移动信息终端的数字版权保护方法 |
| KR20070050712A (ko) | 2005-11-11 | 2007-05-16 | 엘지전자 주식회사 | Srm의 디지털 저작권 관리 방법 및 장치 |
| US20070145152A1 (en) * | 2005-12-28 | 2007-06-28 | Fabrice Jogand-Coulomb | Nested memory system with near field communications capability |
| US20070145135A1 (en) * | 2005-12-28 | 2007-06-28 | Fabrice Jogand-Coulomb | Methods used in a nested memory system with near field communications capability |
| CN101395596B (zh) | 2006-03-06 | 2010-10-27 | Lg电子株式会社 | 数据传递方法 |
| US20090133129A1 (en) | 2006-03-06 | 2009-05-21 | Lg Electronics Inc. | Data transferring method |
| US8429300B2 (en) | 2006-03-06 | 2013-04-23 | Lg Electronics Inc. | Data transferring method |
| US20080005806A1 (en) * | 2006-06-30 | 2008-01-03 | Nokia Corporation | Apparatus, network entity and associated methods and computer program products for selectively enabling features subject to digital rights management |
| KR20080022476A (ko) | 2006-09-06 | 2008-03-11 | 엘지전자 주식회사 | 논컴플라이언트 컨텐츠 처리 방법 및 디알엠 상호 호환시스템 |
| KR20080051971A (ko) * | 2006-12-07 | 2008-06-11 | 삼성전자주식회사 | 휴대용 단말기에서 디지털 저작권 관리 컨텐츠 편집 방법및 장치 |
| EP2044549B1 (en) * | 2007-01-05 | 2014-03-12 | LG Electronics Inc. | Method for transferring resource and method for providing information |
| EP2013771B1 (en) * | 2007-02-16 | 2013-08-21 | LG Electronics Inc. | Method for managing domain using multi domain manager and domain system |
| KR100923456B1 (ko) * | 2007-02-23 | 2009-11-09 | 삼성전자주식회사 | 휴대용 단말기에서 디지털 저작권 관리 컨텐츠 관리 방법 및 장치 |
| US8639627B2 (en) * | 2007-07-06 | 2014-01-28 | Microsoft Corporation | Portable digital rights for multiple devices |
| KR101887426B1 (ko) * | 2012-03-16 | 2018-08-10 | 삼성전자주식회사 | 컨텐츠 공유 시스템에서 프라이버시를 보장하기 위한 장치 및 방법 |
| JP6701646B2 (ja) * | 2015-09-02 | 2020-05-27 | 富士通株式会社 | 情報処理装置、情報処理システム及び情報管理方法 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002297816A (ja) * | 2001-03-29 | 2002-10-11 | Sony Corp | 情報処理装置および方法、記録媒体、並びにプログラム |
| JP2002297945A (ja) * | 2001-03-30 | 2002-10-11 | Nippon Telegr & Teleph Corp <Ntt> | コンテンツ仲介方法及び装置、プログラム、記録媒体 |
| JP2003162600A (ja) * | 2001-08-08 | 2003-06-06 | Matsushita Electric Ind Co Ltd | ライセンス情報変換装置 |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2002219860A1 (en) * | 2000-11-10 | 2002-06-11 | Full Audio Corporation | Digital content distribution and subscription system |
| JP4524480B2 (ja) * | 2000-11-24 | 2010-08-18 | 三洋電機株式会社 | データ端末装置 |
| US7472280B2 (en) * | 2000-12-27 | 2008-12-30 | Proxense, Llc | Digital rights management |
| JP4151274B2 (ja) * | 2001-02-09 | 2008-09-17 | ソニー株式会社 | 情報処理装置および方法、ライセンスサーバ、並びにプログラム |
| JP3818505B2 (ja) * | 2002-04-15 | 2006-09-06 | ソニー株式会社 | 情報処理装置および方法、並びにプログラム |
| US7631318B2 (en) * | 2002-06-28 | 2009-12-08 | Microsoft Corporation | Secure server plug-in architecture for digital rights management systems |
-
2004
- 2004-07-23 EP EP04748090A patent/EP1557762A1/en not_active Withdrawn
- 2004-07-23 JP JP2005512091A patent/JPWO2005010762A1/ja active Pending
- 2004-07-23 WO PCT/JP2004/010882 patent/WO2005010762A1/ja not_active Ceased
- 2004-07-23 US US10/897,214 patent/US20050021556A1/en not_active Abandoned
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002297816A (ja) * | 2001-03-29 | 2002-10-11 | Sony Corp | 情報処理装置および方法、記録媒体、並びにプログラム |
| JP2002297945A (ja) * | 2001-03-30 | 2002-10-11 | Nippon Telegr & Teleph Corp <Ntt> | コンテンツ仲介方法及び装置、プログラム、記録媒体 |
| JP2003162600A (ja) * | 2001-08-08 | 2003-06-06 | Matsushita Electric Ind Co Ltd | ライセンス情報変換装置 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010503083A (ja) * | 2006-10-17 | 2010-01-28 | 華為技術有限公司 | ライセンスをエクスポートするためのシステム及び方法 |
| WO2011161898A1 (ja) * | 2010-06-21 | 2011-12-29 | パナソニック株式会社 | コンテンツ複製システム、コンテンツ利用装置、管理サーバ、コンテンツ利用方法、コンテンツ利用プログラム及び集積回路 |
Also Published As
| Publication number | Publication date |
|---|---|
| EP1557762A1 (en) | 2005-07-27 |
| JPWO2005010762A1 (ja) | 2006-09-14 |
| US20050021556A1 (en) | 2005-01-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2005010762A1 (ja) | データ処理装置 | |
| EP1571556A1 (en) | Data processing apparatus and data distributing apparatus | |
| TWI321289B (en) | Relevant methods and systems for generating compact hardware identification of computer system for controlling usage of software package in computer system, and computer readable medium for recording relevant instructions | |
| US7865445B2 (en) | Information processing method, information processing apparatus, computer program and storage medium | |
| US20070288383A1 (en) | Method and apparatus for issuing rights object required to use digital content | |
| EP1794729B1 (en) | Method, device and computer program product for activating the right of use of at least one secured content item | |
| US8369528B2 (en) | Method and apparatus for providing encrypted key based on DRM type of host device | |
| JP2004139433A (ja) | 端末装置とこの装置で使用する記録媒体、及びコンテンツ管理システムとその管理サーバ | |
| JP5185271B2 (ja) | デジタルコンテンツの配信制御 | |
| EP1636661B1 (en) | Digital rights management | |
| CN1979514A (zh) | 在不具有内部电源的装置中实现安全时钟的方法和设备 | |
| KR20060115550A (ko) | 디알엠 컨버터 | |
| WO2008069887A2 (en) | Method and system for allowing content protected by a first drm system to be accessed by a second drm system | |
| JP2005275441A (ja) | 電子音楽装置およびその制御方法を実現するためのプログラム | |
| JP2008047050A (ja) | ソフトウエアダウンロード方法、アプリケーション用メディア作成方法、アプリケーション用メディア作成プログラム、並びにソフトウエア配布システム | |
| WO2025050986A1 (zh) | 元数据的生成方法及电子设备 | |
| JP6743344B2 (ja) | オフライン認証下で情報を階層管理する配布情報管理方法及び配布情報管理プログラム | |
| JP2013088845A (ja) | 情報処理装置、情報処理方法およびコンピュータプログラム | |
| WO2011117942A1 (ja) | コンテンツ受信機、コンテンツ利用システム、コンテンツ再生方法、プログラム、および記録媒体 | |
| US20150256706A1 (en) | Photo media printing method and photo media printing system | |
| Pestoni | Content Protection Interoperability Challenges and Opportunities in the Home Environment | |
| JP2007193470A (ja) | 画像処理装置及び画像処理システム | |
| JP2004287901A (ja) | 音楽コンテンツ利用装置およびプログラム並びにコンピュータ読み取り可能な記録媒体 | |
| WO2008148245A1 (en) | Digital content protection method and system based on user identification | |
| JP2013088844A (ja) | 情報処理装置、情報処理方法およびコンピュータプログラム |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| WWE | Wipo information: entry into national phase |
Ref document number: 200480021547.4 Country of ref document: CN |
|
| AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
| AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2005512091 Country of ref document: JP |
|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
| WWE | Wipo information: entry into national phase |
Ref document number: 2004748090 Country of ref document: EP |
|
| WWP | Wipo information: published in national office |
Ref document number: 2004748090 Country of ref document: EP |
|
| WWW | Wipo information: withdrawn in national office |
Ref document number: 2004748090 Country of ref document: EP |




