JP2018022285A - Entry/exit system and entry/exit control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an entry/exit system capable of highly precisely identifying a person in a vehicle and an entry/exit control method.SOLUTION: The entry/exit system has an on-vehicle device ID collation device, an entry/exit management device and an entry/exit roadside device. An information control part of the on-vehicle device ID collation device identifies a portable terminal ID of a portable terminal owned by a person riding in a vehicle on the basis of an on-vehicle device ID which is identification information of an on-vehicle device of the vehicle intruding in the entry/exit system and transmits the portable terminal ID to the entry/exit management device. The entry/exit management device authentication processing part executes authentication processing for collation information received by the entry/exit management device. An entry/exit control part of the entry/exit roadside device determines opening/closing of an entry/exit restriction part on the basis of a result of the authentication processing.SELECTED DRAWING: Figure 1

Description

  Embodiments described herein relate generally to an entry / exit system and an entry / exit control method.

  Conventionally, there has been a system for controlling opening and closing of an entrance / exit suppression unit of an apartment or a commercial facility using an onboard unit ID transmitted from an ETC onboard unit. However, since the vehicle-mounted device ID transmitted from the vehicle-mounted device is an ID associated with the vehicle, the person in the vehicle cannot be accurately identified. For this reason, there are cases where the above system cannot be used in places where high security is required.

JP 2005-227996 A JP 2009-294310 A

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

  The problem to be solved by the present invention is to provide an entry / exit system and an entry / exit control method capable of specifying a person in the vehicle with higher accuracy.

  The entry / exit system according to the embodiment includes an in-vehicle device ID collation device, an entry / exit management device, and an entry / exit roadside device. The information control unit of the in-vehicle device ID collating device determines the mobile terminal ID of the mobile device possessed by the person who gets on the vehicle based on the in-vehicle device ID that is the identification information of the on-vehicle device of the vehicle that has entered the exit / exit system. The mobile terminal ID is identified and transmitted to the entrance / exit management device. The entry / exit management device authentication processing unit executes an authentication process on the collation information received by the entry / exit management device. The entry / exit control unit of the entry / exit roadside device determines opening / closing of the entry / exit suppression unit based on the result of the authentication process.

Schematic which shows the specific application example of the entrance / exit system 1 of 1st embodiment. The system block diagram showing the system configuration | structure of the entrance / exit system 1. FIG. The schematic block diagram showing the function structure of the onboard equipment 100. FIG. FIG. 2 is a schematic block diagram illustrating a functional configuration of a mobile terminal 500. The sequence diagram showing the flow of a process of the entrance / exit system 1 in 1st embodiment. The system block diagram showing the system configuration | structure of the entrance / exit system 2 of 2nd embodiment. In the entrance / exit system 2 in 2nd embodiment, the sequence diagram showing the flow of a process until a provider carries out tied registration of vehicle equipment ID, facility ID, and portable terminal ID. The sequence diagram showing the flow of a process of the entrance / exit system 2 in 2nd embodiment. The system block diagram showing the system configuration | structure of the entrance / exit system 3 in 3rd embodiment. In the entrance / exit system 3 in 3rd embodiment, the sequence diagram showing the flow of a process until use of onboard equipment ID and portable terminal ID is started. The sequence diagram showing the flow of a process of the entrance / exit system 3 in 3rd embodiment.

  Hereinafter, an entry / exit system and an entry / exit control method of an embodiment will be described with reference to the drawings.

(First embodiment)
FIG. 1 is a schematic diagram showing a specific application example of the entry / 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, the 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 the entrance / exit. The in-vehicle device ID verification device 300 and the entrance / exit management device 400 are connected to the entry / exit roadside device 200 via the network 700. The mobile terminal 500 is owned by a vehicle driver.

  The in-vehicle device ID verification device 300 is, for example, a dedicated information processing device managed by an external organization such as the government. The entrance / exit management apparatus 400 is an information processing apparatus that stores an authentication information table in which a mobile terminal ID, facility variable password information, and mobile terminal password information that is not updated and is set in advance by the in-vehicle device user. 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. For example, the mobile terminal ID may be a mail address, a serial number, a MAC address, or the like. The portable terminal password information is information stored in advance in the authentication information table by the in-vehicle device user. The facility variable password information is password information periodically generated by the entrance / exit management device 400. The facility variable password information is information that is changed in a short cycle such as every day. Therefore, the facility variable password information is information that cannot be known until notified even by a person who gets on the vehicle. The combination of the facility variable password information, the portable terminal password information, and the portable terminal ID is hereinafter referred to as “collation information”.

  The on-vehicle device 100 is an on-vehicle device for receiving an automatic fee collection service by ETC. The vehicle-mounted device 100 is set with an vehicle-mounted device ID when the vehicle-mounted device 100 is attached to the vehicle. The portable terminal 500 is a terminal that can perform short-range wireless communication or medium-range wireless communication. Specifically, the portable terminal 500 is a portable terminal such as a smartphone or a tablet.

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

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 the vehicle-mounted device ID is registered be 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 external organization.
On the other hand, the collation information including the mobile terminal ID (for example, e-mail address) is personal information and important information, but does not need to be managed as strictly as the vehicle-mounted device ID. It is desirable to be registered / updated. Therefore, the collation information is managed by the entry / exit management device 400. In the entry / exit system 1 described above, the vehicle-mounted device ID collation device 300 manages the vehicle-mounted device ID and the portable terminal ID in association with each other, and the portable terminal ID is transmitted to the entry / exit management device 400. That is, the vehicle-mounted device ID is not transmitted to the entry / exit management device 400. With such a configuration, it is possible to more strictly manage the vehicle-mounted device ID and maintain security.

Next, each component which comprises the entrance / exit system 1 is demonstrated using a block diagram. FIG. 2 is a system configuration diagram showing the system configuration of the entry / exit system 1.
The entry / exit roadside device 200 includes an onboard equipment communication unit 201, an encryption processing unit 202, an IP communication unit 204, a terminal communication unit 203, a communication control unit 205, an entry / exit control unit 206, and an entry / exit communication unit 207. The entry / exit roadside device 200 includes a plurality of network interfaces, a CPU (Central Processing Unit) connected by a bus, a memory, an auxiliary storage device, and the like. Note that all or part of the functions of the entry / exit roadside device 200 may be realized by using hardware such as an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). . The entry / exit roadside device 200 may be configured using a plurality of information processing devices.

  The onboard equipment communication unit 201 is a network interface for communicating with the onboard equipment 100. The wireless communication may be, for example, DSRC (Dedicated Short Range Communication) used as a conventional ETC method or ETC 2.0 method.

  The encryption processing unit 202 executes encryption processing of the vehicle-mounted device ID, and generates an encrypted vehicle-mounted device ID.

  The terminal communication unit 203 is a network interface for the entry / exit roadside device 200 to communicate with the mobile terminal 500. For the wireless communication, for example, a short-range wireless communication method is desirable in order to prevent communication from a long distance. The 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 entry / exit roadside device 200 to communicate. The IP communication unit 204 communicates with the vehicle-mounted device ID verification device 300 in order to make an inquiry about the mobile terminal ID via the network 700.

  The communication control unit 205 controls the execution of the authentication process of the entry / exit roadside device 200 when a vehicle equipped with the vehicle-mounted device 100 enters the entry / exit system 1.

  The entrance / exit control unit 206 controls the entrance / exit suppressor 600 to open based on an instruction from the entrance / exit management device 400.

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

  The entry / exit suppressor 600 is a device that prevents the vehicle from actually entering. Specifically, the entrance / exit suppressor 600 includes a circuit breaker, a shutter, and the like. The entry / exit suppressor 600 includes a communication unit 601, an entry / exit control unit 602, and an entry / exit suppression unit 603.

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

  The entrance / exit control unit 602 notifies the entrance / exit suppression unit 603 of an opening instruction based on the opening instruction from the entrance / exit roadside device 200. After notifying the opening instruction, the entrance / exit control unit 602 notifies the entrance / exit suppression unit 603 of the closing instruction when a predetermined time elapses. Moreover, the entrance / exit control part 602 may notify the entrance / exit suppression part 603 of a gate closing instruction after passing the entrance / exit suppression part 603 which the onboard equipment 100 opened.

  The entry / exit suppression unit 603 opens the entrance / exit suppression unit 603 when receiving a notification of the opening instruction from the entrance / exit control unit 602. Further, the entrance / exit suppression unit 603 is closed when a gate instruction is notified from the entrance / exit control unit 602. Moreover, as for the entrance / exit suppression part 603, the entrance part and the exit part may differ.

  The in-vehicle device ID collation apparatus 300 includes an IP communication unit 301, a device information storage unit 302, an information control unit 303, and a decryption processing unit 304. The in-vehicle device ID verification device 300 is configured using an information processing device such as a mainframe, a workstation, or a personal computer. The in-vehicle device ID collation device 300 can be any device as long as it can provide the following functions. The in-vehicle device ID collation apparatus 300 includes a network interface, a CPU connected by a bus, a memory, an auxiliary storage device, and the like. Note that all or part of the functions of the vehicle-mounted device ID verification device 300 may be realized using hardware such as an ASIC, PLD, or FPGA.

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

  In the example illustrated in FIG. 2, the onboard device ID record in the uppermost stage of the onboard device ID table 311 has the onboard device ID “XXX” and the mobile terminal ID “xxx @ xxx”. This onboard equipment ID record indicates that when the onboard equipment ID received by the onboard equipment ID verification device 300 is “XXX”, the information control unit 303 acquires the mobile terminal ID “xxx @ xxx”. In addition, the onboard equipment ID table 311 shown by FIG. 2 is only a specific example. Therefore, the vehicle-mounted device ID table 311 may be configured in a mode different from that in FIG.

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

  The decryption processing unit 304 executes decryption processing of 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 entrance / exit management apparatus 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 entry / 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 entry / exit management device 400 can be any device as long as it can provide the following functions. The entry / exit management device 400 includes a network interface, a CPU connected by a bus, a memory, an auxiliary storage device, and the like. Note that all or part of the functions of the entry / exit management device 400 may be realized using hardware such as an ASIC, PLD, or FPGA.

  The IP communication unit 401 is a network interface with which the entry / exit management device 400 communicates. The IP communication unit 401 communicates with the entry / 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 verification 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. In the authentication control unit 402, the authentication processing unit 404 executes verification processing of verification information. The authentication control unit 402 transmits the authentication processing execution result of the authentication processing unit 404 to the entry / 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.

  As shown in FIG. 2, the authentication information table 411 has collation 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 portable 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 “vehicle device user”). The portable terminal password information may be any information as long as it is information used as existing authentication information such as a character string including numbers and alphabets, a combination of patterns, a line pattern, and the like. The portable terminal password information may be biological information such as a fingerprint or a face, for example. The portable terminal password information may be a combination of a plurality of information.

  In the example shown in FIG. 2, the uppermost authentication information record of the authentication information table 411 has the device ID “xxx @ xxx”, the facility variable password information “QQQQ”, and the portable terminal password information “RRRR”. In the authentication information record, when 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 entry / exit management device 400, The authentication processing unit 404 determines that the authentication is successful. 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 portable terminal password information was updated.

  The authentication processing unit 404 executes authentication processing based on the collation information received by the entry / 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 entry / exit management device 400 and the authentication information record stored in the authentication information storage unit 403 satisfy a predetermined authentication condition (for example, match), the authentication processing unit 404 satisfies the in-vehicle device. 100 is determined to be a device having a legitimate authority. On the other hand, when the verification 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 a predetermined authentication condition (for example, do not match), the authentication processing unit 404 determines that the in-vehicle device 100 It is determined that the device does not have a valid authority.

  The facility variable password information generation unit 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 password information may be, for example, once a day. As the facility variable password information, a random value is generated for each record.

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

  FIG. 3 is a schematic block diagram illustrating a functional configuration of the vehicle-mounted device 100. 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 by a bus. The on-vehicle device 100 functions as a device including the communication unit 101, the information control unit 102, the on-vehicle device information storage unit 103, the audio output unit 104, the display unit 105, and the card input / output unit 106 by executing the authentication program. All or some of the functions of the vehicle-mounted 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. The computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a semiconductor storage device, or a storage device such as a hard disk or a semiconductor storage device built in the computer system. 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 that can communicate with the vehicle-mounted device communication unit 201. The communication unit 101 communicates with the entry / exit roadside device 200. For communication, for example, the communication method may be DSRC.

  The information control unit 102 controls the execution of the authentication process 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 entry / exit roadside device 200. The information control unit 102 notifies the audio output unit 104 of the facility variable password information received from the entry / exit roadside device 200. The information control unit 102 notifies the display unit 105 of the facility variable password information received from the entry / exit roadside device 200. The vehicle-mounted device ID is identification information of the vehicle-mounted device of the vehicle that has entered the entry / exit system. As long as OBE ID is a value which does not overlap with other OBE ID, what kind of value may be sufficient as it. The vehicle-mounted device ID may be, for example, an ETC (Electronic Toll Collection System) vehicle-mounted device WCN (Wireless Call Number), a serial number, or the like.

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

  The audio output unit 104 is configured using an existing audio output device such as a speaker, an earphone, or a headphone. The audio output unit 104 may be an interface for connecting the 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 an audio output device connected to itself.

  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 be an interface for connecting the 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 a video output device connected to the display unit 105.

  The card input / output unit 106 includes a card slot into which the card 107 is inserted. The card input / output unit 106 acquires and registers information with respect to the card 107 inserted in the card slot. In the example of FIG. 3, the card input / output unit 106 includes one card slot and one card 107 is inserted. However, the configuration may be different from that shown in FIG. For example, the card input / output unit 106 may have two or more card slots.

  The card 107 is a card for performing fee settlement using the ETC system. The card 107 is used by being inserted into a card slot provided in the card input / output unit 106. 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, an organization that is affiliated with the credit card company, etc.) Information of a type indicating a service provided to the user is recorded in advance. In addition to the card information, the card 107 records information on an entrance toll gate where the user has started using the road and information on an exit toll gate where the user has finished using the road.

  FIG. 4 is a schematic block diagram illustrating a functional configuration of the mobile terminal 500. The portable terminal 500 is configured using an information processing apparatus such as a tablet computer, a personal computer, or a smartphone. The portable 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 portable terminal 500 includes a network interface, a CPU, a memory, an auxiliary storage device, and the like connected by a bus. The portable terminal 500 is held by a person who gets on the vehicle, for example.

  The short-range wireless communication unit 501 is a network interface with which the mobile terminal 500 communicates. The near field communication unit 501 is a near field communication unit for communicating with the entry / 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 entry / exit management device 400. The input / output control unit 502 transmits the input information to the entry / exit management device 400 via the entry / exit roadside device 200.

  The display unit 503 is a video output device such as a CRT display, a liquid crystal display, or an organic EL display. The display unit 503 may be an interface for connecting the 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 a video output device connected to the display unit 503.

  The input unit 504 is configured using an existing input device such as a touch panel, a button, or a switch. The input unit 504 may be an interface for connecting the input device to the portable terminal 500. In this case, the input unit 504 generates input data from the input signal input in the input device and inputs the input data to the mobile terminal 500. The input unit 504 transmits the input signal that has been input to the entry / exit roadside device 200. When the input unit 504 is configured using a touch panel, the input unit 504 and the display unit 503 may be configured integrally.

  Next, the operation will be described. FIG. 5 is a sequence diagram showing the flow of processing of the entry / exit system 1 in the first embodiment. As an advance preparation, the on-vehicle device user notifies the on-vehicle device ID verification device 300 of the on-vehicle device ID and the portable terminal ID. Moreover, the onboard equipment user may transmit onboard equipment ID and portable terminal ID from the onboard equipment 100 to the onboard equipment ID collation apparatus 300. FIG. 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 onboard equipment ID collation apparatus 300 performs registration processing of the received onboard equipment ID and mobile terminal ID. Specifically, the onboard equipment ID collation apparatus 300 registers the onboard equipment ID and the portable terminal ID in the onboard equipment ID table 311 in association with each other (step S102). The in-vehicle device ID verification device 300 transmits the mobile terminal ID to the entry / exit management device 400 (step S103). The vehicle-mounted device user transmits the portable terminal password information determined by the user to the entrance / exit management device 400. Moreover, the vehicle-mounted device user may transmit the portable terminal password information from the portable terminal 500 to the entry / 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 registers the received mobile terminal ID, mobile terminal authentication information, and facility variable authentication information in the authentication information table 411 in association with each other (step S105). This completes the preliminary preparation.

  Next, the information control part 102 acquires OBE ID from the onboard equipment information storage part 103, and transmits to the entrance / exit roadside apparatus 200 via the communication part 101 (step S201).

  The onboard equipment communication unit 201 notifies the onboard equipment ID to the communication control unit 205. The communication control unit 205 executes encryption processing of the vehicle-mounted device ID by 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. In the information control unit 303, the decryption processing unit 304 performs decryption processing of the encrypted vehicle-mounted device ID. The decryption processing unit 304 generates the vehicle-mounted device ID from the encrypted vehicle-mounted device ID (step S204). The information control unit 303 identifies the onboard unit ID record having the same onboard unit ID from the onboard unit ID table 311 of the device information storage unit 302 (step S205). When 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 verification device 300 ends the process (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 obtains the value of the facility variable password information from the authentication information table 411 of the authentication information storage unit 403 from the authentication information record with the matching mobile terminal ID (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 entry / exit roadside device 200 (steps S210 to S211).

  The information control unit 102 utters the value of the facility variable password information via the audio 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 receives collation information by an operation of a person who gets on the vehicle (step S213). The person in the vehicle is, for example, a vehicle-mounted device user, a vehicle driver, or the like. The input unit 504 notifies the input / output control unit 502 of collation information. The input / output control unit 502 transmits the collation information to the entry / exit management device 400 via the short-range wireless communication unit 501 and the entry / exit roadside device 200 (steps S214 to S215).

  The IP communication unit 401 notifies the authentication control unit 402 of verification information. In the authentication control unit 402, the authentication processing unit 404 executes verification processing of verification information. Specifically, the authentication processing unit 404 compares the verification information received from the mobile terminal 500 with the verification information stored in the authentication information record. If the predetermined authentication condition is satisfied (for example, matches), the authentication processing unit 404 The unit 404 determines that the vehicle-mounted device 100 is a device having a valid authority. On the other hand, when the predetermined condition is not satisfied (for example, does not match), the authentication processing unit 404 determines that the in-vehicle device 100 is a device that does not have a valid authority (step S216). The authentication control unit 402 transmits an authentication process execution result to the entry / exit roadside device 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 processing execution result (step S218). If the authentication process execution result is a successful authentication (step S218—YES), the entry / exit control unit 206 transmits an opening instruction to the entry / exit suppressor 600 via the entry / exit communication unit 207 (step S219). On the other hand, if the authentication process execution result is not authentication success (step S218—NO), the entry / exit control unit 206 ends the process (step S220).

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

  In the processing flow of FIG. 5, the verification information acquired in step S <b> 213 may be encrypted by the encryption processing unit 202. In such a case, when the 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 with higher safety is possible compared to the case where the verification information is transmitted without executing the encryption process.

(Second embodiment)
First, an outline of the entry / exit system 2 in the second embodiment will be described. The second embodiment is used when the business operator installs the entrance / exit roadside device 200a at two or more places. For example, when vehicle management is performed on the premises such as a construction site, the construction company performs association between the vehicle-mounted device 100 and the entry / exit roadside device 200a. Therefore, when there are a plurality of construction sites, linking is a heavy burden on the construction company. Therefore, the entry / exit system 2 reduces the burden associated with this association. Specifically, the vehicle-mounted device ID collating device 300a registers the vehicle-mounted device ID, the facility ID, and the mobile terminal ID in association with each other. The facility ID is an identifier for identifying the entry / 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, a facility name or an arbitrary character string. The onboard equipment ID collating device 300a specifies the mobile terminal ID using the onboard equipment ID and the facility ID received from the entry / exit roadside device 200a. When at least one of the vehicle-mounted device ID and the facility ID is different, the vehicle on which the vehicle-mounted device 100 is mounted is regarded as trying to enter the unauthorized entry / exit roadside device 200a. Therefore, this vehicle cannot enter the construction site. By being configured in this way, the construction company does not need to be associated with each construction site. As a result, the burden of linking by the construction company is reduced.

  Hereinafter, the entrance / exit system 2 will be described in detail 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 entry / exit system 2 in the second embodiment differs from the first embodiment in that a facility ID is newly used. Only differences from the first embodiment will be described below. The entry / exit system 2 is different from the entry / exit road side device 200 in the first embodiment in that it has an entry / exit road side device 200a and an onboard device ID collation device 300a instead of the onboard device ID collation device 300. Unlike the entry / exit system 1, it has the same configuration as the entry / exit system 1 in other respects.

  The entrance / exit roadside apparatus 200a includes an encryption processing unit 202a that executes encryption processing on the vehicle-mounted device ID and facility ID instead of the encryption processing unit 202 that executes encryption processing on the vehicle-mounted device ID. The entry / 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 entry / exit roadside device 200a further includes an installer information storage unit 208a that stores a facility ID. The entrance / exit road side device 200a has the same configuration as the entrance / exit road side device 200 in other points.

The in-vehicle device ID collating device 300a includes a device information storage unit 302a that stores a facility ID in place of the device information storage unit 302 that stores the in-vehicle device ID and the portable terminal ID. The in-vehicle device ID collation device 300a controls the process of specifying the mobile terminal ID from the in-vehicle device ID and the facility ID instead of the information control unit 303 that controls the process of specifying the mobile terminal ID from the on-vehicle device ID. Is provided. The in-vehicle device ID collating apparatus 300a includes a decryption processing unit 304a that executes decryption processing of the encrypted in-vehicle device ID and the encrypted facility ID instead of the decryption processing unit 304 that performs decryption processing of the encrypted in-vehicle device ID. Is provided. The OBE ID verification device 300a has the same configuration as the OBE ID verification device 300 in other points.

The onboard equipment ID table 311a is different from the onboard equipment ID table 311 in the first embodiment in that it further includes a facility ID column, and has the same configuration as the onboard equipment ID table 311 in other points.

  In the example shown in FIG. 6, the onboard unit ID record a in the onboard unit ID table 311a has the onboard unit ID “XXX” and the facility ID “AAA” received by the onboard unit ID collating device 300a. The information control unit 303a indicates that the mobile terminal ID acquires “xxx @ xxx”. In addition, the onboard equipment ID table 311a shown in FIG. 6 is only a specific example. Therefore, the vehicle-mounted device ID table 311a may be configured in a mode different from FIG. For example, the vehicle-mounted device ID table 311a may register the time stamp when the vehicle-mounted device ID record a is generated.

  FIG. 7 is a sequence diagram showing a flow of processing until the business operator 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 business operator determines which entry / exit roadside device 200a the in-vehicle device user enters / exits. Therefore, the business operator uses the in-vehicle device ID use consent form. The in-vehicle device ID use consent form indicates which in-vehicle device 200a the in-vehicle device can enter / exit. The business operator obtains the approval of the vehicle-mounted device user for the vehicle-mounted device ID use consent form. Thereafter, the business operator registers the content of the in-vehicle device ID use consent form in the on-vehicle device ID verification device 300a. After registration, the in-vehicle device user can enter / exit the entry / exit roadside device 200a shown in the in-vehicle device ID use consent form.

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

  Next, the business operator creates an in-vehicle device ID use consent form. In the onboard equipment ID use consent form, “onboard equipment user name”, “onboard equipment ID”, “license expiration date”, “portable terminal ID”, and “facility ID” are described. In addition, the item of this onboard equipment ID use consent form is only a specific example. Therefore, the onboard equipment ID use consent form may be configured with items different from the onboard equipment ID use consent form. For example, the vehicle-mounted device ID use consent form may have a facility name item. Further, the onboard equipment ID use consent form may be an electronic medium such as a web form (step S302).

  The business entity sends a vehicle-mounted device ID use consent form to the vehicle-mounted device user (step S303). The on-vehicle device user executes an approval process of the on-vehicle device ID use consent form. Specifically, the approval process is such that the vehicle-mounted device user signs the vehicle-mounted device ID use consent form. The approval process may be an electronic signature. The in-vehicle device ID use approval document for which the approval process has been executed is set as an approved in-vehicle device ID use approval document (step S304). The on-vehicle device user sends an approved on-vehicle device ID use consent form to the business operator (step S305). The business entity transmits an approved OBE ID use consent form to the OBE ID verification device 300a. In addition, the business operator may send an approved OBE ID use consent form to the management organization of the OBE ID verification device 300a (step S306).

  The onboard equipment ID collation apparatus 300a generates the onboard equipment ID table 311a (step S307). The OBE ID collation apparatus 300a generates the OBE ID record a in which “OBE ID”, “facility ID”, and “mobile terminal ID” described in the approved OBE ID usage consent form are registered ( Step S308).

  FIG. 8 is a sequence diagram showing the flow of processing of the entry / exit system 2 in the second embodiment. First, the information control part 102 acquires OBE ID from the onboard equipment information storage part 103, and transmits to the entrance / exit roadside apparatus 200a via the communication part 101 (step S201).

  The onboard equipment communication part 201 notifies onboard equipment ID to the communication control part 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 by 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 executes decryption processing of the encrypted vehicle-mounted device ID and the encrypted facility ID by the decryption processing unit 304a. The decryption processing unit 304a generates the 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 the onboard equipment ID record in which the onboard equipment ID and the facility ID match from the onboard equipment ID table 311a of the device information storage section 302a (step S205a). When 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 vehicle-mounted device IDs do not match (step S205a-NO), the vehicle-mounted device ID verification device 300a ends the process (step S207). The information control unit 303a transmits the portable 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 obtains the value of the facility variable password information from the authentication information table 411 of the authentication information storage unit 403 from the authentication information record with the matching mobile terminal ID (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 entry / exit roadside device 200a (steps S210 to S211).

  The information control unit 102 utters the value of the facility variable password information via the audio 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 receives collation information by an operation of a person who gets on the vehicle (step S213). The input unit 504 notifies the input / output control unit 502 of collation information. The input / output control unit 502 transmits the collation information to the entry / exit management device 400 via the short-range wireless communication unit 501 and the entry / exit roadside device 200a (steps S214 to S215).

  The IP communication unit 401 notifies the authentication control unit 402 of verification information. In the authentication control unit 402, the authentication processing unit 404 executes verification processing of verification information. Specifically, the authentication processing unit 404 compares the verification information received from the mobile terminal 500 with the verification information stored in the authentication information record. If the predetermined authentication condition is satisfied (for example, matches), the authentication processing unit 404 The unit 404 determines that the vehicle-mounted device 100 is a device having a valid authority. On the other hand, when the predetermined condition is not satisfied (for example, does not match), the authentication processing unit 404 determines that the in-vehicle device 100 is a device that does not have a valid authority (step S216). The authentication control unit 402 transmits the authentication result to the entry / exit roadside device 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 processing execution result (step S218). If the authentication process execution result is a successful authentication (step S218—YES), the entry / exit control unit 206 transmits an opening instruction to the entry / exit suppressor 600 via the entry / exit communication unit 207 (step S219). On the other hand, if the authentication process execution result is not authentication success (step S218—NO), the entry / exit control unit 206 ends the process (step S220).

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

(Third embodiment)
First, an outline of the entry / exit system 3 in the third embodiment will be described. The third embodiment assumes an entry / exit system that can enter / 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 identity verification is not required. For this purpose, the following processing is executed.

  In the first embodiment, the authentication process using the facility variable password information and the portable terminal password information transmitted from the portable terminal 500 is executed, but in the third embodiment, the portable terminal without using these two pieces of information. The authentication process is executed only with the ID. In the first embodiment, the mobile terminal ID is transmitted from the mobile terminal 500 to the entry / exit management device 400. However, in the third embodiment, the mobile terminal ID is input from the in-vehicle 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.

  Hereinafter, the entrance / exit system 3 will be described in detail with reference to FIG. FIG. 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 is different from the first embodiment in that the mobile terminal 500 is not used. Only differences from the first embodiment will be described below.

  The entry / exit roadside device 200b does not have the terminal communication unit 204. The entrance / exit road side device 200b has the same configuration as the entrance / exit road side device 200 in other points.

  The entry / exit management device 400 b includes an authentication control unit 402 b instead of the authentication control unit 402. The entry / exit management device 400b includes an authentication information storage unit 403b that stores a portable terminal ID instead of the authentication information storage unit 403 that stores verification information. The entry / exit management device 400b includes an authentication processing unit 404b that executes an authentication process using a mobile terminal ID instead of the authentication processing unit 404 that executes an authentication process using verification information. The entrance / exit management device 400b does not have the facility variable password information generation unit 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 authentication information record b at the top of the authentication information table 411b has the mobile terminal ID “xxx @ xxx”. In the authentication information record b, when the mobile terminal ID received from the in-vehicle device ID verification device 300 is “xxx @ xxx”, the authentication processing unit 404b determines that the authentication is successful. 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 a flow of processing until use of the vehicle-mounted device ID and the portable terminal ID is started in the entrance / exit system 3 in the third embodiment. First, the vehicle-mounted device user transmits the vehicle-mounted device ID and the mobile terminal ID to the vehicle-mounted device ID verification device 300. Moreover, you may transmit from a web page. The transmission may be sent to the management organization of the vehicle-mounted device ID verification device 300 (step S401). Next, the onboard equipment ID collation apparatus 300 executes registration processing of the onboard equipment ID and the mobile terminal ID. Specifically, the onboard equipment ID collation apparatus 300 generates an onboard equipment ID record in the onboard equipment ID table. The onboard equipment ID collation apparatus 300 registers the onboard equipment ID and the mobile terminal ID in the onboard equipment ID record (step S402).

  The on-vehicle device user notifies the business operator (for example, an apartment management organization) of the on-vehicle device ID and the permission to use the on-vehicle device ID (step S403). When the business operator receives the vehicle-mounted device ID and the vehicle-mounted device ID use permission, the business entity transmits the vehicle-mounted device ID to the vehicle-mounted device ID verification device 300. Moreover, you may transmit for every onboard equipment user. Further, the transmission may be transmitted collectively after receiving the on-vehicle device IDs of all the on-vehicle device users. Moreover, you may transmit from a web page. The transmission may be sent to the management organization of the vehicle-mounted device ID verification device 300 (step S404). The onboard equipment ID collation apparatus 300 specifies portable terminal ID using onboard equipment ID (step S405). The onboard equipment ID verification device 300 transmits the portable 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). As described above, in the entry / exit system 3, use of the vehicle-mounted device ID and the portable terminal ID is started.

  FIG. 11 is a sequence diagram showing the flow of processing of the entry / exit system 3 in the third embodiment. First, the information control part 102 acquires OBE ID from the OBE information storage part 103, and transmits to the entrance / exit roadside apparatus 200b via the communication part 101 (step S201).

  The onboard equipment communication unit 201 notifies the onboard equipment ID to the communication control unit 205. The communication control unit 205 executes encryption processing of the vehicle-mounted device ID by 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. In the information control unit 303, the decryption processing unit 304 performs decryption processing of the encrypted vehicle-mounted device ID. The decryption processing unit 304 generates the vehicle-mounted device ID from the encrypted vehicle-mounted device ID (step S204). The information control unit 303 identifies the onboard unit ID record having the same onboard unit ID from the onboard unit ID table 311 of the device information storage unit 302 (step S205). When 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 verification device 300 ends the process (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 execute 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, a match) The authentication processing unit 404b determines that the vehicle-mounted device 100 is a device having a valid authority. On the other hand, when the predetermined condition is not satisfied (for example, does not match), the authentication processing unit 404b determines that the vehicle-mounted device 100 is a device that does not have a valid authority (step S216b). The authentication control unit 402b transmits the authentication process execution result to the entry / exit roadside device 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 processing execution result (step S218). If the authentication process execution result is a successful authentication (step S218—YES), the entry / exit control unit 206 transmits an opening instruction to the entry / exit suppressor 600 via the entry / exit communication unit 207 (step S219). On the other hand, if the authentication process execution result is not authentication success (step S218—NO), the entry / exit control unit 206 ends the process (step S220).

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

  According to at least one embodiment described above, the person in the vehicle can be identified with higher accuracy by having the authentication processing function for the authentication information and the portable terminal ID.

  Although several embodiments of the present invention have been described, these embodiments are 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 changes can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalents thereof.

DESCRIPTION OF SYMBOLS 1 ... Entrance / exit system, 2 ... Entrance / exit system, 3 ... Entrance / exit system, 10 ... Facility, 100 ... Onboard equipment, 101 ... Communication part, 102 ... Information control part, 103 ... Onboard equipment information storage part, 104 ... Sound output , 105 ... display unit, 106 ... card input / output unit, 107 ... card, 200 ... entry / exit roadside device, 201 ... onboard equipment communication part, 202 ... encryption processing part, 203 ... terminal communication part, 204 ... IP communication part , 205 ... Communication control unit, 206 ... Entry / exit control unit, 207 ... Entry / exit communication unit, 300 ... Onboard unit ID collating device, 301 ... IP communication unit, 302 ... Device information storage unit, 303 ... Information control unit, 304 ... Decryption processing unit, 311... OBE ID table, 400... Entry / exit management device, 401... IP communication unit, 402... Authentication control unit, 403 ... authentication information storage unit, 404 ... authentication processing unit, 405. Information generation unit, 411 ... authentication information table, 500 ... mobile terminal, 501 ... near field communication unit, 502 ... input / output control unit, 503 ... display unit, 504 ... input unit, 600 ... entry / exit suppressor, 601 ... communication , 602... Entry / exit control unit, 603... Entry / exit suppression unit, 200a .. entry / exit roadside device, 202a .. encryption processing unit, 205a ... communication control unit, 208a ... installer information storage unit, 300a. Device, 302a ... Device information storage unit, 303a ... Information control unit, 304a ... Decryption processing unit, 311a ... Onboard unit 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 (8)

An entry / exit system comprising an onboard unit ID collation device, an entry / exit management device, and an entry / exit roadside device,
The vehicle-mounted device ID verification device is:
Based on the vehicle-mounted device ID that is identification information of the vehicle-mounted device of the vehicle that has entered the entry / exit system, the portable terminal ID of the portable terminal possessed by the person who gets on the vehicle is specified, and the portable terminal ID is entered and exited An information control unit for transmitting to the management device;
The entry / exit management device includes:
An authentication processing unit that performs authentication processing on the verification information received by the entry / exit management device;
The entry / exit roadside device is:
An entry / exit system including an entry / exit control unit that determines opening / closing of an entry / exit suppression unit based on a result of the authentication process. The entry / exit management device executes an authentication process based on collation information input to a portable terminal possessed by a person who rides the vehicle.
The entry / exit system according to claim 1. The vehicle-mounted device ID verification device identifies the mobile terminal ID based on the vehicle-mounted device ID and a facility ID that is identification information of the entry / exit roadside device, and transmits the mobile terminal ID to the entry / exit management device. ,
The entrance / exit system of any one of Claim 1 or 2. The authentication processing unit executes an authentication process using the mobile terminal ID as verification information.
The entry / exit system according to claim 1. An entry / exit control method performed by an entry / exit system including an onboard unit ID collation device, an entry / exit management device, and an entry / exit roadside device,
Based on the vehicle-mounted device ID, which is identification information of the vehicle-mounted device of the vehicle that has entered the entry / exit system, the vehicle-mounted device ID verification device identifies a portable terminal ID of a portable terminal possessed by a person who gets on the vehicle, An information control step of transmitting the portable terminal ID to the entry / exit management device;
An authentication processing step in which the entrance / exit management device executes an authentication process on the collation information received by the entrance / exit management device;
An entrance / exit control step in which the entrance / exit roadside device determines opening / closing of the entrance / exit suppression unit based on a result of the authentication process,
An entry / exit control method. The entry / exit management device executes an authentication process based on collation information input to a portable terminal possessed by a person who rides the vehicle.
The entrance / exit control method according to claim 5. The vehicle-mounted device ID verification device identifies the mobile terminal ID based on the vehicle-mounted device ID and a facility ID that is identification information of the entry / exit roadside device, and transmits the mobile terminal ID to the entry / exit management device. ,
The entrance / exit control method of any one of Claim 5 or 6. The authentication processing step executes an authentication process using the mobile terminal ID as verification information.
The entrance / exit control method according to claim 5.

Images