Input / Output Management System

Abstract

To provide an in / out management system that is constructed with simple constitution although media having high security standards, for example, credit cards etc., are utilized for in / out management of facilities.SOLUTION: An in / out management system 100 comprises a token conversion server 10 which converts a security ID into a token, a reader RD which reads and reports the security ID to the token conversion server 10 and also receives notice of a corresponding token, and an information management server 50 which manages in / out information associatively with the token reported by the reader RD.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to an entrance and exit management system that performs entrance and exit management in various facilities using a payment medium such as a credit card.

Background Art

[0002] As a technology related to card information processing, when using a card for purchasing goods or services, it is possible to suppress an increase in cost and strengthen the security of card information by performing information processing while determining the presence or absence of the confidentiality of card information (see Patent Document 1).

[0003] However, in Patent Document 1 above, although a method for strengthening the security of card information when using a card is disclosed, there is no disclosure regarding the mode of using a card for service provision other than purchasing using card information.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

[0005] The present invention has been made in view of the above points, and an object thereof is to provide an entrance and exit management system that is constructed with a simple configuration while using a medium with high security standards such as a credit card when managing entrance and exit in a facility.

[0006] The entrance and exit management system for achieving the above object includes a token conversion server that tokenizes a security ID, a reader that reads the security ID, notifies the token conversion server, and receives a notification of a corresponding token, and an information management server that manages entrance and exit information in association with the token notified by the reader.

[0007] In the above input / output management system, the reader receives a notification of a token corresponding to the security ID, and by associating with the token received by the reader and performing various management, when performing information management regarding entry and exit in various facilities such as a parking lot, even when using a medium with a high security standard such as a credit card, it is not necessary to align the entire system with a high security standard. Therefore, a system with a high security standard can be constructed with a simple configuration.

[0008] In a specific aspect of the present invention, the reader is provided in a parking lot or a bicycle parking lot, and the information management server manages the entry and exit information of vehicles using the parking lot or the bicycle parking lot based on the token received by the reader. In this case, in the entry / exit management in the parking lot or the bicycle parking lot, a token corresponding to the security ID can be used.

[0009] In another aspect of the present invention, it includes a settlement machine that is communicably connected to the information management server and performs settlement of fees based on the entry and exit information of the vehicle. In this case, in the settlement machine, management of the vehicle associated with the token (especially settlement management) can be performed.

[0010] In still another aspect of the present invention, as the settlement machine, it includes a pre-settlement machine that accepts pre-settlement processing of fees. In this case, pre-settlement using the token becomes possible in the pre-settlement machine.

[0011] In still another aspect of the present invention, as the reader, it further includes a facility-side reader installed in a facility other than a parking lot or a bicycle parking lot. The facility-side reader reads the security ID when using the facility and receives a notification of the corresponding token from the token conversion server. The information management server performs an application process of a parking lot or bicycle parking lot fee discount based on the token received by the facility-side reader. In this case, application of a fee discount using the token becomes possible.

[0012] In yet another aspect of the present invention, the reader has a storage unit that stores the notification history of the token together with the corresponding security ID, and when communication between the reader and the token conversion server becomes impossible, the information management server manages the entry and exit information based on the history stored in the storage unit. In this case, even when communication with the token conversion server becomes impossible, entry and exit management using the token can be maintained.

[0013] In yet another aspect of the present invention, the reader is composed of an entrance-side reader installed at the entrance and an exit-side reader installed at the exit, and the entrance-side reader transmits the token notified upon entry to the exit-side reader. In this case, entry and exit management using the token is performed through the cooperation between the entrance-side reader and the exit-side reader.

[0014] In yet another aspect of the present invention, there is an entrance determination unit that receives a token notification from the entrance-side reader, is communicably connected to the information management server, and determines whether entry is permitted, and an exit determination unit that receives a token notification from the exit-side reader, is communicably connected to the information management server, and determines whether exit is permitted. When communication with the information management server becomes impossible, the exit determination unit determines whether exit is permitted based on the token notification from the entrance-side reader. In this case, even when communication with the information management server becomes impossible, it is possible to determine whether exit is permitted using the token.

[0015] In yet another aspect of the present invention, the reader includes a ticket gate reader provided at the ticket gate of the station, and the information management server manages the entry and exit information of the passengers at the ticket gate based on the token notified by the ticket gate reader. In this case, the token can be used for the entry and exit management of the passengers at the station ticket gate.

[0016] In yet another aspect of the present invention, the information management server sets the expiration date and the blacklist target for the token notified by the reader. In this case, various management operations associated with the entry and exit management can be performed together using the token.

Brief Description of the Drawings

[0017]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Mode for Carrying Out the Invention

[0018] 〔First Embodiment〕 Hereinafter, with reference to FIG. 1 and the like, an example of the entry / exit management system according to the first embodiment will be described. As shown in FIG. 1 and the like, the entry / exit management system 100 according to the present embodiment is provided in the parking lot PA and performs entry / exit management for vehicles VE (see FIG. 3) entering and leaving the parking lot PA. That is, the entry / exit management system 100 functions as a parking management system.

[0019] In the entry / exit management system 100 of the present embodiment, entry / exit management using a security ID is possible. As a more specific example, for example, as shown in FIG. 1, entry / exit management in the parking lot PA is performed using a credit card CC, which is a payment medium. In the following example, in addition to the case of using a credit card CC, a mode of issuing a conventional parking ticket for parking management is also shown to coexist, but it is also possible to adopt a mode that requires the use of a credit card CC for entry / exit management. In addition, it is also conceivable to use various other media (such as IC cards) in combination with the credit card CC.

[0020] Here, the credit card CC, which is an example of the payment medium, is described as being EMV (Europay, MasterCard, VISA protocol) compliant and capable of non-contact reading.

[0021] To enable the above-described mode, the entry / exit management system 100 includes a token conversion server 10, an entrance reception device 20, an exit reception device 30, and an information management server 50. In the drawing, the arrows A1 and A2 indicate the directions of entry and exit of the vehicle, respectively.

[0022] The token conversion server 10 is a facility for tokenizing the security ID of the credit card CC. The token conversion server 10 is composed of a server that has obtained a PCIDSS (Payment Card Industry Data Security Standard) certification or a server capable of generating a corresponding token in order to ensure the security of the card information of the credit card CC as a payment medium. The token conversion server 10 performs tokenization (generation of a token) on the security ID of the credit card CC, that is, the credit card number (PAN: Primary Account Number), which is the payment medium in the above-described manner, between a specific external device (such as the entrance-side reader RDa described later), and notifies the generated token.

[0023] The entrance reception device 20 includes, for example, a ticket vending machine 21 and a gate device 22, and performs operations related to permitting or denying entry of a vehicle into the parking lot PA. The ticket vending machine 21 is a parking ticket issuing machine that issues a parking ticket from the discharge port 21a. The gate device 22 is a device that raises and lowers the gate bar 22a to indicate whether entry of a vehicle is permitted. In addition to the above, in the present embodiment, in particular, the entrance reception device 20 includes an entrance determination unit 20a as a main body part for determining whether entry is permitted, and an entrance-side reader RDa.

[0024] The entrance-side reader RDa is composed of an EMV authentication reading device in order to enable communication regarding the PAN with the token conversion server 10 as a server that has obtained a PCIDSS certification and the token corresponding thereto. That is, the entrance-side reader RDa reads the PAN as the security ID from the credit card CC and notifies the token conversion server 10, and receives notification of the token corresponding to the PAN from the token conversion server 10. In an example shown in the figure, in the entrance reception device 20, an interface unit 23a for performing non-contact reading of the credit card CC is provided. That is, the entrance-side reader RDa performs non-contact reading of the credit card CC via the interface unit 23a.

[0025] The entrance determination unit 20a is composed of various circuits etc., for example, and while receiving the token notified to the entrance-side reader RDa from the entrance-side reader RDa, it determines whether the vehicle of the holder (passenger) of the credit card CC can enter the parking lot PA. Further, the entrance determination unit 20a can communicate with the information management server 50, and outputs the information of the received token (token ID) and the information at the time of entry such as the entry time to the information management server 50. That is, the entrance determination unit 20a receives the notification of the token from the entrance-side reader RDa, is communicably connected to the information management server 50, and functions as the main body part of the entry reception device 20 by determining whether entry is permitted or not. Incidentally, when the entrance determination unit 20a determines that entry is permitted, it outputs a command to raise and lower the gate bar 22a to the gate device 22 in order to allow the corresponding vehicle to pass.

[0026] The exit reception device 30 has the same configuration as the above-described entry reception device 20, and performs operations related to whether the vehicle can exit the parking lot PA. For this reason, the exit reception device 30 includes, for example, a settlement device 31, a gate device 32, an exit determination unit 30a, and an exit-side reader RDb. The settlement device 31 inserts and discharges the parking ticket from the reception port 31a and performs various processes necessary for parking fee settlement such as inquiries to the information management server 50. The gate device 32 is a device that raises and lowers the gate bar 32a to indicate whether the vehicle can exit.

[0027] The exit-side reader RDb reads the security ID of the credit card CC via the interface unit 33a, notifies the token conversion server 10, and receives the notification of the corresponding token from the token conversion server 10. The exit determination unit 30a is composed of various circuits etc., for example, and while receiving the token notified to the exit-side reader RDb from the exit-side reader RDb, it functions as the main body part of the exit reception device 30 by determining whether the vehicle of the holder (passenger) of the credit card CC can exit the parking lot PA.

[0028] The information management server 50 is composed of various storage devices, electronic circuits, etc., stores various data related to parking management including the token ID, and performs necessary judgment processing. In the illustrated example, the information management server 50 includes a communication unit 51 and a parking data management unit 52, and for parking management, it transmits and receives various information to and from the entry reception device 20 and the exit reception device 30 via the communication unit 51. The parking data management unit 52 is provided with a token data management unit 52a that manages various data related to the token ID, and a parking ticket data management unit 52b that manages various data related to the parking ticket issued by the entry reception device 20. That is, the information management server 50 performs parking management based on the token ID and the information of the parking ticket. As described above, the information management server 50 can manage the entry / exit information associated with the token notified by the entrance-side reader RDa of the entry reception device 20 or the exit-side reader RDb of the exit reception device 30.

[0029] When extracting the operations such as acquisition and notification of tokens in the entry / exit management system 100, it becomes as shown in the block diagram exemplified as Figure 2. Explaining in order, first, when the security ID (PAN) of the credit card CC is read by the reader RD (entrance-side reader RDa or exit-side reader RDb), the reader RD notifies the token conversion server 10 of the read security ID. The token conversion server 10 that has received the notification from the reader RD tokenizes the security ID (tokenization) and notifies the generated token to the reader RD. The reader RD that has received the notification from the token conversion server 10 transmits the token to the information management server 50 that performs various information management. In the example shown in Figure 1, the token is output to the information management server 50 from the entrance-side reader RDa or the exit-side reader RDb as the reader RD via the entrance determination unit 20a or the exit determination unit 30a. Also, at this time, various information related to the token and parking management is associated and managed in the information management server 50. That is, in the information management server 50, data management using the token as an ID is performed.

[0030] When tokenizing the security ID as described above, from the perspective of maintaining high security, as described above, for example, the token conversion server 10 is composed of a server that has obtained a PCI DSS certification, etc., and the same security maintenance compliant with this is also applied to the reader RD (the entrance-side reader RDa and the exit-side reader RDb) that communicates with the token conversion server 10. That is, among the configurations shown in FIG. 2, the token conversion server 10 and the reader RD indicated by hatching comply with PCI DSS certification. On the other hand, for configurations other than these (for example, the information management server 50), they are not directly involved in tokenization and perform various information management, etc., solely based on the notified tokens. Therefore, for the information management server 50, etc., that is not hatched, it is possible to configure it to be non-compliant with PCI DSS certification, and it is possible to adopt a simpler configuration compared to the token conversion server 10, etc.

[0031] In this embodiment, in view of this point, by configuring the access control system 100, when performing information management regarding entry and exit in the parking lot PA (see FIG. 1), while using a medium with a high security standard such as a credit card, as a whole system, it is not necessary to meet a high security standard, thus realizing the construction of a system with a simple configuration. Note that the information management in the manner exemplified in FIG. 2 is applicable not only to parking lots but also to bicycle parking lots or various other facilities.

[0032] Hereinafter, with reference to the conceptual diagram shown as FIG. 3, an example will be described of the outline of vehicle VE entry / exit management using tokens in the parking lot PA where the entry / exit management system 100 is introduced. Also in FIG. 3, similar to the case shown in FIG. 2, among the respective parts constituting the entry / exit management system 100, for the configuration compliant with PCIDSS authentication, it is indicated by hatching, and for those non-compliant, it is shown without hatching. More specifically, in the illustration, the token conversion server 10, the entrance-side reader RDa, and the exit-side reader RDb indicated by hatching are regarded as the PCIDSS authentication compliant part 100A, and the entrance determination unit 20a, the exit determination unit 30a, and the information management server 50 shown without hatching are regarded as the PCIDSS authentication non-compliant part 100B. That is, the processing related to the tokenization of the security ID (PAN) of the credit card CC is exclusively performed within the PCIDSS authentication compliant part 100A, and in the PCIDSS authentication non-compliant part 100B, various management is performed using the already generated token as the ID.

[0033] Hereinafter, with reference to FIG. 3, an example will be described of a series of processes from the entry to the exit of the vehicle VE when the credit card CC is used for parking management.

[0034] First, when the security ID (PAN) of the credit card CC owned by the passenger of the vehicle VE attempting to enter the parking lot PA is read by the entrance-side reader RDa of the entrance reception device 20 (step S1), the entrance-side reader RDa requests the tokenization of the security ID from the token conversion server 10 (step S2). In the token conversion server 10, in response to the request from the entrance-side reader RDa, a token is generated. When the entrance-side reader RDa receives the response of the token corresponding to step S2 from the token conversion server 10 (step S3), it transfers the received token to the entrance determination unit 20a (step S4).

[0035] The entrance determination unit 20a associates the entry information of the vehicle VE corresponding to the credit card CC, that is, information such as the entry time, with the token received from the entrance-side reader RDa in step S4 and registers it in the information management server 50 (step S5). Note that the entrance determination unit 20a, together with the registration in step S5, also performs various necessary operations such as raising and lowering the gate bar 22a (see Fig. 1) to allow the vehicle VE for which the registration has been received to enter the venue.

[0036] On the other hand, for the vehicle VE attempting to exit the parking lot PA, first, when the security ID (PAN) of the credit card CC is read by the exit-side reader RDb of the exit reception device 30 (step S6), the exit-side reader RDb requests the token conversion server 10 to perform tokenization on the security ID (step S7). When receiving the response of the corresponding token from the token conversion server 10 (step S8), it transfers the received token to the exit determination unit 30a (step S9).

[0037] The exit determination unit 30a requests the information management server 50 for the information about the token received from the exit-side reader RDb in step S9 (here, it is regarded as the entry information) to calculate the parking fee for the target vehicle VE (step S10). When receiving the response of the corresponding entry information from the information management server 50 (step S11), it calculates the parking fee based on the received entry information (step S12).

[0038] Note that for steps after S12, the exit reception device 30 equipped with the settlement device 31 and the gate device 32 (see Fig. 1) performs various necessary processes such as settlement processing and exit processing.

[0039] In the above example, the entrance reception device 30 has been described as calculating the parking fee. However, for example, the information management server 50 may be responsible for calculating the parking fee, and the exit determination unit 30a may request the information on the calculation result of the parking fee instead of the above-described entrance information as the information about the token in step S10. In addition, when the entry / exit management system 100 is applied to the bicycle parking lot, the configuration is the same as described above. That is, in the above, the part where the vehicle (automobile) VE is described can be replaced with a bicycle, and each part such as the gate device can be configured according to the specifications of the bicycle parking lot, so that the same configuration becomes possible.

[0040] Hereinafter, with reference to FIG. 4, an example of the data handled by the information management server 50, that is, the data for the entry / exit management of the vehicle VE, will be described. Here, an example of the data stored in the token data management unit 52a of the parking data management unit 52, which is the data of the vehicle VE using the token, that is, the parking data, is shown. In the information management server 50, for example, as shown in FIGS. 4(A) and 4(B), each time a token is generated, a data table DT is created, and a series of data groups corresponding to a plurality of data tables DT as shown in FIG. 4(C) are stored in the token data management unit 52a and updated each time the vehicle VE enters or exits. For each data table DT, as shown in FIG. 4(A) etc., in addition to the number of the generated token (token ID), the issue date and time of the token, and the data DD1 regarding the expiration date of the token, the data DD2 regarding the contract details of the vehicle VE and the data DD3 regarding the time information such as the time of entry / exit are stored. In the illustrated example, in addition to these pieces of information, the data DD4 indicating whether or not it is a blacklist target is also stored. Normally, the data DD4 is not a blacklist target. However, for example, regarding the information of the token corresponding to the vehicle VE that has had problems such as not having a normal exit when using the past parking lot PA, it is registered as a blacklist target, and it can be detected in subsequent use of the parking lot PA.

[0041] Regarding the contract details shown in data DD2, various aspects can be considered. As illustrated in Fig. 4(A), for a vehicle VE that regularly uses the parking lot PA, information indicating the usage period is stored, and usage history is recorded in the time information shown as data DD3. On the other hand, as illustrated in Fig. 4(B), for a vehicle VE that is used temporarily, it is recorded that the usage is only valid for the current day. Regarding these data DD1 to DD4, recording and updating are performed based on the registration command from the entrance determination unit 20a at the time of entry (step S5 in Fig. 3) and the information request from the exit determination unit 30a at the time of exit (step S10 in Fig. 3).

[0042] Hereinafter, with reference to the flowchart of Fig. 5, an example of a series of operations in the entry / exit management system 100 of the above-described aspect will be described. First, with reference to Fig. 5(A), an example of the operation of the entry / exit management system 100 when a vehicle VE enters will be described.

[0043] Among the entry / exit management system 100, the entry reception device 20 detects the presence of a vehicle VE attempting to enter (step S101) by, for example, various sensors etc. (not shown). In step S101, when a vehicle VE is detected (step S101: Yes), it is confirmed whether the vehicle VE uses the security ID of the credit card CC for entry / exit management (step S102).

[0044] In step S102, when it is confirmed that the security ID is used, that is, when the security ID is read by the entrance side reader RDa (step S102: Yes), the entrance side reader RDa performs tokenization processing (tokenization request and its response) on the read security ID (step S103).

[0045] Here, a check for blacklist registration regarding the security ID is performed (step S104). Regarding the check for blacklist registration, as an example, when tokenization is performed in step S103, a case where the target credit card CC is unusable can be considered. That is, it is assumed that the credit card CC itself is on the blacklist and no token can be obtained during the processing in the token conversion server 10. Also, as another example, although tokenization is performed in step S103, when registering the ID information of the token in the information management server 50, it is assumed that the data (data DD4 in FIG. 4) managed in the information management server 50 is on the blacklist. That is, it is assumed that there were problems when using the past parking lot PA.

[0046] In step S104, if it is determined that there is no blacklist registration (step S104: No), a process of accepting the token is performed, that is, parking management registration for registering various data in the token data management unit 52a of the information management server 50 at the time of entry is performed (step S105). After passing through step S105, the entry reception device 20 permits the entry of the vehicle VE and performs various operations such as raising and lowering the gate bar 22a by the gate device 22 to guide it into the venue (step S106).

[0047] On the other hand, in step S104, if it is determined that there is blacklist registration (step S104: Yes), the entry reception device 20 issues a warning notice to that effect (step S107). Regarding the mode of the warning notice, various modes are assumed. For example, it is possible to notify the passenger of the vehicle VE that passage is impossible by voice or display, etc., and also to contact the management responsible person of the parking lot PA to that effect. Also, the mode of the warning notice may be made variously different according to the content determined to be registered on the blacklist. When the warning notice in step S107 is issued, without permitting entry in the entry reception device 20, the entry / exit management system 100 ends a series of processes.

[0048] Also, in step S102, if it is not confirmed that the security ID is used, the admission reception device 20 issues a parking ticket, that is, issues a parking ticket from the discharge port 21a of the ticket vending machine 21 (step S108). As a typical example of a mode that does not use the security ID, a ticket vending button (not shown) for issuing a parking ticket is provided in the admission reception device 20, and it is assumed that the ticket vending button is pressed. Along with the issuance of the parking ticket by the admission reception device 20, various information such as the issuance time and the parking ticket number is transmitted to the information management server 50, and these information are recorded in the parking ticket data management unit 52b of the parking data management unit 52 in the information management server 50. After the issuance of the parking ticket in step S108, the admission reception device 20 permits the entry of the vehicle VE and performs various operations such as the raising and lowering of the gate bar 22a by the gate device 22 to guide the vehicle into the venue (step S106).

[0049] When the admission reception device 20 finishes the above series of operations, it starts detecting the presence of a new vehicle VE that attempts to enter again (step S101).

[0050] Next, with reference to FIG. 5(B), an example of the operation of the entrance / exit management system 100 when the vehicle VE exits will be described.

[0051] Among the entrance / exit management system 100, the exit reception device 30 detects the presence of the vehicle VE that attempts to exit by, for example, various sensors (not shown) (step S201). In step S201, when the vehicle VE is detected (step S201: Yes), it is confirmed whether the vehicle VE uses the security ID of the credit card CC for entrance / exit management (step S202).

[0052] In step S202, the use of the security ID is confirmed. That is, when the security ID is read by the exit-side reader RDb (step S202: Yes), the exit-side reader RDb performs tokenization processing on the read security ID (step S203), and further, in the exit reception device 30, collation of the corresponding token is performed (step S204). That is, the exit reception device 30 can determine whether to permit exit in the exit determination unit 30a by referring to the data managed in the information management server 50 and the data corresponding to the token acquired in step S203.

[0053] Also, here, corresponding to the processing in step S203 and step S204, confirmation of blacklist registration regarding the security ID (step S205) is performed. Examples of cases where blacklist registration has occurred include cases where, for example, after permission to enter at the entrance reception device 20, the target credit card CC itself is blacklisted, or the data managed in the information management server 50 is blacklisted.

[0054] In step S205, if it is determined that there is no blacklist registration (step S205: No), the exit determination unit 30a determines whether to permit exit (step S206). Specifically, as step S206, for example, various processes such as determination of the necessity of settlement processing based on the collation result performed in step S204 and processing for completing the settlement processing when settlement processing is required are performed. As a result, if it is determined that exit permission is possible (step S207: Yes), the exit reception device 30 permits the vehicle VE to exit and performs various operations such as raising and lowering the gate bar 32a by the gate device 32 (step S208).

[0055] On the other hand, in step S205, when it is determined that the vehicle is registered in the blacklist (step S205: Yes), or in step S207, when it is determined that the vehicle is not permitted to enter the venue (step S207: No), the entrance / exit reception device 30 issues a warning notice to that effect (step S209). Note that various forms of warning notices are conceivable. For example, the vehicle occupants of vehicle VE may be notified of the inability to pass through by voice or display, etc., and the management responsible person of the parking lot PA may also be notified to that effect. Also, in this case, if necessary, new registration or continuous registration of blacklist registration, etc., is performed. When the warning notice in step S209 is issued, without permitting the vehicle to exit at the entrance / exit reception device 30, the access control system 100 ends a series of processes.

[0056] Also, in step S202, when it is not confirmed that the security ID is used (step S210), that is, when the entrance / exit reception device 30 receives the parking ticket inserted from the reception port 31a, based on the data regarding the received parking ticket, a determination of whether to permit the vehicle to exit is made (step S206), and the exit process is performed (steps S207 to S209).

[0057] As described above, the access control system 100 in the present embodiment includes a token conversion server 10 that tokenizes a security ID, a reader RD that reads the security ID, notifies the token conversion server 10, and receives a notification of the corresponding token, and an information management server 50 that manages access information in association with the token notified by the reader RD. In this case, in the access control system 100, the reader RD receives a notification of a token corresponding to the security ID, and by adopting a mode in which various management is performed in association with the token notified by the reader RD, for example, for vehicles VE entering and leaving the parking lot PA or bicycles entering and leaving the bicycle parking area, when performing information management regarding access to various facilities, even if a medium with a high security standard such as a credit card CC is used, it is not necessary to conform the entire system to a high security standard, so a system with a high security standard can be constructed with a simple configuration.

[0058] 〔Second Embodiment〕 Hereinafter, an example of the access control system 100 according to the second embodiment will be described with reference to FIG. 6 and the like. In the present embodiment, in the access control system 100 described as an example in the first embodiment, further, the reader has a storage unit and stores the notification history of the token together with the corresponding security ID, and when a communication trouble occurs, it is different from the first embodiment in that the information stored in the storage unit is used. Note that the overall configuration of the access control system 100 is the same as that in the first embodiment, so detailed descriptions of the components indicated by the same reference numerals in the overall configuration are omitted.

[0059] FIG. 6 is a block diagram for explaining an overview of a parking lot PA where the access control system 100 according to the present embodiment is installed, and is a diagram corresponding to FIG. 1. In the present embodiment, in addition to the storage unit Rm being provided in the entrance side reader RDa, the storage unit 20m is provided in the entrance determination unit 20a, and the storage unit 30m is provided in the exit determination unit 30a.

[0060] Each memory unit Rm, 20m, 30m is composed of various storage devices and stores data handled during communication between the units respectively.

[0061] As exemplified in the data table shown in FIG. 7, the memory unit Rm provided in the entrance side reader RDa stores data associating the security ID of the credit card CC, the corresponding token ID, and the generation time (token generation time) in the token conversion server 10 of the token ID as information regarding the notification history of the token. That is, the notification history of the token is accumulated together with the corresponding security ID. Note that, regarding the information (accumulated data) of the communication history accumulated as described above, it may be limited to, for example, a certain number of cases or a period, and the old ones may be sequentially deleted.

[0062] Here, communication is possible between the components constituting the PCIDSS authentication compliant unit 100A indicated by hatching. In particular, in an example shown in the figure, communication (in an example shown in the figure, wired communication) is possible between the entrance side reader RDa including the memory unit Rm and the exit side reader RDb, and the exit side reader RDb can acquire the information stored in the memory unit Rm from the entrance side reader RDa when a trouble occurs in the communication with the token conversion server 10.

[0063] Note that the memory unit 20m provided in the entrance determination unit 20a stores, for example, the token ID transferred from the entrance side reader RDa and the token generation time for the token ID. That is, among the data exemplified in FIG. 4(A) etc., the data acquired at the time of entry is stored.

[0064] Also, here, communication is possible between components that constitute the non-PCI DSS-compliant part 100B shown without hatching. In particular, in one example shown in the figure, communication (in one example shown in the figure, wired communication) is possible between the entrance determination unit 20a including the storage unit 20m and the exit determination unit 30a. When a communication trouble occurs between the exit determination unit 30a and the information management server 50, the exit determination unit 30a can acquire the information stored in the storage unit 20m from the entrance determination unit 20a. Further, when the exit determination unit 30a acquires the information stored in the storage unit 20m, the exit determination unit 30a stores information about a series of processing contents including the acquired information in the storage unit 30m. Then, when the communication with the information management server 50 resumes, the exit determination unit 30a transmits the series of information stored in the storage unit 30m to the information management server 50.

[0065] Hereinafter, with reference to the flowchart of FIG. 8, an example of the operation of the entry / exit management system 100 in the above-described mode when the vehicle VE exits the factory will be described. Here, it is possible to cope with a communication trouble between the exit-side reader RDb and the token conversion server 10 or a communication trouble between the exit determination unit 30a and the information management server 50.

[0066] Similar to the case described with reference to FIG. 5(B), first, the exit reception device 30 continues to detect the presence of the vehicle VE about to exit. When the vehicle VE is detected, the use of the security ID of the credit card CC is confirmed. When the security ID is read, tokenization processing is performed by the exit-side reader RDb (steps S301 to S303).

[0067] Here, during the tokenization process, it is confirmed whether there is a communication trouble between the exit-side reader RDb and the token conversion server 10 (step S304). If a communication trouble has occurred (step S304: Yes), the exit-side reader RDb inquires of the wired-connected entrance-side reader RDa and refers to the accumulated data stored in the storage unit Rm (step S305). That is, the exit-side reader RDb checks whether information corresponding to the security ID targeted at the time of exit exists in the accumulated data temporarily stored at the time of entry. As a result of the reference in step S305, if the corresponding data (token ID) does not exist (step S306: No), the exit reception device 30 aborts the process related to exit (step S307) and ends the series of processes. In this case, the exit reception device 30 notifies the vehicle VE passengers and the parking lot PA management responsible person that there has been a communication trouble by voice, display, etc.

[0068] On the other hand, if the corresponding token ID exists in step S306 (step S306: Yes), the exit-side reader RDb transfers it to the exit determination unit 30a, and thereafter, in the exit reception device 30, processing based on the token ID is performed.

[0069] If no communication trouble occurs in step S304 (step S304: No) and a token is acquired, or if a token is acquired from the storage unit Rm through steps S305, etc., in the exit reception device 30, the acquired token is collated (step S308). That is, the exit reception device 30 collates the acquired token with the data managed in the information management server 50.

[0070] Here, when collating the above tokens, it is confirmed whether there is a communication trouble between the exit determination unit 30a and the information management server 50 (step S309). If a communication trouble has occurred (step S309: Yes), the exit determination unit 30a inquires of the wired-connected entrance determination unit 20a and refers to the accumulated data stored in the storage unit 20m (step S310). That is, the exit determination unit 30a checks whether the information corresponding to the token ID targeted at the time of exit exists in the accumulated data temporarily stored at the time of entry. As a result of the reference in step S305, if the corresponding data (token ID) does not exist (step S311: No), the exit reception device 30 aborts the processing related to exit (step S312), finishes a series of processing, and notifies the vehicle VE passengers and the parking lot PA management responsible person of the existence of a communication trouble by voice, display, or the like.

[0071] On the other hand, if the corresponding token ID exists in step S311 (step S311: Yes), the exit determination unit 30a performs a determination process on whether to permit exit by using, for example, the token generation time for this token ID as corresponding to the entry time. Also, the exit determination unit 30a stores the acquired various data together with the acquired circumstances in the storage unit 30m.

[0072] If no communication trouble occurs in step S309 (step S309: No), when token collation is performed, or when information regarding the token is acquired from the storage unit 20m through steps S310 or the like, the exit reception device 30 checks for blacklist registration (step S313). If it is determined in step S313 that the vehicle is not registered in the blacklist (step S313: No), the exit determination unit 30a performs the same operation processes as those after step S206 in FIG. 5(B), such as a determination on whether to permit exit (steps S314 to S317).

[0073] Also, in step S302, if it is not confirmed that a security ID is used (step S302: No), the entrance / exit reception device 30 receives the parking ticket inserted from the reception port 31a (step S318), and based on the data regarding the received parking ticket, subsequent entrance / exit processing such as determination of permission to exit is performed (steps S314 to S317).

[0074] As described above, also in the entrance / exit management system 100 in the present embodiment, by adopting a mode of performing various managements based on the token corresponding to the security ID, a system with a simple configuration and high security standards can be constructed. In particular, in the present embodiment, the entrance-side reader RDa has a storage unit Rm that stores the notification history of the token together with the corresponding security ID, and when communication between the token conversion server 10 and the exit-side reader RDb becomes impossible, the information management server 50 manages the entrance / exit information based on the history stored in the storage unit Rm of the entrance-side reader RDa, so that even when communication between the exit-side reader RDb and the token conversion server 10 becomes impossible, entrance / exit management using the token can be maintained.

[0075] Also, as another aspect regarding the present embodiment, with reference to the flowchart of FIG. 9, an example of the operation of the entrance / exit management system 100 when the vehicle VE enters the system among a series of operations in the entrance / exit management system 100 of the above aspect will be described.

[0076] Similar to the case described with reference to FIG. 5(A), first, the entrance reception device 20 continuously detects the presence of the vehicle VE attempting to enter, and when the vehicle VE is detected, it confirms the use of the security ID of the credit card CC, and when the security ID is read, tokenization processing is performed by the entrance-side reader RDa (steps S401 to S403).

[0077] Here, during the tokenization process, it is confirmed whether there is a communication trouble between the entrance-side reader RDa and the token conversion server 10 (step S404). If a communication trouble has occurred (step S404: Yes), the entrance-side reader RDa refers to the accumulated data stored in the built-in storage unit Rm (step S405). That is, by tracing the history of the accumulated data, it is confirmed whether there exists data of the same security ID as the currently targeted security ID and the corresponding token ID among the security IDs handled in the past. As a typical example, when a regularly used vehicle VE uses the parking lot PA multiple times within the valid period of the token ID, it is assumed that the corresponding data (past entry data) exists in the storage unit Rm.

[0078] As a result of the reference in step S405, if the corresponding data (token ID) does not exist (step S406: No), the entrance reception device 20 aborts the process related to the entry (step S407) and ends the series of processes. In this case, the entrance reception device 20 notifies the vehicle VE's passenger and the parking lot PA's management responsible person of the existence of the communication trouble by voice, display, etc.

[0079] On the other hand, if the corresponding token ID exists in step S406 (step S406: Yes), the entrance-side reader RDa transfers it to the entrance determination unit 20a, and thereafter, in the entrance reception device 20, processing based on the token ID is performed.

[0080] If no communication trouble occurs in step S404 (step S404: No), when the tokenization process is performed, or when information regarding the token is acquired from the storage unit Rm through step S405 or the like, the entrance determination unit 20a performs the same operation processes as those after step S104 in FIG. 5(A), such as confirmation of blacklist registration (steps S408 to S411).

[0081] Also, in step S402, if it is not confirmed that the security ID is used (step S402: No), the admission reception device 20 issues a parking ticket (step S412), permits the entry of the vehicle VE, and performs various operations such as raising and lowering the gate bar 22a by the gate device 22 to guide the vehicle into the site (step S410).

[0082] 〔Third Embodiment〕 Hereinafter, an example of the entry / exit management system 100 according to the third embodiment will be described with reference to FIG. 10 and the like. In this embodiment, it is different from the first embodiment and the like in that the installation locations of the readers are increased as compared with the entry / exit management system 100 described as an example in the first embodiment and the like. Note that, among the components of the entry / exit management system 100 in this embodiment, detailed descriptions of the components denoted by the same reference numerals as those in the first embodiment and the like are omitted.

[0083] FIG. 10 is a conceptual diagram for explaining the outline of the parking lot PA where the entry / exit management system 100 according to this embodiment is installed, and is a diagram corresponding to FIG. 3. Also, the block diagram shown in FIG. 11 is a diagram corresponding to FIGS. 1 and the like. The entry / exit management system 100 according to this embodiment includes a pre-settlement device 60 and a store terminal device 70 in addition to each part laid in the parking lot PA exemplified with reference to FIGS. 3 and the like.

[0084] The pre-settlement device 60 is a device that enables the pre-settlement process of the parking fee required for exiting. Here, it includes a main body part 60a that performs various processes for pre-settlement and a facility-side reader RDc as a reader RD. As shown in the figure, among the pre-settlement devices 60, the facility-side reader RDc indicated by hatching belongs to the PCIDSS certification compliant part 100A, while the main body part 60a indicated without hatching belongs to the PCIDSS certification non-compliant part 100B. That is, the facility-side reader RDc communicates with the token conversion server 10 to perform tokenization processing. In the main body part 60a, when receiving a token from the facility-side reader RDc, it can associate information related to the pre-settlement process with the acquired token by communicating with the information management server 50.

[0085] The pre-settlement device 60 is installed inside the facility where the parking lot PA is installed, at the entrance of people from the parking lot PA to the facility, etc. By using it, the user US of the parking lot PA who is a passenger in the vehicle VE can omit the settlement process when leaving the lot, enabling a quick exit.

[0086] Among the pre-settlement devices 60, the facility-side reader RDc is composed of an EMV authentication reader. It reads the PAN as a security ID from the credit card CC via the interface unit 63a, notifies the token conversion server 10, and receives a notification of the token corresponding to the PAN from the token conversion server 10.

[0087] Among the pre-settlement devices 60, the main body part 60a is composed of various control circuits, an input operation part, a display part, etc. to enable the above-mentioned pre-settlement process. That is, the main body part 60a functions as a pre-settlement machine that receives an operation command from the user US through the above-mentioned parts and performs various processes for pre-settlement accordingly, thereby receiving the pre-settlement process of the parking fee. Also, here in particular, the main body part 60a can notify the parking data management part 52 (token data management part 52a) of the information management server 50 by associating it with the token received from the facility-side reader RDc regarding the processing result, that is, the result of the pre-settlement process. When using a parking ticket, it can be handled by inserting the parking ticket into the reception port 61a.

[0088] As described above, when the pre-settlement using the pre-settlement device 60 is completed, the pre-settlement device 60 is configured to send a notice to that effect to the information management server 50 responsible for parking management.

[0089] The store terminal device 70 is a device provided in store X within a facility that has a partnership with parking lot PA. Here, as one aspect of the use of the facility (store X), it is assumed that there is a cash register device or the like for employees CL of store X to perform operations. The store terminal device 70 includes a main body part 70a for performing a cash register operation according to the use of store X, and a facility-side reader RDd as a reader RD.

[0090] Among the store terminal devices 70, the facility-side reader RDd is composed of an EMV authentication reading device. It reads the PAN as a security ID from the credit card CC via the interface part 73a, notifies the token conversion server 10, and receives a notification of the token corresponding to the PAN from the token conversion server 10.

[0091] Among the store terminal devices 70, the main body part 70a is composed of various control circuits, an input operation part, a display part, etc. to enable processing related to store use as described above (settlement processing for store use by the cash register). That is, the main body part 70a functions as a cash register device by receiving operation commands from employees CL etc. through the above-mentioned parts and performing various corresponding processes. Also, here in particular, the store terminal device 70 can link the processing result in the main body part 70a that constitutes the PCIDSS non-compliant part 100B with the token received from the facility-side reader RDd that constitutes the PCIDSS compliant part 100A, and notify the parking data management part 52 (token data management part 52a) of the information management server 50.

[0092] With the above-described aspect, the information management server 50 can perform information management involving the provision of various additional services linked with tokens during parking management. Specifically, for example, as shown in the data table in FIG. 12, in the data DD3 indicating time information, in addition to information regarding entry and exit, based on the notification from the store terminal device 70, a discount application for the parking fee corresponding to the use of store X is performed, or it is noted that pre-settlement using the pre-settlement device 60 has been completed, etc. These are managed together with this type of information.

[0093] As described above, also in the access control system 100 according to the present embodiment, by adopting a mode in which various management is performed based on a token corresponding to a security ID, it is possible to construct a system with a simple configuration and high security standards. In particular, in the present embodiment, as the reader RD, it further includes facility-side readers RDc and RDd installed in facilities other than parking lots and bicycle parking lots. Among these, for example, when using the facility (store X inside the facility), the facility-side reader RDd reads the security ID and receives a notification of the corresponding token from the token conversion server 10. The information management server 50 can perform an application process for discounting the fee for the parking lot PA or the like based on the token notified by the facility-side reader RDd. That is, in the case of the above mode, it is possible to apply a fee discount using the token.

[0094] 〔Fourth Embodiment〕 Hereinafter, an example of the access control system 100 according to the fourth embodiment will be described with reference to FIG. 13 and the like. In the first embodiment and the like, the access control system 100 was introduced in a parking lot (or a bicycle parking lot) to perform access control of vehicles. In contrast, in the present embodiment, it is different from other embodiments in that it is a mode of performing access control in facilities other than parking lots, or a mode of comprehensively performing access control in other facilities together with the management of parking lots and the like.

[0095] As conceptually shown in FIG. 13, in the present embodiment, an aspect in the case where the access control system 100 is introduced into the station ST will be described. Here, the case where the access control system 100 is applied in the access control at the station ST using the token notification when passing through the automatic ticket gate AG installed at the station ST will be described. In the illustrated example, an owner (not shown) holding a credit card CC passes through the automatic ticket gate AG installed at one station STα and enters the precincts of the station STα, and uses the train TR to pass through the automatic ticket gate AG installed at another station STβ and exit outside the station STβ, which conceptually represents the situation.

[0096] In this case, each automatic ticket gate AG corresponding to the ticket gate of the station is provided with a ticket gate reader RDe as a leader RD. The automatic ticket gate AG has an interface unit AGa that enables non-contact reading of various media including the credit card CC.

[0097] The ticket gate reader RDe reads the security ID of the credit card CC via the interface unit AGa, notifies the token conversion server 10, and receives the corresponding token from the token conversion server 10. That is, the ticket gate reader RDe, which is an EMV authentication reader, is installed inside the automatic ticket gate AG and communicates with the token conversion server 10 to perform tokenization processing, thereby constituting the PCIDSS-compliant unit 100A.

[0098] While receiving the token notified to the ticket gate reader RDe from the ticket gate reader RDe, the automatic ticket gate AG determines whether to allow passage based on the information about the credit card CC, and further functions as a gate device by opening and closing the gate GT as necessary. Note that the information of the token received from the ticket gate reader RDe in the automatic ticket gate AG and various information such as the passing time at the automatic ticket gate AG associated therewith are notified from the automatic ticket gate AG to the information management server 50 and managed by the information management server 50. That is, the automatic ticket gate AG and the information management server 50 perform entry / exit management based on the token received from the ticket gate reader RDe and can be configured as the non-PCIDSS-compliant unit 100B.

[0099] As described above, also in the access management system 100 according to the present embodiment, by adopting a mode in which various management is performed based on a token corresponding to a security ID, it is possible to construct a system with a simple configuration and high security standards. In particular, in the present embodiment, as the reader RD, a ticket gate reader RDe installed at the station ST is used as a facility other than a parking lot or a bicycle parking lot. That is, as the reader RD, it includes the ticket gate reader RDe provided at the ticket gate of the station ST, and the information management server 50 can be configured to manage the entry / exit information of the passers-by at the ticket gate based on the token notified by the ticket gate reader RDe. That is, in the case of the above mode, tokens are used in the entry / exit management of the passers-by at the ticket gate of the station ST.

[0100] Furthermore, as another aspect (a modified aspect) related to the present embodiment, as illustrated in FIG. 14, it may be configured to comprehensively and intensively manage information in a plurality of facilities by using a token corresponding to the security ID of the credit card CC. In an example shown in FIG. 14, it is possible to perform entry / exit management using the credit card CC in a parking lot PA, a station ST, etc. As a usage mode, as an example shown by arrows R1 to R10 in the figure, a user US (owner of the vehicle VE) who owns the credit card CC sequentially uses each facility. More specifically, first, as shown by arrow R1, the vehicle VE (with the user US on board) enters the parking lot PA and parks. After that, as shown by arrow R2, the user US, who is the owner of the vehicle VE, heads towards the station STα. As shown by arrows R3 and R4, the user US passes through the automatic ticket gate AG of the station STα, boards the train TR from the station STα, gets off at the station STβ, passes through the automatic ticket gate AG of the station STβ, and heads towards the destination (for example, the store X) as shown by arrow R5, and uses the store X. After that, as shown by arrows R6 to R9, the user US returns to the parking lot PA in the reverse order of R2 to R5 above, and finally, as shown by arrow R10, the vehicle VE exits the parking lot PA.

[0101] Regarding the operation of the access control system 100 in the above series of operations, as shown by the solid-line reciprocating arrows in the figure, each time a credit card CC is used, the PCIDSS compliance unit 100A composed of each reader RD, etc. issues and notifies a token corresponding to the security ID. Also, as shown by the dashed-line reciprocating arrows in the figure, in the PCIDSS non-compliance unit 100B composed of the entrance determination unit 20a, etc., information management regarding access based on the issued token is performed centrally. Looking at it another way, in the above aspect, multi-use based on a credit card CC as one physical object is realized.

[0102] 〔Others〕 This invention is not limited to the above-described embodiments, and can be implemented in various modes without departing from the gist thereof.

[0103] First, in the above, the case of adopting the access control system 100 for access control in a parking lot, a bicycle parking lot, or a ticket gate at a station has been described. However, the access control system 100 is not limited to this, and can be used in various modes in various service provisions. For example, it is also conceivable to apply the access control system 100 to the management of entry and exit in an event venue or a membership facility.

[0104] Also, in the above, as the access control by the access control system 100, for example, when introducing it into a parking lot or a bicycle parking lot, it is an aspect of capturing and managing the difference in time between the entry time and the exit time. On the other hand, for example, when introducing it into a ticket gate at a station, it is conceivable to adopt an aspect of capturing and managing the difference in distance (position) between the entry time and the exit time. However, the management items in the access control by the access control system 100 are not limited to time and distance, and various things are conceivable. For example, when managing a vehicle entering and leaving a garbage collection site, it is conceivable to adopt an aspect of capturing the difference in weight between the entry time and the exit time, and various management items can be provided according to the management target.

[0105] In addition, in the above description, the medium for issuing tokens to be managed is a credit card. However, it is also conceivable to configure the entry / exit management system 100 by using other media such as Suica (registered trademark) electronic money, QR code (registered trademark), etc., or by using these in combination with a credit card.

[0106] Also, in the above, for example, regarding the payment of fees, i.e., the settlement process, at a parking lot, various modes can be adopted, and it is not necessarily limited to credit card settlement. On the other hand, looking at the above mode from a different perspective, it can also be regarded as a mode that improves the convenience of users by unifying (making it possible to handle both cases with and without settlement (non-settlement) together with a single credit card).

Explanation of Signs

[0107] 10… Token conversion server, 20… Entrance reception device, 20a… Entrance determination unit, 20m… Storage unit, 21… Ticket issuing machine, 21a… Discharge port, 22… Gate device, 22a… Gate bar, 23a… Interface unit, 30… Exit reception device, 30a… Exit determination unit, 30m… Storage unit, 31… Settlement device, 31a… Reception port, 32… Gate device, 32a… Gate bar, 33a… Interface unit, 50… Information management server, 51… Communication unit, 52… Parking data management unit, 52a… Token data management unit, 52b… Parking ticket data management unit, 60… Pre-settlement device, 60a… Main body part, 63a… Interface unit, 70… Store terminal device, 70a… Main body part, 73a… Interface unit, 100… Entrance / exit management system, 100A… PCIDSS compliance part, 100B… PCIDSS non-compliance part, A1, A2… Arrows, AG… Automatic ticket gate, AGa… Interface unit, CC… Credit card, CL… Employee, DD1~DD4… Data, DT… Data table, GT… Gate, PA… Parking lot, R1~R10… Arrows, RD… Reader, RDa… Entrance side reader, RDb… Exit side reader, RDc, RDd… Facility side reader, RDe… Ticket gate reader, Rm… Storage unit, ST, STα, STβ… Station, TR… Train, US… User, VE… Vehicle, X… Store

Claims

1. A token conversion server that tokenizes a security ID, a reader that reads the security ID, notifies the token conversion server, and receives notification of the corresponding token, and an information management server that manages entry / exit information in association with the token notified by the reader are provided, the reader has an entrance-side reader installed at the entrance and an exit-side reader installed at the exit, the entrance-side reader has a storage unit that stores the notification history of the token together with the corresponding security ID, when communication with the token conversion server becomes impossible at the exit-side reader, the exit-side reader refers to the notification history of the token stored in the storage unit, and the information management server manages the entry / exit information based on the reference result at the exit-side reader. An entry / exit management system.

2. The reader is provided in a parking lot or a bicycle parking area, The information management server manages the entry / exit information of vehicles using the parking lot or the bicycle parking area based on the token notified by the reader. The entry / exit management system according to claim 1.

3. The entry / exit management system according to claim 2, further comprising a calculator that is communicably connected to the information management server and calculates fees based on the entry / exit information of the vehicle.

4. The entry / exit management system according to claim 3, including a pre-calculator that accepts pre-calculation processing of fees as the calculator.

5. The reader further includes a facility-side reader installed in a facility other than the parking lot or the bicycle parking area, when using the facility, the facility-side reader reads the security ID and receives notification of the corresponding token from the token conversion server, The information management server performs an application process for discounting the fees of the parking lot or the bicycle parking area based on the token notified by the facility-side reader. The entry / exit management system according to any one of claims 2 to 4.

6. An entrance determination unit that receives notification of a token from the entrance-side reader, is communicably connected to the information management server, and determines whether entry is permitted at the entrance side, and an exit determination unit that receives notification of a token from the exit-side reader, is communicably connected to the information management server, and determines whether exit is permitted at the exit side are provided. The exit determination unit determines whether or not to allow exit based on the accumulated data stored in the entrance determination unit when communication with the information management server becomes impossible. The entry / exit management system according to any one of claims 1 to 5.

7. The reader includes a ticket gate reader provided at the ticket gate of the station. The information management server manages the entry / exit information of the passengers passing through the ticket gate based on the token notified by the ticket gate reader. The entry / exit management system according to any one of claims 1 to 6.

8. The information management server sets the expiration date and the blacklist target for the token notified by the reader. The entry / exit management system according to any one of claims 1 to 7.

Images