JP3723429B2 - History storage device, verification device, and electronic rights distribution system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention provides a service provided to users with a limited number of times, such as use of special coupons, bargain purchases, free sample exchanges, popular concert ticket purchases, questionnaire responses, popularity voting, etc. The present invention relates to a method and an apparatus for preventing unauthorized use of a service exceeding a limited number of times using a tamper device.
[0002]
[Prior art]
In recent years, many electronic rights distribution systems that digitize tickets and coupons distributed in paper and distribute them on a network have been proposed. For example, as disclosed in Japanese Patent Application No. 2000-038875, a tamper resistant device such as an IC card is used to prevent counterfeiting, tampering, and double use, and to distribute safely, Japanese Patent Application Laid-Open No. 2000-123095 As described above, there are methods related to a method for distributing various types of tickets and coupons using a common device.
[0003]
However, these conventional electronic rights distribution systems that prevent double use can prevent double use of a single electronic right that has been issued, and it is possible to purchase bargain products or receive free samples. It does not provide a method for restricting one person to each other, or preventing the same person from acquiring multiple voting tickets and voting twice in popularity voting.
[0004]
The first way to prevent the same user from exercising the same type of rights more than a limited number of times is to store the electronic rights issue history in a database in the electronic rights issue system and refer to this database at the time of issue. There is a method of controlling not to issue electronic rights to the same user beyond the limit number of times.
[0005]
However, since this method can be checked only at the time of issuance, it has no effect in the case of electronic rights that are permitted to be transferred. For example, as in the case of paper tickets, it is impossible to prevent so-called duffing, where many part-time workers are hired to buy up electronic tickets and sell them to other users.
[0006]
Also, as a similar method, the electronic ticket gate history is stored in a database, and this database is referenced at the ticket gate instead of at the time of issuance, and control is performed so that the same user is not ticketed more than the limit number of times. There is also a way to do it.
[0007]
However, this method is not effective in the case of electronic rights that are allowed to be transferred, as in the check at the time of issuance. In addition, since it is necessary to access a database by connecting to a network, it may be difficult to apply in an application that requires a high-speed ticket gate.
[0008]
Therefore, the second method for solving these problems is to provide a service by recording the history of exercising each of these rights or providing the service in a tamper-proof device such as an IC card held by the user himself / herself. There is a method of asking the user to present an IC card and checking the history of the presented IC card to confirm whether the limit has already been exceeded.
[0009]
This method can be confirmed at high speed even in an offline environment, but since the usage history increases monotonously, the storage area can quickly become full in a device with a small storage capacity such as an IC card. was there.
[0010]
[Problems to be solved by the invention]
The present invention is for solving the above-mentioned problems. For example, one user is fixed, such as free sample exchange, use of special coupons, purchase of bargain products, purchase of popular concert tickets, questionnaire responses, popularity voting, etc. The purpose is to provide a method and a device for reliably checking whether or not this limit is exceeded when there is a limit on the number of services that can be received within the period, especially using the second method described above. In a method of recording a service provision history in a tamper-proof device such as an IC card held by the user himself / herself, the object is to reduce the required storage capacity by providing a function for safely deleting unnecessary history.
[0011]
[Means for Solving the Problems]
In order to achieve the above object, according to claim 1 of the present invention, a history storage unit that stores a list of history data including a service expiration date, a service identifier, and a cumulative service count; a counter unit that stores first date data; Means for receiving a history record request including a service expiration date and a service identifier, means for comparing whether the service expiration date is greater than the first date data, and if the service expiration date is larger, the service expiration date and the service identifier Means for storing history data including the history record request in the history storage unit, means for transmitting the processing result of the history record request, means for receiving a history deletion request including second date data, and second date data Means for comparing whether it is larger than the first date data, means for storing the second date data in the counter section if it is larger, and smaller than the second date data And means for deleting historical data from the history storage unit having an expiration date have to propose a history storage device characterized by comprising a means for transmitting a processing result of the history erasure request.
[0012]
According to the above configuration, history data is recorded or updated only when the service expiration date is greater than the first date data, and the processing result of the history recording request is returned, and it is possible to determine whether the service can be provided. Only when the second date data is larger than the first date data, history data having an expiration date smaller than the second date data is deleted, so that the service frequency limit can be reliably checked offline and unnecessary history is recorded. Only data can be safely deleted.
[0013]
According to claim 2 of the present invention, in the history storage device according to claim 1, the history recording request includes a challenge, and data including the service expiration date, the service identifier, and the challenge is provided by a key of the history storage device. Proposed is a history storage device comprising signature generation means for digitally signing, wherein the processing result of the history recording request includes the digital signature.
[0014]
According to the above configuration, the history storage device described above can generate the processing result of the history recording request to which the digital signature is given, and it is possible to prevent unauthorized processing of the processing result.
[0015]
Further, in claim 3 of the present invention, connection means for connecting to the history storage device; An expiration date recording unit for recording an expiration date of the service, and a service ID recording unit for recording an identifier of the service, obtaining the service expiration date and the service identifier from the expiration date recording unit and the service ID recording unit, In history storage device Said Means for transmitting a history record request including a service expiration date and a service identifier; and the history record request In contrast, in the history storage device, the service expiration date is compared with the previous history erasure date, and if the expiration date is larger, the service expiration date, the service identifier, and how many times the service has been received in the past. Record historical data including cumulative service counts processing Did The result The Means for receiving from the history storage device; Means for displaying the processing result of the history record request on a display unit; A verification device characterized by comprising:
[0016]
According to the said structure, the historical data of the log | history storage apparatus mentioned above can be acquired, and the propriety of service provision can be checked reliably.
[0017]
Moreover, in Claim 4 of this invention, in the verification apparatus of Claim 3, An expiration date recording unit for recording an expiration date of the service, a service ID recording unit for recording an identifier of the service, Generate a challenge A random number generation unit, obtaining a service expiration date and a service identifier from the expiration date recording unit and the service ID recording unit, In history storage device Said Service expiration date and service identifier Generated by the random number generator Means for sending a history record request including a challenge; In response to the history record request, the history storage device compares the service expiration date with the previous history deletion date, and if the expiration date is greater, the service expiration date, the service identifier, and the service are stored in the past. Record history data including the accumulated service count indicating how many times the service has been received, and store the history for the data including the service expiration date, the service identifier, the accumulated service count indicating how many times the service has been received in the past, and the challenge. Means for receiving, from the history storage device, a result of performing a digital signature with the device key; Proposed is a verification device comprising signature verification means for verifying a digital signature included in the processing result of the history record request.
[0018]
According to the above configuration, it is possible to verify the digital signature attached to the processing result of the history recording request generated by the history storage device described above, and to prevent unauthorized alteration of the processing result.
[0019]
Moreover, in Claim 5 of this invention, in the verification apparatus of the said Claim 3 or 4, A timer section for generating current date data, acquiring the current date data from the timer section, and a new history erasure date about one to one week before the current date data Means for sending a history clear request including In response to the history erasure request, the history storage device compares the new history erasure date with the previous history erasure date, and if the new history erasure date is greater than the new history erasure date, Means for receiving from the history storage device a result of processing for erasing previous history data; means for displaying the processing result of the history erasure request on a display unit; A verification device characterized by comprising:
[0020]
According to the above configuration, only unnecessary history data in the above-described history storage device can be safely deleted.
[0021]
According to a sixth aspect of the present invention, in the electronic right distribution system comprising the issuing device, the electronic wallet device, and the ticket gate device, the issuing device includes the verification device according to any one of the third to fifth aspects, The device includes the history storage device according to claim 1, the issuing device includes means for transmitting a history record request to the electronic wallet device, and the electronic wallet device includes the history record request. Includes the cumulative number of times history data is recorded in the history storage unit Means for transmitting the processing result to the issuing device, and the issuing device verifies the processing result; , The cumulative count is less than the specified count limit Proposed is an electronic rights distribution system characterized by having means for verifying whether a constraint condition is satisfied and means for issuing an electronic right only when the constraint condition is satisfied.
[0022]
According to the said structure, it becomes possible to issue safely the electronic right which has the frequency | count of service utilization.
[0023]
According to claim 7 of the present invention, in the electronic rights distribution system according to claim 6, the electronic wallet device further includes the verification device according to any one of claims 3 to 5, and the electronic wallet device is a history record. Means for sending request to transferee's electronic wallet device, and history record request Includes the cumulative number of times history data is recorded in the history storage unit Means for transmitting the processing result to the electronic wallet device of the transfer source, and verifying the processing result , The cumulative count is less than the specified count limit A means of verifying whether the constraints are satisfied, and the electronic rights are only granted when the constraints are satisfied. Move to the destination electronic wallet device An electronic rights distribution system characterized by comprising:
[0024]
According to the above configuration, it is possible to safely transfer an electronic right that has a limit on the number of times the service is used.
[0025]
According to claim 8 of the present invention, in the electronic rights distribution system comprising an issuing device, an electronic wallet device, and a ticket gate device, the ticket gate device includes the verification device according to any one of claims 3 to 5, The device includes the history storage device according to claim 1, the ticket gate device includes means for transmitting a history record request to the electronic wallet device, and the electronic wallet device includes the history record request. Includes the cumulative number of times history data is recorded in the history storage unit Means for transmitting the processing result to the ticket gate, and the ticket gate verifies the processing result. , The cumulative count is less than the specified count limit Proposed is an electronic rights distribution system characterized by having means for verifying whether a constraint condition is satisfied and means for ticketing an electronic right only when the constraint condition is satisfied.
[0026]
According to the above-described configuration, it is possible to safely pass an electronic right that has a limit on the number of times the service is used.
[0027]
DETAILED DESCRIPTION OF THE INVENTION
[Embodiment 1]
FIG. 1 is a block diagram showing an example of an embodiment of a history storage device of the present invention for storing a history of actions performed by a user.
[0028]
In the present invention, it is assumed that one history storage device is distributed to each user by an administrative organization, a credit card issuing organization, or the like. In order to avoid distributing multiple copies to the same user, there is a method of presenting a driver's license, insurance card, fingerprint, etc., and checking whether it has already been distributed.
[0029]
As illustrated in FIG. 1, the history storage device 10 includes a connection unit 11, a history recording unit 12, a signature generation unit 13, a counter unit 14, an addition unit 15, a history deletion unit 16, and a history storage unit 17.
[0030]
The connection unit 11 is a part that exchanges data with a verification device described later. The history recording unit 12 is a part that records a history based on a history recording request received from the connection unit 11. The signature generation unit 13 is a part that generates a digital signature using a secret key held by the history storage device.
[0031]
The counter unit 14 stores a history deletion date, and stores date data designated by a history deletion request as will be described in detail later. The adding unit 15 is a part that increases the value of the counter unit 14. The history erasure unit 16 is a part for erasing the history based on the history erasure request received from the connection unit 11.
[0032]
The history storage unit 17 is a part for storing history data, and an example of the stored history data is shown in FIG. As shown in FIG. 2, the history storage unit 17 stores a set of history data including three sets of <expiration date, service ID, cumulative number>.
[0033]
The service ID (SID) is an identifier for identifying a service provided by the service provider to the user, and identifies, for example, exchange of a specific free sample, purchase of a specific bargain, a specific popularity vote, etc. This identifier is assigned by the service provider.
[0034]
In addition, in the example of limiting the number of purchases of popular concert tickets, there are various methods for assigning SIDs depending on the range to be restricted and the target. For example, the same SID may be assigned to all events held in a specific year for a specific artist, or the same SID may be assigned to events held on a specific date and time of a specific artist. You may do it. Furthermore, different SIDs may be assigned to all events.
[0035]
In this way, the SID can basically be freely set according to the intention of the service provider. However, in order to prevent the same SID from being used between different providers, in this embodiment, a hash for concatenation of the service provider's private key and the identifier provided by the service provider for a specific service The value shall be used.
[0036]
As another embodiment, the same SID can be used by assigning in the URI (Internet Resource Identifier) format standardized by IETF and including the domain name managed by each operator in the URI. It may be prevented.
[0037]
The expiration date is the expiration date for which the service specified by the SID is valid. In this embodiment, a unique expiration date is given for each SID. For example, the purchase deadline corresponds to the purchase of a bargain item, and the vote deadline corresponds to the popularity vote.
[0038]
The cumulative number is an area for recording how many times the service specified by the SID has been received in the past, and increases by 1 each time the service is received.
[0039]
The history storage device 10 basically accepts two requests, a history recording request and a history erasing request. These requests are received from the verification device by the connection unit 11 and processed by the history recording unit 12 and the history erasing unit 16, respectively. FIG. 3 shows a processing flow of the history recording unit 12 when a history recording request is received. FIG. 4 shows a processing flow of the history erasure unit 16 when a history erasure request is received.
[0040]
The history recording unit 12 processes the history recording request in the following flow (FIG. 3).
[0041]
(1) A history record request Record (D, SID, C) including an expiration date D, a service ID (SID), and a challenge C is received from the connection unit 11 (s1). The challenge C is a random number or the like generated by the verification device.
[0042]
(2) Compare D and the history deletion date stored in the counter unit 14 which is larger (which is newer) (s2). If D is smaller (older), the process ends with an exception.
[0043]
(3) Search history data having the same D and SID from the history storage unit 17 (s3).
[0044]
(4) Above ( 3 ), If the history data <D, SID, N> already exist (s4), the history data is updated by adding the cumulative number N to N + 1 (s5).
[0045]
(5) Above ( 3 If no history data exists, <D, SID, 1> is recorded in the history storage unit 17 as new history data (s6).
[0046]
(6) If the history cannot be recorded due to insufficient capacity of the history storage unit 17 in (5) above (s7), a history area shortage exception is generated and the process ends.
[0047]
(7) Sending the concatenation of D, SID, N, and C to the signature generation unit 13, and using the private key K held by the history storage device 10, the signature S _K (D‖SID‖C‖N) is generated (s8) (however, when history data does not exist (the above (4)), N = 0).
[0048]
(8) N and S to the request source by the connection unit 11 _K (D‖SID‖C‖N) is transmitted (returned) (s9).
[0049]
Note that it is possible to provide a history reference request that does not add a history only by checking the past service provision count, but in this embodiment, the function is provided by returning the past service provision count in the processing result of the history record request. Was included. However, the history reference request can be easily realized by omitting the steps (4), (5), and (6).
[0050]
When the above history recording request is received and processed as described above, the history data increases monotonously, and a device with a small storage capacity such as an IC card has a problem that the storage area becomes full immediately. Therefore, in the present invention, a function for deleting a history whose expiration date has passed in the flow shown in FIG. 4 is provided, and a permanent transaction of an electronic medium is enabled.
[0051]
The history erasure unit 16 processes the history erasure request in the following flow (FIG. 4).
[0052]
(1) The history erasure request Clear (D1) including the history erasure date D1 is received from the connection unit 11 (s11). The history erasure date is specified to be a value that is later than the history erasure date specified by the history erasure request in the past and earlier than the current date. For example, a date one day to one week before the current date may be specified by a verification device or the like.
[0053]
(2) The previously given history deletion date and time D0 recorded in the counter unit 14 is acquired and compared with D1, and when D1 is equal to or less than D0, an exception is generated (s12).
[0054]
(3) X = D1−D0 is calculated, and the adding unit 15 adds X to the counter unit 14 (s13). As a result, the history erasure date and time recorded in the counter unit 14 is D1. The calculation with respect to the counter unit 14 is only one-way as described above, and subtraction does not exist. As a method of setting only the increment in this way, there are, for example, a method using a dedicated circuit described in Japanese Patent No. 1884135 and a method realized by software written in a ROM.
[0055]
(4) The history data stored in the history storage unit 17 is searched for history data before D1 and deleted (s14).
[0056]
(5) The connection unit 11 transmits a normal end to the request source (s15).
[0057]
According to the above steps, when a malicious user erases a transaction history by giving a future date as a history erasure date and erasing the transaction history in the step (1), the history erasure date and time recorded in the counter unit 14 Since the date becomes a future date, even if an attempt is made to store the same history again, the exception is terminated in step (2) of the history recording request flow shown in FIG. . Further, even if an attempt is made to return the history erasure date / time recorded in the counter unit 14 to a past date, the value of the counter unit 14 cannot be subtracted as described above, so that such injustice can be prevented.
[0058]
FIG. 5 shows an example of an embodiment of a verification device according to the present invention for verifying a history storage device presented by a user before a service provider provides a service and determining whether the service can be provided. FIG.
[0059]
As shown in FIG. 5, the verification device 20 includes a random number generation unit 21, a service ID recording unit 22, an expiration date recording unit 23, a verification control unit 24, a signature verification unit 25, a history deletion control unit 26, a timer unit 27, a connection The unit 28 and the display unit 29 are included.
[0060]
The random number generation unit 21 is a part for generating a challenge for authenticating the history storage device 10. The service ID recording unit 22 and the expiration date recording unit 23 are portions for recording a service ID and an expiration date for a service that the verification device 20 wants to verify, respectively. The verification control unit 24 is a part that controls the verification process.
[0061]
The signature verification unit 25 is a part that verifies the signature data transmitted from the history storage device 10 and authenticates the history storage device 10. The history erasure control unit 26 is a part that generates and transmits a history erasure request. The timer unit 27 is a part that generates the current time. The connection unit 28 is a part connected to the history storage device 10. The display unit 29 is a part that displays whether the service can be provided to the verifier and the user.
[0062]
FIG. 6 shows a verification processing flow by the verification apparatus. The verification control unit 24 checks the history recorded in the history storage device 10 in the next flow and verifies whether the service can be provided.
[0063]
(1) The history storage device 10 is connected to the verification device 20 (s21). When the history storage device 10 is realized by a contact type IC card, when the card is inserted, and when the history storage device 10 is realized by a non-contact type IC card, it is an opportunity that senses that the card is approached. Connected.
[0064]
(2) The random number generator 21 generates a random number C (s22).
[0065]
(3) The SID and D are acquired from the service ID recording unit 22 and the expiration date recording unit 23, and the history recording request Record (D, SID, C) is transmitted to the history storage device 10 through the connection unit 11 (s23). In another embodiment, some services that can be provided to the user are displayed using the display device, and SIDs and D corresponding to the services selected by the user or the verifier may be acquired.
[0066]
(4) As a result of the request from the connection unit 11, the past service provision count N and the signature S by the history storage device 10 _K (D‖SID‖C‖N) is received (s24). When a history area shortage exception is notified, it is displayed on the display unit 29.
[0067]
(5) The signature verification unit 25 verifies whether the signature data acquired in (4) is correct (s25). In order to verify, a verification key of the history storage device 10, that is, a public key in the case of the public key method, and a common key in the case of the common key method are necessary. It is assumed that the verification unit 25 holds it.
[0068]
(6) The past service provision count N is displayed on the display unit 29 (s26). The verifier permits the service provision if the number is less than the limit number. For example, in the case of free sample exchange, the service is provided when it has not been delivered in the past (N = 0), and in the case of bargain purchase, when the purchase limit is not exceeded.
[0069]
FIG. 7 shows a processing flow of the history erasure control unit 26 that makes a history erasure request when the history cannot be recorded due to an error such as a lack of history area exception.
[0070]
(1) A history deletion instruction is input from the display unit 29 (s31).
[0071]
(2) The current date is acquired from the timer unit 27 (s32).
[0072]
(3) A date one to one week before the current date is designated as the history deletion date and time D1, and the user is notified (displayed) that the history will be deleted (s33).
[0073]
(4) When an OK instruction is issued from the user, the connection unit 28 transmits a history deletion request Clear (D1) to the history storage device 10 (s34).
[0074]
(5) The result is received from the connection unit 28 and displayed on the display unit 29 (s35).
[0075]
[Embodiment 2]
The above embodiment distributes a history storage device in the form of a member card or the like in advance to provide a uniform service to all members. For example, one souvenir is distributed to all members. In some cases, there is an unprecedented feature that only one member card can be safely distributed without issuing a right such as a voucher in advance by simply notifying the member by e-mail or the like.
[0076]
In the second embodiment, an example is shown in which this function is combined with a conventional electronic rights distribution system to control the number of times that a specific electronic right is issued or exercised rather than all members. A typical example is when the purchase of popular concert tickets is limited to one person.
[0077]
FIG. 8 is a configuration diagram showing an example of an embodiment of the electronic rights distribution system of the present invention using the history storage device and the verification device described above.
[0078]
As shown in FIG. 8, this system includes an issuing device 100, an electronic rights storage device 200, a ticket gate device 300, and a network device 400.
[0079]
It is assumed that the issuing device 100 is owned by an organization that issues electronic rights, the electronic rights storage device 200 is owned by a user, and the ticket gate device 300 is owned by an organization that issues electronic rights, and is issued for each issuer, each user, and each ticket gate. There may be more than one.
[0080]
The issuing device 100 includes an electronic right generation unit 101, an electronic right issue unit 102, a communication unit 103, and a verification device 104.
[0081]
The electronic right storage device 200 includes a communication unit 201, a storage control unit 202, an exercise control unit 203, an electronic right storage unit 204, a history storage device 205, and a verification device 206. This apparatus is also called an electronic wallet.
[0082]
The ticket gate device 300 includes an electronic right ticket gate unit 301, a communication unit 302, and a verification device 303.
[0083]
The history storage device 205 and the verification devices 104, 206, and 303 are the same as those described in the first embodiment.
[0084]
The network device 400 is a public network such as the Internet or a telephone network, or a private network using a LAN or a dedicated line. The issuing device 100, the electronic rights storage device 200, and the ticket gate device 300 communicate with each other via this device. Make it possible.
[0085]
Electronic rights are circulated among the above devices by the following four types of transactions: issuance, transfer, consumption, and presentation.
[0086]
Issued transaction: A transaction that generates an electronic right and gives the user ownership of the electronic right. In the present embodiment, the issuing device 100 generates an electronic right and stores it in the electronic right storage unit 204 of the electronic right storage device 200 owned by the user.
[0087]
Transfer transaction: A transaction to transfer ownership of electronic rights from one user to another. In the present embodiment, the electronic rights stored in the electronic rights storage unit 204 of the electronic rights storage device 200 held by the assigning user is extracted and deleted, and the electronic rights storage device 200 held by the assigning user is deleted. It is realized by storing in the electronic right storage unit 204 of the above.
[0088]
Consumption transaction: A transaction that invalidates ownership of electronic rights. In the present embodiment, it is realized by taking out and deleting the electronic rights stored in the electronic rights storage unit 204 of the electronic rights storage device 200 held by the user and notifying the ticket gate device 300 of the deletion. To do.
[0089]
It should be noted that a method for preventing unauthorized duplication and the multiple use of electronic rights in the process of issuing, transferring, and consuming transactions is not the subject of the present invention, and has already been proposed. Since it is easy to implement the method for preventing the multiple use of rights in combination with the present invention, details are omitted.
[0090]
Regarding the multiple use prevention method of electronic rights, for example, as described in JP-A-11-213068, JP-A-2000-123095, etc., a transfer list is attached to electronic rights to be distributed, and double use is possible. The original information (token) is stored in a tamper-proof device such as an IC card as described in Japanese Patent Application No. 2000-038875, etc. , A method for preventing unauthorized duplication by providing a protocol for enabling safe distribution of original information, owner authentication information for each electronic right on a network as described in Japanese Patent Application No. 11-31090 A number of methods have been proposed, such as a method for authenticating the right owner by managing the password.
[0091]
FIG. 9 is an explanatory diagram showing an example of the data structure of electronic rights stored in the electronic rights storage unit 204. As shown in the figure, one electronic right includes four data areas of right information in which a service (right) ID, an expiration date, a frequency limit, and other electronic rights are defined. In order to give electronic rights transaction restrictions, the service ID and expiration date shown in the first embodiment are set in the electronic rights.
[0092]
The number limit specifies the upper limit value of the number of times transactions are allowed within the valid period. In the present embodiment, it is regarded as a transaction that a new electronic right is stored in the electronic right storage device 200 by an issue or transfer transaction. That is, the upper limit value of the number of transactions is the upper limit value of the number of times of storage in the electronic rights storage device 200. Depending on the embodiment, it is possible to specify various conditions such as providing transaction restrictions separately for each transaction of issuing, transferring, and consuming electronic rights.
[0093]
In the right information, unique information for each electronic right is defined. For example, the identifier of the issuing organization, the contents of the rights, the signature of the issuer, etc. are defined.
[0094]
Next, electronic rights transactions (issuance processing) performed using these devices will be described in detail.
[0095]
(1) The issuing device 100 uses the electronic right generation unit 101 to generate an electronic right including an expiration date (D), a service ID (SID), a frequency limit, and a right content. Further, the verification device 104 generates a random number C.
[0096]
(2) The issuing device 100 transmits an electronic rights storage request including D, SID, and C generated in (1) to the electronic rights storage device 200. In the transmission of the electronic right storage request, the electronic right itself (ownership) has not yet moved. Although the transfer of electronic rights is not described in detail in the present invention, it is realized by transferring original information unique to rights information described in Japanese Patent Application No. 2000-038875, for example.
[0097]
(3) The electronic rights storage device 200 generates a history record request Record (D, SID, C) by the storage control unit 202 and sends it to the history storage device 205.
[0098]
(4) The electronic rights storage device 200 records the history data in the history storage unit by the history storage device 205 and transmits the result to the storage control unit 202.
[0099]
(5) The electronic right storage device 200 sends the result of the above (4) to the issuing device 100 by the storage control unit 202.
[0100]
(6) The issuing device 100 verifies the result of the above (4) by the verification device 104. Details are the same as in the first embodiment.
[0101]
(7) The issuing device 100 further verifies that the cumulative number N is less than or equal to the number limit specified for the electronic right.
[0102]
(8) When the issuing device 100 succeeds in the verifications (6) and (7), the issuing device 100 moves the electronic rights to the electronic rights storage device 200.
[0103]
(9) The electronic right storage device 200 stores the electronic right received by the storage control unit 202 in the electronic right storage unit 204.
[0104]
Electronic rights are stored in the electronic rights storage device not only by issuance but also by transfer from another electronic rights storage device. Therefore, the flow in the case where the electronic right is transferred from the first electronic right storage device (hereinafter denoted by reference numeral 200A) to the second electronic right storage device (hereinafter denoted by reference numeral 200B) is shown below. .
[0105]
(1) In the first electronic rights storage device 200A, the exercise control unit 203 acquires the expiration date D and service ID (SID) of the electronic rights to be transferred from the electronic rights storage unit 204. Further, the verification device 206 generates a random number C.
[0106]
(2) The first electronic rights storage device 200A transmits an electronic rights storage request including D, SID, and C to the second electronic rights storage device 200B.
[0107]
(3) In the second electronic rights storage device 200B, the storage control unit 202 generates a history record request Record (D, SID, C) and sends it to the history storage device 205.
[0108]
(4) The second electronic rights storage device 200B records the history data in the history storage unit by the history storage device 205 and transmits the result to the storage control unit 202.
[0109]
(5) The second electronic rights storage device 200B sends the result of (4) above to the first electronic rights storage device 200A by the storage control unit 202.
[0110]
(6) The first electronic rights storage apparatus 200A verifies the result of the above (4) by the verification apparatus 206. Details are the same as in the first embodiment.
[0111]
(7) The first electronic rights storage device 200A further verifies that the cumulative number N is less than or equal to the number limit specified for the electronic right.
[0112]
(8) When the verification of (6) and (7) is successful, the first electronic rights storage device 200A moves the electronic rights to the second electronic rights storage device 200B.
[0113]
(9) The second electronic rights storage device 200B stores the electronic rights received by the storage controller 202 in the electronic rights storage 204.
[0114]
By the above steps, before the electronic rights are stored in the electronic rights storage device, the past transaction history, the storage history for each electronic rights SID in the above embodiment is checked. It is possible to prevent storing more than the limit number of times. Moreover, it is possible to check not only at the time of issue but also at the time of transfer.
[0115]
In addition, when a different SID is assigned to each individual electronic right, it can be used as one of methods for preventing double use.
[0116]
Next, other parities of the present invention will be described.
[0117]
(1) In the above embodiment, the history storage device is assumed to be realized in a tamper-proof device such as an IC card, but this is recorded in a server on the network device, and the cumulative number of transactions is limited. It is also possible to control storage in the electronic wallet by inquiring the server to check whether the value has been exceeded. Such a method is similar to a conventional double-use check server. However, in the present invention, unlike a simple double-use check server, not only a double use of individual electronic rights units but also a difference by SID. It is different from the conventional method in that a flexible check function can be provided, such as limiting the number of transactions per unit.
[0118]
(2) In the above embodiment, one SID is assigned to one electronic right. However, it is also possible to assign a plurality of SIDs and give some constraints by AND or OR. .
[0119]
(3) In the above embodiment, the cumulative number N is used as the service provision frequency. However, by managing the cumulative number N as the service provision frequency and adding a plurality of frequencies to one service provision, for example, one It is also possible to apply to control of the loan limit per month.
[0120]
(4) In the above embodiment, when a history record request is transmitted to the history storage device, the cumulative number N is returned. Instead of returning N, a truth value indicating whether the number limit value has been exceeded is returned. You may carry out. However, in this case, it is necessary to record the number limit value for each SID in the history storage device so that it can be determined whether or not the cumulative number of transactions exceeds the number limit value.
[0121]
(5) In the above embodiment, it is assumed that the history storage unit in which history data is stored is recorded in a tamper-proof device such as an IC card, but this is stored in a normal storage medium such as a hard disk, Only the hash value of the history data may be put in the tamper resistant device to prevent the history data from being falsified. In this case, it is necessary to recalculate the hash value every time history data is added or deleted, but the storage capacity of the tamper resistant device can be further reduced.
[0122]
【The invention's effect】
As described above, according to the present invention, whether the service provided to the user has been limited in number of times, whether it has been used illegally beyond the number of times limit, including whether it has been received in the past. Can be verified. In addition, since the history is accumulated in a tamper-proof device such as an IC card, it can be safely verified even offline. In addition, being able to verify offline has the effect of reducing not only the communication cost but also the development cost and operation cost of the center database for managing the usage history.
[0123]
Application examples of the present invention include the number of sample exchanges, restaurant tastings, voting votes, bargain purchases, game appearances, welfare facility usages, concert ticket purchases, shareholder benefits. The number of tickets used, the number of license violations, the loan limit, etc. vary widely. Accordingly, although these restrictions vary depending on the application, it is possible for the service provider to set the SID and expiration date on its own and store the history, so one IC card can be used for many service providers. Can be shared. This also has the effect of reducing the cost of cards per service provider.
[0124]
By using a counter that can only be increased to realize the history erasure date and time, it is possible to safely delete the history related to the expired service, and it is practical even if it is realized with an IC card having a small storage area. In addition, since the timer itself is safe even if it is placed outside the tamper resistant device, there is an effect that it can be realized at a low cost.
[0125]
Conventionally, in order to provide services to members, mailing paper coupons or distributing electronic tickets over the Internet has the purpose of limiting the number of services provided. However, when providing a service to all members having a membership card having the history storage function of the present invention, the service provision frequency can be limited by examining the service provision history in the card, There is an advantage that it is not necessary to issue a coupon. This has the effect of reducing the development cost and operating cost of a system for issuing coupons and the like.
[Brief description of the drawings]
FIG. 1 is a configuration diagram showing an example of an embodiment of a history storage device of the present invention.
FIG. 2 is an explanatory diagram showing an example of history data recorded in a history storage unit
FIG. 3 is a processing flowchart when the history storage device receives a history recording request.
FIG. 4 is a processing flowchart when the history storage device receives a history deletion request.
FIG. 5 is a block diagram showing an example of an embodiment of a verification apparatus according to the present invention.
FIG. 6 is a processing flowchart when the verification device verifies the history storage device.
FIG. 7 is a processing flowchart when the verification device deletes the history from the history storage device.
FIG. 8 is a configuration diagram showing an example of an embodiment of an electronic rights distribution system using a history storage device and a verification device according to the present invention.
FIG. 9 is an explanatory diagram showing an example of a data structure of electronic rights
[Explanation of symbols]
10: history storage device, 11: connection unit, 12: history recording unit, 13: signature generation unit, 14: counter unit, 15: addition unit, 16: history deletion unit, 17: history storage unit,
20: Verification device, 21: Random number generation unit, 22: Service ID recording unit, 23: Expiration date recording unit, 24: Verification control unit, 25: Signature verification unit, 26: History deletion control unit, 27: Timer unit, 28 : Connection unit, 29: display unit, 100: issuing device, 101: electronic right generation unit, 102: electronic right issuing unit, 103: communication unit, 104: verification device, 200: electronic right storage device, 201: communication unit, 202: Storage control unit, 203: Exercise control unit, 204: Electronic right storage unit, 205: History storage device, 206: Verification device, 300: Ticket gate device, 301: Electronic right ticket gate unit, 302: Communication unit, 304: Verification Device, 400: Network device.

Claims (8)

A history record request that includes a history storage unit that stores a list of history data including a service expiration date, a service identifier, and a cumulative service count, and a counter unit that stores first date data, and includes the service expiration date and the service identifier Means for receiving
Means for comparing whether the service expiration date is greater than the first date data;
Means for storing, in the history storage unit, history data including the service expiration date and service identifier in the case of being large;
Means for transmitting the processing result of the history record request;
Means for receiving a history erasure request including second date data;
Means for comparing whether the second date data is greater than the first date data;
Means for storing the second date data in the counter section if it is larger;
Means for deleting history data having an expiration date smaller than the second date data from the history storage unit;
A history storage device comprising means for transmitting the processing result of the history erasure request. The history storage device according to claim 1,
The history record request includes a challenge, and includes signature generation means for performing a digital signature on data including the service expiration date, the service identifier, and the challenge using a key of a history storage device,
A history storage apparatus, wherein the processing result of the history recording request includes the digital signature. A connection means for connecting to the history storage device;
An expiration date recording unit for recording an expiration date of the service, and a service ID recording unit for recording an identifier of the service, acquiring the service expiration date and the service identifier from the expiration date recording unit and the service ID recording unit, and history means for transmitting a history recording request including the service expiration and service identifier in the storage unit,
In response to the history record request , the history storage device compares the service expiration date with the previous history deletion date, and if the expiration date is greater, the service expiration date, the service identifier, and the service are stored in the past. the results of the process of recording was history data including a cumulative service number which indicates how many times received means for receiving from the history storage unit,
A verification apparatus comprising: means for displaying a processing result of the history record request on a display unit . The verification apparatus according to claim 3,
An expiration date recording unit that records an expiration date of the service, a service ID recording unit that records an identifier of the service, and a random number generation unit that generates a challenge, and the service validity from the expiration date recording unit and the service ID recording unit to obtain a time and a service identifier, means for transmitting a history recording request including the challenge generated by the history storage unit and the service expiration and service identifier the random number generator,
In response to the history record request, the history storage device compares the service expiration date with the previous history deletion date, and if the expiration date is greater, the service expiration date, the service identifier, and the service are stored in the past. Record history data including the accumulated service count indicating how many times the service has been received, and store the history for the data including the service expiration date, the service identifier, the accumulated service count indicating how many times the service has been received in the past, and the challenge. Means for receiving, from the history storage device, a result of performing a digital signature with the device key;
A verification apparatus, comprising: signature verification means for verifying a digital signature included in the processing result of the history record request. In the verification apparatus according to claim 3 or 4,
A timer unit that generates current date data, obtains current date data from the timer unit, and issues a history deletion request including a new history deletion date about a day to a week before the current date data. Means for transmitting ;
In response to the history erasure request, the history storage device compares the new history erasure date with the previous history erasure date, and if the new history erasure date is larger, the new history erasure date is earlier than the new history erasure date. Means for receiving from the history storage device the result of the process of erasing the history data;
A verification apparatus comprising: means for displaying a processing result of the history erasure request on a display unit . In an electronic rights distribution system comprising an issuing device, an electronic wallet device and a ticket gate device,
The issuing device includes the verification device according to any one of claims 3 to 5;
The electronic wallet device includes the history storage device according to claim 1 or 2,
The issuing device has means for transmitting a history record request to the electronic wallet device,
Further, the electronic wallet device has means for transmitting the processing result including the cumulative number when the history data is recorded in the history storage unit based on the history recording request to the issuing device,
Further, the issuing device verifies the processing result, and verifies whether the constraint condition that the cumulative number is equal to or less than the specified number limit is satisfied, and issues an electronic right only when the constraint condition is satisfied. And an electronic rights distribution system. The electronic rights distribution system according to claim 6,
The electronic wallet device further includes a verification device according to any one of claims 3 to 5,
Also, the electronic wallet device transmits a history record request to the transferee electronic wallet device, and a processing result including a cumulative number of times when the history data is recorded in the history storage unit based on the history record request. The means for transmitting to the electronic wallet device of the transfer source, the means for verifying whether the processing result is verified and satisfying the constraint that the cumulative number is less than or equal to the specified number limit, and satisfying the constraint Means for transferring electronic rights only to the electronic wallet device of the transfer destination only at times. In an electronic rights distribution system comprising an issuing device, an electronic wallet device and a ticket gate device,
The ticket gate device includes the verification device according to any one of claims 3 to 5,
The electronic wallet device includes the history storage device according to claim 1 or 2,
The ticket gate device has means for transmitting a history record request to the electronic wallet device,
Further, the electronic wallet device has means for transmitting the processing result including the cumulative number when the history data is recorded in the history storage unit based on the history recording request to the ticket gate device,
In addition, the ticket gate apparatus verifies the processing result, verifies whether or not the constraint condition that the cumulative number is equal to or less than the specified number limit is satisfied, and ticket gates only when the constraint condition is satisfied. And an electronic rights distribution system.

Images