JP6233944B1 - Server and system - Google Patents

Abstract

A single server supports a plurality of user devices of different user device types. A plurality of SAMs connected to a reader / writer device via a network, wherein a SAM type of one SAM is different from at least one SAM type of the other SAM, and receives a packet from the reader / writer device; A server that reads response information from the received packet and processes the read response information with one SAM selected from the plurality of SAMs. [Selection] Figure 1

Description

  The present invention relates to a SAM (Secure Application Module).

  A thin client type system in which a plurality of SAMs are installed on the server side has been proposed (see Patent Documents 1, 2, and 3). The plurality of SAMs are the same type of SAM.

Japanese Patent No. 4516394 JP 2003-141064 A JP 2007-124072 A

  However, in the above-described conventional system, only the same type of SAM is arranged on the server side, so that it cannot cope with user devices processed by other types of SAM.

  The above problem can be solved by, for example, the following means.

  A SAM type of one SAM is connected to the reader / writer device via a network, and includes a plurality of SAMs different from the SAM type of at least one other SAM, receives a packet from the reader / writer device, and receives the received packet A server which reads response information from the plurality of SAMs and processes the read response information with one SAM selected from the plurality of SAMs.

  One server can support a plurality of user devices of different user device types.

1 is a schematic diagram showing a system 1 according to a first embodiment. 4 is a schematic diagram illustrating a configuration example of a packet transmitted from the server 30 to the reader / writer devices 22 and 24. FIG. 4 is a schematic diagram illustrating a configuration example of a packet transmitted from the reader / writer device 22 or 24 to the server 30. FIG. It is a schematic diagram explaining a 1st table. It is a schematic diagram explaining a 2nd table. 4 is a flowchart illustrating an operation example of a server 30. It is a schematic diagram explaining the other example of a 1st table. It is a schematic diagram explaining the other example of a 2nd table. 10 is a flowchart for explaining another example of the operation of the server 30. It is a schematic diagram explaining the other example of a 1st table.

[System 1 according to Embodiment 1]
FIG. 1 is a schematic diagram showing a system 1 according to the first embodiment. As shown in FIG. 1, the system 1 according to the first embodiment includes a server 30, reader / writer devices 22 and 24, and user devices 12 and 14. The server 30 is connected to the reader / writer devices 22 and 24 via the network 50, and includes a plurality of SAMs 42, 44, and 46 in which the SAM type of one SAM is different from the SAM type of one other SAM. Packets are received from the devices 22 and 24, response information is read from the received packets, and the response information read by one SAM selected from the plurality of SAMs 42, 44, and 46 is processed. Details will be described below.

(Reader / writer devices 22, 24, user devices 12, 14)
As the user devices 12 and 14, for example, IC cards (Contactless smart cards), smartphones with built-in IC card functions, and the like can be used. The reader / writer devices 22 and 24 are devices for reading and writing data in the user devices 12 and 14, and are composed of, for example, a supermarket cash register device or a station ticket gate. In the communication between the user devices 12 and 14 and the reader / writer devices 22 and 24, for example, the user devices 12 and 14 and the reader / writer devices 22 and 24 are not in contact with each other as in a near field communication system (Near Field Communication). The communication is performed according to a method in which the user devices 12 and 14 and the reader / writer devices 22 and 24 are in contact with each other, such as a method for performing communication with ISO, and ISO 7816. The user devices 12 and 14 include, for example, an IC chip and a storage device, and data such as an electronic money balance is stored in the storage device.

  The reader / writer devices 22 and 24 transmit and receive packets to and from the server 30. When the reader / writer devices 22 and 24 receive a packet from the server 30, the reader / writer devices 22 and 24 read the command information from the received packet, and output the read command information to the user devices 12 and 14. The user devices 12 and 14 execute various processes (for example, increase or decrease of the electronic money balance) according to the command information input from the reader / writer devices 22 and 24, and output response information to the reader / writer devices 22 and 24. Response information is information indicating the content of a response to command information. Information indicating that the process according to the command information has been completed normally or abnormally, information in the user devices 12 and 14 such as a balance of electronic money, or calculation result data during mutual authentication are examples of response information. . The reader / writer devices 22 and 24 transmit a packet including response information output from the user devices 12 and 14 to the server 30.

  FIG. 2 is a schematic diagram illustrating a configuration example of a packet transmitted from the server 30 to the reader / writer devices 22 and 24. As shown in FIG. 2, the packet transmitted from the server 30 to the reader / writer devices 22 and 24 includes a session ID and command information. The session ID is a number for identifying a session. For example, a client ID that identifies a reader / writer device, a user device ID that identifies a user device, and the like are examples of session IDs. The command information includes, for example, “increase the balance of electronic money by 100 yen” and “decrease the balance of electronic money by 100 yen”.

  FIG. 3 is a schematic diagram illustrating a configuration example of a packet transmitted from the reader / writer devices 22 and 24 to the server 30. As shown in FIG. 3, a packet transmitted from the reader / writer devices 22 and 24 to the server 30 includes a session ID, a user device type identifier, and response information.

  The number of user devices 12 and 14 and reader / writer devices 22 and 24 is not particularly limited. In this embodiment, two user devices 12 and 14 and two reader / writer devices 22 and 24 are arranged in the system 1. It shall be.

(Server 30)
The server 30 is connected to the reader / writer devices 22 and 24 via the network 50. The network 50 is, for example, the Internet.

  The server 30 includes an arithmetic device and a storage device. The arithmetic device is composed of, for example, a CPU, and the storage device is composed of, for example, RAM or a hard disk. Programs and data are stored in the storage device. The data includes a first table and a second table described later. The server 30 operates when the arithmetic device reads and executes the program from the storage device.

  FIG. 4 is a schematic diagram illustrating the first table. As shown in FIG. 4, the first table stores a user device type identifier and a SAM type identifier in association with each other. The user device type identifier is an identifier for identifying the user device type. The same user device type identifier is assigned to user devices having the same user device type, and different user device type identifiers are assigned to user devices having different user device types. Whether or not the user device types are the same can be determined by whether or not the algorithms for processing the data are the same. That is, user devices that process data with the same algorithm can be determined to have the same user device type, and user devices that process data with a different algorithm can be determined to have different user device types. Whether or not the algorithm is the same can be determined by whether or not the data processing procedure and the data processing protocol are the same.

  The SAM type identifier is an identifier for identifying the SAM type. The same SAM type identifier is assigned to SAMs having the same SAM type, and different SAM type identifiers are assigned to SAMs having different SAM types. Whether the SAM type is the same can be determined by whether the algorithm for processing the data is the same. That is, SAMs that process data using the same algorithm can be determined to have the same SAM type, and SAMs that process data using a different algorithm can be determined to have different SAM types. Whether or not the algorithm is the same can be determined by whether or not the data processing procedure and the data processing protocol are the same.

  The number of algorithms mounted on one user device or one SAM is not particularly limited. When a plurality of different algorithms are mounted on one user device or one SAM, the user device type or the SAM type can be determined depending on whether the combination of the mounted algorithms is the same. That is, the same user device type identifier and the same SAM type identifier can be assigned to user devices and SAMs with the same combination of installed algorithms, assuming that the user device type and the SAM type are the same. On the other hand, different user device type identifiers and different SAM type identifiers can be assigned to user devices and SAMs with different combinations of installed algorithms, assuming that the user device type and SAM type are different. When a plurality of different algorithms are mounted on one SAM or when a plurality of different algorithms are mounted on one user apparatus, as shown in FIG. 10, in the first table, for one SAM type identifier. A plurality of user device type identifiers may be stored in association with each other, or a plurality of SAM type identifiers may be stored in association with one user device type identifier.

  FIG. 5 is a schematic diagram illustrating the second table. As shown in FIG. 5, the SAMID, the SAM type identifier, and the session ID are stored in the second table in association with each other. The SAMID is a number that uniquely identifies the SAM. The SAMID makes it possible to select one SAM from a plurality of SAMs.

  The server 30 includes a plurality of SAMs 42, 44 and 46. Here, the SAM type of one SAM is different from the SAM type of at least one other SAM. One SAM is one SAM arbitrarily selected from a plurality of SAMs 42, 44, 46. When any one SAM is selected from among the plurality of SAMs 42, 44, 46, the SAM type of the one SAM is different from the SAM type of at least one other SAM included in the plurality of SAMs 42, 44, 46. . That is, the SAM 42 has a SAM type different from at least one of the SAMs 44 and 46, the SAM 44 has a SAM type different from at least one of the SAMs 42 and 46, and the SAM 46 has a SAM type different from at least one of the SAMs 42 and 44.

  The form in which the server 30 includes a plurality of SAMs 42, 44, 46 is not particularly limited. For example, the plurality of SAMs 42, 44, 46 may be built in the server 30 by being inserted into a slot included in the server 30, or may be connected to the server 30 using a USB cable, a LAN cable, or the like.

  FIG. 6 is a flowchart for explaining an operation example of the server 30. Hereinafter, an operation example of the server 30 will be described with reference to FIG.

(Step S1)
The server 30 transmits a packet including the session ID and command information to the reader / writer devices 22 and 24, and proceeds to step S2.

(Step S2)
The server 30 determines whether or not a packet has been received from the reader / writer devices 22 and 24, and if received, proceeds to step S3.

(Step S3)
The server 30 reads the session ID, user device type identifier, and response information from the packet received in step S2, and proceeds to step S4.

(Step S4)
The server 30 determines whether or not the session ID read in step S3 is stored in the second table. If it is stored, the process proceeds to step S5, and if not stored, the process proceeds to step S8.

(Step S5)
The server 30 reads the SAMID associated with the session ID read in step S3 from the second table, selects the SAM of the read SAMID from the plurality of SAMs 42, 44, and 46, and uses the selected SAM. The response information read in step S3 is processed, and the process proceeds to step S6.

(Step S6)
The server 30 determines whether or not the session has been completed by processing the response information in step S5. If completed, the server 30 proceeds to step S7. If not completed, the server 30 returns to step S1 to obtain new command information. The included packet is transmitted to the reader / writer device.

(Step S7)
The server 30 deletes the session ID stored in association with the SAMID of the SAM selected in step S5 from the second table.

(Step S8)
The server 30 reads from the first table the SAM type identifier associated with the user device type identifier read in step S3 in the first table, and proceeds to step S9.

(Step S9)
The server 30 reads the SAMID associated with the SAM type identifier read in step S8 from the second table, selects the SAM of the read SAMID, and proceeds to step S10.

(Step S10)
The server 30 processes the response information read in step S3 with the SAM selected in step S9, and proceeds to step S11.

(Step S11)
The server 30 stores the session ID read in step S3 in association with the SAMID of the SAM selected in step S9 in the second table, and proceeds to step S6.

  According to the system 1 according to the first embodiment described above, a single server 30 can support a plurality of user devices of different user device types. For example, even if the user device types of the user device 12 and the user device 14 are different, a single server 30 can realize settlement processing for these user devices. Further, according to the system 1 according to the first embodiment, a single reader / writer device can support a plurality of user devices of different user device types. For example, a single reader / writer device 22 can realize settlement processing of a plurality of user devices with different user device types. Moreover, according to the system 1 according to the first embodiment, an existing SAM loaded with one algorithm and another algorithm are loaded without developing a new SAM loaded with one algorithm and another algorithm. In addition, it is possible to construct a thin client type system that can handle a plurality of different user device types by utilizing an existing SAM. Therefore, the cost and time required for the introduction of the thin client system can be reduced.

[System according to Embodiment 2]
FIG. 7 is a schematic diagram for explaining another example of the first table. FIG. 8 is a schematic diagram for explaining another example of the second table. FIG. 9 is a flowchart for explaining another operation example of the server 30. As shown in FIGS. 7 to 9, the system according to the second embodiment is different from the system 1 according to the first embodiment in the following points. Other points have the same configuration as the system 1 according to the first embodiment.

  First, the system according to the second embodiment associates a first table that stores user device type identifiers, SAM type identifiers, and session number upper limit values in association with each other, and associates SAMIDs, SAM type identifiers, session IDs, and session numbers. This is different from the system 1 according to the first embodiment in that the second table to be stored is stored.

  In addition, when the read session ID is not stored in the second table, the system according to the second embodiment displays the SAM type identifier and the session number upper limit value associated with the read user device type identifier. SAMID read from one table, the SAMID associated with the read SAM type identifier and the number of sessions less than the read session number upper limit value is read from the second table, and the SAM of the read SAMID is selected as one SAM. In the first embodiment, the session ID read in association with the SAMID of the one SAM is stored in the second table, and the number of sessions stored in the second table is incremented in association with the SAMID of the selected SAM. It differs from the system 1 which concerns. Incrementing means incrementing the number by one.

  In addition, the system according to the second embodiment decrements the number of sessions stored in the second table in association with the SAMID of the selected one SAM when the process with the selected one SAM is completed. This is different from the system 1 according to the first embodiment. Decrement means reducing the number by one.

  Also by the system according to the second embodiment, the same effect as that of the system 1 according to the first embodiment can be obtained. Further, according to the system according to the second embodiment, it is possible to prevent the individual SAMs 42, 44, and 46 from being overloaded.

  Although the embodiments have been described above, the configurations described in the scope of the claims are not limited by these descriptions.

1 System 12, 14 User device 22, 24 Reader / writer device 30 Server 42, 44, 46 SAM
50 network

Claims (5)

Connected to the reader / writer device via the network,
A SAM type of one SAM includes at least a plurality of SAMs different from the SAM type of one other SAM;
Receiving a packet from the reader / writer device;
Read response information from the received packet,
A server that processes the read response information with one SAM selected from the plurality of SAMs;
A first table storing user device type identifiers and SAM type identifiers in association with each other;
There are a column for storing SAMID, a column for storing SAM type identifier, and a column for storing session ID. At least a column for storing SAMID and a column for storing SAM type identifier include SAMID and SAM type identifier. A second table stored in advance,
Read the session ID and user device type identifier from the received packet,
If the read session ID is stored in any row in the second table, the SAMID is calculated from the column storing the SAMID in the row in which the read session ID is stored in the second table. Read, select the SAM of the read SAMID as the one SAM,
If the read session ID is not stored in any row in the second table, the SAM type identifier associated with the read user device type identifier is read from the first table, The SAMID is read from the column storing the SAMID in the row in which the read SAM type identifier in the two tables is stored and the session ID is not stored, and the SAM of the read SAMID is selected as the one SAM. the Lusa over bus stores the read session ID column one SAMID of SAM that the selection in the second table stores the session ID of the row containing. When a session is completed by the process in the selected one SAM, the session ID is deleted from the column storing the session ID in the row in which the SAMID of the selected one SAM is stored in the second table. The server according to claim 1 . Connected to the reader / writer device via the network,
A SAM type of one SAM includes at least a plurality of SAMs different from the SAM type of one other SAM;
Receiving a packet from the reader / writer device;
Read response information from the received packet,
A server that processes the read response information with one SAM selected from the plurality of SAMs;
A first table that stores user device type identifiers, SAM type identifiers, and session number upper limit values in association with each other;
A column storing a SAMID, a column storing a SAM type identifier, a column storing a session ID, and a column storing a number of sessions, and at least a column storing the SAMID, a column storing the SAM type identifier, A second table in which a SAMID, a SAM type identifier, and a session number are respectively stored in advance in a column for storing the number of sessions;
Read the session ID and user device type identifier from the received packet,
If the read session ID is stored in any row in the second table, the SAMID is calculated from the column storing the SAMID in the row in which the read session ID is stored in the second table. Read, select the SAM of the read SAMID as the one SAM,
If the read session ID is not stored in any row in the second table, the SAM type identifier and the session number upper limit value associated with the read user device type identifier are set to the first table. Read from the table, read the SAMID from the column storing the SAMID of the row in which the read SAM type identifier in the second table is stored and the number of sessions less than the read session number upper limit is stored The SAM of the read SAMID is selected as the one SAM, and the read session ID is stored in the column storing the session ID of the row in which the SAMID of the selected one SAM is stored in the second table. Store and select the selected one in the second table AM incremented to salicylate over server the number of sessions stored in the column SAMID stores the number of sessions of the row containing the. When a session is completed by the process in the selected one SAM, the session ID is deleted from the column storing the session ID in the row in which the SAMID of the selected one SAM is stored in the second table. The server according to claim 3 , wherein the number of sessions stored in a column storing the number of sessions in the row in which the SAMID of the selected one SAM in the second table is stored is decremented. A system comprising: the server according to claim 1; and a plurality of the reader / writer devices.

Images