WO2004077301A1 - 端末装置及びサーバ装置並びにそれらを用いたライセンス流通システム - Google Patents
端末装置及びサーバ装置並びにそれらを用いたライセンス流通システム Download PDFInfo
- Publication number
- WO2004077301A1 WO2004077301A1 PCT/JP2004/002122 JP2004002122W WO2004077301A1 WO 2004077301 A1 WO2004077301 A1 WO 2004077301A1 JP 2004002122 W JP2004002122 W JP 2004002122W WO 2004077301 A1 WO2004077301 A1 WO 2004077301A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- domain
- license
- terminal device
- information
- identifier
- Prior art date
Links
- 230000005540 biological transmission Effects 0.000 claims abstract description 45
- 238000000034 method Methods 0.000 claims description 73
- 238000004891 communication Methods 0.000 claims description 50
- 230000002401 inhibitory effect Effects 0.000 abstract 1
- 238000007726 management method Methods 0.000 description 58
- 238000010586 diagram Methods 0.000 description 22
- 239000000284 extract Substances 0.000 description 6
- 239000009261 D 400 Substances 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000013500 data storage Methods 0.000 description 2
- RGHMISIYKIHAJW-UHFFFAOYSA-N 3,4-dihydroxymandelic acid Chemical compound OC(=O)C(O)C1=CC=C(O)C(O)=C1 RGHMISIYKIHAJW-UHFFFAOYSA-N 0.000 description 1
- 239000002131 composite material Substances 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
- H04N21/462—Content or additional data management, e.g. creating a master electronic program guide from data received from the Internet and a Head-end, controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabilities
- H04N21/4627—Rights management associated to the content
-
- 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/101—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities
- G06F21/1012—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM] by binding digital rights to specific entities to domains
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/16—Analogue secrecy systems; Analogue subscription systems
- H04N7/162—Authorising the user terminal, e.g. by paying; Registering the use of a subscription channel, e.g. billing
- H04N7/163—Authorising the user terminal, e.g. by paying; Registering the use of a subscription channel, e.g. billing by receiver means only
Definitions
- the present invention relates to a terminal device that reproduces or records digital work content using a license, a server device that distributes the license, and a license distribution system using the same.
- a server distributes information (hereinafter, referred to as “license j”) including usage conditions and content keys necessary for using content, and transmits a plurality of information on a home network system (home network).
- the terminal device is modeled to use the content by using the license distributed from the server and to perform reproduction and the like.
- licenses distributed from the server are held in individual terminal devices, and the terminal devices use the content by using the licenses owned by the terminal devices.
- licenses transferred between multiple terminal devices it cannot be moved in an unlimited range from the viewpoint of content rights protection and the protection of the privacy of terminal device owners. range In general, only movement within is permitted.
- a server device sets one domain for a plurality of terminal devices owned by the same user, and for each domain, an ID or a domain is set. A key is generated and distributed to each terminal device. By doing so, the same domain key is set to the terminal devices belonging to the same domain.
- the terminal encrypts the content key with the domain key when outputting the content key to the outside.
- the terminal device belonging to the same domain can decrypt the content key, and the terminal device not belonging to the same domain cannot decrypt the content key.
- the conventional terminal device, server device, and license distribution system described above have a problem that licenses are distributed across domains by terminal devices belonging to a plurality of domains.
- FIG. 1 is an explanatory diagram for explaining a problem of a conventional license distribution system and the like.
- the license is moved between the two terminal devices, and the license is moved.
- the license can be used in the terminal device.
- terminal B belongs to two domains X and Y
- terminal A belongs to domain X
- terminal C belongs to domain Y
- the license held by terminal A can be transferred. The range will be described.
- the license held by the terminal device A can be transferred to the terminal device B belonging to the same domain X.
- the license held by the terminal device B can be transferred to the terminal device C belonging to the same domain Y. That is, the license held by the terminal device A moves to the terminal device C belonging to a different domain via the terminal device B. That is, since there are terminal devices belonging to a plurality of domains, it is not possible to control the license transfer range in which license transfer between terminal devices is permitted only in a predetermined domain and other transfers are prohibited. Will be. As a result, there is a problem that each terminal device can freely use a license acquired from a domain to which the terminal device does not belong.
- the present invention has been made in view of such a problem, and an object of the present invention is to provide a terminal device and a server device that appropriately restrict the use of a license in each terminal device, and a license distribution system including the terminal device and the server device. . Disclosure of the invention
- a terminal device is a terminal device in a system having a plurality of domains as terminal device groups, and includes license information for enabling use of digital work. And a license information holding unit that holds the license information in association with domain identification information indicating any one of the plurality of domains, a domain to which another terminal device belongs, and a domain indicated by the domain identification information are different.
- the use prohibiting means includes: first domain discriminating means for discriminating whether a domain to which the other terminal device belongs is different from a domain indicated by the domain identification information; and the first domain discriminating means.
- the use prohibition unit transmits the license information and the domain identification information to the other terminal device, and transmits a domain to which the other terminal device belongs and the domain identification information to the other terminal device. It is determined whether or not the domain indicated by the license information is different. If the domain is different, the use of the license information by the other terminal device is prohibited.
- the terminal device further determines that the domain to which the terminal device belongs is different from the domain indicated by the domain identification information, and that the terminal device is different from the domain determination device.
- a self-use prohibition unit for prohibiting use of the content using the license information by the terminal device itself when performed.
- the terminal device cannot reproduce the content using the license information associated with the domain identification information. Usage can be more appropriately restricted.
- the terminal device may further include a writing unit for rewriting the domain identification information so that a domain indicated by the domain identification information is different. It may be characterized by having a replacement means.
- the content of the domain identification information is rewritten by the terminal device, so that the use of the license can be restricted on a domain-by-domain basis, and the restriction can be relaxed to improve the usability of the user.
- the present invention provides a method program for handling a license by the terminal device, a server device for distributing the license, a method for distributing the license by the server device, and a license distribution system including the terminal device and the server device. It can also be realized.
- FIG. 1 is an explanatory diagram for explaining a conventional problem.
- FIG. 2 is a diagram showing a schematic configuration of the entire license distribution system according to the embodiment of the present invention.
- FIG. 3 is a functional block diagram showing configurations of the domain management server, the license distribution server, and the terminal device according to the embodiment of the present invention.
- FIG. 4 is a diagram showing a table configuration of the domain information storage unit according to the embodiment of the present invention.
- FIG. 5 is a diagram showing a table configuration of the domain determination information storage unit according to the embodiment of the present invention.
- FIG. 6 is a diagram showing a table configuration of the user information storage unit according to the embodiment of the present invention.
- FIG. 7 is a diagram showing a table configuration of the use condition storage unit according to the embodiment of the present invention.
- FIG. 8 is a diagram showing a table configuration of the content key storage unit according to the embodiment of the present invention.
- FIG. 9 is a table configuration of the license storage unit according to the embodiment of the present invention.
- FIG. 10 is a diagram showing a configuration of the license according to the embodiment of the present invention.
- FIG. 11 is a diagram showing a configuration of a communication message according to the embodiment of the present invention.
- FIG. 12 is a diagram showing a configuration of the domain determination information request message body according to the embodiment of the present invention.
- FIG. 13 is a diagram showing a configuration of the domain determination information transmission message body according to the embodiment of the present invention.
- FIG. 14 is a diagram showing a configuration of a license distribution request message body according to the embodiment of the present invention.
- FIG. 15 is a diagram showing a configuration of the license request message body according to the embodiment of the present invention.
- FIG. 16 is a diagram showing a configuration of the license search request message body according to the embodiment of the present invention.
- FIG. 17 is a diagram showing a configuration of a license search reply message body according to the embodiment of the present invention.
- FIG. 18 is a diagram showing a configuration of an embodiment of the present invention: such a license acquisition request message body.
- FIG. 19 is a flowchart illustrating a process in which the terminal device according to the embodiment of the present invention acquires domain determination information from the domain management server.
- FIG. 20 is a flowchart showing a process in which the terminal device according to the embodiment of the present invention acquires a license from a license distribution server.
- FIG. 21 is a flowchart showing a process in which the terminal device according to the embodiment of the present invention searches for a license for another terminal device.
- FIG. 22 shows that the terminal device according to the embodiment of the present invention is radiated from another terminal device.
- 5 is a flowchart showing a process of acquiring a license.
- FIG. 23 is a diagram showing a data structure of a license whose domain identifier is rewritable according to the embodiment of the present invention.
- FIG. 24 is a flowchart showing a process in which the terminal device according to the embodiment of the present invention acquires a license whose domain identifier is rewritable from another terminal device.
- FIG. 2 is a diagram showing an overall schematic configuration of a license distribution system S according to the embodiment of the present invention.
- This license distribution system S is a system in which a server device controls a moving range of a license held by a terminal device, and includes a domain management server 100 that performs domain management, and a license distribution server 20 that distributes licenses. 0, terminal devices 300a to 300c that hold licenses and transfer licenses to and from other terminal devices, and transmission lines N that interconnect these components.
- the domain in the present invention is defined.
- a data distribution service if there are terminal devices that can mutually share and move data, those terminal device groups can be logically grouped.
- the unit to which the group of terminal devices belongs is defined as a domain.
- data movement and sharing between terminal devices belonging to different domains shall not be permitted.
- the unit for setting the domain is determined from the viewpoint of protecting the data rights of the provider of the data distribution service and the viewpoint of protecting the privacy of the user.
- a typical example is to set a domain for each user as a subscriber to the telecommunications service.
- a domain to which only one terminal device belongs may be formed, or one terminal device may belong to two or more domains. Now that the domain has been defined, each component of the license distribution system S will be described.
- the domain management server 100 manages the terminal devices belonging to the domain, generates and manages the domain judgment information set for each domain, and transmits the domain judgment information to the terminal device. It is. Specifically, the domain management server 100 manages the domain and the domain determination information, and based on the request from the terminal device, transmits the domain determination information through the transmission path N. It is a server device for transmitting to terminal devices 300a to 300c, and is realized by a workstation or the like.
- the domain determination information is information for determining whether a communication partner terminal device belongs to the same domain when performing communication between terminal devices.
- domain key an encryption key of a common key cryptosystem shared by terminal devices belonging to the same domain
- domain key list a list of information for identifying terminal devices belonging to the same domain. This is called “domain terminal device list”).
- SA CJ secure authentication channel
- SSL Secure Sock et Layer
- TLS Transport Layer Security
- the license distribution server 200 is a server device that manages usage conditions of content owned by a user and grants a license of the content to the user. Specifically, the license distribution server 200 manages the usage conditions of the content owned by each user or each of the terminal devices 300a to 300c, and The license is generated based on the request from the server, and the license is distributed to the terminal devices 300a to 300c via the transmission path N. Alternatively, in a push-type distribution mode such as digital broadcasting or broadband broadcasting, a temporarily invalidated license is distributed together with the content, and the terminal device 300a to 300c performs charging processing. In this way, relicensing can be activated and content can be used.
- a push-type distribution mode such as digital broadcasting or broadband broadcasting
- a license is data composed of a decryption key (hereinafter referred to as a “content key”) for decrypting encrypted content and information related to content use and transfer control.
- the transmission path N is a network that interconnects the domain management server 100, the license distribution server 200, and the terminal devices 300a to 300c.
- the transmission path N is a communication network such as the Internet, digital broadcasting, or a network in which these are combined.
- Terminal 3 0 0 a ⁇ 3 0 0 c a license between the transmission path N and has a function of connecting, Li Interview one THE makes a use of Konten', other terminal devices It is a device that moves.
- the terminal devices 300a to 300c are devices that allow a user to use data such as content based on a license using a monitor screen or the like.
- 0 0 a ⁇ 300 c is for STB (Set Top Box), digital TV, DVD (Digita IV ersati I e D isc) recorder, HDD (Hard D isk D) rive) A recorder, a content display device such as a PC (Persona IC omputer), a recorder, or a composite device of these.
- STB Set Top Box
- DVD Digita IV ersati I e D isc
- HDD Hard D isk D
- a recorder a content display device such as a PC (Persona IC omputer), a recorder, or a composite device of these.
- a process from when a terminal device 300a to 300c acquires a license and transfers a license to another terminal device is described. This will be described in detail with reference to FIGS. 3 to 22.
- the identifier in the present embodiment is defined.
- the domain identifier is information for uniquely specifying a domain in the license distribution system S.
- the user identifier is information for uniquely identifying a user in the license distribution system S.
- the terminal identifier is information for uniquely identifying a terminal device in the license distribution system S.
- the terminal identifier of the terminal device 300 will be described as “TE RM INAL-ID—00001 J.
- the terminal identifier is stored in the ROM of the terminal device 300. The following explanation is based on this assumption.
- the license identifier is information for uniquely identifying a license in the terminal device 300. Also, by combining the terminal identifier and the license identifier, the license is It can be uniquely specified.
- FIG. 3 is a functional block diagram showing a detailed configuration of the domain management server 100, the license distribution server 200, and the terminal device 300 shown in FIG.
- the functional configuration of the terminal devices 300a to 300c is represented by the terminal device 300a as a representative and the terminal device 300a.
- the domain management server 100 includes a domain information storage unit 111 for storing domain information, a domain determination information storage unit 112 for storing domain determination information, and a terminal device 300.
- a communication unit 101 that communicates with the terminal device 0, a domain determination unit 102 that determines the domain to which the terminal device 300 belongs, and a domain determination information generation unit 103 that generates domain determination information.
- a domain determination information acquisition unit 104 that acquires domain determination information from the domain determination information storage unit 112.
- the license distribution server 2000 includes a user information storage unit 211 for storing user information, a usage condition storage unit 212 for storing usage conditions, a content key storage unit 212 for storing a content key, A communication unit 201 that communicates with the terminal device 300, a license generation unit 202 that generates a license from a usage condition, a domain identifier, and a content key, and a usage condition generation unit 2 that generates a usage condition 0 3 and a domain identification assigning section 204 that sets a domain identifier to be assigned to the license.
- Terminal device 3 0 0 is obtained from the domain judgment information storage unit 311 that stores the domain judgment information obtained from the domain management server 100, the license distribution server 2 0 0, and other terminal devices 3 0 0.
- the license belongs to the terminal device 300 based on the domain determination unit 303 that determines whether the partner terminal device 300 belongs to the same domain and the domain identifier included in the license. Can be processed in the domain A domain identification determination unit 304 that determines whether or not a license is distributed, a license distribution request unit 3006 that generates a license distribution request message and makes a license distribution request to the license distribution server 200, and a license search. And a message requesting license processing such as acquisition, and receiving from another terminal device 300 a license processing requesting unit 307 that requests license processing to another terminal device 300 And a license processing result transmission unit 3005 for returning the processing result of the license processing request to the other terminal device 300.
- Each server and terminal device is composed of each data storage unit and each processing unit.
- Each data storage unit is realized by a storage medium such as an HDD
- each processing unit is a hardware such as an LSI or a CPU, This is realized by a program executed using RAM, ROM, or the like.
- RAM random access memory
- ROM read-only memory
- each storage unit and each processing unit be hard or softly tamper-resistant.
- data and a data structure handled in the present embodiment will be described. First, the data structure of the data stored in each storage unit will be described in the order of the domain management server 100, the license distribution server 200, and the terminal device 300. Finally, the license distribution server in the present embodiment will be described. A description will be given of a license that is distributed from 200 to the terminal device 300 and can be moved to another terminal device, and a data structure of the license.
- the domain information storage unit 111 is a database having a domain management table for managing information about a domain, and is used to associate a domain with a terminal device 300 belonging to the domain. Used. Specifically, the main information storage unit 111 has a domain management table D300 shown in FIG.
- the domain identifier D301 is "DOMAIN-
- the terminal device 300 which is I NAL -I D -00001J, belongs.
- the domain identifier D 301 is ⁇ D OM A I N I D I
- the terminal identifier D 3 0 2 is r T E R M I N A
- ⁇ DO M A I N-I D-0 0 3 J has a terminal s element D 3 0 2 force ⁇ ⁇ E R R R R R — — — — — — — — — — — — — — — —
- terminal identifier D 3 0 2 power ⁇ ⁇ T E R M I N A
- the terminal device 300 having “0 0 1” has a domain identifier D 3 0 1 of ⁇ DO It indicates that the domain of “MAIN—ID—00001” and the domain identifier D301 belong to the domain of ⁇ DOMAIN-ID-00003J.
- the domain determination information storage unit 112 is a database that manages domain determination information that is information for determining whether or not the terminal device 300 of the communication partner belongs to the same domain. This is used to acquire domain judgment information of the domain corresponding to the terminal identifier included in the domain judgment information acquisition request when transmitting domain judgment information in response to the domain judgment information acquisition request from 0.
- the domain determination information is a domain key and a case where the domain determination information is a domain terminal device list will be described.
- the domain judgment information storage unit 112 has a domain judgment information management table D 400 shown in (a) of FIG. 5, and includes a domain identifier D 401 and a domain key D 400. 2 and are managed.
- the domain determination information to be transmitted to the terminal device 300 belonging to the domain whose domain identifier D401 is “DOMAIN-ID-00001” is a domain key “DOMA IN— KEY”. -0 0 0 1 j.
- the domain judgment information storage unit 112 has a domain judgment information management table D410 shown in FIG. 5B, and includes a domain identifier D411 and a domain terminal device list D4. 1 and 2 are managed.
- the domain identification information to be transmitted to the terminal device 300 belonging to the domain whose domain identifier D 411 1 is “D OM AIN—ID-0 0 0 1 J” is the terminal identifier ⁇ E RM INAL-ID- 00 0 1 J N Indicates that this is the domain terminal device list of “TE RM INAL—ID—0 0 0 2”.
- data registration in the domain information storage unit 111 and the domain determination information storage unit 112 is performed by a user who owns the terminal device 300 through a transmission line N to perform domain management. This is done when connecting to the user's website and registering online using the domain registration screen.
- the domain registration may be done offline, such as by using a postcard for registration.
- the above-mentioned business operator assigns the domain identifier D301 to the user and simultaneously assigns the domain to the user.
- the domain determination information generation unit 103 generates domain determination information corresponding to the domain identifier D301, and the domain identifier D401 and the domain key D402 are associated with each other. It is registered in the domain determination information management table D 400 of the domain determination information storage unit 112.
- the terminal identifier of the terminal device 300 is notified online or offline to the operator, so that the domain identifier D301 and the terminal identifier D302 are associated with each other. Then, it is registered in the domain management table D 300 of the domain information storage unit 111 through the domain judgment unit 102. As a result of performing the above-described domain registration processing, a domain management table D300 of the domain information storage unit 111 is constructed.
- the process of adding the terminal device 300 to the domain is performed by connecting the user to the business operator's website, and using the terminal device addition screen, the domain identifier of the domain to be added, and The terminal identifier of the terminal device 300 to be added is input, and the domain identifier D of the domain management table D 300 of the domain information storage unit 111 is input through the domain determination unit 102.
- This is realized by adding the terminal identifier to the terminal identifier D302 corresponding to 301.
- the domain determination information storage unit 1 1 2 when the domain determination information is a domain key Described the data registration to the The same applies to the domain terminal device list.
- the user information storage unit 211 is a database having a user information management table for managing information about the user, and includes a terminal device 300 that accesses the license distribution server 200 and a use condition storage unit. It is used for associating with the user who owns the usage conditions of the content managed in 2.12.
- the user information storage unit 211 has a user information management table D500 shown in FIG. 6, and manages a user identifier D501 and a terminal identifier D502 '. ing.
- a user whose user identifier D 5 01 is ru SER—ID-0000 1 J is a terminal device whose terminal identifier D 5 02 is “TE RM INAL—ID—00 0 1 J.
- It has two terminal devices 300, called ID-1100J and TERM INAL—ID-1002J, and both terminals 300 can access the license distribution server 200.
- the data registration in the user information storage unit 211 is performed when the user registers as a member to receive the service provided by the service provider that operates the content distribution service.
- the user provides a content distribution service through the transmission path N.
- Connect to the W eb site of the operators, by the membership registration screen, may be UTO line to register online, such as using a postcard for membership registration, may be performed off-line.
- the service provider assigns a user identifier D501 to a user.
- the terminal identifier D502 of the terminal device 300 owned by the user is notified to the service provider online or offline, so that the user identifier D501 and the terminal identifier D502 are distinguished.
- the information is associated and registered in the user information management table D500 of the user information storage unit 211.
- the user information management table D500 of the user information storage unit 211 is constructed.
- the use condition storage unit 212 is a database that manages use conditions for content for each user. In response to a license distribution request from the terminal device 300, it is determined whether a use condition owned by the user can be issued. Is used to generate usage conditions when it can be issued.
- the usage condition storage unit 212 includes a user identifier D601 indicating the owner of the usage condition and a content identifier D6 of the content permitted to be used by the usage condition. 02, valid period D603 indicating the start and end dates and times when the content indicated by the content identifier D602 can be used, and the content indicated by the content identifier D602 can be used.
- the number of usable times D 604 indicates the number of times of use, and the use condition management table D 600 comprises.
- the usage condition management table D600 includes a user identifier D6101 ⁇ “USER—ID-00003J”. ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ 0 0 — ID shown in 0 2 ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ID ID ID ID 0— ID— 0 0 04 J It is 220 J, indicating that the number of usable times D 604 is unlimited ( ⁇ ), that is, it can be used any number of times.
- the data registration in the usage condition storage unit 2 1 2 is performed by the content distribution server. This is done by the service provider operating the service when the user purchases the right to use the content. This purchase process may be performed by the user connecting to the service provider's website via the transmission path N and making an online purchase on the content purchase screen, or may be performed offline, such as by using a postcard for purchase. May be.
- the user In the purchase process, the user first specifies the content identifier D602 of the content to be purchased, confirms the usage conditions, and then performs the purchase process.
- the user identifier D 601 of the user who performed the purchase processing, the content identifier D 602, and the use condition are associated with each other and registered in the use condition management table D 600 of the use condition storage unit 212. .
- a use condition management table D 600 of the use condition storage unit 212 is constructed.
- the content key storage unit 2 13 is a database that manages content keys for decrypting encrypted content, and is used to generate a license in response to a license acquisition request from the terminal device 300. It is used to acquire the content key corresponding to the content identifier included in the license acquisition request.
- the content key storage unit 2 13 stores the content identifier D 701 that uniquely identifies the content in the license distribution system S and the content identifier D 701 as shown in FIG. It has a content key management table D700 including a corresponding content key D702.
- the content key management table D 7100 has a content identifier D 7 0 1 of “rc ONTENT—ID— 0 0 0 1” and a content key D 7 02 for decrypting the encrypted content. — KEY— 0 0 0 1 ”.
- the domain information storage unit of the domain management server 100 is used.
- the user information storage unit 211 of the license distribution server 200 may cooperate with the user information storage unit 211 to share the registration process.
- the domain determination information storage unit 3 1 "I is a database for managing the domain determination information, and is used to determine whether the communication partner terminal device 300 belongs to the same domain. The details are as described in the domain determination information storage unit 112.
- the license storage unit 321 is a database for managing licenses. It is used to acquire a license corresponding to the content identifier when using the content in the terminal device 300 or when transmitting a license to another terminal device 300. Specifically, the license storage unit 3 1 2 is
- License management table consisting of license D 8 0 2 corresponding to 0 1
- the license management table D800 indicates that the license of the license identifier D8001 is lower than the license ID of D8001J. Note that the data registration to the license storage unit 312 is performed when the terminal device 300 acquires the license from the license distribution server 200 or another terminal a300.
- License is one of the data used in the content distribution system.
- the content distribution system will be briefly described.
- a content distribution system is used to transfer content to the Internet or other sources. This system enables the server device to distribute the content to the terminal device through communication or digital broadcasting, and to use the content in the terminal device.This protects the copyright of the content, and the content is illegal by malicious users. Copyright protection technology is used to prevent use.
- copyright protection technology is a technology that uses encryption technology to securely control the use of content, such as when a user plays back content or copies it to a recording medium.
- the server device generates a license including a usage condition such as the number of times of reproduction of the content that can be used in the terminal device and a content key for decrypting the encrypted content.
- the terminal device distributes and decrypts the separately acquired encrypted content with the content key of the license, and controls the use of the content based on the usage conditions.
- a content key and a license are assigned in content units and are associated with a content identifier.
- the content identifier is information for uniquely specifying the content in the content distribution system.
- a description will be given assuming that a license is granted on a content basis.
- the license 900 is composed of a usage condition 9001 consisting of information that can be used for the content, a content key 9002 for decrypting the encrypted content corresponding to the license 900, and a license 900. And a domain identifier 903 that identifies a domain that can be used and moved.
- the terms of use 9 0 1 means that the content corresponding to the license 9 For example, “10 times” and the available period, for example, ⁇ 200, 1 February 1, 2000 to 2003, 13 February, etc. ”.
- the license 900 needs to be associated with the content identifier in the license storage unit 312 and the processing related to the license, and the processing of associating the license 900 with the content identifier in the terminal device 300 is required.
- the license 900 may include a content identifier.
- the license data structure has been described above.
- the data structure of the data handled in the present embodiment has been described above.
- processing required until the terminal device 300 transfers a license to a terminal device belonging to the same domain will be described.
- the processing in making the request will be described in the order of Fig. 19 with reference to Figs.
- FIG. 11 shows the contents of the message format of the communication message Ml100 transmitted and received in the communication between the domain management server 100 and the license distribution server 200 and the terminal device 300.
- the communication message M1000 in FIG. 11 includes a message header M1001 and a message body M1002.
- the message header M1001 includes at least information for specifying the transmission destination and information for specifying the transmission source.
- the information specifying the transmission destination is referred to as a message destination, and the information specifying the transmission source is referred to as a destination when transmitting a reply message to the message. Is done.
- a typical example of the information for specifying the transmission source or the transmission destination is an IP address.
- information necessary for the authentication processing may be included in the message header.
- the message itself contains information unique to each message. Information specific to the message body will be explained for each message.
- the body M1100 of the message for requesting domain judgment information in Fig. 12 is composed of the terminal identifier M111.
- the domain determination information transmission message body M1200 in FIG. 13 includes a domain identifier M1201 and domain determination information M1202.
- the data structure of the communication message related to the domain determination information acquisition processing has been described above.
- FIG. 19 shows a case where the terminal device 300 according to the embodiment of the present invention manages the domain.
- 5 is a flowchart illustrating a process of acquiring domain determination information from a server 100.
- the terminal device 300 starts domain determination information acquisition processing in response to a domain determination information acquisition instruction to the terminal application by the user.
- the terminal application that has received the domain determination information acquisition instruction issues a domain determination information acquisition instruction to the domain determination information acquisition unit 302.
- the domain determination information acquisition section 302 receives the domain determination information request message (including the domain determination information request message body M11000 as the message body M1002).
- a communication message Ml100) is generated and transmitted to the domain management server 100 through the communication unit 301 (step S1831).
- the terminal identifier M1101 which is included in the domain determination information request message body M110, sets the terminal identifier acquired from the ROM of the terminal device 300.
- ⁇ T ER M I N A L-I D-0 0 0 1 J is set.
- the domain management server 100 receives the domain determination information request message via the communication unit 101 (step S1811).
- the domain determination unit 102 extracts the terminal identifier M111 from the domain determination information request message body M110, and outputs the domain management information of the domain information storage unit 111.
- the terminal identifier M 1101 is searched from the management table D 300 to check whether the terminal device 300 is registered in the domain (step S 1812). As a result of the search, if the terminal identifier M111 does not exist, the domain determination unit 102 returns, via the communication unit 101, a message including the fact that the terminal does not belong to the domain in the message body. The message is transmitted to the terminal device 300.
- the terminal device 300 Upon receiving the reply message (Step S1832), the terminal device 300 presents the fact to the user and ends the process (FIG. 19: End).
- the domain determination unit 102 determines that the domain identifier D30 of the domain to which the terminal device 300 belongs. Identify 1 and obtain it (step S1813).
- a plurality of domain identifiers are hit by the search.
- the subsequent processing is performed for each domain identifier, and a domain determination information transmission message including a list of a pair of the domain determination information and the domain identifier may be transmitted.
- a reply message including the plurality of hit domain identifiers may be transmitted to the terminal device 300, and the user may select one domain identifier, and the subsequent processing may be performed.
- the domain judgment information acquisition unit 104 searches the domain judgment information management table D 400 of the domain judgment information storage unit 112 for the domain identifier D 310, and finds the domain identifier D 3 A domain key D402, which is domain determination information of the domain corresponding to 01, is specified and obtained (step S1814).
- the domain judgment information acquisition unit 104 attaches a message header to the acquired domain identifier D301 and the domain key D402, and sends a domain judgment information transmission message (message body M10).
- a communication message M 1 00 0) including the domain determination information transmission message body M 1 2000 is generated as 0 2, and transmitted to the terminal device 3 0 0 through the communication unit 1 0 1 (step S 2).
- the terminal device 300 receives the domain determination information transmission message via the communication unit 301 (step S1833), and stores the domain identifier D301 and the domain key D402.
- the extracted information is stored in the domain determination information storage unit 311 in association with both (step S1834), and the process is terminated.
- the domain determination information is a domain terminal device list
- the domain determination information acquisition unit 104 searches the domain determination information management table D 411 of the domain determination information storage unit 112 for the domain identifier D 310 and finds the domain identifier D 310.
- the domain terminal device list D 412 which is the domain determination information of the domain corresponding to 1 is specified and obtained (step S 18 14).
- the domain judgment information acquisition unit 104 adds a message header to the acquired domain identifier D301 and the domain terminal device list D411 to generate a domain judgment information transmission message. Then, it transmits to the terminal device 300 through the communication unit 101 (step S1815).
- the terminal device 300 receives the domain determination information transmission message via the communication unit 301 (step S1833), and outputs a domain identifier D301 and a domain terminal device list. D 412 is extracted, and the two are associated with each other and stored in the domain determination information storage unit 311 (step S 1 834), and the process ends.
- the license delivery request message body M1300 of FIG. 14 includes a terminal identifier M1301, a content identifier M1302, and a domain identifier M1303.
- the license transmission message body Ml 400 in FIG. 15 includes the license M 1 401.
- the data structure of the communication message relating to the license distribution request 'acquisition process has been described above.
- processing of each unit until the terminal device 300 acquires a license from the license distribution server 200 will be described with reference to FIG.
- FIG. 20 is a flowchart illustrating a process in which terminal device 300 according to the embodiment of the present invention acquires a license from license distribution server 200.
- the terminal device 300 starts license acquisition processing in response to a user inputting information to the application of the terminal device 300 and a license acquisition instruction.
- the user for the application on the terminal device 300, obtains at least one of the information for identifying the license to be acquired, the content identifier or the information equivalent to the content identifier, and the acquisition target license.
- You must enter a domain identifier, which is one of the information that identifies a domain that can use or move, or information similar to the domain identifier.
- the terminal device 300 Upon receiving the information input from the user, the terminal device 300 sends the license delivery request message (the message delivery request body Ml 03 as the message delivery request body M102) in the license delivery requesting section 303.
- a communication message Ml 0 0 0) including 0 0 is generated and transmitted to the license distribution server 2 0 0 via the communication section 3 0 1 (step S 1931).
- the terminal identifier M1301 included in the license distribution request message body M1300 includes the terminal identifier "TERM INAL-ID-0" of the terminal device 300 that transmits the license distribution request message. 0 1 ”is set, and the content identifier M 13 02 is set to the content identifier ⁇ CONTENT—ID-00 01 J input by the user, and the domain identifier is set. Ml033 contains the domain identifier entered by the user ⁇ DOMAIN— I
- the license distribution server 200 receives the license distribution request message via the communication unit 201 (step S 1911).
- the license generation unit 202 extracts the content identifier M1302 from the license distribution request message body Ml300, and stores the content key corresponding to the content identifier M1302 in the content key. It is determined whether or not it exists in the section 2 13 (step S 1912).
- the license distribution server 200 cannot generate the license.
- the message is transmitted to the terminal device 300.
- the license generation unit 202 acquires the content key and performs the subsequent processing. Note that, in the present embodiment, as shown in FIG. 8, the content identifier I ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ — ID-0 0 0 0
- the usage condition generation unit 203 receives the license distribution request message body M 13
- the terminal identifier M 1 301 is extracted from 0 0, and the terminal identifier M 1 301 is used as a key from the user information management table D 5 0 0 held by the user information storage unit 211 to determine the terminal identifier.
- the terminal identifier M 1 3 0 1 is the user information management table D 5 0
- the usage condition generation unit 203 determines that the terminal device 300 that has transmitted the license distribution request message is not registered in the content distribution service, and cannot generate a usage condition. Therefore, the processing is terminated, and a reply message containing the message that the terminal identifier does not exist is included in the message body. To the terminal device 300.
- the usage condition generation unit 203 acquires the user identifier D501 and performs the subsequent processing.
- a user identifier “USER—ID—001” exists as a user identifier corresponding to the terminal identifier “TERMINAL—ID—001”. Then, the following description is continued.
- the usage condition generation unit 203 holds the usage condition storage unit 212 based on the user identifier D501 and the content identifier M1302 extracted from the license distribution request message body M1300. From the use condition management table D600 to be used, the target use condition is specified. Specifically, the usage condition generating unit 203 sets the user identifier D 601 and the content identifier D 602 of the usage condition management table D 600 to the user identifier D 501 and the content identifier M 1. Identify the record that matches both 302. If there is no corresponding record, the use condition generating unit 203 sends a reply message including the absence of the use condition to the terminal device 300.
- the use condition generating unit 203 If the corresponding record exists, the use condition generating unit 203 generates a use condition to be distributed based on the stored use condition (step S 1913).
- a generation method at this time there are a method of generating all the usage conditions described in the record and a method of generating a part of the usage conditions described in the record.
- Content identifier rc ONTENT The use condition of the record identified by ID— 0 0 0 1 J is valid period ⁇ ⁇ 2 0 3 1 3 0 J, available The number of times is “10 times”.
- the usage condition generation unit 203 When distributing all the usage conditions, the usage condition generation unit 203 generates the usage conditions by setting the number of usable times, which is a variable usage condition, to ⁇ 10 times, and generates the usage conditions. Number of available times is set to "0 Times ”.
- the usage condition generation unit 203 When distributing a part of the user's right, the usage condition generation unit 203 notifies the terminal device 300 of the number of times the user wants (for example, three times), and the usage condition is a variable usage condition.
- the usage condition is generated with the number of times being “3”, and the usable number of times of the record after generation is set to “7”.
- the usage condition generation unit 203 generates the usage condition with the number of times of use set to “once” when the operation is set to “ ⁇ once”, and the record can be used after the generation.
- the number of times is “9 times”.
- various operations can be considered, but they are not the essence of the present invention.
- it is assumed that the number of usable times is 10 times.
- the domain identification assigning unit 204 extracts the domain identifier M1303 from the license distribution request message body M1300 and determines the domain identifier to be assigned to the license ( Step S 191 4). Note that the domain identification providing unit 204 further extracts the terminal identifier M1301, and the terminal device 300 that has transmitted the license distribution request message corresponds to the domain identifier M1303. It may be possible to check whether it is included in the domain by inquiring the domain information storage unit 111.
- the domain identification assigning section 204 selects the domain to which the terminal apparatus 300 that has transmitted the license distribution request message from the domain information storage section 111 belongs.
- the domain identifier may be specified. In this case, it is not necessary to set the domain identifier 1303 in the license distribution request message body M1300.
- the user may select one domain identifier and determine it as a domain identifier to be assigned to the license.
- the domain identifier may be determined as the domain identifier to be assigned to the license. Multiple domain identifiers are determined In this case, the domain identifier 903 of the license 900 becomes a domain identifier list.
- the domain identification assigning unit 204 assigns the domain identifier Ml303 included in the license distribution request message body M1303 acquired from the terminal device 300 to the license.
- the domain identifier according to the license is treated as a domain identifier to be assigned to the license, it may be treated as a domain identifier to be assigned to the license.
- a predetermined domain identifier is associated with the user identifier D601 included in the usage condition management table D600 of the usage condition storage unit 212. Therefore, the domain identification providing unit 204 specifies a user identifier corresponding to the use condition generated by the use condition generation unit 203 from the use condition management table D600.
- the domain identification assigning unit 204 treats the domain identifier associated with the user identifier as a domain identifier assigned to the license. Further, when a usage type such as a home or a workplace is set as a usage condition in the usage condition management table D600, a domain identifier corresponding to the usage type (home or workplace) is set in the same manner as the user identifier described above. , May be treated as a domain identifier assigned to the license.
- the terminal device 300 generates a license distribution request message including the terminal identifier M1301, the content identifier M1302, and the domain identifier M1303. And transmitted to the license distribution server 200 at a different timing. For example, when establishing a SAC with the license distribution server 200, the terminal device 300 transmits a terminal identifier M1301 to the license distribution server 200, and after the SAC is established, The identifier M 13 02 and the domain identifier M 130 3 are transmitted to the license distribution server 200.
- the license generation unit 202 sets the usage condition generated by the usage condition generation unit 203 as the usage condition 901, and sets the content key acquired in advance as the content key 902.
- the domain identifier determined by the domain identification providing unit 204 is set to the domain and the main identifier 903, and a license 900 is generated (step S1915). Then, the license generation unit 202 converts the license 900 into the license transmission message body Ml 400 license M
- the value is set to 1401, and transmitted to the terminal device 300 via the communication unit 201 (step S1916).
- the meta-instrument 300 receives the license transmission message body ⁇ 140 0 through the communication section 310 and acquires the license M 1 401 (step S).
- the terminal device 300 associates the acquired license M1401 with the same content identifier as the content identifier M1302 of the license distribution request message and stores the license M1401 in the license storage unit 312 (step S12). 1 9 3 4). In the case where the content identifier is included in the license 900, the association process is not required.
- terminal device 300 When terminal device 300 receives a reply message including a non-generation notification from license distribution server 200, terminal device 300 presents to the user the reason for non-generation that is included in the reply message, and terminates the process. (Step S1932).
- processes related to license transfer include a license search process and a license acquisition process. (License search process)
- the terminal device 300 as the search subject transmits a license search process request to the other plurality of terminal devices 300.
- the terminal device 300 as the search subject broadcasts a license search processing request to a plurality of other terminal devices 300 and receives the license search processing request. Returns the presence or absence of the license to be searched. Since the search entity broadcasts the license search processing request, it is not realistic to establish SACC with all communication partners.
- the domain determination in the license search process is not always strict. This is because the purpose of the license search process is to identify the terminal device 300 holding the license that the search subject terminal device 300 wants to acquire, and is not related to license transfer. This is because there is no damage even if the device 300 performs tampering or other fraud.
- license transfer between terminal devices belonging to different domains is not permitted, and license use and transfer can be performed only at terminal devices belonging to the domain to which license use and transfer are permitted. are doing. Therefore, the following two domain judgments are required.
- the first is a domain determination that determines whether the terminal device that transmitted the license processing request and the terminal device that received the license processing request belong to the same domain.
- the second is a domain judgment for judging whether the use of the license or the movement is permitted in the domain to which the terminal device which transmitted the license processing request belongs.
- the former makes a domain judgment based on the domain judgment information, and the latter makes a domain judgment based on the domain identifier included in the license. Perform domain judgment.
- the license search request message body M1500 in Fig. 16 is composed of a content identifier M1501, which is information required for a license search request, and a checksum Ml for the content identifier M1501. 5 0 2
- the license search reply message body M1600 in FIG. 17 includes a license identifier M1661.
- a license search request is transmitted from the terminal device 300a to the terminal device 300b, and it is determined whether or not the terminal device 300b belongs to the same domain as the terminal device 300a.
- the processing of each unit until the terminal device 300a receives the presence or absence of the search target license will be described with reference to FIG.
- FIG. 21 is a flowchart showing a process in which the terminal device 300 according to the embodiment of the present invention searches for a license for another terminal device 300.
- the terminal device 300a starts a license search process in response to a user's input of information to the application of the terminal device 300a and a license search instruction.
- the user is required to provide the application of the terminal device 300a with at least one of the content identifier or the content identifier, which is one of the information specifying the license to be searched, and the terminal device 3a.
- 0 0a holds licenses to be searched if a belongs to multiple domains
- the user does not particularly specify, and the application automatically specifies the domain identifier of the domain to which the terminal device 300a belongs.
- the terminal device 300a belongs to a plurality of domains, the following processing may be performed on all domains to which the terminal device 300a belongs.
- the terminal device 300a which has received the information input from the user, sends the content identifier ⁇ CONTENT—ID—O001J and the content identifier Ml501 in the license processing requesting section 307. (Step S2031), and a checksum M1502 for the content identifier Ml501 is calculated (Step S2032).
- the license processing request unit 307 obtains a domain key from the domain determination information storage unit 311 using the domain identifier ⁇ D OM AIN-ID-00 0 1 J input by the user as a key.
- the content identifier M1501 and the checksum M1502 are encrypted using the domain key (step S2033), and the license search request message (message body M150) is encrypted.
- a communication message M 1 00) including the license search request message body M 1 500 is created.
- the license processing request unit 307 sends a license search request message to the terminal device 300b via the communication unit 301 (step S2034).
- the terminal device 300b transmits the license search request through the communication unit 301.
- the message is received (step S201).
- the domain determination unit 303 of the terminal device 300b obtains the domain key from the domain determination information storage unit 311 and decrypts the encryption unit of the license search request message (step S10). 2 0 1 2), calculate a checksum for the content identifier M 1501 (step S 2 0 13), and judge the match with the checksum M 1 502 (step S 2 0 1 4) ).
- the domain determination unit 303 determines that the terminal device 300a belongs to the same domain as itself, and performs the subsequent processing. If the checksums do not match, it is determined that they do not belong to the same domain, the processing is terminated, and a reply message including the fact that they do not belong to the same domain is transmitted to the terminal device 300a. I do.
- the domain determination unit 303 stores a domain identifier corresponding to the domain key whose checksum matches.
- the domain determination unit 303 repeats step S201 to step S210 in order to determine whether the terminal device 300a belongs to the same domain as itself. Determine whether or not. Further, a domain identifier to which the terminal device 300a belongs may be set in the license search request message, and the above-described repetitive processing may be omitted.
- the domain identification determination unit 304 searches for a license from the license storage unit 312 using the content identifier Ml501 extracted from the license search request message as a key, and holds the license to be searched. If so, obtain this and perform the subsequent processing. If the license to be searched is not held, the domain identification determination unit 304 terminates the processing and returns a reply message including in the message body that the license to be searched is not held. Is transmitted to the terminal device 300a via the communication unit 301.
- the domain identification determination section 304 extracts the domain identifier 903 from the acquired license (step S210), and the domain determination section 303 stores the domain identifier. A match with the identifier is determined (step S201). If the domain identifiers match, the domain identification determination unit 304 determines that the search target license can be moved in the domain to which the terminal device 300a and the terminal device 300b belong. Then, the license processing result transmitting unit 3005 transfers the license identifier, which is the identifier of the license in the terminal device 300b, to the license identifier M1601 of the license search reply message body Ml600. It is set (step S201), and transmitted to the terminal device 300a via the communication unit 301 (step S21018).
- the domain identification determination unit 304 determines that the license to be searched cannot be moved, terminates the processing, and informs that the license to be searched cannot be moved.
- the reply message included in the message body is transmitted to the terminal device 300a.
- the domain identification judgment unit 304 sends a reply message including the error content to the terminal device 300a, but if the reply message is not sent. You may.
- domain determination in license search processing is not necessarily strict. Therefore, instead of performing encryption using a domain key, a domain identifier may be set instead of the checksum M1502. In this case, instead of decrypting the encrypted data, generating the checksum, and checking the checksum of the checksum (steps S201 to S210), the data is stored in the domain determination information storage unit 311. Domain identifier corresponding to the specified domain key and the license search request A match with the domain identifier set in the message is determined.
- the terminal device 300a uses a plurality of domain keys to list the contents of the license search request message body Ml500. It may be sent in the default format. Also, when the terminal device 300a belongs to a plurality of domains and performs domain determination using a domain identifier, the terminal device 300a transmits a list of domain identifiers. Is also good. In any case, the operation of steps S201 to S214 is repeatedly performed.
- the terminal device 300a receives the license search reply message (step S2035), acquires information identifying the terminal device 300 holding the license to be searched from the message header,
- the license identifier M1601 is obtained from the license search reply message body M1600, and information (terminal identifier) identifying the terminal device 300 and the license identifier M1661 are searched for. It is stored together with the content identifier corresponding to the license.
- the terminal device 300b includes the terminal identifier in the license search reply message body M1600 and includes the terminal identifier. For 300a, the terminal identifier may be obtained and stored.
- terminal device 300a transmitting a license search request to terminal device 300b to specifying terminal device 300 holding the license has been described above.
- the terminal device 300 which is the subject of acquisition, transmits a license acquisition process request to one terminal device 300.
- the terminal device that is the subject of the acquisition 3 0 0 transmits a license acquisition processing request to one terminal apparatus 3 0 0 identified as a result of the search processing, and the terminal apparatus 3 0 0 receiving the license acquisition processing request returns a license.
- the license acquisition request message body M1700 in FIG. 18 includes a license identifier M1701, which is information required for a license acquisition request.
- the terminal device 300a transmits a license acquisition request to the terminal device 300b, and determines whether the terminal device 300b belongs to the same domain as the terminal device 300a.
- the processing of each unit until the terminal device 300a receives the acquisition target license will be described with reference to FIG. Here, it is assumed that a domain terminal device list is held as domain determination information.
- FIG. 22 is a flowchart showing a process in which the terminal device 300 according to the embodiment of the present invention acquires a license from another terminal device 300.
- the terminal device 300a starts license acquisition processing in response to a user's information input to the application of the terminal device 300a and a license acquisition instruction.
- the user must input, to the application of the terminal device 300a, at least a content identifier, which is one of the information for specifying the license to be acquired, or information equivalent to the content identifier. .
- the license identifier of the license to be acquired stored in the license search process may be specified. The following description is given on the assumption that the user has input the content identifier rc ONTENT—ID-00001 and has started the license acquisition process.
- the license processing requesting part 3007 of the terminal device 300a that has received the information input from the user specifies the terminal device 300 that holds the search target license stored in the license search process. Is retrieved using the content identifier “CONTENT—ID—0 0 0 1 J” entered by the user as a key. This identifies the terminal device 300 b that is to perform the license acquisition process. The license acquisition process is started.
- the terminal device 300a and the terminal device 300b communicate with each other to establish the SAC (step S2111, step S2131).
- the terminal device 300a transmits a terminal identifier to the terminal device 300b when the SAC is established.
- the domain determination unit 303 of the terminal device 300b stores the terminal identifier of the terminal device 300a acquired at the time of establishing the SAC, in the domain terminal device list stored in the domain determination information storage unit 311. And determines whether or not the terminal device 300a belongs to the same domain as itself (step S2111)
- the terminal device 300b determines that the domains belong to the same domain, and the domain matching notification message including the message that the domains match in the message body. Message to the terminal device 300a. Note that the domain identifier of the matching domain may be included in the domain matching notification message.
- the domain determination unit 303 of the terminal device 300b stores the domain identifier associated with the terminal identifier of the terminal device 300a in the domain terminal device list.
- the terminal identifier of the terminal device 300a exists in a plurality of domain terminal device lists, that is, when both the terminal device 300a and the terminal device 300b belong to a plurality of domains
- the domain identifiers corresponding to the plurality of domains are set in a list format in the domain match notification message, and the terminal device 300a is caused to specify in which domain the license is to be obtained.
- the terminal device 300b may specify it.
- the terminal device 300b determines that the terminal device 300a and the terminal device 300b do not belong to the same domain. Then, a reply message including the fact that the domains do not match in the message body is transmitted to the terminal device 300a.
- the terminal device 300a Upon receiving the domain matching notification message (step S2132), the terminal device 300a receives the user input from the license processing request unit 3007 of the terminal device 300a.
- a license acquisition request message is transmitted to the terminal device 300b via the communication unit 301 (step S2113).
- a domain identifier for designating which domain is to be licensed at the time of license acquisition is used. It may be set in the acquisition request message.
- the terminal device 300b receives the license acquisition request message via the communication unit 301 (step S2113).
- the domain identification determination section 304 of the terminal device 300b searches the license storage section 3122 for the license identifier M1701 extracted from the license acquisition request message, and finds the license identifier. If Ml 7 0 1 is found, the license corresponding to it is acquired, and the subsequent processing is performed. If there is no license identifier M 1 7 0 1, the processing is terminated and the license to be acquired is not held.
- the reply message included in the message body is sent to the terminal device 3.
- the domain identification determination unit 304 extracts the domain identifier 903 from the acquired license (step S2114), and compares the domain identifier stored in the domain determination unit 303 with the domain identifier. A match is determined (step S2115).
- the license processing result transmission unit 3005 sets the acquired license as the license Ml 401 of the license transmission message body M1400 (step S
- step S 2 11 17 the terminal device 300 a via the communication section 310 (step S 2 118).
- the terminal device 300a receives the license transmission message (step S2135), and converts the license M1401 extracted from the license transmission message into a content identifier rc ONTENT. — ID— 0 0 0 1 ”and stored in the license storage unit 3 1 2 (step S 2 1 3 6)
- the terminal device 300a obtains the license, and transmits a license acquisition notification message including the fact that the license is stored in the message body to the terminal device 300b via the communication unit 301 ( Step S 2 1 3 7).
- the terminal device 300b receives the license acquisition notification message (Step S2119), and deletes the license locked in the license storage unit 312 (Step S2). 11 A).
- the terminal device 300b If the license acquisition notification message does not return within a predetermined time after transmitting the license transmission message, or the terminal device 300b receives a notification notifying that the license acquisition or storage has failed. In that case, the locked license may be made available.
- the terminal device 300b transmits the terminal device based on the terminal identifier exchanged when the SAC is established and the domain terminal device list. It is determined whether or not the terminal device 300a and the terminal device 300b belong to the same domain.
- the terminal device 300a transmits the domain key to the terminal device 300b at the time of establishing SAC, and the terminal device 300b Domain judgment may be performed based on whether or not the same key as the domain key is held.
- the terminal device 300a transmits the domain identifier to the terminal device 300b at the time of establishing the SAC
- the terminal device 300b determines the domain with respect to the domain identifier. Domain determination may be performed based on whether or not information is held.
- the terminal device 300a transmits such a terminal identifier, a domain key,
- the domain determination using the domain identifier may be performed not only when the SAC is established but also when a license acquisition request message is transmitted and received after the SAC is established, and the domain determination as described above is performed without establishing the SAC. May be performed.
- a plurality of domain identifiers may be transmitted in a list format. In this case, the terminal device 300b performs domain determination for each domain identifier.
- the terminal device 300 a and the terminal device 300 b both belong to a plurality of domains, the terminal device 300 a or the terminal device 300 b It is sufficient to specify whether to transfer the license in the domain. The same applies to the case where the data transmitted from the terminal device 300a to the terminal device 300b is a domain key.
- the domain identifier of the license is set by the license distribution server 200.
- the license distribution server 200 may set, in the license, information for limiting the number of times of rewriting the domain identifier of the license. This limits the range of license transfer without compromising the convenience of the user.
- FIG. 23 is a diagram illustrating a data structure of a license whose domain identifier is rewritable.
- This license 900A includes the use condition 900A, the content key 9002A, and the domain identifier 903A similar to the license 900 shown in FIG. Includes a rewrite flag 904 A indicating whether or not the domain identifier 903 A is rewritable, a maximum number of rewrites 905 A, and a number of rewrites 9 06 A indicating the number of times of rewriting so far. .
- FIG. 24 shows a case where terminal device 300 according to the embodiment of the present invention is another terminal device.
- FIG. 1 A flowchart showing processing for acquiring license 900 A from 300 is shown in FIG.
- the s metasthesis m. 300 a is the step S 2 13 1 to S 2 13 in FIG.
- step S 100 While performing the same processing A as in step 4 (step S 100), the terminal device 30
- 0b performs the same processing B as step S2 1 1 1 to 2 1 1 4 in FIG.
- the terminal device 300b receives the domain identifier 900 of the license 900A acquired from the terminal device 300a in the same manner as in step S2115 in FIG.
- step S104 It is determined whether 3A matches the domain identifier of the domain to which the terminal device 300a belongs.
- the terminal devices 300a and 300b perform the same processing as the processing shown in FIG. That is, the terminal device 300b executes the same processing C as steps S2116 to S2118 in FIG. 22 (step S106),
- the terminal device 300a receives the license transmission message transmitted by the process C (step S108). Further, the meta-device 300a stores the license 900A extracted from the message in the license storage unit 312 (step S110), and receives a license acquisition notification message. Is transmitted to the terminal device 300b (step S112). Terminal device 3
- step SI16 the license 900A locked by the process C of step SI06 is deleted (step SI114) (step SI16).
- step S104 when the terminal device 300b determines in step S104 that the domain identifiers do not match (mismatch in step S104), the terminal device 300b further rewrites the flag 900A of the license 900A.
- Check 0 4 A step S 118.
- the terminal device 300 b is transferred from the license 90 OA to the maximum number 90 5 A And the rewrite number 9 06 A are obtained (step S 120). If the rewriting flag 904A indicates that rewriting is not possible (step S118 is not possible), the terminal device 300b ends the process.
- the terminal device 300b which has obtained the maximum number 905 A and the number of rewrites 906 A in step S120, checks the number of rewrites 906A (step S122). That is, the terminal device 300b determines whether the number of rewrites 906 A is equal to the maximum number 905 A or whether the number of rewrites 906 A is smaller than the maximum number 905 A. Here, when the number of rewrites 906 A is equal to the maximum number 905 A, the terminal device 300 b ends the processing. Also, when the number of rewrites 90 A is smaller than the maximum number 90 A, the terminal device 300b operates in the same manner as in steps S2116 to S2118 in FIG.
- Step S 124 a license transmission message including the license 90 OA is generated (Step S 126), and the license transmission message is generated.
- the message is transmitted to the terminal device 300a together with the domain rewriting instruction (step S128).
- terminal device 300a Upon receiving the license transmission message and the domain rewrite instruction transmitted from terminal device 300b in step S128, terminal device 300a includes the license transmission message in the license transmission message (step S130).
- La The domain identifier 90 3 A of the license 90 OA and the number of rewrites 9 06 A are rewritten (step S 13 2). That is, the terminal device 300a rewrites the domain identifier 903A to the domain identifier of the domain to which the terminal device 300a belongs so that the number of rewrites 906A is added only once.
- the meta-device 3 OOa executes the above-described steps S110 and S112, and the terminal device 300b executes the above-described steps S114 and S116. I do.
- the terminal device 300b transmitted the domain rewrite instruction to the terminal device 300a, this need not be transmitted. That is, the terminal device 300a is the domain identifier 900 of the license 900A acquired from the terminal device 300b.
- Rewrite A 7 or terminal device 300a rewrites domain identifier 903A of license 900A obtained from terminal device 300b regardless of the presence or absence of the domain rewrite instruction.
- the terminal device 300a transmits the main identifier 903A even if the domain identifier 903A of the license 900A is different from the domain identifier of the domain to which the terminal device 300a belongs.
- the license 900 A can be used by rewriting. If the number of rewrites reaches the maximum number of 9 A, the license is not transmitted to a terminal device belonging to a domain having a domain identifier different from the domain identifier.
- the unauthorized distribution of license 900A can be restricted.
- the terminal device 300a is rewritten so that when the domain identifier 903A is rewritten, the rewrite number 906A is also added only once. May be rewritten to be subtracted only once.
- the initial value of the number of rewrites 9 0 6 A is the maximum number 9 0
- the number of rewrites is set equal to 5 A, and the number of rewrites 9 0 6 A is reduced to 0 When it reaches, rewriting of domain identifier 9 03 A becomes impossible.
- the terminal device 300a that has acquired the license 900A has rewritten the domain identifier 903A of the license 9 OOA and the number of rewrites 9600A.
- the terminal device 300b transmitting A may rewrite.
- the terminal device 300a or the terminal device 300b reached the maximum number 905A when the number of rewriting 906A reached the maximum number 905A. Then, the rewrite flag 904A may be rewritten. That is, the terminal device rewrites the content of the rewrite flag 904A from rewritable to impossible. As a result, the terminal device 300a or the terminal device 300b can check the rewrite flag 904A without comparing the number of rewrites 906A with the maximum number 905A, and can obtain the domain identifier. It is possible to determine whether or not rewriting of 93 A can be performed.
- the domain determination based on the domain identifier is performed after the domain determination based on the domain determination information is performed.
- the order of the two domain judgments is not limited to this. For example, when the SAC is established, if the domain determination based on the domain determination information is not performed and a license acquisition request message including the domain identifier is transmitted, the terminal device 300b performs the domain determination based on the domain identifier. After that, it is possible to make a domain judgment based on the domain judgment information.
- terminal device 300a transmitting a license acquisition request to terminal device 300b to acquiring a license has been described above.
- one domain identifier is set for the license, but two or more domain identifiers may be set.
- the information for specifying a domain has been described as a domain identifier.
- the domain identifier is set in the data format of the license.
- the license distribution server 200 distributes the license in association with the domain identifier and distributes the license in the terminal device 300.
- licenses may be managed for each domain identifier. In this case, the data format of the license does not have to have a domain identifier.
- the terminal device 300b determines whether or not the terminal device 300a can use the license, and if it determines that the license cannot be used, the terminal device 300b sends the license to the terminal device 300a. By not transmitting the license, use of the license by the terminal device 300a was prohibited. However, the terminal device 300b may transmit the license to the terminal device 300a without making the above determination, and may cause the terminal device 300a to determine whether or not the license can be used. In this case, the terminal device 300b sends the license including the domain identifier to the terminal device 300a, and the terminal device 300a is included in the license and the domain identifier of the domain to which the terminal device 300a belongs. It is determined whether or not the domain identifier matches.
- the terminal device 300a If they do not match, the terminal device 300a cannot use the license. In addition, the terminal device 300a stores that the license acquisition source was the terminal device 300b, and stores the domain identifier of the domain to which the terminal device 300a belongs and the domain included in the license. If the ID does not match, return the license to terminal device 300b and Is also good.
- the terminal device 300b does not transmit a license to another terminal device and makes the terminal device determine whether or not use is possible.
- the use was banned.
- the domain identifier of the domain to which the terminal device 300b belongs and the domain identifier included in the license are different. It is determined whether or not the license matches, and if they do not match, the license may be prohibited from being used by the user. This ensures that the use of licenses can be restricted.
- the terminal device, the server device, and the license distribution system including the same can appropriately restrict the use of a license in each terminal device. For example, reproduction and recording of content as a digital work can be performed. And the like using a license, a server device for distributing the license, and a license distribution system using the same.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Computer Hardware Design (AREA)
- Signal Processing (AREA)
- Data Mining & Analysis (AREA)
- Mathematical Physics (AREA)
- Technology Law (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 (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA002506227A CA2506227A1 (en) | 2003-02-28 | 2004-02-24 | Terminal device, server device, license distribution system using the same |
EP04714030A EP1603045A4 (en) | 2003-02-28 | 2004-02-24 | TERMINAL DEVICE, SERVER DEVICE, LICENSE DISTRIBUTION SYSTEM USING THE SAME |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2003052760 | 2003-02-28 | ||
JP2003-052760 | 2003-02-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004077301A1 true WO2004077301A1 (ja) | 2004-09-10 |
Family
ID=32923411
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/002122 WO2004077301A1 (ja) | 2003-02-28 | 2004-02-24 | 端末装置及びサーバ装置並びにそれらを用いたライセンス流通システム |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP1603045A4 (ja) |
KR (1) | KR20050113594A (ja) |
CN (1) | CN100347629C (ja) |
CA (1) | CA2506227A1 (ja) |
WO (1) | WO2004077301A1 (ja) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2006080291A1 (ja) * | 2005-01-25 | 2006-08-03 | Matsushita Electric Industrial Co., Ltd. | 情報配信装置、及び情報配信方法 |
WO2006115364A1 (en) * | 2005-04-25 | 2006-11-02 | Samsung Electronics Co., Ltd. | Method and apparatus for managing digital content |
JP2009140438A (ja) * | 2007-12-10 | 2009-06-25 | Fujitsu Ltd | 情報処理装置及びライセンス配信システム |
US8161296B2 (en) | 2005-04-25 | 2012-04-17 | Samsung Electronics Co., Ltd. | Method and apparatus for managing digital content |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
MX2007016347A (es) * | 2005-07-05 | 2008-03-05 | Koninkl Philips Electronics Nv | Metodo, sistema y dispositivos para proteccion de contenido digital. |
WO2009015607A1 (fr) * | 2007-07-31 | 2009-02-05 | Huawei Technologies Co., Ltd. | Procédé, système et dispositif assurant la gestion de domaine pour un dispositif utilisateur par un gestionnaire de domaine |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH11213553A (ja) * | 1998-01-28 | 1999-08-06 | Toshiba Corp | 契約管理装置および再生装置 |
JP2002169726A (ja) * | 2000-11-30 | 2002-06-14 | Sony Corp | 情報処理装置および方法、並びにプログラム格納媒体 |
JP2002297816A (ja) * | 2001-03-29 | 2002-10-11 | Sony Corp | 情報処理装置および方法、記録媒体、並びにプログラム |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7073063B2 (en) * | 1999-03-27 | 2006-07-04 | Microsoft Corporation | Binding a digital license to a portable device or the like in a digital rights management (DRM) system and checking out/checking in the digital license to/from the portable device or the like |
US7096268B1 (en) * | 1999-09-01 | 2006-08-22 | Matsushita Electric Industrial Co., Ltd. | Copyrighted data processing method and apparatus |
CA2373641C (en) * | 2000-03-09 | 2010-07-13 | Matsushita Electric Industrial Co., Ltd. | Management apparatus, editing apparatus, recording medium, method, and audio data playback management system including management apparatus, editing apparatus and recording medium |
KR20040015714A (ko) * | 2001-07-17 | 2004-02-19 | 마쯔시다덴기산교 가부시키가이샤 | 컨텐츠 이용장치와 네트워크 시스템, 및 라이센스 정보취득방법 |
-
2004
- 2004-02-24 WO PCT/JP2004/002122 patent/WO2004077301A1/ja active Application Filing
- 2004-02-24 CN CNB2004800015374A patent/CN100347629C/zh not_active Expired - Lifetime
- 2004-02-24 EP EP04714030A patent/EP1603045A4/en not_active Withdrawn
- 2004-02-24 CA CA002506227A patent/CA2506227A1/en not_active Abandoned
- 2004-02-24 KR KR1020057008439A patent/KR20050113594A/ko not_active Application Discontinuation
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH11213553A (ja) * | 1998-01-28 | 1999-08-06 | Toshiba Corp | 契約管理装置および再生装置 |
JP2002169726A (ja) * | 2000-11-30 | 2002-06-14 | Sony Corp | 情報処理装置および方法、並びにプログラム格納媒体 |
JP2002297816A (ja) * | 2001-03-29 | 2002-10-11 | Sony Corp | 情報処理装置および方法、記録媒体、並びにプログラム |
Non-Patent Citations (1)
Title |
---|
"IBM Response to DVB-CPT Call for Proposals for Content Protection & Copy Management: xCP Cluster Protocol", 19 October 2001 (2001-10-19), pages I - IV, 1 - 32, XP001148193, Retrieved from the Internet <URL:http://www.almaden.ibm.com/software/ds/ContentAssurance/papers/xCP_DVB.pdf> * |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2006080291A1 (ja) * | 2005-01-25 | 2006-08-03 | Matsushita Electric Industrial Co., Ltd. | 情報配信装置、及び情報配信方法 |
WO2006115364A1 (en) * | 2005-04-25 | 2006-11-02 | Samsung Electronics Co., Ltd. | Method and apparatus for managing digital content |
EP1875378A1 (en) * | 2005-04-25 | 2008-01-09 | Samsung Electronics Co., Ltd. | Method and apparatus for managing digital content |
US8161296B2 (en) | 2005-04-25 | 2012-04-17 | Samsung Electronics Co., Ltd. | Method and apparatus for managing digital content |
EP1875378A4 (en) * | 2005-04-25 | 2014-12-10 | Samsung Electronics Co Ltd | METHOD AND DEVICE FOR ADMINISTERING DIGITAL CONTENT |
JP2009140438A (ja) * | 2007-12-10 | 2009-06-25 | Fujitsu Ltd | 情報処理装置及びライセンス配信システム |
Also Published As
Publication number | Publication date |
---|---|
CN1717642A (zh) | 2006-01-04 |
EP1603045A4 (en) | 2009-01-21 |
CN100347629C (zh) | 2007-11-07 |
CA2506227A1 (en) | 2004-09-10 |
KR20050113594A (ko) | 2005-12-02 |
EP1603045A1 (en) | 2005-12-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9886687B2 (en) | Method and apparatus for digital rights management | |
JP4912406B2 (ja) | 第1プラットフォームから第2プラットフォームへのディジタルライセンスの移送 | |
JP4218451B2 (ja) | ライセンス管理システム、サーバ装置および端末装置 | |
KR100467929B1 (ko) | 디지털 컨텐츠의 보호 및 관리를 위한 시스템 | |
JP4750352B2 (ja) | デジタルコンテンツに対応するデジタルライセンスを取得する方法 | |
EP1460511B1 (en) | Reviewing cached user-group information in connection with issuing a digital rights management (DRM) license for content | |
EP1452942A2 (en) | Issuing a digital rights management (DRM) license for content based on cross-forest directory information | |
EP1378811A2 (en) | Systems and methods for issuing usage licenses for digital content and services | |
EP1686504A1 (en) | Flexible licensing architecture in content rights management systems | |
US20070288391A1 (en) | Apparatus, information processing apparatus, management method, and information processing method | |
WO2004063933A1 (ja) | コンテンツ利用又は管理のためのシステム、方法及びプログラム | |
KR20020064672A (ko) | 콘텐츠 이용 관리 시스템 및 콘텐츠 이용 관리 방법 | |
JP2000242604A (ja) | コンテンツ配布システム、端末装置および記録媒体 | |
KR100752511B1 (ko) | 디지털 핑거 프린팅을 이용한 디지털 콘텐츠 공급 시스템 | |
US20090199279A1 (en) | Method for content license migration without content or license reacquisition | |
JP2004302817A (ja) | ライセンス管理システム | |
JP4469631B2 (ja) | 端末装置、サーバ装置、ライセンス流通システム、ライセンス情報の取り扱い方法、およびプログラム | |
US20100077486A1 (en) | Method and apparatus for digital content management | |
WO2004077301A1 (ja) | 端末装置及びサーバ装置並びにそれらを用いたライセンス流通システム | |
US10445474B2 (en) | Controlling delivery of encrypted media assets | |
KR100585840B1 (ko) | Drm 컨텐츠 서비스 사용자 인증 방법 | |
JP2006195740A (ja) | 管理装置 | |
KR101054619B1 (ko) | 컨텐츠 재생 시스템 및 방법 | |
JP2004015753A (ja) | 情報配信システム、これに接続されるコンテンツ利用装置、これらを含む情報システム、およびプログラム | |
JP2005149002A (ja) | コンテンツ流通管理方法および装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
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: 2004714030 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020057008439 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2506227 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20048015374 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2069/CHENP/2005 Country of ref document: IN |
|
WWP | Wipo information: published in national office |
Ref document number: 1020057008439 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 2004714030 Country of ref document: EP |