EP1557762A1 - Datenverarbeitungsvorrichtung - Google Patents

Datenverarbeitungsvorrichtung Download PDF

Info

Publication number
EP1557762A1
EP1557762A1 EP04748090A EP04748090A EP1557762A1 EP 1557762 A1 EP1557762 A1 EP 1557762A1 EP 04748090 A EP04748090 A EP 04748090A EP 04748090 A EP04748090 A EP 04748090A EP 1557762 A1 EP1557762 A1 EP 1557762A1
Authority
EP
European Patent Office
Prior art keywords
usage constraint
export
permission information
right data
handling permission
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.)
Withdrawn
Application number
EP04748090A
Other languages
English (en)
French (fr)
Inventor
Naohiko Noguchi
Eiji Takahashi
Osamu Uchida
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Panasonic Holdings Corp
Original Assignee
Matsushita Electric Industrial Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Matsushita Electric Industrial Co Ltd filed Critical Matsushita Electric Industrial Co Ltd
Publication of EP1557762A1 publication Critical patent/EP1557762A1/de
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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 apparatus which handles data including right data related to handling of digital contents in an electronic device such as a portable information terminal, cellular phone apparatus or recording medium such as a memory card.
  • DRM Digital Rights Management
  • the DRM system may be built in a recording medium such as a memory card, built in player software of audio and movie, built in transmission/reception, transfer software or a combination thereof.
  • the DRM system grants each case of contents permission (described as right data related to the handling of the contents) and controls the use of contents such as reproduction based on this right data. Therefore, without the right data, it is not possible to use contents and once the usage permission of the right data expires, use of the contents is not possible any longer.
  • contents downloaded for portable information terminals are controlled by a specific DRM system which controls the portable information terminal, and it has not been possible to record the contents in a memory card under the management of a different DRM system and use them for other devices. It will be convenient if the user, etc., of the contents can arbitrarily convert data so that the data can be used among recording media and devices under the management of such different DRM systems and output the data (hereinafter this will be referred to as "export").
  • An aspect of the invention is a data processing apparatus which processes data including right data related to handling of digital contents, comprising: an acquisition section that acquires the right data corresponding to the digital contents, a data storage section that stores the right data, a right data distribution source information storage section that stores right data distribution source information indicating a location of a distribution source of the right data on a network, and a contents handling section that handles the contents data of digital contents corresponding to the right data according to the right data, wherein, when said digital contents are exported to a contents handling management system at an export destination, said contents handling section converts right data corresponding to said digital contents so as to be adaptable to the contents handling management system at the export destination and acquires right data corresponding to the contents data acquired from said distribution source based on said right data distribution source information.
  • right data related to the handling of the digital contents includes copyright information in the DRM systems. That is, suppose the right data refers to information on how to handle contents, information for protecting copyright of the contents, information on the copyright of the contents, information on use of the contents and information on control (constraints) of circulation and use of the contents, etc.
  • FIG.1 illustrates a configuration of a contents distribution system according to Embodiment 1 of the present invention.
  • the configuration and operation in a case where contents data is downloaded and acquired from a contents distribution source using a portable terminal apparatus such as a cellular phone apparatus this downloaded contents data is exported (meaning that data is converted and output so as to be available among different recording media and devices and different DRM systems) to a memory card and usage permission, etc., is updated by acquiring only right data related to the acquired contents will be explained.
  • a server of the contents distribution source corresponds to the data distribution apparatus and a portable terminal apparatus corresponds to the data processing apparatus.
  • the contents distribution system is constructed of a portable terminal apparatus 11 which downloads the contents, a server 12 which is the contents distribution source, a memory card 13 to which the contents is exported from the portable terminal apparatus 11 and a communication network 14 which connects the portable terminal apparatus 11 and the server 12.
  • the portable terminal apparatus 11 has the function of a data processing apparatus which downloads contents data and right data distributed by the server 12 and processes data including the contents data and right data in accordance with a first DRM system used in the own apparatus.
  • the contents are available to this portable terminal apparatus 11 according to the contents handling management based on the first DRM system.
  • the contents data includes various types of data such as music, images, characters or combinations thereof, etc.
  • the contents are used in various ways such as reproduction of music contents and display of images and character contents.
  • the portable terminal apparatus 11 also has the function of converting right data so as to be adaptable to a second DRM system as appropriate in order to export the contents data to a medium and apparatus in a different environment of a second DRM system such as the memory card 13.
  • being "adaptable to a DRM system” means being available (reproducible, recordable, transferable, etc.) conforming to rules, etc., of the DRM system.
  • the portable terminal apparatus 11 also has the function of reacquiring right data on the contents data which has been downloaded and already existing and updating usage permission, etc., for the contents. By updating the right data, it is possible to use the contents when the usage permission expires or when a trial period ends.
  • the right data includes handling permission information on the use of the contents such as a usage count of the contents, deadline, whether or not the contents can be exported to other DRM systems and information describing usage conditions including constraint information, etc.
  • the server 12 has the function of the data distribution apparatus which distributes contents data and right data to the portable terminal apparatus 11.
  • This server 12 prepares contents data and right data on these contents according to a request from the portable terminal apparatus 11, provides and distributes them to the portable terminal apparatus 11.
  • the right data includes copyright information describing usage condition including permission, constraint on the use of the contents for copyright protection and usage permission, etc.
  • As the contents data data in an appropriate format corresponding to the portable terminal apparatus 11 to which the contents are distributed and the DRM system used there is provided.
  • the memory card 13 is a recording medium which stores contents data and right data according to a second DRM system which is different from the first DRM system used in the portable terminal apparatus 11 .
  • the communication network 14 is constructed by including various communication sections such as a mobile communication network, telephone network and Internet network.
  • FIG.2 illustrates an internal configuration of the portable terminal apparatus 11 and memory card 13 according to this embodiment.
  • the portable terminal apparatus 11 can incorporate or mount the memory card 13 in a detachable manner and is constructed by including a control section 61, a transmission/reception section 62, a memory 63 and a memory card interface (I/F) section 64.
  • the control section 61 is a block which exercises overall control on the entire operation of the portable terminal apparatus 11 and includes a download section 65 which downloads contents data and right data from the server 12, a contents management section 66 which handles the downloaded contents data based on the right data and a contents conversion section 67 which converts contents data and right data so as to be adaptable to the second DRM system in the memory card 13 to which the contents data is exported.
  • the download section 65 has the function of an acquisition section according to patent claims and the contents management section 66 and contents conversion section 67 realize the function of a contents handling section according to patent claims.
  • This control section 61 is constructed of a processor which operates according to a predetermined program and a software module for realizing the functions of the above described sections.
  • the contents conversion section 67 may also be mounted on a different apparatus outside the portable terminal apparatus 11.
  • control section 61 also has the function of executing an application program stored in the memory 63 and thereby accessing the server 12 which is the right data distribution source for distributing the right data.
  • application program for accessing the server 12 browser software, etc., which acquires and displays distribution information of the server 12 is used.
  • the memory 63 has the function of a data storage section according to patent claims, stores the contents data and right data, thus realizing the function as the data storage section.
  • This memory 63 includes a contents data storage area 68 which stores downloaded contents data, a right data storage area 69 which stores right data and a distribution source information storage area 70 which stores distribution source information for identifying the distribution source of the right data.
  • the transmission/reception section 62 is a block for carrying out transmission/reception of data to/from the server 12 through the communication network 14 and uses a publicly known radio communication apparatus.
  • the memory card interface section 64 is constructed by including a card slot, etc., for mounting and connecting the memory card 13.
  • the memory card 13 also has the function as a data storage section which stores contents data and right data exported from the portable terminal apparatus 11.
  • This memory card 13 includes a contents data storage area 71 which stores the exported contents data, a right data storage area 72 which stores right data and a distribution source information storage area 73 which stores distribution source information for identifying the distribution source of the right data.
  • FIG.3 illustrates an internal configuration of the server 12 according to this embodiment.
  • the server 12 is constructed by including a control section 81, a transmission/reception section 82, a memory 83 and a data storage section 84.
  • the control section 81 is a block which exercises overall control on the entire operation of the server 12 and includes a contents data supply section 85 which supplies contents data as a section which distributes contents data and right data according to a contents distribution request or right data distribution request from the portable terminal apparatus 11, a right data supply section 86 which supplies right data and a distribution section 87 which distributes contents data and right data.
  • This control section 81 is constructed by including a processor which operates according to a predetermined program and a software module for realizing the function of the above described sections. Furthermore, the control section 81 acquires terminal information on the portable terminal apparatus 11 which has made access and accesses the data storage section 84 which stores information such as contents data and right data as required and acquires distribution information.
  • the control section 81 supplies distribution source information for identifying the distribution source of the right data to the portable terminal apparatus 11 which is the distribution destination.
  • distribution source information for example, URL (Uniform Resource Locator) information indicating the position (address) of the server 12 on the network is used.
  • the data storage section 84 stores contents data of various formats according to the apparatus and medium at the contents distribution destination, various types of right data in accordance with the DRM system at the contents distribution destination.
  • contents data to be distributed from the server 12 it is also possible to prepare contents data of a plurality of formats so as to be adaptable to a plurality of devices and media, a plurality of DRM systems beforehand, store them in the data storage section 84 and selectively provide some contents data from the data storage section or prepare contents data of a basic format and convert and provide the contents data each time according to the contents distribution destination based on this data.
  • the right data it is also possible to prepare a plurality of types of right data beforehand so as to be adaptable to a plurality of DRM systems, store them in the data storage section 84 and selectively provide some right data from the data storage section or provide right data by generating or converting it each time according to the contents distribution destination or other distribution conditions.
  • a provider (issuer) of contents data may be the same as or different from a provider (issuer) of right data and the server 12 maybe constructed according to the modes of these providers as appropriate.
  • the server 12 is represented by one apparatus, but the server 12 may also be constructed of a plurality of server apparatuses having these functions .
  • the transmission/reception section 82 is a block for carrying out transmission/reception of data to/from the portable terminal apparatus 11 through the communication network 14 and uses a publicly known communication apparatus.
  • the memory 83 stores distribution information for the portable terminal apparatus 11.
  • FIG.4 and FIG.5 schematically illustrate a data flow example of this embodiment.
  • FIG.4A, 4B and FIG.5A, 5B there may be a total of four modes in which distribution source information and contents data are stored, as shown in FIG.4A, 4B and FIG.5A, 5B. That is, there is a case where both distribution source information 93 and contents data 91 are stored in the portable terminal apparatus 11 in a first DRM system environment as shown in FIG.4A, a case where the distribution source information 93 is stored in the portable terminal apparatus 11 in the first DRM system environment and the contents data 91 is stored in the memory card 13 in the second DRM system environment as shown in FIG.4B, a case where both the distribution source information 93 and the contents data 91 are stored in the memory card 13 in the second DRM system environment as shown in FIG. 5A, or a case where the distribution source information 93 is stored in the memory card 13 in the second DRM system environment and the contents data 91 is stored in the portable terminal apparatus 11 in the first DRM system environment as shown in FIG.5B.
  • Embodiment 1 the operation when the distribution source information 93 is stored in the portable terminal apparatus 11 in the first DRM system environment as shown in FIG.4A, 4B will be explained.
  • the portable terminal apparatus 11 accesses the server 12 which is the distribution source of the right data based on the distribution source information 93 and acquires the right data.
  • the acquired right data is converted so as to be adaptable to the second DRM system as appropriate and the converted right data 92 is exported to the memory card 13.
  • the contents data 91 is stored in the portable terminal apparatus 11, decryption and encryption or data format conversion is carried out according to the circumstances, and the contents data 91A encrypted in compliance with the second DRM system is exported to the memory card 13.
  • the right data even if the right data includes the usage condition at the export destination, the right data cannot be handled in the portable terminal apparatus 11 unless the right data is adaptable to the first DRM system used in the portable terminal apparatus 11, and therefore when contents are downloaded from the server 12 to the portable terminal apparatus 11, the right data is provided as information corresponding to the first DRM system.
  • the right data When contents are exported from the portable terminal apparatus 11 to the memory card 13, the right data needs to be converted so as to be adaptable to the second DRM system used in the memory card 13.
  • FIG. 6 is a flow chart showing an operating procedure for updating the right data of the contents according to Embodiment 1. This section will describe an example where when usage permission of right data such as a usage count of contents is consumed and ceases to be in effect, right data reissued to acquire additional usage permission is acquired.
  • the contents management section 66 acquires distribution source information on the corresponding right data from the memory 63 (step S601) .
  • the download section 65 accesses the server 12 which stores the right data based on the acquired distribution source information to request the server to distribute the right data (step S602).
  • the control section 81 of the server 12 receives the request for distribution of the right data through the transmission/reception section 82 (step S603). Then, the right data supply section 86 of the control section 81 identifies the contents corresponding to the distribution request and when the right data can be reissued, the right data supply section 86 reissues and prepares the right data corresponding to the contents (step S604). Then, the distribution section 87 distributes the right data to the portable terminal apparatus 11 (step S605).
  • the download section 65 of the portable terminal apparatus 11 receives the distributed right data (step S606) and stores the right data in the memory 63 of the portable terminal apparatus 11.
  • the contents management section 66 acquires the right data stored in the memory 63 (step S607) and performs management related to the handling of the contents based on the right data.
  • the portable terminal apparatus 11 reproduces the contents data, it carries out decryption on the acquired right data and contents data first and then uses the contents based on the right data and carries out processing such as reproduction.
  • the contents management section 66 decrypts the acquired right data (step S608) .
  • the right data is downloaded from the server 12, the right data is encrypted in compliance with the first DRM system used in the portable terminal apparatus 11, and therefore the right data is decrypted using a cryptographic key corresponding to this first DRM system.
  • this step is omitted.
  • the contents conversion section 67 converts the right data of the decrypted raw data so as to be adaptable to the DRM system of the memory card 13 to which the right data is exported (step S609). At this time, the contents conversion section 67 performs a conversion so that the usage permission, etc., based on the copyright of the right data is equivalent to or smaller than the scope of rights before the conversion. That is, when, for example, both DRM systems of the portable terminal apparatus 11 and memory card 13 do not include any corresponding handling permission information on the right data, a conversion is performed in a direction in which the permission content is reduced. On the other hand, when, for example, both DRM systems of the portable terminal apparatus 11 and memory card 13 do not include any corresponding constraint information on the right data, a conversion is performed in a direction in which the constraint content is increased.
  • a predetermined conversion rule is set for a conversion of right data. Furthermore, for usage conditions involving permission or constraint that cannot be described in the DRM system at either the export source or export destination, it is possible to preset their correspondence and perform a conversion according to the setting (apply a default value), etc., so as to set the usage conditions as appropriate within a range in which the usage condition is not expanded illegally. At this time, between the two DRM systems, a consensus on the specification such as the format, function, capacity of available contents data is formed and a consensus is also formed on the rule about rewriting of the right data.
  • the right data conversion rule such as (1) to convert handling permission information supported by the DRM system at the export destination, (2) to delete, without conversion, handling permission information not supported by the DRM system at the export destination, (3) to delete the original handling permission information without conversion when constraint information is added to handling permission information supported by the DRM system at the export destination and when there is constraint information not supported by the DRM system at the export destination, (4) to convert the handling permission information and constraint information when only the constraint information supported by the DRM system at the export destination is added in the handling permission information supported by the DRM system at the export destination, (5) not to convert handling permission information not existing in the right data at the conversion source, (6) not to ignore but convert constraint information existing in right data at the conversion source.
  • the contents conversion section 67 encrypts the converted right data using a cryptographic key in the second DRM system used in the memory card 13 (step S610) . Furthermore, when contents data is exported to the memory card 13 as shown in FIG.4A, the contents management section 66 acquires the target contents data of the right data from the memory 63 and carries out decryption (step S611) . When the contents data is stored in the portable terminal apparatus 11, it is encrypted in compliance with the first DRM system, and therefore the contents data is decrypted using the cryptographic key in the first DRM system. Then, the contents conversion section 67 encrypts the contents data of the decrypted raw data using the cryptographic key in the second DRM system used in the memory card 13 (step S612) .
  • steps S611, S612 above are omitted.
  • the right data which has been reissued and distributed by the server 12, downloaded and converted so as to be adaptable to the second DRM system by the portable terminal apparatus 11, is output from the contents conversion section 67 of the control section 61, exported to the memory card 13 through the memory card interface section 64 (step S613), stored and recorded in the storage area in the card.
  • the contents data is exported, it is exported as with the right data.
  • the memory card 13 updates the usage permission, etc., with the right data acquired as shown above and can use the exported contents data.
  • the contents data whose reproduction permission deadline or allowable reproduction count, etc., expires and whose usage permission ceases to be in effect can be reused by reacquiring the right data and updating it.
  • Embodiment 1 since the distribution source information on the right data is stored in the portable terminal apparatus 11, updating the right data in the memory card 13 requires the portable terminal apparatus 11 which is the export source of the contents to update the right data.
  • the target contents data of the right data is stored in the memory card 13 as shown in FIG. 4B, the contents need not be exported and the contents data encrypted according to the second DRM system in the memory card 13 can be used as is.
  • Embodiment 2 the operation when the distribution source information 93 is stored in the memory card 13 in the second DRM system environment as shown in FIG.5A, 5B will be explained.
  • the portable terminal apparatus 11 acquires the distribution source information 93 from the memory card 13, accesses the server 12 which is the distribution source of the right data based on this distribution source information 93 and acquires the right data.
  • the acquired right data is converted as appropriate so as to be adaptable to the second DRM system and the converted right data 92 is exported to the memory card 13.
  • the contents data 91 is stored in the portable terminal apparatus 11, the data is decrypted and encrypted or the data format is converted according to the circumstances and the contents data 91A encrypted in compliance with the second DRM system is exported to the memory card 13.
  • FIG.7 is a flow chart showing an operating procedure for updating the right data of the contents according to Embodiment 2. This section will describe an example where when usage permission of right data such as a usage count of contents is consumed and ceases to be in effect, right data reissued to acquire additional usage permission is acquired.
  • the contents management section 66 accesses the memory card 13 through the memory card interface section 64 to request for distribution source information on the right data (step S701) and acquires the distribution source information on the corresponding right data from the memory card 13 (step S702) .
  • the download section 65 accesses the server 12 which stores the right data based on the acquired distribution source information to request it to distribute the right data (step S703).
  • the control section 81 of the server 12 receives the distribution request of the right data through the transmission/reception section 82 (step S704). Then, the right data supply section 86 of the control section 81 identifies the contents whose distribution is requested and when the contents can be reissued, the right data supply section 86 reissues and prepares the right data corresponding to the contents (step S705). Then, the distribution section 87 distributes the right data to the portable terminal apparatus 11 (step S706).
  • the download section 65 of the portable terminal apparatus 11 receives the distributed right data (step S707) and stores it in the memory 63 of the portable terminal apparatus 11.
  • the contents management section 66 acquires the right data stored in the memory 63 (step S708) and manages the handling of the contents based on the right data.
  • the portable terminal apparatus 11 reproduces the contents data, it decrypts the acquired right data and contents data first and then uses the contents based on the right data and carries out processing such as reproduction.
  • the contents management section 66 decrypts the acquired right data (step S709).
  • the contents conversion section 67 converts the right data of the decrypted raw data so as to be adaptable to the DRM system of the memory card 13 to which the right data is exported (step S710).
  • the contents conversion section 67 encrypts the converted right data using the cryptographic key in the second DRM system used in the memory card 13 (step S711) . Furthermore, when the contents data is exported to the memory card 13 as shown in FIG.5B, the contents management section 66 acquires the target contents data of the right data from the memory 63 and decrypts the contents data. Then, the contents conversion section 67 encrypts the contents data of the decrypted raw data using the cryptographic key in the second DRM system used in the memory card 13.
  • the contents data is stored in the memory card 13 as shown in FIG.5A, the above described step is omitted.
  • the right data which has been reissued and distributed from the server 12, downloaded and converted so as to be adaptable to the second DRM system by the portable terminal apparatus 11, is output from the contents conversion section 67 of the control section 61, exported to the memory card 13 through the memory card interface section 64 (step S712) and stored and recorded in the storage area in the card.
  • the contents data is exported as with the right data.
  • the memory card 13 updates the usage permission, etc., with the right data acquired as shown above and can use the exported contents data.
  • the distribution source information on the right data is stored in the memory card 13, and therefore when the right data is updated, not only the portable terminal apparatus which is the export source of the contents but also other portable terminal apparatuses can update the right data. That is, since the memory card itself stores the distribution source information on the right data, the right data can be updated irrespective of the device in which the memory card is inserted.
  • the target contents data of the right data is stored in the memory card 13 as shown in FIG.5A, the contents need not be exported and the contents data encrypted in the second DRM system in the memory card 13 can be used as is.
  • the right data when the right data is redistributed through the updating operation of the right data, the right data need not necessarily be the same as the previously distributed right data.
  • the right data is not limited to one type of right data for the contents, and a plurality of pieces of right data may also be provided for one piece of contents data. Furthermore, it is also possible to set usage conditions which differ from one DRM system to another. For example, when the updating of the right data is charged, a detailed setting of fees is available according to usage conditions classified in detail. Furthermore, with regard to distribution of the fees, too, a detailed setting is available according to complicated usage conditions such as the export destination and the number of times export is allowed. Furthermore, in the case of composite contents, etc., for example, contents related to reproduction of music contents and display of its lyrics, it is possible to provide a plurality of pieces of handling permission information in one piece of right data.
  • the export destination of the contents is not limited to the memory card, but the present invention is applicable to anything such as a recording medium in which contents data is recorded, a device which uses the contents data for reproduction, etc., or a contents usage program such as a contents data reproduction program which is operated by a computer, if it is at least compliant with the DRM system.
  • the export destination can also be an external device or recording medium connected by wireless or wired communication means.
  • contents data and right data are not limited to data which is downloaded from a server by a portable terminal apparatus, but the present invention is likewise applicable to cases where data pushed (sent) by e-mail, etc., is acquired.
  • the contents user who is an end user can acquire right data apart from the contents data based on the distribution source information on the right data or reacquire the right data when the previously acquired usage permission ceases to be in effect, and can acquire right data as appropriate and update it at the export destination. For this reason, it is possible to acquire right data according to the user's request, etc., and make exported contents data available.
  • Embodiment 3 will describe a specific example of the conversion rule when right data is converted using the above described handling permission information. While the foregoing explanations have described the case where the right data includes usage conditions including permission and constraint on the use of contents for copyright protection, copyright information describing usage permission, etc., the following explanations will describe in detail conversion rules when converting right data using handling permission information which describes permission and constraint on the use of contents more specifically. Furthermore, this embodiment sets usage constraint information as the above described constraint information which constrains the usage period and usage count, etc., related to the method of use of contents set in the handling permission information.
  • the contents distribution system according to Embodiment 3 has a configuration similar to that of the portable terminal apparatus 11, server 12 and memory card 13 shown in FIG.1 to FIG.3, and therefore illustrations and explanations thereof will be omitted.
  • the handling permission information is information for setting a method of use of contents and usage permission and non-permission, etc., corresponding to the method of use, and included in the above described right data.
  • the contents conversion section 67 converts right data based on setting contents of handling permission information included in the right data decrypted by the contents management section 66.
  • the matrix table in Table 3 shows an example where both the export source DRM and the export destination DRM adopt "1-A: Right permission model” in Table 1, and an example where both the export source DRM and the export destination DRM can apply handling permission information for method of use "reproduction". More specifically, the example in Table 3 is an example of the right data conversion processing where the export source DRM is a DRM which can apply three of "execute”, "print” and “reproduction” as the handling permission information but cannot apply the handling permission information related to "display”, while the export destination DRM is a DRM which can apply "execute", "display” and “reproduction” as the handling permission information but cannot apply handling permission information related to "print”.
  • Pattern 1 shows that since the handling permission information for the method of use "reproduction” is set to "o: Usage permitted” at the export source DRM, right data is exported by setting the handling permission information for the method of use "reproduction” at the export destination DRM to "o: Usage permitted” and setting all other handling permission information at the export destination to " ⁇ : Usage non-permitted", that is, pattern 1 shows that export processing is "o: possible”.
  • " in the table means that any one of "o: Usage permitted” " ⁇ : Usage non-permitted” is selectable.
  • Pattern 2 shows that since the handling permission information for the method of use "reproduction” is set to " ⁇ : Usage non-permitted” at the export source DRM, export of the right data is " ⁇ : impossible".
  • "-" in the table means that since export is not performed, no setting is performed in the handling permission information at the export destination DRM.
  • case 1-1 is applied to the conversion rule to convert the right data ("only one type of method of use is available to digital contents to be exported” and "only handling permission information is applicable at the export source DRM” and “only the handling permission information is applicable at the export destination DRM") "1.
  • the handling permission information on the method of use related to the contents exists at both the export source and export destination, 1-1.
  • the handling permission information is "permitted” at the export source, right data is converted and exported so that the handling permission information content is inherited to the export destination (however, all other handling permission information at the export destination is set to "non-permitted"), 1-2.
  • the handling permission information is "non-permitted” at the export source, right data is not exported.
  • the contents conversion section 67 first decides whether the handling permission information on the method of use (reproduction) related to the audio contents exists at both the export source DRM and the export destination DRM or not (step S801) . When it decides that the handling permission information on the method of use (reproduction) exists at none of them (step S801: NO), the contents conversion section 67 moves on to step S802 and terminates this processing without exporting the right data.
  • step S801: YES when it decides that the handling permission information on the method of use (reproduction) exists in both of them (step S801: YES), the contents conversion section 67 moves on to step S803 and decides whether the handling permission information is set to "permitted” at the export source or not.
  • the handling permission information on the method of use "reproduction” related to audio contents is set to "o: Usage permitted”.
  • the contents conversion section 67 decides that the handling permission information is set to "permitted” at the export source (step S803: YES), moves on to step S804, converts and exports right data so that the setting contents of the handling permission information are inherited to the export destination and all other handling permission information at the export destination is set to "non-permitted” and terminates this processing.
  • the handling permission information on the method of use "reproduction” related to the audio contents is set to " ⁇ : Usage non-permitted". For this reason, the contents conversion section 67 decides that the handling permission information is not set to "permitted” at the export source DRM (step S803: NO), moves on to step S802 and terminates this processing without exporting the right data.
  • case 1-2 is applied to the conversion rule for converting right data, "1.
  • the handling permission information on the method of use related to the contents exists at both the export source and export destination ("only one type of method of use is available to digital contents to be exported", "only the handling permission information is applicable at the export DRM and both the handling permission information and constraint information for the handling permission information are applicable at the export destination DRM") "1-1.
  • the handling permission information is "permitted” at the export source, right data is converted and exported so that the handling permission information content is inherited to the export destination. In this case, all usage constraint information for the handling permission information at the export destination is set to "no constraint".
  • the contents conversion section 67 first decides whether the handling permission information on the method of use (reproduction) related to the audio contents exists at both the export source and export destination or not (step S901). When it decides that the handling permission information on the method of use (reproduction) does not exist at both the export source and export destination (step S901: NO), the contents conversion section 67 moves on to step S902 and terminates this processing without exporting the right data.
  • step S903 decides whether the handling permission information is set to "permitted” at the export source or not.
  • step S904 decides whether the handling permission information is set to "permitted” at the export source or not.
  • step S904 the contents conversion section 67 decides whether the usage constraint information related to the handling permission information at the export destination can be set to "no constraint” or not. When it decides that "no constraint” can be set (step S904: YES), the contents conversion section 67 moves on to step S905.
  • step S905 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information are inherited to the export destination, all usage constraint information related to the handling permission information is set to "no constraint” and all other handling permission information at the export destination is set to "non-permitted” and terminates this processing.
  • step S904 when it decides that the usage constraint information related to the handling permission information at the export destination cannot be set to "no constraint" (step S904: NO), the contents conversion section 67 moves on to step S906, converts and exports right data so that the setting contents of the handling permission information are inherited to the export destination and the usage constraint information related to the handling permission information is set to a state with the least settable constraint. Furthermore, in step S906, the contents conversion section 67 sets all handling permission information other than the handling permission information at the export destination to " ⁇ : Usage non-permitted".
  • step S903 when it decides in step S903 that the handling permission information is set to "non-permitted" at the export source (step S903: NO), the contents conversion section 67 moves on to step S902 and terminates this processing without exporting the right data.
  • the matrix table in Table 4 shows examples where the export source DRM adopts "1-A: Right permission model” in Table 1, the export destination DRM adopts "1-C: Usage constraint model” in Table 1, the export source DRM can apply only the handling permission information and the export destination DRM can apply usage constraint information on the method of use available to the contents. More specifically, the examples in Table 4 show right data conversion processing examples where the export source DRM is a DRM that can apply four of "execute”, “display”, “print” and “reproduction” as the handling permission information and the export destination DRM is a DRM that can apply "usage count” as the usage constraint information. Furthermore, suppose a case where a count setting such as "no constraint” is also possible for "usage count” as the usage constraint information at the export destination DRM.
  • Pattern 1 shows that since the handling permission information on the method of use "reproduction” is set to “o: Usage permitted” at the export source DRM, usage constraint information on the method of use “reproduction” at the export destination DRM is set to "non-constrained", that is, “no constraint”, and all other usage constraint information at the export destination is set to contents meaning "not available”, thereby indicating that right data is exported, that is, export processing is "o: possible”.
  • “ “ in the table means that any one of "o: Usage permitted” or “ ⁇ : Usage non-permitted” is selectable.
  • Pattern 2 shows that since the handling permission information on the method of use "reproduction” is set to " ⁇ : Usage non-permitted” at the export source DRM, export of right data is " ⁇ : impossible".
  • "-" in the table means that since no export is performed, no usage constraint information is set at the export destination DRM.
  • case 1-3 is applied to the conversion rule for converting right data, ("only one type of method of use is available to digital contents to be exported", "only the handling permission information is applicable at the export source DRM, only usage constraint information is applicable at the export destination DRM") "1.
  • the handling permission information on the method of use related to the contents exists at the export source, 1-1.
  • the handling permission information on the method of use related to the contents is "permitted” at the export source, right data is converted and exported so that all usage constraint information on the method of use related to the contents at the export destination is set to "no constraint".
  • the contents conversion section 67 first decides whether the handling permission information on the method of use (reproduction) related to the audio contents exists at the export source DRM or not (step S1001). When it decides that the handling permission information on the method of use (reproduction) does not exist at the export source (step S1001: NO), the contents conversion section 67 moves on to step S1002 and terminates this processing without exporting the right data.
  • step S1003 decides whether the handling permission information is set to "permitted” at the export source or not.
  • the handling permission information on the method of use "reproduction” related to the audio contents is set to "o: Usage permitted”.
  • the contents conversion section 67 decides that the handling permission information is set to "permitted” at the export source (step S1003: YES), moves on to step S1004 and decides whether the usage constraint information of the method of use related to the handling permission information can be set to "no constraint" for the export destination or not.
  • Pattern 1 in Table 4 contemplates the case where a count setting of "no constraint” is also possible as the usage constraint information "usage count” of the method of use "reproduction” related to the handling permission information.
  • the contents conversion section 67 decides that it is possible to set "no constraint” (step S1004: YES) and moves on to step S1005.
  • step S1005 the contents conversion section 67 converts and exports right data so that all usage constraint information on the method of use related to the audio contents is set to "no constraint" for the export destination and other usage constraint information is set to contents meaning "not available", and terminates this processing.
  • step S1004 decides in step S1004 that the usage constraint information on the method of use "reproduction” related to the handling permission information cannot be set to "no constraint" for the export destination (step S1004: NO)
  • the contents conversion section 67 moves on to step S1006, converts and exports right data so that the usage constraint on the method of use related to the contents is set to a state with the least settable constraint for the export destination and terminates this processing.
  • step S1003 when it decides in step S1003 that the handling permission information is set to "non-permitted" at the export source, that is, in the case of pattern 2 in Table 4, the contents conversion section 67 moves on to step S1002 and terminates this processing without exporting the right data.
  • the export source DRM adopts a right permission model
  • the export source DRM adopts a right permission model
  • the export destination DRM adopts a usage constraint model
  • the export source DRM can apply the handling permission information on the method of use corresponding to the digital contents
  • the export destination DRM can apply the usage constraint information on the method of use corresponding to the digital contents, executing conversion processing on the right data based on the conversion rule shown in case 1-3 based on the setting contents of the handling permission information on the method of use corresponding to the digital contents of one type of method of use at the export source allows the export destination DRM to convert right data so as to obtain usage permission equivalent to that at the export source DRM or the usage permission closest possible to the equivalent usage permission although in a direction in which the right is reduced, with the result that it is possible to perform export in such a way that the method of use of the exported digital contents is constrained appropriately according to the method of use permitted at the export source DRM.
  • case 1-4 when audio contents are exported from the export source DRM to the export destination DRM, case 1-4 is applied to the conversion rule for converting right data ("only one type of method of use is available to the digital contents to be exported", "both handling permission information and constraint information for the handling permission information are applicable at the export source DRM, and only the handling permission information is applicable at the export destination DRM") "1.
  • the handling permission information on the method of use related to the contents exists at both the export source and the export destination, 1-1 .
  • the handling permission information is "permitted” at the export source, 1-1-1.
  • the contents conversion section 67 first decides whether the handling permission information on the method of use (reproduction) related to the audio contents exists at both the export source and the export destination or not (step S1101). When it decides that the handling permission information on the method of use (reproduction) does not exist at both the export source and the export destination (step S1101 : NO), the contents conversion section 67 moves on to step S1102 and terminates this processing without exporting the right data.
  • step S1101: YES when it decides that the handling permission information on the method of use (reproduction) exists at both the export source and the export destination (step S1101: YES), the contents conversion section 67 moves on to step S1103 and decides whether the handling permission information is set to "permitted” at the export source or not. When it decides that the handling permission information is set to "permitted” at the export source (step S1103: YES), the contents conversion section 67 moves on to step S1104.
  • step S1104 the contents conversion section 67 decides whether all usage constraint information related to the handling permission information at the export source is "no constraint" or not. When it decides that all usage constraint information is set to "no constraint" (step S1104: YES), the contents conversion section 67 moves on to step S1105.
  • step S1105 the contents conversion section 67 set and exports right data so that the setting contents of the handling permission information are inherited to the export destination and all other handling permission information is set to "non-permitted", and terminates this processing.
  • step S1103 when it decides in step S1103 that the handling permission information is not set to "permitted" at the export source (step S1103: NO), the contents conversion section 67 moves on to step S1102, and terminates this processing without exporting the right data.
  • step S1104 when it decides in step S1104 that all usage constraint information related to the handling permission information at the export source is not set to "no constraint" (step S1104: NO), the contents conversion section 67 moves on to step S1102, and terminates this processing without exporting the right data.
  • case 1-5 is applied to the conversion rule for converting right data ("only one type of method of use is available to digital contents to be exported", "both handling permission information and constraint information for the handling permission information are applicable at both the export source DRM and the export destination DRM") "1.
  • handling permission information on the method of use related to the contents exists at both the export source and the export destination, 1-1.
  • the handling permission information is "permitted” at the export source, 1-1-1.
  • right data is not exported.
  • the handling permission information is "non-permitted" at the export source, right data is not exported.
  • the handling permission information on the method of use related to the contents does not exist at the export destination, right data is not exported.
  • right data is not exported.
  • the contents conversion section 67 first decides whether the handling permission information on the method of use (reproduction) related to the audio contents exists at both the export source and the export destination or not (step S1201). When it decides that the handling permission information on the method of use (reproduction) does not exist at both the export source and the export destination (step S1201: NO), the contents conversion section 67 moves on to step S1202 and terminates this processing without exporting the right data.
  • step S1203 decides whether the handling permission information is set to "permitted” at the export source or not.
  • step S1204 the contents conversion section 67 decides whether or not the export destination can realize a usage constraint equivalent to that at the export source with regard to the usage constraint information related to the handling permission information.
  • step S1204 NO
  • the contents conversion section 67 moves on to step S1205.
  • step S1205 the contents conversion section 67 decides whether or not the export destination can realize a stricter usage constraint than the export source with regard to the usage constraint information related to the handling permission information.
  • step S1205: YES the contents conversion section 67 moves on to step S1206.
  • step S1206 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information are inherited to the export destination, a usage constraint which is stricter than, yet as close as possible to that at the export source is set for the usage constraint information related to the handling permission information and all other handling permission information at the export destination is set to "non-permitted", and terminates this processing.
  • step S1204 when it decides in step S1204 that the export destination can realize a usage constraint equivalent to that at the export source (step S1204: YES) the contents conversion section 67 moves on to step S1207.
  • step S1207 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information are inherited to the export destination, the usage constraint information related to the handling permission information is set to a usage constraint equivalent to that at the export source and all other handling permission information at the export destination is set to "non-permitted" and terminates this processing.
  • step 1203 when it decides in step 1203 that the handling permission information is not set to "permitted" at the export source (step 1203: NO), the contents conversion section 67 moves on to step 1202 and terminates this processing without exporting the right data.
  • step S1205 when it decides in step S1205 that the export destination cannot realize a stricter usage constraint than the export source (step S1205: NO), the contents conversion section 67 moves on to step S1202 and terminates this processing without exporting the right data.
  • case 1-6 when contents are exported from the export source DRM to the export destination DRM, case 1-6 is applied to the conversion rule for converting right data ("only one type of method of use is available to the digital contents to be exported", "both the handling permission information and constraint information for the handling permission information are applicable at the export source DRM, only the constraint information is applicable at the export destination DRM") "1.
  • the handling permission information on the method of use related to the contents exists at the export source, 1-1.
  • the handling permission information is "permitted” at the export source, 1-1-1.
  • an equivalent usage constraint can be realized at the export destination DRM, right data is converted and exported so that an equivalent usage constraint is set. 1-1-2.
  • the contents conversion section 67 first decides whether the handling permission information on the method of use (reproduction) related to the audio contents exists at the export source or not (step S1301) . When it decides that the handling permission information on the method of use (reproduction) does not exist at the export source (step S1301: NO), the contents conversion section 67 moves on to step S1302 and terminates this processing without exporting the right data.
  • step S1301: YES when it decides that the handling permission information exists at the export source (step S1301: YES), the contents conversion section 67 moves on to step S1303, and decides whether the handling permission information is set to "permitted” at the export source or not. When it decides that the handling permission information is set to "permitted” at the export source (step S1303: YES), the contents conversion section 67 moves on to step S1304.
  • step S1304 the contents conversion section 67 decides whether or not the export destination can realize a usage constraint equivalent to that at the export source with regard to the usage constraint information related to the handling permission information.
  • step S1304: NO the contents conversion section 67 moves on to step S1305.
  • step S1305 the contents conversion section 67 decides whether or not the export destination can realize a stricter usage constraint than the export source with regard to the usage constraint information related to the handling permission information.
  • step S1305: YES the contents conversion section 67 moves on to step S1306.
  • step S1306 the contents conversion section 67 converts and exports right data so that a usage constraint which is stricter than, yet as close as possible to that at the export source is set for the export destination with regard to the usage constraint on the method of use related to the digital contents, and terminates this processing.
  • step S1304 when it decides in step S1304 that the export destination can realize a usage constraint equivalent to that at the export source (step S1304: YES), the contents conversion section 67 moves on to step S1307.
  • step S1307 the contents conversion section 67 converts and exports right data so that a usage constraint equivalent to that at the export source is set for the export destination with regard to the usage constraint on the method of use related to the digital contents, and terminates this processing.
  • step 1303 when it decides in step 1303 that the handling permission information is not set to "permitted" at the export source (step 1303: NO), the contents conversion section 67 moves on to step 1302 and terminates this processing without exporting the right data.
  • step S1305 when it decides in step S1305 that the export destination cannot realize a stricter usage constraint than the export source (step S1305: NO), the contents conversion section 67 moves on to step S1302, and terminates this processing without exporting the right data.
  • the matrix table in Table 5 shows examples where the export source DRM adopts "1-C: Usage constraint model” in Table 1, the export destination DRM adopts "1-A: Right permission model” in Table 1, and the export source DRM can apply the usage constraint information for the method of use "reproduction” and the export destination DRM can apply the handling permission information for the method of use "reproduction”.
  • the examples in Table 5 are right data conversion processing examples where the export source DRM is a DRM which can apply "reproduction count” and "reproduction period” as the usage constraint information, the export destination DRM is a DRM which can apply four of "execute”, "display”, "print” and "reproduction” as the handling permission information.
  • Pattern 1 shows that the usage constraint information on the method of use "reproduction” is set to "reproduction count: NO constraint” "reproduction period: NO constraint” at the export source DRM, and the handling permission information on the method of use “reproduction” related to the audio contents exists at the export destination DRM, and therefore right data is thereby exported by setting the setting content of the handling permission information to "permitted", that is, the export processing is "o: possible”. Furthermore, “ ⁇ ” in the table here indicates “ ⁇ : Usage non-permitted”.
  • Pattern 2 shows that since the usage constraint information for the method of use "reproduction” is set to "reproduction count: 3 times (with constraint)" at the export source DRM, export of the right data is " ⁇ : impossible”. Furthermore, "-" in the table here means that since no export is performed, handling permission information is not set at the export destination DRM.
  • Pattern 3 shows that since the usage constraint information for the method of use "reproduction” is set to "reproduction period: 3 days (with constraint)" at the export source DRM, export of the right data is " ⁇ : impossible”. Furthermore, "-" in the table here means that since no export is performed, handling permission information is not set at the export destination DRM.
  • Pattern 4 shows that the usage constraint information for the method of use "reproduction” is set to "reproduction count: 3 times (with constraint)” "reproduction period: 3 days (with constraint)” at the export source DRM, export of the right data is " ⁇ : impossible”. Furthermore, "-" in the table here means that since no export is performed, the handling permission information is not set at the export destination DRM.
  • case 1-7 is applied to the conversion rule for converting right data ("only one type of method of use is available to digital contents to be exported", “only the constraint information is applicable at the export source DRM and only the handling permission information is applicable at the export destination DRM") "1.
  • all usage constraint information related to the contents is "no constraint" at the export source, 1-1.
  • the handling permission information on the method of use related to the contents exists at the export destination, right data is converted and exported so that the handling permission information content is set to "permitted”. 1-2.
  • the handling permission information on the method of use related to the contents does not exist at the export destination, right data is not exported. 2.
  • at least one piece of usage constraint information at the export source is other than "no constraint", right data is not exported”.
  • the contents conversion section 67 first decides whether all usage constraint information on the method of use related to the audio contents is set to "no constraint" at the export source or not (step S1401). In pattern 1 in Table 5, "reproduction count” and “reproduction period” which are usage constraint information at the export source DRM are all set to "no constraint”. For this reason, the contents conversion section 67 decides that all usage constraint information is set to "no constraint" (step S1401: YES) and moves on to step S1403.
  • step S1403 the contents conversion section 67 decides whether the handling permission information on the method of use (reproduction) related to the audio contents exists at export destination or not (step S1403) . Since in pattern 1 in Table 5, the handling permission information on the method of use "reproduction" at the export destination DRM exists, the contents conversion section 67 decides that the handling permission information exists at the export destination (step S1403: YES) and moves on to step S1404.
  • step S1404 the contents conversion section 67 converts and exports right data so that the setting content of the handling permission information related to the audio contents is set to "permitted” for the export destination and terminates this processing. Therefore, in pattern 1 in Table 5, right data is converted and exported so that the setting content of the handling permission information related to the audio contents is set to "permitted” for the export destination and all other handling permission information is set to "non-permitted”.
  • the usage constraint information on the method of use related to the audio contents is set to "reproduction count: 3 times (with constraint)” or “reproduction period: 3 days (with constraint)”.
  • the contents conversion section 67 decides in step S1401 that all usage constraint information related to the audio contents is not set to "no constraint" at the export source (step S1401: NO), moves on to step S1402 and terminates this processing without exporting the right data.
  • step S1403 when it decides in step S1403 that the handling permission information on the method of use (reproduction) related to the audio contents does not exist at the export destination (step S1403: NO), the contents conversion section 67 moves on to step S1402 and terminates this processing without exporting the right data.
  • case 1-8 is applied to the conversion rule for converting right data ("only one type of method of use is available to digital contents to be exported” "only constraint information is applicable at the export source DRM, both handling permission information and usage constraint information are applicable at the export destination DRM) "1.
  • the handling permission information on the method of use related to the contents exists at the export destination DRM, 1-1 .
  • an equivalent usage constraint can be realized at the export destination DRM, right data is converted and exported so that the handling permission information content is set to "permitted” for the export destination and an equivalent usage constraint is set (however, all other handling permission information at the export destination is set to "non-permitted”).
  • the contents conversion section 67 first decides whether the handling permission information on the method of use (reproduction) related to the audio contents exists at the export destination or not (step S1501). When it decides that the handling permission information on the method of use (reproduction) does not exist at the export destination (step S1501: NO), the contents conversion section 67 moves on to step S1502 and terminates this processing without exporting the right data.
  • step S1501: YES when it decides that the handling permission information on the method of use (reproduction) exists at the export destination (step S1501: YES), the contents conversion section 67 moves on to step S1503, and decides whether or not the export destination can realize a usage constraint equivalent to that at the export source with regard to the usage constraint information related to the handling permission information.
  • step S1503: NO the contents conversion section 67 moves on to step S1504.
  • step S1504 the contents conversion section 67 decides whether or not the export destination can realize a stricter usage constraint than the export source with regard to the usage constraint information related to the handling permission information.
  • step S1504: NO the contents conversion section 67 moves on to step S1505.
  • step S1505 the contents conversion section 67 converts and exports right data so that the setting content of the handling permission information related to the audio contents is set to "permitted" for the export destination, the usage constraint information related to the handling permission information is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all other handling permission information at the export destination is set to "non-permitted", and terminates this processing.
  • step S1503 when it decides in step S1503 that with regard to the usage constraint information related to the handling permission information, the export destination can realize a usage constraint equivalent to that at the export source (step S1503: YES), the contents conversion section 67 moves on to step S1506.
  • step S1506 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information related to the audio contents are set to "permitted" for the export destination, a usage constraint equivalent to that at the export source is set as the usage constraint information related to the handling permission information and all other handling permission information at the export destination is set to "non-permitted", and terminates this processing.
  • step S1504 when it decides in step S1504 that with regard to the usage constraint information related to the handling permission information, the export destination cannot realize a stricter usage constraint than the export source (step S1504: NO), the contents conversion section 67 moves on to step S1502 and terminates this processing without exporting the right data.
  • case 1-9 is applied to the conversion rule for converting right data ("only one type of method of use is available to digital contents to be exported", "only the constraint information is applicable at both the export source DRM and the export destination DRM") "1.
  • the usage constraint information on the method of use related to the contents exists at the export source, 1-1.
  • right data is converted and exported so that an equivalent usage constraint is set. 1-2.
  • the contents conversion section 67 first decides whether the usage constraint information on the method of use (reproduction) related to the audio contents exists at the export source or not (step S1601). When it decides that the usage constraint information on the method of use (reproduction) does not exist at the export source (step S1601:NO), the contents conversion section 67 moves on to step S1602 and terminates this processing without exporting the right data.
  • step S1603 decides whether or not the export destination can realize a usage constraint equivalent to that at the export source with regard to the usage constraint information on the method of use related to the contents.
  • step S164 the contents conversion section 67 moves on to step S1604.
  • step S1604 the contents conversion section 67 decides whether or not the export destination can realize a stricter usage constraint than the export source with regard to the usage constraint information on the method of use related to the contents.
  • step S1604: YES the contents conversion section 67 moves on to step S1605.
  • step S1605 the contents conversion section 67 converts and exports right data so that with regard to the usage constraint information on the method of use related to the contents, a usage constraint which is stricter than, yet as close as possible to that at the export source is set for the export destination, and terminates this processing.
  • step S1603 when it decides in step S1603 that with regard to the usage constraint information on the method of use related to the contents, the export destination can realize a usage constraint equivalent to that at the export source (step S1603: YES), the contents conversion section 67 moves on to step S1606.
  • step S1606 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use related to the contents is set to a usage constraint equivalent to that at the export source for the export destination, and terminates this processing.
  • step S1604 when it decides in step S1604 that with regard to the usage constraint information on the method of use related to the contents, the export destination cannot realize a stricter usage constraint than the export source (step S1604: NO), the contents conversion section 67 moves on to step S1602 and terminates this processing without exporting the right data.
  • the matrix table in Table 6 shows an example where both the export source DRM and the export destination DRM adopt "2-E: Right permission + usage constraint model (two types of method of use are individually supported)" in Table 2 and both the export source DRM and the export destination DRM can apply handling permission information and constraint information.
  • Table 6 is an example of right data conversion processing where the export source DRM is a DRM to which four of "execute”, “display”, “print” and “reproduction” are applicable as the handling permission information and two of "display count” and “print count” are applicable as usage constraint information, while the export destination DRM is a DRM to which four of "execute”, “display”, “print” and “reproduction” are applicable as the handling permission information and three of "display count”, "print count” and “reproduction count” are applicable as the usage constraint information.
  • this example shows a case where "0 times (not available)/1 time/2 times/ ⁇ /9 times/10 times/no constraint” can be set for the usage constraint information "display count” and "print count” at the export source DRM and "0 times(not available)/1 time/2 times/3 times/4 times/5 times/no constraint” can be set for the usage constraint information "display count”, "print count” and "reproduction count” at the export destination DRM.
  • Pattern 1 shows an example where both pieces of the handling permission information on the two methods of use “display” and “print” available to digital contents to be exported at the export source DRM are set to “o: Usage permitted” and the usage constraint information on the methods of use “display” and “print” is set to "display count: No constraint” and "print count: No constraint”.
  • Pattern 2 shows an example where both pieces of the handling permission information for two methods of use "display” and “print” available to digital contents to be exported at the export source DRM are set to "o: Usage permitted” and usage constraint information for the respective methods of use "display” and “print” is set to "display count: No constraint", "print count: 10 times”.
  • Pattern 3 shows an example where both pieces of the handling permission information on the two methods of use “display” and “print” available to digital contents to be exported at the export source DRM are set to "o: Usage permitted” and the usage constraint information on the respective methods of use “display” and “print” is set to "display count: No constraint", "print count: 3 times".
  • Pattern 4 shows an example where both pieces of the handling permission information on the two methods of use "display” and “print” available to digital contents to be exported at the export source DRM are set to "o: Usage permitted” and the usage constraint information of the respective methods of use "display” and “print” is set to "display count: 10 times", “print count: No constraint”.
  • pattern 5 shows an example where both pieces of the handling permission information on the two methods of use "display” and “print” available to digital contents to be exported at the export source DRM are set to "o: Usage permitted” and the usage constraint information on the respective methods of use "display” and “print” is set to "display count: 10 times", “print count: 10 times”.
  • Pattern 6 shows an example where both pieces of the handling permission information on the two methods of use "display” and “print” available to digital contents to be exported at the export source DRM are set to "o: Usage permitted” and the usage constraint information on the respective methods of use "display” and “print” is set to "display count: 10 times", “print count: 3 times”.
  • Pattern 7 shows an example where both pieces of the handling permission information on the two methods of use “display” and “print” available to digital contents to be exported at the export source DRM are set to "o: Usage permitted” and the usage constraint information on the respective methods of use “display” and “print” is set to "display count: 3 times", “print count: No constraint”.
  • Pattern 8 shows an example where both pieces of the handling permission information on the two methods of use "display” and “print” available to digital contents to be exported at the export source DRM are set to "o: Usage permitted” and the usage constraint information on the respective methods of use "display” and “print” is set to "display count : 3 times", “print count: 10 times”.
  • Pattern 9 shows an example where both pieces of the handling permission information on the two methods of use “display” and “print” available to digital contents to be exported at the export source DRM are set to "o: Usage permitted” and the usage constraint information on the respective methods of use “display” and “print” is set to "displaycount: 3 times", “print count: 3 times”.
  • Pattern 10 shows an example where the handling permission information on the method of use "display” available to digital contents to be exported at the export source DRM is set to "o: Usage permitted", the handling permission information on the method of use "print” is set to "x: Usage non-permitted” and the usage constraint information on the method of use "display” is set to "display count: No constraint”.
  • Pattern 11 shows an example where the handling permission information on the method of use "display” available to digital contents to be exported at the export source DRM is set to "o: Usage permitted", the handling permission information on the method of use "print” is set to " ⁇ : Usage non-permitted” and the usage constraint information on the method of use "display” is set to "display count: 10 times".
  • Pattern 12 shows an example where the handling permission information on the method of use "display" available to digital contents to be exported at the export source DRM is set to "o: Usage permitted", the handling permission information on the method of use "print” is set to " ⁇ : Usage non-permitted” and the usage constraint information on the method of use "display” is set to "display count: 3 times".
  • Pattern 13 shows an example where the handling permission information on the method of use "print” available to digital contents to be exported at the export source DRM is set to "o: Usage permitted", the handling permission information on the method of use "display” is set to " ⁇ : Usage non-permitted” and the usage constraint information on the method of use "print” is set to "print count: No constraint”.
  • Pattern 14 shows an example where only the handling permission information on the method of use "print” available to digital contents to be exported at the export source DRM is set to "o: Usage permitted", the handling permission information on the method of use "display” is set to " ⁇ : Usage non-permitted” and the usage constraint information on the method of use "print” is set to "print count: 10 times".
  • Pattern 15 shows an example where the handling permission information on the method of use "print” available to digital contents to be exported at the export source DRM is set to "o: Usage permitted", the handling permission information on the method of use "display” is set to " ⁇ : Usage non-permitted” and the usage constraint information on the method of use "print” is set to "print count: 3 times".
  • Pattern 16 shows that both pieces of the handling permission information on the method of use "display” and "print” at the export source DRM are set to "x: Usage non-permitted", and therefore right data is not exported, that is, the export processing is "x: impossible”.
  • case 2-53 is applied to the conversion rule for converting right data, (there are two types (X, Y) of method of use available to "digital contents to be exported", “the handling permission information and the constraint information for the handling permission information are applicable at both the export source DRM and the export destination DRM") "1.
  • both pieces of the handling permission information on the two methods of use (X, Y) are "permitted” at the export source, 1-1.
  • the usage constraint information on the handling permission information on the method of use Y at the export destination DRM allows a description in a direction in which the usage constraint is tightened compared to the export source, right data is converted and exported so that the handling permission information contents of methods of use X and Y are set to "permitted" for the export destination, the usage constraint information content on the handling permission information on the method of use X at the export destination is set to a usage constraint equivalent to that at the export source and the usage constraint information content on the handling permission information on the method of use Y is set to the closest possible usage constraint content with a tightened usage constraint with respect to the export source (however, all other handling permission information at the export destination is set to "non-permitted")" is applied.
  • the usage constraint information content on the handling permission information on the method of use Y at the export destination is set to a usage constraint equivalent to that at the export source and the usage constraint information content for the handling permission information on the method of use X is set to the closest possible usage constraint content with a tightened usage constraint with respect to the export source (however, all other handling permission information at the export destination is set to "non-permitted")" is applied.
  • the contents conversion section 67 first decides whether both pieces of the handling permission information indicating two methods of use X "display” and Y "print” available to the wallpaper contents are set to "permitted” at the export source (FIG.17: step S1701) or not.
  • step S1701 in FIG.17 when it decides in step S1701 in FIG.17 that the handling permission information indicating none of two methods of use X "display”, Y "print” is set to "permitted” at the export source (patterns 10 to 16 in Table 6) (step S1701: NO), the contents conversion section 67 moves on to step S1702, decides whether both pieces of the handling permission information on the two methods of use X, Y available to wallpaper contents are set to "non-permitted” at the export source or not. In patterns 10 to 15 out of patterns 10 to 16 in Table 6, one or both of the handling permission information indicating the two methods of use "display/print” of wallpaper contents is/are set to "o: Usage permitted". For this reason, the contents conversion section 67 decides that the handling permission information indicating the two methods of use "display/print” are not set to "non-permitted” (step S1702: NO) and moves on to step S1704.
  • step S1702 when it decides that both pieces of the handling permission information indicating the two methods of use "display/print" are set to "non-permitted” (pattern 16 in Table 6) (step S1702: YES), the contents conversion section 67 moves on to step S1703 and terminates this processing without exporting the right data.
  • step S1704 the contents conversion section 67 decides whether the handling permission information indicating the method of use X "display” available to wallpaper contents is set to "permitted” at the export source or not. In patterns 10 to 12 out of patterns 10 to 15 in Table 6, the handling permission information indicating the method of use X "display” is set to "permitted” at the export source. For this reason, the contents conversion section 67 decides that the handling permission information indicating the method of use X "display” is set to "permitted” at the export source (step S1704: YES) and moves on to step S1722 in FIG.22.
  • step S1704: NO when it decides that the handling permission information indicating the method of use X "display" is not set to "permitted” at the export source (patterns 13 to 15 in Table 6) (step S1704: NO), the contents conversion section 67 moves on to step S1727 in FIG.23.
  • step S1701 in FIG.17 when it decides in step S1701 in FIG.17 that both pieces of the handling permission information indicating the methods of use X, Y are set to "permitted" at the export source (patterns 1 to 9 in Table 6) (step S1701: YES), the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating both methods of use X, Y at the export destination can set a usage constraint equivalent to that at the export source or not in step S1705 in FIG.18.
  • the usage constraint information "display count/print count” at the export source is set to "no constraint” for the two methods of use “display/print” of wallpaper contents, and it is likewise possible to set "no constraint” at the export destination. For this reason, the contents conversion section 67 decides that an equivalent usage constraint can be set (step S1705: YES) and moves on to step S1706. (Patterns 3, 7, 9 in Table 6 also correspond to this case).
  • step S1706 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information on both methods of use X, Y are set to "permitted" for the export destination, the usage constraint information on the handling permission information on both methods of use X, Y at the export destination is set to a usage constraint equivalent to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1705 when it decides in step S1705 in FIG.18 that both pieces of the usage constraint information cannot set the same usage constraint (e.g., pattern 2 in Table 6) (step S1705: NO), the contents conversion section 67 moves on to step S1707.
  • step S1707 the contents conversion section 67 decides whether both pieces of the usage constraint information on the handling permission information indicating the methods of use X, Y at the export destination can set a usage constraint equivalent to that at the export source or not.
  • step S1707: YES the contents conversion section 67 moves on to step S1715 in FIG.21.
  • step S1707 when it decides in step S1707 in FIG.18 that it is not impossible to set both pieces of usage constraint information to an equivalent usage constraint (e.g., patterns 2, 4, 6, 8 in Table 6) (step S1707: NO), the contents conversion section 67 moves on to step S1708.
  • step S1708 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating the method of use X "display" at the export destination can set a usage constraint equivalent to that at the export source or not.
  • step S1708 in FIG.18 When it decides in step S1708 in FIG.18 that a usage constraint equivalent to that at the export source can be set (e.g., patterns 2, 8 in Table 6) (step S1708: YES), the contents conversion section 67 moves on to step S1709 in FIG.19. Furthermore, when it decides in step S1708 in FIG.18 that a usage constraint equivalent to that at the export source cannot be set (e.g., patterns 4, 6 in Table 6) (step S1708: NO), the contents conversion section 67 moves on to step S1712 in FIG.20.
  • a usage constraint equivalent to that at the export source e.g., patterns 2, 8 in Table 6
  • step S1708: NO the contents conversion section 67 moves on to step S1712 in FIG.20.
  • step S1709 in FIG.19 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating the method of use Y "print” at the export destination can set a stricter usage constraint than the export source or not. For example, in pattern 2 in Table 6, for the usage constraint "print count: 10" on the handling permission information indicating the method of use Y "print” at the export source, usage constraint information "print count: 5" can be set at the export destination. For this reason, the contents conversion section 67 decides that a stricter usage constraint than the export source can be set (step S1709: YES) and moves on to step S1711 (pattern 8 in Table 6 also corresponds to this case).
  • step S1711 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the methods of use X, Y are set to "permitted" for the export destination, the usage constraint information on the method of use X at the export destination is set to a usage constraint equivalent to that at the export source, the usage constraint information on the method of use Y at the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all handling permission information at the export destination other than the relevant permission information is set to "non-permitted".
  • step S1709 when it decides in step S1709 in FIG.19 that a stricter usage constraint than the export source cannot be set (step S1709: NO), the contents conversion section 67 moves on to step S1710.
  • step S1710 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the method of use X are set to "permitted" for the export destination, the usage constraint information on the handling permission information indicating the method of use X is set to a usage constraint equivalent to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1712 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating the method of use X at the export destination can set a stricter usage constraint than the export source or not. For example, in pattern 4 in Table 6, for the usage constraint "display count: 10" on the handling permission information indicating the method of use X "display” at the export source, the usage constraint information at the export destination can set "display count: 5". For this reason, the contents conversion section 67 decides that a stricter usage constraint than the export source can be set (step S1712: YES) and moves on to step S1714. (Pattern 6 in Table 6 also corresponds to this case.)
  • step S1714 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating methods of use X, Y are set to "permitted" for the export destination, the usage constraint information related to the method of use Y at the export destination is set to a usage constraint equivalent to that at the export source, the usage constraint information related to the method of use X at the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1712 when it decides in step S1712 in FIG.20 that a stricter usage constraint than the export source cannot be set (step S1712: NO), the contents conversion section 67 moves on to step S1713.
  • step S1713 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the method of use X is set to "permitted" for the export destination, the usage constraint information on the handling permission information indicating the method of use Y is set to a usage constraint equivalent to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1715 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating both methods of use X, Y at the export destination can set a stricter usage constraint than the export source.
  • step S1715: YES When it decides that a stricter usage constraint than the export source can be set (e.g., pattern 5 in Table 6) (step S1715: YES), the contents conversion section 67 moves on to step S1716.
  • step S1716 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the methods of use X, Y are set to "permitted" for the export destination, the usage constraint information on the handling permission information on both methods of use X, Y at the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1715 when it decides in step S1715 in FIG.21 that the usage constraint information on the handling permission information indicating the methods of use X, Y at the export destination cannot set a stricter usage constraint than the export source (step S1715: NO), the contents conversion section 67 moves on to step S1717.
  • step S1717 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating both methods of use X, Y at the export destination is unable to set a stricter usage constraint than the export source or not.
  • step S1717: YES When it decides that the usage constraint information on the handling permission information indicating the methods of use X, Y at the export destination is unable to set a stricter usage constraint than the export source (step S1717: YES), the contents conversion section 67 moves on to step S1718 and does not export right data. Furthermore, when it decides that the usage constraint information on the handling permission information indicating both methods of use X, Y at the export destination is not unable to set a stricter usage constraint than the export source (step S1717: NO), the contents conversion section 67 moves on to step S1719.
  • step S1719 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating the method of use X at the export destination can set a stricter usage constraint than the export source or not.
  • step S1719: YES the contents conversion section 67 moves on to step S1720.
  • step S1720 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the method of use X is set to "permitted" for the export destination, the usage constraint information on the handling permission information indicating the method of use X is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1719 in FIG.21 when it decides in step S1719 in FIG.21 that the usage constraint information on the handling permission information indicating the method of use X at the export destination cannot set a stricter usage constraint than the export source (step S1719: NO), the contents conversion section 67 moves on to step S1721.
  • step S1721 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the method of use Y are set to "permitted" for the export destination, the usage constraint information related to the handling permission information indicating the method of use Y is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1722 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating the method of use X at the export destination can set a usage constraint equivalent to that at the export source or not.
  • a usage constraint similar to that at the export source can be set (e.g., patterns 10, 12 in Table 6) (step S1722: YES)
  • step S1722: YES the contents conversion section 67 moves on to step S1723.
  • step S1723 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the method of use X are set to "permitted" for the export destination, the usage constraint information on the handling permission information indicating the method of use X is set to a usage constraint equivalent to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1724 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating the method of use X at the export destination can set a stricter usage constraint than the export source or not.
  • a stricter usage constraint than the export source e.g., pattern 11 in Table 6
  • step S1724: YES the contents conversion section 67 moves on to step S1725.
  • step S1725 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the method of use X are set to "permitted" for the export destination, the usage constraint information on the handling permission information indicating the method of use X is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1724 when it decides in step S1724 in FIG.22 that the usage constraint information on the handling permission information indicating the method of use X at the export destination cannot set a stricter usage constraint than the export source (step S1724: NO), the contents conversion section 67 moves on to step S1726, and terminates this processing without exporting the right data.
  • step S1727 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating the method of use Y at the export destination can set a usage constraint equivalent to that at the export source or not.
  • a usage constraint similar to that at the export source can be set (e.g., patterns 13, 15 in Table 6) (step S1727: YES)
  • step S1728 the contents conversion section 67 moves on to step S1728.
  • step S1728 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the method of use Y are set to "permitted" for the export destination, the usage constraint information on the handling permission information indicating the method of use Y is set to a usage constraint equivalent to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1727 in FIG.23 when it decides in step S1727 in FIG.23 that the usage constraint information on the handling permission information indicating the method of use Y at the export destination cannot set a usage constraint equivalent to that at the export source (step S1727: NO), the contents conversion section 67 moves on to step S1729.
  • step S1729 the contents conversion section 67 decides whether the usage constraint information on the handling permission information indicating the method of use Y at the export destination can set a stricter usage constraint than the export source or not.
  • a stricter usage constraint than the export source e.g., pattern 14 in Table 6
  • step S1729: YES the contents conversion section 67 moves on to step S1730.
  • step S1730 the contents conversion section 67 converts and exports right data so that the setting contents of the handling permission information indicating the method of use Y are set to "permitted" for the export destination, the usage constraint information related to the handling permission information indicating the method of use Y is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all handling permission information at the export destination other than the relevant handling permission information is set to "non-permitted".
  • step S1729 when it decides in step S1729 in FIG.23 that the usage constraint information on the handling permission information indicating the method of use Y at the export destination cannot set a stricter usage constraint than the export source (step S1729: NO), the contents conversion section 67 moves on to step S1731 and terminates this processing without exporting the right data.
  • case 2-57 is applied to the conversion rule for converting right data ("there are two types of methods of use (X, Y) available to digital contents to be exported", "both the handling permission information and constraint information for the handling permission information are applicable at the export source DRM, only the constraint information is applicable at the export destination DRM") "1.
  • both pieces of the handling permission information indicating two methods of use (X, Y) are "permitted” at the export source, 1-1.
  • the usage constraint information on the method of use Y at the export destination DRM can make a setting in a direction in which the usage constraint is tightened compared to the export source
  • right data is converted and exported so that the setting contents of the usage constraint information on the method of use X are set to a usage constraint equivalent to that at the export source for the export destination and the setting contents of the usage constraint information on the method of use Y at the export destination are set to the closest possible usage constraint content with a tightened usage constraint with respect to the export source" (however, all other usage constraint information at the export destination is set to contents meaning "not available”) is applied.
  • the usage constraint information on the method of use X at the export destination DRM can make a setting in a direction in which the usage constraint is tightened compared to the export source
  • right data is converted and exported so that the setting contents of the usage constraint information on the method of use Y are set to a usage constraint equivalent to that at the export source for the export destination and the setting contents of the usage constraint information on the method of use X at the export destination are set to the closest possible usage constraint content with a tightened usage constraint with respect to the export source (however, all other usage constraint information at the export destination is set to contents meaning "not available") " is applied.
  • the contents conversion section 67 first decides whether both pieces of the handling permission information indicating the two methods of use X, Y available to the contents are set to "permitted” at the export source or not (FIG.24: step S2401) . When it decides that both pieces of the handling permission information indicating the two methods of use X, Y are set to "permitted” at the export source (step S2401: YES), the contents conversion section 67 moves on to step S2405 in FIG.25.
  • step S2401 in FIG.24 when it decides in step S2401 in FIG.24 that both pieces of the handling permission information indicating the two methods of use X, Y are not set to "permitted” at the export source (step S2401: NO), the contents conversion section 67 moves on to step S2402 and decides whether both pieces of the handling permission information indicating the two methods of use X, Y available to the contents are set to "non-permitted” at the export source or not. When it decides that both pieces of the handling permission information indicating the two methods of use X, Y are not set to "non-permitted” at the export source (step S2402: NO), the contents conversion section 67 moves on to step S2404.
  • step S2402 when it decides in step S2402 in FIG.24 that both pieces of the handling permission information indicating the two methods of use X, Y are set to "non-permitted" at the export source (step S2402: YES), the contents conversion section 67 moves on to step S2403 and terminates this processing without exporting the right data.
  • the contents conversion section 67 decides in step S2404 in FIG.24 whether the handling permission information indicating the method of use X is set to "permitted” at the export source or not. When it decides that the handling permission information indicating the method of use X is set to "permitted” at the export source (step S2404: YES), the contents conversion section 67 moves on to step S2422 in FIG.29.
  • step S2404 when it decides that the handling permission information indicating the method of use X is not set to "permitted" at the export source (step S2404: NO), the contents conversion section 67 moves on to step S2427 in FIG.30.
  • step S2401 in FIG.24 When it decides in step S2401 in FIG.24 that both pieces of the handling permission information indicating the methods of use X, Y are set to "permitted" at the export source (step S2401: YES), the contents conversion section 67 moves on to step S2405 in FIG. 25.
  • step S2405 the contents conversion section 67 decides whether the usage constraint information on the methods of use X, Y at the export destination can set a usage constraint equivalent to that at the export source or not. When it decides that the usage constraint information on the methods of use X, Y at the export destination can set a usage constraint equivalent to that at the export source (step S2405: YES), the contents conversion section 67 moves on to step S2406.
  • step S2406 the contents conversion section 67 converts and exports right data so that the usage constraint information on the two methods of use X, Y for the export destination is set to a usage constraint equivalent to that at the export source and all usage constraint information on the method of use other than the two methods of use X, Y is set to contents meaning "not available”.
  • step S2405 when it decides in step S2405 in FIG.25 that the respective pieces of usage constraint information on both methods of use X, Y at the export destination cannot set a usage constraint equivalent to that at the export source (step S2405: NO), the contents conversion section 67 moves on to step S2407.
  • step S2407 the contents conversion section 67 decides whether both pieces of the usage constraint information on the two methods of use X, Y at the export destination can set a usage constraint equivalent to that at the export source or not.
  • step S2407: YES the contents conversion section 67 moves on to step S2415 in FIG.28.
  • step S2407 when it decides in step S2407 in FIG.25 that both pieces of usage constraint information on the two methods of use X, Y at the export destination cannot set a usage constraint equivalent to that at the export source (step S2407: NO), the contents conversion section 67 moves on to step S2408.
  • step.S2408 the contents conversion section 67 decides whether the usage constraint information on the method of use X at the export destination can set a usage constraint equivalent to that at the export source or not.
  • step S2408 in FIG.25 When it decides in step S2408 in FIG.25 that the usage constraint information on the method of use X at the export destination can set a usage constraint equivalent to that at the export source (step S2408: YES), the contents conversion section 67 moves on to step S2409 in FIG.26. Furthermore, when it decides in step S2408 in FIG.25 that the usage constraint information on the method of use X at the export destination cannot set a usage constraint equivalent to that at the export source (step S2408: NO), the contents conversion section 67 moves on to step S2412 in FIG.27.
  • step S2409 in FIG.26 the contents conversion section 67 decides whether the usage constraint information on the method of use Y at the export destination can set a stricter usage constraint than the export source or not.
  • step S2409: YES the contents conversion section 67 moves on to step S2411.
  • step S2411 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use X for the export destination is set to a usage constraint equivalent to that at the export source, the usage constraint information on the method of use Y at the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all usage constraint information on the method of use other than the two methods of use X, Y at the export destination is set to contents meaning "not available”.
  • step S2409 when it decides in step S2409 in FIG.26 that the usage constraint information on the method of use Y at the export destination cannot be set to a stricter usage constraint than the export source (step S2409: NO), the contents conversion section 67 moves on to step S2410.
  • step S2410 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use X for the export destination is set to a usage constraint equivalent to that at the export source and all usage constraint information on the method of use other than the method of use X at the export destination is set to contents meaning "not available".
  • step S2412 the contents conversion section 67 decides whether the usage constraint information on the method of use X at the export destination can set a stricter usage constraint than the export source or not.
  • step S2413 the contents conversion section 67 moves on to step S2413.
  • step S2413 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use Y for the export destination is set to a usage constraint equivalent to that at the export source, all usage constraint information on the method of use other than the method of use Y at the export destination is set to contents meaning "not available”.
  • step S2412 when it decides in step S2412 in FIG.27 that the usage constraint information on the method of use X at the export destination can set a stricter usage constraint than the export source (step S2412: YES), the contents conversion section 67 moves on to step S2414.
  • step S2414 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use Y for the export destination is set to a usage constraint equivalent to that at the export source, the usage constraint information on the method of use X at the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all usage constraint information on the method of use other than the two methods of use X, Y at the export destination is set to contents meaning "not available”.
  • step S2415 the contents conversion section 67 decides whether the respective usage constraints on the two methods of use X, Y at the export destination can set a stricter usage constraint than the export source or not.
  • step S2415 When it decides in step S2415 in FIG.28 that the respective usage constraints on the two methods of use X, Y at the export destination can set a stricter usage constraint than the export source (step S2415: YES), the contents conversion section 67 moves on to step S2416.
  • step S2416 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use X for the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source, the usage constraint information on the method of use Y at the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all usage constraint information on the method of use other than the two methods of use X, Y at the export destination is set to contents meaning "not available”.
  • step S2415 when it decides in step S2415 in FIG.28 that the respective usage constraints on the two methods of use X, Y at the export destination cannot set a stricter usage constraint than the export source (step S2415: NO), the contents conversion section 67 moves on to step S2417.
  • step S2417 the contents conversion section 67 decides whether both usage constraints on the two methods of use X, Y at the export destination can set a stricter usage constraint than the export source or not.
  • step S2417 in FIG.28 When it decides in step S2417 in FIG.28 that the respective usage constraints on the two methods of use X, Y at the export destination cannot set a stricter usage constraint than the export source (step S2417: YES), the contents conversion section 67 moves on to step S2418 and does not export right data. Furthermore, when it decides in step S2417 in FIG.28 that the respective usage constraints on the two methods of use X, Y at the export destination are not unable to set a stricter usage constraint than the export source (step S2417: NO), the contents conversion section 67 moves on to step S2419.
  • step S2419 the contents conversion section 67 decides whether the usage constraint information on the method of use X at the export destination can set a stricter usage constraint than the export source or not.
  • step S2419: YES the contents conversion section 67 moves on to step S2420.
  • step S2420 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use X for the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all usage constraint information on the method of use other than the two methods of use X and Y at the export destination is set to contents meaning "not available”.
  • step S2419 when it decides in step S2419 in FIG.28 that the usage constraint information on the method of use X at the export destination cannot set a stricter usage constraint than the export source (step S2419: NO), the contents conversion section 67 moves on to step S2421 .
  • step S2421 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use Y for the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all usage constraint information on the method of use other than the two methods of use X, Y at the export destination is set to contents meaning "not available".
  • step S2422 the contents conversion section 67 decides whether the usage constraint information on the method of use X at the export destination can set a usage constraint equivalent to that at the export source or not.
  • step S2422 the usage constraint information on the method of use X at the export destination can set a usage constraint equivalent to that at the export source (step S2422: YES)
  • step S2423 the contents conversion section 67 moves on to step S2423.
  • step S2423 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use X for the export destination is set to a usage constraint equivalent to that at the export source and all usage constraint information on the method of use other than the method of use X at the export destination is set to contents meaning "not available”.
  • step S2422 in FIG.29 when it decides in step S2422 in FIG.29 that the usage constraint information on the method of use X at the export destination cannot set a usage constraint equivalent to that at the export source (step S2422 : NO), the contents conversion section 67 moves on to step S2424.
  • step S2424 the contents conversion section 67 decides whether the usage constraint information on the method of use X at the export destination can set a stricter usage constraint than the export source or not.
  • step S2424: YES the contents conversion section 67 moves on to step S2425.
  • step S2425 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use X for the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all usage constraint information on the method of use other than the method of use X at the export destination is set to contents meaning "not available”.
  • step S2424 when it decides in step S2424 in FIG.29 that the usage constraint information on the method of use X at the export destination cannot set a stricter usage constraint than the export source (step S2424: NO), the contents conversion section 67 moves on to step S2426 and terminates this processing without exporting the right data.
  • step S2427 the contents conversion section 67 decides whether the usage constraint information on the method of use Y at the export destination can set a usage constraint equivalent to that at the export source or not.
  • step S2427 the usage constraint information on the method of use Y at the export destination can set a usage constraint equivalent to that at the export source (step S2427: YES)
  • step S2428 the contents conversion section 67 moves on to step S2428.
  • step S2428 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use Y for the export destination is set to a usage constraint equivalent to that at the export source and all usage constraint information on the method of use other than the method of use Y at the export destination is set to contents meaning "not available”.
  • step S2427 in FIG.30 when it decides in step S2427 in FIG.30 that the usage constraint information on the method of use Y at the export destination cannot set a usage constraint equivalent to that at the export source (step S2427: NO), the contents conversion section 67 moves on to step S2429.
  • step S2429 the contents conversion section 67 decides whether the usage constraint information on the methodof use Y at the export destination can set a stricter usage constraint than the export source or not.
  • step S2429: YES the contents conversion section 67 moves on to step S2430.
  • step S2430 the contents conversion section 67 converts and exports right data so that the usage constraint information on the method of use Y for the export destination is set to a usage constraint which is stricter than, yet as close as possible to that at the export source and all usage constraint information unrelated to on the method of use other than the method of use Y at the export destination is set to contents meaning "not available”.
  • step S2429 when it decides in step 2429 in FIG.30 that the usage constraint information on the method of use Y at the export destination cannot set a stricter usage constraint than the export source (step S2429: NO), the contents conversion section 67 moves on to step S2431 and terminates this processing without exporting the right data.
  • the present invention has the advantage of providing a data processing apparatus that is capable of updating right data and making contents available to users of digital contents and such, when contents data is converted to be compatible with different contents handling systems and exported, and consequently the present invention is applicable for use in a data processing apparatus that handles data including right data related to handling of digital contents in an electronic device such as a portable information terminal, cellular phone apparatus and recording medium such as a memory card.

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)
EP04748090A 2003-07-25 2004-07-23 Datenverarbeitungsvorrichtung Withdrawn EP1557762A1 (de)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
JP2003280257 2003-07-25
JP2003280257 2003-07-25
JP2004085795 2004-03-23
JP2004085795 2004-03-23
PCT/JP2004/010882 WO2005010762A1 (ja) 2003-07-25 2004-07-23 データ処理装置

Publications (1)

Publication Number Publication Date
EP1557762A1 true EP1557762A1 (de) 2005-07-27

Family

ID=34082398

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04748090A Withdrawn EP1557762A1 (de) 2003-07-25 2004-07-23 Datenverarbeitungsvorrichtung

Country Status (4)

Country Link
US (1) US20050021556A1 (de)
EP (1) EP1557762A1 (de)
JP (1) JPWO2005010762A1 (de)
WO (1) WO2005010762A1 (de)

Families Citing this family (22)

* Cited by examiner, † Cited by third party
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 삼성전자주식회사 서로 다른 ｄｒｍ이 적용된 콘텐츠의 전송 및 재생 방법
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의 디지털 저작권 관리 방법 및 장치
US20070145135A1 (en) * 2005-12-28 2007-06-28 Fabrice Jogand-Coulomb Methods used in a nested memory system with near field communications capability
US20070145152A1 (en) * 2005-12-28 2007-06-28 Fabrice Jogand-Coulomb Nested memory system with near field communications capability
US20090063629A1 (en) 2006-03-06 2009-03-05 Lg Electronics Inc. Data transfer controlling method, content transfer controlling method, content processing information acquisition method and content transfer system
US8429300B2 (en) 2006-03-06 2013-04-23 Lg Electronics Inc. Data transferring method
US20090133129A1 (en) 2006-03-06 2009-05-21 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 엘지전자 주식회사 논컴플라이언트 컨텐츠 처리 방법 및 디알엠 상호 호환시스템
CN101165698B (zh) * 2006-10-17 2011-07-27 华为技术有限公司 一种导出许可的方法及系统
KR20080051971A (ko) * 2006-12-07 2008-06-11 삼성전자주식회사 휴대용 단말기에서 디지털 저작권 관리 컨텐츠 편집 방법및 장치
US8918508B2 (en) * 2007-01-05 2014-12-23 Lg Electronics Inc. Method for transferring resource and method for providing information
EP2013771B1 (de) * 2007-02-16 2013-08-21 LG Electronics Inc. Verfahren zum verwalten einer domäne unter verwendung eines multidomänen-managers und eines domänensystems
KR100923456B1 (ko) * 2007-02-23 2009-11-09 삼성전자주식회사 휴대용 단말기에서 디지털 저작권 관리 컨텐츠 관리 방법 및 장치
US8639627B2 (en) * 2007-07-06 2014-01-28 Microsoft Corporation Portable digital rights for multiple devices
CN102473231A (zh) * 2010-06-21 2012-05-23 松下电器产业株式会社 内容复制系统、管理服务器、内容使用装置、方法、程序及集成电路
KR101887426B1 (ko) * 2012-03-16 2018-08-10 삼성전자주식회사 컨텐츠 공유 시스템에서 프라이버시를 보장하기 위한 장치 및 방법
JP6701646B2 (ja) * 2015-09-02 2020-05-27 富士通株式会社 情報処理装置、情報処理システム及び情報管理方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
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 ソニー株式会社 情報処理装置および方法、ライセンスサーバ、並びにプログラム
JP2002297816A (ja) * 2001-03-29 2002-10-11 Sony Corp 情報処理装置および方法、記録媒体、並びにプログラム
JP2002297945A (ja) * 2001-03-30 2002-10-11 Nippon Telegr & Teleph Corp <Ntt> コンテンツ仲介方法及び装置、プログラム、記録媒体
JP3734461B2 (ja) * 2001-08-08 2006-01-11 松下電器産業株式会社 ライセンス情報変換装置
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

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2005010762A1 *

Also Published As

Publication number Publication date
US20050021556A1 (en) 2005-01-27
JPWO2005010762A1 (ja) 2006-09-14
WO2005010762A1 (ja) 2005-02-03

Similar Documents

Publication Publication Date Title
EP1571556A1 (de) Datenverarbeitungsvorrichtung und datenverteilungsvorrichtung
EP1557762A1 (de) Datenverarbeitungsvorrichtung
JP4768741B2 (ja) 少なくとも１つの保護されたコンテンツアイテムの使用権限を有効にする方法、装置、及びコンピュータプログラム製品
RU2357288C2 (ru) Устройство и способ поддержки обмена содержимым между доменами с отличающимися drm
EP1770540A1 (de) Datenverarbeitungseinrichtung
JP2007072639A (ja) コンテンツ管理サーバ
JP2008065696A (ja) コンテンツ共有システム及びコンテンツ共有方法
KR20090029913A (ko) 복제를 방지하기 위한 소프트웨어 설치 시스템 및 방법
JP5819203B2 (ja) 多機能装置に接続する大容量記憶装置にネットワークアクセスを可能にするシステム及び方法
KR20080074683A (ko) 디지털 저작권 관리 방법 및 장치
US20060294018A1 (en) Digital rights management
JP5009832B2 (ja) コンテンツ利用管理システム、情報処理装置、および方法、並びにプログラム
JP4901311B2 (ja) データ処理装置、データ処理方法、およびデータ処理プログラム
CN101165698B (zh) 一种导出许可的方法及系统
US20090182999A1 (en) Method And System For Security Certificate Properties For Protocol Exchange
Mendis et al. A Legal and Empirical Study into the Intellectual Property Implications of 3D Printing. Executive Summary
KR100713844B1 (ko) 디알엠 컨버터
JPWO2013132728A1 (ja) 情報処理装置、情報記憶装置、情報処理システム、および情報処理方法、並びにプログラム
JP2015049714A (ja) ソフトウェア管理装置、ソフトウェア管理システム、ソフトウェア管理方法、及びプログラム
KR101991787B1 (ko) 홈 네트워크 미디어 전송 협상
JP2009514322A (ja) 互いに異なるｄｒｍ方式を支援する端末機間にコンテンツを提供するｄｒｍゲートウェイの動作方法およびこの方法が採用されたｄｒｍゲートウェイ
KR20070104287A (ko) Ｄｒｍ 툴이 적용된 디지털 컨텐츠를 재생하는 방법 및장치
KR100784285B1 (ko) 디지털 저작권 오퍼 관리 시스템의 동작 방법 및 그 방법을채용한 디지털 저작권 오퍼 관리 시스템
WO2011012594A1 (en) Content encryption using broadcast encryption
JP2005182592A (ja) 実行ライセンス管理装置とそれを内蔵したコントローラ

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20050509

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL HR LT LV MK

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20070910