JP2024098427A - Settlement device, settlement system, and settlement method - Google Patents

Abstract

To provide a settlement system that can prevent fraudulent acts at a tollgate of a toll road and can reduce introduction cost and maintenance cost of an administrator.SOLUTION: A settlement device of an embodiment includes a processor that executes collection processing based on first and second databases. The first database is configured to be able to store vehicle information. The second database is configured to be able to store vehicle information registered in advance by a user and information on settlement means. In the collection processing, the processor executes at least one of a group consisting of reading a vehicle license plate, sensing a vehicle, determining a vehicle type, determining the number of axles, and checking a traveling direction, based on image data, and stores the acquired vehicle information in the first database. The processor calculates a toll based on information associated with the read vehicle license plate, and charges the user for the calculated toll utilizing the settlement means associated with the read vehicle license plate.SELECTED DRAWING: Figure 15

Description

The embodiments relate to a payment device, a payment system, and a payment method.

Electronic toll collection systems (ETC: Electronic Toll Collection (registered trademark)) are known that automatically collect tolls at toll booths on toll roads.

Japanese Patent Application Publication No. 07-021423 Japanese Patent Application Publication No. 10-134219 JP 2022-052136 A JP 2020-135201 A JP 2020-086731 A JP 2022-104743 A

To provide a payment system that can prevent fraud at toll booths on toll roads and reduce the operator's implementation and maintenance costs.

The settlement device of the embodiment includes a processor capable of executing a toll collection process for tolls on a toll road based on a first database and a second database. The first database is configured to be capable of storing information on the vehicle number, the time of entry into the toll road, the name of the entry toll gate, the time of exit from the toll road, the name of the exit toll gate, the vehicle type, and the number of axles. The second database is configured to be capable of storing vehicle information including the vehicle number, the vehicle type, and the number of axles, and information on the payment method, which are registered in advance by the user. In the collection process, the processor executes at least one of the following groups based on the image data: reading the vehicle number in the toll gate, detecting the vehicle in the toll gate, determining the vehicle type, determining the number of axles, and confirming the direction of travel, and stores the acquired vehicle information in the first database. In the collection process, the processor calculates the toll based on information associated with the read vehicle number among the information stored in the first database. In the collection process, the processor charges the calculated toll to the user using the payment method associated with the read vehicle number among the information stored in the second database.

FIG. 1 is a block diagram showing an example of the overall configuration of a payment system according to an embodiment. FIG. 2 is a schematic diagram showing an example of the hardware configuration of a toll booth system provided in the payment system according to the embodiment. FIG. 2 is a block diagram showing an example of a hardware configuration of a server used in the payment system according to the embodiment. FIG. 2 is a block diagram showing an example of a hardware configuration of a terminal device used in the payment system according to the embodiment. FIG. 2 is a block diagram showing an example of the functional configuration of a management server included in the payment system according to the embodiment. FIG. 2 is a block diagram showing an example of the functional configuration of a database storage unit of a management server included in the payment system according to the embodiment. 11 is a table showing an example of a configuration of a user registration information database stored in a database storage unit of a management server provided in the payment system according to the embodiment. 11 is a table showing an example of a configuration of a usage history database stored in a database storage unit of a management server provided in the payment system according to the embodiment. 11 is a table showing an example of a configuration of a traveling vehicle information database stored in a database storage unit of a management server provided in the payment system according to the embodiment. 11 is a table showing an example of a configuration of an unusable information database stored in a database storage unit of a management server included in the payment system according to the embodiment. 11 is a table showing an example of the configuration of a fee calculation table information database stored in a database storage unit of a management server provided in the payment system according to the embodiment. FIG. 2 is a block diagram showing an example of the functional configuration of an information management unit of a management server included in the payment system according to the embodiment. FIG. 2 is a block diagram showing an example of the functional configuration of an image processing unit of a management server included in the payment system according to the embodiment. FIG. 2 is a block diagram showing an example of the functional configuration of a main processing unit of a management server included in the payment system according to the embodiment. 11 is a flowchart showing an example of an entrance toll gate process of the payment system according to the embodiment. 10 is a flowchart showing an example of a vehicle determination process of the payment system according to the embodiment. FIG. 4 is a schematic diagram showing a specific example of a vehicle determination process of the payment system according to the embodiment. 11 is a flowchart showing an example of a first entrance process of the payment system according to the embodiment. 11 is a flowchart showing an example of a second entrance process of the payment system according to the embodiment. 11 is a flowchart showing an example of an exit toll gate process of the payment system according to the embodiment. 11 is a flowchart showing an example of a first exit process of the payment system according to the embodiment. 11 is a flowchart showing an example of a second exit process of the payment system according to the embodiment. 11 is a flowchart showing an example of a third exit process of the payment system according to the embodiment.

The following describes the embodiments with reference to the drawings. The drawings are schematic or conceptual. The dimensions and ratios of each drawing are not necessarily the same as those in reality. In this specification, the same reference numerals are used to designate components that have substantially the same functions and configurations. A "hyphen + number" or "letter" following a letter that constitutes a reference numeral is used to distinguish between elements that are referred to by the reference numeral containing the same letter and have similar configurations. When there is no need to distinguish between elements indicated by reference numerals containing the same letter, these elements are referred to by reference numerals containing only letters.

<1> Configuration First, the configuration of the payment system 1 according to the embodiment will be described.

<1-1> Overall configuration of the payment system 1 Fig. 1 is a block diagram showing an example of the overall configuration of the payment system 1 according to the embodiment. As shown in Fig. 1, the payment system 1 includes, for example, an entrance toll gate system 10-1, an exit toll gate system 10-2, a management server 20-1, a payment company server 20-2, a toll gate terminal device 30-1, an administrator terminal device 30-2, and a user terminal device 30-3.

The entrance toll gate system 10-1, the exit toll gate system 10-2, and the toll gate terminal device 30-1 are each connected to the management server 20-1, for example, via a dedicated communication line. The settlement company server 20-2, the administrator terminal device 30-2, and the user terminal device 30-3 are each connected to the management server 20-1, for example, via a network NW, which is a public communication line. By using a dedicated communication line between the management server 20-1 and each of the entrance toll gate system 10-1, the exit toll gate system 10-2, and the toll gate terminal device 30-1, high-speed and stable communication can be realized. Note that the settlement system 1 is only required to be configured so that the management server 20-1 can communicate with other devices and servers. Public communication lines may be used for these communications. The operation of the settlement system 1 described below can be performed regardless of the type of line used in the settlement system 1.

The entrance toll booth system 10-1 is a toll booth system installed at the entrance of a toll road. The exit toll booth system 10-2 is a toll booth system installed at the exit of a toll road. The number of entrance toll booth systems 10-1 and exit toll booth systems 10-2 installed on a toll road is two or more. The payment system 1 can charge tolls to users of the toll road using the combination of the entrance toll booth system 10-1 and the exit toll booth system 10-2. In this specification, when a common configuration is described between the entrance toll booth system 10-1 and the exit toll booth system 10-2, they are also simply referred to as the "toll booth system 10".

The management server 20-1 is a server capable of operating and managing the entrance toll gate system 10-1 and the exit toll gate system 10-2. The functions of the management server 20-1 described below may be realized by multiple servers. The settlement company server 20-2 is a server of a company that provides a settlement service used for toll settlement. The number of settlement company servers 20-2 that can be used by the settlement system 1 corresponds to the number of settlement companies with which the settlement system 1 is affiliated. In this specification, when a common configuration is handled between the management server 20-1 and the settlement company server 20-2, they are also simply referred to as "server 20".

The toll gate terminal device 30-1 is a terminal device that implements the operation means of the entrance toll gate system 10-1 and the exit toll gate system 10-2. The toll gate terminal device 30-1 is used, for example, as an input device when correcting the driving data of a vehicle using a toll road at a toll gate, and as an output device when checking the lane image at a toll gate. The administrator terminal device 30-2 is a terminal device that implements the management means of the payment system 1. The administrator terminal device 30-2 is used, for example, as a terminal device that adds toll gates, deletes toll gates, and revises tolls. The user terminal device 30-3 is a terminal device used when using the payment system 1 on a toll road. The user terminal device 30-3 is configured to be able to register a user in the payment system 1 and view the usage history of the toll road via a website, etc. In this specification, when a common configuration is handled between the toll gate terminal device 30-1, the administrator terminal device 30-2, and the user terminal device 30-3, they are also simply called "terminal device 30".

In the payment system 1, the toll booth terminal device 30-1 may be omitted if the above-mentioned operation means can be executed by a general terminal device and a website, etc. Similarly, in the payment system 1, the administrator terminal device 30-2 may be omitted if the above-mentioned management means can be executed by a general terminal device and a website, etc. Examples of the user terminal device 30-3 include a smartphone, a mobile phone terminal, a desktop computer, and a laptop computer. The user terminal device 30-3 is not limited to this, and may be configured to be able to access the website services provided by the payment system 1 via an Internet line (for example, a network NW).

<1-2> Hardware configuration of the payment system 1 <1-2-1> Hardware configuration of the toll gate system 10 Fig. 2 is a schematic diagram showing an example of the hardware configuration of the toll gate system 10 included in the payment system 1 according to the embodiment. As shown in Fig. 2, the toll gate system 10 includes, for example, a lane 11, a vehicle detection area 12, a gate 13, cameras 14A and 14B, cameras 15A and 15B, guide boards 16 and 17, an automated toll collection machine 18, and a roof 19.

Lane 11 is the route that vehicles travel when entering or exiting a toll road. In FIG. 2, the direction of travel of vehicles using the toll gate is indicated by a thick arrow. In the following explanation, the direction of travel of the vehicle is referred to as "forward," and the opposite direction to the vehicle's direction of travel is referred to as "rearward."

The vehicle detection area 12 is an area of the lane 11 that corresponds to the middle part of the toll gate. The toll gate system 10 is configured to be able to detect a vehicle in the vehicle detection area 12 and execute processes related to the payment of tolls for the toll road for that vehicle. For example, the payment system 1 executes vehicle determination processing and toll collection processing, which will be described later, in the vehicle detection area 12.

The gate 13 is a departure controller installed in the front portion of the lane 11. The gate 13 of the entrance toll booth system 10-1 controls the entry of vehicles in the toll booth into the toll road. The gate 13 of the exit toll booth system 10-2 controls the exit of vehicles in the toll booth from the toll road. The gate 13 is equipped with, for example, a bar configured to be able to open and close the vehicle's travel path. The entry or exit of a vehicle into or from the toll road is permitted when the gate 13 is open, and is prohibited when the gate 13 is closed.

Each of the cameras 14A and 14B is an imaging device installed so as to capture an image of the vehicle detection area 12 from the front. For example, the angle of view of the camera 14A is wider than that of the camera 14B. The camera 14A captures an image of the entire vehicle traveling within the toll gate from the front. The camera 14B captures an image of the license plate in front of the vehicle traveling within the toll gate. Each of the cameras 14A and 14B is optimized according to the subject to be captured. The cameras 14A and 14B may be integrated as long as they can satisfy the image quality performance required for the vehicle determination process described below.

Each of the cameras 15A and 15B is an imaging device installed so as to be able to capture an image of the vehicle detection area 12 from behind. For example, the angle of view of the camera 15A is wider than that of the camera 15B. The camera 15A captures an image of the entire vehicle traveling within the toll gate from behind. The camera 15B captures an image of the license plate on the rear of the vehicle traveling within the toll gate. Each of the cameras 15A and 15B is optimized according to the subject of the image. The cameras 15A and 15B may be integrated as long as they can satisfy the image quality performance required for the vehicle determination process described below. To improve the accuracy of image processing, three or more cameras may be installed in the front and rear. A camera may be installed on the side of the vehicle detection area 12.

Each of the information boards 16 and 17 is a display installed so as to be visible to the user driving the vehicle. Each of the information boards 16 and 17 is used to notify the driver of the vehicle of information. The information board 16 is installed in front of the vehicle detection area 12. The information board 17 is installed, for example, in the rear of the vehicle detection area 12. The information board 16 notifies the user whether or not the vehicle can enter the toll gate and whether or not the vehicle can exit the toll gate. The information board 17 notifies the user whether or not the vehicle can enter the toll gate.

The automatic toll collection machine 18 is a device that performs processing related to the payment of tolls. For example, the automatic toll collection machine 18 of the entrance toll gate system 10-1 is configured to be able to issue a toll ticket. For example, the time of entry into the toll road and the entrance toll gate are recorded on the toll ticket. The payment system 1 uses the toll ticket for vehicles that have not been registered for use by a toll road user in the payment system 1, and vehicles whose registered vehicle information differs from the vehicle information that actually uses the toll gate. The automatic toll collection machine 18 of the exit toll gate system 10-2 is configured to be able to perform processing related to the payment of tolls by toll road users. The automatic toll collection machine 18 can support multiple methods of toll payment. For example, cash, credit card, transportation IC, barcode payment, and electronic payment such as cryptocurrency can be used as a method of payment for tolls using the automatic toll collection machine 18. Any of the following methods of electronic payment may be used: advance payment, immediate payment, and post-payment.

The roof 19 is a structure for preventing the toll gate system 10 from being affected by weather. The roof 19 is installed, for example, so as to cover each component of the toll gate system 10. The roof 19 can suppress the images captured by the cameras 14 and 15 from being disturbed by bad weather, reflected sunlight, and the like. In other words, the roof 19 can suppress the deterioration of image quality when the cameras 14 and 15 capture license plates. As a result, the roof 19 can improve the stability of the entrance toll gate processing and the exit toll gate processing described below. Note that the roof 19 may be omitted if there is a low risk that these processes will not be performed normally due to weather, etc. The toll gate system 10 may use a general roof used in toll gates.

<1-2-2> Hardware configuration of server 20 Fig. 3 is a block diagram showing an example of a hardware configuration of server 20 used in payment system 1 according to the embodiment. As shown in Fig. 3, server 20 includes, for example, a CPU (Central Processing Unit) 21, a ROM (Read Only Memory) 22, a RAM (Random Access Memory) 23, a storage device 24, and a communication interface 25.

The CPU 21 is a processor that executes various programs related to the control of the server 20. The ROM 22 is a non-volatile storage device that stores the control program of the server 20. The RAM 23 is a volatile storage device used as a working area for the CPU 21. The storage device 24 is a non-volatile storage medium configured to store information according to the functions of the server 20. The communication interface 25 is an interface circuit used for communication using at least one of a dedicated communication line and a public communication line.

<1-2-3> Hardware configuration of terminal device 30 Fig. 4 is a block diagram showing an example of a hardware configuration of terminal device 30 used in payment system 1 according to an embodiment. As shown in Fig. 4, terminal device 30 includes, for example, a CPU 31, a ROM 32, a RAM 33, a storage device 34, a communication interface 35, an input interface 36, and a display 37.

The CPU 31 is a processor that executes various programs related to the control of the terminal device 30. The ROM 32 is a non-volatile storage device that stores the control program of the terminal device 30. The RAM 33 is a volatile storage device used as a working area for the CPU 31. The storage device 34 is a non-volatile storage medium configured to store information according to the functions of the terminal device 30. The communication interface 35 is an interface circuit used for communication using at least one of a dedicated communication line and a public communication line. The input interface 36 is an interface used by users such as users of the toll gate system 10 and managers and operators of the toll gates. Users can operate the terminal device 30 using the input interface 36. The display 37 is a display device used to display information that can be viewed by the user.

<1-3> Functional configuration of payment system 1 <1-3-1> Functional configuration of management server 20-1 Fig. 5 is a block diagram showing an example of the functional configuration of the management server 20-1 provided in the payment system 1 according to the embodiment. As shown in Fig. 5, the management server 20-1 operates as a computer including, for example, a database storage unit 100, an information management unit 200, a communication management unit 300, an image processing unit 400, and a main processing unit 500.

The database storage unit 100 constructs various databases used in the operation of the payment system 1 and manages the various constructed databases. Information stored in the various databases can be accessed and changed by the information management unit 200 and the main processing unit 500.

The information management unit 200 creates various websites related to the operation of the payment system 1 and manages the created websites. The various websites are configured to be accessible not only by the administrator and operator of the payment system 1, but also by users of the payment system 1 and payment companies affiliated with the payment system 1.

The communication management unit 300 controls the communication between each component of the management server 20-1 and each terminal device 30 connected to the network NW. Specifically, the communication management unit 300 can control, for example, the communication between the information management unit 200 and the user terminal device 30-3, and between the main processing unit 500 and the administrator terminal device 30-2.

The image processing unit 400 performs image processing based on the images captured by the cameras 14A, 14B, 15A, and 15B of the toll gate system 10. The image processing includes detecting vehicles in the toll gate, reading the vehicle license plate numbers of the vehicles in the toll gate, and determining at least one of the following: vehicle type, number of axles, traveling direction, and the presence or absence of an obstacle. In this specification, the vehicle type is a category determined based on the size of the vehicle body, etc. On toll roads, different tolls are assigned to each vehicle type. The number of axles corresponds to the number of tires that are in contact with the ground when the vehicle is viewed from the side, for example. The toll on a toll road may vary depending on the number of axles.

The main processing unit 500 controls the entrance toll gate system 10-1 and the exit toll gate system 10-2 based on the results of image processing by the image processing unit and information from various databases stored in the database storage unit 100. The main processing unit 500 performs processing related to the billing of tolls, for example. The main processing unit 500 can also be controlled by the toll gate terminal device 30-1.

In the above explanation, the management server 20-1 functions as the database storage unit 100, the information management unit 200, the communication management unit 300, the image processing unit 400, and the main processing unit 500, but is not limited to this. A separate server may be assigned to each functional block of the management server 20-1. The management server 20-1 does not have to be configured with hardware devices, and may be constructed with a server on a cloud network.

<1-3-2> Functional configuration of the database storage unit 100 Fig. 6 is a block diagram showing an example of the functional configuration of the database storage unit 100 of the management server 20-1 included in the payment system 1 according to the embodiment. Note that "DB" shown in the figure is an abbreviation for database. As shown in Fig. 6, the database storage unit 100 stores, for example, a user registration information database 101, a usage history database 102, a traveling vehicle information database 103, an unavailable information database 104, and a fee calculation table information database 105.

The user registration information database 101 stores information entered when the user terminal device 30-3 registered as a user of the payment system 1. The usage history database 102 stores information related to the usage history of toll roads for each user of the payment system 1. The traveling vehicle information database 103 stores data on vehicles that have entered and exited toll gates. The traveling vehicle information database 103 is used when calculating the toll billing amount. The unusable information database 104 stores information related to vehicles that cannot use the payment methods registered in the user registration information database 101. The toll calculation table information database 105 stores information used to calculate tolls for toll roads.

Below, an example of the configuration of each of the user registration information database 101, the usage history database 102, the traveling vehicle information database 103, the unavailable information database 104, and the fare calculation table information database 105 will be described in order.

(User registration information database 101)
7 is a table showing an example of the configuration of the user registration information database 101 stored in the database storage unit 100 of the management server 20-1 included in the payment system 1 according to the embodiment. As shown in Fig. 7, information stored in the user registration information database 101 includes, for example, name, vehicle number, presence or absence of a disability, contact information, payment method, and settlement method details.

In the user registration information database 101, "name" corresponds to a user of the payment system 1. In this example, "NNNN" and "MMMM" are registered in the "name" field of the user registration information database 101. "Vehicle number" corresponds to the vehicle number assigned to the user's vehicle. "Presence or absence of disability" is used when determining whether or not to apply a disability discount rate. As information indicating "presence or absence of disability", part of the information recorded in the disability certificate may be stored. "Contact information" is, for example, an email address. "Payment method" is, for example, credit card payment, bank transfer, electronic money, etc. "Payment method details" is detailed information of the payment method shown in the associated record. As the payment method details, information according to the payment method is stored. When the payment method is credit card payment, the payment method details include information such as the credit card card number. A database of payment method details may be constructed for each payment method. In this example, the vehicle number "AA0000", problem "present", contact information "XXX@YYYY", payment method "credit card", and settlement method details "card number, etc." are registered in association with the name "NNNN". Also, the vehicle number "BB1111", problem "not present", contact information "YYY@ZZZZ", payment method "direct debit", and settlement method details "account number, etc." are registered in association with the name "MMMM".

Various database structures may be used as the database structure of the user registration information database 101. The user registration information database 101 may have a configuration in which the user's vehicle number, the presence or absence of a malfunction, contact information, payment method, and settlement method details are stored in association with each other.

(Usage History Database 102)
Fig. 8 is a table showing an example of the configuration of the usage history database 102 stored in the database storage unit 100 of the management server 20-1 included in the payment system 1 according to the embodiment. Fig. 8 shows information related to the usage history of a toll road for a certain user. As shown in Fig. 8, the information stored in the usage history database 102 includes, for example, the number of uses, the entry time, the entry toll gate, the exit time, the exit toll gate, and the toll.

In the usage history database 102, the "number of uses" corresponds to the number of times a user registered in the user registration information database 101 has used a toll road. The "number of uses" may be replaced with the date of use of the toll road. The "entrance time" corresponds to the date and time when the user's vehicle passed through the entrance toll gate. The "entrance toll gate" corresponds to the name of the entrance toll gate that the user's vehicle passed through. The "exit time" corresponds to the date and time when the user's vehicle passed through the exit toll gate. The "exit toll gate" corresponds to the name of the exit toll gate that the user's vehicle passed through. The "toll fee" corresponds to the toll fee charged when the toll road is used. In this example, "1 (time)" and "2 (times)" are registered in the "number of uses" item in the usage history database 102. And, associated with the number of uses "1", the entry time "2022/9/1 12:31", the entry toll gate "A toll gate", the exit time "2022/9/1 16:41", the exit toll gate "B toll gate", and the toll "50" are registered. Also, associated with the number of uses "2", the entry time "2022/9/8 10:10", the entry toll gate "A toll gate", the exit time "2022/9/8 17:20", the exit toll gate "C toll gate", and the toll "300" are registered.

Various database structures may be used as the database structure of the usage history database 102. The usage history database 102 may have a configuration in which the entry time, the entry toll gate, the exit time, the exit toll gate, and the toll are stored in association with each other.

(Traveling vehicle information database 103)
9 is a table showing an example of the configuration of the traveling vehicle information database 103 stored in the database storage unit 100 of the management server 20-1 included in the payment system 1 according to the embodiment. As shown in FIG. 9, the information stored in the traveling vehicle information database 103 includes, for example, the entry time, the entry toll gate, the exit time, the exit toll gate, the vehicle number, the vehicle type, the number of axles, the presence or absence of an obstacle, and the toll.

In the traveling vehicle information database 103, "entry time" corresponds to the date and time when the vehicle passed through the entrance toll gate. "entrance toll gate" corresponds to the name of the entrance toll gate that the vehicle passed through. "exit time" corresponds to the date and time when the vehicle passed through the exit toll gate. "exit toll gate" corresponds to the name of the exit toll gate that the vehicle passed through. "Vehicle number", "vehicle type", "number of axles", and "presence or absence of obstacle" each correspond to information about the vehicle that used the toll road. "Toll" corresponds to the toll charged when using the toll road. In this example, "AA0000" and "BB1111" are registered in the "vehicle number" item of the traveling vehicle information database 103. And, associated with the vehicle number "AA0000", the entry time "2022/9/1 12:31", the entry toll gate "A toll gate", the exit time "2022/9/1 16:41", the exit toll gate "B toll gate", the vehicle type "normal", the number of axles "2", the obstacle "present", and the toll "50" are registered. Also, associated with the vehicle number "BB1111", the entry time "2022/9/1 12:50", the entry toll gate "A toll gate", the exit time "2022/9/1 18:10", the exit toll gate "C toll gate", the vehicle type "large", the number of axles "3", the obstacle "not present", and the toll "900" are registered.

The entry time and exit time are used to determine whether or not to apply a time-based discount. The combination of vehicle type and number of axles is used to determine the final vehicle type. For example, for a medium-sized vehicle with three axles, the toll that applies is the toll for large vehicles. In this way, the traveling vehicle information database 103 can be used to accurately determine the vehicle type by storing a combination of vehicle type and number of axles.

In addition, the traveling vehicle information database 103 stores information on the vehicle type determined by the vehicle determination means described below. Various database structures can be used as the database structure of the traveling vehicle information database 103. The traveling vehicle information database 103 only needs to have a configuration in which the entry time, entry toll gate, exit time, exit toll gate, vehicle number, vehicle type, number of axles, presence or absence of obstacles, and toll are stored in association with each other.

(Unavailable Information Database 104)
10 is a table showing an example of the configuration of the unusable information database 104 stored in the database storage unit 100 of the management server 20-1 included in the payment system 1 according to the embodiment. As shown in FIG. 10, the information stored in the unusable information database 104 includes, for example, a vehicle number, a payment method, and details of the settlement method.

In the unusable information database 104, "vehicle number" corresponds to the vehicle number of a vehicle registered in the user registration information database 101 and for which the pre-registered payment method cannot be used. "Payment method" corresponds to the payment method associated with the vehicle number. "Payment method details" corresponds to detailed information of the payment method associated with the vehicle number. In this example, "CC2222" and "DD3333" are registered in the "vehicle number" item of the running vehicle information database 103. Also, associated with the vehicle number "CC2222", the payment method "credit card" and payment method details "card number, etc." are registered. Also, associated with the vehicle number "DD3333", the payment method "direct debit" and payment method details "account number, etc." are registered.

Various database structures may be used for the unusable information database 104. The unusable information database 104 only needs to have at least vehicle number information. The unusable information database 104 may also be integrated with the user registration information database 101. In this case, the user registration information database 101 further stores information regarding the availability of the payment method.

(Fee calculation table information database 105)
11 is a table showing an example of the configuration of the fee calculation table information database 105 stored in the database storage unit 100 of the management server 20-1 included in the payment system 1 according to the embodiment. As shown in FIG. 11, the information stored in the fee calculation table information database 105 includes, for example, an entrance toll gate, an exit toll gate, a discount time period, a normal toll, a time period discount, and an obstacle discount.

In the toll calculation table information database 105, the "entrance toll gate" corresponds to the name of the entrance toll gate where the vehicle entered the toll road. The "exit toll gate" corresponds to the name of the exit toll gate where the vehicle exited the toll road. The "discount time period" indicates the time period during which the time period discount is applied in the section between the associated entrance toll gate and exit toll gate. The "normal toll" indicates the toll when the time period discount or the obstacle discount is not applied. The "time period discount" indicates the toll when the time period discount is applied. The "obstacle discount" indicates the toll when the obstacle discount is applied. In addition, in the toll calculation table information database 105, each of the "normal toll", "time period discount", and "obstacle discount" stores information on the toll for each vehicle type. In this example, the vehicle types shown are "large", "medium", "normal", and "small". Not limited to this, the vehicle classification in each of the "normal toll", "time period discount", and "obstacle discount" can be changed as appropriate depending on the type of toll discount that can be applied. In this example, a pair of "Tollgate A" and "Tollgate B" and a pair of "Tollgate A" and "Tollgate C" are registered in the pair of items "Entry tollgate" and "Exit tollgate" in the toll calculation table information database 105. In addition, in association with the pair of "Tollgate A" and "Tollgate B", the following are registered: discount time period "23:00-04:00", normal tolls "large: 500, medium: 300, normal: 200, small: 150", time period discounts "large: 400, medium: 200, normal: 100, small: 50", and obstacle discounts "large: 400, medium: 200, normal: 50, small: 40". Also, associated with the pair "Tollgate A" and "Tollgate C", the following are registered: discount time period "23:00-05:00", normal tolls "Large: 900, Medium: 700, Regular: 500, Small: 450", time-of-day discounts "Large: 700, Medium: 500, Regular: 400, Small: 350", and disability discounts "Large: 700, Medium: 500, Regular: 300, Small: 250".

Various database structures may be used as the database structure of the toll calculation table information database 105. The toll calculation table information database 105 only needs to store the information necessary for calculating the toll.

<1-3-3> Functional configuration of the information management unit 200 FIG. 12 is a block diagram showing an example of the functional configuration of the information management unit 200 of the management server 20-1 included in the payment system 1 according to the embodiment. FIG. 12 also shows some of the functions of the terminal and server that communicate with the information management unit 200. As shown in FIG. 12, the information management unit 200 functions as a computer equipped with, for example, a user registration website operating means 201, a history viewing website operating means 202, a tollgate management website operating means 203, a system management website operating means 204, and a payment management means 205. The user terminal device 30-3 functions as a computer equipped with, for example, a user information registration means 601 and a usage history viewing means 602. The tollgate terminal device 30-1 functions as a computer equipped with, for example, a tollgate operation means 603. The manager terminal device 30-2 functions as a computer equipped with, for example, a system management means 604. The payment company server 20-2 functions as a computer equipped with, for example, a payment availability notification means 605.

Each of the user information registration means 601, the usage history viewing means 602, the system management means 604, and the payment availability notification means 605 is configured to be able to communicate with the information management unit 200, for example, via the communication management unit 300. The toll booth operation means 603 is configured to be able to communicate with the information management unit 200, for example, via the main processing unit 500. This is not limited to the above, and it is sufficient that the information management unit 200 is configured to be able to communicate with each of the user information registration means 601, the usage history viewing means 602, the system management means 604, the payment availability notification means 605, and the toll booth operation means 603.

The user registration website operating means 201 is a means for operating the user information registration website of the payment system 1. The user information registration website is used when the user terminal device 30-3 uses the user information registration means 601. The user information registration means 601 is a means for accessing the user information registration website by the user terminal device 30-3 and registering user information. Before using a toll road, a user of the payment system 1 uses the user information registration means 601 to register, for example, the name, vehicle number, the presence or absence of a disability, contact information, payment method, and settlement method details. As a result, the information registered by the user information registration means 601 is stored in the user registration information database 101. Note that when registering user information, a method may be used in which a photographed image of the vehicle number or a photographed image of a disability certificate is converted into character data and registered in order to prevent fraud.

The history viewing website operating means 202 is a means for operating a website for viewing the usage history of toll roads. The usage history viewing website is used when the user terminal device 30-3 uses the usage history viewing means 602. The usage history viewing means 602 is a means for accessing the usage history viewing website and viewing the usage history of toll roads. It is assumed that the usage history viewing website is accessed and viewed by the user terminal device 30-3. This is not limited to the above, and if there is another way for the user to check the usage history of toll roads, the usage history viewing means 602 does not need to be used. The usage history viewing website and the user information registration website may be integrated.

The toll gate management website operating means 203 is a means for operating the toll gate management website (a website for operating the toll gate). The toll gate management website is used when the toll gate terminal device 30-1 uses the toll gate operation means 603. The toll gate operation means 603 is a means for accessing the toll gate management website to, for example, modify tolls or close traffic lanes at the toll gate. Note that if there is another means for operating the toll gate, the toll gate operation means 603 may be omitted.

The system management website operating means 204 is a means for operating the system management website. The system management website is used when the administrator terminal device 30-2 uses the system management means 604. The system management means 604 is a means for accessing the system management website to, for example, add or delete toll gates, revise tolls, etc. Note that if there is another means for managing toll gates collectively, the system management means 604 may be omitted.

The payment management means 205 is a means for managing information related to payments in the payment system 1. The payment management means 205 periodically accesses the payment company server 20-2 to check whether the payment means registered in the user registration information database 101 are available. The payment company server 20-2 uses the payment availability notification means 605 to notify information indicating whether the payment means are available. The payment management means 205 updates the unavailable information database 104 based on the information notified from the payment availability notification means 605. For example, when a payment means is unavailable, the payment management means 205 stores information on the associated vehicle number and information on the payment means in the unavailable information database 104. In addition, when the payment means of a vehicle number stored in the unavailable information database 104 is updated to be available, the payment management means 205 deletes information corresponding to that vehicle number from the unavailable information database 104.

<1-3-4> Functional configuration of the image processing unit 400 Fig. 13 is a block diagram showing an example of the functional configuration of the image processing unit 400 of the management server 20-1 included in the payment system 1 according to the embodiment. Fig. 13 also shows some of the functions of the toll gate system 10 that communicates with the image processing unit 400. As shown in Fig. 13, the image processing unit 400 functions as a computer including, for example, a vehicle detection means 401, a license plate reading means 402, a vehicle type determination means 403, an axle number determination means 404, an obstacle determination means 405, and a traveling direction confirmation means 406. The toll gate system 10 includes, for example, a vehicle front image capture means 701, a vehicle rear image capture means 702, and a vehicle side image capture means 703.

The vehicle detection means 401 is a means for determining whether or not a vehicle is present within the toll gate from one image taken by at least one of the vehicle front photographing means 701, the vehicle rear photographing means 702, and the vehicle side photographing means 703, or from multiple images taken at regular time intervals. The vehicle front photographing means 701 is a means for photographing the entire vehicle body from the front of the vehicle. The vehicle front photographing means 701 is realized, for example, by a combination of a camera 14A that photographs the entire vehicle body from the front at a wide angle and a camera 14B that photographs the front license plate in detail. The vehicle rear photographing means 702 is a means for photographing the entire vehicle body from the rear of the vehicle. The vehicle rear photographing means 702 may be realized by a combination of a camera 15A that photographs the entire vehicle body from the rear at a wide angle and a camera 15B that photographs the rear license plate in detail. The vehicle side photographing means 703 is a means for photographing the side of the vehicle so that the number of tires on the ground can be recognized. The vehicle side photographing means 703 is realized, for example, by a combination of cameras 14A and 15A. Note that the vehicle detection means 401 may use any method as long as it can determine the presence or absence of a vehicle within the toll gate based on the data photographed by each photographing means.

The number reading means 402 is a means for converting the vehicle number printed on the license plate photographed by one or both of the vehicle front photographing means 701 and the vehicle rear photographing means 702 into character data. The number reading means 402 may use any method as long as it is capable of recognizing the license plate of the vehicle within the toll booth based on the data photographed by each photographing means and converting the vehicle number into character data.

The vehicle type determination means 403 is a means for determining the vehicle type of the vehicle in the toll gate from an image of the entire vehicle captured by at least one of the vehicle front image capture means 701, the vehicle rear image capture means 702, and the vehicle side image capture means 703. The vehicle type determination means 403 is configured to be able to determine the vehicle type by capturing the characteristics of the vehicle type using an image processing method such as machine learning. Note that the vehicle type determination means 403 may use any method as long as it is possible to determine the vehicle type based on the data captured by each image capture means. On toll roads, vehicle types are classified into five levels, for example, small, normal, medium, large, and extra large. This is not limited to this, and vehicle types may be classified in more detail on toll roads, and a fee system may be set for each vehicle type.

The axle number determination means 404 is a means for determining the number of axles of a vehicle in a toll booth from an image of the entire vehicle captured by at least one of the vehicle front image capture means 701, the vehicle rear image capture means 702, and the vehicle side image capture means 703. The axle number determination means 404 is configured to be able to determine the vehicle type by capturing the characteristics of the vehicle type using an image processing method such as machine learning. Note that the axle number determination means 404 may use any method as long as it is possible to determine the vehicle type based on the data captured by each image capture means.

The obstacle determination means 405 is a means for determining whether or not a vehicle in a toll booth is using the obstacle discount from an image of the entire vehicle captured by at least one of the vehicle front image capture means 701, the vehicle rear image capture means 702, and the vehicle side image capture means 703. The obstacle determination means 405 determines that the vehicle is using the obstacle discount, for example, by reading information on a disability certificate placed in a specific position on the vehicle. Without being limited to this, the obstacle determination means 405 may use any method as long as it is possible to determine whether or not the obstacle discount is to be used (i.e., the presence or absence of an obstacle) based on data captured by each image capture means.

The traveling direction confirmation means 406 is a means for determining the traveling direction of a vehicle traveling within a toll gate from an image of the entire vehicle captured by at least one of the vehicle front photographing means 701, the vehicle rear photographing means 702, and the vehicle side photographing means 703. The traveling direction confirmation means 406 determines the traveling direction of the vehicle, for example, by processing images captured at regular time intervals. The traveling direction confirmation means 406 is not limited to this, and may use any method as long as it is possible to determine the traveling direction of the vehicle based on the data captured by each photographing means. The traveling direction confirmation means 406 is used, for example, for the purpose of confirming that the vehicle within the toll gate moves beyond the gate 13 after the gate 13 opens.

<1-3-5> Functional configuration of the main processing unit 500 Fig. 14 is a block diagram showing an example of the functional configuration of the main processing unit 500 of the management server 20-1 included in the payment system 1 according to the embodiment. Fig. 14 also shows some of the functions of the toll gate system 10 that communicates with the main processing unit 500. As shown in Fig. 14, the main processing unit 500 functions as a computer including, for example, a traveling vehicle information recording means 501, a guide board control means 502, a gate control means 503, a passage permission determination means 504, a toll calculation means 505, a toll billing means 506, and a history information recording means 507. The toll gate system 10 includes, for example, a gate driving means 704, an automatic toll collection machine control means 705, and a guide display means 706.

The traveling vehicle information recording means 501 is used as a means for storing data in the traveling vehicle information database 103. The traveling vehicle information recording means 501 may use any method as long as it is possible to store in the traveling vehicle information database 103 the entry time of the traveling vehicle, the entry toll booth, the exit time, the entry fee area, the vehicle number, the vehicle type, the number of axles, the presence or absence of obstacles, the toll, etc.

The guide board control means 502 is a means for transmitting information to be displayed on the guide boards 16 and 17 to the guide display means 706. The guide display means 706 controls the display of the guide boards 16 and 17 based on the information received from the guide board control means 502. The guide board control means 502 may use any method as long as it is possible to control the display of each of the guide boards 16 and 17.

The gate control means 503 is a means for transmitting instructions for opening and closing the gate to the gate driving means 704. The gate driving means 704 controls the opening and closing of the gate 13 by driving the bar of the gate 13 based on the information received from the gate control means 503. The gate control means 503 may use any method as long as it is capable of controlling the opening and closing of the gate 13.

The passage permission determination means 504 checks whether there are any matching parts in the vehicle number, payment method, and payment method details between the user registration information database 101 and the unusable information database 104. If there is no match, the passage permission determination means 504 determines that the pre-registered payment method can be used, and if there is a match, determines that the pre-registered payment method cannot be used. The passage permission determination means 504 also notifies the gate control means 503 of passage permission based on the completion of payment or settlement of the toll. In this case, the gate control means 503 is configured to control the opening and closing of the gate based on the notification from the passage permission determination means 504.

The toll calculation means 505 is a means for calculating a toll using the traveling vehicle information database 103 and the toll calculation table information database 105. For example, the toll calculation means 505 finds a record corresponding to a combination of an entrance toll gate and an exit toll gate recorded in the traveling vehicle information database 103 from the toll calculation table information database 105. Then, the toll calculation means 505 applies, as a toll to be charged to the user, one of the normal toll, the time-of-day discount, and the obstacle discount among the toll settings found. For example, if the entry time and the exit time in the traveling vehicle information database 103 are included in the discount time period in the toll calculation table information database 105, the toll calculation means 505 applies the time-of-day discount toll. In addition, if the traveling vehicle information database 103 finds that the obstacle discount is applicable, the toll calculation means 505 applies the obstacle discount toll. If multiple types of discount conditions are met, the cheapest toll may be applied. Without being limited to this, the toll can be set by the administrator or operator of the toll gate. The toll information calculated by the toll calculation means 505 is stored, for example, in the traveling vehicle information database 103. Note that the toll calculation means 505 only needs to have a function for calculating the toll, and may calculate the toll using a method other than the above (for example, a conventional method).

The toll billing means 506 bills the user for the toll calculated by the toll calculation means 505. The toll billing means 506 searches the user registration information database 101 for a vehicle number that matches the vehicle number in the traveling vehicle information database 103. The toll billing means 506 then bills the user for the toll stored in the traveling vehicle information database 103 based on the payment method and payment method details listed in the user registration information database 101. The toll billing means 506 may use the automatic toll collection machine control means 705 to bill the toll. The automatic toll collection machine control means 705 accepts the payment of the toll by electronic payment such as cash, credit card, transportation IC, barcode payment, and cryptocurrency. Note that the toll billing means 506 may bill the toll by any method other than the above (for example, a conventional method) as long as it has a function of billing the toll.

The history information recording means 507 checks whether a vehicle recorded in the traveling vehicle information database 103 is registered in the user registration information database 101. If the vehicle is registered in the user registration information database 101, the history information recording means 507 records the toll road usage history in association with the registered user. In other words, the history information recording means 507 stores information on the toll road usage history recorded in the traveling vehicle information database 103 in the usage history database 102. Note that the history information recording means 507 only needs to have a function for recording the toll road usage history of the user, and may record the toll road usage history of the user using a method other than the above (for example, a conventional method).

<2> Operation The payment system 1 executes entrance toll gate processing at the entrance toll gate system, and executes exit toll gate processing at the exit toll gate system. The entrance toll gate processing is a process of collecting tolls for users (vehicles) entering a toll road, and is executed by the combination of the entrance toll gate system 10-1 and the management server 20-1. The exit toll gate processing is a process of collecting tolls for users (vehicles) exiting a toll road, and is executed by the combination of the exit toll gate system 10-2 and the management server 20-1. Below, the entrance toll gate processing and the exit toll gate processing will be described in order as the operation of the payment system 1 according to the embodiment.

<2-1> Entrance toll gate processing Fig. 15 is a flowchart showing an example of the entrance toll gate processing of the payment system 1 according to the embodiment. The payment system 1 is configured to repeatedly execute the series of processes shown in Fig. 15. The flow of the entrance toll gate processing will be described below with reference to Fig. 15. Note that the "toll gate" in the entrance toll gate processing corresponds to the entrance toll gate system 10-1.

When the entrance toll gate process starts, the payment system 1 checks whether a vehicle has been detected within the toll gate (S10). Specifically, the vehicle front photographing means 701 photographs the vehicle detection area 12. Then, the vehicle detection means 401 determines whether a vehicle is present in the vehicle detection area 12 based on the data photographed by the vehicle front photographing means 701.

If no vehicle is detected within the toll gate in the process of S10 (S10, NO), the payment system 1 executes the process of S10 again. At this time, the guide board control means 502 may cause the guide display means 706 (e.g., the guide board 17) to display a message encouraging vehicles outside the toll gate to enter the toll gate.

If a vehicle is detected within the toll gate in the process of S10 (S10, YES), the payment system 1 proceeds to the process of S11. At this time, the guide board control means 502 causes the guide display means 706 (e.g., guide board 17) to display a message indicating that vehicles outside the toll gate are prohibited from entering the toll gate.

In the process of S11, the payment system 1 executes a vehicle determination process. The vehicle determination process is a process for acquiring information on the vehicle that has entered the toll gate. The payment system 1 can determine the vehicle model, etc., through the vehicle determination process. The details of the vehicle determination process will be described later.

Next, the payment system 1 stores the vehicle determination result in the traveling vehicle information database 103 (S12). Specifically, the traveling vehicle information recording means 501 stores, in the traveling vehicle information database 103, information regarding the vehicle number, vehicle type, number of axles, and the presence or absence of a fault obtained by the vehicle determination process.

Next, the payment system 1 checks whether the vehicle number exists in the user registration information database 101 (S13). Specifically, the passage permission determination means 504 searches the user registration information database 101 for the vehicle number detected within the vehicle detection area 12.

If it is confirmed in the processing of S13 that the vehicle number exists in the user registration information database 101 (S13, YES), the payment system 1 proceeds to processing of S14.

If it is confirmed in the process of S13 that the vehicle number does not exist in the user registration information database 101 (S13, NO), the payment system 1 proceeds to the process of S17.

In the process of S14, the payment system 1 checks whether the vehicle information matches between the traveling vehicle information database 103 and the user registration information database 101. Specifically, the passage permission determination means 504 determines whether each piece of vehicle information, such as the vehicle type and number of axles, is the same between the user registration information database 101 and the traveling vehicle information database 103. If even one item does not match, the passage permission determination means 504 determines that the vehicle information does not match.

If it is confirmed in the processing of S14 that the vehicle information matches between the traveling vehicle information database 103 and the user registration information database 101 (S14, YES), the payment system 1 proceeds to processing of S15.

If it is confirmed in the processing of S14 that the vehicle information does not match between the traveling vehicle information database 103 and the user registration information database 101 (S14, NO), the payment system 1 proceeds to processing of S17.

In the process of S15, the payment system 1 checks whether the vehicle number is not present in the unusable information database 104. Specifically, the passage permission determination means 504 searches the unusable information database 104 for the vehicle number detected within the vehicle detection area 12.

If it is confirmed in the process of S15 that the vehicle number does not exist in the unusable information database 104 (S15, YES), the payment system 1 proceeds to the process of S16.

If it is confirmed in the processing of S15 that the vehicle's number is present in the unusable information database 104 (S15, NO), the payment system 1 proceeds to processing of S17.

In the process of S16, the payment system 1 executes the first entry process. The first entry process is a process for collecting tolls that is executed when a vehicle is allowed to enter a toll road using a pre-registered payment method. Details of the first entry process will be described later. When the first entry process is completed, the payment system 1 ends the series of processes in FIG. 15.

In the process of S17, the payment system 1 executes the second entry process. The second entry process is a process for collecting tolls that is executed when a vehicle with no user registration, a vehicle suspected of fraud, or a vehicle that cannot use a pre-registered payment method is allowed to enter a toll road. Details of the second entry process will be described later. When the second entry process is completed, the payment system 1 ends the series of processes in FIG. 15.

(Vehicle determination process)
16 is a flowchart showing an example of a vehicle determination process in the payment system 1 according to the embodiment. The flow of the vehicle determination process will be described below with reference to FIG.

When the vehicle determination process starts, the payment system 1 photographs the entire vehicle using, for example, the vehicle front photographing means 701, the vehicle rear photographing means 702, and the vehicle side photographing means 703 (S111). Specifically, cameras 14A and 14B photograph the vehicle in the vehicle detection area 12 from the front, and cameras 15A and 15B photograph the vehicle in the vehicle detection area 12 from the rear. The photographed image includes an overall image that allows the size of the vehicle to be recognized, the front and rear license plates of the vehicle, all tires used by the vehicle to travel, and an obstacle presence/absence identification section. For example, the front and rear license plates are photographed more finely by cameras 14B and 15B, respectively, than by cameras 14A and 15A.

Next, the payment system 1 converts the image of the license plate into character data (S112). Specifically, the license plate reading means 402 extracts the vehicle number from the portion of the image data captured by the process of S111 that corresponds to the license plate. The license plate reading means 402 then converts the extracted vehicle number into character data. The converted character data is, for example, temporarily stored in the RAM 23.

Next, the payment system 1 determines the vehicle type (S113). Specifically, the vehicle type determination means 403 estimates the size of the vehicle from a portion of the image data captured by the process of S111 that corresponds to the overall image of the vehicle. The vehicle type determination means 403 then determines the vehicle type based on the estimated vehicle size. In the process of S113, the vehicle type determination means 403 may estimate the vehicle type, manufacturer, and name based on the image data of the vehicle. For example, the vehicle type determination means 403 may estimate the vehicle type, manufacturer, and name by previously storing a large number of images of automobiles in association with the vehicle type, manufacturer, and name, and comparing the vehicle image data with the previously stored information. In addition, the payment system 1 may charge a toll based on a more detailed fee schedule based on the estimated information.

Next, the payment system 1 determines the number of axles (S114). Specifically, the axle number determination means 404 counts the number of axles of the vehicle being used for traveling from the portion of the image data captured by the processing of S111 that corresponds to the side of the vehicle. The axle number determination means 404 then determines the count result as the number of axles of the vehicle.

Next, the payment system 1 determines whether or not there is a fault (S115). Specifically, the fault determination means 405 determines whether or not a fault discount is to be applied from the portion of the image data captured by the process of S111 that corresponds to the fault/fault identification section.

When the process of S115 is completed, the payment system 1 ends the series of processes in FIG. 16. Note that in the vehicle determination process, the processes of S112 to S115 may be processed in any other order or may be executed in parallel. In the vehicle determination process, a determination process associated with information not used in calculating the toll fee may be omitted. The vehicle determination process may at least perform at least one of the following: reading the vehicle number, detecting the vehicle within the toll gate, determining the vehicle type, determining the number of axles, and checking the direction of travel. Information related to the determination process omitted in the vehicle determination may be omitted from various databases.

Figure 17 is a schematic diagram showing a specific example of vehicle determination processing in the payment system 1 according to the embodiment. Figure 17 shows an example of the side image capture result of a four-wheeled vehicle WV. In the image shown in Figure 17, the vehicle WV has, for example, a front license plate NPF, a rear license plate NPR, a windshield FG, an identification unit IB, and wheels WH1 and WH2.

The front license plate NPF is installed in front of the vehicle WV, and the rear license plate NPR is installed in the rear of the vehicle WV. Therefore, the front license plate NPF and the rear license plate NPR can be photographed by the camera 14B in front of the vehicle detection area 12 and the camera 15B in the rear of the vehicle detection area 12, respectively. The identification unit IB is installed, for example, on the inside of the windshield FG. In this case, the identification unit IB is photographed, for example, by the camera 14A. The tires of each of the wheels WH1 and WH2 are in contact with the ground in the image of the side of the vehicle WV. In this case, the axle number determination means 404 determines that the number of axles of the vehicle WV is "2" based on the number of tires in contact with the ground when viewed from the side of the vehicle WV.

The number reading means 402 only needs to determine the vehicle number of a vehicle in the vehicle detection area 12 based on the photographing results of at least one of the front number plate NPF and the rear number plate NPR. If the vehicle is a two-wheeled vehicle, it does not have a front number plate NPF but has a rear number plate NPR. Therefore, when determining the vehicle number of a two-wheeled vehicle, the number reading means 402 determines the vehicle number based on the photographing results of the rear number plate NPR. In vehicles that use the disability discount, it is sufficient that an identification unit IB is installed so that it can be identified by either of the cameras 14 and 15. On the other hand, vehicles of users who do not use the disability discount do not need to have an identification unit for the presence or absence of a disability.

(First admission process)
18 is a flowchart showing an example of the first entry process of the payment system 1 according to the embodiment. The flow of the first entry process will be described below with reference to FIG.

When the first entry process starts, the payment system 1 stores the entry time and the name of the entry toll booth in the traveling vehicle information database 103 (S161). Specifically, the traveling vehicle information recording means 501 stores the entry time and the name of the entry toll booth in a record in the traveling vehicle information database 103 that is associated with the vehicle number of the vehicle in the vehicle detection area 12.

Next, the payment system 1 opens the gate 13 (S162). Specifically, the gate control means 503 causes the gate driving means 704 to execute a process to open the gate 13. Thereafter, the guide board control means 502 may cause the guide display means 706 (e.g., the guide board 16) to display a message encouraging vehicles in the toll booth to enter (enter) the toll road.

Next, the payment system 1 checks whether the vehicle has entered (S163). Specifically, the travel direction confirmation means 406 checks the travel direction and position of the vehicle within the vehicle detection area 12. For example, when the vehicle travels forward and leaves the vehicle detection area 12, the travel direction confirmation means 406 determines that the vehicle has entered the toll road.

If it is confirmed in the process of S163 that the vehicle has not entered (S163, NO), the payment system 1 executes the process of S163 again.

If it is confirmed in the process of S163 that the vehicle has entered (S163, YES), the payment system 1 proceeds to the process of S164.

In the process of S164, the payment system 1 closes the gate 13. Specifically, the gate control means 503 causes the gate driving means 704 to execute a process to close the gate 13.

Next, the payment system 1 stores the entry time, the name of the entrance toll booth, etc. in the usage history database 102 in association with the user's vehicle number (S165). Specifically, the history information recording means 507 stores information such as the entry time and the name of the entrance toll booth in a table in the usage history database 102 associated with the user. This allows the user to check the entry time to the toll road, the name of the entrance toll booth, etc. by accessing the history viewing website. Furthermore, in the processing of S165, the payment system 1 may notify the user's contact information, such as by email, that they have entered the toll road.

When processing of S165 is completed, the payment system 1 ends the series of processes shown in FIG. 18.

(Second admission process)
19 is a flowchart showing an example of the second entry process of the payment system according to the embodiment. The flow of the second entry process will be described below with reference to FIG.

When the second entry process starts, the payment system 1 issues a pass (S171). Specifically, the automatic toll collection machine 18 of the entrance toll gate system 10-1 issues a pass on which, for example, the entry time and the name of the entrance toll gate are recorded. In the process of S171, the payment system 1 may use a method other than a payment method using a pass as long as it is possible to pay the toll.

Next, the payment system 1 checks whether the pass ticket has been received (S172). Specifically, the pass permission determination means 504 checks whether the pass ticket has been received from the automatic toll collection machine 18. At this time, the information board control means 502 may cause the information display means 706 (e.g., the information board 16) to display a message encouraging the user of the vehicle in the toll gate to receive the pass ticket. Note that the processing of S172 may be a determination processing that is compatible with the processing of S171 in which the pass ticket is not used when the pass ticket is not used in the processing of S171.

If it is confirmed in the process of S172 that the pass has not been received (S172, NO), the payment system 1 executes the process of S172 again.

If it is confirmed in the processing of S172 that the pass has been received (S172, YES), the payment system 1 proceeds to processing of S161.

In the process of S161, the payment system 1 stores the entry time and the name of the entry toll gate in the traveling vehicle information database 103, as in the first entry process.

Next, the payment system 1 opens the gate 13 (S162) in the same manner as in the first entry process. Thereafter, the guide board control means 502 may cause the guide display means 706 (e.g., the guide board 16) to display a message encouraging vehicles in the toll booth to enter (enter) the toll road.

Next, the payment system 1 checks whether the vehicle has entered (S163), similar to the first entry process.

If it is confirmed in the process of S163 that the vehicle has not entered (S163, NO), the payment system 1 executes the process of S163 again.

If it is confirmed in the processing of S163 that the vehicle has entered (S164, YES), the payment system 1 proceeds to processing of S164.

In processing S164, the payment system 1 closes the gate 13, similar to the first entry processing.

When processing of S164 is completed, the payment system 1 ends the series of processes shown in FIG. 19.

<2-3> Exit toll gate processing Fig. 20 is a flowchart showing an example of the exit toll gate processing of the payment system 1 according to the embodiment. The payment system 1 is configured to repeatedly execute the series of processes shown in Fig. 20. The flow of the exit toll gate processing will be described below with reference to Fig. 20. Note that the "toll gate" in the exit toll gate processing corresponds to the exit toll gate system 10-2.

When the exit toll gate processing starts, the payment system 1 checks whether a vehicle has been detected within the toll gate (S10), similar to the entrance toll gate processing.

If no vehicle is detected within the toll gate in the process of S10 (S10, NO), the payment system 1 executes the process of S10 again. At this time, the guide board control means 502 may cause the guide display means 706 to display a message encouraging the vehicle to enter the toll gate.

If a vehicle is detected within the toll gate in the process of S10 (S10, YES), the payment system 1 proceeds to the process of S11. At this time, the guide board control means 502 causes the guide display means 706 to display a message indicating that the vehicle is prohibited from entering the toll gate.

In the process of S11, the payment system 1 executes the vehicle determination process in the same manner as the entrance toll gate process.

Next, the payment system 1 searches for a matching vehicle number in the traveling vehicle information database 103 (S20). Specifically, the passage permission determination means 504 searches the traveling vehicle information database 103 for the vehicle number detected in the vehicle detection area 12. In subsequent processing, the payment system 1 refers to information associated with the vehicle number found by the search in various databases.

Next, the payment system 1 checks whether the vehicle's number is present in the user registration information database 101, similar to the entrance toll gate processing (S13).

If it is confirmed in the processing of S13 that the vehicle number exists in the user registration information database 101 (S13, YES), the payment system 1 proceeds to processing of S14.

If it is confirmed in the processing of S13 that the vehicle number does not exist in the user registration information database 101 (S13, NO), the payment system 1 proceeds to processing of S23.

In the processing of S14, the payment system 1 checks whether the vehicle information matches between the traveling vehicle information database 103 and the user registration information database 101, in the same way as in the entrance toll gate processing.

If it is confirmed in the processing of S14 that the vehicle information matches between the traveling vehicle information database 103 and the user registration information database 101 (S14, YES), the payment system 1 proceeds to processing of S15.

If it is confirmed in the processing of S14 that the vehicle information does not match between the traveling vehicle information database 103 and the user registration information database 101 (S14, NO), the payment system 1 proceeds to processing of S23.

In processing S15, the payment system 1 checks whether the vehicle's number is not present in the unusable information database 104, similar to the entrance toll gate processing.

If it is confirmed in the process of S15 that the vehicle number does not exist in the unusable information database 104 (S15, YES), the payment system 1 proceeds to the process of S21.

If it is confirmed in the processing of S15 that the vehicle number exists in the unusable information database 104 (S15, NO), the payment system 1 proceeds to processing of S22.

In the process of S21, the payment system 1 executes the first exit process. The first exit process is a process for collecting tolls that is executed when a vehicle exits a toll road using a pre-registered payment method. Details of the first exit process will be described later. When the first exit process is completed, the payment system 1 ends the series of processes in FIG. 20.

In the process of S22, the payment system 1 executes the second exit process. The second exit process is a process for collecting tolls that is executed when a vehicle that has used the first entry process but for which the pre-registered payment method can no longer be used over time is allowed to exit the toll road. Details of the second exit process will be described later. When the second exit process is completed, the payment system 1 ends the series of processes in FIG. 20.

In the process of S23, the payment system 1 executes the third exit process. The third exit process is a toll collection process that is executed when a vehicle with no user registration, a vehicle suspected of fraud, or a vehicle that was unable to use a pre-registered payment method at the time of entry is allowed to exit the toll road. Details of the third exit process will be described later. When the third exit process is completed, the payment system 1 ends the series of processes in FIG. 20.

(First entry process)
21 is a flowchart showing an example of a first exit process of the payment system according to the embodiment. The flow of the first exit process will be described below with reference to FIG.

When the first exit process starts, the payment system 1 stores the exit time and the name of the exit toll gate in the traveling vehicle information database 103 (S211). Specifically, the traveling vehicle information recording means 501 stores the information on the exit time and the name of the exit toll gate in a record in the traveling vehicle information database 103 that is associated with the vehicle number of the vehicle in the vehicle detection area 12.

Next, the payment system 1 calculates the toll based on the usage information stored in the traveling vehicle information database 103 and the toll calculation table information database 105 (S212). Specifically, the toll calculation means 505 calculates the toll according to the usage information associated with the vehicle number in the vehicle detection area 12 in the traveling vehicle information database 103 by applying the toll according to the vehicle classification and the presence or absence of a disability stored in the toll calculation table information database 105.

Next, the payment system 1 stores the calculated toll amount in the traveling vehicle information database 103 (S213). Specifically, the traveling vehicle information recording means 501 stores the toll amount calculated by the processing of S212 in a record in the traveling vehicle information database 103 that is associated with the vehicle number of the vehicle in the vehicle detection area 12.

Next, the payment system 1 charges the toll using the payment method stored in the user registration information database 101 (S214). Specifically, the toll charging means 506 charges the toll calculated by the processing of S212 using the payment method included in the record in the user registration information database 101 that is associated with the vehicle number of the vehicle in the vehicle detection area 12.

Next, the payment system 1 opens the gate 13 (S215). Specifically, the gate control means 503 causes the gate driving means 704 to execute a process to open the gate 13. Thereafter, the guide board control means 502 may cause the guide display means 706 (e.g., the guide board 16) to display a message encouraging vehicles in the toll booth to exit the toll road.

Next, the payment system 1 checks whether the vehicle has exited (S216). Specifically, the travel direction confirmation means 406 checks the travel direction and position of the vehicle within the vehicle detection area 12. For example, if the vehicle is traveling forward and has exited the vehicle detection area 12, the travel direction confirmation means 406 determines that the vehicle has exited the toll road.

If it is confirmed in the process of S216 that the vehicle has not entered the race (S216, NO), the payment system 1 executes the process of S216 again.

If it is confirmed in the process of S216 that the vehicle has entered the race (S216, YES), the payment system 1 proceeds to the process of S217.

In the process of S217, the payment system 1 closes the gate 13. Specifically, the gate control means 503 causes the gate driving means 704 to execute a process to close the gate 13.

Next, the payment system 1 stores the exit time, the name of the exit toll gate, the toll, etc. in the usage history database 102 in association with the user's vehicle number (S218). Specifically, the history information recording means 507 stores information such as the exit time, the name of the exit toll gate, and the usage fee in a table in the usage history database 102 associated with the user. This allows the user to check the exit time from the toll road, the name of the exit toll gate, the toll, etc. by accessing the history viewing website. Furthermore, in the processing of S218, the payment system 1 may notify the user of their exit from the toll road via their contact information, such as email.

When processing of S218 is completed, the payment system 1 ends the series of processes shown in FIG. 21.

(Second entry process)
22 is a flowchart showing an example of the second exit process of the payment system according to the embodiment. The flow of the second exit process will be described below with reference to FIG.

When the second exit process starts, the payment system 1 stores the exit time and the name of the exit toll gate in the traveling vehicle information database 103, just like the first exit process (S211).

Next, similar to the first exit process, the payment system 1 calculates the toll based on the usage information stored in the traveling vehicle information database 103 and the toll calculation table information database 105 (S212).

Next, the payment system 1 stores the calculated toll amount in the traveling vehicle information database 103, similar to the first exit process (S213).

Next, the payment system 1 issues an instruction to settle the toll (S221). Specifically, the automatic toll collector 18 of the exit toll gate system 10-2 enters a state in which it can accept payment of the toll calculated in S212 in cash. The information board control means 502 also causes the information display means 706 (e.g., information board 16) to display the toll amount. The toll amount may be displayed by the automatic toll collector 18. The method of settling the toll in S221 is not limited to cash, and may be electronic payment such as credit card, transportation IC, barcode payment, or cryptocurrency.

Next, the payment system 1 checks whether the toll has been settled (S222). Specifically, the passage permission determination means 504 checks whether the driver of the vehicle has completed the settlement of the toll using the automatic toll collection machine 18.

If it is confirmed in the process of S222 that the toll has not been settled (S222, NO), the payment system 1 executes the process of S222 again.

If it is confirmed in the processing of S222 that the toll has been settled (S222, YES), the payment system 1 proceeds to processing of S215.

In the process of S215, the payment system 1 opens the gate 13, as in the first exit process. Thereafter, the guide board control means 502 may cause the guide display means 706 (e.g., the guide board 16) to display a message encouraging vehicles in the toll gate to exit the toll road.

Next, the payment system 1 checks whether the vehicle has exited (S216), similar to the first exit process.

If it is confirmed in the process of S216 that the vehicle has not entered the race, the payment system 1 executes the process of S216 again.

If it is confirmed in the process of S216 that the vehicle has entered the race, the payment system 1 proceeds to the process of S217.

In processing S217, the payment system 1 closes the gate 13, similar to the first exit processing.

Next, similar to the first exit process, the payment system 1 stores the exit time, the name of the exit toll gate, the toll, etc. in the usage history database 102 in association with the user's vehicle number (S218).

When processing of S218 is completed, the payment system 1 ends the series of processes shown in FIG. 22.

(Third entry process)
23 is a flowchart showing an example of the third exit process of the payment system according to the embodiment. The flow of the third exit process will be described below with reference to FIG.

When the third exit process starts, the payment system 1 issues an instruction to insert a pass (S231). Specifically, the information board control means 502 causes the information display means 706 (e.g., information board 16) to display a message encouraging users of vehicles in the toll gate to insert a pass.

Next, the payment system 1 checks whether the toll ticket has been inserted into the automatic toll collection machine 18 (S232). Specifically, the passage permission determination means 504 checks whether the toll ticket has been inserted into the automatic toll collection machine 18.

If it is confirmed in the process of S232 that the toll ticket has not been inserted into the automated toll collection machine 18 (S232, NO), the payment system 1 executes the process of S232 again.

If it is confirmed in the processing of S232 that the toll ticket has been inserted into the automatic toll collection machine 18 (S232, YES), the payment system 1 proceeds to processing of S211.

In the process of S211, the payment system 1 stores the exit time and the name of the exit toll gate in the traveling vehicle information database 103, as in the first exit process (S211).

Next, similar to the first exit process, the payment system 1 calculates the toll based on the usage information stored in the traveling vehicle information database 103 and the toll calculation table information database 105 (S212).

Next, the payment system 1 stores the calculated toll amount in the traveling vehicle information database 103, similar to the first exit process (S213).

Next, the payment system 1 issues an instruction to settle the toll, as in the second exit process (S221). At this time, the information board control means 502 causes the information display means 706 (e.g., information board 16) to display the amount of the toll.

Next, the payment system 1 checks whether the toll has been settled (S222), as in the second exit process.

If it is confirmed in the process of S222 that the toll has not been settled (S222, NO), the payment system 1 executes the process of S222 again.

If it is confirmed in the processing of S222 that the toll has been settled (S222, YES), the payment system 1 proceeds to processing of S215.

Next, the payment system 1 opens the gate 13 (S215) in the same manner as in the first exit process. Thereafter, the guide board control means 502 may cause the guide display means 706 (e.g., the guide board 16) to display a message encouraging vehicles in the toll gate to exit the toll road.

Next, the payment system 1 checks whether the vehicle has exited (S216), similar to the first exit process.

If it is confirmed in the process of S216 that the vehicle has not entered the race, the payment system 1 executes the process of S216 again.

If it is confirmed in the process of S216 that the vehicle has entered the race, the payment system 1 proceeds to the process of S217.

In processing S217, the payment system 1 closes the gate 13, similar to the first exit processing.

When the process of S217 is completed, the payment system 1 ends the series of processes in FIG. 23. Note that, in the case where the process of S171 in FIG. 19 is a toll payment method other than using a toll ticket, each of the processes of S231 and S232 may use a method that is compatible with the process of S171.

<3> Effects According to the settlement system 1 described above, it is possible to prevent fraud at toll booths of toll roads and reduce the introduction and maintenance costs of operators. The effects of the embodiment will be described in detail below.

A method using ETC (registered trademark) is known as a method for paying tolls on toll roads. This method requires the preparation of an on-board unit and an ETC card, which requires time and cost for advance preparation. In contrast, a method can be considered in which tolls are collected by combining the vehicle's license plate information with location information obtained from the positioning function of a mobile terminal (e.g. GPS). In this case, by using image processing and a mobile terminal, it is possible to reduce introduction and operating costs.

However, this method cannot detect illegal passage when the license plate has been replaced. Tolls are set, for example, based on the vehicle type and number of axles of the vehicle. One possible method for accurately detecting the vehicle type and number of axles is to use hardware devices such as vehicle identification footplates, vehicle length detectors, and vehicle height detectors. Combining a toll collection system that uses license plate information with hardware devices such as vehicle identification footplates can prevent illegal passage. However, this results in high implementation and maintenance costs for toll booth operators.

The payment system 1 according to the embodiment acquires information on the vehicle number and information on the vehicle type and number of axles from images captured by the cameras 14 and 15 through image processing. Then, based on the acquired information, the payment system 1 collectively manages information on vehicles traveling on the toll road in the traveling vehicle information database 103. As a result, a toll collection system for toll roads using the payment system 1 can determine whether the vehicle number and the vehicle type and number of axles of the vehicle actually traveling are appropriate. In other words, the payment system 1 can prevent unauthorized passage through the replacement of license plates in the same way as when hardware equipment is used.

In addition, in the payment system 1 according to the embodiment, the user pre-registers the vehicle number, the payment method to be used when using the toll road, and vehicle information such as the vehicle type and axles in the user registration information database 101. The payment method pre-registered in the user registration information database 101 is then used when passing through a toll gate. This allows the payment system 1 to simplify the procedure for passing through a toll gate to the same extent as when using a combination of an ETC card and an on-board unit.

Furthermore, the payment system 1 according to the embodiment allows a user to use a pre-registered payment method when using a toll road with a single registration, without the user having to send planned use information in advance. In other words, the payment system 1 allows a user to use a desired payment method regardless of the route taken, as long as the toll gate is managed by the management server 20-1. The payment system 1 is compatible with the current toll fee system, and can easily replace the current toll collection system. In other words, the number of hardware devices used at toll gates can be reduced by using the payment system 1.

As described above, the payment system 1 according to the embodiment can provide the operator of a toll booth with the advantages of preventing fraudulent passage and reducing implementation and maintenance costs by reducing hardware equipment. The payment system 1 can also provide the user of the toll booth with the advantage of reducing implementation costs by eliminating the need to prepare an on-board unit and ETC card. Therefore, the payment system 1 according to the embodiment can prevent fraud at toll booths on toll roads and reduce the operator's implementation and maintenance costs.

<4> Others In the embodiment, the flowchart used to explain the operation is merely an example. The order of the operations explained using the flowchart may be changed within the possible range, other processes may be added, or some processes may be omitted. In addition, based on the vehicle information determined in the process of S20 of the exit toll gate process, it may be determined whether the vehicle information of the same vehicle number has changed while traveling on the toll road. By making such a determination, it is possible to detect fraud after entering the toll road. In this case, the exit toll gate system 10-2, for example, refers to the traveling vehicle information database 103 and charges the higher of the tolls calculated based on the vehicle information at the time of entry and the time of exit. In this case, the toll is paid by cash, for example.

The hardware configurations of the server 20 and the terminal device 30 described in the embodiment may be other configurations. For example, instead of a CPU, an MPU (Micro Processing Unit), an ASIC (Application Specific Integrated Circuit), or an FPGA (Field-Programmable Gate Array) may be used. The functions of the server 20 and the terminal device 30 may be realized in part or in whole by dedicated hardware, or may be configured as a program executed by a processor such as a CPU. In other words, the functions of the server 20 and the terminal device 30 may be realized using a computer and a program. The program may be recorded on a storage medium, or the program may be provided via a network.

Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents as set forth in the claims.

1...payment system, 10...toll booth system, 10-1...entrance toll booth system, 10-2...exit toll booth system, 11...lane, 12...vehicle detection area, 13...gate, 14, 15...camera, 16, 17...guide board, 18...automatic toll collection machine, 19...roof, 20...server, 20-1...management server, 20-2...payment company server, 21...CPU, 22...ROM, 23...RAM, 24...storage device, 25...communication interface, 30...terminal device, 30-1...toll booth terminal device, 30-2...Administrator terminal device, 30-3...User terminal device, 31...CPU, 32...ROM, 33...RAM, 34...Storage device, 35...Communication interface, 36...Input interface, 37...Display, 100...Database storage unit, 101...User registration information database, 102...Usage history database, 103...Traveling vehicle information database, 104...Unavailable information database, 105...Fee calculation table information database, 200...Information management unit, 201...Utilization User registration website operating means, 202... history viewing website operating means, 203... tollgate management website operating means, 204... system management website operating means, 205... payment management means, 300... communication management unit, 400... image processing unit, 401... vehicle detection means, 402... number reading means, 403... vehicle type determination means, 404... axle number determination means, 405... fault determination means, 406... direction confirmation means, 500... main processing unit, 501... running vehicle information recording means, 502... guide board control control means, 503...gate control means, 504...passage permission determination means, 505...toll fee calculation means, 506...toll fee billing means, 507...history information recording means, 601...user information registration means, 602...usage history viewing means, 603...toll gate operation means, 604...system management means, 605...payment approval/disapproval notification means, 701...vehicle front photographing means, 702...vehicle rear photographing means, 703...vehicle side photographing means, 704...gate driving means, 705...toll collection machine control means, 706...guidance display means

Claims (13)

A processor capable of executing a toll collection process for a toll road based on a first database and a second database,
The first database is configured to store information on a vehicle number, a time of entry into a toll road, a name of an entry toll gate, a time of exit from a toll road, a name of an exit toll gate, a vehicle type, and a number of axles;
The second database is configured to store vehicle information including a vehicle number, a vehicle model, and a number of axles, and information on a payment method, which are registered in advance by a user;
The processor, in the receipt process,
Based on the image data, reading the vehicle number within the toll booth, detecting the vehicle within the toll booth, determining the vehicle type, determining the number of axles, and confirming the direction of travel are performed, and the acquired vehicle information is stored in the first database;
Calculating a toll based on information associated with the read vehicle number among information stored in the first database;
billing the user for the calculated toll using a payment method associated with the read vehicle number among the information stored in the second database;
Payment device. The processor, in the receipt process,
When the read vehicle number is registered in the second database, a toll is charged using a payment method associated with the read vehicle number among the information stored in the second database;
If the read vehicle number is not included in the second database, a toll is charged using cash or electronic payment.
The payment device according to claim 1 . The processor, in the receipt process,
When the vehicle information acquired based on the image data matches the vehicle information stored in the second database and associated with the read vehicle number, the toll is charged to the user using a payment means associated with the read vehicle number among the information stored in the second database;
When the vehicle information acquired based on the image data does not match the vehicle information stored in the second database and associated with the read vehicle number, a toll is charged using cash or electronic payment.
The payment device according to claim 1 . When it is confirmed in the collection process that the read vehicle number is registered in the second database and the registered payment method is unavailable, the processor collects the toll using cash or electronic payment.
The payment device according to claim 1 . The processor, in the toll collection process, determines whether or not a disability discount is applicable based on the image data, and if the disability discount is applicable, charges the toll with the disability discount applied.
The payment device according to claim 1 . The processor stores in a third database a history of toll road use by a vehicle having a vehicle number registered in the second database;
the third database is referenced by a website that allows users to access the usage history;
The payment device according to claim 1 . A payment device according to claim 1 ;
a storage device configured to be able to store the first database and the second database;
A photographing device capable of photographing a vehicle in a toll booth so that the license plate, the vehicle type, and the number of axles can be identified.
Payment system. A payment method using a first database configured to store information such as a vehicle number, a time of entry into a toll road, a name of an entry toll gate, a time of exit from a toll road, a name of an exit toll gate, a vehicle type, and a number of axles, and a second database configured to store vehicle information including the vehicle number, the vehicle type, and the number of axles, which are registered in advance by a user, and information on a payment method,
Based on the image data, execute at least one of a group consisting of reading the vehicle number in the toll booth, detecting the vehicle in the toll booth, determining the vehicle type, determining the number of axles, and confirming the direction of travel, and store the acquired vehicle information in the first database;
Calculating a toll based on information associated with the read vehicle number among information stored in the first database;
and charging the calculated toll to the user using a payment method associated with the read vehicle number among the information stored in the second database.
Payment Method. When the read vehicle number is registered in the second database, charging a toll using a payment method associated with the read vehicle number among the information stored in the second database;
If the vehicle number is not included in the second database, charging a toll using cash or electronic payment.
The payment method according to claim 8. When the vehicle information acquired based on the image data matches the vehicle information stored in the second database and associated with the read vehicle number, charging the user a toll using a payment method associated with the read vehicle number among the information stored in the second database;
and if the vehicle information acquired based on the image data does not match the vehicle information stored in the second database and associated with the read vehicle number, charging a toll using cash or electronic payment.
The payment method according to claim 8. If it is confirmed that the vehicle number read is registered in the second database and the registered payment method is unavailable, the toll is charged using cash or electronic payment.
The payment method according to claim 8. The method further includes determining whether or not a disability discount is applicable based on the image data, and if the disability discount is applicable, charging a toll fee to which the disability discount has been applied.
The payment method according to claim 8. and storing in a third database a history of toll road use by a vehicle having a vehicle number registered in the second database,
the third database is referenced by a website that allows users to access the usage history;
The payment method according to claim 8.