WO2004010307A1 - 情報処理装置、および情報処理方法、並びにコンピュータ・プログラム - Google Patents
情報処理装置、および情報処理方法、並びにコンピュータ・プログラム Download PDFInfo
- Publication number
- WO2004010307A1 WO2004010307A1 PCT/JP2003/008267 JP0308267W WO2004010307A1 WO 2004010307 A1 WO2004010307 A1 WO 2004010307A1 JP 0308267 W JP0308267 W JP 0308267W WO 2004010307 A1 WO2004010307 A1 WO 2004010307A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- content
- usage right
- information
- right information
- key
- Prior art date
Links
- 230000010365 information processing Effects 0.000 title claims description 59
- 238000003672 processing method Methods 0.000 title claims description 25
- 238000004590 computer program Methods 0.000 title claims description 18
- 238000007726 management method Methods 0.000 claims description 62
- 230000004044 response Effects 0.000 claims description 36
- 230000005540 biological transmission Effects 0.000 claims description 17
- 238000012795 verification Methods 0.000 claims description 13
- 238000004519 manufacturing process Methods 0.000 claims description 7
- 238000012545 processing Methods 0.000 abstract description 148
- 238000000034 method Methods 0.000 abstract description 117
- 230000008569 process Effects 0.000 description 103
- 238000009826 distribution Methods 0.000 description 42
- 238000010586 diagram Methods 0.000 description 39
- 238000003860 storage Methods 0.000 description 26
- 230000004913 activation Effects 0.000 description 19
- 230000015654 memory Effects 0.000 description 15
- 238000004891 communication Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 11
- 238000013478 data encryption standard Methods 0.000 description 5
- 238000012790 confirmation Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 125000002066 L-histidyl group Chemical group [H]N1C([H])=NC(C([H])([H])[C@](C(=O)[*])([H])N([H])[H])=C1[H] 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000002131 composite material Substances 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000010926 purge Methods 0.000 description 1
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]
- G06F21/106—Enforcing content protection by specific content processing
- G06F21/1063—Personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
-
- 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]
- G06F21/107—License processing; Key processing
-
- 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]
- G06F21/108—Transfer of content, software, digital rights or licenses
- G06F21/1082—Backup or restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2107—File encryption
Definitions
- the present invention relates to an information processing apparatus, an information processing method, and a computer program.
- an information processing device that realizes the confirmation of the right to use the content when the content is used for reproduction and the like, and realizes a flexible content use mode for the user by enabling the content preview and preview processing; and
- the present invention relates to an information processing method and a computer program.
- various software data hereinafter, referred to as “Content”
- Content such as music data, game programs, image data, etc.
- a network such as the Internet, or a memory card, HD, DVD.
- the distribution through distribution media such as CDs and the like is becoming popular.
- Distribution contents include a PC (Personal Computer) owned by the user, a recording / reproducing device, a reproduction-only device, or a storage device in a game device, for example, a card-type storage device having an HD or flash memory, a CD, a DVD, etc. And the playback process is executed.
- Information devices such as recording / reproducing devices, game devices, and PCs have an interface for receiving content from a network or an interface for accessing a memory card-HD, DVD, CD, etc. It has control means, programs and data required for playback, including RAM and ROM used as memory areas.
- Various contents such as music data, J3 ⁇ 4 image data, and programs are transmitted from a recording / reproducing device used as a reproducing device, a game device, a user instruction from an information device main body such as a PC, or via a connected input means.
- the information is called out from, for example, a built-in or detachable storage medium, and is reproduced through the information device itself or a connected display, speaker, or the like.
- Many software contents such as game programs, music data, image data, etc., generally have their distribution rights reserved by their creators and sellers. Therefore, when distributing these contents, certain usage restrictions, that is, only authorized users are allowed to use the software, and unauthorized copying is not performed, that is, security is considered.
- a configuration has been proposed in which content and usage rights for using the content are independently managed and provided to users.
- the user obtains the encrypted content, for example, and further purchases the usage right data, thereby obtaining a key for decrypting the encrypted content based on key data and the like that can be obtained from the usage right data. (Content key) and use the content.
- usage right data stores setting information of a user's content usage permission mode, and the content can be used within a range permitted by the permission information.
- the present invention has been made in view of such a situation, and allows a user to perform legitimate purchase processing of content and use legitimate content based on the usage right, and to accompany the purchase of content. It is an object of the present invention to provide an information processing apparatus, an information processing method, and a computer program that enable content previewing or previewing. It is still another object of the present invention to provide an information processing apparatus, an information processing method, and a computer program that can prevent disorderly secondary distribution of preview data and preview data. According to a first aspect of the present invention,
- An information processing device that controls decryption and use of encrypted content.
- Control means for controlling use of the content based on usage right information (usagerigtht) corresponding to the content in response to the instruction to use the content;
- the control unit permits the content to be decrypted and used based on the description content in the default usage right information.
- the control unit includes: It is characterized in that it verifies whether a flag indicating trial content is included in the content, and permits reproduction of the content based on the verification result.
- the information processing apparatus further includes: a transmission unit that transmits a registration request for a service; and a default usage right information transmitted from a license server in response to the registration request.
- Receiving means for receiving the information Further, in one embodiment of the information processing apparatus of the present invention, the receiving means further receives key information necessary for decrypting the content.
- a second aspect of the present invention is:
- An information processing apparatus comprising: Further, in one embodiment of the information processing apparatus of the present invention, the content permitted to be used based on the default usage right information is provided for a trial purpose, and the default usage right information is It is characterized in that reproduction is permitted when the content includes a flag indicating trial content. Further, a third aspect of the present invention provides
- the control step includes:
- An information processing method characterized by including: Further, in one embodiment of the information processing method of the present invention, the content permitted to be used based on the default usage right information is provided for a trial purpose, and the control step further includes: And verifying whether or not the content includes a flag indicating that the content is trial content, and permitting reproduction of the content based on a verification result. Further, in one embodiment of the information processing method of the present invention, the information processing method further includes a transmitting step of transmitting a registration request for a service, and a default usage right information transmitted from the license server in response to the registration request. Receiving the information. Further, in one embodiment of the information processing method according to the present invention, the information processing method further includes a step of receiving key information necessary for decrypting the content. Further, a fourth aspect of the present invention provides
- An information processing method comprising: Further, in one embodiment of the information processing method of the present invention, the content permitted to be used based on the default usage right information is provided for a trial purpose, and the default usage right information is If the content includes a flag indicating that the content is a trial content, It is described that the reproduction is permitted. Further, a fifth aspect of the present invention provides
- a computer that executes information processing for controlling decryption and use of the encrypted content
- the control step includes:
- the computer is characterized by comprising a 'program.
- the content permitted to be used based on the default usage right information is provided for a trial purpose
- the control step further comprises: And verifying whether the content includes a flag indicating that the content is trial content, and permitting reproduction of the content based on a verification result.
- the computer program further comprises: a transmitting step of transmitting a registration request for a service; and a default usage right information transmitted from a license server in response to the registration request. And a receiving step of receiving.
- the computer program further includes a step of receiving key information necessary for decrypting the content.
- the computer is characterized by having a program. Further, in one embodiment of the computer program of the present invention, the content permitted to be used based on the default usage right information is provided for trial purposes, and the default usage right information is: It is characterized in that reproduction is permitted when the content includes a flag indicating trial content. Further, a seventh aspect of the present invention provides
- a content usage management system having a content usage device that decrypts and uses encrypted content, and a usage right issuing device that issues a usage right that describes the usage right of the encrypted content.
- the usage right issuing device includes: Receiving means for receiving the registration request;
- a content use management system comprising: key information required for decrypting the encrypted content in response to the registration request; and transmission means for transmitting default usage right information.
- a content usage management system having a content usage device that decrypts and uses encrypted content, and usage rights (usagerules) capability S of the encrypted content, and a usage right issuing device that issues a written usage right.
- the content usage management method is characterized by having: According to the configuration of the present invention, the client acquires the default usage right information (Default Usage Right) at the time of registration processing with the license server, and obtains the default usage right at the time of the audition processing without the content purchase processing. Content playback is permitted based on the information, and the user can preview and play the content without purchasing the content. In addition, clients who are permitted to listen are registered in the license server and are limited to those who have default usage right information. This prevents random listening data. Further, according to the configuration of the present invention, even in the preview process without the content purchase process, the hardware support as the EKB corresponding to the category set corresponding to the hardware as the content use device is realized.
- the default usage right information Default Usage Right
- the computer program of the present invention is, for example, a storage medium, a communication medium, such as a CD or FD, provided in a computer-readable format to a general-purpose computer system capable of executing various program codes. It is a computer program that can be provided by a storage medium such as an MO or a communication medium such as a network. By providing such a program in a computer-readable format, processing according to the program is realized on a computer system.
- FIG. 1 is a diagram showing an outline of a content providing system to which the present invention is applied.
- Fig. 2 is a diagram showing a configuration example of a client, each server, and a management system.
- Figure 3 explains the various keys, data encryption processing, and distribution processing. 2003/008267
- FIG. 11 is a diagram illustrating a tree configuration.
- FIG. 4 shows an example of an enabling key block (EKB) used to distribute various keys and data.
- EKB enabling key block
- Figure 5 is a diagram showing an example of distribution and an example of decryption processing using a content key activation key block (EKB).
- EKB content key activation key block
- FIG. 6 is a diagram showing a format example of the activation keep lock (EKB).
- FIG. 7 is a diagram for explaining a configuration of a tag of an activation key block (EKB).
- FIG. 8 is a diagram illustrating category division in a tree configuration.
- FIG. 9 is a diagram for explaining the category division in the grid configuration.
- FIG. 10 is a diagram illustrating a specific example of category division in a tree configuration.
- FIG. 11 is a diagram showing an execution processing sequence (part 1) between entities in content purchase or preview processing.
- FIG. 12 is a flowchart showing a transaction ID generation and issue processing procedure executed in the management system.
- FIG. 13 is a diagram showing an execution processing sequence (part 2) between entities in the content purchase or preview processing.
- FIG. 14 is a flowchart showing a download permission processing procedure executed in the management system.
- FIG. 15 is a diagram illustrating an example of a data configuration of a startup file.
- FIG. 16 is a flowchart showing an application execution procedure based on a startup file executed on the client.
- Fig. 17 is a diagram showing an example of the data structure of service data and usage right information.
- FIG. 18 is a diagram showing an execution processing sequence between each entity in the content purchase processing.
- FIG. 19 is a diagram for explaining the outline of the content reproduction process.
- FIG. 20 is a diagram for explaining an example of content decryption and use processing using an activation keep-up (EKB).
- EKB activation keep-up
- FIG. 21 is a diagram showing an execution process sequence between each entity in the content preview process.
- FIG. 22 is a diagram for explaining the outline of the trial content reproduction process.
- FIG. 23 is a diagram showing a processing sequence (part 1) between each entity in the license / content backup / restore processing.
- FIG. 24 is a diagram showing a configuration example of the restorer processing request file [resstore, dat].
- FIG. 25 is a diagram showing the configuration of the MAC generation processing.
- FIG. 26 is a diagram showing a processing sequence (part 2) between the entities in the license / content backup / restore processing.
- FIG. 27 is a diagram showing a processing sequence (part 3) between the entities in the license / content backup / restore processing.
- FIG. 28 is a diagram depicting a processing flow for generating a recommendation file
- FIG. 29 is a diagram showing a recommendation file generation screen.
- FIG. 30 is 1 which shows an example of a recommendation file configuration.
- FIG. 31 is a diagram illustrating a configuration example of a content file stored in a recommendation file.
- FIG. 32 is a diagram illustrating a display example of a content description file stored in a recommendation file.
- FIG. 33 is a diagram showing a license information acquisition processing flow (part 1) in the client receiving the recommendation file.
- FIG. 34 is a diagram showing a license information acquisition processing flow (part 2) in the client that has received the recommendation file.
- BEST MODE FOR CARRYING OUT THE INVENTION the configuration of the present invention will be described in detail. The explanation will be given in accordance with the following items.
- FIG. 1 is a diagram illustrating an outline of a content providing system to which the present invention is applied.
- the client 10 that uses the content is an information processing apparatus as a device that can use, that is, reproduce, the content.
- various information processing apparatuses such as a PC and a PDA are included.
- the client 10 has a browser 11 and a client application 12 as software, and the browser 11 and the client application 12 and other programs are executed by control means such as a CPU.
- Client 1 and application 12 are clients that purchase and listen to the content, process the service data described later, acquire license information including content usage right information, and backup the content and license information.
- the term “preview” is used to mean not only the preview of audio data but also the preview of image data.
- the client 10 is connected to a shop server 21, a license server 22, and a content server 23 via a communication network such as the Internet.
- the content server 23 provides the content to the client 10.
- the license server 22 provides the use right information of the content used by the client to the client 10.
- the shop server 21 functions as a contact point when the client 10 purchases the content, presents the content that can be purchased or auditioned through a browser, and accepts a request for purchase or audition from the client. In addition, charging processing for purchased contents is performed as necessary.
- a management system 31 is connected to the shop server 21 and the license server 22.
- the management system 31 issues a transaction ID (TID) that functions as permission information for the content request from the client 10 received by the shop server 21 and issues content download permission information.
- TID transaction ID
- the management system 31 also permits the license server 22 to issue usage right data (Usage Right) as content usage right information. The details of these processes will be described later.
- the client 10 executes the acquisition of the usage right from the license server 22 and the acquisition of the content from the content server 23 under the control of the client application 12, and provides the shop server 21.
- Information browsing and settlement processing are executed by launching the browser 11 under the control of the client application 12.
- FIG. 1 shows one client and one server at a time. Many of these are connected on a communication network such as the Internet, and clients connect to various shop servers. Freely select the content provided by each shop server, acquire the content from the content server that stores the selected content, select the license server that issues the right to use the acquired content, and select the selected license server. Acquire the usage right from the license server.
- the content is provided from the content server 23 to the client 10 as encrypted content.
- the license server 22 provides the client 10 with content usage right information corresponding to the content, and the client application 12 of the client 10 verifies the usage right information and determines that the usage right is available. If determined, the encrypted content is decrypted and used.
- the client 10 uses the enabling key block (EKB: Enabling Key Block) and the device 'node' key (DNK: Device Node Key) as key information to enable the use of content based on the content usage right. And other key data.
- the enabling key block (EKB) and the device 'node' key (DNK: Device Node Key) decrypt the encrypted content only when the user device has the right to use the content. This is the key data for obtaining the encryption key required for using the content to make it usable.
- the content server 23 encrypts the content and provides the encrypted content to the client 10. Further, the license server 22 generates usage right information (Usage Right) based on the content usage conditions and provides the generated usage right information to the user device 30.
- the management system 3 1 It generates service data based on the device node key (DNK: Device Node Key) and the enabling key block (EKB: Enabling Key Block) provided by the client and provides it to the client 10.
- the service data includes the services required for decryption processing of the encrypted content. ⁇ Enabling key block (EKB) with device node key (SDNK).
- the conditions for using the contents include the conditions for limiting the use period, the number of copies, and the number of portable media (PM: Portable Media) that can simultaneously use the contents (so-called check-out). ) (Depending on the number).
- Portable media (PM) is a storage medium that can be used in portable devices such as flash memory or small HD, optical disk, magneto-optical disk, and MD (Mini Disk).
- the CPU Central Processing Unit
- ROM Read Only Memory
- RAM Random Access Memory
- a ROM (Read Only Memory) 102 stores programs used by the CPU 101, calculation parameters, fixed data, and the like.
- RAM (Random Access Memory) 103 is a program used in the execution of CPU 101. Gram and parameters that change as appropriate during execution. These elements are interconnected by a bus 111 composed of a CPU bus and the like.
- the encryption / decryption unit 104 performs content encryption / decryption processing, device node key (DNK: Device Node Key), and enabling key block (EKB: Enabling Key Block) application processing such as DES (Data Encryption Standard). Performs encryption processing, MAC generation, verification processing, etc., to which the encryption algorithm is applied.
- DNS Device Node Key
- EKB Enabling Key Block
- the codec unit 105 executes data encoding processing and decoding processing of various systems such as, for example, ATRAC (Adaptive Transform Acoustic Coding) 3 system, MPEG, and JPEG system.
- Data to be processed is input from the removable storage medium 121 via the bus 111, the input / output interface 112, the drive 110, or via the communication unit 109.
- the processed data is stored in the removable storage medium 121 or output via the communication unit 109 as necessary.
- the input / output interface 112 includes an input unit 106 such as a keyboard and a mouse, a display unit such as a CRT and LCD, an output unit 107 including speakers, a storage unit 108 such as a hard disk, a modem, and a terminal adapter.
- a communication unit 109 constituted by the above is connected to perform data transmission / reception via a communication network such as the Internet.
- a broadcast encryp- tion to make the content available only to the client who has the right to use the content.
- a description will be given of a device and key management configuration based on a tree configuration, which is one mode of the (Broadcast Encryption) system.
- Namers 0 to 15 shown at the bottom of FIG. 3 are user devices as clients who use the content.
- each leaf of the hierarchical tree structure shown in FIG. 3 corresponds to a device.
- Each device 0 to 15 has a key (node key) assigned to a node from its own leaf to the root in the hierarchical tree structure shown in Fig. 3 at the time of manufacture, shipment, or thereafter.
- K 0000 0 to K 1 11 1 1 shown at the bottom of FIG. 3 are the relief keys assigned to the respective devices 0 to 15, and the second from the bottom KR (root key).
- Keys described in section (nodes): KR to K 1 1 1 are the node keys.
- device 0 owns a leaf key K00000 and node keys: K000, K00, K0, and KR.
- Device 5 owns K0101, K010, KOI, K0, and KR.
- Device 15 owns 1 1 1 1, 111 1 1, 1 1, 1 ⁇ 1, KR.
- FIG. 1 device node key
- each device included in the structure of FIG. 3 includes various types of recording media, for example, various types using devices such as DVDs, CDs, MDs, and flash memories that are embedded in a device or detachably attached to the device. Devices are included.
- various application services It is possible. On such a coexistence configuration of different devices and different applications, the hierarchical tree structure that is the content or key distribution configuration shown in Fig. 3 is applied.
- a portion surrounded by a dotted line in FIG. 3, that is, devices 0, 1, 2, and 3 are set as one group using the same recording medium.
- the common content is collectively encrypted and sent from the provider, the content key used commonly for each device is sent, or each device is sent. Then, the process of encrypting and outputting the payment data of the content fee to the provider or the payment machine is executed.
- Institutions that transmit and receive data to and from each device such as content servers, license servers, or shop servers, collectively store the data enclosed by the dotted line in Fig. 3, that is, devices 0, 1, 2, and 3 as one gnole.
- An organization that sends and receives data to and from each device functions as a means for delivering message data.
- the node key and leaf key may be managed collectively by a single management system having a key management center function, or a message data distribution means such as a provider or settlement institution that performs various data transmission / reception to / from each group. May be managed for each group.
- These node keys and leaf keys are updated in the event of, for example, a key leak, and this updating process is executed by a management system having a key management center function, a provider, a payment institution, or the like.
- one group The three devices 0, 1, 2, and 3 included in a device node key (DNK: Device Node Key) including a common key K 00, K 0, and KR as a device node key (DN K: Device Node Key) Hold.
- DNK Device Node Key
- the commonly owned node key K 00 is the owned key common to devices 0, 1, 2, and 3.
- the value Enc (K00, Knew) obtained by encrypting the new key Knew with the node key K00 is stored in the device 0, 1, 2, 3 via the network or in a recording medium.
- Enc (K 00, Kn ew) indicates that K b is data encrypted by K a.
- K0 0 1 1 From then on, device 3 must be disconnected from the system to protect the data sent and received by the system (group of devices 0, 1, 2, 3).
- K (t) aaa indicates that the generation of the key Kaaa is an update key of t.
- the update key distribution process will be described.
- the key is updated, for example, by storing a table composed of block data called an enabling key block (EKB: Enabling Key Block) shown in FIG. , 1, 2.
- the activation keep lock (EKB) is shown in Fig. 3.
- the Activation Key Block (EKB) is sometimes called the Key Renewal Block (KRB).
- the activation key block (EKB) shown in Fig. 4 (A) is configured as block data with a data structure that allows only devices that require node key updates to be updated.
- the example in Fig. 4 is block data formed for the purpose of distributing an updated node key of generation t in devices 0, 1, and 2 in the tree structure shown in Fig. 3.
- device 0 and device 1 need K (t) 00, K (t) 0 and K (t) R as update node keys, and device 2 as update node key.
- K (t) 001, K (t) 00, K (t) 0, and K (t) R are required.
- the EKB in Fig. 4 (A) contains multiple encryption keys.
- the encryption key at the bottom is Enc (K 0 0 10, K (t) 00 1).
- This is the updated node key K (t) 0 0 1, which is encrypted by the leaf key K 0 0 10 of device 2 .
- Device 2 decrypts this encryption key with its own leaf key, and K (t ) 0 0 1 can be obtained.
- ⁇ 00001 is the third encryption key from the top in Fig. 4 (A).
- E nc (K 0 0 0, K (t) 0 0) is decrypted to obtain K (t) 0 0, and then the second encryption key E nc (K (t) 0 0, ⁇ (t) 0), and the updated node key K (t) 0, the first encryption key Enc (K (t) 0, K (t) R) to obtain K (t) R.
- devices 0, 1, and 2 can obtain the updated key K (t) R.
- the index in Fig. 4 (A) indicates the absolute address of the node key and leaf key used as the decryption key. If the node keys at the upper stage of the ll structure shown in Fig.
- Fig. 4 By using the activation keep key (EKB) of (B), the updated node key K (t) 00 can be distributed to devices 0, 1, and 2.
- the EKB shown in Fig. 4 (B) can be used, for example, when distributing a new content key shared by a specific group. As a specific example, assume that devices 0, 1, 2, and 3 in the group indicated by the dotted line in FIG. 3 use a recording medium and a new common content key K (t) con is required.
- FIG. 5 as an example of processing for obtaining a key at time t, for example, a content key K (t) con applied to content encryption / decryption, a new common content key K ( An example of processing of device 0, which has received data Enc ((t) 00, K (t) con) obtained by encrypting t) con and EKB shown in FIG. 4B via a recording medium, is shown. That is, this is an example in which the encrypted message data by the EK B is used as the content key K (t) con.
- the device 0 performs the same EKB processing as described above using the generation KB stored at the time t and the node key K 000 stored in advance. Generate the node key K (t) 00.
- the updated content key K (t) con is decrypted by using the decrypted updated node key K (t) 00, and is encrypted and stored by the leaf key K00000 which only oneself has for later use. .
- FIG. 6 shows an example of the format of the activation key block (EKB).
- Version 201 is an identifier that indicates the version of the activation keep mouth (EKB).
- the version has the function of identifying the latest EKB and the function of indicating the correspondence between contents.
- Depth indicates the number of layers in the hierarchical tree for the device to which the activation keep-up packet (EKB) is distributed.
- the data pointer 203 is a pointer indicating the position of the data part in the enabling key block (EKB)
- the tag pointer 204 is the position of the tag part
- the signature pointer 205 is a pointer indicating the position of the signature.
- the data section 206 stores, for example, data obtained by encrypting a node key to be updated.
- each key related to the updated node key as shown in FIG. It stores an encryption key and the like.
- the tag part 2007 is a tag indicating the positional relationship between the encrypted node key and the leaf key stored in the data part.
- This tag assignment / rail will be described with reference to FIG. Fig. 7 shows an example in which the enabling key block (EKB) described in Fig. 4 (A) is sent as data.
- the data at this time is as shown in Table (b) of FIG.
- the top node address included in the encryption key at this time is set as the top node address. In this case, the top node address is KR because the root key update key K (t) R is included.
- the data Enc ((t) 0, K (t) R) at the top is at the position shown in the hierarchical tree shown in (a) of FIG.
- the next data is E nc (K (t) 0 0, K (t) 0), which is at the lower left position of the previous data on the tree.
- the tag is set to 0; otherwise, 1 is set.
- Tags are set as ⁇ left (L) tag, right (R) tag ⁇ . Since there is data to the left of the data Enc (K (t) 0, K (t) R) at the top, the L tag is 0, and there is no data to the right, so the R tag is 1.
- tags are set for all data, and the data strings and tag strings shown in Fig. 7 (c) are configured.
- the tag is set to indicate where the data Enc (KXXX, Kyy) is located in the tree structure. Since the key data Enc (KXXX, Kyyy) ... stored in the data section is simply a series of encrypted keys, the key data of the encryption key stored as data by the tag described above is used. This makes it possible to determine the position on the top. Without using the tag described above, using a node index corresponding to the encrypted data as in the configuration described in FIG.
- the signature 208 is an electronic signature executed by, for example, a management system having a key management center function, a content server, a license server, or a shop server that issues an activation keep lock (EKB).
- the device that has received the EKB verifies the signature by verifying that it has a valid activation keep lock (EKB) issued by the issuer.
- FIG. 8 shows an example of the classification of categories with a hierarchical structure.
- a root key K root 301 is set at the top of the hierarchical structure
- a node key 302 is set at the following middle
- a leaf key 303 is set at the bottom. Is set.
- Each device has an individual leaf key and a series of node and root keys from the leaf key to the root key.
- a node having the M-th stage from the top is set as a category node 304.
- each of the nodes in the M-th stage is a device setting node of a specific category.
- the node and leaf below the M + 1st stage are defined as one node in the Mth stage. Nodes and leaves related to chairs.
- the category [MemoryStick (trademark)] is set, and the nodes connected to this node and below include various devices using the memory stick. It is set as a category-specific node or leaf. That is, the nodes 305 and below are defined as a set of related nodes and leaves of the device defined in the memory stick category.
- a stage several stages lower than the M stage can be set as the subcategory node 306.
- the node below the category [Memory Stick] node 3 05 is a sub-category node included in the category of devices using Memory Stick.
- a sub-category node a playback-only device, which is included in the playback-only device category, is set to a node below the node, and a node with a music playback function is included in the playback-only device category.
- [PHS] node 308 and [mobile phone] node 309 included in the telephone category can be set.
- the category and subcategory are not only device types, but also arbitrary units (for example, processing units, jurisdictional units, or provided service units) that are managed independently by a certain manufacturer, content provider, or payment institution. These are collectively referred to as entities below). For example, if one category node is set as a dedicated vertex node for a game device XYZ sold by a game device manufacturer, the game device sold by the manufacturer XYz stores the lower node key and leaf key below the vertex node for sale After that, the distribution of encrypted content, or the distribution and update of various keys, is made up of node keys and leaf keys below the top node key. 7
- Key block is generated and distributed, and usable data can be distributed only to devices below the top node.
- one vertex of the category stage or subcategory stage is set.
- a manufacturer or content provider that manages a node to independently generate an activation key block (EKB) with that node as the vertex and distribute it to devices belonging to the vertex node and below.
- Key update can be performed without affecting devices belonging to other categories of nodes that do not belong to.
- FIG. 9 key management is performed in a tree-structured system. In the example of FIG.
- the nodes in the 8 + 24 + 32 stage have a clear structure, and the category corresponds to each node from the root node to the lower 8 stages.
- the category here means a category such as a category of a device using a semiconductor memory such as a memory stick and a category of a device receiving digital broadcasting.
- This system (referred to as T system) corresponds to one of the category nodes as a system for managing licenses. That is, the keys corresponding to the nodes in the lower 24 levels of the T system node are applied to the service provider or the service provided by the service provider. In this example, thereby, a 2 2 4 (about 1 6 mega) service providers or services can and defining child.
- the lowest 32 levels can define 2 32 (approximately 4 giga) users (or user devices).
- the keys corresponding to each node on the path from the bottom 32 nodes to the T system node constitute a DNK (Device Node Key), and the bottom PT / JP2003 / 008267
- the ID corresponding to 28f is the leaf ID.
- the content key that encrypted the content is encrypted with the updated root key KR ', and the upper-level updated node key is encrypted using its immediately lower-level updated node key, and the Deployed.
- the update node key one level up from the end of the EKB is encrypted with the node key or leaf key at the end of the EKB and placed in the EKB.
- the user device uses one of the DNK keys described in the service data to decrypt and decode the updated node key of the immediately higher hierarchy described in the EKB distributed with the content data. Using the key obtained in this way, it decrypts the updated node key in the layer above it described in the EKB.
- the user device can obtain the updated root key KR '.
- the tree categorization allows a configuration in which one node is defined as a vertex and the following nodes are set as related nodes of the category or sub-category defined at the vertex node.
- a configuration is realized in which a manufacturer or service provider that manages one vertex node in the subcategory stage independently generates an activation key block (EKB) having that node as a vertex and distributes it to devices belonging to the vertex node and below.
- EKB activation key block
- the T system node 351 is set below the root node 350, and the T service node 352 and the T hard node 353 are set below that.
- the tree with the T-hard node 355 as the top is a category tree that sets the user device itself as a leaf 355 and distributes a hard-compliant EKB [EKB (H)] issued for the device.
- the tree with the T service node 352 at the top is a category tree that distributes a service-compatible EKB [EKB (S)] issued in response to services provided to user device devices.
- EKB (S) service-compatible EKB
- Both the hardware-compatible EKB [EKB (H)] and the service-compatible EKB [EKB (S)] have DNKs (Device Node Keys) assigned to devices that have the proper authority.
- DNKs Device Node Keys
- FIG. 11 shows the initial stage of the communication sequence in the content purchase process executed between a client such as a PC having a client application and a browser and a shop server, a content server, a license server, and a management system. Steps are shown. Hereinafter, the processing shown in the sequence diagram will be described.
- a user who wishes to purchase content designates URL as a communicable information processing device such as his / her PC (step (1)), and presents the shop server via a browser.
- the client selects the content from the content list presented by the shop server, specifies purchase or audition (step (4)), and sends the request data to the shop server via the browser.
- the request data includes the content ID (CID), shop server identifier (Shop ID), and data to specify whether to purchase or listen.
- the shop server requests the management system to determine whether the content can be provided (step (6)).
- This determination request includes the content ID (CID) and the shop server identifier (Shop ID).
- the management system executes a transaction ID (TID) issuance process (step (7)).
- the details of the transaction ID (TID) issuance processing will be described with reference to the flowchart of FIG.
- step S101 the management system generates a random number, and generates a transaction ID (TID) based on the generated random number.
- step S102 the generated transaction ID (TID) and the content ID (CID) specified by the shop server are stored in the storage unit as transaction data in association with each other.
- the generated transaction ID (TID) is output and issued to the shop server.
- the management system After generating the transaction ID (TID), the management system sends the generated transaction ID (TID) and price information to the shop server as TID information (step (8)). You. However, price information is required only when content is purchased, and is not included in content preview processing.
- the shop server that has received the TID information executes the charging process (step (9)) based on the price included in the TID information when the request from the client is to purchase the content. If the request from the client is not a content purchase but a content preview request, this accounting process (step (9)) is omitted.
- the shop server downloads the content for which a purchase or a preview request has been made, on condition that billing has been executed, and in the content preview process, on condition that TID information has been received from the management system.
- the permission request is sent to the management system (step (10)).
- the management system executes a download permission request verification process (step (11)). The details of the download permission request verification process will be described with reference to the flow in FIG. First, in step S201, the management system compares the transaction ID (TID) included in the received download permission request with the transaction ID (TID) generated earlier and stored in the storage unit.
- step S202 a content ID (CID) recorded corresponding to the verified transaction ID (TID) is obtained, and in step S203, a download permission for the content corresponding to the CID is issued. I do.
- Management system Dow After the download permission request verification process (step (11)), a download permission for the content is issued to the shop server (step (12)).
- the download permission includes transaction ID (TID), content server URL (C—URL), license server URL (L—URL), content ID (CID), usage right information ID (UID), UR L (S—UR L), which includes the service ID.
- the shop server When the shop server receives the download permission from the management system, it generates a startup file for starting the use of the content in the client application (playback processing, etc.) and sends it to the client application via the client browser. You. An example of a startup file will be described with reference to FIG.
- the startup file 360 contains the transaction ID (TID) previously generated by the management system, the content ID (CID) purchased or audited by the client, and the usage right information ID (CID) included in the download permission information generated by the management system. UID), the service ID included in the download permission information generated by the management system, the license server URL, the product (content) URL, and identification data indicating whether the processing is purchase or trial listening.
- TID transaction ID
- CID content ID
- CID usage right information ID
- UID the service ID included in the download permission information generated by the management system
- the license server URL the license server URL
- the product (content) URL and identification data indicating whether the processing is purchase or trial listening.
- the extension set in the startup file is set according to whether it is purchase or audition, and this is determined by the client application.
- Each application may be started.
- the client application starts the application according to the start file (step (15)).
- the application startup process executed in the client application will be described with reference to FIG.
- step S301 first, it is determined whether or not service data corresponding to the service ID set in the startup file is stored in the information processing device as a client system.
- the service data is received from the license server when the client wants to receive various services, for example, the content use service. For example, it is data that recognizes the collective right to use the services provided by a specific service provider.
- Figure 17 (a) shows an example of the data structure of service data.
- the service data 370 contains a leaf ID unique to the client, a service ID as a service identifier, and a device node key (DNK) that are set in the EKB distribution zone. Contains data encrypted with key (K root), E (K root, DN K).
- the registration processing corresponds to the processing of the processing steps (15) and (16) shown in FIG. If it is determined in step S301 shown in FIG. 16 that the service data corresponding to the service ID is not held, a registration process is executed in step S302 to receive the service data. In addition, during the registration process, the default usage right information is issued from the license server to the client.
- the usage right information normally stores the usage conditions of the purchased content and is issued in response to the purchase of the content, whereas the default usage right information is not issued on the condition that the content is purchased. No client registration process or service Issued on condition that the data is issued. This default usage right information is applied as valid content usage right information in the content preview process described later.
- Figure 17 (b) shows an example of the data structure of the usage right information.
- the usage right information 37 1 contains the usage right information ID as the usage right information identifier, the time stamp as the issue date and time information, the leaf ID unique to the client, and the content correspondence. In the case of, the content ID and the usage condition target content type information are stored.
- the content ID is omitted or a common ID is set for content that can be previewed.
- the setting is made such that the use of the content for which the audition flag is set to ON (ON) is permitted.
- the content 3 72 has a preview flag 3 73 set, and if the preview flag 3 73 is set to ON, the content permitted to be previewed is set. If the preview content is set to OFF (OFF), it indicates that the content is not permitted to be previewed.
- step S302 registration processing, that is, acquisition of service data and default usage right information from the license server is completed.
- step S303 it is determined whether the startup file received from the shop server is a startup file for a purchase application or a startup file for a preview application. If it is the start file of the application for purchase, proceed to step S304 to execute the application for purchase, and if it is the start file of the application for preview, proceed to step S305 to execute the application for preview. .
- step S305 the execution sequence of the purchase application will be described with reference to the sequence diagram in FIG.
- the client application executes a content download request to the content server (step (2 1)).
- This is the content for which the client has previously made a purchase request, and is the content corresponding to the content ID (CID) recorded in the usage right information (see Fig. 17 (b)).
- the client application specifies the content by the content ID (CID) and executes a content download request to the content server.
- CID content ID
- This content information includes encrypted content, and as shown in FIG. 17 (c), content data encrypted with the content key: Kc: Enc (Kc, Content), content key: Kc Root key: Data encrypted with K root: Enc (K root, K c), and further: Root key: EKB for acquiring K root, audition flag data, service ID, and other information are added.
- File. Upon receiving the content information, the client responds to the received content.
- a request to acquire the usage right information (Usage Right) is transmitted to the license server (step (23)).
- This request includes the usage rights information ID (UID) contained in the boot file (see Fig. 15) previously received from the shop server, the leaf ID as client identification data, and the request from the shop server.
- UID usage rights information ID
- the license server When the license server receives the request for obtaining the usage right information (Usage Right), it performs an order inquiry process (step (24)) to the management system.
- This request includes a usage rights information ID (UID) and a transaction ID (TID).
- the management server that has received the order inquiry transmits response information in which the usage conditions corresponding to the usage right information ID (UID) are set to the license server as an order inquiry response (step (25)).
- the license server Upon receiving the response information, the license server generates usage right information (Usage Right) in which content usage conditions are set, and issues it to the client (step (26)).
- the content use conditions are composed of the number of times the content has been played, the time limit, and permission information for various processes such as copying to external devices and checkout processes.
- the client that receives the usage right information (Usage Right) can use the content received earlier from the content server based on the usage conditions recorded in the usage right information (Usage Right). It becomes.
- a user issues a content playback request (step (27)) specifying a content ID (CID) and usage right information (Usage Right) ID
- the client application performs content playback according to the usage conditions. Execute (Step (2 8)).
- the basic content playback procedure is explained with reference to Figure 19 I do.
- the content is provided from the content server 382 to the client 383, and the service data and the usage right information are provided as licenses from the license server 381 to the client 383.
- (Usage Right) is given.
- the content is encrypted by a content key: K c (E nc (K c, Content)), and the content key K c is a key obtained from a root key K root obtainable from the E KB
- the client 3 8 3 obtains a device node key (DNK) from the service data received from the license server, decrypts the content key EKB based on the obtained DNK, and obtains a root key: K root.
- DNK device node key
- Fig. 20 is a diagram illustrating a content use processing sequence based on decryption processing of content to which EKB [EKB (H)] for hardware and EKB [EKB (S)] for service are applied.
- the service data 401 and the usage right information 400 shown in 20 are data to be received from the license server, and the encrypted content file 402 is data to be received from the content server.
- 401 is the leaf ID as a leaf identifier, the purge of the applicable EKB, and the services required to decrypt the service-enabled EKB [EKB (S)]. It stores the data E (K root ', SDNK) that is encrypted by the root key K root' that is set to the device node key (S DNK) corresponding to the hardware-compatible category tree.
- the encrypted content file 402 is a service-compatible EKB [EKB (S)] that stores a root key K root that is set corresponding to the service-compatible category tree, a content ID (CID) with the root key K root, Data E (root, CID + Kc), which is encrypted with a content key (Kc) applied to content encryption and decryption processing, and ⁇ , content (Content) are encrypted with a content key Kc It is a Faigle containing data E (K c, Contet).
- the usage right information 403 is data that stores leaf IDs and content usage condition information.
- the content usage condition information includes various usage conditions such as a usage period, the number of times of use, and copy restrictions set for the content.
- the user device that has received the usage right information 4003 stores the usage right information as security information corresponding to the content, or stores it in an AV index file as index data of the content.
- the usage right information can be stored as security information corresponding to the content. It is preferable to store the information and perform processing referring to all usage right information when using the content.
- the usage right information 403 including the selected information is indexed into the content.
- step S501 shown in FIG. 20 the user device applies the hardware-compatible device node key (HDNK) 412 to execute the hardware-compatible EKB (H) 411 decryption process.
- EKB (H) 4 1 1 Get the root key K root 'that is set corresponding to the hardware category.
- the processing of EKB to which DNK is applied follows the method described above with reference to FIG.
- step S502 using the root key K root 'extracted from E KB (H), the decryption processing of the encrypted data E (K root, S DNK) in the service data 401 is performed.
- step S503 using the device node key (S DNK) extracted from the service data, the service-compatible EKB [EKB (S)] stored in the encrypted content file 402 is used. Executes the process (decryption) and obtains the root key K root set for the service-compatible category tree stored in the service-compatible EKB [EKB (S)].
- step S504 using the root key K root extracted from the service-compatible EKB [EKB (S)], the encrypted data E (K Root, CID + K c) is decrypted and the content ID (CID) and content key (K c) are obtained.
- step S505 the encrypted content file 402 Executes the matching (collation) process of the content ID (CID) extracted from the URL and the content ID stored in the usage right information.
- step S506 the content key (Kc) extracted from the encrypted content file 402 is applied to encrypt the content.
- the encrypted content E (Kc, Content) stored in the content file 402 is decrypted to reproduce the content.
- EKB hardware-compatible EKB [EKB (H)] as an EKB corresponding to the category tree set corresponding to the hardware as the content usage device
- the legitimate HD NK Only the user device having the can acquire the SD NK and use the service.
- the matching process is performed between the content identifier (CID) obtained from the encrypted content file 402 and the CID obtained from the usage right information. Acquisition of the CID information and storing of the CID information can be required for the content playback process. Use is realized.
- the processing in the case where the processing of the client application is an application for executing the preview processing will be described with reference to the sequence diagram of FIG. In the case of the trial listening process, the content information file (see Fig.
- the client application executes a content download request to the content server (step (31)). This is the content for which the client has previously requested a preview.
- the client application specifies the content by the content ID (CID) and executes a content download request to the content server.
- the content server transmits partial data (content part) of the content to the client one after another (step (32)).
- the client that has received the content template executes a reproduction process for the received content (step (33)), and sends a subsequent content part request to the content server. Streaming reproduction is performed by continuously executing this processing.
- the procedure of the preview playback process will be described with reference to the flow of FIG.
- the client application determines the service ID from the preview content file received from the content server. To get.
- step S702 it is determined whether there is default usage right information (Default Usage Right) (see FIG. 17 (b)) corresponding to the extracted service ID.
- the default usage right information is the usage right information transmitted from the license server together with the service data (see Fig. 17 (a)) during the client registration process, and is used in response to the purchased content.
- step S705 the default usage right information used for content that can be listened to.
- the default usage right information (Defau 1 t Usage Right) is a condition for permitting the execution of the audition. If the default usage right information is not held, proceed to step S705. However, the content reproduction is not executed as an error, and the process ends.
- step S703 the default usage right information is verified and the record of the usage right information is confirmed.
- the default usage right information stores, for example, the permission to listen to the content with the audition flag on or the content ID information that allows audition, and acquires such information.
- step S704 the content is played back based on the usage conditions of the default usage right information (Default Usage Right). As described with reference to FIGS.
- the reproduction process is a reproduction process including a process of decrypting the encrypted content received from the content server.
- the listening process that does not involve the content purchase process is also based on the EKB process, similar to the playback of the purchased content described with reference to FIG. It is necessary to obtain a key for content decryption by key acquisition processing.
- a hardware compatible EKB [EKB (H)] as an EKB corresponding to a category tree set corresponding to hardware as a content using device, and a category tree set corresponding to a content using service.
- Service configuration as an EKB that supports EKB [E KB (S)] can be configured so that only users with a legitimate DNK can execute content playback. It becomes possible.
- the client obtains the default usage right information (Defau 1 t UsageRight) at the time of registration processing with the license server, and defaults at the time of audition processing without the content purchase processing. Since the content can be played back based on the usage right information, the user can preview and play the content without purchasing the content. Since registration processing to the sense server is performed and only the clients having the default usage right information are limited, it is possible to prevent the trial data from being randomly distributed.
- the sequence diagram in Fig. 21 shows an example of streaming playback. However, the trial listening data is stored in the storage medium of the client, and the presence or absence of the default usage right information (Default Usage Right) is determined during playback. Then, it is also possible to adopt a configuration in which reproduction is performed based on the recording of the default usage right information.
- the restore process is the content-related license information that is executed when the client purchases the content or as a post-purchase process, that is, as service data and usage right information re-acquisition, storage processing, or content re-acquisition processing. Be executed.
- As a processing mode it is possible to reacquire any one of the service data, the usage right information, and the content, or reacquire all the data.
- an example of a service data, usage right information, re-acquisition of all content data, and a storage processing sequence will be described. However, the present invention is not limited to such a process of re-acquiring all data.
- FIGS. Figure 23 shows the initial stage of the communication sequence in the backup restorer process executed between the client application, a client such as a PC having a browser, and the shop server, content server, license server, and management system. Steps are shown. The processing shown in the sequence diagram will be described below. It is assumed that the client has made a formal content purchase in accordance with the content purchase processing described above. The sequence shown in FIG. 23 is a sequence that is executed following the content purchase. The client that has executed the content purchase processing generates a restore processing request file [restore, dat] as a data file for obtaining backup / restore data (step (50)).
- Figure 24 shows the configuration of the restore processing request file [restore, dat].
- the restore processing request file [restore.dat] is composed of a leaf ID as client identification data in the EKB distribution tree, a hash (hash) key, and a MAC (Message) Authentication Code) Consists of the verification data.
- the client application calculates a hash value or MAC as verification data based on the leaf ID by applying a secret key shared with the management system, and obtains a restore processing request file including the leaf ID and the verification data. restore, dat ".
- a message authentication code (MAC) is generated as data for falsification verification of data.
- Figure 25 shows an example of MAC value generation using the DES encryption processing configuration. As shown in the configuration of Fig.
- the target message is divided into 8-byte units (hereinafter, the divided messages are referred to as M1, ⁇ 2, ⁇ , ⁇ ), and the initial value ( Exclusive OR of Initial Value (hereinafter, referred to as IV)) and Ml (the result is referred to as I1).
- M1, ⁇ 2, ⁇ , ⁇ the initial value
- IV Exclusive OR of Initial Value
- Ml the result is referred to as I1
- E1 and E 1 are XORed
- the output I 2 is input to the DES encryption unit, and encrypted using the key K 1 (output E 2). Thereafter, this process is repeated, and all messages are subjected to encryption processing.
- the last EN that appears is the message authentication code (MAC).
- the client accesses the restorer page provided by the management system via a browser (step (51)), and the management system presents the restore page to the client browser (step (52)).
- the restore page presented by the management system is a page that has a function to execute upload processing of the restore processing request file [restore, dat].
- the client uploads the restore processing request file [restore, dat] generated by the client application on the restorer page presented by the management system.
- the restore processing request file [restore, dat] contains the leaf ID as the client identification data in the EKB distribution tree and the fiMA C (Message Authentication Code) , Consisting of a hash value.
- the management system Upon receiving the restore processing request file [restore.dat], the management system calculates a hash value for the leaf ID using the secret key shared with the client, and performs a comparison process between the calculated hash value and the received hash value. Then, the received data is verified (step (54)).
- a backup / restore startup file is transmitted to the client (step (55)), provided that the calculated hash value and the received hash value match.
- the configuration of the startup file has the same file configuration as described above with reference to FIG.
- the startup file is passed from the browser to the client application (step (5)), starts the backup restore execution program that is selected and determined by the description of the startup file, or the extension, and executes the restore process (step (5)). (57)).
- the processing target of the backup / restore processing includes service data, content, and content usage right information.
- Service data is described above As described above, it can be obtained by the registration process with the license server, and the content can be obtained from the content server.
- the usage right information is obtained from the license server. In backup Z restorer processing, each of these data will be obtained from each server.
- the client application sends a registration request to the license server (step (61)).
- This registration request includes the transaction ID (TID) contained in the startup file generated by the management system.
- the license server identifies the acquisition of backup / restore service data based on the transaction ID (TID), and provides service management data, that is, backup of service data, to the management system.
- a request is made (step (62)) for allocating the / restor data.
- the management system verifies, based on the management data, whether or not there is a client terminal that has executed processing based on the same transaction ID, and if so, stores them in association with each other (Step (63)). ) This is to set an upper limit (for example, three) for the number of knock-up / restore processes, and to enable the setting not to execute the process if the processing request exceeds the upper limit.
- the management system that has executed the management data update process transmits a service pre-data allocation response to the license server (step (64)). This is sent as issuance permission information for the backup Z restorer service data. It is believed.
- the license server that has received the service pre-data allocation response executes the process of issuing backup / restore service data to the client (step (65)).
- the service data includes, as the service data 370, a leaf ID unique to the client set in the EKB delivery library and a service identifier. It includes the service ID, and data (E (K root, DNK)) obtained by encrypting the device node key (DNK) with the root key (K root).
- E (K root, DNK) data obtained by encrypting the device node key (DNK) with the root key (K root).
- the default usage right information (see Figure 17 (b)) is also issued from the license server to the client.
- the usage right information normally stores the usage conditions of the purchased content and is issued in response to the purchase of the content. It is not issued as a condition, but is issued on condition that client registration processing or service data issuance processing is performed.
- This default usage right information is applied as effective usage right information at the time of content preview processing as described above.
- the client having received the service data and the default usage right information from the license server, stores these data in a storage means for backup (step (66)).
- a description will be given of the content backup no-restoration process.
- the client application executes a content download request to the content server (step (71)). This is the same content that the client purchased earlier.
- Client app The location specifies the content by the content ID (CID) and executes a content download request to the content server.
- the content server Upon receiving the content download request, the content server transmits the content information corresponding to the CID to the client (step (72)).
- This content information is information including the encrypted content.
- the content key the content data decoded by Kc: Enc (Kc, Content)
- the content key: Kc is routed
- Key Data encrypted with K root: Enc (K root, K c)
- Norret key File containing EKB for acquiring K root, audition flag data, service ID, etc. .
- the client that has received the content information transmits a request for obtaining usage right information (Usage Right) corresponding to the received content to the license server (step (73)).
- This request includes the usage right information ID (UID) included in the startup file (see Fig. 15), leaf ID as client identification data, and transaction ID (TID).
- the license server When the license server receives the request for obtaining the usage right information (Usage Right), it performs order inquiry processing (step (74)) to the management system.
- This request includes a usage rights information ID (UID) and a transaction ID (TID).
- the management server that has received the order inquiry sends response information in which the usage conditions corresponding to the usage right information ID (UID) are set to the license server as an order inquiry response (step (75)).
- the license server Upon receiving the response information, the license server generates usage right information (Usage Right) in which the content usage conditions are set, and sends the usage right to the client. Is reissued (step (76)).
- the content use conditions are constituted by the number of times the content has been played, the time limit, copying to external devices, and permission information for various processes such as checkout processes.
- the client that has received the usage right information (Usage Right) stores the previously received content and the usage right information in the storage means as backup data.
- the usage right information issued by the license server may be one in which usage conditions different from the usage right information issued at the time of legitimate content purchase processing are set.
- use rights for backup / restore processing by setting conditions that are stricter than the use conditions included in the use right information issued when purchasing legitimate content, such as restrictions on the use period, prohibition of copying, or prohibition of checkout Set and issue information
- the client who has purchased the content regularly performs the so-called secondary distribution of content, which provides the purchased content to other clients, and newly distributes the right to use the content from the license server to receive the secondary distribution content.
- the following describes a configuration that enables the client to use the content on condition that the client has a legitimate content usage right, and further reduces the content distribution load from the content server.
- the client that plays back the content receives the encrypted content from the content server, and also receives the license information, ie, the service data, from the license server. Receiving usage right information corresponding to the content Is required.
- the license information that is, service data and usage right information
- a communication network such as the Internet
- various types of content such as music data, image data, and programs
- the data capacity is large.
- the transmission time becomes longer, causing various problems such as a burden on the content server and an increase in network traffic.
- a content distribution error may occur due to a communication error during communication.
- Figure 28 shows a flow that explains the processing procedure for generating a content file to be provided to another client by a client that has received the content properly.
- a data file containing the content to be provided to other clients is called a recommendation file.
- the recommendation file includes a content file containing the encrypted content and, if necessary, a description file (eg, an HTML file) of the content.
- the processing flow of FIG. 28 will be described. The client executing the processing shown in Fig.
- FIG. 28 executes the content purchase processing described above, and Or a client who has received a recommendation file from another client and obtained a legitimate license in subsequent procedures.
- the processing in FIG. 28 is executed as one execution program of the client application (client application 12 in FIG. 1) under the control of the control means (CPU or the like) of the information processing device as a client system.
- the client displays a recommendation file creation screen on the display of its client device.
- Figure 29 shows an example of a recommendation file creation screen.
- Movement processing between the contents list 651 and the list 654 is executed by the operation of the movement switches 652 and 653.
- the recommendation file creation button 655 is pressed in step S803.
- an explanation file for example, an explanation file described in HTML is generated and stored in the recommendation file along with the content file. Or choose. This can be arbitrarily selected by the user.
- the recommendation file includes a recommendation file 720 composed of a content file 721 including an encrypted content and a content description file 722, and FIG.
- a recommendation file 730 consisting only of the content file 721 including the encoded content
- the client can freely select the mode.
- step S804 if it is selected not to create a content explanation file, a recommendation file 730 including only the content file 721 shown in FIG. 30 (b) is generated.
- Figure 31 shows the configuration of the content inlay.
- the content file (MQT file) 721 contains the encrypted content, meta information as additional information of the content, a shop server URL indicating a shop where the content can be purchased, and a content as a content identifier. Contains the ID (CID).
- the encrypted content stored in the content file is the content encrypted by the content key Kc, and the content key Kc is a valid key provided by applying the activation key block (EKB) distribution tree configuration.
- EKB activation key block
- step S804 if the creation of a content description file is selected in step S804, the flow advances to step S806, and the description data (metadata) for generating the content description file (HTML file) is stored in the content management table. get.
- the content description data corresponding to the content is stored in the content file together with the encrypted content, but the client that has obtained the right to use the content properly obtains the metadata corresponding to the content extracted from the content file. Is stored and managed in a separate file as content management data, and the metadata for the description file generated in the recommendation file is extracted from this content management data.
- step S807 the meta extracted from the content management data Executes the process of pasting the data to the template HTML file set in the client application, generates a description HTML file corresponding to the content, and in step S808, converts the content file and the description HWML file Generate a new recommendation file.
- Figure 32 shows an example of the display configuration of an HTML file as data for explaining the content. The example shown in FIG. 32 is an example when the content is music data. As shown in FIG. 32, the explanation file describes an information list of music titles, artists, distributors, etc. of music contents, and further describes various operations and processes. A client that receives a recommendation file from another client will first open this description file.
- the content stored in the recommendation file is encoded content and cannot be played back without obtaining the proper license information, that is, service data and usage right information corresponding to the content. Absent. Therefore, when the client that has received the recommendation file uses the content stored in the recommendation file, a procedure for acquiring the license information is executed.
- This license information acquisition processing will be described with reference to the processing flow of FIG. 33 and FIG.
- the client that has received the recommendation file opens the explanatory file (HTML file) shown in Fig. 32, and clicks the preview and purchase content distribution site button 731 (step S811). By this click processing, the client application starts (step S812), reads the content file (MQT file) (see Fig. 31) stored in the same recommendation file, and reads out the content file from the content file.
- MQT file content file
- Extract Content ID (CID) and Shop URL Exit step S8 13
- the preview button for the content description file and the purchase content distribution site button 731 extract the shop server URL from the content file and start the client application program that executes the process of outputting the extracted URL to the browser. It is configured as link data. Therefore, the client who received the recommendation file can easily connect to the shop and execute the purchase procedure.
- a content file name is set based on the content ID (CID) extracted from the content file. This is executed as a file name setting process preset in the client application. For example, a title of the content, an artist name, or a composite data thereof is applied.
- step S815 the content file having the file name set in step S815 is stored in the storage unit of the client.
- step S816 the shop URL extracted from the content file in step S816 is passed to the browser, and the browser reads a shop page corresponding to the received URL from the shop server.
- step S831 of the processing flow in FIG. 34 a shop screen is displayed on the client display.
- the following processing is basically the same as any of the content purchase processing and the trial listening processing described above, and has been described with reference to FIGS. 11, 13, 18, and 21. It will follow the process. However, since the content itself has already been obtained from the recommendation file by the con-client, the content server's content reception processing is omitted.
- step S832 An outline of a series of processing is the processing shown in step S832 and subsequent steps of the processing flow in FIG.
- the shop server sends an activation file for purchase. It has the same configuration as the startup file described above with reference to FIG.
- step S833 a content ID (CID) as a content identifier is obtained from the startup file.
- step S8334 a content file name is calculated based on the content ID (CID). It is specified in the client application that the content file name when storing the content in the client device is set based on the content ID (CID) as described in the description of the flow in FIG. 33 above.
- the CID is associated with the file name.
- step S835 it is determined whether a file having the same file name as the file name calculated from the content ID (CID) is stored in the storage unit of the client device. If no content is stored, the flow advances to step S8337 to connect to the content server and download the content. This process is the same as the content purchase process described above.
- step S814 and S815 of FIG. 33 the client receiving the recommendation file stores the content file in which the predetermined file name is set in the storage unit. The content download process is omitted, and the content use right information acquisition process in step S8336 is executed, and the process can be terminated.
- the client executes content playback, as described above, the content identifier (CID) stored in the content usage right information and the playback pair are used.
- the content is compared with the content identifier (CID) of the target content, and the content is reproduced on condition that the CID matches.
- the content key Kc is obtained by decrypting the activation key block (EKB) provided by applying the activation key block (EKB) distribution tree configuration, and the encrypted content is applied by applying the acquired content key Kc.
- the client who already has the content provides the content file including the encrypted content and the recommendation file including the explanatory file to the other client, so that the other client can transmit the content file to the content distribution server.
- Content can be received without access. Since other clients can use the content on condition that they obtain the usage right information, unauthorized use of the content is prevented.
- the ability to install and execute a program that records the processing sequence in the memory of a computer built into dedicated hardware, or a general-purpose computer that can execute various processing It is possible to install and execute the program at the same time.
- the program can be recorded in a hard disk or a ROM (Read Only Memory) as a storage medium in advance.
- the program may be removable recording such as a flexi disk, a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto Optical) disk, a DVD (Digital Versatile Disk), a magnetic disk, or a semiconductor memory. It can be stored (recorded) temporarily or permanently on a medium.
- a removable recording medium can be provided as so-called package software.
- the program can be installed on a computer from a removable recording medium as described above, and can be transferred wirelessly from a download site to a computer, a LAN (Local Area Network), or a network such as the Internet.
- the program can be transferred to a computer via a wire, and the computer can receive the transferred program and install the program on a storage medium such as a built-in hard disk.
- the various processes described in the specification may be executed not only in chronological order according to the description, but also in parallel or individually according to the processing capability of the device that executes the processes or as necessary.
- the client obtains the default usage right information (Defau1t UsageRight) at the time of registration processing with the license server, and performs the content purchase processing.
- Content playback is permitted based on the default usage right information at the time of the trial listening process without the content, and the user can preview and play the content without executing the purchase of the content.
- clients who are permitted to listen are registered in the license server and are limited to those who have the default usage right information. This prevents random listening data.
- the hardware corresponding to the EKB corresponding to the category set corresponding to the hardware as the content using device can be used.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Multimedia (AREA)
- Technology Law (AREA)
- Computer Hardware Design (AREA)
- Mathematical Physics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Storage Device Security (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP03738574A EP1524604A4 (en) | 2002-07-23 | 2003-06-30 | INFORMATION PROCESSING DEVICE, INFORMATION PROCESSING METHOD AND COMPUTER PROGRAM |
US10/490,232 US8090102B2 (en) | 2002-07-23 | 2003-06-30 | Information processing device, information processing method, and computer program |
KR1020047004155A KR100983982B1 (ko) | 2002-07-23 | 2003-06-30 | 정보 처리 장치 및 정보 처리 방법과 컴퓨터 판독 가능 기록 매체 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2002213700A JP3864867B2 (ja) | 2002-07-23 | 2002-07-23 | 情報処理装置、および情報処理方法、並びにコンピュータ・プログラム |
JP2002-213700 | 2002-07-23 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004010307A1 true WO2004010307A1 (ja) | 2004-01-29 |
Family
ID=30767847
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2003/008267 WO2004010307A1 (ja) | 2002-07-23 | 2003-06-30 | 情報処理装置、および情報処理方法、並びにコンピュータ・プログラム |
Country Status (6)
Country | Link |
---|---|
US (1) | US8090102B2 (ja) |
EP (1) | EP1524604A4 (ja) |
JP (1) | JP3864867B2 (ja) |
KR (1) | KR100983982B1 (ja) |
CN (1) | CN100428256C (ja) |
WO (1) | WO2004010307A1 (ja) |
Families Citing this family (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8151259B2 (en) | 2006-01-03 | 2012-04-03 | Apple Inc. | Remote content updates for portable media devices |
US8732086B2 (en) * | 2003-01-02 | 2014-05-20 | Catch Media, Inc. | Method and system for managing rights for digital music |
US8666524B2 (en) | 2003-01-02 | 2014-03-04 | Catch Media, Inc. | Portable music player and transmitter |
JP4343542B2 (ja) * | 2003-01-30 | 2009-10-14 | ソニー株式会社 | 情報処理システム、情報処理装置および情報処理方法、並びにプログラムおよび記録媒体 |
US7724716B2 (en) | 2006-06-20 | 2010-05-25 | Apple Inc. | Wireless communication system |
US7831199B2 (en) | 2006-01-03 | 2010-11-09 | Apple Inc. | Media data exchange, transfer or delivery for portable electronic devices |
US9264468B2 (en) * | 2003-07-14 | 2016-02-16 | Sony Corporation | Recording device, recording method, and program |
JP4478871B2 (ja) * | 2004-05-19 | 2010-06-09 | ソニー株式会社 | コンテンツデータ再生装置、コンテンツデータ提供装置、コンテンツデータ再生方法、コンテンツデータ提供方法、コンテンツデータ再生プログラム及びコンテンツデータ提供プログラム |
US20060064759A1 (en) * | 2004-09-22 | 2006-03-23 | Wildlife Acoustics, Inc. | Method and apparatus for controlling access to downloadable content |
US7706637B2 (en) * | 2004-10-25 | 2010-04-27 | Apple Inc. | Host configured for interoperation with coupled portable media player device |
US7536565B2 (en) | 2005-01-07 | 2009-05-19 | Apple Inc. | Techniques for improved playlist processing on media devices |
US8300841B2 (en) | 2005-06-03 | 2012-10-30 | Apple Inc. | Techniques for presenting sound effects on a portable media player |
JP2007011452A (ja) * | 2005-06-28 | 2007-01-18 | Sony Corp | プログラム、データ処理方法、データ処理装置、オーディオ再生装置 |
US7930369B2 (en) | 2005-10-19 | 2011-04-19 | Apple Inc. | Remotely configured media device |
JP4556857B2 (ja) * | 2005-12-07 | 2010-10-06 | セイコーエプソン株式会社 | 情報配信装置、情報配信装置の制御方法および制御プログラム |
US8654993B2 (en) | 2005-12-07 | 2014-02-18 | Apple Inc. | Portable audio device providing automated control of audio volume parameters for hearing protection |
US8255640B2 (en) | 2006-01-03 | 2012-08-28 | Apple Inc. | Media device with intelligent cache utilization |
US20070198428A1 (en) * | 2006-02-22 | 2007-08-23 | Microsoft Corporation | Purchasing of computer service access licenses |
US7853945B2 (en) | 2006-02-22 | 2010-12-14 | Michael Kramer | Integrated computer server imaging |
US20070198427A1 (en) * | 2006-02-22 | 2007-08-23 | Microsoft Corporation | Computer service licensing management |
US7848527B2 (en) | 2006-02-27 | 2010-12-07 | Apple Inc. | Dynamic power management in a portable media delivery system |
JP2007304849A (ja) * | 2006-05-11 | 2007-11-22 | Sony Corp | 管理装置、情報処理装置、管理方法および情報処理方法 |
US8358273B2 (en) | 2006-05-23 | 2013-01-22 | Apple Inc. | Portable media device with power-managed display |
US7729791B2 (en) | 2006-09-11 | 2010-06-01 | Apple Inc. | Portable media playback device including user interface event passthrough to non-media-playback processing |
US8341524B2 (en) | 2006-09-11 | 2012-12-25 | Apple Inc. | Portable electronic device with local search capabilities |
US8090130B2 (en) | 2006-09-11 | 2012-01-03 | Apple Inc. | Highly portable media devices |
US20080114695A1 (en) * | 2006-11-10 | 2008-05-15 | Semantic Components S.L. | Process for implementing a method for the on-line sale of software product use licenses through a data network, and software component which allows carrying out said process |
US7589629B2 (en) | 2007-02-28 | 2009-09-15 | Apple Inc. | Event recorder for portable media device |
WO2008122308A1 (en) * | 2007-04-04 | 2008-10-16 | Media Patents S.L. | Process for the on-line distribution, through a data network, of digital files protected by intellectual property rights and computer readable medium containing a program for carrying out said process |
ES2326949B1 (es) | 2008-03-18 | 2010-07-14 | Clarity Systems, S.L. | Procedimiento utilizado por un servidor de streaming para realizar una transmision de un fichero multimedia en una red de datos. |
US7984097B2 (en) * | 2008-03-18 | 2011-07-19 | Media Patents, S.L. | Methods for transmitting multimedia files and advertisements |
CN102158810B (zh) * | 2011-04-20 | 2016-09-28 | 中兴通讯股份有限公司 | 基于组播方式下载应用的方法、装置和*** |
CA2780879C (en) * | 2011-06-21 | 2019-02-12 | Research In Motion Limited | Provisioning a shared secret to a portable electronic device and to a service entity |
CN103098072B (zh) * | 2011-09-06 | 2016-04-27 | 松下电器产业株式会社 | 记录介质装置以及记录介质装置的控制方法 |
US8458494B1 (en) * | 2012-03-26 | 2013-06-04 | Symantec Corporation | Systems and methods for secure third-party data storage |
US8966287B2 (en) | 2012-03-26 | 2015-02-24 | Symantec Corporation | Systems and methods for secure third-party data storage |
US8904503B2 (en) | 2013-01-15 | 2014-12-02 | Symantec Corporation | Systems and methods for providing access to data accounts within user profiles via cloud-based storage services |
US9202076B1 (en) | 2013-07-26 | 2015-12-01 | Symantec Corporation | Systems and methods for sharing data stored on secure third-party storage platforms |
US9076004B1 (en) | 2014-05-07 | 2015-07-07 | Symantec Corporation | Systems and methods for secure hybrid third-party data storage |
JP2016015073A (ja) * | 2014-07-03 | 2016-01-28 | ソニー株式会社 | 情報処理装置、情報処理方法およびコンテンツ提供システム |
CN108063756B (zh) | 2017-11-21 | 2020-07-03 | 阿里巴巴集团控股有限公司 | 一种密钥管理方法、装置及设备 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07221751A (ja) * | 1994-02-07 | 1995-08-18 | Nippon Telegr & Teleph Corp <Ntt> | ディジタル情報複製方法及びその装置 |
JPH08272746A (ja) * | 1994-11-23 | 1996-10-18 | Xerox Corp | 料金通知メカニズムを有するディジタルワークの配給及び使用を制御するためのシステムと料金通知方法 |
JPH09297682A (ja) * | 1996-04-30 | 1997-11-18 | Nec Corp | 試用pp管理システム |
JP2000293439A (ja) * | 1999-04-06 | 2000-10-20 | Fujitsu Ltd | コンテンツ利用制御システム、コンテンツ利用装置およびその利用方法をコンピュータに実行させるプログラムを記録したコンピュータ読み取り可能な記録媒体 |
WO2001044907A1 (en) * | 1999-12-17 | 2001-06-21 | Microsoft Corporation | Inter-server communication using request with encrypted parameter |
JP2002133147A (ja) * | 2001-10-15 | 2002-05-10 | Fujitsu Ltd | コンテンツ売上金分配システム及び分配方法 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5553139A (en) * | 1994-04-04 | 1996-09-03 | Novell, Inc. | Method and apparatus for electronic license distribution |
US5758257A (en) * | 1994-11-29 | 1998-05-26 | Herz; Frederick | System and method for scheduling broadcast of and access to video programs and other data using customer profiles |
CN100452071C (zh) * | 1995-02-13 | 2009-01-14 | 英特特拉斯特技术公司 | 用于安全交易管理和电子权利保护的***和方法 |
US6108420A (en) * | 1997-04-10 | 2000-08-22 | Channelware Inc. | Method and system for networked installation of uniquely customized, authenticable, and traceable software application |
US6385596B1 (en) * | 1998-02-06 | 2002-05-07 | Liquid Audio, Inc. | Secure online music distribution system |
US6727914B1 (en) * | 1999-12-17 | 2004-04-27 | Koninklijke Philips Electronics N.V. | Method and apparatus for recommending television programming using decision trees |
EP1334583A2 (en) * | 2000-10-26 | 2003-08-13 | General Instrument Corporation | Enforcement of content rights and conditions for multimedia content |
US6993508B1 (en) * | 2000-12-29 | 2006-01-31 | Novell, Inc. | Method and mechanism for vending digital content |
US20020108114A1 (en) * | 2001-02-08 | 2002-08-08 | Sony Corporation | System and method for presenting DVD bulletin board screen personalized to viewer |
-
2002
- 2002-07-23 JP JP2002213700A patent/JP3864867B2/ja not_active Expired - Fee Related
-
2003
- 2003-06-30 CN CNB038013436A patent/CN100428256C/zh not_active Expired - Fee Related
- 2003-06-30 KR KR1020047004155A patent/KR100983982B1/ko not_active IP Right Cessation
- 2003-06-30 WO PCT/JP2003/008267 patent/WO2004010307A1/ja active Application Filing
- 2003-06-30 EP EP03738574A patent/EP1524604A4/en not_active Withdrawn
- 2003-06-30 US US10/490,232 patent/US8090102B2/en not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07221751A (ja) * | 1994-02-07 | 1995-08-18 | Nippon Telegr & Teleph Corp <Ntt> | ディジタル情報複製方法及びその装置 |
JPH08272746A (ja) * | 1994-11-23 | 1996-10-18 | Xerox Corp | 料金通知メカニズムを有するディジタルワークの配給及び使用を制御するためのシステムと料金通知方法 |
JPH09297682A (ja) * | 1996-04-30 | 1997-11-18 | Nec Corp | 試用pp管理システム |
JP2000293439A (ja) * | 1999-04-06 | 2000-10-20 | Fujitsu Ltd | コンテンツ利用制御システム、コンテンツ利用装置およびその利用方法をコンピュータに実行させるプログラムを記録したコンピュータ読み取り可能な記録媒体 |
WO2001044907A1 (en) * | 1999-12-17 | 2001-06-21 | Microsoft Corporation | Inter-server communication using request with encrypted parameter |
JP2002133147A (ja) * | 2001-10-15 | 2002-05-10 | Fujitsu Ltd | コンテンツ売上金分配システム及び分配方法 |
Non-Patent Citations (2)
Title |
---|
"Windows media rights manager FAQ", MICROSOFT CORPORATION, 2001, XP002972359, Retrieved from the Internet <URL:http://www.archive.org/web/20010813233655/www.microsoft.com/japan/windows/windowsmedia.wm7/DRM/FAQ.asp?LNK=1> [retrieved on 20030904] * |
ITARU HOSOMI, MASAYUKI NAKAE, TOSHIHARU ICHIYAMA: "Digital joho ryutsu architecture mediashell to sono riyo.kakin seigyo", INFORMATION PROCESSING SOCIETY OF JAPAN KENKYU HOKOKU 98-EIP-2, INFORMATION PROCESSING SOCIETY OF JAPAN, vol. 98, no. 85, 19 September 1998 (1998-09-19), pages 49 - 56, XP002907859 * |
Also Published As
Publication number | Publication date |
---|---|
EP1524604A1 (en) | 2005-04-20 |
US8090102B2 (en) | 2012-01-03 |
US20040255135A1 (en) | 2004-12-16 |
CN100428256C (zh) | 2008-10-22 |
JP2004054744A (ja) | 2004-02-19 |
JP3864867B2 (ja) | 2007-01-10 |
KR100983982B1 (ko) | 2010-09-27 |
CN1571959A (zh) | 2005-01-26 |
EP1524604A4 (en) | 2007-11-14 |
KR20050026905A (ko) | 2005-03-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2004010307A1 (ja) | 情報処理装置、および情報処理方法、並びにコンピュータ・プログラム | |
US7836311B2 (en) | Information processing apparatus, information processing method, and computer program used therewith | |
KR101028176B1 (ko) | 정보 기록 매체, 정보 처리 장치, 정보 처리 방법, 및 컴퓨터 프로그램을 기록한 컴퓨터 판독가능 기록 매체 | |
JP3788438B2 (ja) | 情報記録媒体、情報処理装置、および情報処理方法、並びにコンピュータ・プログラム | |
JP4760101B2 (ja) | コンテンツ提供システム,コンテンツ再生装置,プログラム,およびコンテンツ再生方法 | |
US7933837B2 (en) | Content information providing system, content information providing server, content reproduction apparatus, content information providing method, content reproduction method and computer program | |
JP5113299B2 (ja) | Drm提供装置、システムおよびその方法 | |
EP1538543A1 (en) | License management device, license management method, and computer program | |
WO2003088056A1 (fr) | Dispositif de traitement d'information, procede et programme correspondants | |
WO2002087147A1 (fr) | Dispositif et procede d'enregistrement/de reproduction d'informations | |
JP2003317376A (ja) | 情報管理装置および方法、記録媒体、並びにプログラム | |
JP3818503B2 (ja) | 情報処理装置および方法、並びにプログラム | |
JP4053701B2 (ja) | デジタルコンテント無断複製防止システム | |
JP4449959B2 (ja) | 情報処理装置、および情報処理方法、並びにコンピュータ・プログラム | |
JP4192499B2 (ja) | 情報処理装置、情報処理方法、およびコンテンツ入出力処理システム、コンテンツ入出力処理方法、並びにコンピュータ・プログラム | |
JP2004054745A (ja) | 情報処理装置、および二次配信コンテンツ生成方法、情報処理方法、並びにコンピュータ・プログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CN KR US |
|
AL | Designated countries for regional patents |
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 LU MC NL PT SE SI SK TR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003738574 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10490232 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020047004155 Country of ref document: KR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 20038013436 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2003738574 Country of ref document: EP |