JP7785876B2 - User identification system and user identification method - Google Patents

Description

Embodiments of the present invention relate to a user identification system and a user identification method.

Conventionally, there have been systems that use the on-board unit ID transmitted from ETC on-board units to control the opening and closing of entry/exit control sections in apartment buildings and commercial facilities. However, because the on-board unit ID transmitted from the on-board unit is an ID associated with the vehicle, it is not possible to accurately identify the people inside the vehicle. As a result, these systems have sometimes been unable to be used in locations requiring high security.

Japanese Patent Application Laid-Open No. 2005-227996 JP 2009-294310 A

"Apartment Parking Lot (Apartment ETC System)", [online], [Retrieved May 24, 2016], Internet <URL: http://www.furuno.com/jp/dsrc/case/enter_leave/>

The problem that this invention aims to solve is to provide a user identification system and method that can identify people inside a vehicle with greater accuracy.

The entry/exit system of this embodiment includes an on-board device ID matching device, an entry/exit management device, and an entry/exit roadside device. The information control unit of the on-board device ID matching device identifies the mobile terminal ID of the mobile terminal carried by the person riding in the vehicle based on the on-board device ID, which is identification information for the on-board device of the vehicle that has entered the entry/exit system, and transmits the mobile terminal ID to the entry/exit management device. The entry/exit management device authentication processing unit performs authentication processing on the matching information received by the entry/exit management device. The entry/exit control unit of the entry/exit roadside device determines whether to open or close the entry/exit restriction unit based on the results of the authentication processing.

1 is a schematic diagram showing a specific application example of the entrance/exit system 1 of the first embodiment. FIG. 1 is a system configuration diagram showing the system configuration of an entrance/exit system 1. FIG. 2 is a schematic block diagram showing the functional configuration of the vehicle-mounted device 100. FIG. 5 is a schematic block diagram showing the functional configuration of a mobile terminal 500. FIG. 2 is a sequence diagram showing the processing flow of the entry/exit system 1 according to the first embodiment. FIG. 10 is a system configuration diagram showing the system configuration of an entry/exit system 2 according to a second embodiment. FIG. 11 is a sequence diagram showing the flow of processing until an operator links and registers an in-vehicle device ID, a facility ID, and a mobile terminal ID in the entry/exit system 2 according to the second embodiment. FIG. 11 is a sequence diagram showing the processing flow of the entry/exit system 2 in the second embodiment. FIG. 10 is a system configuration diagram showing the system configuration of an entry/exit system 3 according to a third embodiment. FIG. 11 is a sequence diagram showing a processing flow until the use of the vehicle-mounted device ID and the mobile terminal ID is started in the entry/exit system 3 according to the third embodiment. FIG. 11 is a sequence diagram showing the flow of processing by the entry/exit system 3 according to the third embodiment.

The following describes an embodiment of the entrance/exit system and entrance/exit control method with reference to the drawings.

(First embodiment)
1 is a schematic diagram showing a specific application example of the first embodiment of the entrance/exit system 1. In FIG. 1, the entrance/exit system 1 is a system that controls the entrance/exit of a vehicle using an on-board device 100 mounted on the vehicle.
1 , a facility 10 is surrounded by a fence or the like. An entrance/exit roadside device 200 and an entrance/exit control device 600 are provided at the entrance/exit of the facility 10. An in-vehicle ID matching device 300 and an entrance/exit management device 400 are connected to the entrance/exit roadside device 200 via a network 700. A mobile terminal 500 is carried by a driver of the vehicle or the like.

The vehicle-mounted device ID matching device 300 is, for example, a dedicated information processing device managed by an external organization such as a government. The entry/exit management device 400 is an information processing device that stores an authentication information table that associates mobile device IDs, facility variable PINs, and mobile device PINs that are preset by the vehicle-mounted device user and do not need to be updated. Here, the mobile device ID is identification information for the mobile device 500. The mobile device ID may be any value that does not overlap with other mobile device IDs. The mobile device ID may be, for example, an email address, serial number, MAC address, etc. The mobile device PIN is information that is stored in the authentication information table in advance by the vehicle-mounted device user. The facility variable PIN is PIN information that is periodically generated by the entry/exit management device 400. The facility variable PIN is information that changes at short intervals, such as daily. For this reason, the facility variable PIN is information that cannot be known even to those riding in the vehicle until notified. The combination of facility variable PIN, mobile terminal PIN, and mobile terminal ID will be referred to as "verification information" below.

The in-vehicle unit 100 is an in-vehicle unit for receiving electronic toll collection services via ETC. An in-vehicle unit ID is set for the in-vehicle unit 100 when it is installed in a vehicle. The mobile terminal 500 is a terminal capable of short-range wireless communication or medium-range wireless communication. Specifically, the mobile terminal 500 is a portable terminal such as a smartphone or tablet.

In the entry/exit system 1 configured in this manner, authentication is not based solely on the onboard device ID, which is the identification information of the onboard device 100, but also on the facility variable PIN and mobile terminal PIN. This makes it possible to authenticate people who are actually in the vehicle, enabling people inside the vehicle to be identified with greater accuracy. Furthermore, in the entry/exit system 1 configured in this manner, unless the onboard device 100 and the mobile terminal 500 are near the entry/exit roadside unit 200, they cannot be authenticated by the entry/exit management device 400. This prevents the mobile terminal 500 from being operated by someone away from the vehicle. This also makes it possible to identify people inside the vehicle with greater accuracy.

Since the vehicle-mounted device ID is very important information, it must be managed strictly. Therefore, it is desirable that the vehicle-mounted device ID matching device 300, which has a table in which the vehicle-mounted device IDs are registered, be managed by a strict organization. For example, the vehicle-mounted device ID matching device 300 may be configured as a server device operated by a public organization such as an affiliated organization.
On the other hand, although verification information including a mobile terminal ID (e.g., an email address) is personal information and important, it does not need to be managed as strictly as an in-vehicle device ID, and it is preferable that it be registered and updated flexibly for each facility 10. Therefore, the verification information is managed by the entry/exit management device 400. In the above-described entry/exit system 1, the in-vehicle device ID and the mobile terminal ID are associated and managed in the in-vehicle device ID verification device 300, and the mobile terminal ID is transmitted to the entry/exit management device 400. In other words, the in-vehicle device ID is not transmitted to the entry/exit management device 400. This configuration makes it possible to manage the in-vehicle device ID more strictly and maintain security.

Next, a description will be given of each component that makes up the entrance/exit system 1 with reference to a configuration diagram. FIG. 2 is a system configuration diagram showing the system configuration of the entrance/exit system 1.
The ingress/egress roadside device 200 includes an in-vehicle communication unit 201, an encryption processing unit 202, an IP communication unit 204, a terminal communication unit 203, a communication control unit 205, an ingress/egress control unit 206, and an ingress/egress communication unit 207. The ingress/egress roadside device 200 includes a plurality of network interfaces, a CPU (Central Processing Unit) connected by a bus, a memory, an auxiliary storage device, etc. Note that all or part of the functions of the ingress/egress roadside device 200 may be realized using hardware such as an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array). The ingress/egress roadside device 200 may be configured using a plurality of information processing devices.

The vehicle-mounted device communication unit 201 is a network interface for communicating with the vehicle-mounted device 100. Wireless communication may be, for example, DSRC (Dedicated Short Range Communication), which is used in the conventional ETC system or the ETC 2.0 system.

The encryption processing unit 202 performs encryption processing on the vehicle-mounted device ID and generates an encrypted vehicle-mounted device ID.

The terminal communication unit 203 is a network interface that allows the entrance/exit roadside unit 200 to communicate with the mobile terminal 500. For wireless communication, a short-range wireless communication method is preferable to prevent communication from long distances. Wireless communication may be, for example, wireless LAN (Wi-Fi), Bluetooth (registered trademark), or NFC (Near Field Communication).

The IP communication unit 204 is a network interface through which the entry/exit roadside unit 200 communicates. The IP communication unit 204 communicates with the vehicle-mounted device ID matching device 300 via the network 700 to query the mobile terminal ID.

The communication control unit 205 controls the execution of authentication processing by the entrance/exit roadside unit 200 when a vehicle equipped with the on-board unit 100 enters the entrance/exit system 1.

The entry/exit control unit 206 controls the entry/exit inhibitor 600 to open the gate based on instructions from the entry/exit management device 400.

The entry/exit communication unit 207 is a network interface that allows the entry/exit roadside device 200 to communicate with the entry/exit inhibitor 600. The entry/exit communication unit 207 communicates with the entry/exit inhibitor 600. The communication method may be, for example, wired communication. The communication method may also be, for example, wireless communication such as Bluetooth or wireless LAN.

The entry/exit inhibitor 600 is a device that actually prevents vehicles from entering. Specifically, the entry/exit inhibitor 600 is composed of a barrier, shutters, etc. The entry/exit inhibitor 600 includes a communication unit 601, an entry/exit control unit 602, and an entry/exit inhibitor 603.

The communication unit 601 is an interface unit that communicates with the entrance/exit roadside unit 200, and the communication method can be any method, such as Bluetooth, wireless LAN, wired LAN, etc.

The entry/exit control unit 602 notifies the entry/exit suppression unit 603 of an open gate command based on an open gate command from the entry/exit roadside unit 200. After notifying the open gate command, the entry/exit control unit 602 notifies the entry/exit suppression unit 603 of a close gate command when a predetermined time has elapsed. In addition, the entry/exit control unit 602 may notify the entry/exit suppression unit 603 of a close gate command after the vehicle-mounted device 100 passes through the entry/exit suppression unit 603 that has opened the gate.

When the entry/exit control unit 603 receives a notification of an open gate instruction from the entry/exit control unit 602, it opens the entry/exit control unit 603. Furthermore, when the entry/exit control unit 603 receives a notification of a close gate instruction from the entry/exit control unit 602, it closes the entry/exit control unit 603. Furthermore, the entry and exit control unit 603 may have different entrance and exit sections.

The vehicle-mounted device ID matching device 300 comprises an IP communication unit 301, a device information storage unit 302, an information control unit 303, and a decryption processing unit 304. The vehicle-mounted device ID matching device 300 is configured using an information processing device such as a mainframe, workstation, or personal computer. The vehicle-mounted device ID matching device 300 can be any device that is capable of providing the functions listed below. The vehicle-mounted device ID matching device 300 comprises a network interface, a CPU connected via a bus, memory, and auxiliary storage device. Note that all or part of the functions of the vehicle-mounted device ID matching device 300 may be realized using hardware such as an ASIC, PLD, or FPGA.

The IP communication unit 301 is a network interface through which the vehicle-mounted device ID matching device 300 communicates. The IP communication unit 301 communicates with the entry/exit roadside unit 200 and the entry/exit management device 400 via the network 700.

The device information storage unit 302 is configured using a storage device such as a magnetic hard disk drive or a semiconductor storage device. The device information storage unit 302 stores an in-vehicle device ID table 311. As shown in Figure 2, the in-vehicle device ID record has values for the in-vehicle device ID and the mobile terminal ID.

In the example shown in Figure 2, the topmost in-vehicle device ID record in the in-vehicle device ID table 311 has an in-vehicle device ID of "XXX" and a mobile terminal ID of "xxx@xxx". This in-vehicle device ID record indicates that if the in-vehicle device ID received by the in-vehicle device ID matching device 300 is "XXX", the information control unit 303 will obtain the mobile terminal ID "xxx@xxx". Note that the in-vehicle device ID table 311 shown in Figure 2 is only one specific example. Therefore, the in-vehicle device ID table 311 may be configured in a manner different from that shown in Figure 2.

The information control unit 303 executes the decryption process of the encrypted vehicle-mounted device ID in the decryption processing unit 304. The information control unit 303 acquires the mobile terminal ID stored in the record where the vehicle-mounted device ID satisfies (e.g., matches) the specified requirements from the vehicle-mounted device ID table 311 in the device information storage unit 302. The information control unit 303 transmits the mobile terminal ID to the entry/exit management device 400.

The decryption processing unit 304 executes the decryption process for the encrypted vehicle-mounted device ID. The decryption processing unit 304 notifies the information control unit 303 of the decrypted vehicle-mounted device ID.

The access control device 400 comprises an IP communication unit 401, an authentication control unit 402, an authentication information storage unit 403, an authentication processing unit 404, and a facility variable password generation unit 405. The access control device 400 is configured using information processing devices such as network equipment, mainframes, workstations, and personal computers. The access control device 400 can be any device that is capable of providing the functions listed below. The access control device 400 comprises a network interface, a CPU connected via a bus, memory, and auxiliary storage devices. Note that all or part of the functions of the access control device 400 may be realized using hardware such as an ASIC, PLD, or FPGA.

The IP communication unit 401 is a network interface through which the entry/exit management device 400 communicates. The IP communication unit 401 communicates with the entry/exit roadside unit 200 and the vehicle-mounted device ID matching device 300 via the network 700.

The authentication control unit 402 receives the mobile terminal ID from the vehicle-mounted device ID matching device 300. The authentication control unit 402 obtains the facility variable PIN from the authentication information storage unit 403 and transmits it to the vehicle-mounted device 100. The authentication control unit 402 performs authentication processing of the matching information in the authentication processing unit 404. The authentication control unit 402 transmits the authentication processing result of the authentication processing unit 404 to the entrance/exit roadside unit 200.

The authentication information storage unit 403 is configured using a storage device such as a magnetic hard disk drive or a semiconductor storage device. The authentication information storage unit 403 stores an authentication information table 411.

As shown in FIG. 2, the authentication information table 411 has matching information for each authentication information record. The facility variable PIN is authentication information that is periodically generated by the facility variable PIN generation unit 405. The facility variable PIN may be, for example, a character string including numbers and letters. The mobile terminal PIN is authentication information that has been pre-registered in the authentication information record by the user of the vehicle-mounted device 100 (hereinafter referred to as the "vehicle-mounted device user"). The mobile terminal PIN may be any information that is used as existing authentication information, such as a character string including numbers and letters, a combination of pictures, or a line pattern. The mobile terminal PIN may be, for example, biometric information such as a fingerprint or face. The mobile terminal PIN may also be a combination of multiple pieces of information.

In the example shown in FIG. 2, the authentication information record at the top of the authentication information table 411 has a device ID of "xxx@xxx", a facility variable PIN of "QQQQ", and a mobile device PIN of "RRRR". If the authentication information received by the access control device 400 has a mobile device ID of "xxx@xxx", a facility variable PIN of "QQQQ", and a mobile device PIN of "RRRR", the authentication processing unit 404 determines that authentication has been successful. Note that the authentication information table 411 shown in FIG. 2 is merely one specific example. Therefore, the authentication information table 411 may be configured in a manner different from that shown in FIG. 2. For example, the authentication information table 411 may include the date and time when the mobile device PIN was updated.

The authentication processing unit 404 performs authentication processing based on the matching information received by the entry/exit management device 400 and the authentication information record stored in the authentication information storage unit 403. Specifically, if the matching information received by the entry/exit management device 400 and the authentication information record stored in the authentication information storage unit 403 satisfy predetermined authentication conditions (e.g., they match), the authentication processing unit 404 determines that the on-board device 100 is a device with legitimate authority. On the other hand, if the matching information received by the entry/exit management device 400 and the authentication information record stored in the authentication information storage unit 403 do not satisfy predetermined authentication conditions (e.g., they do not match), the authentication processing unit 404 determines that the on-board device 100 is a device without legitimate authority.

The facility variable PIN generation unit 405 generates a facility variable PIN at a predetermined frequency. The facility variable PIN generation unit 405 registers the generated facility variable PIN in the facility variable PIN in the authentication information table 411 of the authentication information storage unit 403. The facility variable PIN may be generated, for example, once a day. A random value is generated for each record of the facility variable PIN.

The network 700 connects the entry/exit roadside device 200, the vehicle-mounted device ID matching device 300, and the entry/exit management device 400 so that they can communicate with each other. The network 700 may be configured, for example, as the Internet.

Figure 3 is a schematic block diagram showing the functional configuration of the in-vehicle device 100. The in-vehicle device 100 is configured using an ETC in-vehicle device mounted on a vehicle. The in-vehicle device 100 includes a network interface, a CPU, memory, and auxiliary storage device connected via a bus. By executing an authentication program, the in-vehicle device 100 functions as a device including a communication unit 101, an information control unit 102, an in-vehicle device information storage unit 103, an audio output unit 104, a display unit 105, and a card input/output unit 106. Note that all or part of the functions of the in-vehicle device 100 may be realized using hardware such as an ASIC, PLD, or FPGA. The authentication program may be recorded on a computer-readable recording medium. Examples of computer-readable recording media include portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and semiconductor storage devices, as well as storage devices such as hard disks and semiconductor storage devices built into a computer system. Note that the in-vehicle device 100 may also be configured using in-vehicle devices such as a car navigation system or audio system.

The communication unit 101 is a network interface capable of communicating with the vehicle-mounted device communication unit 201. The communication unit 101 communicates with the entry/exit roadside unit 200. The communication method may be, for example, DSRC.

The information control unit 102 controls the execution of the authentication process of the vehicle-mounted device 100. It acquires the vehicle-mounted device ID from the vehicle-mounted device information storage unit 103 and transmits it to the vehicle-mounted device ID matching device 300 via the entry/exit roadside device 200. The information control unit 102 notifies the audio output unit 104 of the facility variable PIN received from the entry/exit roadside device 200. The information control unit 102 notifies the display unit 105 of the facility variable PIN received from the entry/exit roadside device 200. The vehicle-mounted device ID is identification information for the vehicle-mounted device of a vehicle that has entered the entry/exit system. The vehicle-mounted device ID may be any value that does not overlap with other vehicle-mounted device IDs. The vehicle-mounted device ID may be, for example, the WCN (Wireless Call Number) or serial number of an ETC (Electronic Toll Collection System) vehicle-mounted device.

The vehicle-mounted device information storage unit 103 is configured using a storage device such as a magnetic hard disk drive or a semiconductor storage device. The vehicle-mounted device information storage unit 103 stores the vehicle-mounted device ID.

The audio output unit 104 is configured using an existing audio output device such as a speaker, earphone, or headphone. The audio output unit 104 may also be an interface for connecting an audio output device to the in-vehicle device 100. In this case, the audio output unit 104 generates an audio signal from the audio data and outputs the audio signal to the audio output device connected to the audio output unit 104.

The display unit 105 is a video output device such as a CRT (Cathode Ray Tube) display, a liquid crystal display, or an organic EL (Electro Luminescence) display. The display unit 105 may also be an interface for connecting a video output device to the vehicle-mounted device 100. In this case, the display unit 105 generates a video signal from the video data and outputs the video signal to the video output device connected to it.

The card input/output unit 106 has a card slot into which a card 107 is inserted. The card input/output unit 106 acquires and registers information for the card 107 inserted in the card slot. Note that in the example of Figure 3, the card input/output unit 106 has one card slot and is configured to accept one card 107. However, a configuration different from that shown in Figure 3 may also be used. For example, the card input/output unit 106 may have two or more card slots.

Card 107 is a card used to settle tolls using the ETC system. Card 107 is inserted into a card slot provided in card input/output unit 106 for use. Information recorded on card 107 includes identification information unique to each card 107, and pre-recorded information indicating the organization issuing card 107 (specifically, a credit card company or an institution affiliated with a credit card company) or the type of service provided to the user of card 107. In addition to the card information, card 107 also records information on the entrance toll gate where the user began using the road and the exit toll gate where the user finished using the road.

Figure 4 is a schematic block diagram showing the functional configuration of the mobile terminal 500. The mobile terminal 500 is configured using an information processing device such as a tablet computer, personal computer, or smartphone. The mobile terminal 500 includes a short-range wireless communication unit 501, an input/output control unit 502, a display unit 503, and an input unit 504. The mobile terminal 500 includes a network interface, a CPU, memory, auxiliary storage device, and the like, all connected via a bus. The mobile terminal 500 is owned, for example, by a passenger in a vehicle.

The short-range wireless communication unit 501 is a network interface for communication between the mobile terminal 500. The short-range wireless communication unit 501 is a communication unit for short-range wireless communication for communication with the entrance/exit roadside unit 200. The communication method may be Bluetooth, wireless LAN, NFC, etc.

The input/output control unit 502 performs input/output processing to receive authentication from the entry/exit management device 400. The input/output control unit 502 transmits input information to the entry/exit management device 400 via the entry/exit roadside unit 200.

Display unit 503 is a video output device such as a CRT display, LCD display, or organic EL display. Display unit 503 may also be an interface for connecting a video output device to mobile terminal 500. In this case, display unit 503 generates a video signal from video data and outputs the video signal to the video output device connected to it.

The input unit 504 is configured using an existing input device such as a touch panel, button, or switch. The input unit 504 may also be an interface for connecting the input device to the mobile terminal 500. In this case, the input unit 504 generates input data from an input signal input to the input device and inputs the data to the mobile terminal 500. The input unit 504 transmits the input signal to the entrance/exit roadside unit 200. Note that if the input unit 504 is configured using a touch panel, the input unit 504 and the display unit 503 may be configured as an integrated unit.

Next, the operation will be explained. Figure 5 is a sequence diagram showing the processing flow of the entry/exit system 1 in the first embodiment. As a preliminary step, the vehicle-mounted device user notifies the vehicle-mounted device ID and mobile terminal ID to the vehicle-mounted device ID matching device 300. The vehicle-mounted device user may also transmit the vehicle-mounted device ID and mobile terminal ID from the vehicle-mounted device 100 to the vehicle-mounted device ID matching device 300. The vehicle-mounted device user may also transmit the vehicle-mounted device ID and mobile terminal ID from the mobile terminal 500 to the vehicle-mounted device ID matching device 300 (step S101). Next, the vehicle-mounted device ID matching device 300 executes a registration process for the received vehicle-mounted device ID and mobile terminal ID. Specifically, the vehicle-mounted device ID matching device 300 registers the vehicle-mounted device ID and mobile terminal ID in association with each other in the vehicle-mounted device ID table 311 (step S102). The vehicle-mounted device ID matching device 300 transmits the mobile terminal ID to the entry/exit management device 400 (step S103). The vehicle-mounted unit user transmits the mobile device PIN that they have determined to the entry/exit management device 400. Alternatively, the vehicle-mounted unit user may transmit the mobile device PIN from the mobile device 500 to the entry/exit management device 400 (step S104). The facility variable PIN generation unit 405 generates the facility variable PIN. The entry/exit management device 400 associates the received mobile device ID, mobile device authentication information, and facility variable authentication information and registers them in the authentication information table 411 (step S105). This completes the advance preparation.

Next, the information control unit 102 acquires the vehicle-mounted device ID from the vehicle-mounted device information storage unit 103 and transmits it to the entry/exit roadside unit 200 via the communication unit 101 (step S201).

The vehicle-mounted device communication unit 201 notifies the communication control unit 205 of the vehicle-mounted device ID. The communication control unit 205 performs encryption processing of the vehicle-mounted device ID using the encryption processing unit 202. The encryption processing unit 202 generates an encrypted vehicle-mounted device ID from the vehicle-mounted device ID (step S202). The communication control unit 205 transmits the encrypted vehicle-mounted device ID to the vehicle-mounted device ID matching device 300 via the IP communication unit 204 (step S203).

The IP communication unit 301 notifies the information control unit 303 of the encrypted vehicle-mounted device ID. The information control unit 303 executes decryption processing of the encrypted vehicle-mounted device ID using the decryption processing unit 304. The decryption processing unit 304 generates an vehicle-mounted device ID from the encrypted vehicle-mounted device ID (step S204). The information control unit 303 identifies an vehicle-mounted device ID record with a matching vehicle-mounted device ID from the vehicle-mounted device ID table 311 in the device information storage unit 302 (step S205). If the vehicle-mounted device ID matches (step S205-YES), the information control unit 303 acquires the value of the mobile terminal ID (step S206). If the vehicle-mounted device ID does not match (step S205-NO), the vehicle-mounted device ID matching device 300 terminates processing (step S207). The information control unit 303 transmits the mobile terminal ID to the entry/exit management device 400 via the IP communication unit 301 (step S208).

The IP communication unit 401 notifies the authentication control unit 402 of the mobile terminal ID. The authentication control unit 402 retrieves the value of the variable facility PIN from the authentication information record in the authentication information table 411 of the authentication information storage unit 403 that matches the mobile terminal ID (step S209). The authentication control unit 402 transmits the value of the variable facility PIN to the vehicle-mounted device 100 via the IP communication unit 401 and the entrance/exit roadside unit 200 (steps S210 to S211).

The information control unit 102 speaks the value of the facility variable PIN via the audio output unit 104. The information control unit 102 displays the value of the facility variable PIN via the display unit 105 (step S212).

The input unit 504 receives verification information input by a person in the vehicle (step S213). The person in the vehicle may be, for example, the in-vehicle device user or the vehicle driver. The input unit 504 notifies the input/output control unit 502 of the verification information. The input/output control unit 502 then transmits the verification information to the entry/exit management device 400 via the short-range wireless communication unit 501 and the entry/exit roadside unit 200 (steps S214 to S215).

The IP communication unit 401 notifies the authentication control unit 402 of the matching information. The authentication control unit 402 then performs authentication processing of the matching information using the authentication processing unit 404. Specifically, the authentication processing unit 404 compares the matching information received from the mobile terminal 500 with the matching information stored in the authentication information record, and if the matching information satisfies predetermined authentication conditions (e.g., matches), the authentication processing unit 404 determines that the on-board device 100 is a device with legitimate authority. On the other hand, if the predetermined conditions are not met (e.g., do not match), the authentication processing unit 404 determines that the on-board device 100 is a device without legitimate authority (step S216). The authentication control unit 402 transmits the authentication processing execution result to the entry/exit roadside unit 200 (step S217).

The IP communication unit 204 notifies the entry/exit control unit 206 of the authentication process execution result. The entry/exit control unit 206 executes processing based on the authentication process execution result (step S218). If the authentication process execution result is successful (step S218-YES), the entry/exit control unit 206 sends an open gate instruction to the entry/exit inhibitor 600 via the entry/exit communication unit 207 (step S219). On the other hand, if the authentication process execution result is not successful (step S218-NO), the entry/exit control unit 206 terminates processing (step S220).

The communication unit 601 notifies the entry/exit control unit 602 of the gate opening instruction. Upon receiving the gate opening instruction, the entry/exit control unit 602 executes the gate opening process of the entry/exit control unit 603 (step S221).

In the processing flow of Figure 5, the matching information acquired in step S213 may be encrypted by the encryption processing unit 202. In such a case, when the matching information is transmitted from the entrance/exit roadside unit 200 to the entrance/exit management device 400 in step S215, it is possible to prevent eavesdropping on the matching information. As a result, more secure entrance/exit management is possible compared to transmitting matching information without encryption.

Second Embodiment
First, an overview of the entry/exit system 2 in the second embodiment will be described. The second embodiment is used when a business operator installs entry/exit roadside devices 200a at two or more locations. For example, when vehicle management is performed within the premises of a construction site or the like, the construction company associates the on-board device 100 with the entry/exit roadside device 200a. Therefore, when there are multiple construction sites, the association process places a significant burden on the construction company. Therefore, the entry/exit system 2 reduces the burden of this association process. Specifically, an on-board device ID, a facility ID, and a mobile terminal ID are associated and registered in the on-board device ID matching device 300a. The facility ID is an identifier that identifies the entry/exit roadside device 200a. The facility ID may be any value that does not overlap with other facility IDs. The facility ID may be, for example, the name of the facility or an arbitrary character string. The on-board device ID matching device 300a identifies the mobile terminal ID using the on-board device ID and facility ID received from the entry/exit roadside device 200a. If at least one of the on-board device ID and the facility ID is different, the vehicle equipped with this on-board device 100 is deemed to be attempting to enter the unauthorized access roadside unit 200a. Therefore, this vehicle is not allowed to enter the construction site. With this configuration, construction companies are no longer required to perform linking for each construction site. This reduces the burden of linking on construction companies.

The entry/exit system 2 will be described in detail below using Figure 6. Figure 6 is a system configuration diagram showing the system configuration of the entry/exit system 2 in the second embodiment. The entry/exit system 2 in the second embodiment differs from the first embodiment in that a facility ID is newly used. Only the differences from the first embodiment will be described below. The entry/exit system 2 differs from the entry/exit system 1 in the first embodiment in that it has an entry/exit roadside device 200a instead of the entry/exit roadside device 200, and an on-board device ID matching device 300a instead of the on-board device ID matching device 300; in all other respects, it has the same configuration as the entry/exit system 1.

Ingress/exit roadside device 200a has an encryption processing unit 202a that performs encryption processing on an in-vehicle device ID and a facility ID, instead of the encryption processing unit 202 that performs encryption processing on an in-vehicle device ID. Ingress/exit roadside device 200a has a communication control unit 205a that controls authentication processing of an in-vehicle device 100 using an in-vehicle device ID and a facility ID, instead of the communication control unit 205 that controls authentication processing of an in-vehicle device 100 using an in-vehicle device ID. In other respects, ingress/exit roadside device 200a has the same configuration as ingress/exit roadside device 200.

Instead of the device information storage unit 302 that stores the vehicle-mounted device ID and the mobile terminal ID, the vehicle-mounted device ID matching device 300a has a device information storage unit 302a that also stores a facility ID. Instead of the information control unit 303 that controls the process of identifying the mobile terminal ID from the vehicle-mounted device ID, the vehicle-mounted device ID matching device 300a has an information control unit 303a that controls the process of identifying the mobile terminal ID from the vehicle-mounted device ID and the facility ID. Instead of the decryption processing unit 304 that performs the decryption process of the encrypted vehicle-mounted device ID, the vehicle-mounted device ID matching device 300a has a decryption processing unit 304a that performs the decryption process of the encrypted vehicle-mounted device ID and the encrypted facility ID. In all other respects, the vehicle-mounted device ID matching device 300a has the same configuration as the vehicle-mounted device ID matching device 300.

The vehicle-mounted device ID table 311a differs from the vehicle-mounted device ID table 311 in the first embodiment in that it additionally has a column for facility IDs, but otherwise has the same configuration as the vehicle-mounted device ID table 311.

In the example shown in Figure 6, the top row of the vehicle-mounted device ID record a in the vehicle-mounted device ID table 311a indicates that when the vehicle-mounted device ID received by the vehicle-mounted device ID matching device 300a is "XXX" and the facility ID is "AAA", the information control unit 303a obtains the mobile terminal ID as "xxx@xxx". Note that the vehicle-mounted device ID table 311a shown in Figure 6 is only one specific example. Therefore, the vehicle-mounted device ID table 311a may be configured in a manner different from that shown in Figure 6. For example, the vehicle-mounted device ID table 311a may register the timestamp when the vehicle-mounted device ID record a was generated.

Figure 7 is a sequence diagram showing the processing flow until an operator links and registers an in-vehicle device ID, facility ID, and mobile terminal ID in the entrance/exit system 2 in the second embodiment. The entrance/exit system 2 is installed with multiple entrance/exit roadside devices 200a. Therefore, the operator decides which entrance/exit roadside device 200a the in-vehicle device user will use for entrance and exit. To do this, the operator uses an in-vehicle device ID usage consent form. The in-vehicle device ID usage consent form indicates which entrance/exit roadside device 200a the in-vehicle device user is allowed to use for entrance and exit. The operator obtains the in-vehicle device user's approval for the in-vehicle device ID usage consent form. The operator then registers the contents of the in-vehicle device ID usage consent form in the in-vehicle device ID matching device 300a. After registration, the in-vehicle device user can enter and exit the entrance/exit roadside device 200a indicated in the in-vehicle device ID usage consent form.

First, the vehicle-mounted device user performs a user registration process for the vehicle-mounted device ID and mobile terminal ID. The user registration process may be performed, for example, on a user registration web page (step S301).

Next, the operator creates an in-vehicle device ID usage consent form. The in-vehicle device ID usage consent form includes the "in-vehicle device user name," "in-vehicle device ID," "license expiration date," "mobile terminal ID," and "facility ID." Note that the items in this in-vehicle device ID usage consent form are only one example. Therefore, an in-vehicle device ID usage consent form may be composed of items different from those in this in-vehicle device ID usage consent form. For example, the in-vehicle device ID usage consent form may include a field for the facility name. The in-vehicle device ID usage consent form may also be an electronic medium such as a web form (step S302).

The operator sends the vehicle-mounted device ID usage consent to the vehicle-mounted device user (step S303). The vehicle-mounted device user executes approval processing for the vehicle-mounted device ID usage consent. Specifically, the approval processing involves the vehicle-mounted device user signing the vehicle-mounted device ID usage consent. The approval processing may also be electronic signature processing. The vehicle-mounted device ID usage consent that has undergone approval processing is designated as an approved vehicle-mounted device ID usage consent (step S304). The vehicle-mounted device user sends the approved vehicle-mounted device ID usage consent to the operator (step S305). The operator transmits the approved vehicle-mounted device ID usage consent to the vehicle-mounted device ID matching device 300a. The operator may also send the approved vehicle-mounted device ID usage consent to the management organization of the vehicle-mounted device ID matching device 300a (step S306).

The vehicle-mounted device ID matching device 300a generates a vehicle-mounted device ID table 311a (step S307). The vehicle-mounted device ID matching device 300a generates a vehicle-mounted device ID record a in which the "vehicle-mounted device ID," "facility ID," and "mobile terminal ID" listed in the approved vehicle-mounted device ID usage consent are registered (step S308).

Figure 8 is a sequence diagram showing the processing flow of the entry/exit system 2 in the second embodiment. First, the information control unit 102 acquires the vehicle-mounted device ID from the vehicle-mounted device information storage unit 103 and transmits it to the entry/exit roadside unit 200a via the communication unit 101 (step S201).

The vehicle-mounted device communication unit 201 notifies the communication control unit 203a of the vehicle-mounted device ID. The communication control unit 205a acquires the facility ID stored in the installer information storage unit 208a. The communication control unit 205a performs encryption processing of the vehicle-mounted device ID and facility ID using the encryption processing unit 202a. The encryption processing unit 202a generates an encrypted vehicle-mounted device ID from the vehicle-mounted device ID. The encryption processing unit 202a generates an encrypted facility ID from the facility ID (step S202a). The communication control unit 205a transmits the encrypted vehicle-mounted device ID and encrypted facility ID to the vehicle-mounted device ID matching device 300a via the IP communication unit 204 (step S203a).

The IP communication unit 301 notifies the information control unit 303a of the encrypted vehicle-mounted device ID and encrypted facility ID. The information control unit 303a performs decryption processing of the encrypted vehicle-mounted device ID and encrypted facility ID using the decryption processing unit 304a. The decryption processing unit 304a generates a vehicle-mounted device ID from the encrypted vehicle-mounted device ID. The decryption processing unit 304a generates a facility ID from the encrypted facility ID (step S204a). The information control unit 303a identifies a vehicle-mounted device ID record from the vehicle-mounted device ID table 311a in the device information storage unit 302a where the vehicle-mounted device ID and facility ID match (step S205a). If the vehicle-mounted device ID and facility ID match (step S205a-YES), the information control unit 303 acquires the value of the mobile terminal ID (step S206). If the vehicle-mounted device IDs do not match (step S205a-NO), the vehicle-mounted device ID matching device 300a terminates processing (step S207). The information control unit 303a transmits the mobile terminal ID to the entry/exit management device 400 via the IP communication unit 301 (step S208).

The IP communication unit 401 notifies the authentication control unit 402 of the mobile terminal ID. The authentication control unit 402 retrieves the value of the variable facility PIN from the authentication information record in the authentication information table 411 of the authentication information storage unit 403 that matches the mobile terminal ID (step S209). The authentication control unit 402 transmits the value of the variable facility PIN to the vehicle-mounted device 100 via the IP communication unit 401 and the entrance/exit roadside unit 200a (steps S210 to S211).

The information control unit 102 speaks the value of the facility variable PIN via the audio output unit 104. The information control unit 102 displays the value of the facility variable PIN via the display unit 105 (step S212).

The input unit 504 receives verification information input by the vehicle occupant (step S213). The input unit 504 notifies the input/output control unit 502 of the verification information. The input/output control unit 502 then transmits the verification information to the entry/exit management device 400 via the short-range wireless communication unit 501 and the entry/exit roadside unit 200a (steps S214 to S215).

The IP communication unit 401 notifies the authentication control unit 402 of the matching information. The authentication control unit 402 then performs authentication processing of the matching information using the authentication processing unit 404. Specifically, the authentication processing unit 404 compares the matching information received from the mobile terminal 500 with the matching information stored in the authentication information record, and if the matching information satisfies predetermined authentication conditions (e.g., matches), the authentication processing unit 404 determines that the on-board device 100 is a device with legitimate authority. On the other hand, if the predetermined conditions are not met (e.g., do not match), the authentication processing unit 404 determines that the on-board device 100 is a device without legitimate authority (step S216). The authentication control unit 402 transmits the authentication result to the entry/exit roadside unit 200a (step S217).

The IP communication unit 204 notifies the entry/exit control unit 206 of the authentication process execution result. The entry/exit control unit 206 executes processing based on the authentication process execution result (step S218). If the authentication process execution result is successful (step S218-YES), the entry/exit control unit 206 sends an open gate instruction to the entry/exit inhibitor 600 via the entry/exit communication unit 207 (step S219). On the other hand, if the authentication process execution result is not successful (step S218-NO), the entry/exit control unit 206 terminates processing (step S220).

The communication unit 601 notifies the entry/exit control unit 602 of the gate opening instruction. Upon receiving the gate opening instruction, the entry/exit control unit 602 executes the gate opening process of the entry/exit control unit 603 (step S221).

(Third embodiment)
First, an outline of the entrance/exit system 3 in the third embodiment will be described. The third embodiment is assumed to be an entrance/exit system that allows entry and exit with a simple configuration without using a mobile terminal 500 in a place such as an apartment parking lot where high security such as identity verification is not required. For this purpose, the following processing is executed.

In the first embodiment, authentication processing was performed using the facility variable PIN and mobile terminal PIN transmitted from the mobile terminal 500, but in the third embodiment, authentication processing is performed using only the mobile terminal ID without using these two pieces of information. Also, in the first embodiment, the mobile terminal ID was transmitted from the mobile terminal 500 to the entry/exit management device 400, but in the third embodiment, it is transmitted from the vehicle-mounted ID matching device 300 to the entry/exit management device 400 without going through the mobile terminal 500. With this configuration, in the third embodiment, it is possible to achieve entry/exit without using the mobile terminal 500.

The entry/exit system 3 will be described in detail below using Figure 9. Figure 9 is a system configuration diagram showing the system configuration of the entry/exit system 3 in the third embodiment. The entry/exit system 3 in the third embodiment differs from the first embodiment in that it does not use a mobile terminal 500. Only the differences from the first embodiment will be described below.

Entry/exit roadside device 200b does not have a terminal communication unit 203. In all other respects, entry/exit roadside device 200b has the same configuration as entry/exit roadside device 200.

The entry/exit management device 400b has an authentication control unit 402b instead of the authentication control unit 402. The entry/exit management device 400b has an authentication information storage unit 403b that stores a mobile terminal ID instead of the authentication information storage unit 403 that stores matching information. The entry/exit management device 400b has an authentication processing unit 404b that performs authentication processing using a mobile terminal ID instead of the authentication processing unit 404 that performs authentication processing using matching information. The entry/exit management device 400b does not have a facility variable PIN generation unit 405. In other respects, the entry/exit management device 400b has the same configuration as the entry/exit management device 400.

The authentication information storage unit 403b stores the authentication information table 411b. The authentication information record b has a mobile device ID. In the example shown in Figure 9, the authentication information record b at the top of the authentication information table 411b has the mobile device ID "xxx@xxx". If the mobile device ID received from the vehicle-mounted device ID matching device 300 is "xxx@xxx", the authentication processing unit 404b determines that authentication has been successful for this authentication information record b. Note that the authentication information table 411b shown in Figure 9 is only one specific example. Therefore, the authentication information table 411b may be configured in a manner different from that shown in Figure 9. For example, the authentication information table 411b may have the date and time when the mobile device ID was registered.

Figure 10 is a sequence diagram showing the processing flow until the use of the vehicle-mounted device ID and mobile terminal ID begins in the entrance/exit system 3 in the third embodiment. First, the vehicle-mounted device user transmits the vehicle-mounted device ID and mobile terminal ID to the vehicle-mounted device ID matching device 300. The transmission may also be via a web page or sent to the management organization of the vehicle-mounted device ID matching device 300 (step S401). Next, the vehicle-mounted device ID matching device 300 executes a registration process for the vehicle-mounted device ID and mobile terminal ID. Specifically, the vehicle-mounted device ID matching device 300 generates a vehicle-mounted device ID record in the vehicle-mounted device ID table. The vehicle-mounted device ID matching device 300 registers the vehicle-mounted device ID and mobile terminal ID in the vehicle-mounted device ID record (step S402).

The vehicle-mounted device user notifies the operator (e.g., a condominium management organization) of the vehicle-mounted device ID and permission to use the vehicle-mounted device ID (step S403). Upon receiving the vehicle-mounted device ID and permission to use the vehicle-mounted device ID, the operator transmits the vehicle-mounted device ID to the vehicle-mounted device ID matching device 300. The transmission may be for each vehicle-mounted device user. The transmission may also be performed collectively after receiving the vehicle-mounted device IDs of all vehicle-mounted device users. The transmission may also be performed from a web page. The transmission may also be sent to the management organization of the vehicle-mounted device ID matching device 300 (step S404). The vehicle-mounted device ID matching device 300 identifies the mobile terminal ID using the vehicle-mounted device ID (step S405). The vehicle-mounted device ID matching device 300 transmits the mobile terminal ID to the entry/exit management device 400b (step S406). The entry/exit management device 400b registers the mobile terminal ID in the authentication information table 411b (step S407). Now, the entry/exit system 3 will begin using the vehicle-mounted device ID and mobile terminal ID.

Figure 11 is a sequence diagram showing the processing flow of the entry/exit system 3 in the third embodiment. First, the information control unit 102 acquires the vehicle-mounted device ID from the vehicle-mounted device information storage unit 103 and transmits it to the entry/exit roadside unit 200b via the communication unit 101 (step S201).

The vehicle-mounted device communication unit 201 notifies the communication control unit 205 of the vehicle-mounted device ID. The communication control unit 205 performs encryption processing of the vehicle-mounted device ID using the encryption processing unit 202. The encryption processing unit 202 generates an encrypted vehicle-mounted device ID from the vehicle-mounted device ID (step S202). The communication control unit 205 transmits the encrypted vehicle-mounted device ID to the vehicle-mounted device ID matching device 300 via the IP communication unit 204 (step S203).

The IP communication unit 301 notifies the information control unit 303 of the encrypted vehicle-mounted device ID. The information control unit 303 executes decryption processing of the encrypted vehicle-mounted device ID using the decryption processing unit 304. The decryption processing unit 304 generates an vehicle-mounted device ID from the encrypted vehicle-mounted device ID (step S204). The information control unit 303 identifies an vehicle-mounted device ID record with a matching vehicle-mounted device ID from the vehicle-mounted device ID table 311 in the device information storage unit 302 (step S205). If the vehicle-mounted device IDs match (step S205-YES), the information control unit 303 acquires the value of the mobile terminal ID (step S206). If the vehicle-mounted device IDs do not match (step S205-NO), the vehicle-mounted device ID matching device 300 terminates processing (step S207). The information control unit 303 transmits the mobile terminal ID to the entry/exit management device 400b via the IP communication unit 301 (step S208).

The IP communication unit 401 notifies the authentication control unit 402b of the mobile terminal ID. The authentication control unit 402b causes the authentication processing unit 404b to perform authentication processing of the mobile terminal ID. Specifically, the authentication processing unit 404b compares the mobile terminal ID received from the vehicle-mounted device ID matching device 300 with the mobile terminal ID registered in the authentication information record b. If the predetermined authentication conditions are met (e.g., they match), the authentication processing unit 404b determines that the vehicle-mounted device 100 is a device with legitimate authority. On the other hand, if the predetermined conditions are not met (e.g., they do not match), the authentication processing unit 404b determines that the vehicle-mounted device 100 is a device without legitimate authority (step S216b). The authentication control unit 402b transmits the authentication processing execution result to the entry/exit roadside unit 200 (step S217).

The IP communication unit 204 notifies the entry/exit control unit 206 of the authentication process execution result. The entry/exit control unit 206 executes processing based on the authentication process execution result (step S218). If the authentication process execution result is successful (step S218-YES), the entry/exit control unit 206 sends an open gate instruction to the entry/exit inhibitor 600 via the entry/exit communication unit 207 (step S219). On the other hand, if the authentication process execution result is not successful (step S218-NO), the entry/exit control unit 206 terminates processing (step S220).

The communication unit 601 notifies the entry/exit control unit 602 of the gate opening instruction. Upon receiving the gate opening instruction, the entry/exit control unit 602 executes the gate opening process of the entry/exit control unit 603 (step S221).

According to at least one of the embodiments described above, by having an authentication processing function for authentication information and mobile device ID, it is possible to identify people inside the vehicle with greater accuracy.

While several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments may be embodied in a variety of other forms, and various omissions, substitutions, and modifications may be made without departing from the spirit of the invention. These embodiments and their variations are within the scope of the invention and its equivalents as defined in the claims, as well as the scope and spirit of the invention.

1...Entry/Exit System, 2...Entry/Exit System, 3...Entry/Exit System, 10...Facility, 100...In-Vehicle Device, 101...Communication Unit, 102...Information Control Unit, 103...In-Vehicle Device Information Storage Unit, 104...Audio Output Unit, 105...Display Unit, 106...Card Input/Output Unit, 107...Card, 200...Entry/Exit Roadside Device, 201...In-Vehicle Device Communication Unit, 202...Encryption Processing Unit, 203...Terminal Communication Unit, 2 04...IP communication unit, 205...communication control unit, 206...entrance/exit control unit, 207...entrance/exit communication unit, 300...vehicle-mounted device ID matching device, 301...IP communication unit, 302...device information storage unit, 303...information control unit, 304...decryption processing unit, 311...vehicle-mounted device ID table, 400...entrance/exit management device, 401...IP communication unit, 402...authentication control unit, 403...authentication information storage unit, 404 ...Authentication processing unit, 405...Facility variable password generation unit, 411...Authentication information table, 500...Mobile terminal, 501...Short-range wireless communication unit, 502...Input/output control unit, 503...Display unit, 504...Input unit, 600...Entry/exit control unit, 601...Communication unit, 602...Entry/exit control unit, 603...Entry/exit control unit, 200a...Entry/exit roadside device, 202a...Encryption processing unit, 205a...Communication control unit, 208a...Installer information storage unit, 300a...Vehicle-mounted device ID matching unit, 302a...Device information storage unit, 303a...Information control unit, 304a...Decryption processing unit, 311a...Vehicle-mounted device ID table, 200b...Entry/exit roadside device, 400b...Entry/exit management device, 402b...Authentication control unit, 403b...Authentication information storage unit, 404b...Authentication processing unit, 411b...Authentication information table

Claims (9)

a device information storage unit that stores a record in which an in-vehicle device ID, which is identification information of the in-vehicle device, is associated with user information that can uniquely identify a user of the in-vehicle device;
a communication unit that receives, from an access roadside device provided near a facility to be managed, information indicating an on-board device ID that the access roadside device has received from an on-board device of a vehicle;
an acquisition unit that acquires the user information related to a record stored in the device information storage unit when the record matches the vehicle-mounted device ID indicated by the received information;
a terminal communication unit provided near a facility to be managed, and an authentication processing unit configured to receive matching information acquired from the user's mobile terminal near the terminal communication unit , and to perform authentication processing based on the acquired user information and the received matching information. The user identification system according to claim 1 , wherein the verification information is information for identifying the user by verifying it with the user information. The user identification system of claim 1, wherein the verification information includes a password that is generated periodically. The user identification system described in claim 1, wherein the verification information includes a password preset by the user. The record stored in the device information storage unit further includes a facility ID of the facility to be managed,
The user identification system according to claim 1 , wherein the communication unit receives the facility ID. the communication unit receives the encrypted vehicle-mounted device ID as information indicating the vehicle-mounted device ID,
The user identification system according to any one of claims 1 to 5, wherein the acquisition unit decrypts the encrypted vehicle-mounted device ID, and if a record matching the vehicle-mounted device ID obtained by decryption is stored in the device information storage unit, acquires the user information related to the record. A user identification system as described in any one of claims 1 to 6, comprising an entry/exit control unit that determines whether to open or close an entry/exit control unit that prevents entry into or exit from the managed facility based on the results of the authentication process. The user identification system of claim 7, wherein the entry/exit control unit does not open the entry/exit restriction unit if a record matching the vehicle-mounted device ID indicated by the received information is not stored in the device information storage unit. A user identification method performed by a user identification system including a device information storage unit that stores a record associating an on-board device ID, which is identification information of an on-board device, with user information that can uniquely identify a user of the on-board device, and one or more information processing devices,
a receiving step in which the information processing device receives, from an access roadside device provided near a facility to be managed, information indicating an on-board device ID received by the access roadside device from an on-board device of a vehicle;
an information acquisition step of the information processing device acquiring the user information related to a record stored in the device information storage unit when the record matches the vehicle-mounted device ID indicated by the received information;
and an authentication processing step in which the information processing device receives, from a terminal communication unit provided near the facility to be managed, matching information acquired from the user's mobile terminal near the terminal communication unit , and performs authentication processing based on the acquired user information and the received matching information.