JP2007199959A - Content use right management system, electronic ticket issuing system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a content use right according to safety of a user terminal. <P>SOLUTION: The user terminal 20 is a means making an issue request for an electronic ticket for use of a content to a ticket issuing server 10, and transmits level correspondence information corresponding to a security level of the user terminal 20 to the ticket issuing server 10 according to the request. The ticket issuing server 10 stores correspondence relation between the security level and the use right, receives the issue request for the electronic ticket and the level correspondence information according thereto from the user terminal 20, gets the use right corresponding to the security level corresponding to the level correspondence information, and provides the electronic ticket showing the gotten use right to the user terminal 20. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a technique for protecting the rights of digital contents, and more particularly to a technique for managing the issuance of electronic tickets.

  In recent years, with the development of computers, networks, and communication technologies, the use of digital contents (hereinafter simply referred to as “contents”) has increased rapidly, and the copying and distribution of contents has become extremely easy. For this reason, a system has been proposed in which content is protected by encryption and the like, and copyright protection and information leakage are prevented by issuing an electronic ticket (also called a license) to an authorized user.

  In these conventionally proposed methods, it is verified that the electronic ticket is correct on the computer that uses the content, and if it is correct (if it is not forged), the user can use the content within the scope of rights described in the electronic ticket. To provide.

  However, in the conventional system, issuance of electronic tickets is managed based on user qualification information. Also, the validity of the electronic ticket is verified in the use of the content. For this reason, the content is used with the same right regardless of the security level of the environment in which the electronic ticket is verified or the content is used. Thus, conventionally, the right to use content cannot be controlled according to the security level of the usage environment.

  Here, the usage rights include general conditions for permitting the use of content, such as those related to operations such as viewing rights, printing rights, and editing rights, as well as attributes such as the usage period, the number of usages, and the payment method (payment / buying each time). Point to. The usage right is also called a usage condition.

  For example, in the conventional system, detailed rights cannot be set in the following cases.

  While a user uses a desktop PC with an IC card reader at the company and uses the IC card token to authenticate the usage rights, the user uses a notebook PC without an IC card reader and uses software Assume that usage rights authentication is performed using a token. Here, although IC card tokens and software tokens have different resistances (security levels) to attacks, conventional systems do not consider security levels and issue electronic tickets with the same usage rights to both.

  In addition, when a token receives a content usage request from an application, the token determines whether or not to accept the usage request based on the presence or absence of an electronic ticket corresponding to the content and the usage right indicated on the electronic ticket. In some cases, the application can decrypt the content. The token is tamper resistant.

  Also, even if a PC has the same software token installed, the risk of theft and unauthorized use differs between a PC installed in a locked room and a PC placed in a place where anyone can enter and exit. Security level is different. However, even in such a case, in the conventional system, an electronic ticket having the same right is issued to the same user, and the right cannot be controlled by the security level.

  In addition, in the consumer electronic content distribution market where there are many companies, there are many cases where the provider of electronic content and the provider of tokens are different. In that case, a token distributed by a token provider that the content provider can trust (for example, a token distributor who evaluated the implementation method, etc.) and a token provider with a low reliability (using the same electronic ticket system) It was not possible to control ticket issuance according to the reliability (security level) of token distributors, such as changing the conditions of electronic tickets sold with tokens distributed by token distributors only.

  Recognizing powerful rights in an environment with a low security level raises the concern that the risk of content leakage will increase, but conventional systems have not been considered from such a viewpoint.

  As a conventional technique for managing the use of content by a user, the system disclosed in Patent Document 1 issues a right to use (license) of a right that can be used by a function according to the function of a device that uses the service. In this system, the right to use is limited depending on the function of the device to be used, but it is not considered what safety level the device has. Even devices having the same function may have different safety levels.

  In the system disclosed in Patent Document 2, a user and a plurality of machines are connected, and a license that can be used by a plurality of limited machines is issued. In this system, the machines that can use the content are limited, but the usage conditions are described in the license, the same usage conditions are applied, and the safety level of the machine is not considered.

  In the system of Patent Document 3, a group corresponding to the identifier of the user who requested the license is searched in the directory, and a license having a right corresponding to the group is issued to the user. However, in this system, the right indicated by the issued license depends on the attribute of the user and does not depend on the security level of the using device.

  In the system of Patent Document 4, usage condition information is included in an electronic ticket (license), so that flexible conditions can be set for rights authentication when using content. In this system, use conditions stored in advance are used, and selection of use conditions is not mentioned.

JP 2004-334356 A JP 2004-259280 A JP 2004-246900 A JP-A-10-093550

  The present invention solves at least one of the problems of the prior art.

  One aspect of the present invention is a content usage right management system that includes a user terminal that uses content, and an issue server that issues an electronic ticket for using the content to the user terminal. A requesting unit that issues an electronic ticket issuing request for use of content to the issuing server, and transmits level correspondence information corresponding to the security level of the user terminal to the issuing server in response to the request; The issuance server includes a usage right information storage unit that stores the correspondence between the security level and the usage rights, receives an electronic ticket issuance request from the user terminal and the corresponding level correspondence information, and corresponds to the level correspondence information. An electronic ticket indicating the usage right that is obtained from the usage right information storage unit, corresponding to the security level to be used Ticket providing unit for providing to the user terminal, comprises, providing a content usage rights management system.

  In another aspect of the present invention, a usage right information storage unit for storing a correspondence relationship between a security level and a usage right, an electronic ticket issuance request and a level correspondence information associated therewith are received from a user terminal, and the level correspondence information An electronic ticket issuing system is provided that includes a ticket providing unit that obtains a usage right corresponding to a security level corresponding to, from a usage right information storage unit and provides an electronic ticket indicating the obtained usage right to the user terminal.

  In yet another aspect of the present invention, the computer system receives a usage right information storage unit that stores a correspondence relationship between the security level and the usage right, receives an electronic ticket issue request from the user terminal, and level correspondence information associated therewith, Provides a program for functioning as a ticket providing unit that obtains a usage right corresponding to the security level corresponding to the level correspondence information from the usage right information storage unit and provides an electronic ticket indicating the obtained usage right to the user terminal. To do.

  In yet another aspect of the present invention, a computer is a content holding unit that holds content including usage right information for each security level, and an electronic ticket for using the content is obtained from the electronic ticket issuing system. The ticket acquisition unit, the level acquisition unit for obtaining the security level of the computer, and the use of the content using the electronic ticket corresponding to the content acquired by the ticket acquisition unit when the use of the content is requested A usage control unit that controls the usage right corresponding to the security level of the computer obtained by the level acquisition unit from information on usage rights for each security level included in the content, and the range of the obtained usage rights And a usage control unit that permits the use of the content. It provides a computer.

  In still another aspect of the present invention, the computer includes a content holding unit that holds content including usage right information for each security level, and a ticket for acquiring an electronic ticket for using the content from the electronic ticket issuing system. An acquisition unit, a level acquisition unit for determining the security level of the computer, and, when use of content is requested, the use of the content is controlled using an electronic ticket corresponding to the content acquired by the ticket acquisition unit A usage control unit that obtains a usage right corresponding to the security level of the computer obtained by the level acquisition unit from information on the usage right for each security level included in the content, and the range of the obtained usage right It functions as a usage control unit that permits the use of content. To provide a program for.

    In still another aspect of the present invention, there is provided a content usage right management system including a user terminal that uses content, and an issue server that issues an electronic ticket for using the content to the user terminal. Is a content holding unit for holding content including a content key ID for each security level, means for issuing an electronic ticket issuance request for use of content to the issuing server, and corresponds to the security level of the user terminal A requesting unit that transmits the content key ID to the issuing server in response to the request, and the issuing server stores a usage right information storage unit that stores a correspondence relationship between the content key ID and the usage right, The issue request and the accompanying content key ID are received, and the content key ID is supported Seeking use rights from the usage right information storage unit, the ticket providing unit which provides electronic ticket indicating the utilization right sought to that user terminal comprises, providing a content usage rights management system.

  In still another aspect of the present invention, a computer for using content, a content holding unit that holds content including a content key ID for each security level, and an electronic device for using the content to the issuing server A means for issuing a ticket issue request, wherein a request unit that transmits a content key ID corresponding to the security level of the computer to the issue server in response to the request, and the content key ID acquired in response to the issue request There is provided a computer including an acquisition unit that acquires a corresponding electronic ticket.

  In still another aspect of the present invention, the computer includes a content holding unit that holds content including a content key ID for each security level, and a unit that issues an electronic ticket issuance request for content use to the issuing server. A request unit that transmits a content key ID corresponding to the security level of the computer to the issuing server in response to the request, and an acquisition that acquires an electronic ticket corresponding to the content key ID acquired in response to the issuing request And a program for functioning.

  Hereinafter, embodiments of the present invention (hereinafter referred to as “embodiments”) will be described with reference to the drawings.

  First, an example of the system of the embodiment will be described with reference to FIG. In this system, a ticket issuing server 10, a user terminal 20 such as a personal computer, and a content providing server 30 are connected to a network 40 such as a LAN (local area network) or the Internet.

  The ticket issuing server 10 issues an electronic ticket in response to a request from the user terminal 20. The electronic ticket is data including key information for releasing usage restrictions on the content provided by the content providing server 30 to the user terminal 20, and is also called a license. When the content is encapsulated by a technique such as encryption, the electronic ticket includes a key for decrypting the encapsulated content or information necessary for generating the key. Further, the electronic ticket may include information on the right to use the content (that is, usage conditions). The content usage rights include, for example, operations on the content permitted to the user (for example, “permitting browsing only”, “permitting viewing and writing”, etc.), the number of times the content is permitted to be used in the electronic ticket, or The expiration date of the electronic ticket can be exemplified. Of course, it may be a combination of two or more of them.

  The ticket issuing server 10 receives an electronic ticket issuance request from the user terminal 20, determines whether or not to issue an electronic ticket in response to the request, and determines that the electronic ticket is to be issued. It is issued to the terminal 20. If it is determined that it cannot be issued, error information determined in advance indicating that it cannot be issued is returned to the user terminal 20.

  In the case of a system that sells content or an electronic ticket, it is determined whether or not an electronic ticket is issued in response to a request, for example, whether or not a user operating the user terminal 20 has settled a fee for using the content. Based on. In the case of a system that provides content to a limited user registered in advance according to the authority of the user, such as when providing an in-house document to the user, for example, an access control list (ACL) is provided. Based on the registered user authority information, it is determined whether or not the requesting electronic ticket may be issued to the requesting user, or the usage right indicated in the issued electronic ticket is determined.

  Next, a configuration example of the user terminal 20 will be described with reference to FIG. The example of FIG. 2 is an example in which an access ticket system disclosed in Japanese Patent Application Laid-Open No. 10-247905 or Japanese Patent Application Laid-Open No. 11-031105 by the applicant is adopted as a content usage right management system using an electronic ticket. is there. As shown in FIG. 2, the user terminal 20 includes a content handling program 210 and a token (ticket management unit) 220.

  The token 220 is a functional module that manages a ticket (license) of each capsule installed in the user terminal 20. This module is implemented as tamper-resistant software or hardware. The token 220 includes a control unit 222, a token ID holding unit 224, a ticket holding unit 226, and a key holding unit 228. The token ID holding unit 224 stores identification information (token ID) given to the token 220 itself. The ticket holding unit 226 holds electronic ticket (license) data for using the encapsulated content (hereinafter simply referred to as “capsule”) 230. Each ticket held by the ticket holding unit 226 can be searched by the key ID. Although only one capsule 230 is shown in FIG. 2, a plurality of capsules 230 can be stored in the user terminal 20. The key holding unit 228 holds an individual key unique to the token 220. In response to a request from the content handling program 210, the control unit 222 determines whether or not the capsule 230 can be used, and performs processing according to the determination result. For example, the control unit 222 determines whether the electronic ticket corresponding to the target capsule 230 is in the ticket holding unit 226. If there is an electronic ticket, the decryption key for decrypting the encrypted content key 236 is obtained by combining the information contained in the electronic ticket and the individual key information in the key holding unit 228, The content key is decrypted using this, and the capsule 230 is decrypted using the decrypted content key. If there is no electronic ticket corresponding to the capsule 230, error processing is performed. In the case of this system, the token ID and the individual key information of the user terminal 20 are registered in advance in the ticket issuing server 10. The ticket issuing server 10 issues an appropriate ticket corresponding to the token 220 of the user terminal 20 by using these pieces of information.

  The content handling program 210 is a program that provides a predetermined service to the user by opening the encapsulated content, such as a viewer for browsing the content or editing software for editing the content. .

  The capsule 230 is encapsulated content provided from the content providing server 30 to the user terminal 20. The content is data or programs, and there are various contents such as data such as image data, video data, document data, music data, and programs such as business applications and game programs. The capsule 230 has an encrypted content body 232, a key ID 234, and an encrypted content key 236. The encrypted content body 232 is a content body to be provided to the user, and is encrypted with a content key. The encrypted content key 234 is obtained by encrypting a content key for decrypting the encrypted content main body 232, and the key ID 236 is an ID for specifying a public key obtained by encrypting the content key. .

  The schematic configuration of the system has been described above. In the present embodiment, the right to use the capsule 230 at the user terminal 20 is controlled according to the security level of the user terminal 20. An example of this usage right control method will be described below.

  First, the first method will be described with reference to FIG. In this method, the type of token 220 provided in the user terminal 20 is regarded as the security level, and the usage rights given to the user are controlled according to the type. The type of the token 220 is, for example, a hardware token such as an IC card or a software token. In general, hardware tokens are more secure than software tokens because of the limited physical interface. Therefore, in this method, the user terminal 20 provided with the software token is allowed only a smaller / weaker right than that provided with the hardware token, thereby reducing the risk when the security is broken.

  In the example of FIG. 3, the ticket issuing server 10 includes a key ID-usage right table 110 and a token-usage right table 120. The key ID-use right table 110 is a table in which a key ID and a use right corresponding to the key ID are registered. As described above, the key ID is identification information of the public key obtained by encrypting the content key, and can also be regarded as identification information of the capsule 230. As the usage right corresponding to the key ID, the operation right for the capsule 230 (content) is illustrated in the figure. For example, a usage right “reading and printing is possible” is registered in the content of the key ID 001, and a usage right “reading is possible only” is registered in the content of the key ID 002.

  On the other hand, a token ID and a corresponding usage right are registered in the token-use right table 120. The token ID is unique identification information assigned to the tokens 220A, 220B,... Mounted on the user terminals 20A, 20B,. In this table 120, usage rights (operation authority information in the illustrated example) are registered in association with token IDs.

  The ticket issuing server 10 uses these tables 110 and 120 to determine whether or not to issue an electronic ticket to the user, and if so, the contents of the usage right incorporated in the electronic ticket. The ticket issuing server 10 prioritizes the latter of the tables 110 and 120 for this determination. That is, if the entry of the token ID included in the issue request from the user terminal is in the table 120, the ticket issuing server 10 issues an electronic ticket indicating the right to use the entry. If there is no entry corresponding to the table 120, the ticket issuing server 10 checks the table 110 and searches for an entry corresponding to the key ID included in the issue request, and if there is, issues an electronic ticket indicating the right to use the entry. If there is no corresponding entry in both tables, the ticket issuing server 10 cancels the issuance of the electronic ticket and makes an error.

  The user terminal 20A includes a hardware token 220A as a token for managing an electronic ticket. The ID of this token is 100. A software token 220B is installed in the user terminal 20B, and its token ID is 101. Assume that these user terminals 20A and 20B have the same capsule 230 with a key ID of 001.

  In the user terminal 20A, when the user tries to open the capsule 230, the content handling program 210 (see FIG. 2) checks whether there is an electronic ticket for the content 230 in the hardware token 220A. If there is, the capsule 230 is opened using the electronic ticket. If not, the content handling program 210 sends a ticket issuance request 300A indicating the token ID 100 of the hardware token 220A and the key ID 001 of the capsule 230 to the ticket issuance server 10. Upon receiving this request, the ticket issuing server 10 searches the token-usage right table 120 for an entry for the token ID indicated in the request. In the example of FIG. 3, a usage right “viewing and printing is permitted” is permitted for the token ID. The ticket issuing server 10 provides an electronic ticket 310A including the usage right to the user terminal 20A.

  Note that the ticket issuing server 10 creates the electronic ticket 310A including the decryption information considering the individual key information (described above) of the user terminal 20A corresponding to the token ID. Even using the electronic ticket 310A, the capsule 230 cannot be decrypted.

  In the user terminal 20A that has received the electronic ticket 310A, the content handling program 210 uses the electronic ticket 310A and the token 220 to verify whether the electronic ticket 310A is valid. Opens the capsule 230 and allows the user to use the content in the capsule 230 with the usage right indicated in the electronic ticket 310A.

  When an electronic ticket issue request 300B for the capsule 230 with the same key ID is sent from the user terminal 20B to the ticket issue server 10, the ticket issue server 10 searches for an entry corresponding to the token ID 101 included in the request 300B. . Since the usage right of the entry is known as “browsing only”, the electronic ticket 310B in which the usage right of “browsing only” is set is provided to the user terminal 20B.

  As described above, in the embodiment of FIG. 3, the token ID of the token 220 provided in the user terminal 20 is used as information indicating the security level of the user terminal 20. The security level of the token 220 is an attribute of the token itself. Further, the token ID is uniquely assigned to the token 220. Further, what usage rights are assigned to the security level of the token can be determined in advance according to the security policy of the system. Therefore, the usage right corresponding to the security level of the token 220 can be registered in advance in the ticket issuing server 10 in association with the token ID of the token 220.

  The correspondence relationship between the token ID and the usage right is registered in the ticket issuing server 10, for example, when the individual token 220 is manufactured by the manufacturer.

  As another method, for example, in the secure registration procedure when the individual key information of the token 220 installed in the user terminal 20 is registered in the ticket issuing server 10 in association with the token ID, the token 220 is registered. Information indicating whether the token is a hardware token or a software token (a kind of security level) may also be sent to the ticket issuing server 10 side. In this case, based on this information, the ticket issuing server 10 registers the usage right corresponding to the type in the token-usage right table 120 in association with the token ID.

  In the example of FIG. 3, the token-usage right table 120 is prioritized over the key ID-usage right table 110, but instead, the right to use is obtained based on the tables 110 and 120, and the use right of both of them is determined. Only the common part right may be set in the electronic ticket. That is, for example, when one is “viewable only” and the other is “viewable and printable”, an electronic ticket “readable only” is issued. In addition, when the usage right is an effective period, an electronic ticket is issued with the effective period determined from the key ID and the effective period determined from the token ID as the effective period. Moreover, you may make it use the one with a narrower right among the usage rights of both. For example, in the case where the usage right item is numerical such as the number of times of use, the number of times of use obtained from the key ID is compared with that obtained from the token ID, and the one with the narrower right is adopted. .

  Next, a second method of usage right control will be described with reference to FIG. In FIG. 4, elements that are the same as or similar to the elements shown in FIG.

  In this example, the user terminal 20A, 20B includes the security level information of the user terminal 20A or 20B in addition to the token ID and key ID in the issue request 320A or 320B sent to the ticket issuing server 10. In this example, information on whether the token 220 incorporated in the user terminal 20A or 20B is the hardware token 220A or the software token 220B is used as the security level information.

  The ticket issuing server 10 includes a usage right table 130. In the usage right table 130, for each combination of a key ID (that is, a content ID) and a security level, a usage right corresponding to the combination is registered. For example, when the key ID is 001 and the security level is an H / W (hardware) token, the right to use “viewable and printable” is given.

  In this example, an electronic ticket 310A having a usage right “viewable and printable” is provided for the user terminal 20A whose security level is a hardware token, and for the user terminal 20B whose security level is a software token. In this case, an electronic ticket 310B having a usage right “reading only” is provided.

  In the example of FIG. 3 described above, the usage right provided to the user terminal 20A or 20B is determined depending on the token ID of the user terminal 20A or 20B regardless of the target content. On the other hand, in the example of FIG. 4, the usage rights given to the user terminals of each security level can be made different for each content.

  Next, a third method of usage right control will be described with reference to FIG. 5, elements that are the same as or similar to the elements shown in FIG.

  In this example, in response to the issue request 330A or 330B sent from the user terminal 20A or 20B to the ticket issuing server 10, in addition to the token ID and key ID, the user ID of the user who issues the request, and the security of the user terminal 20A or 20B Include level information. The user ID can be acquired when the user logs in to the user terminal 20A or 20B, or when the user logs in to the ticket issuing server 10 or another management server on the network. In this example, information on whether the token is a hardware token or a software token is used as the security level.

  In the usage right table 140 of the ticket issuing server 10, for each combination of a key ID (that is, a content ID), a user ID, and a security level, a usage right corresponding to the combination is registered. For example, when the key ID is 001, the user ID is 201, and the security level is an H / W (hardware) token, a usage right “viewable and printable” is given. On the other hand, even when the same key ID is 001 and the security level is H / W token, if the user ID is 202, the usage right given to the user is “view only”.

  In this example, even when an electronic ticket for the same capsule 230 is requested from the same user terminal 20A, when the user with the user ID 201 makes a request, the electronic ticket 310A having the usage right “viewable and printable” is displayed. In response to a request from the user ID 202, an electronic ticket 310B having the right to use “only browsing” is provided.

  In the example of FIG. 4 described above, the usage rights given to the user terminals of each security level can be varied for each content. However, in the example of FIG. 5, it can be varied for each user.

  In the example of FIG. 5, the so-called three-dimensional usage right table 140 using the key ID, the user ID, and the security level as a key is used, but the structure of the usage right table 140 that the ticket issuing server 10 has is the same. It will be clear that it is not limited. For example, two tables may be provided for each key ID (that is, for each content): a table in which usage rights are registered for each user ID, and a table in which usage rights are registered for each security level. In this case, the ticket issuing server 10 obtains two tables corresponding to the key ID included in the issuance request 330A or 330B, and obtains the usage rights corresponding to the user ID and token ID included in the request from each table. Issue an electronic ticket that shows the common part of both or the narrower right of both.

  Next, the fourth and fifth methods of usage right control will be described with reference to FIGS. In the first to third methods described above, the right to use according to the security level of the user terminal 20 is determined on the ticket issuing server 10 side. On the other hand, in the fourth and fifth methods described below, the user terminal 20 performs the determination. Accordingly, the ticket issuing server 10 itself can be the same as that of the prior art.

  First, the fourth method will be described with reference to FIGS. 6 and 7. FIG. 6 is a diagram showing a configuration of the user terminal 20 in this method, and FIG. 7 is a diagram showing data exchange between the user terminal 20 and the ticket issuing server 10 in this method. In FIG. 6, elements that are the same as or similar to the elements shown in FIG. In FIG. 7, the same or similar elements as those shown in FIG.

  In this method, the capsule 230 is provided with level / usage right correspondence information 238. The level / use right correspondence information 238 is information indicating the correspondence between the security level and the use right. In the example shown in FIG. 7, the usage right “viewing and printing is possible” is included in the security level of H / W (hardware token), and “browsing” is included in the security level of S / W (software token). The right to use is only associated with each other.

  As shown in FIG. 7, in this fourth method, the issuance requests 300A and 300B issued by the user terminals 20A and 20B include a token ID and a key ID. Upon receiving this request, the ticket issuing server 10 refers to the key ID-usage right table 110 and issues an electronic ticket 310A corresponding to the key ID. That is, in this example, the electronic ticket 310A indicating the same usage right “browsing and printing is possible” is given to the user terminal 20A and the user terminal 20B.

  In the user terminal 20A that has received the electronic ticket 310A, when the use of the capsule 230a is instructed, the content handling program 210 refers to the level / usage right correspondence information 238 of the capsule 230a, and the security level of the user terminal 20A, that is, H The user knows that the usage right corresponding to the / W token is “readable and printable”. Then, the use of the capsule 230a from the user is restricted according to the common right of the use right obtained from the level / use right correspondence information 238 and the use right shown in the electronic ticket 310A or the right of the narrower of both. In the case of the user terminal 20A, the user is allowed to both view and print. On the other hand, in the case of the user terminal 20B, the usage right obtained from the level / usage right correspondence information 238 is “reading is only possible”. Therefore, when combined with the usage right of the electronic ticket 310A, the user is allowed to only browse. .

  The content handling program 210 can obtain the security level of the user terminal 20 by making an inquiry to the token 220. In this case, each token 220 may be given information on the security level at the time of manufacturing the token. Also, if the token 220 is a hardware token or a software token, it can be identified by inquiring the operating system or the like.

  In the fourth method, the ticket issuing server 10 can be the same as the conventional one. Further, since the capsule 230a has the level / usage right correspondence information 238, the content provider can set what kind of usage right is given to the terminal of what security level. You don't have to be directly involved in it.

  Next, a fifth method of usage right control will be described with reference to FIGS. FIG. 8 is a diagram showing a configuration of the user terminal 20 in this method, and FIG. 9 is a diagram showing data exchange between the user terminal 20 and the ticket issuing server 10 in this method. In FIG. 8, elements that are the same as or similar to the elements shown in FIG. In FIG. 9, the same or similar elements as those shown in FIG.

  In this method, the capsule 230 is provided with level / key ID correspondence information 235 instead of having a single key ID 234 (see FIG. 2). The level / key correspondence information 235 is information indicating the correspondence between the security level and the key ID. In the example shown in FIG. 9, a key ID 001 is associated with a security level of H / W (hardware token), and a key ID 002 is associated with a security level of S / W (software token).

  That is, in this method, the same content is regarded as different for each security level, and different key IDs are given. In the key ID-usage right table 110 of the ticket issuing server 10, the right to use corresponding to each security level is registered for each of a plurality of key IDs for the same content. The same public key may be associated with a plurality of key IDs for the same content, or different public keys may be associated.

  As shown in FIG. 9, in the fifth method, the issue requests 300A and 300C issued by the user terminals 20A and 20B include a token ID and a key ID. However, the difference from the case of FIG. 3 is that the key ID values are different between the issuance requests 300A and 300C despite the electronic ticket issuance request for the same capsule 230B. That is, the issue request 300A includes the key ID 001 corresponding to the security level “hardware token” of the user terminal 20A, whereas the issue request 300C corresponds to the security level “software token” of the user terminal 20B. Key ID002 is included.

  Upon receiving the issue request 300A or 300C, the ticket issue server 10 refers to the key ID-usage right table 110 and issues an electronic ticket 310A or 310B corresponding to the key ID included in the request. That is, in this example, the electronic ticket 310A indicating the usage right “reading and printing is possible” corresponding to the key ID 001 is given to the user terminal 20A, and the “viewing only” usage corresponding to the key ID 002 is given to the user terminal 20B. An electronic ticket 310B indicating the right is given.

  As described above, also in the fifth method, it is possible to control the content usage right given to the user according to the security level of the user terminal 20A or 20B.

  Although the embodiment of the present invention has been described above, the above description is merely an example, and various modifications are possible within the scope of the present invention.

  For example, in the above example, the operation authority (or operation restriction) for the content such as “browsing and printing is possible” is exemplified as the usage right to be controlled. However, the usage right is not limited to this. It will be apparent to those skilled in the art that other rights items such as the number of times can be similarly controlled. In addition, if the security level is below a certain threshold, payment of the purchase price is requested before the electronic ticket is issued, and if the security level is higher than the threshold, postpayment is permitted. It may be determined according to

  In the above example, the security level of the user terminal 20 is exemplified based on the distinction between the token 220 installed in the terminal 20 and whether it is a hardware token or a software token. However, as the security level for the token 220, leveling based on distinction other than hardware or software is also conceivable.

  For example, a security level can be assigned to a distributor who distributes the token 220 (such as a hardware token manufacturer, a software token vendor, or a vendor that issues tokens received from them). That is, for example, when token distributors form a consortium regarding token standards and operations, tokens distributed by distributors belonging to the consortium should be assigned a higher security level than tokens distributed by other third-party vendors. Can do. In this case, the ticket issuing server 10 or the user terminal 20 can identify from which distributor the token is based on the token ID of the token 220. Further, the distributor's token 220 belonging to the consortium may have information indicating that fact or information on the security level corresponding to the consortium.

  Further, when registering the token 220 of the user terminal 20 in the ticket issuing server 10, the operator of the issuing server 10 may determine the security level of the user terminal 20. For example, the security level may be determined by the owner or administrator of the user terminal 20 based on the matters to be reported on the ticket issuing server 10 side. For example, the type of the user terminal 20 (for example, whether it is a desktop PC or a notebook PC), an installation location (whether it is installed in a secure location such as a locked room, or the like) Whether it is installed or carried), whether or not the user terminal 20 is allowed to be taken out, and the facts and arrangements regarding the security management of the user terminal 20 are reported to the owner of the user terminal 20; Based on this, the security level of the user terminal 20 may be determined. The determined security level may be registered in the token 220 or reflected in the token ID-usage right table 120.

  Further, the conventional method of determining the usage right to be given to the user based on the electronic ticket price settlement or the access control list can be combined with the method of the present embodiment in which the usage right is determined based on the security level of the user terminal 20. In this case, for example, the common part of the usage right obtained by the conventional method and the usage right obtained based on the security level, or the narrower usage right of both may be set in the electronic ticket.

  In the above, an access ticket type content usage right management system has been described as an example. However, the system of the present invention for controlling usage rights according to the security level of the user terminal 20 will be apparent to those skilled in the art. In addition, the present invention can be similarly applied to a content usage right management system other than the access ticket method.

  In the above example, the token is managed by the token in the above example. However, if the electronic ticket cannot be tampered with or the content cannot be decrypted correctly after tampering, the token is managed outside the token. You may make it have a ticket holding part.

  In the above example, the token has a control unit that determines whether it can be used and performs processing according to the determination result. However, the control unit may be configured to have a content handling program and a token separately. Good. For example, the content handling program may have a portion for generating data for proof of usage right inside the token, verifying the data for proof, and performing decryption of content and usage control. As a result, even when a token is configured with an IC card or the like having a low processing speed, processing at the time of using the content can be accelerated.

  In the above example, the content handling program 210 opens the capsule 230 and performs processing for browsing and editing the capsule 230. However, in the case of an application program in which the content (capsule 230) itself is encapsulated, Such a content handling program 210 is not necessarily required.

  The ticket issuing server 10 described above is typically realized by executing a program describing the function or processing content of each element described above on a general-purpose computer. As shown in FIG. 10, the computer has a circuit in which a CPU (Central Processing Unit) 40, a memory (primary storage) 42, various I / O (input / output) interfaces 44, and the like are connected via a bus 46, as shown in FIG. It has a configuration. Further, a hard disk drive 48, a disk drive 50 for reading portable non-volatile recording media of various standards such as a CD, a DVD, and a flash memory are connected to the bus 46 via, for example, an I / O interface 44. . Such a drive 48 or 50 functions as an external storage device for the memory. A program in which the processing contents of the embodiment are described is stored in a fixed storage device such as the hard disk drive 48 via a recording medium such as a CD or DVD or via a network, and is installed in a computer. The program stored in the fixed storage device is read into the memory and executed by the CPU, whereby the processing of the embodiment is realized. Similarly, the user terminal 20 can be realized by installing a hardware or software token on a general-purpose computer and further installing the content handling program 210 described above.

It is a figure which shows schematic structure of the system of embodiment. It is a figure which shows an example of a structure of a user terminal. It is a figure for demonstrating an example of the usage right control system of a content. It is a figure for demonstrating another example of the usage right control system of a content. It is a figure for demonstrating another example of the usage right control system of a content. It is a figure which shows another example of a structure of a user terminal. It is a figure for demonstrating another example of the usage right control system of a content. It is a figure which shows another example of a structure of a user terminal. It is a figure for demonstrating another example of the usage right control system of a content. It is a figure which shows an example of the hardware constitutions of the general purpose computer which can be utilized as a ticket issuing server or a user terminal.

Explanation of symbols

  10 ticket issuing server, 20 user terminal, 30 content providing server, 40 network, 210 content handling program, 220 token, 222 control unit, 224 token ID holding unit, 226 ticket holding unit, 228 key holding unit, 230 capsule, 232 encryption Content body encrypted, 234 Key ID, 236 Encrypted content key.

Claims (11)

A content usage right management system including a user terminal that uses content, and an issue server that issues an electronic ticket for using the content to the user terminal,
User terminal
A request unit that issues an electronic ticket issue request for use of content to the issue server, and transmits level correspondence information corresponding to the security level of the user terminal to the issue server in response to the request,
With
The issuing server
A usage right information storage unit for storing the correspondence between security levels and usage rights;
An electronic ticket that receives a request for issuing an electronic ticket from the user terminal and accompanying level correspondence information, obtains a usage right corresponding to the security level corresponding to the level correspondence information from the usage right information storage unit, and indicates the obtained usage right Providing a ticket to the user terminal,
A content usage right management system. The content usage right management system according to claim 1,
The user terminal includes a token that performs right-of-use authentication using an electronic ticket received from the issuing server,
The level correspondence information is identification information of the token.
Content usage right management system characterized by this. The content usage right management system according to claim 1,
The usage right information storage unit stores the correspondence between the security level and the usage right for each content,
The ticket providing unit obtains the usage right indicated by the electronic ticket issued to the user terminal based on the correspondence between the security level and the usage right for the requested content;
Content usage right management system characterized by this. The content usage right management system according to claim 1,
The usage right information storage unit stores the correspondence between the security level and the usage right for each content and for each user,
The ticket providing unit obtains the usage right indicated by the electronic ticket issued to the user terminal based on the correspondence between the security level and the usage right corresponding to the combination of the requested content and the requesting user;
Content usage right management system characterized by this. A usage right information storage unit for storing a correspondence relationship between security levels and usage rights;
An electronic ticket that receives a request for issuing an electronic ticket from the user terminal and the level correspondence information associated therewith, obtains a usage right corresponding to the security level corresponding to the level correspondence information from the usage right information storage unit, and indicates the obtained usage right Providing a ticket to the user terminal,
An electronic ticket issuing system comprising: Computer system
A usage right information storage unit for storing the correspondence between security levels and usage rights;
An electronic ticket that receives a request for issuing an electronic ticket from the user terminal and the level correspondence information associated therewith, obtains a usage right corresponding to the security level corresponding to the level correspondence information from the usage right information storage unit, and indicates the obtained usage right Providing a ticket to the user terminal,
Program to function as. A computer,
A content holding unit for holding content including usage right information for each security level;
A ticket acquisition unit for acquiring an electronic ticket for use of content from the electronic ticket issuing system;
A level acquisition unit for determining the security level of the computer;
A use control unit that controls the use of the content by using an electronic ticket corresponding to the content acquired by the ticket acquisition unit when use of the content is requested, and for each security level included in the content From a usage right information, a usage control unit that obtains a usage right corresponding to the security level of the computer obtained by the level acquisition unit, and permits the use of the content within the range of the obtained usage right;
A computer comprising: Computer
A content holding unit for holding content including usage right information for each security level;
A ticket acquisition unit for acquiring an electronic ticket for use of content from the electronic ticket issuing system;
A level acquisition unit for determining the security level of the computer;
A use control unit that controls the use of the content by using an electronic ticket corresponding to the content acquired by the ticket acquisition unit when use of the content is requested, and for each security level included in the content From a usage right information, a usage control unit that obtains a usage right corresponding to the security level of the computer obtained by the level acquisition unit, and permits the use of the content within the range of the obtained usage right;
Program to make it function. A content usage right management system including a user terminal that uses content, and an issue server that issues an electronic ticket for using the content to the user terminal,
User terminal
A content holding unit for holding content including a content key ID for each security level;
A requesting unit that issues an electronic ticket for requesting use of content to the issuing server, and transmits a content key ID corresponding to the security level of the user terminal to the issuing server in response to the request,
With
The issuing server
A usage right information storage unit for storing the correspondence between the content key ID and the usage right;
An electronic ticket issuance request and a content key ID associated therewith are received from the user terminal, a usage right corresponding to the content key ID is obtained from the usage right information storage unit, and an electronic ticket indicating the obtained usage right is sent to the user terminal. Ticket offer department to provide,
A content usage right management system. A computer for using content,
A content holding unit for holding content including a content key ID for each security level;
A means for making an issue request for an electronic ticket for use of content to an issue server, a request unit that transmits a content key ID corresponding to the security level of the computer to the issue server in response to the request;
An acquisition unit for acquiring an electronic ticket corresponding to the content key ID acquired in response to the issue request;
A computer comprising: Computer
A content holding unit for holding content including a content key ID for each security level;
A means for making an issue request for an electronic ticket for use of content to an issue server, a request unit that transmits a content key ID corresponding to the security level of the computer to the issue server in response to the request;
An acquisition unit for acquiring an electronic ticket corresponding to the content key ID acquired in response to the issue request;
Program to make it function.

Images