JP2006323720A - Electronic ticket issuing device and electronic ticket issue control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable the suppression of double issue of an electronic ticket. <P>SOLUTION: When an issuing request for an electronic ticket for contents comes from a user terminal 20, an inquiry part 14 of the ticket issuing device 10 inquires the user terminal 20 whether it has an electronic ticket corresponding to the request or not. The user terminal 20 replies whether it has the corresponding electronic ticket or not responding to the inquiry. When the reply shows that it has not the corresponding electronic ticket, a judgement part 16 of the ticket issuing device 10 judges that the issue of the electronic ticket is necessary to the issue request; and when the reply shows that it has the corresponding electronic ticket, the judgement part 16 of the ticket issuing device judges that the issue is unnecessary. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a management technique for protecting digital content from unauthorized use, and more particularly to management of issuance of an electronic ticket that enables the use of content.

  In recent years, various contents such as images, videos, documents, sounds, game programs, and other software have been provided to users from various content providers. In providing these contents, DRM (Digital Rights Management) technology is used in order to protect the rights of the contents provider such as copyrights.

  One of the DRM technologies is a system using an electronic ticket. In this system, content is distributed to users in a state where usage restrictions are imposed by encryption or the like. When the user uses the content, the user separately obtains an electronic ticket including information necessary for canceling the use restriction. The electronic ticket is sometimes called license information or usage right information.

  In such a system, there are cases where the user needs to reacquire the electronic ticket, for example, when the acquired electronic ticket is destroyed or invalidated. Patent Documents 1 to 3 disclose a mechanism for enabling a user terminal to reacquire an electronic ticket from a ticket issuing device via a network.

JP 2004-056620 A JP 2004-032220 A JP 2004-295875 A

  The user terminal makes a request for reacquisition of the electronic ticket to the ticket issuing device not only when the electronic ticket is destroyed or invalidated as described above.

  For example, a content download program installed in a user terminal may be implemented so that an electronic ticket acquisition request is automatically made when content is downloaded. In addition, there is a case where software that handles usage-restricted content is implemented so as to automatically make an electronic ticket acquisition request when the user is instructed to use the content. In these cases, an electronic ticket acquisition request is issued even when an electronic ticket corresponding to the content is in the user terminal.

  In some cases, for example, the use authority granted to the user by the content provider side may be expanded, for example, by allowing only print output to be permitted until browsing with a viewer. In some cases, the provision of the provision authority is performed without notifying the user who has already acquired the electronic ticket. Therefore, in order to cope with this, the content handling software on the user terminal sends the content to the user terminal. Even if there is an electronic ticket, the specification may be such that the electronic ticket is acquired again, for example, when an instruction to use the content is received from the user.

  As described above, an electronic ticket acquisition request for the same target content as the electronic ticket on the user terminal may be sent to the ticket issuing device for the convenience of software installed on the user terminal side.

  In any of the methods disclosed in Patent Documents 1 to 3, since the ticket issuing device issues an electronic ticket when there is an electronic ticket acquisition request from the user terminal, there is an electronic ticket with the same content in the user terminal. An electronic ticket is also issued. Such overlapping issue of electronic tickets wastes computing resources and communication lines of both the ticket issuing device and the user terminal, and increases the management cost of issued electronic tickets.

  The present invention is a program for causing a computer system to function as an electronic ticket issuing device that issues an electronic ticket for releasing usage restrictions on content, and the computer system is configured to transmit an electronic ticket for content from a user terminal. A determination unit that determines whether or not the terminal of the user holds an electronic ticket for the content when receiving the issue request, and determines that it is necessary to issue an electronic ticket for the issue request if not held; A program for causing an electronic ticket corresponding to the issue request to be issued to the user terminal when the determination unit determines that an issue is necessary is provided.

  The best mode for carrying out the present invention (hereinafter referred to as “embodiment”) will be described below with reference to the drawings.

  In the following description, content whose use is restricted by digital technology is called encapsulated content. Usage restrictions include prohibition / restriction of the usage itself, and each operation that can be performed on the content (for example, in the case of a document, viewing (display), printing, editing, copying, transfer to another person, etc.) There are also bans and restrictions. The content of usage restrictions is usually determined by the content provider. Even for the same content, the content of usage restrictions (usage authority from the user's perspective) may change for each user who uses the same content. In some cases, the contents of usage restrictions are determined according to user attributes (for example, age, gender, job title, affiliation group, whether or not a fee has been paid to a predetermined billing system, etc.).

  The basis of usage restrictions is content encryption. The encapsulated content includes encrypted content and ID information (not the key itself) for specifying a key necessary for releasing (decrypting) the encryption. When individual operations on content are restricted, data describing operation items to be restricted is incorporated into the encapsulated content. The restriction of each operation is realized by controlling software that opens content on the user terminal, for example, based on the description.

  The electronic ticket is digital data used for releasing the usage restriction on the encapsulated content, and is also called license information (or data), usage right data, or the like. The electronic ticket includes key data for decrypting the encrypted content in the encapsulated content. The electronic ticket does not need to include the decryption key itself necessary for decryption. The key data included in the electronic ticket is, for example, a part of the decryption key (this is combined with, for example, other information held in the user terminal to form the decryption key) or the decryption key at the user terminal Data required for the operation [For example, the key generation algorithm on the user terminal side (this algorithm may be based on information held by the user terminal may be used as a parameter) to generate the decryption key Such as]. Further, in the case of a configuration that allows the use of individual operation items to be restricted, information indicating the operation item for which the use restriction is released is described in the electronic ticket. In addition, the electronic ticket incorporates, as necessary, a description indicating a procedure such as a ticket issuance date and time, an expiration date or an effective period, a use frequency limit, and a billing payment required for use.

  The encapsulated content and the electronic ticket have been described above. Next, a first embodiment of the present invention will be described with reference to FIG.

  In FIG. 1, a ticket issuing device 10 is connected to a network 30 such as the Internet, and provides an electronic ticket issuing service to the user terminal 20 operated by the user via the network 30. The ticket issuing device 10 includes an authority information storage unit 12, an inquiry unit 14, a determination unit 16, and an issue processing unit 18.

  The authority information storage unit 12 stores usage authority information that defines the usage authority content of content that can be given to each user at a local point. FIG. 2 shows an example of a record structure of usage authority information stored in the authority information storage unit 12. This example is an example in the case where the usage authority content for the content is defined for each user. In this example, one record includes a content ID 110, a user ID 120, an authority content 130, a valid period 140, and a last update date 150. The content ID 110 and the user ID 120 are identification information given to the content and the user that are the targets of the usage authority record, respectively. Since the key necessary for the protection (encryption) release of the encapsulated content is used for each content, the key ID of such a release key may be registered instead of the content ID 110. The authority content 130 includes an authority flag for each operation item such as browsing 132, printing 134, copying 136, and editing 138. If the flag is set on, the user is authorized for the operation item. If there is only simple control of whether to permit or prohibit the use of content, the authority content 130 may be only a 1-bit flag. The validity period (or expiration date) 140 is information that defines the validity period of the electronic ticket of the content to be given to the user, and is, for example, the length of the period or the expiration date of the electronic ticket. The last update date and time 150 is the date and time when the content of the record was last updated. Note that the items of the record shown in FIG. 2 are exemplary, and not all items are necessarily required.

  The usage authority information shown in FIG. 2 defines the usage authority content for one content for each user, but this is only an example. In addition, the usage authority content can be defined for a group composed of a plurality of users. In this case, a group ID that is group identification information is described in the record instead of the user ID 120. Then, by referring to a database that manages which user belongs to which group (for example, a list of IDs of users belonging to the group is registered for each group ID), use of the user belonging to the group with respect to the content Authority can be determined. The group can include not only the user but also other groups as members. That is, the right to use content for a certain group is applied to members (users or groups) belonging to the group, and when the member is a group, it is further applied to the members of the group.

  Further, the usage authority content can be defined for the user (or group) attribute. The user attributes are information representing user attributes such as sex, age, title, smoker / non-smoker, and are registered in a database for managing users. Group attributes can be considered similarly. When the usage authority is defined for an attribute such as a user, the user ID 120 in the record is replaced with an individual attribute value or a logical expression of a plurality of attribute values. When usage rights are specified for attribute values or attribute value logical expressions in this way, the user corresponding to the attribute value or attribute value logical expression is identified by referring to the database that manages the users. Then, the use authority is applied to each identified user.

  Note that there are cases where a record of the user's usage authority information for the same content is not only set for the individual user but also set for a group or attribute. In addition, for the same content, use authority information may be set for a plurality of groups and attributes to which the user belongs. In these cases, a plurality of use authority information is searched for one user from the authority information storage unit 12. In such a case, the content of the user's usage authority (permitted operation items, effective period, etc.) can be obtained by combining the plurality of usage authority information. For example, logical sum, logical product, and other logical expressions are applied to the plurality of usage authority information.

  In response to an electronic ticket issue request (hereinafter simply referred to as a ticket request) from the user terminal 20, the inquiry unit 14 inquires about information on an electronic ticket held on the user terminal 20 side. The determination unit 16 determines whether or not it is necessary to issue an electronic ticket based on the inquiry result of the inquiry unit 14. The issuance processing unit 18 issues an electronic ticket when the determination unit 16 determines that it is necessary to issue an electronic ticket.

  The user terminal 20 includes a content handling unit 22, an authentication processing unit 24, and a ticket folder 26. The ticket folder 26 is a means for holding an electronic ticket downloaded to the user terminal 20.

  The content handling unit 22 is means for performing processing for using the encapsulated content in the user terminal 20 for use by the user. When the content is a document, an application for browsing the document, an application for editing the document, and the like correspond to the content handling unit 22.

  In the ticket folder 26, as shown in FIG. 3, ticket data 220, which is entity data of each electronic ticket, is stored in association with the content ID 210 of the content corresponding to the electronic ticket. Instead of the content ID 210, a key ID of a key used for decrypting the content may be used. The electronic ticket is downloaded from the ticket issuing device 10 and registered in the ticket folder 26 when, for example, the user explicitly instructs the terminal 20 to download the electronic ticket. It is also possible to configure the download program on the user terminal 20 to automatically download the corresponding electronic ticket when the encapsulated content is downloaded. Alternatively, the authentication processing unit 24 may be configured to automatically download from the ticket issuing device 10 when the user instructs the terminal 20 to use the encapsulated content (such as opening a file).

  When the user gives an instruction to use the encapsulated content, the authentication processing unit 24 performs authentication for the use. The authentication is performed based on an electronic ticket corresponding to the content ID (or key ID) of the encapsulated content. If the corresponding electronic ticket is not in the ticket folder 26, the authentication processing unit 24 may make a request to the ticket issuing device 10. When there is no corresponding electronic ticket (when it cannot be acquired even if requested), the use of the encapsulated content via the content handling unit 22 is prohibited. When there is a corresponding electronic ticket, the use restriction of the encapsulated content is released according to the authority content indicated in the electronic ticket, and the user can use the content via the content handling unit 22. If the application corresponding to the content handling unit 22 supports plug-in, the authentication processing unit 24 can be incorporated into the application in the form of a plug-in.

  In such a system, a process when a ticket request is issued from the user terminal 20 to the ticket issuing device 10 will be described with reference to FIG.

  In this procedure, first, (1) the user terminal 20 issues a ticket request. This ticket request includes the content ID (or key ID) of the content corresponding to the requested electronic ticket. At the time of this request, the user ID of the requesting user is sent to the ticket issuing device 10. When user authentication is performed by the ticket issuing device 10 at the time of ticket request, user authentication information is also sent from the user terminal 20 to the ticket issuing device 10. In addition, a technique for restricting transfer of an electronic ticket by creating an electronic ticket not only according to a user ID but also according to unique information of the user terminal 20 (or a device such as a network card incorporated therein) is known. (For example, refer to Japanese Patent Application Laid-Open No. 10-247905 by the applicant of the present application), when using such a technique, the unique information of the user terminal 20 is also sent to the ticket issuing device 10 together.

  In the ticket issuing device 10 that has received the ticket request, (2) the inquiry unit 14 inquires whether the user terminal 20 has the electronic ticket that is the object of the request. This inquiry includes a content ID or a key ID in order to specify a target electronic ticket. Upon receiving this inquiry, the user terminal 20 searches the ticket folder 26 to check whether there is a target electronic ticket (S10), and (3) returns the search result to the ticket issuing device 10. The user terminal 20 has a protocol for responding to such an inquiry. In the ticket issuing device 10 that has received the response from the user terminal 20, the determination unit 16 determines whether or not it is necessary to issue an electronic ticket according to the response (S12). The simplest determination rule is that when the user terminal 20 holds the electronic ticket in the ticket folder 26, the electronic ticket is not issued, and otherwise it is issued. There are some more advanced judgment methods that take into account the contents of usage rights, etc., but these will be explained together later. If the determination unit 16 determines that issuance is necessary, the issuance processing unit 18 creates an electronic ticket and sends it to the user terminal 20. In the electronic ticket creation process, the authority content that can be given to the requesting user with respect to the target content is obtained based on the information in the authority information storage unit 12, and the use authority within the range of the requested authority content is indicated. Create an electronic ticket. If the determination unit 16 determines that the issuance is unnecessary, the issuance processing unit 18 sends a message indicating that the electronic ticket is not issued to the user terminal 20 because the issuance is duplicated.

  In the above example, the ticket issuing device 10 specifies a target electronic ticket and inquires of the user terminal 20 about the presence or absence of the electronic ticket, but instead obtains a list of electronic tickets held by the user terminal 20 from the user terminal 20. From this list, the ticket issuing device 10 may determine whether there is a target electronic ticket.

  Moreover, in the above example, the case where the electronic ticket was hold | maintained at the memory | storage device incorporated in the user terminal 20 was taken as an example. However, an external storage device such as an IC card storing an electronic ticket or a USB (Universal Serial Bus) memory may be used by being mounted on the user terminal 20 by the user. In this case, the user terminal 20 can acquire information on the electronic ticket from the external storage device via an external input / output unit such as a card reader that reads an IC card or a USB port, and from the inquiry unit 14 of the ticket issuing device 10. When there is an inquiry, it is checked whether there is an electronic ticket corresponding to the external storage device via the external input / output unit, and the result is returned to the inquiry unit 14. Of course, in some cases, the user terminal 20 includes the ticket folder 26 and can accept an electronic ticket on the external storage device. In such a case, the user terminal 20 responds to the inquiry by both the ticket folder 26 and the external storage device. Check out.

  What has been described above is a method in which the ticket issuing device 10 inquires of the user terminal 20 about the electronic ticket information held by the user terminal 20. Next, a second embodiment, which is another method, will be described with reference to FIG. In FIG. 5, the same elements as those shown in FIG. 1 are denoted by the same reference numerals, and the description thereof is omitted.

  In the configuration shown in FIG. 5, the ticket issuing device 10 has an issue history management unit 13. The issue history management unit 13 records information on the electronic ticket issued by the ticket issuing device 10 to the user of each user terminal 20. The issuance history management unit 13 creates and stores a history record as shown in FIG. 6 every time the issuance processing unit 18 issues an electronic ticket. One history record includes the user ID 310 of the issue destination user, the content ID 320 (or the corresponding key ID) of the content that is the target of the issued electronic ticket, the authority content 330 permitted by the issued electronic ticket, and the electronic The issue date and time 340 at which the ticket was issued is included. The authority content 330 includes a flag indicating permission or prohibition for each operation, as in the case of the usage authority record shown in FIG. When a mechanism for issuing an electronic ticket that reflects the unique information of the user terminal 20 in addition to the user ID is adopted, the unique information of the user terminal 20 that is the issue destination is also recorded in the issue history record. Note that the items of the record shown in FIG. 6 are exemplary, and not all items are necessary. For example, if it is only necessary to determine whether or not an electronic ticket has been issued, the user ID 310 and the content ID 320 are sufficient.

  When the ticket issuing device 10 receives a ticket request from the user terminal 20, the determination unit 16 a of this embodiment examines the issue history management unit 13 instead of making an inquiry to the user terminal 20, and It is determined whether an electronic ticket has been issued to the requesting user. In this determination process, if there is a record corresponding to the user ID / content ID pair sent with the ticket request in the issuance history management unit 13, it is determined that the has been issued. Also, the expiration date of the issued electronic ticket is recorded in the issue history record, and if there is a corresponding record, it is further determined whether the expiration date has expired, and if it has not expired, it is determined that it has been issued If not, it may be determined that it has not been issued.

  As described above, in the first and second embodiments, when the ticket issuing device 10 receives a request for an electronic ticket from the user terminal 20, whether or not the electronic ticket has been issued to the user terminal 20. The electronic ticket is not issued if it has already been issued, so that it is possible to prevent duplicate issuance of electronic tickets.

  In the above example, the determination units 16 and 16a have determined whether or not to issue the ticket based on whether or not the target electronic ticket has already been issued to the user terminal 20. Hereinafter, an example in which the necessity of issuing is determined in more detail based on the contents of the issued electronic ticket will be described. In each of the following examples, when the requested electronic ticket is in the user terminal 20, it is further determined whether or not a new ticket is issued based on the contents of the electronic ticket. If not, the electronic ticket is issued as in the above embodiment.

(A) First, the first example is determination based on the issue date and time of the electronic ticket. That is, in this example, when it is determined that the target electronic ticket is in the user terminal 20 by the inquiry (first embodiment) or the issuance history (second embodiment) to the user terminal 20, the electronic terminal Check the ticket issue date and time. In the case of the first embodiment, in response to an inquiry (2) from the ticket issuing device 10 to the user terminal 20 (see FIG. 4), the user terminal 20 issues an electronic ticket issue date and time (this is described in the electronic ticket). ) Information may be returned. In the case of the second embodiment, it can be checked from the issue history management unit 13. In other examples described later, similarly, information on the contents of the electronic ticket as basic information for determination is acquired from the user terminal 20 (in the case of the first embodiment), or the issue history management unit 13. (In the case of the second embodiment).

  The determination units 16 and 16a determine the issue date and time obtained in this way, and the last update date and time 150 (see FIG. 2) of the usage authority record corresponding to the combination of the requesting user and the requested content in the authority information storage unit 12. Compare. If the issue date and time is the same as or newer than the last update date and time 150, it means that the user terminal 20 has an electronic ticket that shows the same authority as the usage authority that should be given at present. judge. Conversely, if the issuance date is older than the last update date, the authority content indicated in the electronic ticket held by the user terminal 20 may be out of date, so it is determined that it is necessary to issue the electronic ticket.

(A) The second example is a determination based on the width of the authority content of the use authority. There are two types: a direction that prioritizes expansion of the user's rights and a direction that prioritizes the content provider's rights.

  First, the former will be described. In this example, the determination units 16 and 16a are indicated in the authority contents of the electronic ticket in the user terminal 20 (that is, which operation items are permitted and which are prohibited) and the corresponding records in the authority information storage unit 12. When the latter is wider than the former (that is, the latter permits all the operation items permitted by the former and one or more other operation items are permitted) when compared with the authority content 130, It is determined that it is necessary to issue an electronic ticket. Thus, by issuing a new electronic ticket in accordance with the authority content 130 of the authority information storage unit 12, the authority of the user can be expanded. On the other hand, if the authority content of the electronic ticket is equal to or wider than the authority content of the authority information storage unit 12, it is determined that the user's authority does not increase even if a new electronic ticket is issued, and is not required. In addition, when the authority content described in the electronic ticket and the authority content of the authority information storage unit 12 are not in a broad relationship (in other words, an inclusion relationship), that is, neither the former nor the latter is permitted on the other side. When one or more operation items are included, a new electronic ticket is issued in accordance with the authority content of the current authority information storage unit 12.

  Next, a case where priority is given to the content provider's rights will be described. In this case, contrary to the above-described case of user priority, if the authority content of the authority information storage unit 12 is narrower than the authority content of the electronic ticket held by the user terminal 20, the latter authority content is followed. It is determined that a new electronic ticket needs to be issued. This is to issue a new electronic ticket when the authority granted to the user is narrower than before. When the authority content of the electronic ticket in the user terminal 20 is equal to the authority content of the authority information storage unit 12, or when the former is narrower than the latter, it is determined that it is not necessary to issue a new ticket. If the former and the latter are not in a narrow relationship, a new electronic ticket is issued as in the case of user priority.

  Note that whether the user priority or the content provider priority can be set in the ticket issuing device 10, and the determination unit 16 or 16a can determine according to the setting. It is also preferable that the user priority or the content provider priority can be set for each content or for each content provider.

(C) The third example is determination based on the validity period of the electronic ticket. That is, in this example, the validity period described in the electronic ticket in the user terminal 20 is compared with the validity period 140 indicated in the corresponding record in the authority information storage unit 12, and a new one is created based on the inclusion relation between the former and the latter. Determine whether or not to issue a new electronic ticket. In this case as well, two methods of user priority and content provider priority can be realized based on the same idea as in the second example. For example, in the user priority method, when the end date / time of the valid period registered in the authority information storage unit 12 is changed so as to be delayed (the start date / time does not change), the end date / time of the electronic ticket held by the user If is earlier than that, a new electronic ticket is issued.

(D) A fourth example is a determination based on the number of times an electronic ticket is used. That is, in this example, the number of times that the electronic ticket can be used is defined, and the user terminal 20 sets the number of times that can be used as an initial value, and subtracts the remaining number of times that can be used each time content is used using the electronic ticket. I will do it. Then, the remaining number of times that the electronic ticket can be used is compared with the number of times that the corresponding ticket registered in the authority information storage unit 12 can be used, and whether or not it is necessary to newly issue an electronic ticket is determined based on the magnitude relationship between the two. . In this case as well, two methods of user priority and content provider priority can be realized based on the same idea as in the second example. For example, in the content provider priority method, the number of times of use registered in the authority information storage unit 12 is changed from the remaining number of times of use of the electronic ticket on the user terminal 20 side due to a change in registered contents of the authority information storage unit 12 or the like. When the number is reduced, a new electronic ticket is issued.

  In the above, some examples of rules for determining whether or not to issue are described. However, these rules can be used not only independently, but also combined so that they are issued when any of the rules is satisfied. It is also possible.

  Moreover, although the case where the user terminal 20 has one electronic ticket for one content has been shown in the above example, the user terminal 20 has a plurality of electronic tickets for one content for some reason. There is also. In such a case, the determination unit 16 or 16a compares the authority content of the user to be compared with the authority content registered in the authority information storage unit 12 for determining whether the electronic ticket is issued or not. It can also be obtained from the combination of For example, if the user's authority content is the logical sum of the authority contents of the plurality of electronic tickets, operation items that cannot be used in any electronic ticket in the user terminal 20 are permitted in the authority information in the authority information storage unit 12. If so, a new electronic ticket will be issued. A logical product may be used instead of the logical sum. More generally, a user's authority may be obtained by applying a logical expression that combines logical operations such as logical sum, logical product, negation, etc. to the authority of the plurality of electronic tickets. In addition, although the content of authority was demonstrated above, the same handling is possible also about an effective period and the frequency | count of use.

  The ticket issuing device 10 according to the embodiment described above is realized by causing a general-purpose computer system to execute a program describing the above-described functions and operations.

It is a figure which shows the structure of 1st Embodiment. It is a figure which shows an example of the record structure of authority information. It is a figure which shows the data structure for the management of the electronic ticket in a ticket folder. It is a figure which shows the process sequence of 1st Embodiment. It is a figure which shows the structure of 2nd Embodiment. It is a figure which shows the structure of the record of the ticket issue history recorded on the issue history management part.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Ticket issuing apparatus, 12 Authority information storage part, 14 Inquiry part, 16 Judgment part, 18 Issue processing part, 20 User terminal, 22 Content handling part, 24 Authentication processing part, 26 Ticket holder, 30 Network

Claims (13)

A program for causing a computer system to function as an electronic ticket issuing device that issues an electronic ticket for releasing usage restrictions on content, the computer system comprising:
When receiving an electronic ticket issuance request for content from the user's terminal, it is checked whether or not the user's terminal holds an electronic ticket for the content. Judgment means for judging that issuance is necessary,
Issuance control means for issuing an electronic ticket corresponding to the issuance request to the terminal of the user when it is determined that the issuance is necessary by the determination means;
Program to function as.   The program according to claim 1, wherein the determination unit checks whether or not the terminal holds an electronic ticket for the content by making an inquiry to the terminal of the user.   The program according to claim 1, wherein the determination unit checks whether an electronic ticket is held in an external storage unit connected to the terminal by making an inquiry to the terminal of the user. The program further causes the computer system to function as an issue history storage unit that stores information on an issue history of an electronic ticket to a user terminal,
The determination means checks whether the terminal holds an electronic ticket for the content by referring to the issue history storage means.
The program according to claim 1.   When the user terminal holds an electronic ticket for the content, the determination unit further checks the issue date and time of the electronic ticket, and determines whether or not the electronic ticket should be issued based on the issue date and time. The program according to claim 1. The program further includes authority information storage means for storing information on authority to be given to each user with respect to the computer system.
In the case where the terminal of the user holds an electronic ticket for the content, the determination means further uses the user's authority to use the content indicated in the electronic ticket and the authority information storage means The user's authority to use the content is compared, and the necessity of issuing an electronic ticket for the content is determined based on the comparison result.
The program according to claim 1.   The determination means is based on a comparison between the operation content permitted to be used with the use authority of the electronic ticket held by the user terminal and the operation content permitted with the use authority required from the authority information storage means. The program according to claim 6, wherein it is determined whether or not an electronic ticket is issued.   The determination means is based on a comparison between the validity period of the ticket authorized with the use authority of the electronic ticket held by the terminal of the user and the validity period of the ticket authorized with the use authority obtained from the authority information storage means. The program according to claim 6, wherein it is determined whether or not an electronic ticket is issued for the content.   The determination means is based on a comparison between the remaining available number of times of the electronic ticket held by the terminal of the user and the available number of times of use of the ticket that is permitted with the use authority obtained from the authority information storage means. 7. The program according to claim 6, wherein the necessity of issuing a ticket is determined.   The determination unit determines that the usage authority obtained from the authority information storage unit is more advantageous for the user than the usage authority indicated in the electronic ticket for the content held by the user terminal. 7. The program according to claim 6, wherein it is determined that it is necessary to issue an electronic ticket.   The determination unit determines that the use authority obtained from the authority information storage unit is more disadvantageous for the user than the use authority indicated in the electronic ticket for the content held by the user terminal. 7. The program according to claim 6, wherein it is determined that it is necessary to issue an electronic ticket. An electronic ticket issuing device that issues an electronic ticket for releasing usage restrictions of content,
When receiving an electronic ticket issuance request for content from the user's terminal, it is checked whether or not the user's terminal holds an electronic ticket for the content. A determination means for determining that issuance is necessary;
Issuance control means for issuing an electronic ticket corresponding to the issuance request to the user's terminal when it is determined that the issuance is necessary by the determination means;
An electronic ticket issuing device comprising: A method executed by the electronic ticket issuing device for the electronic ticket issuing control for releasing the restriction on use of the content,
When receiving an electronic ticket issuance request for content from the user's terminal, it is checked whether or not the user's terminal holds an electronic ticket for the content. A determination step for determining that issuance is necessary;
A step of issuing an electronic ticket corresponding to the issue request to the terminal of the user when it is determined that the issue is necessary in the determination step;
An electronic ticket issue control method comprising:

Images