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

Description

An embodiment of the present invention relates to an entry/exit system and an entry/exit control method.

Conventionally, there has been a system for controlling the opening/closing of an entry/exit restraint unit in an apartment building or commercial facility by using an on-vehicle device ID transmitted from an ETC on-board device. However, since the vehicle-mounted device ID transmitted from the vehicle-mounted device is an ID associated with the vehicle, it is not possible to accurately identify a person in the vehicle. Therefore, in places where high security is required, there are cases where the above system cannot be utilized.

JP-A-2005-227996 JP 2009-294310 A

"Mansion parking lot (Mansion ETC system)", [online], [searched May 24, 2016], Internet <URL: http://www.furuno.com/jp/dsrc/case/enter_leave/>

A problem to be solved by the present invention is to provide a user identification system and a user identification method that can identify persons in the vehicle with higher accuracy.

A user identification system of an embodiment has an onboard device ID verification device and a management device. The vehicle-mounted device ID verification device has a device information storage unit, a communication unit, an acquisition unit, and an information control unit. The device information storage unit stores a record in which a vehicle-mounted device ID, which is identification information of a vehicle-mounted device, is associated with a mobile terminal ID of a mobile terminal possessed by a user of the vehicle-mounted device. The communication unit receives, from a roadside device provided near a facility to be managed, information indicating an onboard device ID received by the roadside device from the onboard device of the vehicle. The acquisition unit acquires the mobile terminal ID related to the record when a record matching the vehicle-mounted device ID indicated by the received information is stored in the device information storage unit. The information control unit transmits the acquired mobile terminal ID to the management device. The management device has an authentication processing unit. The authentication processing unit executes authentication processing based on the mobile terminal ID received from the vehicle-mounted device ID matching device.

Schematic which shows the specific example of application of the entry/exit system 1 of 1st embodiment. 1 is a system configuration diagram showing a system configuration of an entry/exit system 1; FIG. 2 is a schematic block diagram showing the functional configuration of the vehicle-mounted device 100; FIG. FIG. 5 is a schematic block diagram showing the functional configuration of a mobile terminal 500; The sequence diagram showing the flow of processing of the entry/exit system 1 in 1st embodiment. The system block diagram showing the system configuration|structure of the entry/exit system 2 of 2nd embodiment. The sequence diagram showing the flow of processing until a business operator links|links and registers vehicle-mounted device ID, facility ID, and portable terminal ID in the entrance/exit system 2 in 2nd embodiment. The sequence diagram showing the flow of processing of the entrance/exit system 2 in 2nd embodiment. The system block diagram showing the system configuration|structure of the entry/exit system 3 in 3rd embodiment. The sequence diagram showing the flow of processing until use of vehicle-mounted device ID and portable terminal ID is started in the entrance/exit system 3 in 3rd embodiment. The sequence diagram showing the flow of processing of the entry/exit system 3 in the third embodiment.

An entry/exit system and an entry/exit control method according to embodiments will be described below with reference to the drawings.

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

The vehicle-mounted device ID verification device 300 is, for example, a dedicated information processing device or the like managed by an affiliated organization such as the government. The entrance/exit management device 400 is an information processing device that stores an authentication information table that associates mobile terminal IDs, facility variable password information, and non-updated mobile terminal password information preset by the user of the vehicle-mounted device. Here, the mobile terminal ID is identification information of the mobile terminal 500 . The mobile terminal ID may be any value as long as it does not overlap with other mobile terminal IDs. The mobile terminal ID may be, for example, an e-mail address, serial number, MAC address, or the like. The mobile terminal password information is information stored in the authentication information table in advance by the user of the vehicle-mounted device. The facility variable password information is password information periodically generated by the entrance/exit management device 400 . The facility variable personal identification information is information that is changed in a short cycle such as every day. Therefore, the facility variable personal identification information is information that even a person who gets into the vehicle cannot know until it is notified. A combination of the facility variable password information, mobile terminal password information and mobile terminal ID is hereinafter referred to as "verification information".

The vehicle-mounted device 100 is a vehicle-mounted device for receiving an automatic toll collection service by ETC. The vehicle-mounted device ID is set when the vehicle-mounted device 100 is attached to the vehicle. The mobile terminal 500 is a terminal capable of short-range wireless communication, middle-range wireless communication, or the like. The mobile terminal 500 is specifically a portable terminal such as a smart phone or a tablet.

In the entrance/exit system 1 configured as described above, authentication is performed not only by the vehicle-mounted device ID, which is the identification information of the vehicle-mounted device 100, but also by using the facility variable password information or the mobile terminal password information. Therefore, it is possible to authenticate a person who is actually in the vehicle, and to identify the person in the vehicle with higher accuracy. In addition, in the entrance/exit system 1 configured in this way, authentication by the entrance/exit management device 400 cannot be performed unless the vehicle-mounted device 100 and the mobile terminal 500 are near the entrance/exit roadside device 200 . Therefore, it is possible to prevent the mobile terminal 500 from being operated by a person away from the vehicle. This also makes it possible to identify a person in the vehicle with higher accuracy.

In addition, since the vehicle-mounted device ID is very important information, it must be strictly managed. Therefore, it is desirable that the vehicle-mounted device ID verification device 300 having a table in which vehicle-mounted device IDs are registered is managed by a strict organization. For example, the vehicle-mounted device ID verification device 300 may be configured by a server device operated by a public organization such as an affiliated organization.
On the other hand, verification information including a mobile terminal ID (e.g., e-mail address) is personal information and is important information. It is desirable to be registered and updated. Therefore, the verification information is managed by the entrance/exit management device 400 . In the entrance/exit system 1 described above, the vehicle-mounted device ID and the mobile terminal ID are associated and managed in the vehicle-mounted device ID verification device 300 , and the mobile terminal ID is transmitted to the entrance/exit management device 400 . That is, the vehicle-mounted device ID is not transmitted to the entrance/exit management device 400 . With such a configuration, it is possible to manage the vehicle-mounted device ID more strictly and maintain security.

Next, each component constituting the entrance/exit system 1 will be described with reference to a configuration diagram. FIG. 2 is a system configuration diagram showing the system configuration of the entrance/exit system 1. As shown in FIG.
The entrance/exit roadside device 200 includes a vehicle-mounted device communication unit 201 , an encryption processing unit 202 , an IP communication unit 204 , a terminal communication unit 203 , a communication control unit 205 , an entrance/exit control unit 206 and an entrance/exit communication unit 207 . The entrance/exit roadside device 200 includes a plurality of network interfaces, a CPU (Central Processing Unit) connected via a bus, a memory, an auxiliary storage device, and the like. All or part of each function of the entrance/exit 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 entrance/exit 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 . The wireless communication may be, for example, DSRC (Dedicated Short Range Communication) used as a conventional ETC system or ETC2.0 system.

The encryption processing unit 202 executes encryption processing of the vehicle-mounted device ID to generate an encrypted vehicle-mounted device ID.

The terminal communication unit 203 is a network interface for the entrance/exit roadside device 200 to communicate with the mobile terminal 500 . For wireless communication, for example, a short-range wireless communication system is desirable in order to prevent communication from a long distance. Wireless communication may be, for example, wireless LAN (Wifi), BlueTooth (registered trademark), and NFC (Near Field Communication).

The IP communication unit 204 is a network interface for the entrance/exit roadside device 200 to communicate. The IP communication unit 204 communicates with the vehicle-mounted device ID verification device 300 via the network 700 to inquire about the mobile terminal ID.

The communication control unit 205 controls execution of authentication processing of the entrance/exit roadside device 200 when a vehicle equipped with the vehicle-mounted device 100 intrudes into the entrance/exit system 1 .

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

The entrance/exit communication unit 207 is a network interface for the entrance/exit roadside device 200 to communicate with the entrance/exit suppressor 600 . The entrance/exit communication unit 207 communicates with the entrance/exit suppressor 600 . The communication method may be, for example, wired communication. The communication method may be, for example, wireless communication such as BlueTooth or wireless LAN.

The entry/exit restraint device 600 is a device that prevents a vehicle from actually entering. Specifically, the entrance/exit suppressor 600 is configured by a barrier, a shutter, and the like. The entry/exit suppressor 600 includes a communication section 601 , an entry/exit control section 602 and an entry/exit suppression section 603 .

The communication unit 601 is an interface unit that communicates with the entrance/exit roadside device 200, and may use any communication method such as BlueTooth, wireless LAN, or wired LAN.

The entrance/exit control unit 602 notifies the entrance/exit control unit 603 of the gate opening instruction based on the gate opening instruction from the entrance/exit roadside device 200 . The entry/exit control unit 602 notifies the entry/exit control unit 603 of the gate closing instruction after a predetermined period of time has elapsed after notifying the entry/exit control unit 602 of the gate opening instruction. In addition, the entry/exit control unit 602 may notify the entry/exit suppression unit 603 of the gate closing instruction after the vehicle-mounted device 100 has passed through the entry/exit suppression unit 603 that has opened.

The entrance/exit suppression unit 603 opens the entrance/exit suppression unit 603 upon receiving the gate opening instruction from the entrance/exit control unit 602 . Further, the entrance/exit suppression unit 603 closes when receiving a gate closing instruction from the entrance/exit control unit 602 . Also, the entering/leaving control unit 603 may have different entry and exit sections.

The vehicle-mounted device ID verification device 300 includes an IP communication unit 301 , a device information storage unit 302 , an information control unit 303 and a decoding 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 verification device 300 can be any device as long as it can have the functions described below. The vehicle-mounted device ID collation device 300 includes a network interface, a CPU connected by a bus, a memory, an auxiliary storage device, and the like. All or part of each function of the vehicle-mounted device ID verification device 300 may be implemented using hardware such as ASIC, PLD, and FPGA.

The IP communication unit 301 is a network interface for the vehicle-mounted device ID verification device 300 to communicate. The IP communication unit 301 communicates with the entrance/exit roadside device 200 and the entrance/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 device or a semiconductor storage device. The device information storage unit 302 stores an onboard device ID table 311 . The vehicle-mounted device ID record has the values of the vehicle-mounted device ID and the mobile terminal ID, as shown in FIG.

In the example shown in FIG. 2, the vehicle-mounted device ID record at the top of the vehicle-mounted device ID table 311 has a vehicle-mounted device ID of "XXX" and a mobile terminal ID of "xxx@xxx". This onboard device ID record indicates that when the onboard device ID received by the onboard device ID verification device 300 is "XXX", the information control unit 303 acquires the portable terminal ID "xxx@xxx". Note that the vehicle-mounted device ID table 311 shown in FIG. 2 is merely a specific example. Therefore, the vehicle-mounted device ID table 311 may be configured in a manner different from that in FIG.

The information control unit 303 causes the decryption processing unit 304 to decrypt the encrypted vehicle-mounted device ID. The information control unit 303 acquires a mobile terminal ID stored in a record whose vehicle-mounted device ID satisfies (for example, matches) a predetermined requirement from the vehicle-mounted device ID table 311 of the device information storage unit 302 . The information control unit 303 transmits the mobile terminal ID to the entrance/exit management device 400 .

The decryption processing unit 304 executes decryption processing of the encrypted vehicle-mounted device ID. The decoding processing unit 304 notifies the information control unit 303 of the decoded vehicle-mounted device ID.

The entrance/exit management device 400 includes 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 information generation unit 405 . The entrance/exit management device 400 is configured using an information processing device such as a network device, a mainframe, a workstation, or a personal computer. The entrance/exit management device 400 can be any device as long as it can have the following functions. The entrance/exit management device 400 includes a network interface, a CPU connected via a bus, a memory, an auxiliary storage device, and the like. All or part of each function of the entrance/exit management apparatus 400 may be implemented using hardware such as ASIC, PLD, and FPGA.

The IP communication unit 401 is a network interface for the entrance/exit management device 400 to communicate. The IP communication unit 401 communicates with the entrance/exit roadside device 200 and the vehicle-mounted device ID verification 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 acquires the facility variable password information 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 verification information in the authentication processing unit 404 . The authentication control unit 402 transmits the authentication processing execution result of the authentication processing unit 404 to the entrance/exit roadside device 200 .

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

As shown in FIG. 2, the authentication information table 411 has verification information for each authentication information record. The facility variable password information is authentication information periodically generated by the facility variable password information generation unit 405 . The facility variable password information may be, for example, a character string including numbers and alphabets. The mobile terminal password information is authentication information registered in advance 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 password information may be any information that can be used as existing authentication information, such as a character string including numbers and alphabets, a combination of pictures, and a pattern of lines. The mobile terminal password information may be, for example, biometric information such as a fingerprint or face. The mobile terminal personal identification information may 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", facility variable password information of "QQQQ", and mobile terminal password information of "RRRR". If the mobile terminal ID is "xxx@xxx", the facility variable password information is "QQQQ", and the mobile terminal password information is "RRRR" among the authentication information received by the entrance/exit management device 400, this authentication information record is The authentication processing unit 404 determines that the authentication has succeeded. Note that the authentication information table 411 shown in FIG. 2 is merely a specific example. Therefore, the authentication information table 411 may be configured in a manner different from that in FIG. For example, the authentication information table 411 may have the date and time when the mobile terminal password information was updated.

The authentication processing unit 404 executes authentication processing based on the verification information received by the entrance/exit management device 400 and the authentication information record stored in the authentication information storage unit 403 . Specifically, when the verification information received by the entrance/exit management device 400 and the authentication information record stored in the authentication information storage unit 403 satisfy a predetermined authentication condition (for example, they match), the authentication processing unit 404 determines the vehicle-mounted device. 100 is determined to be an authorized device. On the other hand, if the verification information received by the entrance/exit management device 400 and the authentication information record stored in the authentication information storage unit 403 do not satisfy a predetermined authentication condition (for example, they do not match), the authentication processing unit 404 confirms that the vehicle-mounted device 100 It is determined that the device does not have proper authority.

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

The network 700 connects the entrance/exit roadside device 200, the vehicle-mounted device ID verification device 300, and the entrance/exit management device 400 so as to be able to communicate with each other. Network 700 may comprise, for example, the Internet.

FIG. 3 is a schematic block diagram showing the functional configuration of the vehicle-mounted device 100. As shown in FIG. The vehicle-mounted device 100 is configured using an ETC vehicle-mounted device mounted on a vehicle. The vehicle-mounted device 100 includes a network interface, a CPU, a memory, an auxiliary storage device, and the like connected via a bus. The vehicle-mounted device 100 functions as a device including a communication unit 101, an information control unit 102, a vehicle-mounted device information storage unit 103, an audio output unit 104, a display unit 105, and a card input/output unit 106 by executing an authentication program. All or part of each function of the vehicle-mounted device 100 may be implemented using hardware such as ASIC, PLD, and FPGA. The authentication program may be recorded on a computer-readable recording medium. Computer-readable recording media include portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and semiconductor storage devices, and storage devices such as hard disks and semiconductor storage devices incorporated in computer systems. The vehicle-mounted device 100 may be configured using a vehicle-mounted device such as a car navigation device or an audio device mounted on the vehicle.

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 entrance/exit roadside device 200 . For communication, for example, the communication scheme may be DSRC.

The information control unit 102 controls execution of authentication processing of the vehicle-mounted device 100 . The vehicle-mounted device ID is acquired from the vehicle-mounted device information storage unit 103 and transmitted to the vehicle-mounted device ID verification device 300 via the entrance/exit roadside device 200 . The information control unit 102 notifies the voice output unit 104 of the facility variable password information received from the entrance/exit roadside device 200 . The information control unit 102 notifies the display unit 105 of the facility variable password information received from the entrance/exit roadside device 200 . The vehicle-mounted device ID is identification information of the vehicle-mounted device of the vehicle that has entered the entrance/exit system. The vehicle-mounted device ID may be any value as long as it 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 the 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 device 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 existing audio output devices such as speakers, earphones, and headphones. The audio output unit 104 may be an interface for connecting an audio output device to the vehicle-mounted 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 thereto.

A display unit 105 is a video output device such as a CRT (Cathode Ray Tube) display, a liquid crystal display, an organic EL (Electro Luminescence) display, or the like. The display unit 105 may 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 thereto.

The card input/output unit 106 has a card slot into which the 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 the example of FIG. 3 shows a configuration in which the card input/output unit 106 has one card slot into which one card 107 is inserted. However, a configuration different from that in FIG. 3 may be used. For example, the card input/output unit 106 may have two or more card slots.

A card 107 is a card for performing toll settlement using the ETC system. The card 107 is used by inserting it into a card slot provided in the card input/output unit 106 . The information recorded on the card 107 includes identification information unique to each card 107, an organization that issues the card 107 (specifically, a credit card company or an organization affiliated with the credit card company, etc.) Type information indicating the service provided to the user is recorded in advance. In addition to the card information, the card 107 records information on the entrance tollgate where the user started using the road and information on the exit tollgate where the user finished using the road.

FIG. 4 is a schematic block diagram showing the functional configuration of mobile terminal 500. As shown in FIG. The mobile terminal 500 is configured using an information processing device such as a tablet computer, a personal computer, or a smart phone. 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, a memory, an auxiliary storage device, and the like connected via a bus. The mobile terminal 500 is possessed by, for example, a person who gets on the vehicle.

A short-range wireless communication unit 501 is a network interface for the mobile terminal 500 to communicate. The short-range wireless communication unit 501 is a short-range wireless communication unit for communicating with the entrance/exit roadside device 200 . The communication method may be BlueTooth, wireless LANS, NFC, or the like.

The input/output control unit 502 executes input/output processing for receiving authentication by the entrance/exit management device 400 . The input/output control unit 502 transmits input information to the entrance/exit management device 400 via the entrance/exit roadside device 200 .

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

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

Next, the operation will be explained. FIG. 5 is a sequence diagram showing the flow of processing of the entrance/exit system 1 in the first embodiment. As a preparation, the user of the vehicle-mounted device notifies the vehicle-mounted device ID verification device 300 of the vehicle-mounted device ID and the portable terminal ID. Moreover, the vehicle-mounted device user may transmit the vehicle-mounted device ID and the portable terminal ID from the vehicle-mounted device 100 to the vehicle-mounted device ID verification device 300 . Moreover, the onboard equipment user may transmit onboard equipment ID and portable terminal ID from the portable terminal 500 to the onboard equipment ID collation apparatus 300 (step S101). Next, the vehicle-mounted device ID collation apparatus 300 performs registration processing of the received vehicle-mounted device ID and portable terminal ID. Specifically, the vehicle-mounted device ID verification device 300 associates and registers the vehicle-mounted device ID and the mobile terminal ID in the vehicle-mounted device ID table 311 (step S102). The vehicle-mounted device ID verification device 300 transmits the mobile terminal ID to the entrance/exit management device 400 (step S103). The vehicle-mounted device user transmits the mobile terminal password information determined by himself to the entrance/exit management device 400 . Further, the user of the vehicle-mounted device may transmit the mobile terminal password information from the mobile terminal 500 to the entrance/exit management device 400 (step S104). The facility variable password information generation unit 405 generates facility variable password information. The entrance/exit management device 400 associates and registers the received mobile terminal ID, mobile terminal authentication information, and facility variable authentication information 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 entrance/exit roadside device 200 via the communication unit 101 (step S201).

The vehicle-mounted device communication unit 201 notifies the vehicle-mounted device ID to the communication control unit 205 . The communication control unit 205 executes encryption processing of the vehicle-mounted device ID in 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 verification 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 causes the decryption processing unit 304 to decrypt the encrypted vehicle-mounted device ID. The decryption processing unit 304 generates a vehicle-mounted device ID from the encrypted vehicle-mounted device ID (step S204). The information control unit 303 identifies a vehicle-mounted device ID record with a matching vehicle-mounted device ID from the vehicle-mounted device ID table 311 of 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 onboard device IDs do not match (step S205-NO), the onboard device ID verification device 300 terminates the process (step S207). The information control unit 303 transmits the mobile terminal ID to the entrance/exit management device 400 via the IP communication unit 301 (step S208).

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

The information control unit 102 utters the value of the facility variable password information via the voice output unit 104 . The information control unit 102 displays the value of the facility variable password information via the display unit 105 (step S212).

The input unit 504 is operated by a person riding in the vehicle to input verification information (step S213). The people in the vehicle are, for example, the user of the vehicle-mounted device, the driver of the vehicle, and the like. The input unit 504 notifies the input/output control unit 502 of the collation information. The input/output control unit 502 transmits verification information to the entrance/exit management device 400 via the short-range wireless communication unit 501 and the entrance/exit roadside device 200 (steps S214 to S215).

IP communication section 401 notifies authentication control section 402 of the verification information. The authentication control unit 402 performs authentication processing of verification information in the authentication processing unit 404 . Specifically, the authentication processing unit 404 compares the verification information received from the mobile terminal 500 and the verification information stored in the authentication information record, and if a predetermined authentication condition is satisfied (for example, they match), the authentication processing is performed. The unit 404 determines that the vehicle-mounted device 100 is an authorized device. On the other hand, if the predetermined condition is not met (for example, they do not match), the authentication processing unit 404 determines that the vehicle-mounted device 100 is an unauthorized device (step S216). The authentication control unit 402 transmits the execution result of authentication processing to the entrance/exit roadside device 200 (step S217).

The IP communication unit 204 notifies the entrance/exit control unit 206 of the authentication processing execution result. The entrance/exit control unit 206 executes processing based on the authentication processing execution result (step S218). If the authentication processing execution result is authentication success (step S218-YES), the entrance/exit control unit 206 transmits a gate opening instruction to the entrance/exit suppressor 600 via the entrance/exit communication unit 207 (step S219). On the other hand, if the authentication processing execution result is not authentication success (step S218-NO), the entrance/exit control unit 206 ends the processing (step S220).

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

In the process flow of FIG. 5, the encryption processing unit 202 may perform encryption processing on the collation information acquired in step S213. In such a case, when verification information is transmitted from the entrance/exit roadside device 200 to the entrance/exit management device 400 in step S215, wiretapping of the verification information can be prevented. As a result, entrance/exit management can be performed with a higher degree of security than when verification information is transmitted without performing encryption processing.

(Second embodiment)
First, the outline of the entrance/exit system 2 in the second embodiment will be described. The second embodiment is used when a business operator installs the entrance/exit roadside devices 200a at two or more locations. For example, when vehicle management is performed on the premises of a construction site or the like, the construction company performs linking between the vehicle-mounted device 100 and the entrance/exit roadside device 200a. Therefore, when there are multiple construction sites, linking becomes a heavy burden on the construction business operator. Therefore, the entrance/exit system 2 reduces the burden of this linkage. Specifically, the vehicle-mounted device ID, the facility ID, and the portable terminal ID are associated and registered in the vehicle-mounted device ID verification device 300a. The facility ID is an identifier that identifies the entrance/exit roadside device 200a. The facility ID may be any value as long as it 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 vehicle-mounted device ID verification device 300a identifies the mobile terminal ID using the vehicle-mounted device ID and the facility ID received from the entrance/exit roadside device 200a. If at least one of the vehicle-mounted device ID and the facility ID is different, it is assumed that the vehicle equipped with this vehicle-mounted device 100 is attempting to enter the unauthorized entry/exit roadside device 200a. Therefore, this vehicle cannot enter the construction site. With such a configuration, the construction company does not need to deal with linking for each construction site. Therefore, the burden of linking correspondence on the construction business operator is reduced.

The entry/exit system 2 will be described in detail below with reference to FIG. FIG. 6 is a system configuration diagram showing the system configuration of the entry/exit system 2 in the second embodiment. The entrance/exit system 2 in the second embodiment differs from the first embodiment in that facility IDs are newly used. Only points different from the first embodiment will be described below. The entry/exit system 2 has an entry/exit roadside device 200a instead of the entry/exit roadside device 200, and a vehicle-mounted device ID verification device 300a instead of the vehicle-mounted device ID verification device 300 in the first embodiment. Unlike the entrance/exit system 1, it has the same configuration as the entrance/exit system 1 in other respects.

The entrance/exit roadside device 200a includes an encryption processing unit 202a that executes encryption processing on the vehicle-mounted device ID and the facility ID, instead of the encryption processing unit 202 that executes encryption processing on the vehicle-mounted device ID. The entrance/exit roadside device 200a uses a vehicle-mounted device ID and a facility ID to control the authentication processing of the vehicle-mounted device 100 instead of the communication control unit 205 that controls the authentication processing of the vehicle-mounted device 100 using the vehicle-mounted device ID. 205a. The entrance/exit roadside device 200a further includes an installer information storage unit 208a that stores the facility ID. The entrance/exit roadside device 200a has the same configuration as the entrance/exit roadside device 200 in other respects.

The vehicle-mounted device ID verification device 300a includes a device information storage unit 302a that stores facility IDs instead of the device information storage unit 302 that stores vehicle-mounted device IDs and mobile terminal IDs. The vehicle-mounted device ID verification device 300a replaces the information control unit 303 that controls the processing of identifying the mobile terminal ID from the vehicle-mounted device ID with an information control unit 303a that controls the processing of identifying the mobile terminal ID from the vehicle-mounted device ID and the facility ID. Prepare. The vehicle-mounted device ID collation device 300a includes a decryption processing unit 304a that performs decryption processing of the encrypted vehicle-mounted device ID and the encrypted facility ID instead of the decryption processing unit 304 that performs the decryption processing of the encrypted vehicle-mounted device ID. Prepare. The vehicle-mounted device ID verification device 300a has the same configuration as the vehicle-mounted device ID verification device 300 in other respects.

The vehicle-mounted device ID table 311a differs from the vehicle-mounted device ID table 311 in the first embodiment in that it further has a facility ID column.

In the example shown in FIG. 6, the vehicle-mounted device ID record a at the top of the vehicle-mounted device ID table 311a is when the vehicle-mounted device ID received by the vehicle-mounted device ID verification device 300a is "XXX" and the facility ID is "AAA". , the information control unit 303a acquires "xxx@xxx" as the mobile terminal ID. Note that the vehicle-mounted device ID table 311a shown in FIG. 6 is merely a specific example. Therefore, the vehicle-mounted device ID table 311a may be configured in a manner different from that in FIG. For example, the vehicle-mounted device ID table 311a may register the time stamp at which the vehicle-mounted device ID record a was generated.

FIG. 7 is a sequence diagram showing the flow of processing until the business operator links and registers the vehicle-mounted device ID, the facility ID, and the mobile terminal ID in the entry/exit system 2 according to the second embodiment. In the entrance/exit system 2, a plurality of entrance/exit roadside devices 200a are installed. Therefore, the operator determines which entrance/exit roadside device 200a the user of the vehicle-mounted device enters/exits. Therefore, the business operator uses the onboard device ID usage consent form. The onboard unit ID usage consent form indicates which entry/exit roadside device 200a the onboard unit user can enter/exit from. The operator obtains the OBE user's approval for the OBE ID usage consent form. After that, the operator registers the content of the onboard device ID usage consent form in the onboard device ID verification device 300a. After registration, the user of the vehicle-mounted device can enter/exit the entrance/exit roadside device 200a indicated in the vehicle-mounted device ID usage agreement.

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

Next, the operator prepares an on-vehicle device ID usage consent form. The onboard unit ID usage consent form includes the “onboard unit user name”, “onboard unit ID”, “licensing period”, “portable terminal ID”, and “facility ID”. It should be noted that the items of this vehicle-mounted device ID usage consent form are only one specific example. Therefore, the vehicle-mounted device ID usage consent form may be composed of items different from the vehicle-mounted device ID usage consent form. For example, the vehicle-mounted device ID usage consent form may have an item of facility name. Also, the onboard device ID usage consent form may be an electronic medium such as a web form (step S302).

The operator sends the vehicle-mounted device ID usage consent form to the vehicle-mounted device user (step S303). The vehicle-mounted device user executes approval processing of the vehicle-mounted device ID usage consent form. Approval processing is, specifically, the user of the vehicle-mounted device signs the vehicle-mounted device ID usage consent form. Also, the approval process may be an electronic signature. The vehicle-mounted device ID use consent form for which the approval process has been executed is used as the approved vehicle-mounted device ID use consent form (step S304). The vehicle-mounted device user sends an approved vehicle-mounted device ID usage agreement to the business operator (step S305). The operator transmits the consent for use of the approved vehicle-mounted device ID to the vehicle-mounted device ID verification device 300a. In addition, the business operator may send the approved vehicle-mounted device ID usage consent form to the management organization of the vehicle-mounted device ID verification device 300a (step S306).

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

FIG. 8 is a sequence diagram showing the flow of processing of the entrance/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 entrance/exit roadside device 200a via the communication unit 101 (step S201).

The vehicle-mounted device communication unit 201 notifies the vehicle-mounted device ID to the communication control unit 203a. The communication control unit 205a acquires the facility ID stored in the installer information storage unit 208a. The communication control unit 205a executes encryption processing of the vehicle-mounted device ID and the facility ID in 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 the encrypted facility ID to the vehicle-mounted device ID verification 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 the encrypted facility ID. The information control unit 303a decrypts the encrypted vehicle-mounted device ID and the encrypted facility ID in 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 whose vehicle-mounted device ID and facility ID match from the vehicle-mounted device ID table 311a of the device information storage unit 302a (step S205a). If the vehicle-mounted device ID and the facility ID match (step S205a-YES), the information control unit 303 acquires the value of the mobile terminal ID (step S206). If the onboard device IDs do not match (step S205a-NO), the onboard device ID verification device 300a terminates the process (step S207). The information control unit 303a transmits the mobile terminal ID to the entrance/exit management device 400 via the IP communication unit 301 (step S208).

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

The information control unit 102 utters the value of the facility variable password information via the voice output unit 104 . The information control unit 102 displays the value of the facility variable password information via the display unit 105 (step S212).

The input unit 504 is operated by a person riding in the vehicle to input verification information (step S213). The input unit 504 notifies the input/output control unit 502 of the collation information. The input/output control unit 502 transmits verification information to the entrance/exit management device 400 via the short-range wireless communication unit 501 and the entrance/exit roadside device 200a (steps S214 to S215).

IP communication section 401 notifies authentication control section 402 of the verification information. The authentication control unit 402 performs authentication processing of verification information in the authentication processing unit 404 . Specifically, the authentication processing unit 404 compares the verification information received from the mobile terminal 500 and the verification information stored in the authentication information record, and if a predetermined authentication condition is satisfied (for example, they match), the authentication processing is performed. The unit 404 determines that the vehicle-mounted device 100 is an authorized device. On the other hand, if the predetermined condition is not met (for example, they do not match), the authentication processing unit 404 determines that the vehicle-mounted device 100 is an unauthorized device (step S216). The authentication control unit 402 transmits the authentication result to the entrance/exit roadside device 200a (step S217).

The IP communication unit 204 notifies the entrance/exit control unit 206 of the authentication processing execution result. The entrance/exit control unit 206 executes processing based on the authentication processing execution result (step S218). If the authentication processing execution result is authentication success (step S218-YES), the entrance/exit control unit 206 transmits a gate opening instruction to the entrance/exit suppressor 600 via the entrance/exit communication unit 207 (step S219). On the other hand, if the authentication processing execution result is not authentication success (step S218-NO), the entrance/exit control unit 206 ends the processing (step S220).

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

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

In the first embodiment, the authentication process is executed using the facility variable password information and the mobile terminal password information transmitted from the mobile terminal 500. However, in the third embodiment, the mobile terminal Authentication processing is executed using only the ID. Further, in the first embodiment, the mobile terminal ID is transmitted from the mobile terminal 500 to the entrance/exit management device 400, but in the third embodiment, the mobile terminal ID is transmitted from the vehicle-mounted device ID verification device 300 without going through the mobile terminal 500. It is transmitted to the exit management device 400 . With this configuration, in the third embodiment, entry/exit can be realized without using the mobile terminal 500 .

The entry/exit system 3 will be described in detail below with reference to FIG. FIG. 9 is a system configuration diagram showing the system configuration of the entrance/exit system 3 in the third embodiment. The entrance/exit system 3 in the third embodiment differs from the first embodiment in that the portable terminal 500 is not used. Only points different from the first embodiment will be described below.

The entrance/exit roadside device 200 b does not have the terminal communication unit 203 . The entrance/exit roadside device 200b has the same configuration as the entrance/exit roadside device 200 in other respects.

The entrance/exit management device 400b includes an authentication control unit 402b in place of the authentication control unit 402. FIG. The entrance/exit management device 400b includes an authentication information storage unit 403b that stores a mobile terminal ID in place of the authentication information storage unit 403 that stores verification information. The entrance/exit management device 400b includes 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 collation information. The entrance/exit management device 400b does not have the facility variable personal identification information generator 405 . The entrance/exit management device 400b has the same configuration as the entrance/exit management device 400 in other respects.

The authentication information storage unit 403b stores an authentication information table 411b. The authentication information record b has a mobile terminal ID. In the example shown in FIG. 9, the mobile terminal ID of the authentication information record b at the top of the authentication information table 411b is "xxx@xxx". When the mobile terminal ID received from the vehicle-mounted device ID verification device 300 is "xxx@xxx", the authentication processing unit 404b determines that the authentication information record b has been successfully authenticated. Note that the authentication information table 411b shown in FIG. 9 is merely a specific example. Therefore, the authentication information table 411b may be configured in a manner different from that in FIG. For example, the authentication information table 411b may have the date and time when the mobile terminal ID was registered.

FIG. 10 is a sequence diagram showing the flow of processing until 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. First, the user of the vehicle-mounted device transmits the vehicle-mounted device ID and the portable terminal ID to the vehicle-mounted device ID verification device 300 . Alternatively, the transmission may be sent from a web page. Moreover, you may send to the management organization of the onboard equipment ID collation apparatus 300 for transmission (step S401). Next, the vehicle-mounted device ID verification apparatus 300 performs registration processing of the vehicle-mounted device ID and the mobile terminal ID. Specifically, the vehicle-mounted device ID verification device 300 generates a vehicle-mounted device ID record in the vehicle-mounted device ID table. The vehicle-mounted device ID verification device 300 registers the vehicle-mounted device ID and the mobile terminal ID in the vehicle-mounted device ID record (step S402).

The vehicle-mounted device user notifies the vehicle-mounted device ID and the permission to use the vehicle-mounted device ID to the company (for example, the condominium management organization, etc.) (step S403). Upon receiving the vehicle-mounted device ID and the vehicle-mounted device ID usage permission, the business operator transmits the vehicle-mounted device ID to the vehicle-mounted device ID verification device 300 . Also, the transmission may be made for each on-vehicle device user. Moreover, after receiving the vehicle-mounted device ID of all the vehicle-mounted device users, you may transmit collectively. Alternatively, the transmission may be sent from a web page. Alternatively, the transmission may be sent to the management organization of the vehicle-mounted device ID verification device 300 (step S404). The vehicle-mounted device ID verification device 300 identifies the mobile terminal ID using the vehicle-mounted device ID (step S405). The vehicle-mounted device ID verification device 300 transmits the mobile terminal ID to the entrance/exit management device 400b (step S406). The entrance/exit management device 400b registers the mobile terminal ID in the authentication information table 411b (step S407). As described above, in the entrance/exit system 3, use of the vehicle-mounted device ID and the mobile terminal ID is started.

FIG. 11 is a sequence diagram showing the flow of processing of the entrance/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 entrance/exit roadside device 200b via the communication unit 101 (step S201).

The vehicle-mounted device communication unit 201 notifies the vehicle-mounted device ID to the communication control unit 205 . The communication control unit 205 executes encryption processing of the vehicle-mounted device ID in 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 verification 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 causes the decryption processing unit 304 to decrypt the encrypted vehicle-mounted device ID. The decryption processing unit 304 generates a vehicle-mounted device ID from the encrypted vehicle-mounted device ID (step S204). The information control unit 303 identifies a vehicle-mounted device ID record with a matching vehicle-mounted device ID from the vehicle-mounted device ID table 311 of 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 onboard device IDs do not match (step S205-NO), the onboard device ID verification device 300 terminates the process (step S207). The information control unit 303 transmits the mobile terminal ID to the entrance/exit management device 400b via the IP communication unit 301 (step S208).

The IP communication unit 401 notifies the mobile terminal ID to the authentication control unit 402b. 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 verification device 300 with the mobile terminal ID registered in the authentication information record b, and satisfies a predetermined authentication condition (for example, matches). ), the authentication processing unit 404b determines that the vehicle-mounted device 100 is an authorized device. On the other hand, if the predetermined condition is not satisfied (for example, they do not match), the authentication processing unit 404b determines that the vehicle-mounted device 100 is not authorized (step S216b). The authentication control unit 402b transmits the execution result of authentication processing to the entrance/exit roadside device 200 (step S217).

The IP communication unit 204 notifies the entrance/exit control unit 206 of the authentication processing execution result. The entrance/exit control unit 206 executes processing based on the authentication processing execution result (step S218). If the authentication processing execution result is authentication success (step S218-YES), the entrance/exit control unit 206 transmits a gate opening instruction to the entrance/exit suppressor 600 via the entrance/exit communication unit 207 (step S219). On the other hand, if the authentication processing execution result is not authentication success (step S218-NO), the entrance/exit control unit 206 ends the processing (step S220).

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

According to at least one of the embodiments described above, it is possible to identify a person in the vehicle with higher accuracy by having an authentication processing function for the authentication information and the mobile terminal ID.

While several embodiments of the invention have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and modifications can be made without departing from the scope of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, as well as the scope of the invention described in the claims and equivalents thereof.

DESCRIPTION OF SYMBOLS 1... Entrance/exit system, 2... Entrance/exit system, 3... Entrance/exit system, 10... Facility, 100... Vehicle-mounted device, 101... Communication part, 102... Information control part, 103... Vehicle-mounted device information storage part, 104... Voice output Unit 105 Display unit 106 Card input/output unit 107 Card 200 Entry/exit roadside device 201 Vehicle-mounted device communication unit 202 Encryption processing unit 203 Terminal communication unit 204 IP communication unit , 205... Communication control unit, 206... Entrance/exit control unit, 207... Entrance/exit communication unit, 300... Vehicle-mounted device ID verification device, 301... IP communication unit, 302... Device information storage unit, 303... Information control unit, 304... Decryption processing unit 311 On-vehicle 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 information generation Part 411... Authentication information table 500... Portable terminal 501... Near field wireless communication part 502... Input/output control part 503... Display part 504... Input part 600... Entrance/exit suppressor 601... Communication part 602... Entrance/exit control unit, 603... Entrance/exit suppression unit, 200a... Entrance/exit roadside device, 202a... Encryption processing unit, 205a... Communication control unit, 208a... Installer information storage unit, 300a... Vehicle-mounted device ID verification device, 302a... Device information storage unit 303a... Information control unit 304a... Decryption processing unit 311a... Vehicle-mounted device ID table 200b... Entrance/exit roadside device 400b... Entrance/exit management device 402b... Authentication control unit 403b... Authentication information Storage unit 404b Authentication processing unit 411b Authentication information table

Claims (2)

A user identification system comprising an onboard device ID verification device and a management device,
The vehicle-mounted device ID verification device,
a device information storage unit that stores a record that associates a vehicle-mounted device ID, which is identification information of the vehicle-mounted device, with a mobile terminal ID of a mobile terminal owned by a user of the vehicle-mounted device;
a communication unit that receives, from a roadside device provided in the vicinity of a facility to be managed, information indicating an onboard device ID received by the roadside device from the onboard device of the vehicle;
an acquisition unit that acquires the mobile terminal ID associated with the record when a record matching the vehicle-mounted device ID indicated by the received information is stored in the device information storage unit;
an information control unit that transmits the acquired mobile terminal ID to the management device,
The management device
After receiving the mobile terminal ID from the vehicle-mounted device ID matching device, receiving verification information including the mobile terminal ID from the user, and performing authentication processing based on the received mobile terminal ID and the received verification information. A user identification system comprising: an authentication processor to perform; A vehicle-mounted device ID collation device having a device information storage unit that stores a record that associates a vehicle-mounted device ID, which is identification information of a vehicle-mounted device, with a mobile terminal ID of a mobile terminal owned by a user of the vehicle-mounted device, and a management device. A user identification method performed by a user identification system comprising
a receiving step in which the vehicle-mounted device ID verification device receives information indicating the vehicle-mounted device ID received by the vehicle-mounted device from the vehicle-mounted device, from an entrance/exit roadside device provided near a facility to be managed;
an ID obtaining step of obtaining the portable terminal ID associated with the record matching the vehicle-mounted device ID indicated by the information received by the vehicle-mounted device ID matching device, when the record is stored in the device information storage unit; ,
an information control step in which the vehicle-mounted device ID verification device transmits the acquired mobile terminal ID to the management device;
After receiving the mobile terminal ID from the vehicle-mounted device ID matching device, the management device receives matching information including the mobile terminal ID from the user, and compares the received mobile terminal ID with the received matching information. and an authentication process step of performing an authentication process based on.

Images