WO2020003337A1

WO2020003337A1 - Server device and system

Info

Publication number: WO2020003337A1
Application number: PCT/JP2018/023928
Authority: WO
Inventors: 三露　学
Original assignee: Quadrac株式会社
Priority date: 2018-06-25
Filing date: 2018-06-25
Publication date: 2020-01-02

Abstract

[Problem] To provide a server device or the like in which the management of key information is simple, and which is capable of suppressing the degradation of security, which is caused by key information of a plurality of service providers intermingled in one SAM device. [Solution] This server device is included in a system provided with: at least one first user device which stores first key information; at least one second user device which stores second key information; a client device which is capable of performing near field communication with any one among the first user device and the second user device; the server device which is connected to the client device through a network; and a plurality of SAM devices which are connected to the server device, and include at least one first SAM device which stores the first key information and at least one second SAM device which stores the second key information.

Description

Server device and system

(4) The present disclosure relates to a server device and a system.

A system having one SAM and a plurality of non-contact IC chips has been proposed in Patent Document 1 (Patent Document 1). In Patent Document 1, one SAM has all the encryption keys stored in each of a plurality of non-contact IC chips, and one SAM can read and write information from or to any of the non-contact IC chips. Have been.

JP 2006-98830 A

However, according to the above system, since encryption keys of a plurality of service providers are mixed in one SAM, management of the encryption keys becomes difficult or complicated, and security may be reduced.

課題 The above problem can be solved, for example, by the following embodiment of the present invention.

Short-range wireless communication with at least one first user device that stores first key information, at least one second user device that stores second key information, and with each of the first user device and the second user device Device, a server device connected to the client device via a network, at least one first SAM device connected to the server device and storing the first key information, and the second A plurality of SAM devices including at least one second SAM device for storing key information, and the server device in a system including: a communication partner of the client device is the first user device; Selecting one of the first SAM devices from a plurality of SAM devices, and issuing a command to the selected one of the first SAM devices; Requesting encryption, receiving the encrypted command from the selected one of the first SAM devices, transmitting the encrypted command to the first user device via the client device, Receiving an encrypted response from the device via the client device, reselecting the same one of the selected first SAM devices as the selected one of the first SAM devices, and selecting the reselected one of the first SAM devices; Requesting the client device to decrypt the received encrypted response, receiving the decrypted response from the reselected one of the first SAM devices, processing the response, and communicating with the client device. Is the second user device, selects one of the plurality of SAM devices, the second SAM device, and selects the selected one of the second SAM devices. Requesting command encryption for the second SAM device, receiving the encrypted command from the selected one of the second SAM devices, transmitting the encrypted command to the second user device via the client device, Receiving an encrypted response from the second user device via the client device, reselecting the same one second SAM device as the selected one second SAM device, and reselecting the reselected one A server device that requests the second SAM device to decrypt the received encrypted response, receives the decrypted response from the reselected one of the second SAM devices, and processes the response.

According to an embodiment of the present invention, SAM devices are allocated to each service provider (that is, key information of a plurality of service providers is not mixed in one SAM device), and different service providers are used. It is possible to read and write data in a plurality of user devices that contract with the user. Therefore, it is possible to provide a server device and a system that can easily manage key information and can suppress a decrease in security due to a mixture of key information of a plurality of service providers in one SAM device.

1 is a diagram illustrating a configuration example of a system 1 according to a first embodiment. FIG. 3 is a sequence diagram illustrating an operation example of the system 1 according to the first embodiment. FIG. 3 is a sequence diagram illustrating an operation example of the system 1 according to the first embodiment. FIG. 6 is a diagram illustrating an example of a SAM device management table. FIG. 13 is a sequence diagram partially showing an operation example of the system according to the second embodiment.

[System 1 according to Embodiment 1]
FIG. 1 is a diagram illustrating a configuration example of a system 1 according to the first embodiment. As shown in FIG. 1, the system 1 includes at least one first user device 11 that stores first key information A, at least one second user device 12 that stores second key information B, A client device 20 for performing short-range wireless communication with the device 11 or the second user device 12, a server device 30 connected to the client device 20 via a network NW, and a first key information A connected to the server device 30; This is a system including a plurality of SAM devices including at least one first SAM device 41 that stores therein and at least one second SAM device 42 that stores second key information B. The details will be described below.

(First User Device 11, Second User Device 12)
The first user device 11 and the second user device 12 are devices owned and operated by the user. More specifically, the first user device 11 is a user device used by a user who makes a contract with a first service provider, and the second user device 12 is used by a user who makes a contract with a second service provider. User device. The first user device 11 and the second user device 12 include a smartphone, an IC card (Integrated Circuit Card) or a smart card (Smart Card) in which a non-contact IC chip or a non-contact IC chip function is incorporated. Can be

The first user device 11 and the second user device 12 (more specifically, for example, a storage area in the above-described non-contact IC chip or a storage area of a device having a non-contact IC chip function) store the first data The second data is respectively stored. The first data and the second data are data handled in the system 1. For example, in addition to the balance of electronic money, personal information such as name, date of birth, gender, address, card ID, expiration date of the card, floor Limits and card usage history can be included in this. The floor limit is the minimum amount that requires authorization (credit approval). Authorization means that a credit card member store confirms the credit of a card user (card member) with a card company. For the settlement of the amount less than the floor limit, the authorization can be set to be unnecessary, and the settlement can be completed without performing the authorization. However, it is also possible to set the floor limit to 0 yen, and in this case, authorization is required for virtually all settlements. By causing the first user device 11 to execute the command received from the first SAM device 41, the client device 20 reads or writes the first data stored in the first user device 11 (hereinafter, reading is referred to as reading). And writing is sometimes called writing.) Similarly, the client device 20 reads or writes the second data stored in the second user device 12 by causing the second user device 12 to execute the command received from the second SAM device 42.

The first user device 11 and the second user device 12 (more specifically, for example, a storage area in the above-described non-contact IC chip or a storage area of a device having a non-contact IC chip function) have a first key. Information A and second key information B are respectively stored. The second key information B is key information different from the first key information A. That is, the first key information A takes a value different from that of the second key information B.

In the present embodiment, in order to facilitate understanding, the system 1 has one first user device 11 and one second user device 12, but the number of first user devices 11 and second user devices 12 May be two, three, or four or more. Also, in addition to the first user device 11 and the second user device 12, a user device that stores key information different from the first user device 11 and the second user device 12, such as a third user device and a fourth user device. May exist.

(Client device 20)
The client device 20 is a device capable of performing short-range wireless communication with any of the first user device 11 and the second user device 12, for example, a cash register device installed in a supermarket or a convenience store, a ticket gate of a station, and the like. Ticket gate installed at the entrance, Electronic Toll Collection System (ETC) installed at the entrance of the highway, terminals installed at government offices, terminals installed at leisure facilities such as amusement parks, movie theaters and zoos (entrance And / or a terminal that charges when leaving), a cash register of a restaurant such as a restaurant, and the like. For example, a reader / writer that enables communication with the first user device 11 or the second user device 12 is built in or externally attached to the client device 20. In this case, the client device 20 can communicate with the first user device 11 and the second user device 12 via the reader / writer. The client device 20 can communicate with either the first user device 11 or the second user device 12, but can communicate with only one of the user devices at a time. However, as a result of the time-division communication being performed at a relatively high speed, there may be cases where communication can be regarded as simultaneous with a plurality of user devices.

Communication between the client device 20 and the first user device 11 or the second user device 12 is performed by short-range wireless communication. The short-range wireless communication includes a method in which the client device 20 and the first user device 11 and the second user device 12 perform communication without contact, such as NFC (Near Field Communication), and a client device, such as ISO7816. A method of performing communication by contacting the first user device 11 and the second user device 12 with the user device 20 may be included.

In the present embodiment, in order to facilitate understanding, the system 1 has one client device 20, but the number of client devices 20 may be two, three, or four. There may be more than one.

(Server device 30)
The server device 30 is a device connected to the client device 20 via the network NW. The network NW is, for example, the Internet. Communication between the client device 20 and the server device 30 is performed in accordance with a protocol such as HTTPS, TCP / IP, or UDP. The server device 30 includes, for example, an arithmetic device including a CPU and a storage device including a RAM and a hard disk. For example, programs and data are stored in the storage device, and the server device 30 operates when, for example, the arithmetic device reads out and executes the program from the storage device. Note that the data may include a SAM management table described later. The server device 30 may be a single device, but the processing of the server device 30 may be distributed to a plurality of devices. In this case, when viewed from the client device 20, the server device 30 substantially appears to be operating as a single device, and thus the entire plurality of devices are regarded as the server device 30.

For example, encrypted commands and responses are transmitted and received between the server device 30 and the client device 20 in a packet format. That is, the server device 30 transmits, for example, a packet including the encrypted command in the payload portion to the client device 20. In other words, the server device 30 transmits the encrypted command or the data obtained by adding other data to the encrypted command to the client device 20 with a header added. When receiving the packet from the server device 30, the client device 20 extracts the encrypted command from the received packet and transmits the command to the first user device 11 and the second user device 12. Similarly, the client device 20 transmits, for example, a packet including the encrypted response in the payload portion to the server device 30. In other words, the client device 20 transmits the encrypted response or the data obtained by adding other data to the encrypted response to the server device 30 with the header added. When receiving the packet from the client device 20, the server device 30 extracts an encrypted response from the received packet and transmits the response to the first SAM device 41 and the second SAM device 42.

The payload portion or the header portion of the packet transmitted from the client device 20 to the server device 30 preferably includes client device identification information for identifying the client device 20, and further includes key information identification information. Is more preferable. Furthermore, the payload part or the header part of the packet transmitted and received between the client device 20 and the server device 30 may include a session ID, a sequence number, and the like. When the client device identification information is included in the packet, reselection of the first SAM device 41 and the second SAM device 42 by the server device 30 becomes easy. When the key information identification information is included in the packet, the selection of the first SAM device 41 or the second SAM device 42 by the server device 30 becomes easy.

In the present embodiment, in order to facilitate understanding, the system 1 has one server device 30, but the number of server devices 30 may be two or three. Or four or more. In this case, the client device can switch the server device as the communication partner. In the case where a plurality of client devices are arranged, for example, the communication destination of one or more client devices arranged in a certain area or a commercial facility is set to one server device, and the communication destination is set in another area or a commercial facility. By setting the communication destination of one or more client devices arranged in the server to another server device, the load on the server device can be reduced.

(Multiple SAM devices)
The SAM device is a device having a function of a SAM (Secure Application Module). The plurality of SAM devices include at least one first SAM device 41 that stores first key information A and at least one second SAM device 42 that stores second key information B. The first SAM device 41 is a SAM device that stores key information assigned to a first service provider, and the second SAM device 42 is a SAM device that stores key information allocated to a second service provider. is there. The first key information A and the second key information B are also stored in the first user device 11 and the second user device 12, respectively. That is, the first SAM device 41 and the first user device 11 store common key information, and the second SAM device 42 and the second user device 12 store common key information.

SAM devices include those capable of storing only key information assigned to one service provider and those capable of storing key information assigned to a plurality of service providers. . However, in the present embodiment, even when the latter SAM device is used, one SAM device stores only the key information assigned to one service provider. In other words, in the case of using the latter SAM device, it is possible to store key information assigned to a plurality of service providers in one SAM device according to the specifications and structure of the SAM device. In the embodiment, even when such a SAM device is used, one SAM device stores only the key information assigned to one service provider.

(1) Only one key information assigned to one service provider may be stored in one SAM device. For example, when there are 10 SAM devices, one of them stores one piece of key information P assigned to the first service provider, and the remaining four units are assigned to the second service provider. The stored key information Q can be stored. This makes it possible to associate the key information with the SAM device on a one-to-one basis, thereby simplifying the management of the key information.

{On the other hand, one SAM device may store a plurality of pieces of key information assigned to one service provider. For example, when there are ten SAM devices, a plurality of key information P1... PN (N is an integer of 2 or more) assigned to the first service provider is stored in each of the six SAM devices, and the remaining SAM devices are stored. A plurality of pieces of key information Q1... QN (N is an integer of 2 or more) assigned to the second service provider can be stored in each of the four units. That is, the former six SAM devices each store a plurality of key information P1... PN (N is an integer of 2 or more), and the latter four SAM devices each store a plurality of key information Q1. (N is an integer of 2 or more). In this way, for example, even if one key information assigned to one service provider leaks out, the key information is converted from the one key information without replacing the SAM device. By switching to other key information assigned to the service provider, security can be ensured. When the number of users of one service provider is large, it is possible to store key information assigned to one service provider in a plurality of SAM devices and connect them to a server device in order to improve processing capacity. It is valid. However, when only one key information assigned to one service provider is stored in one SAM device, a plurality of SAM devices for one service provider are required when the one key information leaks. For example, it is necessary to perform a recovery operation such as replacing all of the SAMs or storing new key information in all the SAM devices for one service provider. However, if a plurality of pieces of key information assigned to the one service provider are stored in each of the plurality of SAM apparatuses for one service provider, the key can be changed without replacing the SAM apparatus as described above. Information can be switched. Therefore, even when the key information is leaked, security can be easily maintained.

The first key information A and the second key information B are key information used in mutual authentication, and are assigned to each service provider. For example, when the first key information A is assigned to the Suica (registered trademark) service provider, a different second key information B is assigned to the Edy (registered trademark) service provider. Shall be. Further, the first key information A is, for example, a secret key of the first SAM device 41 and the first user device 11, and the second key information B is, for example, the second SAM device 42 and the second user device 12 Is the secret key possessed by. Mutual authentication means that the user device authenticates the SAM device and the SAM device authenticates the user device by confirming that the user device and the SAM device have the same key information. Mutual authentication confirms the authenticity of each other. That is, it is confirmed that the SAM device is not forged for the user device, and that the user device is not forged for the SAM device.

Mutual authentication can be performed in various ways. An example is as follows.
(1) First, the SAM device generates a first random number, encrypts the first random number with the key information of its own device, and transmits it to the user device.
(2) Next, the user device receives the encrypted first random number from the SAM device, decrypts the encrypted first random number with the key information of the user device, obtains the first random number, and uses the obtained first random number as the self device. Encrypt with the key information of the device. Further, the user device generates a second random number and encrypts the second random number with key information of the user device. Then, the user device transmits the encrypted first random number and the encrypted second random number to the SAM device.
(3) Next, the SAM device receives the encrypted first random number from the user device, decrypts the encrypted first random number with the key information of the own device, obtains the first random number, and obtains the first random number in (1). Compare with the generated first random number. If they match, it is determined that the user device has the same key information, and the user device is authenticated.
(4) In addition, the SAM device receives the encrypted second random number from the user device, decrypts the encrypted second random number with the key information of the device itself, obtains the second random number, and transmits the obtained second random number to the device itself. Is encrypted with the key information possessed by. Then, the SAM device transmits the encrypted second random number to the user device.
(5) Next, the user apparatus receives the encrypted second random number from the SAM apparatus, decrypts the encrypted second random number with the key information of the user apparatus to obtain the second random number, and obtains the second random number in (2) above. Compare with the generated second random number. If they match, it is determined that the SAM device has the same key information, and the SAM device is authenticated.

The first SAM device 41 and the first user device 11 generate a first session key using, for example, a random number generated at the time of mutual authentication. Then, the first SAM device 41 uses the generated first session key to encrypt the command for the first user device 11 and to decrypt the response received from the first user device 11. In addition, the first user device 11 uses the generated first session key to decrypt the command received from the first SAM device 41 and encrypt the response to the first SAM device 41. Similarly, the second SAM device 42 and the second user device 12 generate a second session key using, for example, a random number generated during mutual authentication. Then, the second SAM device 42 uses the generated second session key to encrypt the command for the second user device 12 and to decrypt the response received from the second user device 12. Further, the second user device 12 uses the generated second session key to decrypt the command received from the second SAM device 42 and encrypt the response to the second SAM device 42. If the first session key and the second session key are generated by using random numbers generated at the time of mutual authentication (for example, the first random number, the second random number, or a combination thereof), these are used. Since the value of the key may be different for each mutual authentication, security is improved. In this embodiment, one session is started by one mutual authentication, and another session is started when the mutual authentication is performed again. The first session key and the second session key are key information that can take different values each time mutual authentication is performed, and are substantially effective only for one mutual authentication, that is, only for one session. For this reason, the first session key and the second session key are referred to as “session keys”.

(4) The encryption algorithm is common between service providers, that is, between SAM devices used by each service provider. For example, the algorithm by which the first SAM device 41 performs mutual authentication and generates the first session key is the same as the algorithm by which the second SAM device 42 performs mutual authentication and generates the second session key. . Also, an algorithm in which the first SAM device 41 (first user device 11) encrypts (decrypts) a command using the first session key and a second SAM device 42 (second user device 12) uses the second session key The algorithm for encrypting (decrypting) the command is the same. Also, an algorithm in which the first user device 11 (first SAM device 41) decrypts (encrypts) the response using the first session key, and a second SAM device 42 (second user device 12) uses the second session key The algorithm for decrypting (encrypting) the response is the same. The difference in the algorithm corresponds to the difference in the type of the SAM device. That is, if the algorithm is different, the type of the SAM device is different. For example, since algorithms are different between FeliCa (registered trademark) and Mifare (registered trademark), SAM devices based on both standards have different types. Whether or not the same algorithm is used can be determined based on whether or not the data processing procedure and the data processing protocol are the same.

The @command is information for identifying a command to be executed by the first user device 11 or the second user device 12, or a command itself to be executed. The instruction may include an instruction for reading (reading) the first data and the second data, and an instruction for writing (writing) the first data. For example, when the first data or the second data is the balance of electronic money or the personal information of the user, the command for instructing the reading (reading) of the first data or the second data performs the balance inquiry and the identity inquiry of the electronic money. Can be used in some cases. The command for writing the first data or the second data is used to increase or decrease the balance of electronic money, or to update personal information such as an address.

The response is information corresponding to a command execution result by the first user device 11 or the second user device 12, and includes a read result and a write result of the first data and the second data. For example, when the command instructs the reading (reading) of the first data and the second data, the first data and the second data stored in the first user device 11 and the second user device 12 respond to the command. Can be included. Further, for example, when the command instructs writing (writing) of the first data or the second data, the success or failure of writing (whether successful or failed) may be included in the response. The response includes, in addition to information corresponding to the execution result of the command, mutual authentication performed between the first SAM device 41 and the first user device 11 and between the second SAM device 42 and the second user device 12. May be included.

In this embodiment, in order to facilitate understanding, the system 1 has one first SAM device 41 and one second SAM device 42, but the number of the first SAM device 41 and the second SAM device 42 is two. There may be three, or four or more. Also, in addition to the first SAM device 41 and the second SAM device 42, there are a plurality of SAM devices such as a third SAM device and a fourth SAM device that store key information different from those of the first SAM device 41 and the second SAM device 42. Is also good.

[Operation Example of System 1 According to First Embodiment]
Next, an operation example of the system 1 according to the first embodiment will be described with reference to FIGS. 2A and 2B. 2A and 2B are sequence diagrams illustrating an operation example of the system 1 according to the first embodiment. Hereinafter, as an example, the client device 20 is a POS terminal installed in a supermarket, the first user device 11 is a smartphone of a first shopper, and the second user device 12 is a second POS terminal different from the first shopper. A first shopper who is a shopper's smartphone and makes a payment of 1,000 yen with first electronic money (for example, Suica (registered trademark)) at a POS terminal, which is an example of the client device 20, The description will be made on the assumption that the shopper makes a payment of 3,000 yen with the second electronic money (for example, Edy (registered trademark)) at the POS terminal which is an example of the client device 20.

First, a case where the communication partner of the client device 20 is the first user device 11 will be described.

(Step 1)
First, the client device 20 requests the server device 30 to transmit a command to be executed by the first user device 11. For example, a POS terminal as an example of the client device 20 reads information of 1,000 yen from a barcode of a product that the first shopper wants to purchase, and transmits a predetermined bit string to the server device 30. Requesting transmission of a command to reduce 1,000 yen. The request can include client device identification information for identifying the client device 20.

(Steps 2 and 3)
Next, the server device 30 selects one first SAM device 41 from the plurality of SAM devices. This selection is made, for example, by the server device 30 receiving the key information identification information from the first user device 11 via the client device 20 (Step 2), and storing the SAM device stored in association with the received key information identification information. The identification information is read from the SAM device management table shown in FIG. 3, the SAM device identified by the read SAM device identification information is selected, and the selected SAM device is mutually authenticated with the first user device 11. The notification can be made (Step 3). If the client device identification information is included in the request in Step 1 or the server device 30 has the client device identification information of the client device 20 by another method, the server device 30 The information can be stored in the SAM device management table shown in FIG. 3 in association with the SAM device identification information read in Step 3.

(Steps 4 and 5)
Next, mutual authentication using the first key information A is performed between the selected one first SAM device 41 and the first user device 11, and a first session key is generated (Step 4). The generated first session key is stored in both the first SAM device 41 and the first user device 11. After the completion of the mutual authentication, the first SAM device 41 notifies the server device 30 that the mutual authentication has been completed (Step 5).

(Step 6)
Next, the server device 30 requests the selected one of the first SAM devices 41 to encrypt a command to be transmitted to the client device 20. For example, by transmitting a predetermined bit string, a request for command encryption for reducing the amount of 1,000 yen is required.

(Step 7)
Next, the selected one first SAM device 41 generates the requested command and encrypts it. For example, the selected one first SAM device 41 generates a command for reducing the amount of 1,000 yen, and encrypts the command with the first session key generated in Step 4.

(Step 8)
Next, the server device 30 receives the encrypted command from the one selected first SAM device 41.

(Step 9)
Next, the server device 30 transmits the encrypted command to the first user device 11 via the client device 20.

(Step 10)
Next, the first user device 11 decrypts the command received from the server device 30 via the client device 20, executes the decrypted command, encrypts a response corresponding to the result, and transmits the encrypted response. The data is transmitted to the server device 30 via the client device 20. As a result, the server device 30 receives the encrypted response from the first user device 11, which is the communication partner of the client device 20. The first user device 11 or the client device 20 can include, for example, client device identification information for identifying the client device 20 in the packet including the response.

(Step 11)
Next, the server device 30 reselects the same first SAM device 41 as the previously selected one first SAM device 41, and the re-selected first SAM device 41 is encrypted and received from the client device 20. Request to decrypt the response. In this reselection, when the client device identification information is included in the packet including the received response, the SAM device identification information stored in association with the client device identification information is described in the SAM device management shown in FIG. This can be performed by reading from the table and selecting the SAM device identified by the read SAM device identification information. This request can be made, for example, by transmitting a predetermined bit string.

(Step 12)
Next, the one reselected first SAM device 41 decrypts the encrypted response.

(Step 13)
Next, the server device 30 receives the decrypted response from the reselected one of the first SAM devices 41 and processes it. This process includes, for example, a process of deleting the client device identification information stored in association with the SAM device identification information identifying one reselected first SAM device 41 from the SAM device management table of FIG. May be included.

(Step 14)
Next, the server device 30 notifies the client device 20 that the process of reducing the 1,000 yen has been completed.

Next, a case where the communication partner of the client device 20 is the second user device 12 will be described.

(Step 21)
First, the client device 20 requests the server device 30 to transmit a command to be executed by the second user device 12. For example, a POS terminal, which is an example of the client device 20, reads information of 3,000 yen from a barcode of a product that the second shopper wants to purchase, and transmits a predetermined bit string to the server device 30. Requesting transmission of a command to reduce 3,000 yen. The request can include client device identification information for identifying the client device 20.

(Steps 22 and 23)
Next, the server device 30 selects one second SAM device 42 from the plurality of SAM devices. This selection is made, for example, by the server device 30 receiving the key information identification information from the second user device 12 via the client device 20 (Step 22), and storing the SAM device stored in association with the received key information identification information. The identification information is read from the SAM device management table shown in FIG. 3, the SAM device identified by the read SAM device identification information is selected, and the selected SAM device is mutually authenticated with the second user device 12. The notification can be made (Step 23). When the request in Step 21 includes the client device identification information, or when the server device 30 has the client device identification information of the client device 20 by another method, the server device 30 The information can be stored in the SAM device management table shown in FIG. 3 in association with the SAM device identification information read in Step 3.

(Steps 24 and 25)
Next, mutual authentication is performed between the selected one second SAM device 42 and the second user device 12 using the second key information B, and a second session key is generated (Step 24). The generated second session key is stored in both the selected one of the second SAM devices 42 and the second user device 12. After the completion of the mutual authentication, the second SAM device 42 notifies the server device 30 that the mutual authentication has been completed (Step 25).

(Step 26)
Next, the server device 30 requests the selected one of the second SAM devices 42 to encrypt a command to be transmitted to the client device 20. For example, by transmitting a predetermined bit string, a request is made to encrypt a command for reducing 3,000 yen.

(Step 27)
Next, the selected one second SAM device 42 generates the requested command and encrypts it. For example, the selected one second SAM device 42 generates a command for reducing 3,000 yen, and encrypts the command with the second session key generated in Step 24.

(Step28)
Next, the server device 30 receives the encrypted command from the selected one second SAM device 42.

(Step 29)
Next, the server device 30 transmits the encrypted command to the second user device 12 via the client device 20.

(Step 30)
Next, the second user device 12 decrypts the command received from the server device 30 via the client device 20, executes the decrypted command, encrypts a response according to the result, and transmits the encrypted response. The data is transmitted to the server device 30 via the client device 20. Thereby, the server device 30 receives the encrypted response from the second user device 12 that is the communication partner of the client device 20. The second user device 12 or the client device 20 can include, for example, client device identification information for identifying the client device 20 in the packet including the response.

(Step 31)
Next, the server device 30 reselects the same second SAM device 42 as the one second SAM device 42 previously selected, and the re-selected second SAM device 42 receives the encrypted SAM received from the client device 20. Request to decrypt the response. In this reselection, when the client device identification information is included in the packet including the received response, the SAM device identification information stored in association with the client device identification information is described in the SAM device management shown in FIG. This can be performed by reading from the table and selecting the SAM device identified by the read SAM device identification information. This request can be made, for example, by transmitting a predetermined bit string.

(Step32)
Next, the reselected second SAM device 42 decrypts the encrypted response.

(Step33)
Next, the server device 30 receives the decrypted response from the reselected second SAM device 42 and processes it. This process includes, for example, a process of deleting the client device identification information stored in association with the SAM device identification information for identifying one reselected second SAM device 42 from the SAM device management table of FIG. May be included.

(Step 34)
Next, the server device 30 notifies the client device 20 that the process of reducing the 3,000 yen has been completed.

According to the system 1 and the server device 30 according to the first embodiment described above, the SAM device is assigned to each service provider (that is, key information of a plurality of service providers is not mixed in one SAM device). In addition, it is possible to read and write data in a plurality of user devices that make contracts with different service providers. Therefore, it is possible to provide a server device and a system that can easily manage key information and can suppress a decrease in security due to a mixture of key information of a plurality of service providers in one SAM device.

[SAM device management table]
FIG. 3 is a diagram showing an example of the SAM device management table. As shown in FIG. 3, the SAM device management table can store SAM device identification information, key information identification information, and client device identification information in association with each other. The SAM device identification information and the key information identification information are stored in association with each other in advance, and when the SAM device identified by the SAM device identification information is selected, the client device identification information is associated with the SAM device identification information. It is memorized. When the processing by the SAM device identified by the SAM device identification information ends, the client device identification information stored in association with the SAM device identification information is deleted. The SAM device management table can be stored in a storage device of the server device 30, for example.

[System according to Embodiment 2]
Next, a system according to the second embodiment will be described. The configuration of the system according to the second embodiment is the same as that of the system 1 according to the first embodiment, and a description thereof will not be repeated.

[Operation Example of System According to Second Embodiment]
Next, an operation example of the system according to the second embodiment will be described. An operation example of the system according to the second embodiment is different from the operation example of the system 1 according to the first embodiment in a method of selecting one SAM device from a plurality of SAM devices by the server device 30. Specifically, the operation differs from the operation example of the system 1 according to the first embodiment in Steps 2, 3, 4, 22, 23, and 24. Hereinafter, an operation example of the system according to the second embodiment will be described with reference to FIG. FIG. 4 is a sequence diagram partially illustrating an operation example of the system according to the second embodiment.

In the operation example of the system 1 according to the first embodiment, for example, when the first user device 11 is a communication partner of the client device 20, the server device 30 transmits the key information identification information from the first user device 11 via the client device 20. The received SAM device identification information is read from the SAM device management table shown in FIG. 3 and stored in association with the received key information identification information, and the SAM identified by the read SAM device identification information is received (Step 2). By selecting the device and notifying the selected SAM device to perform mutual authentication with the first user device 11 (Step 3), the server device 30 allows the server device 30 to select one first SAM from among the plurality of SAM devices. The device 41 was selected. However, in the operation example according to the system according to the second embodiment, the server device 30 requests mutual authentication for one SAM device included in a plurality of SAM devices at random or in accordance with a predetermined rule. A successful SAM device is selected from a plurality of SAM devices as one SAM device. For example, the server device 30 first requests the second SAM device 42 for mutual authentication with the first user device 11 (Step 41). As a result, the second SAM device 42 attempts mutual authentication with the first user device 11, but the mutual authentication fails because no common key information is stored (Step 42). Then, the server device 30 requests the first SAM device 41 to perform mutual authentication with the first user device 11 (Step 43). As a result, the first SAM device 41 attempts mutual authentication with the first user device 11, but since the common key information is stored, the mutual authentication succeeds (Step 44). The server device 30 selects the SAM device for which the mutual authentication has succeeded as one SAM device. The case where the communication partner of the client device 20 is the second user device 12 can be similarly considered.

Note that each of the above-mentioned requests and data may be composed of one data, or may be composed of a plurality of data. Further, transmission of each request and each data described above may be transmitted by one transmission, or may be transmitted by dividing into a plurality of transmissions. Similarly, the reception of each request or each data described above may be received in one reception, or may be received in a plurality of receptions. In addition, “a certain request X or certain data Y includes certain data Z” includes not only a case where the request X or the data Y includes the data Z itself but also a case where the data Z which can specify the certain data Z is included. It is assumed that the case includes data other than the data itself.

In the above embodiment, the server device 30 requests the first SAM device 41 and the second SAM device 42 to create a command and encrypt the command. However, the server device 30 may create the command. That is, the server device 30 creates a command, transmits the created command to the first SAM device 41 and the second SAM device 42, and the first SAM device 41 and the second SAM device 42 encrypt the command received from the server device 30. May be sent back to the server device 30.

Although the embodiments have been described above, the descriptions described in the claims do not limit the configurations described in the claims.

1 System 11 First User Device 12 Second User Device 20 Client Device 30 Server Device 41 First SAM Device 42 Second SAM Device NW Network

Claims

At least one first user device for storing first key information;
At least one second user device for storing second key information;
A client device capable of performing short-range wireless communication with any of the first user device and the second user device;
A server device connected to the client device via a network,
A plurality of SAM devices connected to the server device and including at least one first SAM device storing the first key information and at least one second SAM device storing the second key information;
The server device in a system comprising:
When the communication partner of the client device is the first user device,
Selecting one of the first SAM devices from the plurality of SAM devices;
Requesting the selected one of the first SAM devices to encrypt a command,
Receiving the encrypted command from the selected one of the first SAM devices and transmitting the encrypted command to the first user device via the client device;
Receiving an encrypted response from the first user device via the client device;
Reselecting the same one of the first SAM devices as the selected one of the first SAM devices, and requesting the reselected one of the first SAM devices to decrypt the received encrypted response;
Receiving the decrypted response from the reselected one of the first SAM devices and processing it;
When the communication partner of the client device is the second user device,
Selecting one of the second SAM devices from the plurality of SAM devices;
Requesting the selected one of the second SAM devices to encrypt a command,
Receiving the encrypted command from the selected one of the second SAM devices and transmitting the encrypted command to the second user device via the client device;
Receiving an encrypted response from the second user device via the client device;
Reselecting the same one second SAM device as the selected one second SAM device, requesting the reselected one second SAM device to decrypt the received encrypted response,
A server device that receives the decoded response from the reselected one of the second SAM devices and processes the response.
The server device according to claim 1, wherein
The first user device comprises:
Storing the first data,
When receiving a command encrypted by the first SAM device from the server device via the client device, decrypts the received command, executes the decrypted command, and encrypts a response according to the result. Transmitted to the server device via the client device,
The second user device includes:
Storing the second data,
When a command encrypted by the second SAM device is received from the server device via the client device, the received command is decrypted, the decrypted command is executed, and a response corresponding to the result is encrypted. Server device for transmitting to the server device via the client device.
The server device according to claim 1 or 2,
The client device,
When requesting the server device to transmit the command, transmitting client device identification information and key information identification information to the server device,
The server device,
A storage device that stores a plurality of SAM identification information for identifying each of the plurality of SAM devices and key information identification information of key information stored in each of the plurality of SAM devices in association with each other;
When the transmission of the command is requested from the client device, from among the plurality of SAM identification information stored in the storage device, no client device identification information is stored in association with the SAM identification information, and the Selecting the SAM identification information in which the received key information identification information is stored in association with the received SAM identification information, and encrypting the command requested to be transmitted to one SAM device identified by the selected SAM identification information; Request,
A server device that stores the received client device identification information in the storage device in association with the selected SAM identification information.
The server device according to claim 3, wherein
The client device,
When transmitting the encrypted response to the server device, transmitting client device identification information and key information identification information to the server device,
The server device,
When the encrypted response is received from the client device, the SAM identification information stored in association with the received client device identification information from among the plurality of SAM identification information stored in the storage device. And a server device that requests one SAM device identified by the selected SAM identification information to decode the received response.
The server device according to claim 1, the plurality of SAM devices connected to the server device, and the client device connected to the server device via a network. system.