JP6682397B2 - Entrance / exit system and entrance / exit control method - Google Patents

Description

  Embodiments of the present invention relate to an entry / exit system and an entry / exit control method.

  Conventionally, there has been a system for controlling opening / closing of an entrance / exit restraint unit of a condominium or a commercial facility using an on-vehicle device ID transmitted from an ETC on-vehicle device. However, since the vehicle-mounted device ID transmitted from the vehicle-mounted device is the ID associated with the vehicle, the person in the vehicle cannot be accurately specified. Therefore, 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

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

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

  The entrance / exit system according to the embodiment includes an on-vehicle device ID collation device, an entrance / exit management device, and an entrance / exit roadside device. The information control unit of the vehicle-mounted device ID collation device determines the mobile terminal ID of the mobile terminal possessed by the person who gets in the vehicle based on the vehicle-mounted device ID that is the identification information of the vehicle-mounted device of the vehicle that has entered the entry / exit system. It specifies and transmits the portable terminal ID to the entry / exit management device. The entrance / exit management device authentication processing unit executes an authentication process on the collation information received by the entrance / exit management device. The entrance / exit control unit of the entrance / exit roadside device determines whether the entrance / exit restraint unit is open or closed 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 configuration diagram showing the system configuration of the entrance / exit system 1. The schematic block diagram showing the functional composition of onboard equipment 100. 3 is a schematic block diagram showing a functional configuration of the mobile terminal 500. FIG. The sequence diagram showing the flow of processing of entry / exit system 1 in a first embodiment. The system block diagram showing the system configuration of the entrance / exit system 2 of 2nd embodiment. In the entry / exit system 2 in 2nd embodiment, the sequence diagram showing the flow of a process until a business operator carries out link registration of onboard equipment ID, facility ID, and portable terminal ID. The sequence diagram showing the flow of processing of entry / exit system 2 in a second embodiment. The system configuration diagram showing the system configuration of the entry / exit system 3 in the third embodiment. In the entry / exit system 3 in 3rd embodiment, the sequence diagram showing the flow of a process until the use of onboard equipment ID and a portable terminal ID is started. The sequence diagram showing the flow of processing of entry / exit system 3 in a third embodiment.

  Hereinafter, an entrance / exit system and an entrance / 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 for controlling entry / exit of a vehicle by 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 its entrance / exit. The vehicle-mounted device ID collation device 300 and the entrance / exit management device 400 are connected to the entrance / exit roadside device 200 via a network 700. The mobile terminal 500 is possessed by the driver of the vehicle.

  The vehicle-mounted device ID collation device 300 is, for example, a dedicated information processing device managed by an external organization such as the government. The entrance / exit management device 400 is an information processing device that stores an authentication information table in which a mobile terminal ID, facility variable password information, and mobile terminal password information that has not been updated and is preset by the vehicle-mounted device user are associated with each other. Here, the mobile terminal ID is identification information of the mobile terminal 500. The mobile terminal ID may have any value as long as it does not overlap with other mobile terminal IDs. The mobile terminal ID may be, for example, a mail address, a serial number, a MAC address, or the like. The mobile terminal personal identification information is information stored in advance in the authentication information table by the vehicle-mounted device user. The facility variable personal identification information is personal identification information that is regularly 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 in a vehicle cannot know until notified. The combination of the facility variable password information, the mobile terminal password information, and the mobile terminal ID will be referred to as “verification information” below.

  The vehicle-mounted device 100 is a vehicle-mounted device for receiving an automatic fee collection service by ETC. When the vehicle-mounted device 100 is attached to the vehicle, the vehicle-mounted device ID is set. The mobile terminal 500 is a terminal capable of short-range wireless communication, medium-range wireless communication, and the like. The mobile terminal 500 is specifically a portable terminal such as a smartphone or a tablet.

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

The vehicle-mounted device ID is very important information and therefore needs to be strictly managed. Therefore, it is desirable that the vehicle-mounted device ID matching device 300 having the table in which the vehicle-mounted device ID is registered be managed by a strict organization. For example, the vehicle-mounted device ID matching 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 is important information, but it does not need to be managed as strictly as the vehicle-mounted device ID, and is rather flexible for each facility 10. It is desirable to register / update. Therefore, the matching information is managed by the entry / exit management device 400. In the entry / exit system 1 described above, the vehicle-mounted device ID collation apparatus 300 manages the vehicle-mounted apparatus ID and the mobile terminal ID in association with each other, and the mobile terminal ID is transmitted to the entry / exit management apparatus 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 constituent element of the entry / exit system 1 will be described with reference to the configuration diagram. FIG. 2 is a system configuration diagram showing the system configuration of the entry / exit system 1.
The entrance / exit roadside device 200 includes an in-vehicle 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 by a bus, a memory, an auxiliary storage device, and the like. All or some of the functions of the entrance / exit roadside device 200 may be realized by using hardware such as ASIC (Application Specific Integrated Circuit), PLD (Programmable Logic Device), and 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 the encryption processing of the vehicle-mounted device ID to generate the 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 the wireless communication, for example, a short-distance wireless communication system is desirable in order to prevent communication from a long distance. The wireless communication may be, for example, a 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 matching device 300 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 opening / closing of the entrance / exit suppressor 600 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 entrance / exit suppressor 600 is a device that prevents the vehicle from actually entering. The entrance / exit suppressor 600 is specifically composed of a breaker, a shutter, and the like. The entrance / exit suppressor 600 includes a communication unit 601, an entrance / exit controller 602, and an entrance / exit suppressor 603.

  The communication unit 601 is an interface unit that communicates with the entry / exit roadside device 200, and the communication method may be any of BlueTooth, wireless LAN, wired LAN, and the like.

  The entrance / exit control unit 602 notifies the entrance / exit suppression unit 603 of a gate opening command based on the gate opening instruction from the entrance / exit roadside device 200. The entrance / exit control unit 602 notifies the entrance / exit restraint unit 603 of a closing instruction when a predetermined time has elapsed after notifying the opening gate instruction. Further, the entrance / exit control unit 602 may notify the entrance / exit restraint unit 603 of a closing instruction after passing through the entrance / exit restraint unit 603 in which the vehicle-mounted device 100 has opened.

  Upon receiving the notification of the gate opening instruction from the entrance / exit control unit 602, the entrance / exit restraint unit 603 opens the entrance / exit restraint unit 603. Further, when the entry / exit control unit 603 receives a notification of a closing instruction from the entry / exit control unit 602, the entry / exit control unit 603 closes. Further, the entrance / exit control unit 603 may have different entrance and exit parts.

  The vehicle-mounted device ID collation device 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 vehicle-mounted device ID collation device 300 is configured using an information processing device such as a mainframe, a workstation, or a personal computer. The vehicle-mounted device ID matching device 300 can be any device as long as it has the following functions. 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. Note that all or some of the functions of the vehicle-mounted device ID matching device 300 may be realized using hardware such as an ASIC, PLD, or FPGA.

  The IP communication unit 301 is a network interface with which the vehicle-mounted device ID matching 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 the vehicle-mounted device ID table 311. As shown in FIG. 2, the vehicle-mounted device ID record has values of the vehicle-mounted device ID and the mobile terminal ID.

  In the example shown in FIG. 2, the vehicle-mounted device ID record at the uppermost stage of the vehicle-mounted device ID table 311 has the vehicle-mounted device ID of “XXX” and the mobile terminal ID of “xxx @ xxx”. This vehicle-mounted device ID record indicates that the information controller 303 acquires the mobile terminal ID “xxx @ xxx” when the vehicle-mounted device ID received by the vehicle-mounted device ID matching device 300 is “XXX”. The vehicle-mounted device ID table 311 shown in FIG. 2 is merely one specific example. Therefore, the vehicle-mounted device ID table 311 may be configured in a mode different from that of FIG. 2.

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

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

  The 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 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 some of the functions of the entry / exit management device 400 may be implemented using hardware such as an ASIC, PLD, or FPGA.

  The IP communication unit 401 is a network interface for the entry / exit management device 400 to communicate with. 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 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. In the authentication control unit 402, the authentication processing unit 404 executes the authentication process of the 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 the 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 that is 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 that is registered in advance in the authentication information record by the user of the vehicle-mounted device 100 (hereinafter referred to as “vehicle-mounted device user”). The mobile 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 pictures, a line pattern, and the like. The mobile terminal password information may be biometric information such as a fingerprint or a face. The mobile terminal security code information may be a combination of a plurality of pieces of information.

  In the example shown in FIG. 2, in the authentication information record at the top of the authentication information table 411, the device ID is “xxx @ xxx”, the facility variable password information is “QQQQ”, and the mobile terminal password information is “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 entrance / exit management device 400, The authentication processing unit 404 determines that the authentication is successful. The authentication information table 411 shown in FIG. 2 is only one specific example. Therefore, the authentication information table 411 may be configured in a mode different from that of FIG. For example, the authentication information table 411 may include the date and time when the mobile terminal password information was updated.

  The authentication processing unit 404 executes an authentication process 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, the authentication processing unit 404 determines whether the collation 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 vehicle-mounted device. It is determined that 100 is a device having a legitimate authority. 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 determines that the vehicle-mounted device 100 is It is determined that the device does not have the proper 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 facility variable password information may be generated once a day, for example. As the facility variable password information, a random value is generated for each record.

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

  FIG. 3 is a schematic block diagram showing the functional configuration of the vehicle-mounted device 100. The vehicle-mounted device 100 is configured by using the ETC vehicle-mounted device mounted on the vehicle. The vehicle-mounted device 100 includes a network interface, a CPU connected to the bus, a memory, an auxiliary storage device, and the like. The vehicle-mounted device 100 functions as a device including the communication unit 101, the information control unit 102, the vehicle-mounted device information storage unit 103, the voice output unit 104, the display unit 105, and the card input / output unit 106 by executing the authentication program. In addition, all or a part of each function of the vehicle-mounted device 100 may be realized by using hardware such as ASIC, PLD, or FPGA. The authentication program may be recorded in a computer-readable recording medium. The computer-readable recording medium is, for example, a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, a portable medium such as a semiconductor storage device, or a storage device such as a hard disk or a semiconductor storage device built into a 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 in 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. The communication may be DSRC, for example.

  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 is transmitted to the vehicle-mounted device ID collation device 300 via the entry / 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 entry / 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, a WCN (Wireless Call Number) or a serial number of an ETC (Electronic Toll Collection System) vehicle-mounted device.

  The vehicle-mounted device information storage unit 103 is configured using a storage device such as a magnetic hard disk 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 an existing audio output device such as a speaker, an earphone, 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 the 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, and 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 the video output device connected to itself.

  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. Note that the example of FIG. 3 shows a configuration in which the card input / output unit 106 has one card slot and one card 107 is inserted. However, the configuration may be different from that 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 charge 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 issuing the card 107 (specifically, a credit card company or an institution affiliated with the credit card company), or a card 107 Information of a type indicating a service provided to the user is recorded in advance. In addition to the card information, the card 107 also records information about the entrance toll gate where the user started to use the road and information about the exit toll gate where the user finished using the road.

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

  The short-range wireless communication unit 501 is a network interface for the mobile terminal 500 to communicate. The short-distance wireless communication unit 501 is a communication unit for short-distance wireless communication 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 an input / output process for being authenticated by the entry / exit management device 400. The input / output control unit 502 transmits the input information to the entry / exit management apparatus 400 via the entry / exit roadside apparatus 200.

  The display unit 503 is a video output device such as a CRT display, a liquid crystal display, 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 the video output device connected to itself.

  The input unit 504 is configured using an existing input device such as a touch panel, buttons, switches and the like. The input unit 504 may be an interface for connecting the input device to the mobile terminal 500. In this case, the input unit 504 generates input data from the input signal input by 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 apparatus 200. When the input unit 504 is configured by using a touch panel, the input unit 504 and the display unit 503 may be integrally configured.

  Next, the operation will be described. FIG. 5 is a sequence diagram showing a processing flow of the entry / exit system 1 in the first embodiment. As a preliminary preparation, the vehicle-mounted device user notifies the vehicle-mounted device ID verification device 300 of the vehicle-mounted device ID and the mobile terminal ID. Further, the vehicle-mounted device user may transmit the vehicle-mounted device ID and the mobile terminal ID from the vehicle-mounted device 100 to the vehicle-mounted device ID collation device 300. Further, the vehicle-mounted device user may transmit the vehicle-mounted device ID and the mobile terminal ID from the mobile terminal 500 to the vehicle-mounted device ID matching device 300 (step S101). Next, the vehicle-mounted device ID collation device 300 executes registration processing of the received vehicle-mounted device ID and mobile terminal ID. Specifically, the vehicle-mounted device ID matching device 300 registers the vehicle-mounted device ID and the mobile terminal ID in the vehicle-mounted device ID table 311 in association with each other (step S102). The vehicle-mounted device ID matching device 300 transmits the mobile terminal ID to the entry / exit management device 400 (step S103). The vehicle-mounted device user transmits the mobile terminal password information determined by himself / herself to the entry / exit management device 400. Further, the vehicle-mounted device user may transmit the mobile terminal password information from the mobile 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 apparatus 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 concludes 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 the vehicle-mounted device ID to the entry / exit roadside device 200 via the communication unit 101 (step S201).

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

  The IP communication unit 301 notifies the information control unit 303 of the encrypted vehicle-mounted device ID. The information control unit 303 causes the decryption processing unit 304 to perform 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 vehicle-mounted device ID record having the same vehicle-mounted device ID from the vehicle-mounted device 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). When the vehicle-mounted device IDs do not match (step S205-NO), the vehicle-mounted device ID matching 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 acquires 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 having 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 entrance / exit roadside device 200 (steps S210 to S211).

  The information control unit 102 speaks 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 personal identification information via the display unit 105 (step S212).

  The collation information is input to the input unit 504 by the operation of the person who gets in 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 the collation information. The input / output control unit 502 transmits the verification 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 the collation information. In the authentication control unit 402, the authentication processing unit 404 executes the authentication process of the verification information. Specifically, the authentication processing unit 404 compares the matching information received from the mobile terminal 500 with the matching information stored in the authentication information record, and if a predetermined authentication condition is satisfied (for example, if they match), the authentication processing is performed. The unit 404 determines that the vehicle-mounted device 100 is a device having a proper authority. On the other hand, when the predetermined condition is not satisfied (for example, they do not match), the authentication processing unit 404 determines that the vehicle-mounted device 100 is a device that does not have the proper authority (step S216). The authentication control unit 402 transmits the authentication processing 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 processing execution result. The entrance / exit control unit 206 executes processing based on the authentication processing execution result (step S218). When the authentication process execution result is successful authentication (step S218-YES), the entry / exit control unit 206 transmits a gate opening instruction to the entry / exit suppressor 600 via the entry / exit communication unit 207 (step S219). On the other hand, when the authentication process execution result is not successful (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 a gate opening instruction. When the entry / exit control unit 602 receives the notification of the gate opening instruction, the entry / exit control unit 602 executes the gate opening process of the entry / exit suppressing unit 603 (step S221).

  In the process flow of FIG. 5, the verification information acquired in step S213 may be encrypted by the encryption processing unit 202. In such a case, when collation information is transmitted from the entry / exit roadside apparatus 200 to the entry / exit management apparatus 400 in step S215, tapping of the collation information can be prevented. As a result, it is possible to perform entrance / exit management with higher safety as compared with the case where the verification information is transmitted without executing the encryption process.

(Second embodiment)
First, the 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 in two or more places. For example, when vehicle management is performed on a premises such as a construction site, the construction company associates the vehicle-mounted device 100 with the entry / exit roadside device 200a. Therefore, when there are multiple construction sites, the linking work is a heavy burden on the construction company. Therefore, the entry / exit system 2 reduces the burden of this association. Specifically, the vehicle-mounted device ID matching 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 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, a facility name or an arbitrary character string. The vehicle-mounted device ID collation device 300a identifies the mobile terminal ID using the vehicle-mounted device 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, it is considered that the vehicle equipped with the vehicle-mounted device 100 is attempting 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. Therefore, the burden of the linking work by the construction company is reduced.

  Hereinafter, the entry / 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 the points different from the first embodiment will be described below. The entry / exit system 2 according to the first embodiment has an entry / exit roadside device 200a in place of the entry / exit roadside device 200 and an onboard device ID collation device 300a in place of the onboard device ID collation device 300. Unlike the entry / exit system 1, the other configurations are the same as the entry / exit system 1.

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

The vehicle-mounted device ID collation device 300a includes a device information storage unit 302a that stores a facility ID instead of the device information storage unit 302 that stores the vehicle-mounted device ID and the mobile terminal ID. The vehicle-mounted device ID collation device 300a controls the process of identifying the mobile terminal ID from the vehicle-mounted device ID, instead of the information control unit 303 that controls the process of identifying the mobile terminal ID from the vehicle-mounted device ID and the facility ID. Equipped with. The vehicle-mounted device ID collation device 300a includes a decryption processing unit 304a that executes a decryption process of an encrypted in-vehicle device ID and an encrypted facility ID instead of the decryption processing unit 304 that executes a decryption process of the encrypted in-vehicle device ID. Equipped with. The vehicle-mounted device ID collation device 300a has the same configuration as the vehicle-mounted device ID collation device 300 in other points.

The vehicle-mounted device ID table 311a is different from the vehicle-mounted device ID table 311 in the first embodiment in that the vehicle-mounted device ID table 311a further includes a facility ID column, and otherwise has the same configuration as the vehicle-mounted device ID table 311.

  In the example shown in FIG. 6, when the vehicle-mounted device ID record a at the top of the vehicle-mounted device ID table 311a is “XXX” for the vehicle-mounted device ID received by the vehicle-mounted device ID collation device 300a and “AAA” for the facility ID. The information control unit 303a indicates that the mobile terminal ID acquires "xxx @ xxx". The vehicle-mounted device ID table 311a shown in FIG. 6 is merely one specific example. Therefore, the vehicle-mounted device ID table 311a may be configured in a mode different from that of FIG. For example, the vehicle-mounted device ID table 311a may register a 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 associates 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 entry / exit system 2, a plurality of entry / exit roadside devices 200a are installed. Therefore, the business operator decides which entry / exit roadside device 200a the entry / exit of the vehicle-mounted device user enters / exits. Therefore, the business operator uses the vehicle-mounted device ID use consent form. The in-vehicle device ID use consent form indicates which in-and-out roadside device 200a the in-vehicle device user can enter and leave. The business operator obtains the in-vehicle device user's approval for the in-vehicle device ID use consent form. After that, the business operator registers the contents of the vehicle-mounted device ID use consent form in the vehicle-mounted device ID collation device 300a. After registration, the vehicle-mounted device user can enter / exit the entrance / exit roadside device 200a indicated in the consent form for using the vehicle-mounted device ID.

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

  Next, the business operator creates an in-vehicle device ID use consent form. In the vehicle-mounted device ID use consent form, "vehicle-mounted device user name", "vehicle-mounted device ID", "permit date", "mobile terminal ID", and "facility ID" are described. Note that the items in this vehicle-mounted device ID use consent form are merely specific examples. Therefore, the vehicle-mounted device ID use consent document may be configured with a different item from this vehicle-mounted device ID use consent document. For example, the vehicle-mounted device ID use consent form may include an item of facility name. Further, the vehicle-mounted device ID use consent form may be an electronic medium such as a web form (step S302).

  The business operator sends an in-vehicle device ID use consent form to the in-vehicle device user (step S303). The vehicle-mounted device user executes the approval process of the vehicle-mounted 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 vehicle-mounted device ID use agreement for which the approval process has been executed is regarded as the approved vehicle-mounted device ID use agreement (step S304). The vehicle-mounted device user sends the approved vehicle-mounted device ID use consent form to the business operator (step S305). The business operator transmits the approved vehicle-mounted device ID use consent form to the vehicle-mounted device ID collation device 300a. In addition, the business operator may send the approved vehicle-mounted device ID use consent form to the management organization of the vehicle-mounted device ID matching device 300a (step S306).

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

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

  The vehicle-mounted device communication unit 201 notifies the communication controller 203a of the vehicle-mounted device ID. The communication control unit 205a acquires the facility ID stored in the installer information storage unit 208a. The communication control unit 205a executes the 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 matching device 300a via the IP communication unit 204 (step S203a).

  The IP communication unit 301 notifies the information control unit 303a of the encrypted vehicle-mounted device ID and the encrypted facility ID. The information control unit 303a executes the 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 an on-vehicle device ID record having a matching on-vehicle device ID and facility ID from the on-vehicle device ID table 311a of the device information storage unit 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). When the vehicle-mounted device IDs do not match (step S205a-NO), the vehicle-mounted device ID matching device 300a ends the process (step S207). The information control unit 303a transmits the mobile terminal ID to the entry / exit management device 400 via the IP communication unit 301 (step S208).

  The IP communication unit 401 notifies the authentication control unit 402 of the mobile terminal ID. The authentication control unit 402 acquires 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 having 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 entrance / exit roadside device 200a (steps S210 to S211).

  The information control unit 102 speaks 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 personal identification information via the display unit 105 (step S212).

  The collation information is input to the input unit 504 by the operation of the person who gets in the vehicle (step S213). The input unit 504 notifies the input / output control unit 502 of the collation information. The input / output control unit 502 transmits the matching 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 the collation information. In the authentication control unit 402, the authentication processing unit 404 executes the authentication process of the verification information. Specifically, the authentication processing unit 404 compares the matching information received from the mobile terminal 500 with the matching information stored in the authentication information record, and if a predetermined authentication condition is satisfied (for example, if they match), the authentication processing is performed. The unit 404 determines that the vehicle-mounted device 100 is a device having a proper authority. On the other hand, when the predetermined condition is not satisfied (for example, they do not match), the authentication processing unit 404 determines that the vehicle-mounted device 100 is a device that does not have the proper 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 processing execution result. The entrance / exit control unit 206 executes processing based on the authentication processing execution result (step S218). When the authentication process execution result is successful authentication (step S218-YES), the entry / exit control unit 206 transmits a gate opening instruction to the entry / exit suppressor 600 via the entry / exit communication unit 207 (step S219). On the other hand, when the authentication process execution result is not successful (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 a gate opening instruction. When the entry / exit control unit 602 receives the notification of the gate opening instruction, the entry / exit control unit 602 executes the gate opening process of the entry / exit suppressing 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 entrance / exit system capable of entering / exiting with a simple configuration in a place such as a condominium parking lot where high security such as identity verification is not required, without using the mobile terminal 500. For this purpose, the following processing is executed.

  In the first embodiment, the authentication process using the facility variable personal identification information and the mobile terminal personal identification information transmitted from the mobile terminal 500 is executed, but in the third embodiment, the mobile terminal does not use these two pieces of information. The authentication process is executed only with the ID. In addition, in the first embodiment, the mobile terminal ID is transmitted from the mobile terminal 500 to the entry / exit management device 400, but in the third embodiment, the mobile terminal ID is input from the vehicle-mounted device ID matching device 300 without going through the mobile terminal 500. It is transmitted to the exit management device 400. With such a 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 entry / exit system 3 in the third embodiment. The entry / exit system 3 in the third embodiment differs from the first embodiment in that the mobile terminal 500 is not used. Only the points different from the first embodiment will be described below.

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

  The entry / exit management device 400b includes an authentication control unit 402b instead of the authentication control unit 402. The entry / exit management device 400b includes an authentication information storage unit 403b that stores a mobile terminal ID instead of the authentication information storage unit 403 that stores collation 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 collation 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 points.

  The authentication information storage unit 403b stores the 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 a mobile terminal ID of “xxx @ xxx”. In this authentication information record b, when the mobile terminal ID received from the vehicle-mounted device ID matching device 300 is “xxx @ xxx”, the authentication processing unit 404b determines that the authentication is successful. The authentication information table 411b shown in FIG. 9 is merely one specific example. Therefore, the authentication information table 411b may be configured in a mode different from that of 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 in the entry / exit system 3 according to the third embodiment until the use of the vehicle-mounted device ID and the mobile terminal ID is started. First, the vehicle-mounted device user transmits the vehicle-mounted device ID and the mobile terminal ID to the vehicle-mounted device ID matching device 300. Moreover, you may transmit from a web page. Further, the transmission may be transmitted to the management organization of the vehicle-mounted device ID collation device 300 (step S401). Next, the vehicle-mounted device ID matching device 300 executes a registration process of the vehicle-mounted device ID and the mobile terminal ID. Specifically, the vehicle-mounted device ID matching device 300 generates an vehicle-mounted device ID record in the vehicle-mounted device ID table. The vehicle-mounted device ID matching device 300 registers the vehicle-mounted device ID and 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 business operator (for example, an apartment management organization) (step S403). Upon receiving 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 matching device 300. In addition, the transmission may be performed for each vehicle-mounted device user. In addition, the transmission may be performed collectively after receiving the vehicle-mounted device IDs of all the vehicle-mounted device users. Moreover, you may transmit from a web page. Further, the transmission may be sent to the management organization of the vehicle-mounted device ID collation device 300 (step S404). The vehicle-mounted device ID matching device 300 identifies the mobile terminal ID using the vehicle-mounted device ID (step S405). The vehicle-mounted device ID matching device 300 transmits the mobile terminal ID to the entry / exit management device 400b (step S406). The entrance / exit management apparatus 400b registers the mobile terminal ID in the authentication information table 411b (step S407). With the above, the use of the vehicle-mounted device ID and the mobile terminal ID is started in the entry / exit system 3.

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

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

  The IP communication unit 301 notifies the information control unit 303 of the encrypted vehicle-mounted device ID. The information control unit 303 causes the decryption processing unit 304 to perform 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 vehicle-mounted device ID record having the same vehicle-mounted device ID from the vehicle-mounted device 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). When the vehicle-mounted device IDs do not match (step S205-NO), the vehicle-mounted device ID matching 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 the authentication process of the mobile terminal ID. Specifically, the authentication processing unit 404b compares the mobile terminal ID received from the vehicle-mounted device ID matching device 300 with the mobile terminal ID registered in the authentication information record b to satisfy a predetermined authentication condition (for example, match). In this case, the authentication processing unit 404b determines that the vehicle-mounted device 100 is a device that has the proper authority. On the other hand, when 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 a device that does not have the proper authority (step S216b). The authentication control unit 402b transmits the authentication processing 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 processing execution result. The entrance / exit control unit 206 executes processing based on the authentication processing execution result (step S218). When the authentication process execution result is successful authentication (step S218-YES), the entry / exit control unit 206 transmits a gate opening instruction to the entry / exit suppressor 600 via the entry / exit communication unit 207 (step S219). On the other hand, when the authentication process execution result is not successful (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 a gate opening instruction. When the entry / exit control unit 602 receives the notification of the gate opening instruction, the entry / exit control unit 602 executes the gate opening process of the entry / exit suppressing unit 603 (step S221).

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

  Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments 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 invention described in the claims and the equivalents thereof as well as included in the scope and the gist of the invention.

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 ... Voice output Numerals, 105 ... Display section, 106 ... Card input / output section, 107 ... Card, 200 ... Entrance / exit roadside apparatus, 201 ... On-board device communication section, 202 ... Encryption processing section, 203 ... Terminal communication section, 204 ... , 205 ... communication control unit, 206 ... entry / exit control unit, 207 ... entry / exit communication unit, 300 ... vehicle-mounted device ID collating device, 301 ... IP communication unit, 302 ... device information storage unit, 303 ... information control unit, 304 ... Decryption processing unit, 311 ... In-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 unit, 411 ... Authentication information table, 500 ... Mobile terminal, 501 ... Short-range wireless communication unit, 502 ... Input / output control unit, 503 ... Display unit, 504 ... Input unit, 600 ... Entrance / exit suppressor, 601 ... Communication Section, 602 ... Entrance / exit control section, 603 ... Entrance / exit suppression section, 200a ... Entrance / exit roadside device, 202a ... Encryption processing section, 205a ... Communication control section, 208a ... Installer information storage section, 300a ... Onboard unit ID collation Device, 302a ... Device information storage unit, 303a ... Information control unit, 304a ... Decryption processing unit, 311a ... In-vehicle 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 (8)

An entrance / exit system comprising an on-vehicle device ID collation device, an entrance / exit management device, and an entrance / exit roadside device,
The vehicle-mounted device ID collation device,
Based on the vehicle-mounted device ID that is the identification information of the vehicle-mounted device of the vehicle that has entered the entrance / exit system, the mobile terminal ID of the mobile terminal carried by the person who gets in the vehicle is specified, and the mobile terminal ID is used for the entry / exit. An information control unit for transmitting to the management device,
The entrance / exit management device,
The entry / exit management device includes an authentication processing unit that executes an authentication process on the verification information received,
The entrance / exit roadside device,
An entry / exit system including an entry / exit control unit that determines whether the entry / exit restraint unit is opened or closed based on a result of the authentication process. The entrance / exit management device executes an authentication process based on collation information input to a mobile terminal carried by a person who gets in the vehicle.
The entry / exit system according to claim 1. The vehicle-mounted device ID matching device specifies the mobile terminal ID based on the vehicle-mounted device ID and a facility ID that is identification information of the entrance / exit roadside device, and transmits the mobile terminal ID to the entrance / exit management device. ,
The entrance / exit system according to claim 1. The authentication processing unit executes an authentication process using the mobile terminal ID as collation information,
The entry / exit system according to claim 1. An entrance / exit control method performed by an entrance / exit system including an on-vehicle device ID collation device, an entrance / exit management device, and an entrance / exit roadside device,
The vehicle-mounted device ID collation device specifies a mobile terminal ID of a mobile terminal carried by a person who gets in the vehicle based on an vehicle-mounted device ID that is identification information of the vehicle-mounted device of the vehicle that has entered the entry / exit system. An information control step of transmitting the mobile 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 verification information received by the entrance / exit management device;
An entrance / exit control step in which the entrance / exit roadside device determines whether the entrance / exit restraint unit is opened or closed based on the result of the authentication process,
An entry / exit control method having: The entrance / exit management device executes an authentication process based on collation information input to a mobile terminal carried by a person who gets in the vehicle.
The entrance / exit control method according to claim 5. The vehicle-mounted device ID matching device specifies the mobile terminal ID based on the vehicle-mounted device ID and a facility ID that is identification information of the entrance / exit roadside device, and transmits the mobile terminal ID to the entrance / exit management device. ,
The entrance / exit control method according to claim 5. In the authentication processing step, the authentication processing is executed using the mobile terminal ID as collation information.
The entrance / exit control method according to claim 5.

Images