WO2018150931A1 - Server and authentication system - Google Patents
Server and authentication system Download PDFInfo
- Publication number
- WO2018150931A1 WO2018150931A1 PCT/JP2018/003879 JP2018003879W WO2018150931A1 WO 2018150931 A1 WO2018150931 A1 WO 2018150931A1 JP 2018003879 W JP2018003879 W JP 2018003879W WO 2018150931 A1 WO2018150931 A1 WO 2018150931A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- authentication
- terminal
- communication device
- wireless communication
- card
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2103—Challenge-response
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
Definitions
- This disclosure relates to a server and an authentication method.
- a new and improved server that can securely authenticate an IC card when diverting an IC card that is assumed to be used offline to a form in which a value is stored in the server. And an authentication method.
- a providing unit that provides authentication data for authentication of the IC card to a terminal that performs proximity contactless communication with the IC card, and the number of times the authentication data is used from the terminal.
- An acquisition unit that acquires reception data received by proximity contactless communication with the IC card, and an authentication unit that authenticates the IC card using the authentication data and the reception data.
- a server is provided.
- the authentication data for authentication of the IC card is provided to a terminal that performs proximity contactless communication with the IC card, and the number of times the authentication data is used from the terminal. Including receiving received data received by proximity non-contact communication with the IC card, and authenticating the IC card using the authentication data and the received data. A method is provided.
- an IC card that is assumed to be used offline is diverted to a form in which a value is stored in a server
- the IC card can be safely authenticated.
- An improved server and authentication method can be provided.
- a secret key and a secure chip for storing it are necessary on the terminal side, leading to increased costs on the terminal side and complicated management. Further, even if a secret key or a secure chip is arranged on the server side, a lot of communication is required, so that the development cost of the server or terminal on the communication path is high. Depending on the existing environment, it was necessary to provide a dedicated communication path separately.
- the present disclosure person has intensively studied a technique for clearing the above-described points.
- the present disclosing person can safely use the IC card when diverting the IC card that is assumed to be used not only online but also offline to a form that retains value in the server. It came to devise the technology that enables authentication.
- FIG. 1 is an explanatory diagram illustrating a configuration example of an authentication system according to an embodiment of the present disclosure.
- a form in which a value is stored in the server increases, and a use form of an IC card that authenticates the owner of the value of the server by confirming that the card is correct is assumed.
- FIG. 1 shows a terminal 200 having a reader / writer that communicates between the IDcd authentication server 100 and the IC card 300 by proximity non-contact communication, and an IC card 300 having an IC chip built therein.
- FIG. 1 also shows a service provider 400 that provides a service to the IC card 300 and another provider 500.
- the service provider 400 and the other provider 500 may be in the form of a server, for example.
- FIG. 2 is an explanatory diagram showing a functional configuration example of the IDcd authentication server 100.
- the IDcd authentication server 100 includes an IC card authentication unit 110, a coupon data management unit 120, a communication data restoration unit 130, and an external communication unit 140.
- the IC card authentication unit 110 authenticates the IC card 300.
- the IC card authentication unit 110 includes a response verifier 111 and an IC card key table 112.
- the response verifier 111 verifies whether the response to the challenge generated by the IC card 300 is correct.
- the response verifier 111 has the same mechanism as the response generation mechanism in the IC card 300.
- the IC card key table 112 holds key information necessary for authenticating the IC card 300.
- the IC card key table 112 holds an IC card key ID and IC card key information for each IC card key.
- the IC card key ID is an ID for identifying the IC card key.
- the IC card key information is key information necessary for authenticating a secret key stored in the IC card.
- the coupon data management unit 120 manages coupon data and service definitions.
- the coupon data is unique data in which information necessary for authentication of the IC card 300 is defined for each terminal 200.
- the coupon data is a data string having a challenge and an ID tokenization key.
- the IDcd authentication server 100 may provide a plurality of coupon data to the terminal 200 in a lump.
- the IDcd authentication server 100 generates and provides the terminal 200 with each request sent in response to the authentication at the terminal 200. Also good.
- the coupon ticket data management unit 120 includes a coupon ticket data generator 121 and a coupon ticket table 122.
- the coupon data generator 121 generates coupon data based on a predetermined rule.
- the coupon ticket table 122 manages the terminal 200 accessing the IC card 300 and holds data necessary for generating coupon ticket data for each terminal 200. More specifically, the coupon ticket table 122 holds a terminal ID, initial coupon data, coupon data derivation key, current usage count, current payout count, and final coupon data.
- the terminal ID is an ID for identifying the terminal 200.
- Initial coupon data is the first key from which coupon data is derived.
- the coupon data derivation key is a key for deriving and generating the next coupon data from the coupon data.
- the current use count is a count indicating how many coupon tickets have been used so far.
- the current number of payouts is the number indicating how many coupon data have been paid out so far.
- the final coupon data is the coupon ticket data that was last authenticated.
- the communication data restoration unit 130 restores data encrypted from the terminal 200 according to a predetermined rule.
- the communication data restoration unit 130 includes a tokenized IDcd restoration unit 131 and a hash generation 132.
- the tokenized IDcd restorer 131 restores the tokenized IDcd.
- the IDcd authentication server 100 holds a service definition table 123 that manages the service provider 400.
- the service definition table 123 manages the service provider and holds a list of terminals used by the service provider and the types of IC card keys to be accepted.
- the service definition table 123 holds a service ID, a terminal ID list, and a key ID list for each service provider 400.
- the service ID is an ID for identifying a service provider.
- the terminal ID list is a terminal ID list of terminals used by service providers.
- the key ID list is an IC card key ID list of IC card keys that can be accepted by each terminal.
- the external communication unit 140 executes communication processing using an arbitrary communication protocol with an external device of the IDcd authentication server 100.
- Example 1 As a first embodiment, an example is shown in which a plurality of coupon data is sent in advance for each terminal, and a response is transmitted to the IDcd authentication server 100 each time the IC card 300 is deceived for authentication. Assuming the case where the terminal 200 is not secure, the case where the terminal 200 obtains the coupon ticket data from the IDcd authentication server 100 via the service provider 400 every time the IC card 300 is tapped is also applicable.
- FIG. 3 is a flowchart showing an operation example of the IDcd authentication server 100 and the IC card 300.
- the IC card key information is transferred from the IC card 300 to the IDcd authentication server 100. Transmit (step S101).
- authentication of the registrant holding the IC card 300 and encryption of a communication path with the IDcd authentication server 100 are performed as necessary.
- the IDcd authentication server 100 registers the IC card key information transmitted from the IC card 300 in the IC card key table 112, and returns the IC card key ID to the IC card 300 (step S102).
- the IC card key ID may be managed by the user of the IC card 300 by some method.
- the IC card key ID may be stored inside the information communication device held by the user of the IC card 300.
- FIG. 4 is a flowchart showing an operation example of the IDcd authentication server 100 and the terminal 200.
- the terminal 200 sends a request for registration to the IDcd authentication server 100 at a predetermined timing (step S111). At this time, authentication of the registrant and encryption of the communication path with the IDcd authentication server 100 are performed as necessary.
- the IDcd authentication server 100 assigns a unique terminal ID, and generates initial coupon data and coupon data derivation key for the terminal ID.
- the IDcd authentication server 100 assigns the generated initial coupon ticket data to the initial coupon ticket data and the final coupon data in the coupon table 122.
- the IDcd authentication server 100 assigns the generated coupon data derivation key to the coupon data derivation key in the coupon table 122. Further, the IDcd authentication server 100 sets the number of the current use count and the current payout count in the coupon ticket table 122 to 0. The IDcd authentication server 100 provides the terminal ID to the terminal 200 (step S112). The terminal 200 holds the current use count in addition to the terminal ID and a coupon ticket data list to be described later. The initial value of the current usage count is set to 0.
- FIG. 5 is a flowchart showing an operation example of the IDcd authentication server 100 and the service provider 400.
- the service provider 400 sends a request for registering the service definition in the IDcd authentication server 100 (step S121). At this time, the identity of the registrant and encryption of the communication path with the IDcd authentication server 100 are performed as necessary.
- the service provider 400 transmits a terminal ID list and an IC card key ID list to the IDcd authentication server 100.
- the IDcd authentication server 100 assigns a unique service ID and registers information in the service definition table 123.
- the IDcd authentication server 100 provides the numbered service ID to the service provider 400 (step S122).
- the service provider 400 notifies the service ID and the IC card key ID list to the terminal 200 that uses the service (the terminal 200 corresponding to the terminal ID included in the terminal ID list) (step S123).
- FIG. 6 is a flowchart illustrating an operation example of the IDcd authentication server 100, the terminal 200, and the service provider 400.
- the service provider 400 requests the IDcd authentication server 100 to pay out the coupon data list for each terminal 200 that wants to pay out the coupon data list (step S131).
- the service provider 400 transmits to the IDcd authentication server 100 information about its own service ID, the terminal ID of the terminal that pays out the coupon ticket data list, and the coupon ticket payout count.
- the IDcd authentication server 100 uses the coupon ticket data generator 121 to generate coupon ticket data for the number of coupon tickets that have been input in the following procedure.
- the IDcd authentication server 100 specifies the terminal ID of the coupon ticket table from the terminal ID input from the service provider 400.
- the IDcd authentication server 100 inputs the final coupon data and the coupon data derivation key to the coupon data generator 121 to generate new coupon data.
- the IDcd authentication server 100 outputs the current number of payouts and the generated coupon data list to the service provider 400, and adds the current number of payouts in the coupon ticket table 122 by the number of payouts (step S132).
- the service provider 400 transfers the current payout count and coupon data list acquired from the IDcd authentication server 100 to the terminal 200 corresponding to the terminal ID (step S133).
- the terminal 200 corresponding to the terminal ID adds the acquired coupon data list to the coupon data list held by itself.
- FIG. 7 is a flowchart showing an operation example of the service provider 400, the terminal 200, and the IC card 300.
- the terminal 200 obtains the following card response each time the IC card 300 is tapped and the IC card 300 needs to be authenticated.
- the terminal 200 extracts the youngest data from the coupon data list held, deletes the coupon data from the coupon data list, and increments the current use count by one.
- the terminal 200 extracts the challenge and the ID tokenization key from the extracted coupon data. For example, the first 8 bytes or 16 bytes of the coupon ticket data are challenged, and the next 8 bytes are used as an ID tokenization key.
- the definition of the challenge and the ID tokenization key is not limited to this example.
- the terminal 200 specifies the IC card key ID to be used by using information determined for each IC card key ID when the IC card 300 is fraudulent. At this time, the terminal 200 issues a one-side authentication command for the IC card 300. At that time, the terminal 200 inputs a challenge to the IC card 300 by proximity contactless communication (step S141), and acquires an IDcd from the IC card 300 and a response generated by the IC card 300 in response to the challenge (step S142). ).
- FIG. 8 is an explanatory diagram for explaining processing in the IC card 300.
- the IC card 300 acquires a challenge from the terminal 200
- the IC card 300 performs a predetermined operation using the IC card key information and IDcd held therein, and generates a response to the challenge. Then, the IC card 300 outputs the IDcd and the response generated for the challenge.
- the terminal 200 generates a tokenized IDcd for the IDcd authentication server 100 using the ID tokenization key.
- the terminal 200 generates a tokenized IDcd by taking an exclusive OR with the IDcd and the ID tokenization key.
- the method for generating the tokenized IDcd is not limited to this example.
- the terminal 200 generates an encrypted response for the response or the like using a predetermined encryption method such as SSL (Secure Sockets Layer).
- the terminal 200 transmits the generated information to the service provider 400 (Step S143).
- the terminal 200 transmits the terminal ID, tokenized IDcd, response, current usage count, and IC card key ID to the service provider 400.
- FIG. 9 is a flowchart showing an operation example of the IDcd authentication server 100 and the service provider 400.
- the service provider 400 transmits the response information acquired from the terminal 200 to the IDcd authentication server 100 and requests authentication that the response is correct (step S151).
- the service provider 400 transmits the service ID, the terminal ID, the tokenized IDcd, the response, the current use count, and the IC card key ID to the IDcd authentication server 100.
- the IDcd authentication server 100 uses the coupon data management unit 120 to generate coupon data according to the following procedure. First, the IDcd authentication server 100 specifies the data in the coupon ticket table 122 from the terminal ID input from the service provider 400 and acquires the final coupon data. Next, the IDcd authentication server 100 generates coupon data from the current usage count input from the service provider 400. The generation is not repeated from the initial coupon data in the coupon table 122 by the number of current usages input from the service provider 400, but the number of differences from the current usage in the coupon table 122 is the final number. The generation of coupon data is repeated from the coupon data using the coupon data generator 121.
- the IDcd authentication server 100 decrypts the received data at the communication data restoration unit 130 using the input response information and the coupon data generated by the coupon data generator 121. First, the IDcd authentication server 100 acquires a challenge and a tokenization key from the coupon data generated by the coupon data generator 121. Next, the IDcd authentication server 100 inputs the IDcd and the tokenized key to the tokenized IDcd decompressor 131 and acquires the IDcd.
- the IDcd authentication server 100 uses the response information input from the service provider 400, the coupon data generated by itself, and the information decrypted by itself to receive a response input from the service provider 400.
- the IC card authenticating unit 110 authenticates the correctness. Specifically, the IDcd authentication server 100 performs authentication by the following procedure. First, the IDcd authentication server 100 acquires IC card key information from the input IC card key ID. Next, the IDcd authentication server 100 inputs the restored IDcd, the challenge generated by itself, and the IC card key information to the response verifier 111 to generate a response, and compares the response with the response input from the service provider 400. To determine whether they are the same.
- the IDcd authentication server 100 regards what is held over the terminal 200 as a correct IC card and IDcd.
- the IDcd authentication server 100 sets the coupon ticket data generated by itself as the final coupon data, and sets the current usage count as the input current usage count. On the other hand, if they do not match, the IDcd authentication server 100 does not perform the subsequent processing and returns a predetermined error message indicating that there is a mismatch to the service provider 400.
- FIG. 10 is an explanatory diagram for explaining processing of the IC card authentication unit 110.
- the IC card authentication unit 110 refers to the IC card key table 112 from the IC card key ID and extracts target IC card key information. Then, the IC card authenticating unit 110 inputs the restored IDcd, the challenge generated by itself, and the IC card key information to the response verifier 111 to generate a response.
- the coupon ticket data is additionally acquired from the IDcd authentication server 100 when it is insufficient.
- the terminal 200 requests the service provider 400 to add coupon ticket data.
- the service provider 400 inputs the service ID, the terminal ID, and the coupon ticket payout number to the IDcd authentication server 100 and requests the IDcd authentication server 100 to additionally generate coupon ticket data.
- the IDcd authentication server 100 performs the same processing as the above-described coupon ticket data list payout processing, and provides the generated coupon ticket data to the service provider 400.
- the service provider 400 transfers the coupon ticket data acquired from the IDcd authentication server 100 to the terminal 200 that has requested the addition of coupon ticket data.
- Example 2 As a next embodiment, an example in which a challenge and a response corresponding to IDcd are paid out in advance when the list of IDcd of the IC card held over the terminal 200 is known in advance will be described.
- FIG. 11 is a flowchart illustrating an operation example of the IDcd authentication server 100, the service provider 400, and the terminal 200.
- the service provider 400 transmits the IDcd list of the IC card 300 to be held over the terminal 200 to the IDcd authentication server 100 (step S201).
- the service provider 400 transmits a list of service IDs and IDcd information (including IDcd and IC card key ID) to the IDcd authentication server 100.
- the IC card authentication unit 110 of the IDcd authentication server 100 acquires IC card key information from the IC card key ID.
- the IC card authenticating unit 110 also generates a challenge. This challenge is generated by random number generation or the like.
- the response verifier 111 of the IDcd authentication server 100 inputs IDcd, IC card key information, and a challenge, and acquires a response. This is repeated for the number of IDcd information lists.
- the IDcd authentication server 100 returns the generated list to the service provider 400 (step S202). Specifically, the IDcd authentication server 100 transmits a list of service IDs and IDcd information (including IDcd, IC card key ID, challenge, and response).
- the service provider 400 transmits the list received from the IDcd authentication server 100 to the terminal 200 (step S203).
- the terminal 200 holds a list sent from the service provider 400.
- FIG. 12 is a flowchart showing an operation example of the terminal 200 and the IC card 300.
- the terminal 200 acquires the IDcd of the IC card 300 by proximity contactless communication (step S211).
- the terminal 200 issues a one-side authentication command of the IC card 300 by holding a challenge corresponding to the IDcd with information specified by the IC card key ID (step S212). ), A response is acquired from the IC card 300 (step S213).
- the terminal 200 confirms whether the response corresponding to the IDcd and the response received from the IC card 300 are the same. In the same case, the terminal 200 regards the fraudulent IC card 300 as the correct IC card and IDcd, and executes the subsequent processing. If they are different, the terminal 200 executes predetermined error processing.
- the terminal 200 generates a challenge to be input to the IC card 300, and the IDcd authentication server 100 proves that the response is a result input to the challenge and the IC card. explain.
- FIG. 13 is a flowchart showing an operation example of the service provider 400, the terminal 200, and the IC card 300.
- the terminal 200 first generates a challenge to be input to the IC card 300.
- the terminal 200 generates a request sentence that combines the service ID, the terminal ID, the IC card key ID, the current usage count, and an arbitrary text.
- FIG. 14 is an explanatory diagram illustrating a structure of a request sentence generated by the terminal 200.
- the terminal 200 generates a hash for the generated request statement.
- the terminal 200 increments the current usage count by one.
- the terminal 200 When the IC card 300 is inserted into the terminal 200, the terminal 200 issues a one-side authentication command of the IC card 300 with information specified by the IC card key ID. At that time, the terminal 200 inputs the generated hash as a challenge to the IC card 300 by proximity contactless communication (step S301), and acquires the IDcd and response from the IC card 300 by proximity contactless communication (step S302).
- the terminal 200 transmits the generated request sentence and the IDcd and response acquired from the IC card 300 to the service provider 400 (step S303).
- FIG. 15 is a flowchart showing an operation example of the IDcd authentication server 100 and the service provider 400.
- the service provider 400 requests the IDcd authentication server 100 to authenticate whether the response is correct (step S311). At this time, the service provider 400 transmits a request statement, IDcd, and response to the IDcd authentication server 100.
- the IDcd authentication server 100 uses the hash generator 132 to generate a hash from the received request sentence and sets it as a challenge. Furthermore, the IDcd authentication server 100 extracts the service ID, the terminal ID, the IC card key ID, and the current usage count from the received request text. Subsequently, the coupon data management unit 120 of the IDcd authentication server 100 refers to the service definition table 123 and confirms whether or not the extracted IC card key ID is in the IC card key ID list corresponding to the service ID. . Subsequently, the IC card authentication unit 110 specifies IC card key information corresponding to the IC card key ID from the IC card key table 112.
- the IDcd authentication server 100 uses the response verifier 111 to input IDcd, challenge, and IC card key information, and generates a response. Then, the IDcd authentication server 100 transmits an authentication result using the generated response to the service provider 400 (step S312). When the received response is equal to the generated response, the IDcd authentication server 100 considers that the received response is generated by inputting a request statement to the IC card 300 specified by the IDcd.
- FIG. 16 is a flowchart illustrating an operation example of the IDcd authentication server 100, the service provider 400, and the other provider 500.
- Other business operator 500 receives the request text, the IDcd, and the response from service business operator 400 (step S321).
- the other business operator 500 transmits a request statement, an IDcd, and a response to the IDcd authentication server 100 (step S322).
- the IDcd authentication server authenticates the response received from the other business operator 500 and returns the result to the other business operator 500 as in the case of the card response authentication.
- Example 4 As a fourth embodiment, a description will be given of an embodiment for the purpose of enhancing tolerance when the network is disconnected and improving response performance in network communication.
- a pair of challenge and response is stored in advance as a cache in the server of the service provider 400. Thereby, the next authentication can be completed between the service provider 400 and the terminal 200, and even if the network between the service provider server and the IDcd authentication server 100 is disconnected, the service provider 400 and the terminal 200 can be implemented.
- FIG. 17 is a flowchart showing an operation example of the IDcd authentication server 100, the service provider 400, the terminal 200, and the IC card 300.
- the terminal 200 periodically sends out polling (step S401).
- This polling includes a Request Service command for acquiring IDm (information unique to the IC card 300) and a key version from the IC card 300.
- IDm information unique to the IC card 300
- key version from the IC card 300.
- the terminal 200 transmits the terminal ID of its own device and the IDm and key version acquired from the IC card 300 in step S402 to the server of the service provider 400 (step S403).
- the server of the service provider 400 selects an authentication key based on the terminal ID of the terminal 200 received from the terminal 200, the IDm of the IC card 300, and the key version (step S404), and receives the IDcd authentication server 100 from the terminal 200.
- the transferred information is transferred (step S405).
- the IDcd authentication server 100 generates a challenge and a response based on information received from the server of the service provider 400 (step S406). Then, the IDcd authentication server 100 pays out the generated challenge and response to the server of the service provider 400 (step S407).
- the server of the service provider 400 provides the challenge and response paid out from the IDcd authentication server 100 to the terminal 200 (step S408).
- the terminal 200 transmits a challenge to the IC card 300 to authenticate the fraudulent IC card 300 (step S409), and the IC card 300 generates a response to the challenge and returns it to the terminal 200 (step S410).
- the terminal 200 compares the response acquired from the server of the service provider 400 with the response generated by the IC card 300 (step S411), and authenticates the IC card 300 (step S412).
- the server of the service provider 400 transfers the information received from the terminal 200 to the IDcd authentication server 100 in order to obtain in advance a challenge / response for the next authentication of the IC card 300 (step S413).
- the IDcd authentication server 100 generates a challenge and a response based on the information received from the server of the service provider 400 (step S414).
- the IDcd authentication server 100 pays out the generated challenge and response to the server of the service provider 400 (step S415).
- the server of the service provider 400 pre-caches the challenge and response paid out from the IDcd authentication server 100 (step S416).
- the service provider 400 and the terminal 200 can be completed at the next authentication of the IC card 300. This will be described below.
- the terminal 200 periodically sends out polling (step S417).
- This polling includes a Request Service command for acquiring IDm and key version from the IC card 300.
- the IC card 300 When receiving the polling transmitted from the terminal 200, the IC card 300 returns the IDm and the key version to the terminal 200 in response to the Request Service command (step S418).
- the terminal 200 transmits its own terminal ID and the IDm and key version acquired from the IC card 300 in step S402 to the server of the service provider 400 (step S419).
- the server of the service provider 400 selects an authentication key based on the terminal ID of the terminal 200, the IDm of the IC card 300, and the key version received from the terminal 200 (step S420).
- the server of the service provider 400 has transferred the information received from the terminal 200 to the IDcd authentication server 100 at the time of the first authentication, but here, the challenge that has been paid out from the IDcd authentication server 100 in step S416 in advance. Since the response and the response are pre-cached, the challenge and response are selected from the pre-cached challenge and response (step S421).
- the server of the service provider 400 provides the challenge and response selected from the pre-cached challenge and response to the terminal 200 (step S422).
- the terminal 200 transmits a challenge to the IC card 300 to authenticate the fraudulent IC card 300 (step S423), and the IC card 300 generates a response to the challenge and returns it to the terminal 200 (step S424).
- the terminal 200 compares the response acquired from the server of the service provider 400 with the response generated by the IC card 300 (step S425), and authenticates the IC card 300 (step S426).
- the server of the service provider 400 transfers the information received from the terminal 200 to the IDcd authentication server 100 in order to obtain in advance a challenge / response for the next authentication of the IC card 300 (step S427).
- the IDcd authentication server 100 generates a challenge and a response based on the information received from the server of the service provider 400 (step S428). Then, the IDcd authentication server 100 pays out the generated challenge and response to the server of the service provider 400 (step S429).
- the server of the service provider 400 pre-caches the challenge and response issued from the IDcd authentication server 100 (step S430).
- the challenge and response pre-cached by the server of the service provider 400 are used, so that the exchange of the authentication of the IC card 300 between the service provider 400 and the terminal 200 is performed. It can be completed.
- the IC card 300 when the IC card 300 is authenticated, there is a problem in communication between the server of the service provider 400 and the IDcd authentication server 100 by using the challenge and response pre-cached by the server of the service provider 400 in advance. Even when data cannot be normally exchanged, the IC card 300 can be authenticated.
- FIG. 18 is a flowchart showing an operation example of the IDcd authentication server 100, the service provider 400, the terminal 200, and the IC card 300.
- the terminal 200 periodically sends out polling (step S431).
- This polling includes a Request Service command for acquiring IDm and key version from the IC card 300.
- the IC card 300 When receiving the polling sent from the terminal 200, the IC card 300 returns the IDm and the key version to the terminal 200 in response to the Request Service command (step S432).
- the terminal 200 transmits its own terminal ID and the IDm and key version acquired from the IC card 300 in step S402 to the server of the service provider 400 (step S433).
- the server of the service provider 400 selects an authentication key based on the terminal ID of the terminal 200, the IDm of the IC card 300, and the key version received from the terminal 200 (step S434).
- the server of the service provider 400 transfers the information received from the terminal 200 to the IDcd authentication server 100, but there is a problem in communication between the server of the service provider 400 and the IDcd authentication server 100. Assume that there is a situation where data cannot be exchanged normally.
- the server of the service provider 400 selects a challenge and response from the pre-cached challenge and response (step S435).
- the server of the service provider 400 provides the challenge and response selected from the pre-cached challenge and response to the terminal 200 (step S436).
- the terminal 200 transmits a challenge to the IC card 300 to authenticate the fraudulent IC card 300 (step S437), and the IC card 300 generates a response to the challenge and returns it to the terminal 200 (step S438).
- the terminal 200 compares the response acquired from the server of the service provider 400 with the response generated by the IC card 300 (step S439), and authenticates the IC card 300 (step S440).
- the server of the service provider 400 deletes the pre-cached challenge and response, and a new challenge is received from the IDcd authentication server 100. And a response may be acquired.
- the server of the service provider 400 may delete the pre-cached challenge and response when a predetermined time has elapsed. This prevents too old challenges and responses from being used for authentication. For example, the server of the service provider 400 may delete periodically pre-cached challenges and responses. Further, the server of the service provider 400 may delete the pre-cached challenge and response when the predetermined timing is reached.
- the server of the service provider 400 may pre-cache challenges and responses for the reserved number of people in advance. Good. Then, the server of the service provider 400 may delete the pre-cached challenge and response when the departure time has passed. Therefore, the IDcd authentication server 100 may add expiration date information when generating a challenge and a response. Further, the server of the service provider 400 may add expiration date information when pre-caching the challenge and response.
- the server of the service provider 400 can perform authentication by the IC card 300 without performing communication with the IDcd authentication server 100. Furthermore, the server of the service provider 400 can delete the challenge and response that are not required and have been pre-cached, thereby preventing the challenge and response from leaking and improving security.
- Example 5 As a fifth embodiment, a description will be given of an embodiment for the purpose of countermeasures against illegal remittance such as MITB (Man In The Browser) countermeasures using authentication by an IC card.
- MITB Man In The Browser
- FIG. 19 is an explanatory diagram showing a state in which the settlement side changes the settlement amount due to fraud. Actually, you are shopping for 1000 yen. If the user confirms the payment amount and presses the “Accept” button or inputs a predetermined security code, the card is placed on the reader / writer and the 1000 yen is paid. Settlement is performed. However, if the settlement side actually sets the settlement amount at 10,000 yen, the transaction information sent from the store to the settlement server becomes a transaction of 10,000 yen, and the settlement server (service provider) 400 servers), a settlement of 10,000 yen is made.
- the settlement server service provider
- FIG. 20 is an explanatory diagram showing a mechanism aimed at preventing fraud on the settlement side.
- the mPOS terminal barcodes the date and purchase amount, hashs the barcode information, and transmits an Authentication1 command from the reader / writer (terminal 200) to the IC card 300.
- the purchaser of the product inputs a predetermined security code to the mPOS terminal, and then puts the IC card 300 on the reader / writer (terminal 200). Thereby, the IC card 300 generates a response according to the Authentication1 command.
- the purchaser of the merchandise makes a payment by placing an EMV card such as a credit card having a non-contact communication function on the reader / writer.
- the settlement side performs a fraud that maliciously changes the settlement amount to 10,000 yen
- the settlement amount of the transaction information becomes 10,000 yen and is sent to the settlement server.
- the settlement server can detect the mismatch of the settlement amount by comparing the response with the transaction information. It becomes.
- the response and transaction information may be collated by the IDcd authentication server 100 instead of the settlement server.
- the settlement server receives the collation result by the IDcd authentication server 100 and executes the settlement process when it is determined that the settlement amount is the same. It will be.
- Example 6 As a sixth embodiment, an embodiment for the purpose of safe and simple remittance between individuals using authentication by an IC card will be described.
- FIG. 21 is an explanatory diagram for explaining a remittance process between individuals using authentication by an IC card.
- the first user's terminal 200 transmits a challenge including a hash of transaction information to the first user's IC card 300.
- the first user's IC card 300 generates a response to the challenge received from the first user's terminal 200.
- This response includes a signature of transaction information indicating that 1000 yen is transferred from the first user to the second user.
- the first user terminal 200 transmits the response generated by the first user IC card 300 to the second user terminal 200.
- the second user's IC card 300 When the second user's terminal 200 receives the response generated by the first user's IC card 300, the second user's IC card 300 includes the first user's IC card included in the response to the second user's IC card 300. A hash of transaction information with a signature of 300 is sent as a challenge. The second user's IC card 300 generates a response to the challenge received from the second user's terminal 200. This response includes a signature of transaction information indicating that 1000 yen is transferred from the first user to the second user. Then, the second user terminal 200 transmits the response generated by the second user IC card 300 to the settlement server.
- the settlement server receives the response generated by the IC card 300 of the first user and the response generated by the IC card 300 of the second user.
- the settlement server transmits both responses to the IDcd authentication server 100.
- the IDcd authentication server 100 collates two responses received from the settlement server, and confirms the authenticity of the two IC cards 300 and confirms the validity of the signature of the transaction information. Note that the IDcd authentication server 100 only checks the authenticity of the IC card 300 and the validity of the signature of the transaction information, and does not know the content of the transaction information.
- the IDcd authentication server 100 can confirm that the two responses received from the settlement server are valid, the IDcd authentication server 100 sends a message to the settlement server to permit the remittance from the first user to the second user. send.
- the settlement server receives a message from the IDcd authentication server 100 indicating that the remittance from the first user to the second user is permitted, the settlement server remits 1000 yen from the first user account to the second user account. Execute the process.
- Such a series of processing enables safe and simple remittance between individuals using authentication by IC card.
- An IDcd authentication server 100 that can perform authentication can be provided.
- each step in the processing executed by each device in this specification does not necessarily have to be processed in chronological order in the order described as a sequence diagram or flowchart.
- each step in the processing executed by each device may be processed in an order different from the order described as the flowchart, or may be processed in parallel.
- IC cards may be portable terminals, such as a smart phone provided with IC chip which has a non-contact communication function.
- a providing unit that provides authentication data for authentication of the wireless communication device to a terminal that performs proximity contactless communication with the wireless communication device including the IC chip; An acquisition unit for acquiring received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal; An authentication unit that authenticates the wireless communication device using the authentication data and the received data; Comprising a server.
- the server according to (1) wherein the providing unit provides a plurality of the authentication data to the terminal in advance prior to authentication of the wireless communication device.
- the server according to (1) or (2), wherein the authentication data provided by the providing unit is generated based on authentication data at the time of last authentication.
- the providing unit includes a set of a challenge to be provided from the terminal to the wireless communication device at the time of authentication of the wireless communication device to be authenticated and a response returned from the wireless communication device to the terminal in response to the challenge.
- the server according to any one of (1) to (3), which is provided to the terminal prior to authentication of the wireless communication device.
- the authentication unit uses the first reception data from the first wireless communication device and the second reception data from the second wireless communication device to use the first wireless communication device and the second wireless communication device.
- the server according to any one of (1) to (4), wherein authentication of the communication device is performed.
- the authentication unit transfers money between a user of the first wireless communication device and a user of the second wireless communication device based on an authentication result of the first wireless communication device and the second wireless communication device.
- the server according to (5) which determines whether or not processing is possible.
- the wireless communication device is an IC card incorporating an IC chip.
- the wireless communication device is a portable terminal incorporating an IC chip.
- the server according to any one of (10) to (15), wherein the wireless communication device is an IC card incorporating an IC chip.
- the wireless communication device is a portable terminal incorporating an IC chip.
- a wireless communication device including an IC chip; A terminal that performs proximity contactless communication with the wireless communication device; A server for providing authentication data for authentication of the wireless communication device to the terminal; With The server A providing unit for providing the authentication data; An acquisition unit for acquiring received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal; An authentication unit that authenticates the wireless communication device using the authentication data and the received data;
- An authentication system comprising:
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Signal Processing (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Software Systems (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
[Problem] To provide a service which allows for the secure authentication of an IC card when using the IC card, which is designed for offline use, in a mode in which value is held in the server. [Solution] Provided is a server comprising: a provision unit which provides authentication data for authenticating a wireless communication device, which is provided with an IC chip, to a terminal which carries out proximity non-contact communication with the wireless communication device; an acquisition unit which acquires reception data that is received from the terminal via proximity non-contact communication with the wireless communication device, including a usage count of the authentication data; and an authentication unit which carries out authentication of the wireless communication device using the authentication data and the reception data.
Description
本開示は、サーバ及び認証方法に関する。
This disclosure relates to a server and an authentication method.
近接非接触通信によって通信するICカードにバリューを持たせることが広く行われてきている(例えば特許文献1等参照)。その際、オフラインでサービスを提供するために、セキュアにバリューを保持するICカードと、そのバリューを操作するためのタンパ耐性をもったセキュアな端末とを活用してきた。一方、昨今、ネットワークが普及し、サーバにバリューを保持する形態が増え、正しいカードであることを確認することでサーバのバリューの持ち主であることを認証するICカードの利用形態が考えられる。
It has been widely performed to give value to an IC card that communicates by proximity non-contact communication (see, for example, Patent Document 1). At that time, in order to provide a service offline, an IC card that securely holds a value and a secure terminal having tamper resistance for operating the value have been utilized. On the other hand, in recent years, networks have become widespread, and the number of forms that hold values in the server has increased, and a use form of an IC card that authenticates the owner of the value of the server by confirming that the card is correct can be considered.
オフラインで利用することを想定したICカードを、サーバにバリューを保持した形態に流用する場合にはICカードの認証において考慮すべき点がある。
When using an IC card that is assumed to be used offline in a form that retains value in the server, there are points to consider in IC card authentication.
そこで、本開示では、オフラインで利用することを想定したICカードを、サーバにバリューを保持した形態に流用する際に、安全にICカードの認証を行うことが可能な、新規かつ改良されたサーバ及び認証方法を提案する。
Therefore, in the present disclosure, a new and improved server that can securely authenticate an IC card when diverting an IC card that is assumed to be used offline to a form in which a value is stored in the server. And an authentication method.
本開示によれば、ICカードとの間で近接非接触通信を行う端末に対して該ICカードの認証のための認証データを提供する提供部と、前記端末から、前記認証データの利用回数を含んだ、前記ICカードとの間の近接非接触通信により受信した受信データを取得する取得部と、前記認証データと前記受信データとを用いて前記ICカードの認証を行う認証部と、を備える、サーバが提供される。
According to the present disclosure, a providing unit that provides authentication data for authentication of the IC card to a terminal that performs proximity contactless communication with the IC card, and the number of times the authentication data is used from the terminal. An acquisition unit that acquires reception data received by proximity contactless communication with the IC card, and an authentication unit that authenticates the IC card using the authentication data and the reception data. A server is provided.
また本開示によれば、ICカードとの間で近接非接触通信を行う端末に対して該ICカードの認証のための認証データを提供することと、前記端末から、前記認証データの利用回数を含んだ、前記ICカードとの間の近接非接触通信により受信した受信データを取得することと、前記認証データと前記受信データとを用いて前記ICカードの認証を行うことと、を含む、認証方法が提供される。
According to the present disclosure, the authentication data for authentication of the IC card is provided to a terminal that performs proximity contactless communication with the IC card, and the number of times the authentication data is used from the terminal. Including receiving received data received by proximity non-contact communication with the IC card, and authenticating the IC card using the authentication data and the received data. A method is provided.
以上説明したように本開示によれば、オフラインで利用することを想定したICカードを、サーバにバリューを保持した形態に流用する際に、安全にICカードの認証を行うことが可能な、新規かつ改良されたサーバ及び認証方法を提供することが出来る。
As described above, according to the present disclosure, when an IC card that is assumed to be used offline is diverted to a form in which a value is stored in a server, the IC card can be safely authenticated. An improved server and authentication method can be provided.
なお、上記の効果は必ずしも限定的なものではなく、上記の効果とともに、または上記の効果に代えて、本明細書に示されたいずれかの効果、または本明細書から把握され得る他の効果が奏されてもよい。
Note that the above effects are not necessarily limited, and any of the effects shown in the present specification, or other effects that can be grasped from the present specification, together with or in place of the above effects. May be played.
以下に添付図面を参照しながら、本開示の好適な実施の形態について詳細に説明する。なお、本明細書及び図面において、実質的に同一の機能構成を有する構成要素については、同一の符号を付することにより重複説明を省略する。
Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, in this specification and drawing, about the component which has the substantially same function structure, duplication description is abbreviate | omitted by attaching | subjecting the same code | symbol.
なお、説明は以下の順序で行うものとする。
1.本開示の実施の形態
1.1.概要
1.2.構成例
1.3.動作例
2.まとめ The description will be made in the following order.
1. Embodiment of the present disclosure 1.1. Outline 1.2. Configuration example 1.3. Example of operation Summary
1.本開示の実施の形態
1.1.概要
1.2.構成例
1.3.動作例
2.まとめ The description will be made in the following order.
1. Embodiment of the present disclosure 1.1. Outline 1.2. Configuration example 1.3. Example of operation Summary
<1.本開示の実施の形態>
[1.1.概要]
まず、本開示の実施の形態について説明する前に、本開示の実施の形態に至った経緯を説明する。 <1. Embodiment of the present disclosure>
[1.1. Overview]
First, before explaining the embodiment of the present disclosure, the background to the embodiment of the present disclosure will be described.
[1.1.概要]
まず、本開示の実施の形態について説明する前に、本開示の実施の形態に至った経緯を説明する。 <1. Embodiment of the present disclosure>
[1.1. Overview]
First, before explaining the embodiment of the present disclosure, the background to the embodiment of the present disclosure will be described.
オフラインでサービスを提供するために、セキュアにバリューを保持するICカードと、そのバリューを操作するためのタンパ耐性をもったセキュアな端末とを活用してきた。一方、昨今、ネットワークが普及し、サーバにバリューを保持する形態が増え、正しいカードであることを確認することでサーバのバリューの持ち主であることを認証するICカードの利用形態が考えられる。
In order to provide offline services, IC cards that securely store values and secure terminals with tamper resistance for operating those values have been used. On the other hand, in recent years, networks have become widespread, and the number of forms that hold values in the server has increased, and a use form of an IC card that authenticates the owner of the value of the server by confirming that the card is correct can be considered.
従来オフラインで利用することを想定したICカードを、サーバにバリューを保持した形態に流用する場合に以下に示す点をクリアにする必要がある。
The following points need to be cleared when an IC card that is assumed to be used offline in the past is diverted to a form that retains value in the server.
ICカードとの相互認証に、多くの通信が発生し、端末の実装が煩雑となっていた。
A lot of communication occurred in mutual authentication with the IC card, and the implementation of the terminal was complicated.
もし秘匿の鍵が漏えいしたとしても検知できず、漏えいされた鍵を使っているのか、そうでないのかの区別ができず、サービス継続を止めるべきかどうかが分からなかった
Even if the secret key was leaked, it could not be detected, it was not possible to distinguish whether the leaked key was used or not, and it was not known whether the service continuation should be stopped
また、ICカードが正しいことを判別するために、端末側に秘匿の鍵とそれを格納するセキュアチップが必要であり、端末側のコスト増や管理の煩雑さに繋がっていた。また、サーバ側に秘匿の鍵やセキュアチップを配置したとしても、多くの通信が必要となるため、通信経路上のサーバや端末の開発コストがかさんでいた。既存の環境によっては、専用の通信路を別途設ける必要があった。
Also, in order to determine whether the IC card is correct, a secret key and a secure chip for storing it are necessary on the terminal side, leading to increased costs on the terminal side and complicated management. Further, even if a secret key or a secure chip is arranged on the server side, a lot of communication is required, so that the development cost of the server or terminal on the communication path is high. Depending on the existing environment, it was necessary to provide a dedicated communication path separately.
セキュアチップを利用してICカードおよびそのIDcdが正しいことを判別したとしても、その結果の転送を受けつけた別の人やシステムは、それが正しいかどうか判別できず、転送元を信じるしかなかった。
Even if it was determined that the IC card and its IDcd were correct using a secure chip, another person or system that accepted the transfer of the result could not determine whether it was correct and had to believe the transfer source. .
判別したICカードおよびそのIDcdを使った各サービスの兌換性やセキュリティ保護レベルに関わらず、秘匿の鍵とセキュアチップは高度に保護する必要があった。
Regardless of the convertibility and security protection level of each service using the identified IC card and its IDcd, the secret key and the secure chip had to be highly protected.
新たにICカードおよびIDcdの証明が必要となった場合、証明のための専用のICカードやIDcdの発行を行っていた。加えて、ICカードの秘匿の鍵を格納したセキュリティチップおよびリーダライタを各端末に都度用意する必要があった。
When a new IC card and IDcd certification was required, a dedicated IC card and IDcd were issued for certification. In addition, it is necessary to prepare a security chip and a reader / writer each storing a secret key for an IC card in each terminal.
そこで本件開示者は、上述した点をクリアにするための技術について鋭意検討を行った。その結果、本件開示者は、以下で説明するように、オンラインだけでなく、オフラインで利用することを想定したICカードを、サーバにバリューを保持した形態に流用する際に、安全にICカードの認証を行うことが可能となる技術を考案するに至った。
Therefore, the present disclosure person has intensively studied a technique for clearing the above-described points. As a result, as described below, the present disclosing person can safely use the IC card when diverting the IC card that is assumed to be used not only online but also offline to a form that retains value in the server. It came to devise the technology that enables authentication.
[1.2.構成例]
図1は、本開示の実施の形態に係る認証システムの構成例を示す説明図である。このシステムでは、サーバにバリューを保持する形態が増え、正しいカードであることを確認することでサーバのバリューの持ち主であることを認証するICカードの利用形態を想定する。図1には、IDcd認証サーバ100と、ICカード300との間で近接非接触通信によって通信を行うリーダライタを有する端末200と、ICチップを内蔵したICカード300と、が示されている。また図1には、ICカード300に対してサービスを提供するサービス事業者400と、その他事業者500と、も示されている。サービス事業者400と、その他事業者500とは、例えばサーバの形態であり得る。 [1.2. Configuration example]
FIG. 1 is an explanatory diagram illustrating a configuration example of an authentication system according to an embodiment of the present disclosure. In this system, a form in which a value is stored in the server increases, and a use form of an IC card that authenticates the owner of the value of the server by confirming that the card is correct is assumed. FIG. 1 shows a terminal 200 having a reader / writer that communicates between theIDcd authentication server 100 and the IC card 300 by proximity non-contact communication, and an IC card 300 having an IC chip built therein. FIG. 1 also shows a service provider 400 that provides a service to the IC card 300 and another provider 500. The service provider 400 and the other provider 500 may be in the form of a server, for example.
図1は、本開示の実施の形態に係る認証システムの構成例を示す説明図である。このシステムでは、サーバにバリューを保持する形態が増え、正しいカードであることを確認することでサーバのバリューの持ち主であることを認証するICカードの利用形態を想定する。図1には、IDcd認証サーバ100と、ICカード300との間で近接非接触通信によって通信を行うリーダライタを有する端末200と、ICチップを内蔵したICカード300と、が示されている。また図1には、ICカード300に対してサービスを提供するサービス事業者400と、その他事業者500と、も示されている。サービス事業者400と、その他事業者500とは、例えばサーバの形態であり得る。 [1.2. Configuration example]
FIG. 1 is an explanatory diagram illustrating a configuration example of an authentication system according to an embodiment of the present disclosure. In this system, a form in which a value is stored in the server increases, and a use form of an IC card that authenticates the owner of the value of the server by confirming that the card is correct is assumed. FIG. 1 shows a terminal 200 having a reader / writer that communicates between the
図2は、IDcd認証サーバ100の機能構成例を示す説明図である。IDcd認証サーバ100は、ICカード認証部110と、回数券データ管理部120と、通信データ復元部130と、外部通信部140と、を含んで構成される。
FIG. 2 is an explanatory diagram showing a functional configuration example of the IDcd authentication server 100. The IDcd authentication server 100 includes an IC card authentication unit 110, a coupon data management unit 120, a communication data restoration unit 130, and an external communication unit 140.
ICカード認証部110は、ICカード300の認証を行う。ICカード認証部110は、レスポンス検証器111と、ICカード鍵テーブル112と、を含んで構成される。レスポンス検証器111は、ICカード300で生成されたチャレンジに対するレスポンスが正しいものであるかどうかを検証する。レスポンス検証器111は、ICカード300におけるレスポンスの生成の仕組みと同じ仕組みを持っている。ICカード鍵テーブル112は、ICカード300を認証するために必要な鍵情報を保持する。具体的には、ICカード鍵テーブル112は、ICカード鍵IDと、ICカード鍵情報とを、ICカード鍵ごとに保持する。ICカード鍵IDは、ICカード鍵を識別するためのIDである。ICカード鍵情報は、ICカードに格納されている秘匿の鍵を認証するために必要な鍵情報である。
The IC card authentication unit 110 authenticates the IC card 300. The IC card authentication unit 110 includes a response verifier 111 and an IC card key table 112. The response verifier 111 verifies whether the response to the challenge generated by the IC card 300 is correct. The response verifier 111 has the same mechanism as the response generation mechanism in the IC card 300. The IC card key table 112 holds key information necessary for authenticating the IC card 300. Specifically, the IC card key table 112 holds an IC card key ID and IC card key information for each IC card key. The IC card key ID is an ID for identifying the IC card key. The IC card key information is key information necessary for authenticating a secret key stored in the IC card.
回数券データ管理部120は、回数券データとサービス定義を管理する。回数券データとは、ICカード300の認証のために必要となる情報が端末200ごとに規定されたユニークなデータである。回数券データは、後述するように、チャレンジと、IDトークン化鍵と、を有するデータ列である。IDcd認証サーバ100は、端末200に対して複数個の回数券データを一括して提供しても良く、端末200での認証に応じて送られる要求の度に生成して端末200に提供しても良い。
The coupon data management unit 120 manages coupon data and service definitions. The coupon data is unique data in which information necessary for authentication of the IC card 300 is defined for each terminal 200. As described later, the coupon data is a data string having a challenge and an ID tokenization key. The IDcd authentication server 100 may provide a plurality of coupon data to the terminal 200 in a lump. The IDcd authentication server 100 generates and provides the terminal 200 with each request sent in response to the authentication at the terminal 200. Also good.
回数券データ管理部120は、回数券データ生成器121と、回数券テーブル122と、を含んで構成される。回数券データ生成器121は、所定のルールに基づいて回数券データを生成する。回数券テーブル122は、ICカード300にアクセスする端末200を管理し、端末200ごとに回数券データを生成するために必要なデータを保持する。回数券テーブル122は、具体的には、端末ID、初期回数券データ、回数券データ派生鍵、現在利用回数、現在払出回数、最終回数券データを保持する。端末IDは、端末200を識別するためのIDである。初期回数券データは、回数券データを派生させる最初の鍵である。回数券データ派生鍵は、回数券データから、次の回数券データを派生生成するための鍵である。現在利用回数は、これまで何個目の回数券データまでが使われたかを示す回数である。現在払出回数は、これまで何個目の回数券データが払い出されたかを示す回数である。最終回数券データは、最後に認証した回数券データである。
The coupon ticket data management unit 120 includes a coupon ticket data generator 121 and a coupon ticket table 122. The coupon data generator 121 generates coupon data based on a predetermined rule. The coupon ticket table 122 manages the terminal 200 accessing the IC card 300 and holds data necessary for generating coupon ticket data for each terminal 200. More specifically, the coupon ticket table 122 holds a terminal ID, initial coupon data, coupon data derivation key, current usage count, current payout count, and final coupon data. The terminal ID is an ID for identifying the terminal 200. Initial coupon data is the first key from which coupon data is derived. The coupon data derivation key is a key for deriving and generating the next coupon data from the coupon data. The current use count is a count indicating how many coupon tickets have been used so far. The current number of payouts is the number indicating how many coupon data have been paid out so far. The final coupon data is the coupon ticket data that was last authenticated.
通信データ復元部130は、端末200から所定のルールにより暗号化されたデータを復元する。通信データ復元部130は、トークン化IDcd復元器131と、ハッシュ生成132と、を含んで構成される。トークン化IDcd復元器131は、トークン化されたIDcdを復元する。
The communication data restoration unit 130 restores data encrypted from the terminal 200 according to a predetermined rule. The communication data restoration unit 130 includes a tokenized IDcd restoration unit 131 and a hash generation 132. The tokenized IDcd restorer 131 restores the tokenized IDcd.
IDcd認証サーバ100は、他にサービス事業者400を管理するサービス定義テーブル123を保持する。サービス定義テーブル123は、サービス事業者を管理し、サービス事業者が利用する端末のリストと、受け入れるICカードの鍵の種類を保持する。サービス定義テーブル123は、サービス事業者400ごとに、サービスID、端末IDリスト、鍵IDリストを保持する。サービスIDは、サービス事業者を識別するためのIDである。端末IDリストは、サービス事業者が利用している端末の端末IDリストである。鍵IDリストは、各端末が受け入れ可能なICカード鍵のICカード鍵IDリストである。
The IDcd authentication server 100 holds a service definition table 123 that manages the service provider 400. The service definition table 123 manages the service provider and holds a list of terminals used by the service provider and the types of IC card keys to be accepted. The service definition table 123 holds a service ID, a terminal ID list, and a key ID list for each service provider 400. The service ID is an ID for identifying a service provider. The terminal ID list is a terminal ID list of terminals used by service providers. The key ID list is an IC card key ID list of IC card keys that can be accepted by each terminal.
外部通信部140は、IDcd認証サーバ100の外部の装置との間で、任意の通信プロトコルによる通信処理を実行する。
The external communication unit 140 executes communication processing using an arbitrary communication protocol with an external device of the IDcd authentication server 100.
[1.3.動作例]
続いて、認証システムの動作例を説明する。 [1.3. Example of operation]
Subsequently, an operation example of the authentication system will be described.
続いて、認証システムの動作例を説明する。 [1.3. Example of operation]
Subsequently, an operation example of the authentication system will be described.
(実施例1)
1つ目の実施例として、事前に端末ごとに複数の回数券データを送付し、ICカード300が翳されるたびにレスポンスをIDcd認証サーバ100に送信して認証を行う例を示す。端末200がセキュアでない場合を想定して、ICカード300が翳されるごとに端末200がサービス事業者400を介してIDcd認証サーバ100から回数券データを取得する場合も該当する。 Example 1
As a first embodiment, an example is shown in which a plurality of coupon data is sent in advance for each terminal, and a response is transmitted to theIDcd authentication server 100 each time the IC card 300 is deceived for authentication. Assuming the case where the terminal 200 is not secure, the case where the terminal 200 obtains the coupon ticket data from the IDcd authentication server 100 via the service provider 400 every time the IC card 300 is tapped is also applicable.
1つ目の実施例として、事前に端末ごとに複数の回数券データを送付し、ICカード300が翳されるたびにレスポンスをIDcd認証サーバ100に送信して認証を行う例を示す。端末200がセキュアでない場合を想定して、ICカード300が翳されるごとに端末200がサービス事業者400を介してIDcd認証サーバ100から回数券データを取得する場合も該当する。 Example 1
As a first embodiment, an example is shown in which a plurality of coupon data is sent in advance for each terminal, and a response is transmitted to the
(1-1)ICカード鍵情報の登録
まずICカード300に保持されているICカード鍵情報をIDcd認証サーバ100に登録する際の動作例を説明する。図3は、IDcd認証サーバ100及びICカード300の動作例を示す流れ図である。ICカード300からは、所定の方法、例えばICカード鍵情報をIDcd認証サーバ100に登録するための端末200にICカード300がかざされたことに応じて、ICカード鍵情報をIDcd認証サーバ100に送信する(ステップS101)。この際、必要に応じてICカード300を保持する登録者の本人認証や、IDcd認証サーバ100との間の通信路の暗号化を行う。IDcd認証サーバ100は、ICカード300から送信されたICカード鍵情報をICカード鍵テーブル112に登録し、ICカード鍵IDをICカード300へ返す(ステップS102)。このICカード鍵IDは、ICカード300のユーザが何らかの方法で管理しても良い。例えばICカード鍵IDは、ICカード300のユーザが保持する情報通信機器の内部で保存されていても良い。 (1-1) Registration of IC Card Key Information First, an operation example when registering IC card key information held in theIC card 300 in the IDcd authentication server 100 will be described. FIG. 3 is a flowchart showing an operation example of the IDcd authentication server 100 and the IC card 300. In response to the IC card 300 being held over the terminal 200 for registering the IC card key information in the IDcd authentication server 100, the IC card key information is transferred from the IC card 300 to the IDcd authentication server 100. Transmit (step S101). At this time, authentication of the registrant holding the IC card 300 and encryption of a communication path with the IDcd authentication server 100 are performed as necessary. The IDcd authentication server 100 registers the IC card key information transmitted from the IC card 300 in the IC card key table 112, and returns the IC card key ID to the IC card 300 (step S102). The IC card key ID may be managed by the user of the IC card 300 by some method. For example, the IC card key ID may be stored inside the information communication device held by the user of the IC card 300.
まずICカード300に保持されているICカード鍵情報をIDcd認証サーバ100に登録する際の動作例を説明する。図3は、IDcd認証サーバ100及びICカード300の動作例を示す流れ図である。ICカード300からは、所定の方法、例えばICカード鍵情報をIDcd認証サーバ100に登録するための端末200にICカード300がかざされたことに応じて、ICカード鍵情報をIDcd認証サーバ100に送信する(ステップS101)。この際、必要に応じてICカード300を保持する登録者の本人認証や、IDcd認証サーバ100との間の通信路の暗号化を行う。IDcd認証サーバ100は、ICカード300から送信されたICカード鍵情報をICカード鍵テーブル112に登録し、ICカード鍵IDをICカード300へ返す(ステップS102)。このICカード鍵IDは、ICカード300のユーザが何らかの方法で管理しても良い。例えばICカード鍵IDは、ICカード300のユーザが保持する情報通信機器の内部で保存されていても良い。 (1-1) Registration of IC Card Key Information First, an operation example when registering IC card key information held in the
(1-2)端末の登録
次に端末200の情報をIDcd認証サーバ100に登録する際の動作例を説明する。図4は、IDcd認証サーバ100及び端末200の動作例を示す流れ図である。端末200は、所定のタイミングでIDcd認証サーバ100に登録するリクエストを送る(ステップS111)。この際、必要に応じて登録者の本人認証や、IDcd認証サーバ100との間の通信路の暗号化を行う。IDcd認証サーバ100は、このリクエストに応じて、ユニークな端末IDを採番し、端末IDに初期回数券データ、回数券データ派生鍵を生成する。IDcd認証サーバ100は、生成した初期回数券データを、回数券テーブル122の初期回数券データと最終回数券データに割り当てる。またIDcd認証サーバ100は、生成した回数券データ派生鍵を回数券テーブル122の回数券データ派生鍵に割り当てる。またIDcd認証サーバ100は、回数券テーブル122の現在利用回数と現在払出回数の数をいずれも0とする。IDcd認証サーバ100は、端末IDを端末200に提供する(ステップS112)。端末200は、端末IDと後述する回数券データリストに加えて、現在利用回数を保持する。現在利用回数の初期値を0とする。 (1-2) Registration of Terminal Next, an operation example when registering information of the terminal 200 in theIDcd authentication server 100 will be described. FIG. 4 is a flowchart showing an operation example of the IDcd authentication server 100 and the terminal 200. The terminal 200 sends a request for registration to the IDcd authentication server 100 at a predetermined timing (step S111). At this time, authentication of the registrant and encryption of the communication path with the IDcd authentication server 100 are performed as necessary. In response to this request, the IDcd authentication server 100 assigns a unique terminal ID, and generates initial coupon data and coupon data derivation key for the terminal ID. The IDcd authentication server 100 assigns the generated initial coupon ticket data to the initial coupon ticket data and the final coupon data in the coupon table 122. The IDcd authentication server 100 assigns the generated coupon data derivation key to the coupon data derivation key in the coupon table 122. Further, the IDcd authentication server 100 sets the number of the current use count and the current payout count in the coupon ticket table 122 to 0. The IDcd authentication server 100 provides the terminal ID to the terminal 200 (step S112). The terminal 200 holds the current use count in addition to the terminal ID and a coupon ticket data list to be described later. The initial value of the current usage count is set to 0.
次に端末200の情報をIDcd認証サーバ100に登録する際の動作例を説明する。図4は、IDcd認証サーバ100及び端末200の動作例を示す流れ図である。端末200は、所定のタイミングでIDcd認証サーバ100に登録するリクエストを送る(ステップS111)。この際、必要に応じて登録者の本人認証や、IDcd認証サーバ100との間の通信路の暗号化を行う。IDcd認証サーバ100は、このリクエストに応じて、ユニークな端末IDを採番し、端末IDに初期回数券データ、回数券データ派生鍵を生成する。IDcd認証サーバ100は、生成した初期回数券データを、回数券テーブル122の初期回数券データと最終回数券データに割り当てる。またIDcd認証サーバ100は、生成した回数券データ派生鍵を回数券テーブル122の回数券データ派生鍵に割り当てる。またIDcd認証サーバ100は、回数券テーブル122の現在利用回数と現在払出回数の数をいずれも0とする。IDcd認証サーバ100は、端末IDを端末200に提供する(ステップS112)。端末200は、端末IDと後述する回数券データリストに加えて、現在利用回数を保持する。現在利用回数の初期値を0とする。 (1-2) Registration of Terminal Next, an operation example when registering information of the terminal 200 in the
(1-3)サービス事業者の登録
次にサービス事業者400の情報をIDcd認証サーバ100に登録する際の動作例を説明する。図5は、IDcd認証サーバ100及びサービス事業者400の動作例を示す流れ図である。サービス事業者400は、サービス定義をIDcd認証サーバ100に登録するリクエストを送る(ステップS121)。この際、必要に応じて、登録者の本人認証や、IDcd認証サーバ100との間の通信路の暗号化を行う。サービス事業者400は、IDcd認証サーバ100に対して、端末IDリスト及びICカード鍵IDリストを送信する。IDcd認証サーバ100は、このリクエストに応じてユニークなサービスIDを採番し、サービス定義テーブル123に情報を登録する。IDcd認証サーバ100は、サービス事業者400へ、採番したサービスIDを提供する(ステップS122)。サービス事業者400は、サービスを利用する端末200(端末IDリストに含まれる端末IDに対応する端末200)に、サービスIDとICカード鍵IDリストを通知する(ステップS123)。 (1-3) Service Provider Registration Next, an operation example when registering information of theservice provider 400 in the IDcd authentication server 100 will be described. FIG. 5 is a flowchart showing an operation example of the IDcd authentication server 100 and the service provider 400. The service provider 400 sends a request for registering the service definition in the IDcd authentication server 100 (step S121). At this time, the identity of the registrant and encryption of the communication path with the IDcd authentication server 100 are performed as necessary. The service provider 400 transmits a terminal ID list and an IC card key ID list to the IDcd authentication server 100. In response to this request, the IDcd authentication server 100 assigns a unique service ID and registers information in the service definition table 123. The IDcd authentication server 100 provides the numbered service ID to the service provider 400 (step S122). The service provider 400 notifies the service ID and the IC card key ID list to the terminal 200 that uses the service (the terminal 200 corresponding to the terminal ID included in the terminal ID list) (step S123).
次にサービス事業者400の情報をIDcd認証サーバ100に登録する際の動作例を説明する。図5は、IDcd認証サーバ100及びサービス事業者400の動作例を示す流れ図である。サービス事業者400は、サービス定義をIDcd認証サーバ100に登録するリクエストを送る(ステップS121)。この際、必要に応じて、登録者の本人認証や、IDcd認証サーバ100との間の通信路の暗号化を行う。サービス事業者400は、IDcd認証サーバ100に対して、端末IDリスト及びICカード鍵IDリストを送信する。IDcd認証サーバ100は、このリクエストに応じてユニークなサービスIDを採番し、サービス定義テーブル123に情報を登録する。IDcd認証サーバ100は、サービス事業者400へ、採番したサービスIDを提供する(ステップS122)。サービス事業者400は、サービスを利用する端末200(端末IDリストに含まれる端末IDに対応する端末200)に、サービスIDとICカード鍵IDリストを通知する(ステップS123)。 (1-3) Service Provider Registration Next, an operation example when registering information of the
(1-4)回数券データリストの出力(払い出し)
次に、IDcd認証サーバ100が回数券データリストを出力する(払い出す)際の動作例を説明する。図6は、IDcd認証サーバ100、端末200及びサービス事業者400の動作例を示す流れ図である。 (1-4) Output of coupon data list (payout)
Next, an operation example when theIDcd authentication server 100 outputs (pays) the coupon data list will be described. FIG. 6 is a flowchart illustrating an operation example of the IDcd authentication server 100, the terminal 200, and the service provider 400.
次に、IDcd認証サーバ100が回数券データリストを出力する(払い出す)際の動作例を説明する。図6は、IDcd認証サーバ100、端末200及びサービス事業者400の動作例を示す流れ図である。 (1-4) Output of coupon data list (payout)
Next, an operation example when the
サービス事業者400は、回数券データリストを払い出したい端末200ごとに、回数券データリストの払い出しをIDcd認証サーバ100に要求する(ステップS131)。サービス事業者400は、IDcd認証サーバ100に対し、自身のサービスID、回数券データリストを払い出す端末の端末ID、回数券データ払い出し数の情報を送信する。
The service provider 400 requests the IDcd authentication server 100 to pay out the coupon data list for each terminal 200 that wants to pay out the coupon data list (step S131). The service provider 400 transmits to the IDcd authentication server 100 information about its own service ID, the terminal ID of the terminal that pays out the coupon ticket data list, and the coupon ticket payout count.
IDcd認証サーバ100は、この払い出し要求に対して、回数券データ生成器121を使って、下記の手順で、入力された回数券データ払い出し数分、回数券データを生成する。まずIDcd認証サーバ100は、サービス事業者400から入力された端末IDから、回数券テーブルの端末IDを特定する。次にIDcd認証サーバ100は、回数券データ生成器121に、最終回数券データと回数券データ派生鍵を入力し、新しい回数券データを生成する。そしてIDcd認証サーバ100は、現在払出回数と生成した回数券データリストをサービス事業者400に出力し、払い出した回数分だけ、回数券テーブル122の現在払出回数を加算する(ステップS132)。
In response to this payout request, the IDcd authentication server 100 uses the coupon ticket data generator 121 to generate coupon ticket data for the number of coupon tickets that have been input in the following procedure. First, the IDcd authentication server 100 specifies the terminal ID of the coupon ticket table from the terminal ID input from the service provider 400. Next, the IDcd authentication server 100 inputs the final coupon data and the coupon data derivation key to the coupon data generator 121 to generate new coupon data. The IDcd authentication server 100 outputs the current number of payouts and the generated coupon data list to the service provider 400, and adds the current number of payouts in the coupon ticket table 122 by the number of payouts (step S132).
サービス事業者400は、IDcd認証サーバ100から取得した現在払出回数、回数券データリストを、端末IDに対応する端末200に転送する(ステップS133)。端末IDに対応する端末200は、自身が保持している回数券データリストに、取得した回数券データリストを追加する。
The service provider 400 transfers the current payout count and coupon data list acquired from the IDcd authentication server 100 to the terminal 200 corresponding to the terminal ID (step S133). The terminal 200 corresponding to the terminal ID adds the acquired coupon data list to the coupon data list held by itself.
(1-5)カードレスポンスの取得
端末200は、ICカード300が翳され認証が必要となるたびに、以下のカードレスポンス取得を行う。図7は、サービス事業者400、端末200及びICカード300の動作例を示す流れ図である。端末200は、ICカード300が翳され、ICカード300の認証が必要となるたびに、以下のカードレスポンス取得を行う。まず端末200は、保持している回数券データリストのうち一番若いデータを取り出し、その回数券データを回数券データリストから削除するとともに、現在利用回数を1インクリメントする。次に端末200は、取り出した回数券データから、チャレンジと、IDトークン化鍵と、を取り出す。例えば、回数券データの先頭8バイトまたは16バイトをチャレンジ、次の8バイトをIDトークン化鍵とする。もちろんチャレンジと、IDトークン化鍵との定義はこの例に限られるものでは無い。 (1-5) Acquisition of Card Response The terminal 200 acquires the following card response each time theIC card 300 is compromised and authentication is required. FIG. 7 is a flowchart showing an operation example of the service provider 400, the terminal 200, and the IC card 300. The terminal 200 obtains the following card response each time the IC card 300 is tapped and the IC card 300 needs to be authenticated. First, the terminal 200 extracts the youngest data from the coupon data list held, deletes the coupon data from the coupon data list, and increments the current use count by one. Next, the terminal 200 extracts the challenge and the ID tokenization key from the extracted coupon data. For example, the first 8 bytes or 16 bytes of the coupon ticket data are challenged, and the next 8 bytes are used as an ID tokenization key. Of course, the definition of the challenge and the ID tokenization key is not limited to this example.
端末200は、ICカード300が翳され認証が必要となるたびに、以下のカードレスポンス取得を行う。図7は、サービス事業者400、端末200及びICカード300の動作例を示す流れ図である。端末200は、ICカード300が翳され、ICカード300の認証が必要となるたびに、以下のカードレスポンス取得を行う。まず端末200は、保持している回数券データリストのうち一番若いデータを取り出し、その回数券データを回数券データリストから削除するとともに、現在利用回数を1インクリメントする。次に端末200は、取り出した回数券データから、チャレンジと、IDトークン化鍵と、を取り出す。例えば、回数券データの先頭8バイトまたは16バイトをチャレンジ、次の8バイトをIDトークン化鍵とする。もちろんチャレンジと、IDトークン化鍵との定義はこの例に限られるものでは無い。 (1-5) Acquisition of Card Response The terminal 200 acquires the following card response each time the
端末200は、ICカード300が翳されたとき、ICカード鍵IDごとに決められた情報を用いて、利用するICカード鍵IDを特定する。この際、端末200は、ICカード300の片側認証コマンドを発行する。その際に、端末200は、近接非接触通信によってチャレンジをICカード300に入力し(ステップS141)、ICカード300からIDcdと、チャレンジに対してICカード300が生成したレスポンスを取得する(ステップS142)。
The terminal 200 specifies the IC card key ID to be used by using information determined for each IC card key ID when the IC card 300 is fraudulent. At this time, the terminal 200 issues a one-side authentication command for the IC card 300. At that time, the terminal 200 inputs a challenge to the IC card 300 by proximity contactless communication (step S141), and acquires an IDcd from the IC card 300 and a response generated by the IC card 300 in response to the challenge (step S142). ).
図8は、ICカード300での処理を説明するための説明図である。ICカード300は、端末200からチャレンジを取得すると、内部で保持しているICカード鍵情報及びIDcdを用いて所定の演算を行って、チャレンジに対するレスポンスを生成する。そしてICカード300は、IDcdと、チャレンジに対して生成したレスポンスを出力する。
FIG. 8 is an explanatory diagram for explaining processing in the IC card 300. When the IC card 300 acquires a challenge from the terminal 200, the IC card 300 performs a predetermined operation using the IC card key information and IDcd held therein, and generates a response to the challenge. Then, the IC card 300 outputs the IDcd and the response generated for the challenge.
続いて端末200は、IDcd認証サーバ100に対して、IDトークン化鍵を使って、トークン化IDcdを生成する。例えば端末200は、IDcdとIDトークン化鍵で排他的論理和を取ることで、トークン化IDcdを生成する。もちろんトークン化IDcdの生成方法は係る例に限定されるものでは無い。また端末200は、レスポンス等に対して、SSL(Secure Sockets Layer)等の所定の暗号化方式を使って暗号化レスポンスを生成する。そして端末200は、生成した情報をサービス事業者400に送信する(ステップS143)。ここで端末200は、サービス事業者400へ、端末ID、トークン化IDcd、レスポンス、現在利用回数、ICカード鍵IDを送信する。
Subsequently, the terminal 200 generates a tokenized IDcd for the IDcd authentication server 100 using the ID tokenization key. For example, the terminal 200 generates a tokenized IDcd by taking an exclusive OR with the IDcd and the ID tokenization key. Of course, the method for generating the tokenized IDcd is not limited to this example. Further, the terminal 200 generates an encrypted response for the response or the like using a predetermined encryption method such as SSL (Secure Sockets Layer). Then, the terminal 200 transmits the generated information to the service provider 400 (Step S143). Here, the terminal 200 transmits the terminal ID, tokenized IDcd, response, current usage count, and IC card key ID to the service provider 400.
(1-6)ICカードの認証
図9は、IDcd認証サーバ100及びサービス事業者400の動作例を示す流れ図である。サービス事業者400は、端末200から取得したレスポンス情報をIDcd認証サーバ100に送信し、レスポンスが正しいことの認証を依頼する(ステップS151)。ここでサービス事業者400は、IDcd認証サーバ100に、サービスID、端末ID、トークン化IDcd、レスポンス、現在利用回数、およびICカード鍵IDを送信する。 (1-6) Authentication of IC Card FIG. 9 is a flowchart showing an operation example of theIDcd authentication server 100 and the service provider 400. The service provider 400 transmits the response information acquired from the terminal 200 to the IDcd authentication server 100 and requests authentication that the response is correct (step S151). Here, the service provider 400 transmits the service ID, the terminal ID, the tokenized IDcd, the response, the current use count, and the IC card key ID to the IDcd authentication server 100.
図9は、IDcd認証サーバ100及びサービス事業者400の動作例を示す流れ図である。サービス事業者400は、端末200から取得したレスポンス情報をIDcd認証サーバ100に送信し、レスポンスが正しいことの認証を依頼する(ステップS151)。ここでサービス事業者400は、IDcd認証サーバ100に、サービスID、端末ID、トークン化IDcd、レスポンス、現在利用回数、およびICカード鍵IDを送信する。 (1-6) Authentication of IC Card FIG. 9 is a flowchart showing an operation example of the
IDcd認証サーバ100は、回数券データ管理部120で、以下の手順によって回数券データを生成する。まずIDcd認証サーバ100は、サービス事業者400から入力された端末IDから、回数券テーブル122の中のデータを特定し、最終回数券データを取得する。次にIDcd認証サーバ100は、サービス事業者400から入力された現在利用回数から回数券データを生成する。回数券テーブル122にある初期回数券データからサービス事業者400から入力された現在利用回数の数分だけ生成を繰り返すのではなく、回数券テーブル122にある現在利用回数との差分の数だけ、最終回数券データから回数券データ生成器121を使って回数券データの生成を繰り返す。
The IDcd authentication server 100 uses the coupon data management unit 120 to generate coupon data according to the following procedure. First, the IDcd authentication server 100 specifies the data in the coupon ticket table 122 from the terminal ID input from the service provider 400 and acquires the final coupon data. Next, the IDcd authentication server 100 generates coupon data from the current usage count input from the service provider 400. The generation is not repeated from the initial coupon data in the coupon table 122 by the number of current usages input from the service provider 400, but the number of differences from the current usage in the coupon table 122 is the final number. The generation of coupon data is repeated from the coupon data using the coupon data generator 121.
IDcd認証サーバ100は、入力されたレスポンス情報と、回数券データ生成器121で生成した回数券データを使って、通信データ復元部130で、受信したデータの復号化を行う。まずIDcd認証サーバ100は、回数券データ生成器121で生成した回数券データから、チャレンジとトークン化鍵とを取得する。次にIDcd認証サーバ100は、IDcdとトークン化鍵とをトークン化IDcd復元器131に入力して、IDcdを取得する。
The IDcd authentication server 100 decrypts the received data at the communication data restoration unit 130 using the input response information and the coupon data generated by the coupon data generator 121. First, the IDcd authentication server 100 acquires a challenge and a tokenization key from the coupon data generated by the coupon data generator 121. Next, the IDcd authentication server 100 inputs the IDcd and the tokenized key to the tokenized IDcd decompressor 131 and acquires the IDcd.
続いて、IDcd認証サーバ100は、サービス事業者400から入力されたレスポンス情報と、自身で生成した回数券データと、自身で復号化した情報を使って、サービス事業者400から入力されたレスポンスが正しいことをICカード認証部110で認証する。具体的には、IDcd認証サーバ100は以下の手順で認証する。まずIDcd認証サーバ100は入力されたICカード鍵IDから、ICカード鍵情報を取得する。次にIDcd認証サーバ100は、レスポンス検証器111に、復元したIDcd、自身で生成したチャレンジ、及びICカード鍵情報を入力してレスポンスを生成し、サービス事業者400から入力されたレスポンスと比較して、両者が同じかどうか判別する。同じ場合は、IDcd認証サーバ100は、端末200にかざされたものは正しいICカードおよびIDcdであるとみなす。そしてIDcd認証サーバ100は、自身で生成した回数券データを最終回数券データとし、現在利用回数を、入力された現在利用回数とする。一方、一致しない場合は、IDcd認証サーバ100は、以降の処理は行わず、サービス事業者400に不一致であったことを示す所定のエラーメッセージを返す。
Subsequently, the IDcd authentication server 100 uses the response information input from the service provider 400, the coupon data generated by itself, and the information decrypted by itself to receive a response input from the service provider 400. The IC card authenticating unit 110 authenticates the correctness. Specifically, the IDcd authentication server 100 performs authentication by the following procedure. First, the IDcd authentication server 100 acquires IC card key information from the input IC card key ID. Next, the IDcd authentication server 100 inputs the restored IDcd, the challenge generated by itself, and the IC card key information to the response verifier 111 to generate a response, and compares the response with the response input from the service provider 400. To determine whether they are the same. In the same case, the IDcd authentication server 100 regards what is held over the terminal 200 as a correct IC card and IDcd. The IDcd authentication server 100 sets the coupon ticket data generated by itself as the final coupon data, and sets the current usage count as the input current usage count. On the other hand, if they do not match, the IDcd authentication server 100 does not perform the subsequent processing and returns a predetermined error message indicating that there is a mismatch to the service provider 400.
図10は、ICカード認証部110の処理を説明するための説明図である。ICカード認証部110は、ICカード鍵IDから、ICカード鍵テーブル112を参照して、対象のICカード鍵情報を抽出する。そしてICカード認証部110は、復元したIDcd、自身で生成したチャレンジ、及びICカード鍵情報をレスポンス検証器111に入力してレスポンスを生成する。
FIG. 10 is an explanatory diagram for explaining processing of the IC card authentication unit 110. The IC card authentication unit 110 refers to the IC card key table 112 from the IC card key ID and extracts target IC card key information. Then, the IC card authenticating unit 110 inputs the restored IDcd, the challenge generated by itself, and the IC card key information to the response verifier 111 to generate a response.
端末200は、認証のたびに回数券データを消費するため、足りなくなったらIDcd認証サーバ100から回数券データを追加で取得する。端末200は、サービス事業者400に、回数券データの追加を依頼する。サービス事業者400は、IDcd認証サーバ100へ、サービスID、端末ID、回数券データ払い出し数を入力して、IDcd認証サーバ100に回数券データの追加生成を依頼する。IDcd認証サーバ100は、上述した回数券データリストの払い出し処理と同じ処理を行って、生成した回数券データをサービス事業者400に提供する。サービス事業者400は、IDcd認証サーバ100から取得した回数券データを、回数券データの追加を依頼した端末200へ転送する。
Since the terminal 200 consumes coupon ticket data every time authentication is performed, the coupon ticket data is additionally acquired from the IDcd authentication server 100 when it is insufficient. The terminal 200 requests the service provider 400 to add coupon ticket data. The service provider 400 inputs the service ID, the terminal ID, and the coupon ticket payout number to the IDcd authentication server 100 and requests the IDcd authentication server 100 to additionally generate coupon ticket data. The IDcd authentication server 100 performs the same processing as the above-described coupon ticket data list payout processing, and provides the generated coupon ticket data to the service provider 400. The service provider 400 transfers the coupon ticket data acquired from the IDcd authentication server 100 to the terminal 200 that has requested the addition of coupon ticket data.
(実施例2)
次の実施例として、端末200にかざされるICカードのIDcdのリストがあらかじめ分かっている場合に、IDcdに対応するチャレンジとレスポンスを事前に払い出す例を示す。 (Example 2)
As a next embodiment, an example in which a challenge and a response corresponding to IDcd are paid out in advance when the list of IDcd of the IC card held over the terminal 200 is known in advance will be described.
次の実施例として、端末200にかざされるICカードのIDcdのリストがあらかじめ分かっている場合に、IDcdに対応するチャレンジとレスポンスを事前に払い出す例を示す。 (Example 2)
As a next embodiment, an example in which a challenge and a response corresponding to IDcd are paid out in advance when the list of IDcd of the IC card held over the terminal 200 is known in advance will be described.
(2-1)チャレンジレスポンスリストの取得
まずチャレンジレスポンスリストの取得処理を説明する。図11は、IDcd認証サーバ100、サービス事業者400及び端末200の動作例を示す流れ図である。サービス事業者400は、端末200にかざされる予定のICカード300のIDcdリストをIDcd認証サーバ100に送信する(ステップS201)。サービス事業者400は、IDcd認証サーバ100へ、サービスID及びIDcd情報のリスト(IDcd及びICカード鍵IDを含む)を送信する。 (2-1) Acquisition of Challenge Response List First, the challenge response list acquisition process will be described. FIG. 11 is a flowchart illustrating an operation example of theIDcd authentication server 100, the service provider 400, and the terminal 200. The service provider 400 transmits the IDcd list of the IC card 300 to be held over the terminal 200 to the IDcd authentication server 100 (step S201). The service provider 400 transmits a list of service IDs and IDcd information (including IDcd and IC card key ID) to the IDcd authentication server 100.
まずチャレンジレスポンスリストの取得処理を説明する。図11は、IDcd認証サーバ100、サービス事業者400及び端末200の動作例を示す流れ図である。サービス事業者400は、端末200にかざされる予定のICカード300のIDcdリストをIDcd認証サーバ100に送信する(ステップS201)。サービス事業者400は、IDcd認証サーバ100へ、サービスID及びIDcd情報のリスト(IDcd及びICカード鍵IDを含む)を送信する。 (2-1) Acquisition of Challenge Response List First, the challenge response list acquisition process will be described. FIG. 11 is a flowchart illustrating an operation example of the
IDcd認証サーバ100のICカード認証部110は、ICカード鍵IDからICカード鍵情報を取得する。またICカード認証部110は、チャレンジも生成する。このチャレンジの生成は、乱数生成等によって行われる。続いてIDcd認証サーバ100のレスポンス検証器111は、IDcd、ICカード鍵情報、チャレンジを入力し、レスポンスを取得する。これを、IDcd情報のリストの数分だけ繰り返す。
The IC card authentication unit 110 of the IDcd authentication server 100 acquires IC card key information from the IC card key ID. The IC card authenticating unit 110 also generates a challenge. This challenge is generated by random number generation or the like. Subsequently, the response verifier 111 of the IDcd authentication server 100 inputs IDcd, IC card key information, and a challenge, and acquires a response. This is repeated for the number of IDcd information lists.
そしてIDcd認証サーバ100は、サービス事業者400に生成したリストを返送する(ステップS202)。具体的には、IDcd認証サーバ100は、サービスID及びIDcd情報のリスト(IDcd、ICカード鍵ID、チャレンジ及びレスポンスを含む)を送信する。
Then, the IDcd authentication server 100 returns the generated list to the service provider 400 (step S202). Specifically, the IDcd authentication server 100 transmits a list of service IDs and IDcd information (including IDcd, IC card key ID, challenge, and response).
サービス事業者400は、IDcd認証サーバ100から受領したリストを端末200に送信する(ステップS203)。端末200は、サービス事業者400から送られたリストを保持しておく。
The service provider 400 transmits the list received from the IDcd authentication server 100 to the terminal 200 (step S203). The terminal 200 holds a list sent from the service provider 400.
(2-2)カードレスポンスの確認
図12は、端末200及びICカード300の動作例を示す流れ図である。端末200は、ICカード300が翳されたとき、ICカード300のIDcdを近接非接触通信によって取得する(ステップS211)。次に端末200は、ICカード300のIDcdを確認したのち、IDcdに対応するチャレンジを、ICカード鍵IDで特定される情報で持って、ICカード300の片側認証コマンドを発行して(ステップS212)、ICカード300からレスポンスを取得する(ステップS213)。 (2-2) Confirmation of Card Response FIG. 12 is a flowchart showing an operation example of the terminal 200 and theIC card 300. When the IC card 300 is fraudulent, the terminal 200 acquires the IDcd of the IC card 300 by proximity contactless communication (step S211). Next, after confirming the IDcd of the IC card 300, the terminal 200 issues a one-side authentication command of the IC card 300 by holding a challenge corresponding to the IDcd with information specified by the IC card key ID (step S212). ), A response is acquired from the IC card 300 (step S213).
図12は、端末200及びICカード300の動作例を示す流れ図である。端末200は、ICカード300が翳されたとき、ICカード300のIDcdを近接非接触通信によって取得する(ステップS211)。次に端末200は、ICカード300のIDcdを確認したのち、IDcdに対応するチャレンジを、ICカード鍵IDで特定される情報で持って、ICカード300の片側認証コマンドを発行して(ステップS212)、ICカード300からレスポンスを取得する(ステップS213)。 (2-2) Confirmation of Card Response FIG. 12 is a flowchart showing an operation example of the terminal 200 and the
端末200は、IDcdに該当するレスポンスと、ICカード300から受信したレスポンスが同じかどうかを確認する。同じ場合には、端末200は、翳されたICカード300が正しいICカードおよびIDcdであるとみなし、以降の処理を実行する。異なる場合は、端末200は、所定のエラー処理を実行する。
The terminal 200 confirms whether the response corresponding to the IDcd and the response received from the IC card 300 are the same. In the same case, the terminal 200 regards the fraudulent IC card 300 as the correct IC card and IDcd, and executes the subsequent processing. If they are different, the terminal 200 executes predetermined error processing.
(実施例3)
3つ目の実施例として、ICカード300に入力するチャレンジを端末200が生成して、IDcd認証サーバ100は、そのレスポンスが、そのチャレンジとICカードに入力した結果であることを証明する例を説明する。 (Example 3)
As a third embodiment, the terminal 200 generates a challenge to be input to theIC card 300, and the IDcd authentication server 100 proves that the response is a result input to the challenge and the IC card. explain.
3つ目の実施例として、ICカード300に入力するチャレンジを端末200が生成して、IDcd認証サーバ100は、そのレスポンスが、そのチャレンジとICカードに入力した結果であることを証明する例を説明する。 (Example 3)
As a third embodiment, the terminal 200 generates a challenge to be input to the
(3-1)カードレスポンス取得
図13は、サービス事業者400と、端末200と、ICカード300と、の動作例を示す流れ図である。端末200は、まずICカード300に入力するチャレンジを生成する。端末200は、サービスIDと、端末IDと、ICカード鍵IDと、現在利用回数と、任意のテキストと、を結合した要求文を生成する。図14は、端末200が生成する要求文の構造を示す説明図である。 (3-1) Card Response Acquisition FIG. 13 is a flowchart showing an operation example of theservice provider 400, the terminal 200, and the IC card 300. The terminal 200 first generates a challenge to be input to the IC card 300. The terminal 200 generates a request sentence that combines the service ID, the terminal ID, the IC card key ID, the current usage count, and an arbitrary text. FIG. 14 is an explanatory diagram illustrating a structure of a request sentence generated by the terminal 200.
図13は、サービス事業者400と、端末200と、ICカード300と、の動作例を示す流れ図である。端末200は、まずICカード300に入力するチャレンジを生成する。端末200は、サービスIDと、端末IDと、ICカード鍵IDと、現在利用回数と、任意のテキストと、を結合した要求文を生成する。図14は、端末200が生成する要求文の構造を示す説明図である。 (3-1) Card Response Acquisition FIG. 13 is a flowchart showing an operation example of the
続いて端末200は、生成した要求文に対するハッシュを生成する。そして端末200は、現在利用回数を1インクリメントする。
Subsequently, the terminal 200 generates a hash for the generated request statement. The terminal 200 increments the current usage count by one.
端末200にICカード300が翳されたとき、端末200には、ICカード鍵IDで特定される情報で持って、ICカード300の片側認証コマンドを発行する。その際に、端末200は、生成したハッシュをチャレンジとしてICカード300に近接非接触通信によって入力し(ステップS301)、ICカード300からIDcdとレスポンスを近接非接触通信によって取得する(ステップS302)。
When the IC card 300 is inserted into the terminal 200, the terminal 200 issues a one-side authentication command of the IC card 300 with information specified by the IC card key ID. At that time, the terminal 200 inputs the generated hash as a challenge to the IC card 300 by proximity contactless communication (step S301), and acquires the IDcd and response from the IC card 300 by proximity contactless communication (step S302).
続いて端末200は、生成した要求文と、ICカード300から取得したIDcd及びレスポンスと、をサービス事業者400に送信する(ステップS303)。
Subsequently, the terminal 200 transmits the generated request sentence and the IDcd and response acquired from the IC card 300 to the service provider 400 (step S303).
(3-2)カードレスポンスの認証
図15は、IDcd認証サーバ100と、サービス事業者400と、の動作例を示す流れ図である。サービス事業者400は、IDcd認証サーバ100に、レスポンスが正しいかの認証を依頼する(ステップS311)。この際、サービス事業者400は、IDcd認証サーバ100に、要求文、IDcd及びレスポンスを送信する。 (3-2) Card Response Authentication FIG. 15 is a flowchart showing an operation example of theIDcd authentication server 100 and the service provider 400. The service provider 400 requests the IDcd authentication server 100 to authenticate whether the response is correct (step S311). At this time, the service provider 400 transmits a request statement, IDcd, and response to the IDcd authentication server 100.
図15は、IDcd認証サーバ100と、サービス事業者400と、の動作例を示す流れ図である。サービス事業者400は、IDcd認証サーバ100に、レスポンスが正しいかの認証を依頼する(ステップS311)。この際、サービス事業者400は、IDcd認証サーバ100に、要求文、IDcd及びレスポンスを送信する。 (3-2) Card Response Authentication FIG. 15 is a flowchart showing an operation example of the
IDcd認証サーバ100は、受信した要求文から、ハッシュ生成器132を使って、ハッシュを生成し、チャレンジとする。さらに、IDcd認証サーバ100は、受信した要求文から、サービスIDと、端末IDと、ICカード鍵IDと、現在利用回数と、を取り出す。続いて、IDcd認証サーバ100の回数券データ管理部120は、サービス定義テーブル123を参照して、サービスIDに対応するICカード鍵IDリストに、取り出されたICカード鍵IDがあるかを確認する。続いて、ICカード認証部110において、ICカード鍵テーブル112から、ICカード鍵IDに対応するICカード鍵情報を特定する。IDcd認証サーバ100は、レスポンス検証器111を使って、IDcd、チャレンジ、ICカード鍵情報を入力して、レスポンスを生成する。そしてIDcd認証サーバ100は、生成したレスポンスを用いた認証結果をサービス事業者400に送信する(ステップS312)。受信していたレスポンスと生成したレスポンスが等しい場合は、IDcd認証サーバ100は、受信したレスポンスが、IDcdで特定されるICカード300に、要求文を入力して生成されたものであるとみなす。
The IDcd authentication server 100 uses the hash generator 132 to generate a hash from the received request sentence and sets it as a challenge. Furthermore, the IDcd authentication server 100 extracts the service ID, the terminal ID, the IC card key ID, and the current usage count from the received request text. Subsequently, the coupon data management unit 120 of the IDcd authentication server 100 refers to the service definition table 123 and confirms whether or not the extracted IC card key ID is in the IC card key ID list corresponding to the service ID. . Subsequently, the IC card authentication unit 110 specifies IC card key information corresponding to the IC card key ID from the IC card key table 112. The IDcd authentication server 100 uses the response verifier 111 to input IDcd, challenge, and IC card key information, and generates a response. Then, the IDcd authentication server 100 transmits an authentication result using the generated response to the service provider 400 (step S312). When the received response is equal to the generated response, the IDcd authentication server 100 considers that the received response is generated by inputting a request statement to the IC card 300 specified by the IDcd.
(3-3)認証結果の転送
サービス事業者400は、認証結果を保持したり、その他事業者500に転送したりする場合がある。図16は、IDcd認証サーバ100と、サービス事業者400と、その他事業者500と、の動作例を示す流れ図である。 (3-3) Transfer of Authentication Result Theservice provider 400 may hold the authentication result or transfer it to the other provider 500. FIG. 16 is a flowchart illustrating an operation example of the IDcd authentication server 100, the service provider 400, and the other provider 500.
サービス事業者400は、認証結果を保持したり、その他事業者500に転送したりする場合がある。図16は、IDcd認証サーバ100と、サービス事業者400と、その他事業者500と、の動作例を示す流れ図である。 (3-3) Transfer of Authentication Result The
その他事業者500は、サービス事業者400から、要求文、IDcd及びレスポンスを受信する(ステップS321)。その他事業者500は、IDcd認証サーバ100に、要求文、IDcd及びレスポンスを送信する(ステップS322)。IDcd認証サーバは、上記カードレスポンス認証と同様に、その他事業者500から受信したレスポンスを認証し、結果をその他事業者500に返す。
Other business operator 500 receives the request text, the IDcd, and the response from service business operator 400 (step S321). The other business operator 500 transmits a request statement, an IDcd, and a response to the IDcd authentication server 100 (step S322). The IDcd authentication server authenticates the response received from the other business operator 500 and returns the result to the other business operator 500 as in the case of the card response authentication.
(実施例4)
4つ目の実施例として、ネットワーク切断時の耐性強化や、ネットワーク通信における応答性能の向上を目的とした実施例を説明する。 Example 4
As a fourth embodiment, a description will be given of an embodiment for the purpose of enhancing tolerance when the network is disconnected and improving response performance in network communication.
4つ目の実施例として、ネットワーク切断時の耐性強化や、ネットワーク通信における応答性能の向上を目的とした実施例を説明する。 Example 4
As a fourth embodiment, a description will be given of an embodiment for the purpose of enhancing tolerance when the network is disconnected and improving response performance in network communication.
サービス事業者のサーバがクローズドなネットワークの中にある場合は、サービス事業者のサーバとIDcd認証サーバ100との間のインターネット通信が影響し、ネットワークの切断や輻輳などの影響を受けやすくなる。
When the service provider's server is in a closed network, Internet communication between the service provider's server and the IDcd authentication server 100 is affected, and the network is easily affected by network disconnection or congestion.
そこで4つ目の実施例では、チャレンジとレスポンスとのペアを、サービス事業者400のサーバにキャッシュとして事前に保持しておく。これにより、次の認証をサービス事業者400と端末200との間で完結させることが出来ると共に、サービス事業者のサーバとIDcd認証サーバ100との間のネットワークが切断していても、サービス事業者400と端末200との間で実施することができる。
Therefore, in the fourth embodiment, a pair of challenge and response is stored in advance as a cache in the server of the service provider 400. Thereby, the next authentication can be completed between the service provider 400 and the terminal 200, and even if the network between the service provider server and the IDcd authentication server 100 is disconnected, the service provider 400 and the terminal 200 can be implemented.
図17は、IDcd認証サーバ100と、サービス事業者400と、端末200と、ICカード300と、の動作例を示す流れ図である。
FIG. 17 is a flowchart showing an operation example of the IDcd authentication server 100, the service provider 400, the terminal 200, and the IC card 300.
端末200は、ポーリングを定期的に送出している(ステップS401)。このポーリングには、ICカード300からIDm(ICカード300固有の情報)及び鍵バージョンを取得するためのRequest Serviceコマンドが含まれる。ICカード300は、端末200から送出されるポーリングを受信すると、Request Serviceコマンドに応じて端末200へIDm及び鍵バージョンを返答する(ステップS402)。
The terminal 200 periodically sends out polling (step S401). This polling includes a Request Service command for acquiring IDm (information unique to the IC card 300) and a key version from the IC card 300. When receiving the polling sent from the terminal 200, the IC card 300 returns the IDm and the key version to the terminal 200 in response to the Request Service command (step S402).
端末200は、自装置の端末ID及び、ステップS402でICカード300から取得したIDm及び鍵バージョンをサービス事業者400のサーバに送信する(ステップS403)。サービス事業者400のサーバは、端末200から受信した端末200の端末ID、ICカード300のIDm及び鍵バージョンに基づいて認証鍵を選択し(ステップS404)、IDcd認証サーバ100へ、端末200から受信した情報を転送する(ステップS405)。
The terminal 200 transmits the terminal ID of its own device and the IDm and key version acquired from the IC card 300 in step S402 to the server of the service provider 400 (step S403). The server of the service provider 400 selects an authentication key based on the terminal ID of the terminal 200 received from the terminal 200, the IDm of the IC card 300, and the key version (step S404), and receives the IDcd authentication server 100 from the terminal 200. The transferred information is transferred (step S405).
IDcd認証サーバ100は、サービス事業者400のサーバから受信した情報に基づいてチャレンジ及びレスポンスの生成を行う(ステップS406)。そしてIDcd認証サーバ100は、生成したチャレンジ及びレスポンスをサービス事業者400のサーバに払い出す(ステップS407)。サービス事業者400のサーバは、IDcd認証サーバ100から払い出されたチャレンジ及びレスポンスを端末200に提供する(ステップS408)。端末200は、翳されたICカード300を認証するためにチャレンジをICカード300に送信し(ステップS409)、ICカード300はそのチャレンジに対するレスポンスを生成して端末200に返す(ステップS410)。端末200は、サービス事業者400のサーバから取得したレスポンスと、ICカード300が生成したレスポンスとを比較し(ステップS411)、ICカード300の認証を行う(ステップS412)。
The IDcd authentication server 100 generates a challenge and a response based on information received from the server of the service provider 400 (step S406). Then, the IDcd authentication server 100 pays out the generated challenge and response to the server of the service provider 400 (step S407). The server of the service provider 400 provides the challenge and response paid out from the IDcd authentication server 100 to the terminal 200 (step S408). The terminal 200 transmits a challenge to the IC card 300 to authenticate the fraudulent IC card 300 (step S409), and the IC card 300 generates a response to the challenge and returns it to the terminal 200 (step S410). The terminal 200 compares the response acquired from the server of the service provider 400 with the response generated by the IC card 300 (step S411), and authenticates the IC card 300 (step S412).
またサービス事業者400のサーバは、ICカード300の次回の認証のためのチャレンジ・レスポンスをあらかじめ取得するために、IDcd認証サーバ100へ、端末200から受信した情報を転送する(ステップS413)。IDcd認証サーバ100は、サービス事業者400のサーバから受信した情報に基づいてチャレンジ及びレスポンスの生成を行う(ステップS414)。そしてIDcd認証サーバ100は、生成したチャレンジ及びレスポンスをサービス事業者400のサーバに払い出す(ステップS415)。サービス事業者400のサーバは、IDcd認証サーバ100から払い出されたチャレンジ及びレスポンスをプリキャッシュする(ステップS416)。これにより、ICカード300の次回の認証時にサービス事業者400と端末200との間で完結させることが出来る。その様子を以下で説明する。
Also, the server of the service provider 400 transfers the information received from the terminal 200 to the IDcd authentication server 100 in order to obtain in advance a challenge / response for the next authentication of the IC card 300 (step S413). The IDcd authentication server 100 generates a challenge and a response based on the information received from the server of the service provider 400 (step S414). Then, the IDcd authentication server 100 pays out the generated challenge and response to the server of the service provider 400 (step S415). The server of the service provider 400 pre-caches the challenge and response paid out from the IDcd authentication server 100 (step S416). Thus, the service provider 400 and the terminal 200 can be completed at the next authentication of the IC card 300. This will be described below.
端末200は、ポーリングを定期的に送出している(ステップS417)。このポーリングには、ICカード300からIDm及び鍵バージョンを取得するためのRequest Serviceコマンドが含まれる。ICカード300は、端末200から送出されるポーリングを受信すると、Request Serviceコマンドに応じて端末200へIDm及び鍵バージョンを返答する(ステップS418)。
The terminal 200 periodically sends out polling (step S417). This polling includes a Request Service command for acquiring IDm and key version from the IC card 300. When receiving the polling transmitted from the terminal 200, the IC card 300 returns the IDm and the key version to the terminal 200 in response to the Request Service command (step S418).
端末200は、自装置の端末ID及び、ステップS402でICカード300から取得したIDm及び鍵バージョンをサービス事業者400のサーバに送信する(ステップS419)。サービス事業者400のサーバは、端末200から受信した端末200の端末ID、ICカード300のIDm及び鍵バージョンに基づいて認証鍵を選択する(ステップS420)。そしてサービス事業者400のサーバは、初回の認証時にはIDcd認証サーバ100へ、端末200から受信した情報を転送していたが、ここでは、あらかじめ上記ステップS416でIDcd認証サーバ100から払い出されたチャレンジ及びレスポンスをプリキャッシュしているので、そのプリキャッシュしたチャレンジ及びレスポンスからチャレンジ及びレスポンスの選択を行う(ステップS421)。
The terminal 200 transmits its own terminal ID and the IDm and key version acquired from the IC card 300 in step S402 to the server of the service provider 400 (step S419). The server of the service provider 400 selects an authentication key based on the terminal ID of the terminal 200, the IDm of the IC card 300, and the key version received from the terminal 200 (step S420). The server of the service provider 400 has transferred the information received from the terminal 200 to the IDcd authentication server 100 at the time of the first authentication, but here, the challenge that has been paid out from the IDcd authentication server 100 in step S416 in advance. Since the response and the response are pre-cached, the challenge and response are selected from the pre-cached challenge and response (step S421).
サービス事業者400のサーバは、プリキャッシュしたチャレンジ及びレスポンスから選択したチャレンジ及びレスポンスを端末200に提供する(ステップS422)。端末200は、翳されたICカード300を認証するためにチャレンジをICカード300に送信し(ステップS423)、ICカード300はそのチャレンジに対するレスポンスを生成して端末200に返す(ステップS424)。端末200は、サービス事業者400のサーバから取得したレスポンスと、ICカード300が生成したレスポンスとを比較し(ステップS425)、ICカード300の認証を行う(ステップS426)。
The server of the service provider 400 provides the challenge and response selected from the pre-cached challenge and response to the terminal 200 (step S422). The terminal 200 transmits a challenge to the IC card 300 to authenticate the fraudulent IC card 300 (step S423), and the IC card 300 generates a response to the challenge and returns it to the terminal 200 (step S424). The terminal 200 compares the response acquired from the server of the service provider 400 with the response generated by the IC card 300 (step S425), and authenticates the IC card 300 (step S426).
またサービス事業者400のサーバは、ICカード300の次回の認証のためのチャレンジ・レスポンスをあらかじめ取得するために、IDcd認証サーバ100へ、端末200から受信した情報を転送する(ステップS427)。IDcd認証サーバ100は、サービス事業者400のサーバから受信した情報に基づいてチャレンジ及びレスポンスの生成を行う(ステップS428)。そしてIDcd認証サーバ100は、生成したチャレンジ及びレスポンスをサービス事業者400のサーバに払い出す(ステップS429)。サービス事業者400のサーバは、IDcd認証サーバ100から払い出されたチャレンジ及びレスポンスをプリキャッシュする(ステップS430)。
Further, the server of the service provider 400 transfers the information received from the terminal 200 to the IDcd authentication server 100 in order to obtain in advance a challenge / response for the next authentication of the IC card 300 (step S427). The IDcd authentication server 100 generates a challenge and a response based on the information received from the server of the service provider 400 (step S428). Then, the IDcd authentication server 100 pays out the generated challenge and response to the server of the service provider 400 (step S429). The server of the service provider 400 pre-caches the challenge and response issued from the IDcd authentication server 100 (step S430).
このように、ICカード300の認証時に、サービス事業者400のサーバであらかじめプリキャッシュしたチャレンジおよびレスポンスを使用することで、サービス事業者400と端末200との間でICカード300の認証に関するやり取りを完結させることが出来る。
As described above, when the IC card 300 is authenticated, the challenge and response pre-cached by the server of the service provider 400 are used, so that the exchange of the authentication of the IC card 300 between the service provider 400 and the terminal 200 is performed. It can be completed.
また、ICカード300の認証時に、サービス事業者400のサーバであらかじめプリキャッシュしたチャレンジおよびレスポンスを使用することで、仮にサービス事業者400のサーバとIDcd認証サーバ100との間の通信に問題があり、正常にデータの授受が出来ない場合であっても、ICカード300の認証が可能となる。
Further, when the IC card 300 is authenticated, there is a problem in communication between the server of the service provider 400 and the IDcd authentication server 100 by using the challenge and response pre-cached by the server of the service provider 400 in advance. Even when data cannot be normally exchanged, the IC card 300 can be authenticated.
図18は、IDcd認証サーバ100と、サービス事業者400と、端末200と、ICカード300と、の動作例を示す流れ図である。
FIG. 18 is a flowchart showing an operation example of the IDcd authentication server 100, the service provider 400, the terminal 200, and the IC card 300.
端末200は、ポーリングを定期的に送出している(ステップS431)。このポーリングには、ICカード300からIDm及び鍵バージョンを取得するためのRequest Serviceコマンドが含まれる。ICカード300は、端末200から送出されるポーリングを受信すると、Request Serviceコマンドに応じて端末200へIDm及び鍵バージョンを返答する(ステップS432)。
The terminal 200 periodically sends out polling (step S431). This polling includes a Request Service command for acquiring IDm and key version from the IC card 300. When receiving the polling sent from the terminal 200, the IC card 300 returns the IDm and the key version to the terminal 200 in response to the Request Service command (step S432).
端末200は、自装置の端末ID及び、ステップS402でICカード300から取得したIDm及び鍵バージョンをサービス事業者400のサーバに送信する(ステップS433)。サービス事業者400のサーバは、端末200から受信した端末200の端末ID、ICカード300のIDm及び鍵バージョンに基づいて認証鍵を選択する(ステップS434)。続いて、サービス事業者400のサーバはIDcd認証サーバ100へ、端末200から受信した情報を転送するが、ここでサービス事業者400のサーバとIDcd認証サーバ100との間の通信に問題があり、正常にデータの授受が出来ない状態が発生しているとする。するとサービス事業者400のサーバは、あらかじめプリキャッシュしたチャレンジ及びレスポンスからチャレンジ及びレスポンスの選択を行う(ステップS435)。
The terminal 200 transmits its own terminal ID and the IDm and key version acquired from the IC card 300 in step S402 to the server of the service provider 400 (step S433). The server of the service provider 400 selects an authentication key based on the terminal ID of the terminal 200, the IDm of the IC card 300, and the key version received from the terminal 200 (step S434). Subsequently, the server of the service provider 400 transfers the information received from the terminal 200 to the IDcd authentication server 100, but there is a problem in communication between the server of the service provider 400 and the IDcd authentication server 100. Assume that there is a situation where data cannot be exchanged normally. Then, the server of the service provider 400 selects a challenge and response from the pre-cached challenge and response (step S435).
サービス事業者400のサーバは、プリキャッシュしたチャレンジ及びレスポンスから選択したチャレンジ及びレスポンスを端末200に提供する(ステップS436)。端末200は、翳されたICカード300を認証するためにチャレンジをICカード300に送信し(ステップS437)、ICカード300はそのチャレンジに対するレスポンスを生成して端末200に返す(ステップS438)。端末200は、サービス事業者400のサーバから取得したレスポンスと、ICカード300が生成したレスポンスとを比較し(ステップS439)、ICカード300の認証を行う(ステップS440)。
The server of the service provider 400 provides the challenge and response selected from the pre-cached challenge and response to the terminal 200 (step S436). The terminal 200 transmits a challenge to the IC card 300 to authenticate the fraudulent IC card 300 (step S437), and the IC card 300 generates a response to the challenge and returns it to the terminal 200 (step S438). The terminal 200 compares the response acquired from the server of the service provider 400 with the response generated by the IC card 300 (step S439), and authenticates the IC card 300 (step S440).
このように、ICカード300の認証時に、サービス事業者400のサーバであらかじめプリキャッシュしたチャレンジおよびレスポンスを使用することで、仮にサービス事業者400のサーバとIDcd認証サーバ100との間の通信に問題があり、正常にデータの授受が出来ない場合であっても、ICカード300の認証が可能となる。
As described above, when using the challenge and response pre-cached in the server of the service provider 400 when authenticating the IC card 300, there is a problem in communication between the server of the service provider 400 and the IDcd authentication server 100. Even if data cannot be exchanged normally, the IC card 300 can be authenticated.
その後、サービス事業者400のサーバとIDcd認証サーバ100との間の通信が回復すると、サービス事業者400のサーバは、プリキャッシュしたチャレンジおよびレスポンスを削除し、また、IDcd認証サーバ100から新たにチャレンジおよびレスポンスを取得しても良い。
Thereafter, when communication between the server of the service provider 400 and the IDcd authentication server 100 is restored, the server of the service provider 400 deletes the pre-cached challenge and response, and a new challenge is received from the IDcd authentication server 100. And a response may be acquired.
なお、サービス事業者400のサーバは、プリキャッシュしたチャレンジおよびレスポンスを、所定の時間が経過した時点で削除するようにしても良い。これにより、あまりにも古いチャレンジおよびレスポンスを認証に使用しないようにすることができる。例えば、サービス事業者400のサーバは、定期的にプリキャッシュしたチャレンジおよびレスポンスを削除してもよい。また、サービス事業者400のサーバは、所定のタイミングに達した時点でプリキャッシュしたチャレンジおよびレスポンスを削除してもよい。
Note that the server of the service provider 400 may delete the pre-cached challenge and response when a predetermined time has elapsed. This prevents too old challenges and responses from being used for authentication. For example, the server of the service provider 400 may delete periodically pre-cached challenges and responses. Further, the server of the service provider 400 may delete the pre-cached challenge and response when the predetermined timing is reached.
例えば、電車やバス、飛行機などの交通機関の乗車の際にICカード300による認証を利用する場合、サービス事業者400のサーバは、あらかじめ予約人数分だけチャレンジおよびレスポンスをプリキャッシュしておいてもよい。そしてサービス事業者400のサーバは、プリキャッシュしたチャレンジおよびレスポンスを、発車時間を過ぎた時点で削除するようにしてもよい。従って、IDcd認証サーバ100は、チャレンジおよびレスポンスを生成する際に、有効期限の情報を付加しても良い。また、サービス事業者400のサーバは、チャレンジおよびレスポンスをプリキャッシュする際に、有効期限の情報を付加しても良い。
For example, when using authentication by the IC card 300 when boarding transportation such as trains, buses, and airplanes, the server of the service provider 400 may pre-cache challenges and responses for the reserved number of people in advance. Good. Then, the server of the service provider 400 may delete the pre-cached challenge and response when the departure time has passed. Therefore, the IDcd authentication server 100 may add expiration date information when generating a challenge and a response. Further, the server of the service provider 400 may add expiration date information when pre-caching the challenge and response.
これにより、サービス事業者400のサーバは、IDcd認証サーバ100との間の通信をおこなわずにICカード300による認証を実施できる。さらにサービス事業者400のサーバは、必要の無い、プリキャッシュしたチャレンジおよびレスポンスを削除することで、チャレンジおよびレスポンスの流出を防ぎ、セキュリティの向上を図ることができる。
Thereby, the server of the service provider 400 can perform authentication by the IC card 300 without performing communication with the IDcd authentication server 100. Furthermore, the server of the service provider 400 can delete the challenge and response that are not required and have been pre-cached, thereby preventing the challenge and response from leaking and improving security.
(実施例5)
5つ目の実施例として、ICカードによる認証を利用したMITB(Man In The Browser)対策などの不正送金対策を目的とした実施例を説明する。 (Example 5)
As a fifth embodiment, a description will be given of an embodiment for the purpose of countermeasures against illegal remittance such as MITB (Man In The Browser) countermeasures using authentication by an IC card.
5つ目の実施例として、ICカードによる認証を利用したMITB(Man In The Browser)対策などの不正送金対策を目的とした実施例を説明する。 (Example 5)
As a fifth embodiment, a description will be given of an embodiment for the purpose of countermeasures against illegal remittance such as MITB (Man In The Browser) countermeasures using authentication by an IC card.
インターネットに接続可能な通信機器の爆発的な普及により、インターネットを経由したEコマース決済や、可搬性のある端末での決済が可能なmPOS決済が普及している。カード認証や本人認証はEMV仕様により厳格に決められているが、取引認証については整理途上の段階にあり、決済に使用されるインターネットブラウザや、mPOS決済を実行する端末の信頼性に依存する所が大きい。
With the explosive spread of communication devices that can be connected to the Internet, e-commerce payments via the Internet and mPOS payments that allow payments with portable terminals are becoming popular. Card authentication and personal authentication are strictly determined by the EMV specification, but transaction authentication is still in the process of being organized and depends on the reliability of the Internet browser used for payment and the terminal that performs mPOS payment. Is big.
そのため、決済する側が悪意を持って決済額を変更するような不正を行ってしまうと、決済される側に損害が与えられるおそれがある。例えば、mPOS端末を使用して1000円の買い物をしたつもりが、実際には1万円の決済になってしまうという例が考えられる。図19は、決済する側が不正により決済額を変更する様子を示す説明図である。実際には1000円の買い物をしており、ユーザが決済額を確認して了承ボタンを押下したり、所定のセキュリティコードを入力したりした上で、カードをリーダライタに翳せば1000円の決済が行われる。しかし、決済する側が実際には1万円で決済額を設定してしまっていれば、店舗から決済サーバに送られる取引情報としては1万円の取り引きとなってしまい、決済サーバ(サービス事業者400のサーバ)では1万円の決済が行われてしまう。
For this reason, if the settlement side performs a fraud that maliciously changes the settlement amount, the settlement side may be damaged. For example, there is an example in which the user intends to make a purchase of 1,000 yen using an mPOS terminal, but the payment is actually 10,000 yen. FIG. 19 is an explanatory diagram showing a state in which the settlement side changes the settlement amount due to fraud. Actually, you are shopping for 1000 yen. If the user confirms the payment amount and presses the “Accept” button or inputs a predetermined security code, the card is placed on the reader / writer and the 1000 yen is paid. Settlement is performed. However, if the settlement side actually sets the settlement amount at 10,000 yen, the transaction information sent from the store to the settlement server becomes a transaction of 10,000 yen, and the settlement server (service provider) 400 servers), a settlement of 10,000 yen is made.
そこで、以下の説明では、そのような不正を防止することが可能な仕組みについて説明する。図20は、決済する側の不正を防止することを目的とした仕組みを示す説明図である。
Therefore, in the following explanation, a mechanism that can prevent such injustice will be explained. FIG. 20 is an explanatory diagram showing a mechanism aimed at preventing fraud on the settlement side.
例えば、1000円をする場合、mPOS端末は、日付及び購入金額をバーコード化し、そのバーコード情報をハッシュ化した上で、Authentication1コマンドをリーダライタ(端末200)からICカード300へ送信する。商品の購入者はmPOS端末に所定のセキュリティコードを入力した上で、ICカード300をリーダライタ(端末200)に翳す。これにより、ICカード300はAuthentication1コマンドに応じたレスポンスを生成する。
For example, in the case of 1000 yen, the mPOS terminal barcodes the date and purchase amount, hashs the barcode information, and transmits an Authentication1 command from the reader / writer (terminal 200) to the IC card 300. The purchaser of the product inputs a predetermined security code to the mPOS terminal, and then puts the IC card 300 on the reader / writer (terminal 200). Thereby, the IC card 300 generates a response according to the Authentication1 command.
その後、商品の購入者は実際に代金を支払うために、例えば非接触通信機能を備えるクレジットカード等のEMVカードをリーダライタに翳して決済する。ここで、決済する側が悪意を持って決済額を1万円に変更するような不正を行うと、取引情報の決済額が1万円となって決済サーバに送られる。しかし、あらかじめICカード300を使用した認証時に、1000円の買い物をしたことに対するレスポンスが生成されているので、決済サーバは、レスポンスと取引情報とを照合して、決済額の不一致の検出が可能となる。なお、レスポンスと取引情報とを照合するのは決済サーバではなく、IDcd認証サーバ100が実行しても良い。IDcd認証サーバ100がレスポンスと取引情報とを照合する場合、決済サーバは、そのIDcd認証サーバ100による照合結果を受け取り、決済額が一致しているという判定が下された場合に決済処理を実行することになる。
After that, in order to actually pay the price, the purchaser of the merchandise makes a payment by placing an EMV card such as a credit card having a non-contact communication function on the reader / writer. Here, if the settlement side performs a fraud that maliciously changes the settlement amount to 10,000 yen, the settlement amount of the transaction information becomes 10,000 yen and is sent to the settlement server. However, since a response to the purchase of 1000 yen is generated in advance when authenticating using the IC card 300, the settlement server can detect the mismatch of the settlement amount by comparing the response with the transaction information. It becomes. Note that the response and transaction information may be collated by the IDcd authentication server 100 instead of the settlement server. When the IDcd authentication server 100 collates the response with the transaction information, the settlement server receives the collation result by the IDcd authentication server 100 and executes the settlement process when it is determined that the settlement amount is the same. It will be.
(実施例6)
6つ目の実施例として、ICカードによる認証を利用した個人間の安全かつ簡便な送金を目的とした実施例を説明する。 (Example 6)
As a sixth embodiment, an embodiment for the purpose of safe and simple remittance between individuals using authentication by an IC card will be described.
6つ目の実施例として、ICカードによる認証を利用した個人間の安全かつ簡便な送金を目的とした実施例を説明する。 (Example 6)
As a sixth embodiment, an embodiment for the purpose of safe and simple remittance between individuals using authentication by an IC card will be described.
通常、個人間で送金取引を行う場合、それぞれの個人が使用する金融機関等で共通の決済サーバや取引サーバといった装置の介在が必要であった。しかし、インターネットに接続可能な通信機器の爆発的な普及により、インターネットを経由した決済の利便性が向上し、それに伴って安全かつ簡便な送金手法が求められている。
Usually, when performing a remittance transaction between individuals, it is necessary to intervene with a device such as a settlement server or transaction server common to financial institutions used by each individual. However, with the explosive spread of communication devices that can be connected to the Internet, the convenience of settlement via the Internet is improved, and accordingly, a safe and simple remittance technique is required.
そこで、上述してきたICカードによる認証を、本人認証だけでなく、取引内容の認証にも用いるようにすることで、それぞれの個人が使用する金融機関等で決済サーバや取引サーバが異なっていても、それぞれの金融機関で共通の認証機能として連携が可能となる。
Therefore, by using the above-mentioned IC card authentication not only for personal authentication but also for transaction content authentication, even if the settlement server and transaction server are different in each financial institution used by each individual. It becomes possible to cooperate as a common authentication function in each financial institution.
図21は、ICカードによる認証を利用した個人間の送金処理を説明する説明図である。ここでは、第1のユーザから第2のユーザへ1000円を送金する場合の送金処理について説明する。第1のユーザの端末200は、第1のユーザのICカード300に対して、取引情報のハッシュを含んだチャレンジを送信する。第1のユーザのICカード300は、第1のユーザの端末200から受信したチャレンジに対するレスポンスを生成する。このレスポンスには、第1のユーザから第2のユーザへ1000円を送金するという取引情報の署名が含まれる。そして、第1のユーザの端末200は、第2のユーザの端末200へ、第1のユーザのICカード300が生成したレスポンスを送信する。
FIG. 21 is an explanatory diagram for explaining a remittance process between individuals using authentication by an IC card. Here, a remittance process when 1000 yen is transferred from the first user to the second user will be described. The first user's terminal 200 transmits a challenge including a hash of transaction information to the first user's IC card 300. The first user's IC card 300 generates a response to the challenge received from the first user's terminal 200. This response includes a signature of transaction information indicating that 1000 yen is transferred from the first user to the second user. Then, the first user terminal 200 transmits the response generated by the first user IC card 300 to the second user terminal 200.
第2のユーザの端末200は、第1のユーザのICカード300が生成したレスポンスを受信すると、第2のユーザのICカード300に対して、そのレスポンスに含まれる、第1のユーザのICカード300の署名が付いた取引情報のハッシュをチャレンジとして送信する。第2のユーザのICカード300は、第2のユーザの端末200から受信したチャレンジに対するレスポンスを生成する。このレスポンスには、第1のユーザから第2のユーザへ1000円を送金するという取引情報の署名が含まれる。そして、第2のユーザの端末200は、決済サーバへ、第2のユーザのICカード300が生成したレスポンスを送信する。
When the second user's terminal 200 receives the response generated by the first user's IC card 300, the second user's IC card 300 includes the first user's IC card included in the response to the second user's IC card 300. A hash of transaction information with a signature of 300 is sent as a challenge. The second user's IC card 300 generates a response to the challenge received from the second user's terminal 200. This response includes a signature of transaction information indicating that 1000 yen is transferred from the first user to the second user. Then, the second user terminal 200 transmits the response generated by the second user IC card 300 to the settlement server.
決済サーバ(サービス事業者400のサーバ)は、第1のユーザのICカード300が生成したレスポンス及び第2のユーザのICカード300が生成したレスポンスを受信する。決済サーバは、双方のレスポンスをIDcd認証サーバ100へ送信する。IDcd認証サーバ100は、決済サーバから受信した2つのレスポンスを照合し、2つのICカード300の真正性の確認と、取引情報の署名の正当性の確認と、を行う。なお、IDcd認証サーバ100は、あくまでICカード300の真正性の確認と、取引情報の署名の正当性の確認と、を行い、取引情報の内容には関知しない。そしてIDcd認証サーバ100は、決済サーバから受信した2つのレスポンスが正当であることが確認出来れば、決済サーバに対して、第1のユーザから第2のユーザへの送金を許可する旨のメッセージを送る。決済サーバは、第1のユーザから第2のユーザへの送金を許可する旨のメッセージをIDcd認証サーバ100から受信すると、第1のユーザの口座から第2のユーザの口座へ1000円を送金する処理を実行する。
The settlement server (the server of the service provider 400) receives the response generated by the IC card 300 of the first user and the response generated by the IC card 300 of the second user. The settlement server transmits both responses to the IDcd authentication server 100. The IDcd authentication server 100 collates two responses received from the settlement server, and confirms the authenticity of the two IC cards 300 and confirms the validity of the signature of the transaction information. Note that the IDcd authentication server 100 only checks the authenticity of the IC card 300 and the validity of the signature of the transaction information, and does not know the content of the transaction information. If the IDcd authentication server 100 can confirm that the two responses received from the settlement server are valid, the IDcd authentication server 100 sends a message to the settlement server to permit the remittance from the first user to the second user. send. When the settlement server receives a message from the IDcd authentication server 100 indicating that the remittance from the first user to the second user is permitted, the settlement server remits 1000 yen from the first user account to the second user account. Execute the process.
このような一連の処理により、ICカードによる認証を利用した個人間の安全かつ簡便な送金が可能となる。
Such a series of processing enables safe and simple remittance between individuals using authentication by IC card.
<2.まとめ>
以上説明したように本開示の実施の形態によれば、オンラインだけでなく、オフラインで利用することを想定したICカードを、サーバにバリューを保持した形態に流用する際に、安全にICカードの認証を行うことが可能なIDcd認証サーバ100を提供することが出来る。 <2. Summary>
As described above, according to the embodiment of the present disclosure, when an IC card that is assumed to be used not only online but also offline is used in a form in which a value is stored in a server, AnIDcd authentication server 100 that can perform authentication can be provided.
以上説明したように本開示の実施の形態によれば、オンラインだけでなく、オフラインで利用することを想定したICカードを、サーバにバリューを保持した形態に流用する際に、安全にICカードの認証を行うことが可能なIDcd認証サーバ100を提供することが出来る。 <2. Summary>
As described above, according to the embodiment of the present disclosure, when an IC card that is assumed to be used not only online but also offline is used in a form in which a value is stored in a server, An
本明細書の各装置が実行する処理における各ステップは、必ずしもシーケンス図またはフローチャートとして記載された順序に沿って時系列に処理する必要はない。例えば、各装置が実行する処理における各ステップは、フローチャートとして記載した順序と異なる順序で処理されても、並列的に処理されてもよい。
Each step in the processing executed by each device in this specification does not necessarily have to be processed in chronological order in the order described as a sequence diagram or flowchart. For example, each step in the processing executed by each device may be processed in an order different from the order described as the flowchart, or may be processed in parallel.
また、各装置に内蔵されるCPU、ROMおよびRAMなどのハードウェアを、上述した各装置の構成と同等の機能を発揮させるためのコンピュータプログラムも作成可能である。また、該コンピュータプログラムを記憶させた記憶媒体も提供されることが可能である。また、機能ブロック図で示したそれぞれの機能ブロックをハードウェアで構成することで、一連の処理をハードウェアで実現することもできる。
In addition, it is possible to create a computer program for causing hardware such as CPU, ROM, and RAM incorporated in each device to exhibit functions equivalent to the configuration of each device described above. A storage medium storing the computer program can also be provided. Moreover, a series of processes can also be realized by hardware by configuring each functional block shown in the functional block diagram with hardware.
なお、上記の各実施例にはICカードを示したが、ICカードは、非接触通信機能を有するICチップを備えたスマートフォン等の携帯端末であってもよい。
In addition, although IC card was shown in said each Example, IC cards may be portable terminals, such as a smart phone provided with IC chip which has a non-contact communication function.
以上、添付図面を参照しながら本開示の好適な実施形態について詳細に説明したが、本開示の技術的範囲はかかる例に限定されない。本開示の技術分野における通常の知識を有する者であれば、特許請求の範囲に記載された技術的思想の範疇内において、各種の変更例または修正例に想到し得ることは明らかであり、これらについても、当然に本開示の技術的範囲に属するものと了解される。
The preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, but the technical scope of the present disclosure is not limited to such examples. It is obvious that a person having ordinary knowledge in the technical field of the present disclosure can come up with various changes or modifications within the scope of the technical idea described in the claims. Of course, it is understood that it belongs to the technical scope of the present disclosure.
また、本明細書に記載された効果は、あくまで説明的または例示的なものであって限定的ではない。つまり、本開示に係る技術は、上記の効果とともに、または上記の効果に代えて、本明細書の記載から当業者には明らかな他の効果を奏しうる。
In addition, the effects described in this specification are merely illustrative or illustrative, and are not limited. That is, the technology according to the present disclosure can exhibit other effects that are apparent to those skilled in the art from the description of the present specification in addition to or instead of the above effects.
なお、以下のような構成も本開示の技術的範囲に属する。
(1)
ICチップを備えた無線通信装置との間で近接非接触通信を行う端末に対して該無線通信装置の認証のための認証データを提供する提供部と、
前記端末から、前記認証データの利用回数を含んだ、前記無線通信装置との間の近接非接触通信により受信した受信データを取得する取得部と、
前記認証データと前記受信データとを用いて前記無線通信装置の認証を行う認証部と、
を備える、サーバ。
(2)
前記提供部は、前記無線通信装置の認証に先立ち、複数の前記認証データを事前に前記端末に提供する、前記(1)に記載のサーバ。
(3)
前記提供部が提供する前記認証データは、最後に認証が行われた際の認証データに基づいて生成されたものである、前記(1)または(2)に記載のサーバ。
(4)
前記提供部は、認証の対象となる無線通信装置の認証時に前記端末から該無線通信装置へ提供するチャレンジと、前記チャレンジに応じて該無線通信装置から前記端末へ返答されるレスポンスとの組を、前記無線通信装置の認証に先立ち前記端末に提供する、前記(1)~(3)のいずれかに記載のサーバ。
(5)
前記認証部は、第1の無線通信装置からの第1の受信データと、第2の無線通信装置からの第2の受信データとを用いて前記第1の無線通信装置及び前記第2の無線通信装置の認証を行う、前記(1)~(4)のいずれかに記載のサーバ。
(6)
前記認証部は、前記第1の無線通信装置及び前記第2の無線通信装置の認証結果に基づき、前記第1の無線通信装置のユーザと前記第2の無線通信装置のユーザとの間の送金処理の可否を決定する、前記(5)に記載のサーバ。
(7)
前記認証部は、前記無線通信装置からの受信データと、取引データと、を用いて、前記取引データの真正性の確認を行う、前記(1)~(4)のいずれかに記載のサーバ。
(8)
前記無線通信装置は、ICチップを内蔵したICカードである、前記(1)~(7)のいずれかに記載のサーバ。
(9)
前記無線通信装置は、ICチップを内蔵した携帯端末である、前記(1)~(7)のいずれかに記載のサーバ。
(10)
ICチップを備えた無線通信装置との間で近接非接触通信を行う端末に対して提供する、該無線通信装置の認証のための認証データを、前記認証データを生成する装置より取得し、取得した前記認証データを前記端末への提供に先立ってキャッシュする、サーバ。
(11)
前記端末が前記無線通信装置を認証する際に、キャッシュした前記認証データを前記端末へ提供する、前記(10)に記載のサーバ。
(12)
前記無線通信装置の認証に際して、前記装置との通信が出来ない場合において、キャッシュした前記認証データを前記端末へ提供する、前記(11)に記載のサーバ。
(13)
所定のタイミングでキャッシュした前記認証データを削除する、前記(10)に記載のサーバ。
(14)
所定のタイミングとして前記認証データの有効期限が経過した時点でキャッシュした前記認証データを削除する、前記(13)に記載のサーバ。
(15)
所定のタイミングとして前記装置との通信が回復するとキャッシュした前記認証データを削除する、前記(13)に記載のサーバ。
(16)
前記無線通信装置は、ICチップを内蔵したICカードである、前記(10)~(15)のいずれかに記載のサーバ。
(17)
前記無線通信装置は、ICチップを内蔵した携帯端末である、前記(10)~(15)のいずれかに記載のサーバ。
(18)
ICチップを備えた無線通信装置との間で近接非接触通信を行う端末に対して該無線通信装置の認証のための認証データを提供することと、
前記端末から、前記認証データの利用回数を含んだ、前記無線通信装置との間の近接非接触通信により受信した受信データを取得することと、
前記認証データと前記受信データとを用いて前記無線通信装置の認証を行うことと、
を含む、認証方法。
(19)
ICチップを備えた無線通信装置と、
前記無線通信装置との間で近接非接触通信を行う端末と、
前記端末に対して該無線通信装置の認証のための認証データを提供するサーバと、
を備え、
前記サーバは、
前記認証データを提供する提供部と、
前記端末から、前記認証データの利用回数を含んだ、前記無線通信装置との間の近接非接触通信により受信した受信データを取得する取得部と、
前記認証データと前記受信データとを用いて前記無線通信装置の認証を行う認証部と、
を備える、認証システム。 The following configurations also belong to the technical scope of the present disclosure.
(1)
A providing unit that provides authentication data for authentication of the wireless communication device to a terminal that performs proximity contactless communication with the wireless communication device including the IC chip;
An acquisition unit for acquiring received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal;
An authentication unit that authenticates the wireless communication device using the authentication data and the received data;
Comprising a server.
(2)
The server according to (1), wherein the providing unit provides a plurality of the authentication data to the terminal in advance prior to authentication of the wireless communication device.
(3)
The server according to (1) or (2), wherein the authentication data provided by the providing unit is generated based on authentication data at the time of last authentication.
(4)
The providing unit includes a set of a challenge to be provided from the terminal to the wireless communication device at the time of authentication of the wireless communication device to be authenticated and a response returned from the wireless communication device to the terminal in response to the challenge. The server according to any one of (1) to (3), which is provided to the terminal prior to authentication of the wireless communication device.
(5)
The authentication unit uses the first reception data from the first wireless communication device and the second reception data from the second wireless communication device to use the first wireless communication device and the second wireless communication device. The server according to any one of (1) to (4), wherein authentication of the communication device is performed.
(6)
The authentication unit transfers money between a user of the first wireless communication device and a user of the second wireless communication device based on an authentication result of the first wireless communication device and the second wireless communication device. The server according to (5), which determines whether or not processing is possible.
(7)
The server according to any one of (1) to (4), wherein the authentication unit confirms the authenticity of the transaction data using received data from the wireless communication device and transaction data.
(8)
The server according to any one of (1) to (7), wherein the wireless communication device is an IC card incorporating an IC chip.
(9)
The server according to any one of (1) to (7), wherein the wireless communication device is a portable terminal incorporating an IC chip.
(10)
Acquire authentication data for authentication of the wireless communication device provided to a terminal that performs proximity contactless communication with a wireless communication device including an IC chip from the device that generates the authentication data, and acquire A server that caches the authentication data prior to provision to the terminal.
(11)
The server according to (10), wherein the authentication data cached is provided to the terminal when the terminal authenticates the wireless communication device.
(12)
The server according to (11), wherein the authentication data cached is provided to the terminal when communication with the device is not possible during authentication of the wireless communication device.
(13)
The server according to (10), wherein the authentication data cached at a predetermined timing is deleted.
(14)
The server according to (13), wherein the authentication data cached when the expiration date of the authentication data elapses as a predetermined timing is deleted.
(15)
The server according to (13), wherein the cached authentication data is deleted when communication with the device is restored at a predetermined timing.
(16)
The server according to any one of (10) to (15), wherein the wireless communication device is an IC card incorporating an IC chip.
(17)
The server according to any one of (10) to (15), wherein the wireless communication device is a portable terminal incorporating an IC chip.
(18)
Providing authentication data for authentication of the wireless communication device to a terminal that performs proximity contactless communication with the wireless communication device including the IC chip;
Obtaining received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal;
Authenticating the wireless communication device using the authentication data and the received data;
Including authentication methods.
(19)
A wireless communication device including an IC chip;
A terminal that performs proximity contactless communication with the wireless communication device;
A server for providing authentication data for authentication of the wireless communication device to the terminal;
With
The server
A providing unit for providing the authentication data;
An acquisition unit for acquiring received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal;
An authentication unit that authenticates the wireless communication device using the authentication data and the received data;
An authentication system comprising:
(1)
ICチップを備えた無線通信装置との間で近接非接触通信を行う端末に対して該無線通信装置の認証のための認証データを提供する提供部と、
前記端末から、前記認証データの利用回数を含んだ、前記無線通信装置との間の近接非接触通信により受信した受信データを取得する取得部と、
前記認証データと前記受信データとを用いて前記無線通信装置の認証を行う認証部と、
を備える、サーバ。
(2)
前記提供部は、前記無線通信装置の認証に先立ち、複数の前記認証データを事前に前記端末に提供する、前記(1)に記載のサーバ。
(3)
前記提供部が提供する前記認証データは、最後に認証が行われた際の認証データに基づいて生成されたものである、前記(1)または(2)に記載のサーバ。
(4)
前記提供部は、認証の対象となる無線通信装置の認証時に前記端末から該無線通信装置へ提供するチャレンジと、前記チャレンジに応じて該無線通信装置から前記端末へ返答されるレスポンスとの組を、前記無線通信装置の認証に先立ち前記端末に提供する、前記(1)~(3)のいずれかに記載のサーバ。
(5)
前記認証部は、第1の無線通信装置からの第1の受信データと、第2の無線通信装置からの第2の受信データとを用いて前記第1の無線通信装置及び前記第2の無線通信装置の認証を行う、前記(1)~(4)のいずれかに記載のサーバ。
(6)
前記認証部は、前記第1の無線通信装置及び前記第2の無線通信装置の認証結果に基づき、前記第1の無線通信装置のユーザと前記第2の無線通信装置のユーザとの間の送金処理の可否を決定する、前記(5)に記載のサーバ。
(7)
前記認証部は、前記無線通信装置からの受信データと、取引データと、を用いて、前記取引データの真正性の確認を行う、前記(1)~(4)のいずれかに記載のサーバ。
(8)
前記無線通信装置は、ICチップを内蔵したICカードである、前記(1)~(7)のいずれかに記載のサーバ。
(9)
前記無線通信装置は、ICチップを内蔵した携帯端末である、前記(1)~(7)のいずれかに記載のサーバ。
(10)
ICチップを備えた無線通信装置との間で近接非接触通信を行う端末に対して提供する、該無線通信装置の認証のための認証データを、前記認証データを生成する装置より取得し、取得した前記認証データを前記端末への提供に先立ってキャッシュする、サーバ。
(11)
前記端末が前記無線通信装置を認証する際に、キャッシュした前記認証データを前記端末へ提供する、前記(10)に記載のサーバ。
(12)
前記無線通信装置の認証に際して、前記装置との通信が出来ない場合において、キャッシュした前記認証データを前記端末へ提供する、前記(11)に記載のサーバ。
(13)
所定のタイミングでキャッシュした前記認証データを削除する、前記(10)に記載のサーバ。
(14)
所定のタイミングとして前記認証データの有効期限が経過した時点でキャッシュした前記認証データを削除する、前記(13)に記載のサーバ。
(15)
所定のタイミングとして前記装置との通信が回復するとキャッシュした前記認証データを削除する、前記(13)に記載のサーバ。
(16)
前記無線通信装置は、ICチップを内蔵したICカードである、前記(10)~(15)のいずれかに記載のサーバ。
(17)
前記無線通信装置は、ICチップを内蔵した携帯端末である、前記(10)~(15)のいずれかに記載のサーバ。
(18)
ICチップを備えた無線通信装置との間で近接非接触通信を行う端末に対して該無線通信装置の認証のための認証データを提供することと、
前記端末から、前記認証データの利用回数を含んだ、前記無線通信装置との間の近接非接触通信により受信した受信データを取得することと、
前記認証データと前記受信データとを用いて前記無線通信装置の認証を行うことと、
を含む、認証方法。
(19)
ICチップを備えた無線通信装置と、
前記無線通信装置との間で近接非接触通信を行う端末と、
前記端末に対して該無線通信装置の認証のための認証データを提供するサーバと、
を備え、
前記サーバは、
前記認証データを提供する提供部と、
前記端末から、前記認証データの利用回数を含んだ、前記無線通信装置との間の近接非接触通信により受信した受信データを取得する取得部と、
前記認証データと前記受信データとを用いて前記無線通信装置の認証を行う認証部と、
を備える、認証システム。 The following configurations also belong to the technical scope of the present disclosure.
(1)
A providing unit that provides authentication data for authentication of the wireless communication device to a terminal that performs proximity contactless communication with the wireless communication device including the IC chip;
An acquisition unit for acquiring received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal;
An authentication unit that authenticates the wireless communication device using the authentication data and the received data;
Comprising a server.
(2)
The server according to (1), wherein the providing unit provides a plurality of the authentication data to the terminal in advance prior to authentication of the wireless communication device.
(3)
The server according to (1) or (2), wherein the authentication data provided by the providing unit is generated based on authentication data at the time of last authentication.
(4)
The providing unit includes a set of a challenge to be provided from the terminal to the wireless communication device at the time of authentication of the wireless communication device to be authenticated and a response returned from the wireless communication device to the terminal in response to the challenge. The server according to any one of (1) to (3), which is provided to the terminal prior to authentication of the wireless communication device.
(5)
The authentication unit uses the first reception data from the first wireless communication device and the second reception data from the second wireless communication device to use the first wireless communication device and the second wireless communication device. The server according to any one of (1) to (4), wherein authentication of the communication device is performed.
(6)
The authentication unit transfers money between a user of the first wireless communication device and a user of the second wireless communication device based on an authentication result of the first wireless communication device and the second wireless communication device. The server according to (5), which determines whether or not processing is possible.
(7)
The server according to any one of (1) to (4), wherein the authentication unit confirms the authenticity of the transaction data using received data from the wireless communication device and transaction data.
(8)
The server according to any one of (1) to (7), wherein the wireless communication device is an IC card incorporating an IC chip.
(9)
The server according to any one of (1) to (7), wherein the wireless communication device is a portable terminal incorporating an IC chip.
(10)
Acquire authentication data for authentication of the wireless communication device provided to a terminal that performs proximity contactless communication with a wireless communication device including an IC chip from the device that generates the authentication data, and acquire A server that caches the authentication data prior to provision to the terminal.
(11)
The server according to (10), wherein the authentication data cached is provided to the terminal when the terminal authenticates the wireless communication device.
(12)
The server according to (11), wherein the authentication data cached is provided to the terminal when communication with the device is not possible during authentication of the wireless communication device.
(13)
The server according to (10), wherein the authentication data cached at a predetermined timing is deleted.
(14)
The server according to (13), wherein the authentication data cached when the expiration date of the authentication data elapses as a predetermined timing is deleted.
(15)
The server according to (13), wherein the cached authentication data is deleted when communication with the device is restored at a predetermined timing.
(16)
The server according to any one of (10) to (15), wherein the wireless communication device is an IC card incorporating an IC chip.
(17)
The server according to any one of (10) to (15), wherein the wireless communication device is a portable terminal incorporating an IC chip.
(18)
Providing authentication data for authentication of the wireless communication device to a terminal that performs proximity contactless communication with the wireless communication device including the IC chip;
Obtaining received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal;
Authenticating the wireless communication device using the authentication data and the received data;
Including authentication methods.
(19)
A wireless communication device including an IC chip;
A terminal that performs proximity contactless communication with the wireless communication device;
A server for providing authentication data for authentication of the wireless communication device to the terminal;
With
The server
A providing unit for providing the authentication data;
An acquisition unit for acquiring received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal;
An authentication unit that authenticates the wireless communication device using the authentication data and the received data;
An authentication system comprising:
100 IDcd認証サーバ
200 端末
300 ICカード 100IDcd authentication server 200 Terminal 300 IC card
200 端末
300 ICカード 100
Claims (19)
- ICチップを備えた無線通信装置との間で近接非接触通信を行う端末に対して該無線通信装置の認証のための認証データを提供する提供部と、
前記端末から、前記認証データの利用回数を含んだ、前記無線通信装置との間の近接非接触通信により受信した受信データを取得する取得部と、
前記認証データと前記受信データとを用いて前記無線通信装置の認証を行う認証部と、
を備える、サーバ。 A providing unit that provides authentication data for authentication of the wireless communication device to a terminal that performs proximity contactless communication with the wireless communication device including the IC chip;
An acquisition unit for acquiring received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal;
An authentication unit that authenticates the wireless communication device using the authentication data and the received data;
Comprising a server. - 前記提供部は、前記無線通信装置の認証に先立ち、複数の前記認証データを事前に前記端末に提供する、請求項1に記載のサーバ。 The server according to claim 1, wherein the providing unit provides a plurality of the authentication data to the terminal in advance prior to authentication of the wireless communication device.
- 前記提供部が提供する前記認証データは、最後に認証が行われた際の認証データに基づいて生成されたものである、請求項1に記載のサーバ。 The server according to claim 1, wherein the authentication data provided by the providing unit is generated based on authentication data when authentication is performed last time.
- 前記提供部は、認証の対象となる無線通信装置の認証時に前記端末から該無線通信装置へ提供するチャレンジと、前記チャレンジに応じて該無線通信装置から前記端末へ返答されるレスポンスとの組を、前記無線通信装置の認証に先立ち前記端末に提供する、請求項1に記載のサーバ。 The providing unit includes a set of a challenge to be provided from the terminal to the wireless communication device at the time of authentication of the wireless communication device to be authenticated and a response returned from the wireless communication device to the terminal in response to the challenge. The server according to claim 1, wherein the server is provided to the terminal prior to authentication of the wireless communication device.
- 前記認証部は、第1の無線通信装置からの第1の受信データと、第2の無線通信装置からの第2の受信データとを用いて前記第1の無線通信装置及び前記第2の無線通信装置の認証を行う、請求項1に記載のサーバ。 The authentication unit uses the first reception data from the first wireless communication device and the second reception data from the second wireless communication device to use the first wireless communication device and the second wireless communication device. The server according to claim 1, wherein authentication of the communication device is performed.
- 前記認証部は、前記第1の無線通信装置及び前記第2の無線通信装置の認証結果に基づき、前記第1の無線通信装置のユーザと前記第2の無線通信装置のユーザとの間の送金処理の可否を決定する、請求項5に記載のサーバ。 The authentication unit transfers money between a user of the first wireless communication device and a user of the second wireless communication device based on an authentication result of the first wireless communication device and the second wireless communication device. The server according to claim 5, which determines whether processing is possible.
- 前記認証部は、前記無線通信装置からの受信データと、取引データと、を用いて、前記取引データの真正性の確認を行う、請求項1に記載のサーバ。 The server according to claim 1, wherein the authentication unit confirms the authenticity of the transaction data using received data from the wireless communication device and transaction data.
- 前記無線通信装置は、ICチップを内蔵したICカードである、請求項1に記載のサーバ。 The server according to claim 1, wherein the wireless communication device is an IC card having an IC chip built therein.
- 前記無線通信装置は、ICチップを内蔵した携帯端末である、請求項1に記載のサーバ。 The server according to claim 1, wherein the wireless communication device is a portable terminal with a built-in IC chip.
- ICチップを備えた無線通信装置との間で近接非接触通信を行う端末に対して提供する、該無線通信装置の認証のための認証データを、前記認証データを生成する装置より取得し、取得した前記認証データを前記端末への提供に先立ってキャッシュする、サーバ。 Acquire authentication data for authentication of the wireless communication device provided to a terminal that performs proximity contactless communication with a wireless communication device including an IC chip from the device that generates the authentication data, and acquire A server that caches the authentication data prior to provision to the terminal.
- 前記端末が前記無線通信装置を認証する際に、キャッシュした前記認証データを前記端末へ提供する、請求項10に記載のサーバ。 The server according to claim 10, wherein when the terminal authenticates the wireless communication device, the cached authentication data is provided to the terminal.
- 前記無線通信装置の認証に際して、前記装置との通信が出来ない場合において、キャッシュした前記認証データを前記端末へ提供する、請求項11に記載のサーバ。 12. The server according to claim 11, wherein, when authentication of the wireless communication device is performed, if the communication with the device is not possible, the cached authentication data is provided to the terminal.
- 所定のタイミングでキャッシュした前記認証データを削除する、請求項10に記載のサーバ。 The server according to claim 10, wherein the authentication data cached at a predetermined timing is deleted.
- 所定のタイミングとして前記認証データの有効期限が経過した時点でキャッシュした前記認証データを削除する、請求項13に記載のサーバ。 14. The server according to claim 13, wherein the authentication data cached when the expiration date of the authentication data has passed as a predetermined timing is deleted.
- 所定のタイミングとして前記装置との通信が回復するとキャッシュした前記認証データを削除する、請求項13に記載のサーバ。 The server according to claim 13, wherein the cached authentication data is deleted when communication with the device is restored at a predetermined timing.
- 前記無線通信装置は、ICチップを内蔵したICカードである、請求項10に記載のサーバ。 The server according to claim 10, wherein the wireless communication device is an IC card having an IC chip built therein.
- 前記無線通信装置は、ICチップを内蔵した携帯端末である、請求項10に記載のサーバ。 The server according to claim 10, wherein the wireless communication device is a portable terminal incorporating an IC chip.
- ICチップを備えた無線通信装置との間で近接非接触通信を行う端末に対して該無線通信装置の認証のための認証データを提供することと、
前記端末から、前記認証データの利用回数を含んだ、前記無線通信装置との間の近接非接触通信により受信した受信データを取得することと、
前記認証データと前記受信データとを用いて前記無線通信装置の認証を行うことと、
を含む、認証方法。 Providing authentication data for authentication of the wireless communication device to a terminal that performs proximity contactless communication with the wireless communication device including the IC chip;
Obtaining received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal;
Authenticating the wireless communication device using the authentication data and the received data;
Including authentication methods. - ICチップを備えた無線通信装置と、
前記無線通信装置との間で近接非接触通信を行う端末と、
前記端末に対して該無線通信装置の認証のための認証データを提供するサーバと、
を備え、
前記サーバは、
前記認証データを提供する提供部と、
前記端末から、前記認証データの利用回数を含んだ、前記無線通信装置との間の近接非接触通信により受信した受信データを取得する取得部と、
前記認証データと前記受信データとを用いて前記無線通信装置の認証を行う認証部と、
を備える、認証システム。 A wireless communication device including an IC chip;
A terminal that performs proximity contactless communication with the wireless communication device;
A server for providing authentication data for authentication of the wireless communication device to the terminal;
With
The server
A providing unit for providing the authentication data;
An acquisition unit for acquiring received data received by proximity non-contact communication with the wireless communication device, including the number of times of use of the authentication data, from the terminal;
An authentication unit that authenticates the wireless communication device using the authentication data and the received data;
An authentication system comprising:
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201880011054.4A CN110268433A (en) | 2017-02-17 | 2018-02-06 | Server and authentication method |
EP18753632.1A EP3584755A4 (en) | 2017-02-17 | 2018-02-06 | Server and authentication system |
JP2018568119A JP7024738B2 (en) | 2017-02-17 | 2018-02-06 | Server and authentication method |
US16/482,559 US20200005298A1 (en) | 2017-02-17 | 2018-02-06 | Server and authentication method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2017028300 | 2017-02-17 | ||
JP2017-028300 | 2017-02-17 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018150931A1 true WO2018150931A1 (en) | 2018-08-23 |
Family
ID=63169352
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2018/003879 WO2018150931A1 (en) | 2017-02-17 | 2018-02-06 | Server and authentication system |
Country Status (5)
Country | Link |
---|---|
US (1) | US20200005298A1 (en) |
EP (1) | EP3584755A4 (en) |
JP (1) | JP7024738B2 (en) |
CN (1) | CN110268433A (en) |
WO (1) | WO2018150931A1 (en) |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002198955A (en) * | 2000-12-27 | 2002-07-12 | Falcon System Consulting Kk | Weighted security system for network communication |
US20050102188A1 (en) * | 1999-06-18 | 2005-05-12 | Hutchison Robin B. | Method and apparatus for ordering goods, services and content over an internetwork using a virtual payment account |
JP2007148470A (en) * | 2005-11-24 | 2007-06-14 | Hitachi Ltd | Processor, auxiliary information generation device, terminal device, authentication device, and biometrics system |
JP2009110202A (en) | 2007-10-29 | 2009-05-21 | Sony Corp | Electronic wallet device, communication method and program |
JP2009230181A (en) * | 2008-03-19 | 2009-10-08 | Seiko Epson Corp | Transmission device, content transmission system, content transmission method, and computer program |
JP2011031797A (en) * | 2009-08-04 | 2011-02-17 | Alpha Corp | Steering lock system and random number generating method thereof |
JP2015036257A (en) * | 2013-08-12 | 2015-02-23 | 凸版印刷株式会社 | Vehicular anti-theft system |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2377706A1 (en) | 1999-06-18 | 2000-12-28 | Echarge Corporation | Method and apparatus for ordering goods, services and content over an internetwork using a virtual payment account |
US20100223186A1 (en) * | 2000-04-11 | 2010-09-02 | Hogan Edward J | Method and System for Conducting Secure Payments |
US8689013B2 (en) * | 2008-10-21 | 2014-04-01 | G. Wouter Habraken | Dual-interface key management |
CN101848430B (en) * | 2009-03-24 | 2014-01-22 | 阿尔卡特朗讯 | Device and method for service request authentication, service request authentication system and method of service request authentication system |
JP5657364B2 (en) * | 2010-12-08 | 2015-01-21 | フェリカネットワークス株式会社 | Information processing apparatus and method, program, and information processing system |
-
2018
- 2018-02-06 WO PCT/JP2018/003879 patent/WO2018150931A1/en unknown
- 2018-02-06 CN CN201880011054.4A patent/CN110268433A/en not_active Withdrawn
- 2018-02-06 US US16/482,559 patent/US20200005298A1/en not_active Abandoned
- 2018-02-06 EP EP18753632.1A patent/EP3584755A4/en not_active Withdrawn
- 2018-02-06 JP JP2018568119A patent/JP7024738B2/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050102188A1 (en) * | 1999-06-18 | 2005-05-12 | Hutchison Robin B. | Method and apparatus for ordering goods, services and content over an internetwork using a virtual payment account |
JP2002198955A (en) * | 2000-12-27 | 2002-07-12 | Falcon System Consulting Kk | Weighted security system for network communication |
JP2007148470A (en) * | 2005-11-24 | 2007-06-14 | Hitachi Ltd | Processor, auxiliary information generation device, terminal device, authentication device, and biometrics system |
JP2009110202A (en) | 2007-10-29 | 2009-05-21 | Sony Corp | Electronic wallet device, communication method and program |
JP2009230181A (en) * | 2008-03-19 | 2009-10-08 | Seiko Epson Corp | Transmission device, content transmission system, content transmission method, and computer program |
JP2011031797A (en) * | 2009-08-04 | 2011-02-17 | Alpha Corp | Steering lock system and random number generating method thereof |
JP2015036257A (en) * | 2013-08-12 | 2015-02-23 | 凸版印刷株式会社 | Vehicular anti-theft system |
Non-Patent Citations (1)
Title |
---|
See also references of EP3584755A4 |
Also Published As
Publication number | Publication date |
---|---|
JP7024738B2 (en) | 2022-02-24 |
EP3584755A4 (en) | 2020-07-29 |
CN110268433A (en) | 2019-09-20 |
EP3584755A1 (en) | 2019-12-25 |
US20200005298A1 (en) | 2020-01-02 |
JPWO2018150931A1 (en) | 2019-12-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR102044747B1 (en) | Method for providing user authentication service based on blockchain | |
RU2711464C2 (en) | Multiple-device transaction verification | |
RU2648944C2 (en) | Methods, devices, and systems for secure provisioning, transmission and authentication of payment data | |
CN107251595B (en) | Secure authentication of users and mobile devices | |
CN108292334A (en) | Wireless living things feature recognition Verification System and method | |
CN110462663A (en) | For indicating the static token system and method for dynamic authentic credential | |
CN105933119B (en) | A kind of authentication method and equipment | |
EP3411846A1 (en) | Systems and methods for code display and use | |
CN106465112A (en) | Offline authentication | |
WO2016009494A1 (en) | Card settlement terminal and card settlement system | |
WO2010003202A2 (en) | System, method and device to authenticate relationships by electronic means | |
KR101092657B1 (en) | Mobile card payment system and method thereof | |
CN103198405A (en) | Intelligent payment method and system based on camera scanning verification | |
US10657523B2 (en) | Reconciling electronic transactions | |
CN102238193A (en) | Data authentication method and system using same | |
CN111062717B (en) | Data transfer processing method, device and computer readable storage medium | |
KR102333811B1 (en) | System and method for processing card payment based on block-chain | |
CN112513904A (en) | Digital asset transaction control method and device, terminal equipment and storage medium | |
CN109496405A (en) | Utilize the more device authentication processes and system of cryptographic technique | |
CN105005732A (en) | Electronic certificate non-contact recognizing and verifying method based on wireless hardware character | |
KR20010087564A (en) | User authentification system and the method using personal mobile device | |
KR102348823B1 (en) | System and Method for Identification Based on Finanace Card Possessed by User | |
JP7024738B2 (en) | Server and authentication method | |
KR20210017308A (en) | Method for providing secondary authentication service using device registration and distributed storage of data | |
KR20230004042A (en) | An apparatus for providing payment services of a distributed token for encrypted data of payment information to be used only by a specific franchisee and a method for operating it |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18753632 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2018568119 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2018753632 Country of ref document: EP Effective date: 20190917 |