JP7508115B2 - Entrance/exit management system and entrance/exit management program - Google Patents

Description

The present invention relates to an entrance/exit management system and an entrance/exit management program.

Various methods have been proposed for cashless payment of parking fees. For example, Patent Document 1 discloses a technology that calculates parking fees based on data on the vehicle's entry time and departure time, transmits the calculated fees to a website server, and accepts payment of the parking fees on the website.

JP 2003-256995 A

However, in the conventional technology described in Patent Document 1, in order to properly manage vehicle entry and exit and settle parking fees, it is necessary to provide separate configurations for detecting when a vehicle enters and when a vehicle leaves. This requires a complex and large-scale system, which creates the problem that it is difficult to build and introduce a system for managing entry and exit and performing cashless settlement.

The present invention has been made in consideration of the above-mentioned problems. Therefore, an object of the present invention is to provide an entrance/exit management system and an entrance/exit management program that can appropriately and reliably perform entrance/exit management at a parking lot and cashless settlement of parking fees with a simple configuration.

The above objectives will be achieved by the following means:

The entrance/exit management system has an acquisition unit, a vehicle entrance/exit restriction unit, a judgment unit, a billing processing unit, and a control unit. The acquisition unit acquires identification information from a vehicle approaching an entrance/exit of a controlled area for parking the vehicle, the identification information including at least one of the following information: vehicle number information of the vehicle, unique information of an on-board device installed in the vehicle, and unique information of an ETC card inserted in the on-board device. The vehicle entrance/exit restriction unit is configured to be capable of restricting the entry of the vehicle into the controlled area and the exit of the vehicle from the controlled area. The judgment unit judges whether a vehicle approaching the entrance/exit of the controlled area is attempting to enter the controlled area or exit from the controlled area. The billing processing unit is configured to be capable of registering the identification information and information regarding a payment means selected by a person who bears the fee to be charged to the vehicle or the user of the vehicle for the parking in association with each other. When the determination unit determines that the vehicle is attempting to enter the controlled area, the control unit controls the vehicle entry/exit restriction unit to permit the vehicle to enter without executing a payment process related to the payment of the fee, and when the control unit determines that the vehicle is attempting to exit the controlled area, the control unit controls the vehicle entry/exit restriction unit to permit the vehicle to exit after executing a payment process related to the payment of the fee.

The entrance/exit management program is configured to cause the information processing device to function as the entrance/exit management system described above.

According to the entrance/exit management system of the present invention, identification information of a vehicle approaching the entrance/exit of a controlled area is obtained from the vehicle, and it is determined whether the vehicle approaching the entrance/exit of the controlled area is attempting to enter or exit the controlled area. If the entrance/exit management system determines that the vehicle is attempting to enter, it allows the vehicle to enter without executing a payment process, and if it determines that the vehicle is attempting to exit, it executes a payment process before allowing the vehicle to exit. Therefore, if the vehicle is attempting to enter, it is possible to allow the vehicle to enter without requesting a payment process, and if the vehicle is attempting to exit, it is possible to execute a payment process using the registered payment information before allowing the vehicle to exit. This makes it possible to properly and reliably perform entrance/exit management and parking fee settlement in a parking lot with a simple configuration.

1 is a diagram showing a schematic configuration of a system according to an embodiment of the present invention; FIG. 2 is a block diagram showing a schematic configuration of an acquisition device. FIG. 2 is a block diagram showing a schematic configuration of a detection device. 1 is a block diagram showing a schematic configuration of a vehicle entry/exit restriction device; FIG. 2 is a block diagram showing a schematic configuration of an information terminal. FIG. 2 is a block diagram showing a schematic configuration of a server. 2 is a block diagram showing a functional configuration of a control unit of the server. FIG. 11 is a diagram illustrating an example of information stored in a server. 2 is a block diagram showing a schematic configuration of an ETC vehicle-mounted unit; FIG. 1 is a block diagram showing a schematic configuration of a payment system. 11 is a flowchart showing a procedure of a process executed by a server. 10 is a subroutine flowchart showing an example of a procedure of a process in step S102 of FIG. 9 . 10 is a subroutine flowchart showing another example of the procedure of the determination process in step S102 of FIG. 9 . 10 is a subroutine flowchart showing the procedure of the payment process in step S108 of FIG. 9. 12 is a subroutine flowchart continuing from FIG. 11 .

Hereinafter, an embodiment of the present invention will be described with reference to the attached drawings. In the description of the drawings, the same elements are given the same reference numerals, and duplicated description will be omitted. In addition, the dimensional ratios of the drawings may be exaggerated for the convenience of explanation and may differ from the actual ratios.
(Overall system configuration)

Figure 1 shows the schematic configuration of a system according to one embodiment of the present invention.

As shown in FIG. 1, system 1 is composed of an in-vehicle system 10, an information terminal 20, a server 30, an ETC vehicle unit 40, and a payment system 50. The in-vehicle system 10, the information terminal 20, the server 30, and the payment system 50 are connected via a network, and each component can communicate using various wired or wireless communication methods. The ETC vehicle unit 40 can wirelessly communicate with the acquisition device 110 of the in-vehicle system 10 using a specific communication standard such as DSRC (Dedicated Short Range Communication).

The on-site system 10 is installed in a controlled area, such as a paid parking lot for parking vehicles. The on-site system 10 includes an acquisition device 110, a detection device 120, and an entry/exit control device 140.

The acquisition device 110 is equipped with an ETC antenna and communicates wirelessly with an ETC vehicle unit 40 mounted on a vehicle near the entrance/exit of the controlled area using a communication standard such as DSRC. The acquisition device 110 also has a camera and takes images of vehicles entering and exiting the controlled area.

The detection device 120 is equipped with various sensors and detects vehicles that are within a controlled area and approaching a specified range near the entrance and exit of the controlled area.

The entry/exit control device 140 is, for example, an entry/exit gate installed at the entrance/exit of a controlled area, and has an entry/exit control unit that can control the entry of vehicles into the controlled area and the exit of vehicles from the controlled area.

The information terminal 20 is a terminal for a user to register payment information, etc. The information terminal 20 is, for example, a terminal such as a smartphone used by the driver of the vehicle. The information terminal 20 communicates with the server 30, etc. via a network.

The server 30 transmits and receives various information between each component of the in-venue system 10, the information terminal 20, the payment system 50, etc.

The ETC vehicle-mounted device 40 is attached to the vehicle and performs wireless communication with the acquisition device 110 that is located within a predetermined distance. The ETC vehicle-mounted device 40 acquires various information from the inserted ETC card and transmits it to the acquisition device 110.

The payment system 50 is a system installed in a payment institution (financial institution) such as a bank or credit card company, or in a payment agent that handles various operations for making payments at such payment institutions.

In this embodiment, an example will be described in which the server 30 constitutes the entrance/exit management system. Note that the processing executed by the server 30 may be executed by other components such as the acquisition device 110 and the detection device 120. In this case, the components constitute the entrance/exit management system. Also, the server 30 and the other components may operate in cooperation with each other, and the server 30 and the other components may constitute the entrance/exit management system.
Each component will be described in detail below.
(Acquisition device 110)

Figure 2A is a block diagram showing the general configuration of the acquisition device.

As shown in FIG. 2A, the acquisition device 110 includes a control unit 111, a memory unit 112, a communication unit 113, an ETC antenna 114, and a camera 115. Each component is connected to each other via a bus so that they can communicate with each other. In addition, each component may be connected to the server 30 directly via a network without using a bus.

The control unit 111 is equipped with a CPU (Central Processing Unit) and, in accordance with a program, controls the components described above, as well as the components of the in-venue system 10 and executes various calculation processes.

The storage unit 112 includes a ROM (Read Only Memory) that stores various programs and data in advance, a RAM (Random Access Memory) that temporarily stores programs and data as a working area, and a hard disk that stores various programs and data.

The communication unit 113 has an interface for communicating with other terminals and devices via a network. The communication unit 113 transmits and receives various data, etc., to and from the server 30, for example.

The ETC antenna 114 is configured to perform wireless communication with the ETC vehicle-mounted unit 40 using a specified communication standard. The acquisition device 110 acquires an on-board unit ID, represented by a wireless call number (WCN), which is unique information for identifying the ETC vehicle-mounted unit 40, from the ETC vehicle-mounted unit 40 via the ETC antenna 114. The acquisition device 110 also acquires an ETC card number, which is unique information for identifying the ETC card inserted into the ETC vehicle-mounted unit 40, from the ETC vehicle-mounted unit 40 via the ETC antenna 114. The ETC card number is acquired in an encrypted state, and can be decrypted before being transmitted to the upper server 30, for example.

The camera 115 photographs vehicles entering and exiting the controlled area. By analyzing the images photographed by the camera 115, information indicating the vehicle number (vehicle number plate) of the vehicle is obtained.
(Detection device 120)

Figure 2B is a block diagram showing the general configuration of the detection device.

As shown in FIG. 2B, the detection device 120 includes a control unit 121, a memory unit 122, a communication unit 123, and a detection unit 124. The components are connected to each other via a bus so that they can communicate with each other. In addition, if the detection device 120 is a device that does not include the control unit 121, the memory unit 122, etc., the detection unit 124 may be configured to be connected to the control unit 111 of the acquisition device 110.

The control unit 121, memory unit 122, and communication unit 123 of the detection device 120 are similar to the corresponding configurations of the acquisition device 110, so duplicated explanations will be omitted.

The detection unit 124 is configured to detect the approach of a vehicle within a specified range near the entrance/exit of the controlled area, and may be configured with various sensors such as a loop coil, a laser lidar (LiDAR: Light Detection and Ranging), a camera, etc. Each of the various sensors described above may be used alone, or multiple sensors may be used in combination.

For example, if a loop coil that electromagnetically detects the approach of a vehicle is used as the detection unit 124, the loop coil is placed within the controlled area near the entrance/exit of the controlled area, such as under the roadway that vehicles travel when exiting the controlled area.

In addition, when a laser lidar is used as the detection unit 124, the laser lidar is installed in a position within the controlled area whose detection range includes a predetermined range near the entrance/exit of the controlled area. By analyzing the image information acquired by the laser lidar, it is detected that the vehicle is within the controlled area and has approached a predetermined range near the entrance/exit of the controlled area.

In addition, when a camera is used as the detection unit 124, the camera is installed in a position within the controlled area that includes a predetermined range near the entrance/exit of the controlled area within its capture range. By analyzing images (video) continuously captured by the camera, it is detected that a vehicle is within the controlled area and has approached a predetermined range near the entrance/exit of the controlled area. Image (video) recognition can be performed using known techniques, such as background subtraction or methods using machine learning.

The sensors that can be used as the detection unit 124 are not limited to the above examples, and may be, for example, a contact sensor that comes into contact with a vehicle to detect the passage of the vehicle, a weight sensor that detects the passage of the vehicle based on the weight of the passing vehicle, etc. Alternatively, an infrared sensor, a sonic sensor, a geomagnetic sensor, etc. provided at a position where the vehicle can be detected may be used.
(Entry/Exit Control Device 140)

Figure 2C is a block diagram showing the general configuration of the entry and exit control device.

As shown in FIG. 2C, the entrance/exit control device 140 includes a control unit 141, a communication unit 142, and an entrance/exit control unit 143. The components are connected to each other via a bus so that they can communicate with each other. In addition, if the entrance/exit control device 140 does not include the control unit 141 or the communication unit 142, the entrance/exit control unit 143 may be configured to be connected to the control device of the acquisition device 110.

The control unit 141 and communication unit 142 of the entry/exit control device 140 are similar to the corresponding configurations of the acquisition device 110, so duplicate explanations will be omitted.

The entry/exit restriction unit 143 is a configuration for restricting the entry and exit of vehicles into the controlled area. The entry/exit restriction unit 143 is configured, for example, by a gate (bollard) or a bar that is arranged at the entrance and exit of the controlled area and operates to block or allow the passage of the vehicle. For example, when the entry and exit of a vehicle into the controlled area is permitted, the entry/exit restriction unit 143 permits the vehicle to enter and exit the controlled area, and restricts the entry and exit of the vehicle again after the vehicle has entered and exited. Note that the method of realizing the entry/exit restriction unit 143 is not limited to the above example, and may be realized by any configuration as long as it is a configuration that can restrict the entry and exit of a vehicle.
(Information terminal 20)

Figure 3 is a block diagram showing the general configuration of an information terminal.

As shown in FIG. 3, the information terminal 20 includes a control unit 21, a memory unit 22, a communication unit 23, a display unit 24, and an operation reception unit 25. Each component is connected to each other via a bus so that they can communicate with each other. The control unit 21, memory unit 22, and communication unit 23 of the information terminal 20 are similar to the corresponding configurations of the acquisition device 110, so duplicated explanations will be omitted.

The display unit 24 includes an LCD (liquid crystal display), an organic EL display, etc., and displays various information. The operation reception unit 25 includes a touch sensor, a pointing device such as a mouse, a keyboard, etc., and receives various operations from the user. The display unit 24 and the operation reception unit 25 may form a touch panel by superimposing a touch sensor as the operation reception unit 25 on the display surface as the display unit 24.
(Server 30)

Figure 4 is a block diagram showing the general configuration of the server. Figure 5 is a block diagram showing the functional configuration of the control unit of the server. Figure 6 is a diagram showing an example of information stored in the server.

As shown in FIG. 4, the server 30 includes a control unit 31, a memory unit 32, and a communication unit 33. The components are connected to each other via a bus so that they can communicate with each other. The control unit 31, memory unit 32, and communication unit 33 of the server 30 are similar to the corresponding configurations of the acquisition device 110, so duplicated explanations will be omitted.

As shown in FIG. 5, the control unit 31 of the server 30 functions as an acquisition unit 311, a vehicle entry/exit restriction unit 312, a judgment unit 313, a billing processing unit 314, and a control unit 315 by loading a program and executing processing. The control unit 31 may also be configured to distribute some of its functions to the control units in each component of the in-venue system 10. For example, the control unit 31 may function as a detection unit based on detection information from the detection unit 124 of the detection device 120.

The acquisition unit 311 acquires, from the acquisition device 110, identification information including at least one of the vehicle number information of a vehicle located within a specified range, the unique information (vehicle unit ID) of the ETC vehicle unit 40 installed in the vehicle, and the unique information (ETC card number) of the ETC card inserted into the ETC vehicle unit 40.

The vehicle entry/exit restriction unit 312 controls the entry/exit restriction device 140 to restrict the entry of vehicles into and the exit of vehicles from the controlled area.

The billing processing unit 314 registers the identification information acquired by the acquisition unit 311 in association with information regarding the payment method selected by the person who bears the fee charged to the vehicle or the vehicle user for parking the vehicle.

The server 30, as the billing processing unit 314, provides a dedicated web page that the user can access using the information terminal 20 in order to associate and register the above information based on instructions from the user. The dedicated web page is provided, for example, using a different URL for each parking lot. For example, when the user's information terminal 20 connects to a server corresponding to the URL via a wireless LAN network, beacon, NFC (Near Field Communication), two-dimensional barcode, etc. provided in the parking lot, the web page of the URL is set to be displayed on the information terminal 20. This allows users who use the parking lot to easily access the web page and register the necessary information.

Next, we will explain the information stored in the memory unit 32 of the server 30.

As shown in FIG. 6, the storage unit 32 of the server 30 stores identification information, payment information, and user information in association with each other. The identification information includes the vehicle-mounted device ID, ETC card number, and vehicle number. The payment information includes credit card information, bank account information, and various information for using other payment schemes. The payment information is used as information regarding the payment method selected by the person who bears the fee charged to the vehicle or the user of the vehicle. The payment information also includes information indicating that the fee is allowed to be automatically paid by a predetermined method when the vehicle leaves the race. The user information includes user identification information, contact information, authentication information, and the like for identifying the user. The user identification information includes, for example, name, address, date of birth, gender, nickname, driver's license number, and the like. The contact information includes, for example, telephone number, email address, ID for SNS and various message services, and the like. The authentication information stores an ID, password, and the like for accessing a member-only website, and the like.

In addition, the memory unit 32 of the server 30 stores information for identifying each controlled area and information for identifying the acquisition device 110 or the detection device 120 installed in each controlled area in association with each other. In this embodiment, an example in which one acquisition device 110 and one detection device 120 are installed for each controlled area has been described, but this is not limited to this. For example, in a controlled area that has multiple vehicle entrances and exits, multiple acquisition devices 110 and multiple detection devices 120 may be installed.

The memory unit 32 of the server 30 also stores identification information of vehicles housed within the controlled area. For example, when a vehicle enters the controlled area, the server 30 stores (registers) the identification information of the vehicle in a database provided in the memory unit 32 to keep track of vehicles being housed. When the vehicle leaves the controlled area, the server 30 may erase (delete) the identification information of the vehicle from the database of the memory unit 32, or may store in the database of the memory unit 32 a message that the vehicle is not housed, in association with the identification information of the vehicle.

In addition, the above information described as being stored in the memory unit 32 may be stored in external storage that can be connected to the server 30 via a network, and may be configured to be accessed and retrieved from the server 30 as needed.
(ETC vehicle unit 40)

Figure 7 is a block diagram showing the general configuration of an ETC vehicle unit.

As shown in FIG. 7, the ETC vehicle unit 40 includes a control unit 41, a memory unit 42, a communication unit 43, a card acceptance unit 44, and an output unit 45. Each component is connected to each other via a bus so that they can communicate with each other. The control unit 41, memory unit 42, and communication unit 43 of the ETC vehicle unit 40 are similar to the corresponding configurations of the acquisition device 110, so duplicate explanations will be omitted.

The card acceptance unit 44 accepts the insertion of an ETC card. The card acceptance unit 44 acquires various information, including the ETC card number, from the inserted ETC card. The control unit 41 transmits the information acquired by the card acceptance unit 44 to the acquisition device 110 via the communication unit 43.

The output unit 45 is configured to output light and sound, and is composed of, for example, an indicator lamp that shows the ETC card reading status and a speaker that outputs audio guidance.

The storage unit 42 stores an in-vehicle device ID, which is represented by a wireless call number (WCN), which is unique information for identifying the ETC in-vehicle device 40 as a wireless base station. Therefore, the acquisition device 110 can acquire the in-vehicle device ID of the ETC in-vehicle device 40 when performing wireless communication with the ETC in-vehicle device 40 via the ETC antenna 114.
(Payment system 50)

Figure 8 is a block diagram showing the general configuration of the payment system. Figure 9 is a diagram showing an example of information related to ETC card numbers stored in the payment system.

As shown in FIG. 8, the payment system 50 includes a control unit 51, a memory unit 52, and a communication unit 53. The components are connected to each other via a bus so that they can communicate with each other. The control unit 51, memory unit 52, and communication unit 53 of the payment system 50 are similar to the corresponding configurations of the acquisition device 110, so duplicated explanations will be omitted.

The payment system 50 is a system installed in, for example, a payment institution (financial institution) such as a bank or credit card company, a payment institution that provides various code payment services, or a payment agent that handles various tasks for making payments at these payment institutions. The server 30 can send and receive information to and from the payment system 50 to execute payment of parking fees by credit card payment, bank account transfer, etc.

The payment system 50 may also store information regarding the credit card associated with the user's ETC card, and information indicating whether the user's ETC card has been rejected (set as invalid) by the ETC card issuer. The above information is stored in the memory unit 52 of the payment system 50. Note that the payment system 50 does not need to store rejection information associated with the ETC card number. In this case, for example, the ETC card number may be converted into credit card information, and whether the credit card has been rejected may be confirmed with the credit card company each time.

The system 1 may include configurations other than those described above. Each of the above configurations may include components other than those described above, or may not include some of the above-mentioned components. Each of the above configurations may be configured by a plurality of devices, or may be configured as an integrated unit. A function described as being performed by a certain configuration may be performed by another configuration instead.
An overview of the processing in the system will be explained.
(Outline of processing)

Figure 9 is a flowchart showing the procedure of the process executed by the server. Figure 10A is a subroutine flowchart showing an example of the procedure of the process of step S102 in Figure 9. Figure 10B is a subroutine flowchart showing another example of the procedure of the judgment process of step S102 in Figure 9. Figure 11 is a subroutine flowchart showing the procedure of the payment process of step S108 in Figure 9. The processes shown in the flowcharts of Figures 9 to 11 are stored as programs in the memory unit 32 of the server 30, and are executed by the control unit 31 controlling each unit.

As shown in FIG. 9, the server 30 determines whether or not vehicle identification information has been acquired from the acquisition device 110 (step S101).

If the identification information has not been acquired (step S101: NO), the server 30 waits until the identification information is acquired.

If the identification information is acquired (step S101: YES), the server 30 judges whether the vehicle is entering a controlled area or is exiting a controlled area (step S102). Details of the judgment process will be described later with reference to Figures 10A and 10B.

If it is determined in the processing of step S102 that entry is being attempted (step S103: YES), the server 30 controls the entry/exit control device 140 to permit the vehicle to enter the controlled area (step S104).

Next, the server 30 determines whether or not the entry of the vehicle has been completed (step S105). For example, the server 30 determines whether or not the entry of the vehicle has been completed based on the detection results of the detection device 120, the images captured by the camera 115, etc.

If entry has not been completed (step S105: NO), the server 30 waits until entry is completed.

If entry is complete (step S105: YES), the server 30 controls the entry/exit control device 140 to restrict the entry and exit of vehicles into the controlled area (step S106), and ends the process.

On the other hand, if it is determined in the processing of step S102 that the participant is about to participate (step S103: NO, step S107: YES), the server 30 executes the payment processing (step S108). Details of the payment processing will be described later with reference to FIG. 11. Note that if it is not determined that the participant is about to participate either (step S107: NO), the server 30 returns to step S101 and continues the processing. Also, the order and method of the processing of steps S102, S103, and S107 are not limited to the example of FIG. 9, and can be executed in any order and method.

Next, the server 30 controls the entry/exit control device 140 to allow the vehicle to exit the controlled area (step S109).

Next, the server 30 determines whether the vehicle has exited (step S110). For example, the server 30 determines whether the vehicle has exited based on an image captured by the camera 115, etc.

If participation has not been completed (step S110: NO), the server 30 waits until participation is completed.

If the exit is completed (step S110: YES), the server 30 controls the entrance/exit control device 140 to regulate the entry/exit of the vehicle into the controlled area (step S111), and ends the process. At this time, the server 30 may notify the information terminal 20 of the user of the exited vehicle of information indicating the name of the parking lot, the entry date/time, the exit date/time, the parking fee, the payment method used, etc., as usage authentication information.
<Decision-making process>

Next, the determination process shown in step S102 in FIG. 9 will be described below with two patterns.
<Pattern 1>

As shown in FIG. 10A, the server 30 refers to the database in the memory unit 32 (step S201) and determines whether the identification information acquired in the processing of step S101 in FIG. 9 is stored as the identification information of a vehicle housed in the controlled area (step S202).

If it is stored as the identification information of a vehicle housed in a controlled area (step S202: YES), the server 30 determines that the vehicle is about to leave the controlled area since the vehicle is already housed in the controlled area (step S203), and ends the determination process.

On the other hand, if the information is not stored as the identification information of a vehicle housed in the controlled area (step S202: NO), the server 30 determines that the vehicle is attempting to enter the controlled area since the vehicle has not yet been housed in the controlled area (step S204), and terminates the determination process.
<Pattern 2>

As shown in FIG. 10B, the server 30 checks the detection status of the detection device 120 that detects a vehicle approaching within a specified range near the entrance/exit of the controlled area (step S211), and determines whether the detection device 120 has detected a vehicle (step S212).

If the detection device 120 detects a vehicle (step S212: YES), the server 30 determines that the vehicle is attempting to exit the controlled area because the vehicle is present near an entrance/exit within the controlled area (step S213), and ends the determination process.

If the detection device 120 does not detect a vehicle (step S212: NO), the server 30 determines that the vehicle is attempting to enter the controlled area because there is no vehicle near the entrance/exit of the controlled area (step S214), and terminates the determination process.
<Payment Processing>

Next, the payment process shown in step S108 of FIG. 9 will be described below.

As shown in Figures 11 and 12, the server 30 determines whether or not payment information related to the payment method used to pay the parking fee is associated with and registered in the identification information acquired in the process of step S101 in Figure 9 (step S301). Specifically, the server 30 refers to the database in the storage unit 32 and determines whether or not payment information such as credit card information, bank account information, etc. is associated with and stored in the acquired identification information.

If payment information has not been registered (step S301: NO), the server 30 outputs a screen that enables the user, who is responsible for the parking fee, to search for vehicle numbers registered in the memory unit 32 of the server 30 using at least a portion of the vehicle number (step S302). The screen output by the server 30 is displayed on the information terminal 20 used by the user. This allows the user to search for vehicle numbers (identification information) stored in the memory unit 32 of the server 30 simply by inputting a portion of the vehicle number that is easy to understand and remember into the search screen.

In this embodiment, the server 30 executes the process of step S303 after executing the processes of steps S301 and S302, but the present invention is not limited to this. For example, if the user is aware that he or she has not registered payment information, the user may access the server 30 using the information terminal 20 at any time before the vehicle leaves the controlled area. In this case, the server 30 executes the processes of steps S303 to S305 before executing the processes of steps S301 and S302, and stores information in the storage unit 32 that the payment process has been completed. When the user leaves the controlled area in this state, the server 30 executes the process of step S301, and can confirm that the identification information (vehicle number, etc.) is associated with the payment information and registered in the storage unit 32, and that the payment process has also been completed, so the server 30 may skip the processes of steps S306 and S307 and end the payment process. For example, by informing the user in advance as described above, the registration process and payment process can be executed in advance, so that there is no need to execute the registration process and payment process near the entrance/exit of the controlled area when the vehicle leaves the controlled area, and the vehicle can be smoothly exited from the controlled area.

The server 30 outputs a screen for accepting the user's registration of associated payment information for the vehicle number (identification information) searched for using the screen output in the processing of step S302 (step S303).

The server 30 determines whether the payment information has been registered in association with the vehicle number (identification information) (step S304). At least one of the vehicle-mounted unit ID and the ETC card number is also stored in the memory unit 32 of the server 30 in association with the vehicle number. Therefore, when payment information is registered in association with the vehicle number, the payment information is also stored in association with at least one of the vehicle-mounted unit ID and the ETC card obtained from the ETC vehicle-mounted unit 40 of the vehicle. The server 30 may also accept registration of information regarding automatic payment using the above payment information (information indicating that automatic payment is permitted) from the user.

If the payment information is not associated and registered (step S304: NO), the server 30 repeats the process of step S304.

If the payment information is associated and registered (step S304: YES), the server 30 executes a process to pay the parking fee using the payment information and parking fee amount information calculated based on a specified fee table, etc. (step S305), and ends the payment process.

On the other hand, if it is determined in the processing of step S301 that payment information has been registered (step S301: YES), the server 30 further determines whether information regarding automatic payment using the payment information (information indicating that automatic payment is permitted) has been registered in the memory unit 32 by the user (step S306).

If information regarding automatic payment has been registered (step S306: YES), the server 30 executes processing to pay the parking fee using the payment information and parking fee amount information calculated based on a specified fee table, etc. (step S307), and ends the payment processing. At this time, the server 30 may, for example, notify the user's information terminal 20 that automatic payment will be performed at the time of exit and therefore there is no need to execute a separate payment process, or may notify the user of information regarding the payment method to be used for automatic payment. The notification may also be used to confirm whether automatic payment will be performed using the payment method registered at the time of exit.

On the other hand, if it is determined in the process of step S306 that information regarding automatic payment is not registered (step S306: NO), the server 30 outputs a screen for accepting the selection of a payment method and a payment instruction from the user (step S308). Specifically, the server 30 displays a screen for accepting the selection of a payment method to be used by the user and accepts the selection from the user. The selection of the payment method may be accepted from among the payment methods for which the user has registered payment information in advance, or the user may input payment information as a new payment method. When payment information for a new payment method is input, the server 30 associates the identification information such as the vehicle-mounted device ID, ETC card number, and vehicle number stored in the memory unit 32 with the payment information input by the user and registers them in the database of the memory unit 32. Furthermore, the server 30 accepts an instruction (payment instruction) to pay the parking fee using the selected payment information from the user by pressing a payment button displayed on the web page, etc. Note that, like the processes of steps S303 to S305 described above, the processes of steps S308 to S310 may be executed at any timing by the user operating the information terminal 20, etc.

The server 30 determines whether the selection of the payment method and payment instructions have been accepted (step S309).

If not accepted (step S309: NO), the server 30 repeats the process of step S309.

If the request has been accepted (step S309: YES), the server 30 executes the parking fee payment process using the above payment information and parking fee amount information calculated based on a specified fee table, etc. (step S310), and ends the payment process.

According to the above embodiment, the following effects are achieved.
The entrance/exit management system (server 30) acquires identification information of a vehicle approaching the entrance/exit of the controlled area from the vehicle, and judges whether the vehicle approaching the entrance/exit of the controlled area is entering or leaving the controlled area. If the entrance/exit management system judges that the vehicle is entering, it allows the vehicle to enter without executing a payment process, and if it judges that the vehicle is leaving, it executes a payment process and then allows the vehicle to leave. Therefore, if the vehicle is entering, it can allow the vehicle to enter without requesting a payment process, and if the vehicle is leaving, it can execute a payment process using the registered payment information and then allow the vehicle to leave. This allows the entrance/exit management and the settlement of parking fees in a parking lot to be performed appropriately and reliably with a simple configuration.

The entrance/exit management system also has a memory unit that stores identification information of vehicles housed within the controlled area, and when the identification information is acquired, if the identification information is not stored as identification information of a vehicle housed within the controlled area, it determines that the vehicle is attempting to enter, and when the identification information is stored as identification information of a vehicle housed within the controlled area, it determines that the vehicle is attempting to exit. As a result, when the identification information is acquired, the entrance/exit management system can determine whether the vehicle is attempting to enter or exit simply by referring to the information stored in the memory unit. Therefore, with a simple configuration and processing, entrance/exit management at the parking lot and settlement of parking fees can be performed appropriately and reliably.

The entrance/exit management system also has a detection unit that detects vehicles within a specified range near the entrance/exit within the controlled area, and when identification information is acquired, if the vehicle is not detected by the detection unit, it determines that the vehicle is attempting to enter, and if the vehicle is detected by the detection unit, it determines that the vehicle is attempting to exit. This allows the entrance/exit management system to determine whether the vehicle is attempting to enter or exit when identification information is acquired, simply by checking the detection status by one detection unit. Therefore, with a simple configuration and processing, entrance/exit management at the parking lot and settlement of parking fees can be performed appropriately and reliably.

Furthermore, when executing payment processing, the entry/exit management system checks the registration of information related to the payment method in the billing processing unit, and if it is registered that the fee will be paid automatically upon exit, it allows the vehicle to exit without confirming payment with the user. This allows the user to instantly exit the vehicle from the controlled area without having to consciously execute the payment process. This eliminates the need to keep users who are in a hurry waiting or to have them perform complicated operations, dramatically improving the convenience of the parking lot for users.

Furthermore, when executing payment processing, the entry/exit management system checks the registration of information relating to the payment method in the billing processing unit, and if it is not registered that the fee will be paid automatically upon entry, it outputs a screen to confirm payment to the user, and allows the vehicle to exit if it receives instructions from the user regarding permission to pay. As a result, if it is not registered that the fee will be paid automatically, it is possible to allow the vehicle to exit only after receiving payment instructions from the user, making it possible to more appropriately manage entry and exit to the parking lot and settle parking fees.

Furthermore, when executing payment processing, the entrance/exit management system checks whether information relating to the payment method has been registered in the billing processing unit, and if information relating to the payment method has not been registered, outputs a screen for the user to register information relating to the payment method, and if registration of information relating to the payment method is accepted from the user, executes the payment processing and registers information relating to the payment method in the billing processing unit in association with the identification information. In this way, if information relating to the payment method has not been registered, the user can be prompted to execute the payment processing and register the payment method. Therefore, parking fee settlement can be carried out more efficiently and reliably.

The present invention is not limited to the above-described embodiment, and various modifications and improvements are possible within the scope of the claims.

For example, in the above embodiment, the information terminal 20 has been described as a terminal that is owned by the user. However, the information terminal 20 may be a shared terminal installed in a parking lot or the like. In this case, even if the user does not own the information terminal, the user can perform operations such as registering necessary information.

The processing of the system according to the embodiment described above may include steps other than those in the flowchart described above, or may not include some of the steps described above. The order of the steps is not limited to the embodiment described above. Each step may be combined with other steps and executed as one step, may be included in other steps and executed, or may be divided into multiple steps and executed. For example, in the flowchart of FIG. 9, an example is described in which the detection process of step S101 is performed before the acquisition process of step S102, but this is not limited thereto, and the acquisition process of step S102 may be performed first.

The means and methods for performing various processes in each device of the system according to the above-mentioned embodiment can be realized by either a dedicated hardware circuit or a programmed computer. The above programs may be provided, for example, by a computer-readable recording medium such as a CD-ROM (Compact Disc Read Only Memory), or may be provided online via a network such as the Internet. In this case, the programs recorded on the computer-readable recording medium are usually transferred to and stored in a storage unit such as a hard disk. The above programs may be provided as standalone application software, or may be incorporated into the software of each device of the system as a function of that device.

1. System,
10. In-house system,
110 Acquisition device,
111 control unit,
112 memory unit,
113 Communications Department,
114 ETC antenna,
115 Camera,
120 Detection device,
121 control unit,
122 memory unit,
123 Communications Department,
124 detection unit,
140 Vehicle control device,
141 control unit,
142 Communications department,
143 Entry and Exit Control Department,
20 information terminal,
21 control unit,
22 memory unit,
23 Communications Department,
24 display unit,
25 Operation reception unit,
30 servers,
31 control unit,
311 Acquisition unit,
312 Vehicle Entry and Exit Control Section;
313 Judgment unit,
314 billing processing unit,
315 control unit,
32 memory unit,
33 Communications Department,
40 ETC on-board unit,
41 control unit,
42 memory unit,
43 Communications Department,
44 Card acceptance section,
45 output unit,
50 Payment systems,
51 control unit,
52 memory unit,
53 Communications Department.

Claims (6)

an acquisition unit that acquires, from a vehicle approaching an entrance/exit of a controlled area for parking vehicles, identification information including at least one of the following information: vehicle number information of the vehicle, unique information of an on-board device installed in the vehicle, and unique information of an ETC card inserted in the on-board device;
a vehicle entry/exit control unit capable of controlling entry of the vehicle into the controlled area and exit of the vehicle from the controlled area;
a determination unit that determines whether a vehicle approaching an entrance/exit of the controlled area is attempting to enter the controlled area or exit the controlled area;
a billing processing unit capable of registering the identification information and information regarding a payment method selected by a person who bears the fee to be charged to the vehicle or the user of the vehicle for the parking in association with each other;
a control unit that controls the vehicle entry/exit regulation unit to permit entry of the vehicle without executing a payment process related to the payment of the fee when the determination unit determines that the vehicle is attempting to enter the controlled area, and controls the vehicle entry/exit regulation unit to permit exit of the vehicle after executing a payment process related to the payment of the fee when the determination unit determines that the vehicle is attempting to exit the controlled area;
having
a storage unit that stores the identification information of vehicles housed in the controlled area;
The judgment unit, when the identification information is acquired by the acquisition unit, determines that the vehicle is attempting to enter if the identification information is not stored as the identification information of the accommodated vehicle, and determines that the vehicle is attempting to exit if the identification information is stored as the identification information of the accommodated vehicle. A detection unit that detects a vehicle approaching a predetermined range in the vicinity of the entrance/exit within the controlled area,
The entry/exit management system of claim 1, wherein the judgment unit judges that the vehicle is attempting to enter if the vehicle is not detected by the detection unit when the identification information is acquired by the acquisition unit, and judges that the vehicle is attempting to exit if the vehicle is detected by the detection unit. The control unit, when executing the payment processing, checks the registration of information regarding the payment means in the billing processing unit, and if it is registered that the fee will be paid automatically upon entry, controls the vehicle entry/exit restriction unit to allow the vehicle to exit without confirming payment to the user. The control unit, when executing the payment processing, checks the registration of information regarding the payment means in the billing processing unit, and if it is not registered that the fee will be automatically paid at the time of exit, outputs a screen for confirming payment to the user, and when an instruction regarding permission for the payment is received from the user, controls the vehicle entry/exit control unit to allow the vehicle to exit. An entry/exit management system as described in any one of claims 1 to 3 . An entry/exit management system as described in any one of claims 1 to 4, wherein, when executing the payment processing, the control unit checks the registration of information regarding the payment means in the billing processing unit, and if the information regarding the payment means is not registered, outputs a screen for the user to register information regarding the payment means, and when registration of information regarding the payment means is accepted from the user, executes the payment processing and registers information regarding the payment means in the billing processing unit in association with the identification information. An entrance/exit management program for causing an information processing device to function as the entrance/exit management system according to any one of claims 1 to 5 .