Post-payment collection system and post-payment collection method

Abstract

To provide an ex-post collection system with which it is possible to more reliably collect the toll of non-ETC vehicles by an inexpensive and simple configuration.SOLUTION: An ex-post collection system comprises a roadside device, a monitoring device, and a server. The roadside device includes a vehicle image acquisition unit for capturing the image of a non-ETC vehicle, a certificate imaging unit for capturing the image of a public certificate held by a user, and a printing unit for issuing an invoice for the toll of the non-ETC vehicle. The monitoring device includes a printing request unit for requesting the roadside device to issue an invoice, and an ex-post collection data creation unit for creating data for ex-post collection including user information, vehicle information, passage information, and payment information. The server includes a storage for recording the data for ex-post collection, and a browsing data creation unit for creating data for browsing which is the data for web pages with which at least some of the data for ex-post collection can be browsed.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a post-collection system and a post-collection method. [Background Art]

[0002] On toll roads, an Electronic Toll Collection System (ETC (registered trademark) system, also referred to as an "automatic toll collection system") is used to automatically collect tolls from vehicles equipped with an on-board device (hereinafter also referred to as "ETC vehicles") (see, for example, Patent Document 1).

[0003] On the other hand, for vehicles not equipped with an on-board device, or vehicles that cannot use the ETC system due to an abnormality in the on-board device or the like (hereinafter collectively referred to as "non-ETC vehicles"), a toll collector stationed at a manned booth provided on the roadside of the toll gate lane is required to meet face-to-face with the user riding in the non-ETC vehicle, and collect the toll by directly handling the transfer of toll tickets, cash, credit cards, and the like. However, when collecting tolls from non-ETC vehicles, contact such as cash transfer occurs between the user and the toll collector, which creates a risk of infection with infectious diseases such as COVID-19. Furthermore, if a toll collector becomes infected, a shortage of toll collectors may disrupt toll gate operations.

[0004] In recent years, since the usage rate of ETC systems is sufficiently high, it has been considered to make toll gates unmanned and exclusive to ETC vehicles. In consideration of the case where a non-ETC vehicle enters an ETC-only toll gate, for example, Patent Document 1 describes a mechanism for retrospectively collecting tolls from non-ETC vehicles by reading and recording personal information recorded on the official identification document of a user riding in a non-ETC vehicle using a non-contact card reader. [Prior Art Documents] [Patent Documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2023-37224 [Overview of the project] [Problems that the invention aims to solve]

[0006] If toll booths are designated exclusively for ETC vehicles, it is undesirable to install expensive equipment such as automated toll collection machines for non-ETC vehicles, which are expected to be few in number. Therefore, when installing equipment for post-payment collection for non-ETC vehicles at toll booths, it is desirable to use inexpensive equipment or existing equipment to create an equipment configuration that can suppress cost increases and lack of installation space.

[0007] Furthermore, when collecting tolls for non-ETC vehicles retroactively, it is conceivable to distribute pamphlets to users explaining payment methods and deadlines (for example, transferring the money to a designated bank account within X days). In this case, users would need to take the pamphlet home, calculate the payment deadline, and go to a bank or convenience store to pay the toll. Due to the complexity of this payment procedure, it is conceivable that a certain number of users would be late in paying or not pay at all. In such cases, toll road operators could incur costs such as sending reminder notices and costs associated with non-payment by users. Therefore, when collecting tolls retroactively, a system is needed to ensure that users make payments more reliably.

[0008] The purpose of this disclosure is to provide a post-payment collection system and method that enable more reliable collection of tolls from non-ETC vehicles with an inexpensive and simple configuration. [Means for solving the problem]

[0009] According to one aspect of this disclosure, the post-collection system is a post-collection system that collects tolls from non-ETC vehicles that cannot be automatically collected by ETC when they arrive at an ETC lane at a toll booth on a toll road, and comprises a roadside device installed in the ETC lane, a monitoring device operated by a monitor who remotely monitors the ETC lane and creates data for post-collection of the non-ETC vehicle, and a server that stores the data for post-collection, wherein the roadside device comprises a vehicle image acquisition unit that photographs the non-ETC vehicle when it arrives at the ETC lane, a certificate photographing unit that photographs an official certificate held by the user riding in the non-ETC vehicle, and a printing unit that issues an invoice for the tolls of the non-ETC vehicle in accordance with the request of the monitoring device, and the monitoring device acquires user information read from the certificate image taken by the certificate photographing unit The system comprises: a user information acquisition unit; a vehicle information acquisition unit that acquires vehicle information read from vehicle images taken by the vehicle image acquisition unit; a traffic information acquisition unit that acquires traffic information that can identify the route traveled on the toll road by the non-ETC vehicle; a print request unit that requests the roadside device to issue an invoice containing at least one of the user information, the vehicle information, the traffic information, and payment information relating to the payment of tolls; and a post-collection data creation unit that creates post-collection data containing the user information, the vehicle information, the traffic information, and the payment information. The server comprises: a storage unit that records the post-collection data created by the monitoring device; and a viewing data creation unit that creates viewing data for a web page that allows viewing of at least a portion of the post-collection data, with some of the information displayed on the web page hidden so that the user and the vehicle cannot be identified by anyone other than the user.

[0010] According to one aspect of this disclosure, a post-collection method is a post-collection method in which, when a non-ETC vehicle that cannot be automatically collected by ETC arrives in an ETC lane at a toll booth on a toll road, the toll for the non-ETC vehicle is collected by a post-collection system comprising: a roadside device installed in the ETC lane; a monitoring device operated by a remote monitor monitoring the ETC lane to create post-collection data for the non-ETC vehicle; and a server to store the post-collection data, wherein the roadside device performs the steps of: photographing the non-ETC vehicle when the non-ETC vehicle that cannot be automatically collected by ETC arrives in the ETC lane; photographing the official identification document held by the user in the non-ETC vehicle; and issuing an invoice for the toll for the non-ETC vehicle in accordance with the request of the monitoring device operated by the remote monitor monitoring the ETC lane, and the monitoring device is photographed by the roadside device The system performs the steps of: obtaining user information read from a certificate image; obtaining vehicle information read from a vehicle image taken by the roadside device; obtaining traffic information that can identify the route the non-ETC vehicle traveled on the toll road; requesting the roadside device to issue an invoice containing at least one of the following: user information, vehicle information, traffic information, and payment information relating to the payment of tolls; and creating post-collection data containing the user information, vehicle information, traffic information, and payment information. The server then performs the steps of: recording the post-collection data created by the monitoring device; and creating viewing data for a web page that allows viewing of at least a portion of the post-collection data, with some of the information displayed on the web page hidden so that the user and the vehicle cannot be identified by anyone other than the user. [Effects of the Invention]

[0011] According to the above configuration, tolls from non-ETC vehicles can be collected more reliably with an inexpensive and simple setup. [Brief explanation of the drawing]

[0012] [Figure 1] This figure shows the overall configuration of the toll collection system according to the first embodiment. [Figure 2] This is a block diagram showing the functional configuration of the roadside device according to the first embodiment. [Figure 3] This is a block diagram showing the functional configuration of the monitoring device and server according to the first embodiment. [Figure 4] This figure shows an example of data for post-collection according to the first embodiment. [Figure 5] This figure shows an example of a total vehicle information table according to the first embodiment. [Figure 6] This figure shows an example of data for viewing according to the first embodiment. [Figure 7] This is a sequence diagram showing an example of post-collection processing according to the first embodiment. [Figure 8] This figure shows an example of an invoice according to the first embodiment. [Figure 9] This is a flowchart showing an example of post-collection processing according to the first embodiment. [Modes for carrying out the invention]

[0013] <First Embodiment> The embodiments will be described in detail below with reference to the drawings.

[0014] (Overall structure) Figure 1 shows the overall configuration of the toll collection system according to the first embodiment. The toll collection system 100 according to this embodiment is installed at a toll booth (entrance toll booth or exit toll booth) on a toll road and collects tolls from vehicles V traveling on a lane L connecting the toll road and a general road. Vehicles V include ETC vehicles equipped with an on-board unit and non-ETC vehicles not equipped with an on-board unit.

[0015] In this embodiment, lane L is an ETC-only lane (hereinafter also referred to as the "ETC lane") that collects tolls from ETC vehicles using the ETC system.

[0016] Furthermore, the toll collection system 100 according to the present embodiment functions as a "post-collection system" that collects the toll of a non-ETC vehicle after the vehicle passes when a non-ETC vehicle arrives at the ETC lane L.

[0017] In the present embodiment, an example in which the toll collection system 100 is provided at an exit tollgate will be described. Hereinafter, the direction in which the ETC lane L extends (±X direction) is referred to as the "lane direction". Furthermore, the toll road side (-X side) in the lane direction is also referred to as the "upstream side", and the general road side (+X side) is also referred to as the "downstream side". Furthermore, the width direction of the ETC lane L (±Y direction) is referred to as the "lane width direction".

[0018] Furthermore, although FIG. 1 shows an example in which only one ETC lane L is provided at the tollgate, the present invention is not limited thereto. In other embodiments, a plurality of ETC lanes L may be provided at the tollgate.

[0019] As shown in FIG. 1, the toll collection system 100 includes a roadside device 1, a monitoring device 4, and a server 5.

[0020] (Configuration of Roadside Device) FIG. 2 is a block diagram showing the functional configuration of the roadside device according to the first embodiment. As shown in FIG. 1 and FIG. 2, the roadside device 1 includes an ETC facility 2 and a printing device 3.

[0021] The ETC facility 2 is a group of devices for performing wireless communication with an on-board device mounted on an ETC vehicle and executing processing for automatically collecting tolls. The ETC facility 2 may be a group of devices used in conventional ETC systems.

[0022] As shown in FIG. 1, the ETC facility 2 includes an entrance-side vehicle detector 21, a license plate reader 22 (NP reader), a roadside antenna 23, a communication vehicle detector 24, a lane server 25, a start controller 26, an exit-side vehicle detector 27, a monitoring camera 28, and a vehicle type discrimination device 29.

[0023] The entry-side vehicle detector 21 is a through-type vehicle detector, as shown in Figure 1, for example, and outputs a detection signal that can distinguish whether or not a vehicle V is present at the entry detection position X1.

[0024] The NP reader 22 captures a vehicle image, including the license plate, of vehicle V when the approaching vehicle detector 21 detects the presence of a vehicle. The NP reader 22 also reads the license plate information (NP information) of vehicle V from the captured vehicle image. The NP information includes the size and color of the license plate, and the characters written on the license plate (such as place name, classification number, symbol, and serial number). The NP reader 22 is one embodiment of the vehicle image acquisition unit in this embodiment. The vehicle image (NP image) and the read NP information captured by the NP reader 22 are transmitted to the monitoring device 4 via the lane server 25.

[0025] When the vehicle entry detector 21 detects that vehicle V is entering the ETC lane L, the roadside antenna 23 emits radio waves for wireless communication towards a predetermined communication area on the ETC lane L. The roadside antenna 23 also communicates wirelessly with an on-board unit (not shown) mounted on vehicle V using a predetermined procedure to obtain on-board unit information from the on-board unit and to notify the on-board unit of the toll fee.

[0026] The communication vehicle detector 24 detects when vehicle V has passed the communication termination position X2. The communication vehicle detector 24 has the same equipment configuration as the entry vehicle detector 21. When the communication vehicle detector 24 detects that vehicle V has passed the communication termination position X2, the roadside antenna 23 stops emitting radio waves.

[0027] The lane server 25 executes the process of collecting tolls from ETC vehicles. The toll collection process by the lane server 25 is the same as that of the conventional ETC system, so a detailed explanation is omitted.

[0028] The departure control unit 26 raises and lowers the opening and closing bar to open the ETC lane L (permission for vehicle V to exit the ETC lane L) and to close it (restriction of vehicle V to exit the ETC lane L).

[0029] The exiting vehicle detector 27 detects when vehicle V passes the exit detection position X3 (exiting from ETC lane L). The exiting vehicle detector 27 has the same equipment configuration as the entering vehicle detector 21.

[0030] The surveillance camera 28 photographs the vehicle V traveling in the ETC lane L from an oblique angle above. Therefore, the image captured by the surveillance camera 28 includes the front and side of the vehicle V. In the case of low-profile vehicles V, the top of the vehicle body may also be included in this image. The surveillance camera 28 is one embodiment of the vehicle image acquisition unit in this embodiment. The vehicle image captured by the surveillance camera 28 is transmitted to the monitoring device 4 via the lane server 25.

[0031] Furthermore, if an NP reader 22 is not installed in the ETC lane L, the surveillance camera 28 may receive instructions from the monitoring device 4 and photograph the license plates of non-ETC vehicles V.

[0032] The vehicle type identification device 29 determines whether vehicle V is towed and its vehicle type classification based on NP information and vehicle specifications of vehicle V (number of axles, height, length, width, etc.) detected by sensors (not shown). The determination results of the vehicle type identification device 29 (vehicle type information indicating the vehicle type classification of vehicle V, and towing information indicating whether or not it is towed) are transmitted to the monitoring device 4 via the lane server 25. Note that the determination process by the vehicle type identification device 29 is the same as that of the conventional ETC system, so a detailed explanation is omitted.

[0033] As shown in Figure 1, the printing device 3 is installed on island I downstream of the communication vehicle detector 24 (+X side) and upstream of the start control unit 26 (-X side) in the lane direction. For example, the printing device 3 is positioned so as to coincide with the position of the driver's seat of a vehicle stopped in front of the start control unit 26 (-X side) when the opening / closing bar of the start control unit 26 is closed.

[0034] The printing device 3 issues an invoice for post-payment collection of tolls when a non-ETC vehicle enters an ETC lane, after the vehicle has exited the toll road. The printing device 3 comprises a lane-side communication unit 31, a certificate scanning unit 32, an input unit 33, a printing unit 34, a processor 35, a memory 36, a storage unit 37, a communication interface 38, and a display unit 29.

[0035] Furthermore, the lane-side communication unit 31, certificate scanning unit 32, input unit 33, and printing unit 34 are located on the side of the printing device 3 facing the lane L side (the +Y side in Figure 1) so that they can be used by users riding in non-ETC vehicles.

[0036] The lane-side communication unit 31 is an intercom handset for users to communicate with toll booth attendants stationed at the toll booth office.

[0037] The certificate photography unit 32 is a camera that photographs official identification documents held by users riding in non-ETC vehicles. Official identification documents are personal identification documents issued by government agencies or other related organizations, such as driver's licenses, My Number cards, passports, and disability certificates.

[0038] The input unit 33 is a device for receiving input operations from the user. For example, the input unit 33 may be a keyboard (numeric keypad) or touch panel for entering a PIN, which will be described later.

[0039] The printing unit 34 is a printer that prints invoices for post-payment (payment of tolls after the fact) in accordance with the instructions of the printing processing unit 352, which will be described later.

[0040] The processor 35 performs the functions of a data processing unit 351, a printing processing unit 352, and a password acquisition unit 353 by operating according to a predetermined program.

[0041] The data processing unit 351 reads the information on the certificate from the certificate image captured by the certificate imaging unit 32 using technologies such as OCR. The information on the certificate includes the certificate number (driver's license number, My Number, passport number, etc.) recorded on the official certificate, the user's name and address, etc. The data processing unit 351 transmits the certificate image captured by the certificate imaging unit 32, the information on the certificate read from the certificate image, and the user information to the monitoring device 4.

[0042] The printing processing unit 352, in accordance with the request from the monitoring device 4, causes the printing unit 34 to print the invoice.

[0043] The PIN acquisition unit 353 acquires a PIN for accessing a web page where the post-collection data described later can be viewed using a browser or similar device. The PIN is set by the user using the input unit 33 of the printing device 3.

[0044] Memory 36 is a so-called main memory and has the storage area necessary for the operation of the processor 35.

[0045] Storage 37 refers to so-called auxiliary storage devices, such as HDDs (Hard Disk Drives) and SSDs (Solid State Drives), which are large-capacity storage devices.

[0046] The communication interface 38 transmits and receives data to and from the monitoring device 4 via the network.

[0047] The display unit 39 is a display device (such as a liquid crystal display) for displaying various information related to the post-payment collection of tolls to the user.

[0048] (Configuration of the monitoring device) Figure 3 is a block diagram showing the functional configuration of the monitoring device and server according to the first embodiment. As shown in Figure 3, the monitoring device 4 includes an office-side communication unit 41, an operation unit 42, a display unit 43, a processor 44, a memory 45, a storage 46, and a communication interface 47.

[0049] The office-side communication unit 41 is an intercom master unit for monitoring personnel to communicate with users riding in non-ETC vehicles.

[0050] The control unit 42 is an input device (keyboard, mouse, etc.) for receiving operations from the monitoring operator.

[0051] The display unit 43 is a display device (such as a liquid crystal display) for displaying various information related to the retroactive collection of tolls for non-ETC vehicles. The operation unit 42 and the display unit 43 may be integrated into a single unit (such as a touch panel).

[0052] The processor 44 operates according to a predetermined program, performing functions as a user information acquisition unit 441, a vehicle information acquisition unit 442, a traffic information acquisition unit 443, a print request unit 444, and a post-collection data creation unit 445.

[0053] The user information acquisition unit 441 acquires user information that includes information that can identify a user riding in a non-ETC vehicle V. In this embodiment, the user information acquisition unit 441 acquires user information from the data processing unit 351 of the roadside device 1, which includes a certificate image and ticket information read from the certificate image.

[0054] The vehicle information acquisition unit 442 acquires vehicle information relating to the non-ETC vehicle V. The vehicle information includes NP information that can identify the non-ETC vehicle V, vehicle type information of the non-ETC vehicle V, and whether or not it is towed. In this embodiment, the vehicle information acquisition unit 442 acquires the NP information of the non-ETC vehicle V read by the NP reader 22. In addition, the vehicle information acquisition unit 442 acquires vehicle type information indicating the vehicle type classification of the non-ETC vehicle V determined by the vehicle type determination device 29, and towing information indicating whether or not it is towed, in place of or in addition to the NP information. Note that the vehicle type information and towing information may be entered by the monitor by referring to vehicle images from the surveillance camera 28, etc.

[0055] The traffic information acquisition unit 443 acquires traffic information that can identify the route traveled by a non-ETC vehicle V. The traffic information includes information about toll booths (entrance toll booths, exit toll booths, intermediate toll booths, and transfer toll booths) that the non-ETC vehicle V passed through, and information about predetermined passage determination points on toll roads. For example, the traffic information acquisition unit 443 acquires traffic information D13 entered by a traffic monitor based on information obtained from a user. Alternatively, the traffic information acquisition unit 443 may acquire traffic information linked to the NP information of the non-ETC vehicle V from the server 5, which will be described later, and input it automatically. The traffic information created by the server 5 is automatically linked to the NP information read by the NP readers at toll booths and passage determination points. By using the traffic information created by the server 5, it is possible to automatically identify and input when and which toll booths and passage determination points a vehicle V with each piece of NP information passed through.

[0056] The printing request unit 444 requests the roadside device 1 (printing device 3) to print an invoice containing at least some of the following information: user information, vehicle information, traffic information, and payment information.

[0057] The post-collection data creation unit 445 creates post-collection data D1 for tolls of non-ETC vehicles V. The created post-collection data D1 is recorded on the server 5.

[0058] Figure 4 shows an example of data for post-collection according to the first embodiment. As shown in Figure 4, the data D1 for post-collection includes user information D11, vehicle information D12, traffic information D13, payment information D14, and recorded data D15 acquired by each part of the monitoring device 4.

[0059] User information D11 includes the certificate number of the official identification document, the user's name, address, and an image of the certificate. Furthermore, if the user presents a disability certificate to receive a discount, discount information such as whether a disability discount is available and the details written on the disability certificate may also be included in user information D11.

[0060] Vehicle information D12 includes NP information of the non-ETC vehicle V, vehicle type information, towing information indicating whether or not it is towed, and vehicle images taken by the NP reader 22 and surveillance camera 28. If the non-ETC vehicle V is long, it may be difficult for the surveillance camera 28 to capture the entire vehicle in a single image. In this case, vehicle information D12 may include multiple vehicle images taken by the surveillance camera 28 at regular intervals, capturing parts of the vehicle from front to rear. The vehicle images may also be moving images.

[0061] Traffic information D13 includes the toll booths (entrance toll booths, exit toll booths, intermediate toll booths, and transfer toll booths) that the non-ETC vehicle V passed through, as well as the identification information (toll booth name / toll booth ID, location name / location ID) and operating company for each toll booth and location on the toll road, the lane number that the non-ETC vehicle V traveled in, and the date and time that the non-ETC vehicle V passed through each toll booth and location.

[0062] Payment information D14 includes the invoice issuance date and time, payment ID, toll fee, payment due date, and payment method. The payment ID is unique information used to associate the invoice with the post-collection data D1. The payment due date may be automatically entered, for example, a predetermined number of days after the issuance date, or it may be entered manually by the monitor. The payment method is information indicating how the user will pay the toll fee, such as the bank account number to which the toll fee will be transferred.

[0063] Audio data D15 is a recording of a conversation between a supervisor and a user.

[0064] Memory 45 is a so-called main memory and has the storage area necessary for the operation of the processor 44.

[0065] Storage 46 refers to so-called auxiliary storage devices, such as HDDs (Hard Disk Drives) and SSDs (Solid State Drives), which are large-capacity storage devices.

[0066] The communication interface 47 transmits and receives data between the roadside device 1 (lane server 25, printing device 3) and server 5 via the network.

[0067] (Server configuration) As shown in Figure 3, the server 5 includes a processor 51, memory 52, storage 53, and a communication interface 54.

[0068] The processor 51 performs its functions as a traffic information creation unit 511 and a viewing data creation unit 512 by operating according to a predetermined program.

[0069] The traffic information creation unit 511 retrieves NP information for non-ETC vehicles V from the all-vehicle information table D2, which stores NP information read by NP readers at each toll booth and pass-through determination point on the toll road, and creates traffic information that includes information on the toll booths passed by the non-ETC vehicles and pass-through determination points along the route. The traffic information creation unit 511 may also provide traffic information for non-ETC vehicles V upon request from the traffic information acquisition unit 443 of the monitoring device 4.

[0070] Figure 5 shows an example of a total vehicle information table according to the first embodiment. As shown in Figure 5, the total vehicle information table D2 includes the type of toll gate or passage determination point (entrance toll gate, exit toll gate, intermediate toll gate, transfer toll gate, or passage determination point), the toll gate operating company, the vehicle's lane (lane number), the vehicle's NP information and image, and the date and time of the vehicle's passage.

[0071] In this embodiment, when the traffic information creation unit 511 receives post-collection data D1 for a non-ETC vehicle V from the monitoring device 4, it searches the NP information of this non-ETC vehicle V from the all-vehicle information table D2 to create traffic information and updates (adds or modifies) the post-collection data D1.

[0072] The data creation unit 512 creates data for viewing, D3, which allows users to check the contents of the post-collection data D1 using a browser or similar device. If a password is set, the data for viewing, D3, is recorded in association with that password. In this case, the data for viewing, D3, can only be viewed when the password set by the user is entered.

[0073] Figure 6 shows an example of browsing data according to the first embodiment. As shown in Figure 6, for example, the viewing data D3 includes user information D31, vehicle information D32, traffic information D33, payment information D34, and recording data D35, similar to the post-collection data D1. In other embodiments, the viewing data D3 may include only some of the information D31 to D35.

[0074] Furthermore, in the example in Figure 6, user information D31 includes the certificate number, the user's name and address, discount information, and a certificate image, but in other embodiments, only some of this information may be included. Similarly, in the example in Figure 6, vehicle information D32 includes NP information, vehicle type information, towing information, and a vehicle image, but in other embodiments, only some of this information may be included.

[0075] Furthermore, the viewing data creation unit 512 creates viewing data D3 in which parts of the user information D31 and vehicle information D32 are hidden so that it would be difficult to identify the user or non-ETC vehicle if someone other than the user were to view it. For textual information such as NP information, the viewing data creation unit 512 hides or masks at least a part of it, such as changing the serial number "12-34" to "12-XX". In addition, the viewing data creation unit 512 applies processing such as blurring or blacking to at least a part of the certificate image and vehicle image (parts that can identify the user or vehicle, such as the certificate number and NP information).

[0076] Memory 52 is a so-called main memory and has the storage area necessary for the operation of the processor 51.

[0077] Storage 53 is a so-called auxiliary storage device, such as an HDD (Hard Disk Drive) or SSD (Solid State Drive), which is a large-capacity storage device. Storage 53 records data for post-collection D1, a table of all vehicle information D2, and data for viewing D3.

[0078] Communication I / F54 transmits and receives data to and from monitoring device 4 via the network.

[0079] (Post-payment collection process 1: Invoice issuance process) Figure 7 is a sequence diagram showing an example of post-collection processing according to the first embodiment. Here, referring to Figure 7, we will explain the process for issuing an invoice when a non-ETC vehicle V arrives at the ETC lane L of a toll booth.

[0080] When a non-ETC vehicle V enters the ETC lane L, the ETC equipment 2 does not process the toll collection, and the departure control unit 26 remains closed. As a result, the non-ETC vehicle V stops before the departure control unit 26. In this case, the passenger in the non-ETC vehicle V operates the lane-side communication unit 31 of the roadside device 1 (printing device 3) to start a conversation with the toll booth attendant (step S101).

[0081] When the monitor confirms, based on conversations with users and information received from ETC equipment 2, that toll collection processing for non-ETC vehicles has not been performed, they instruct the monitoring device 4 to start the post-payment collection process for non-ETC vehicles. At this point, the post-payment collection data creation unit 445 of the monitoring device 4 begins recording the conversation with the user (step S102).

[0082] Next, the process of acquiring the user's user information D11 is performed (step S103). The user information acquisition unit 441 of the monitoring device 4 instructs the roadside device 1 to photograph the certificate when the monitor initiates the post-collection process or when the monitor initiates the photography instruction operation (step S103A). The roadside device 1 then activates the certificate photography unit 32. The monitor also requests the user to hold their official certificate over the certificate photography unit 32.

[0083] The certificate scanning unit 32 of the roadside device 1 scans the official certificate held up by the user (step S103B). In this embodiment, the data processing unit 351 of the roadside device 1 (printing device 3) reads the certificate information from the certificate image captured by the official certificate using OCR or the like, and transmits the user information D11, which includes the certificate image and the certificate information, to the monitoring device 4.

[0084] Next, the user information acquisition unit 441 of the monitoring device 4 acquires user information D11 (step S103C). The acquired user information D11 is displayed on the display unit 43 of the monitoring device 4.

[0085] The monitoring officer may check the user information D11 (certificate image and ticket information) displayed on the display unit 43. If there are any deficiencies, such as the entire official certificate not being visible, the image being unclear, or the ticket information being unreadable, the officer may remotely adjust the tilt, pan, etc. of the certificate shooting unit 32 by operating the control unit 42 of the monitoring device 4, and then repeat steps S103A to S103C.

[0086] In other embodiments, the user information acquisition unit 441 may acquire only the certificate image from the roadside device 1. In this case, instead of the data processing unit 351 of the roadside device 1, the user information acquisition unit 441 reads and acquires the certificate information from the certificate image using OCR or the like. In yet another embodiment, the user information acquisition unit 441 may acquire the certificate information manually entered by the monitor while viewing the certificate image.

[0087] Next, the process of acquiring vehicle information for the non-ETC vehicle V is performed (step S103).

[0088] For example, if an NP reader 22 is not installed in the ETC lane L, NP information is obtained from a vehicle image captured by the roadside device 1's surveillance camera 28. In this case, the vehicle information acquisition unit 442 of the surveillance device 4 instructs the roadside device 1 to photograph the vehicle's license plate (step S104A). Then, the surveillance camera 28 of the roadside device 1 (ETC equipment 2) photographs the license plate of the non-ETC vehicle V (step S104B). At this time, the data processing unit 351 of the roadside device 1 (printing device 3) reads the NP information from the vehicle image (NP image) captured by the surveillance camera 28 using OCR or the like, and transmits the vehicle information D12, which includes the vehicle image and NP information, to the surveillance device 4.

[0089] Next, the vehicle information acquisition unit 442 of the monitoring device 4 acquires vehicle information D12 (step S104C). The acquired vehicle information D12 is displayed on the display unit 43 of the monitoring device 4.

[0090] The monitor may check the vehicle information D12 (vehicle image and NP information) displayed on the display unit 43. If there are any deficiencies, such as an unclear image or unreadable NP information, the monitor may remotely adjust the tilt, pan, etc. of the monitoring camera 28 by operating the control unit 42 of the monitoring device 4, and then repeat steps S104A to S104C.

[0091] In other embodiments, the vehicle information acquisition unit 442 may acquire only vehicle images from the roadside device 1 (surveillance camera 28). In this case, instead of the data processing unit 351 of the roadside device 1, the vehicle information acquisition unit 442 reads and acquires NP information from the vehicle image using OCR or the like. In yet another embodiment, the vehicle information acquisition unit 442 may acquire NP information manually entered by a monitor while viewing the vehicle image.

[0092] Furthermore, if an NP reader 22 is provided in the ETC lane L, the NP reader 22 acquires NP information for a non-ETC vehicle V when the entry-side vehicle detector 21 detects a non-ETC vehicle V. In this case, steps S104A to S104B may be omitted, and in step S104C, the vehicle information acquisition unit 442 may acquire NP information for the non-ETC vehicle from the NP reader 22.

[0093] Furthermore, in step S104C, the vehicle information acquisition unit 442 may further acquire vehicle type information and towing information of the non-ETC vehicle V identified by the vehicle type identification device 29. Alternatively, the vehicle information acquisition unit 442 may acquire vehicle type information and towing information manually entered by the monitoring officer while viewing the vehicle image.

[0094] Next, the traffic information acquisition unit 443 of the monitoring device 4 acquires traffic information D13 (step S105). The traffic information acquisition unit 443 acquires traffic information D13 based on information that the monitoring officer has heard from the user, for example. Alternatively, the monitoring officer may ask the user to present a traffic ticket or transfer ticket, and input the traffic information D13 while checking the traffic ticket or transfer ticket photographed by the certificate photography unit 32.

[0095] In other embodiments, the traffic information acquisition unit 443 may request the server 5 to provide traffic information D13 for non-ETC vehicles V. For example, the traffic information creation unit 511 of the server 5 sequentially creates traffic information for each NP information in the post-processing described later (Figure 9). The traffic information acquisition unit 443 of the monitoring device 4 acquires the traffic information D13 created by the server 5 in step S105. This eliminates the need for monitoring personnel to manually input traffic information.

[0096] Next, the print request unit 444 of the monitoring device 4 requests the roadside device 1 (printing device 3) to print an invoice containing the acquired user information D11, vehicle information D12, traffic information D13, and at least a portion of the payment information D14 (step S106).

[0097] Then, the printing processing unit 352 of the roadside device 1 causes the printing unit 34 to print invoice D4 in accordance with the request from the monitoring device 4 (step S107).

[0098] Figure 8 shows an example of an invoice according to the first embodiment. Invoice D4 may include all of the following information: user information D11, vehicle information D12, traffic information D13, and payment information D14. However, printing all of this information would make invoice D4 very long. Therefore, invoice D4 may only include a selection of this information.

[0099] For example, as shown in Figure 8, invoice D4 may only print information D42, D43, and D44, which are excerpts from vehicle information D12, traffic information D13, and payment information D14. In this case, invoice D4 may also have URL information D46 printed on it, which allows access to a web page (viewing data D3 created by server 5) where the unprinted content can be viewed. This URL information D46 may be text, or it may be a two-dimensional code, as in the example in Figure 8.

[0100] Furthermore, when the printing processing unit 352 prints the certificate number, name, and address included in the user information D11 onto the invoice D4, it hides (conceals, masks) some of the characters before printing them on the printing unit 34. Similarly, when the printing processing unit 352 prints the NP information included in the vehicle information D12 onto the invoice D4, it hides (conceals, masks) some of the characters before printing them on the printing unit 34. This helps to prevent others from identifying the user or non-ETC vehicle if, for example, someone picks up an invoice D4 that the user has dropped. Also, even if some characters are hidden, the user themselves can understand that their certificate number and NP number are printed. In other words, it helps to deter non-payment of tolls by making the user aware that the toll road operator has information (evidence) that can identify them and their vehicle.

[0101] Next, the monitor requests the user to set a password to access the viewing data D3. The user uses the input unit 33 of the roadside device 1 (printing device 3) to set the password. The password acquisition unit 353 of the roadside device 1 then acquires the set password and transmits it to the monitoring device 4 (step S108).

[0102] In other embodiments, the user may omit setting a PIN. In this case, the PIN acquisition unit 353 automatically sets a PIN in step S108 and transmits it to the monitoring device 4. For example, the PIN acquisition unit 353 sets a common PIN for all users. Alternatively, the PIN acquisition unit 353 may generate and set a random PIN for each user. The PIN automatically set by the PIN acquisition unit 353 is displayed on the display unit 39 of the roadside device 1 (printing device 3) to notify the user. Furthermore, the PIN acquisition unit 353 may automatically generate a PIN using one or more pieces of information included in the user information D11. For example, the PIN acquisition unit 353 may set a part of the user's certificate number (for example, the last four digits), a serial number of NP information, or the address or date of birth listed on the certificate as the PIN. Alternatively, the PIN acquisition unit 353 may set a combination of this information (for example, the last four digits of the certificate number + a serial number of NP information) as the PIN. In this case, the information used as the PIN (for example, text information such as "Your PIN is the last four digits of your certificate number.") is printed on invoice D4 to notify the user. This allows users who know their user information D11 to easily find the correct PIN by looking at invoice D4. On the other hand, it makes it difficult for others who do not know the user information D1 to guess the PIN by looking at invoice D4.

[0103] In yet another embodiment, the PIN acquisition unit 353 may automatically set the predetermined PIN if the user has not set a PIN for a predetermined period of time or longer after the invoice D4 has been removed, or when the fare collection process for a subsequent vehicle has started.

[0104] Once the PIN setting is complete, the monitor performs an operation to allow the non-ETC vehicle V to pass (exit from ETC lane L). At this point, the monitoring device 4 instructs the roadside device 1 to allow the non-ETC vehicle V to depart (step S109).

[0105] When the roadside device 1 (for example, the lane server 25) receives instructions from the monitoring device 4, it sends an open command to the departure control unit 26 (step S110) to cause the non-ETC vehicle to exit the ETC lane L.

[0106] Furthermore, when the monitoring officer permits the passage of a non-ETC vehicle V, the post-collection data creation unit 445 of the monitoring device 4 terminates recording of the conversation with the user (step S111).

[0107] Next, the post-collection data creation unit 445 creates post-collection data D1, which includes user information D11, vehicle information D12, and traffic information D13 acquired by each part of the monitoring device 4, payment information D14, and recorded data D15 of a conversation between the user and the monitoring officer, and transmits it to the server 5 along with the PIN for recording (step S112).

[0108] The toll collection system 100 (post-collection system) executes the series of processes shown in Figure 7 each time a non-ETC vehicle V enters the ETC lane L.

[0109] (Post-collection processing 2: Back-office processing) Figure 9 is a flowchart showing an example of a post-collection process according to the first embodiment. Next, referring to Figure 9, we will explain the flow of back-end processing by Server 5.

[0110] First, the traffic information creation unit 511 of server 5 creates traffic information by linking information with the same NP information in the all-vehicle information table D2 (step S201). The creation of traffic information is performed sequentially, for example, each time the all-vehicle information table D2 is updated. In other words, each time a non-ETC vehicle V passes through an entrance toll gate, an intermediate toll gate, a transfer toll gate, or a pass-through determination point, the traffic information creation unit 511 links the NP information acquired by the NP reader at each toll gate and pass-through determination point to create and update the traffic information for this non-ETC vehicle V. Furthermore, when the non-ETC vehicle V arrives at an exit toll gate, the traffic information is updated by linking it with the NP information acquired by the NP reader at the exit toll gate, thereby immediately determining the travel route of this non-ETC vehicle V. In step S105 of Figure 7 described above, the traffic information for the non-ETC vehicle V created and updated in this way is provided to the monitoring device 4 (traffic information acquisition unit 443).

[0111] Furthermore, the traffic information creation unit 511 receives the post-collection data D1 and PIN of non-ETC vehicles V from the monitoring device 4 and records them in the storage 53 (step S202). At this time, for example, if the monitoring officer manually entered the traffic information D13 in step S105 of Figure 7, the post-collection data D1 is updated based on the traffic information created in step S201 (step S203). This allows for retrospective additions and corrections to be made based on the traffic information created from the all-vehicle information table D2, even if there are omissions or errors in the traffic information manually entered by the monitoring officer based on information gathered from users. The traffic information creation unit 511 may also include images of non-ETC vehicles V taken by the NP reader at each toll booth and passage determination point in the traffic information.

[0112] Next, the viewing data creation unit 512 of server 5 creates viewing data D3, which allows users to view the contents of the post-collection data D1 using a browser or the like. At this time, as described above, the viewing data creation unit 512 creates viewing data D3 with some of the user information D31 and vehicle information D32 hidden. The viewing data creation unit 512 also records the viewing data D3 linked to the encryption information and restricts access so that viewing data D3 can only be viewed if the user correctly enters the PIN.

[0113] After exiting the toll road, users can access the data D3 using the URL information D46 printed on the invoice D4 and their PIN. Furthermore, by making users aware that the data D3 contains evidence that can identify them and their vehicle, non-payment of tolls can be deterred.

[0114] (Effect, Action) As described above, the roadside device 1 according to this embodiment includes a vehicle image acquisition unit (NP reader 22, surveillance camera 28) that photographs a non-ETC vehicle V when the non-ETC vehicle V arrives in the ETC lane L, a certificate photographing unit 32 that photographs an official certificate held by the user riding in the non-ETC vehicle V, and a printing unit 34 that issues an invoice D4 for the toll charges of the non-ETC vehicle V. The printing unit 34 prints at least one of the following information on the invoice D4: traffic information D13 that can identify the travel route of the non-ETC vehicle V received from the monitoring device 4, vehicle information D12 that includes information read from the vehicle image taken by the vehicle image acquisition unit (NP reader 22, surveillance camera 28), user information D11 that includes information read from the certificate image taken by the certificate photographing unit 32, and payment information D14 regarding the payment of toll charges.

[0115] In this way, when a non-ETC vehicle V approaches the ETC lane L, the roadside device 1 can automatically issue an invoice for post-payment of tolls to the user. This allows for the unmanned operation of toll booths with an inexpensive and simple configuration. Furthermore, the roadside device 1 can issue an invoice D4 specific to each user. This makes it easier for users to understand the payment procedure compared to general post-payment instructions provided in brochures, etc. As a result, tolls from non-ETC vehicles can be collected more reliably.

[0116] Furthermore, the vehicle image acquisition unit is the NP reader 22, and the vehicle information D12 includes the NP information read by the NP reader 22. The printing unit 34 hides some of the characters in the NP information and prints it on the invoice D4.

[0117] In this way, the roadside device 1 can acquire NP information that can identify non-ETC vehicles V by using the existing NP reader 22 at the toll booth without adding any new configurations. Furthermore, by obscuring some of the characters in the NP information, the roadside device 1 can issue an invoice D4 with vehicle information D12 printed on it, which is difficult for others to identify the vehicle, but which the user can recognize as their own vehicle's NP information. This prevents others from identifying the vehicle from the invoice D4 if the invoice D4 is dropped by the user and picked up by someone else. In addition, by making the user aware that evidence that can identify their vehicle is recorded, non-payment of tolls can be deterred.

[0118] Furthermore, the vehicle image acquisition unit consists of an NP reader 22 and a surveillance camera 28, and the vehicle information D12 includes, in addition to the NP information, vehicle type information of a non-ETC vehicle V identified from one or more vehicle images captured by the surveillance camera 28.

[0119] In this way, the roadside device 1 can issue an invoice D4 with the vehicle type classification of the non-ETC vehicle V printed on it. This allows users to know which vehicle type classification their vehicle was determined to be and how the toll was calculated, in cases where the toll varies depending on the vehicle type.

[0120] Furthermore, the vehicle image acquisition unit is a surveillance camera 28, and the vehicle information D12 includes NP information read from the vehicle image captured by the surveillance camera 28. The printing unit 34 hides some of the characters in the NP information and prints it on the invoice D4.

[0121] In this way, the roadside device 1 can obtain NP information of non-ETC vehicles even in ETC lanes L where the NP reader 22 is not installed, by using the existing surveillance camera 28 at the toll booth. Furthermore, by obscuring some of the characters in the NP information, the roadside device 1 can issue an invoice D4 with vehicle information D12 printed on it, which is difficult for others to identify the vehicle, but which the user can recognize as their own vehicle's NP information. This prevents others from identifying the vehicle from the invoice D4 if the invoice D4 is dropped by the user and picked up by someone else. In addition, by making the user aware that evidence that can identify their vehicle is recorded, non-payment of tolls can be deterred.

[0122] Furthermore, the vehicle image acquisition unit is a surveillance camera 28, and the vehicle information D12 includes, in place of or in addition to the NP information, vehicle type information indicating the vehicle type classification of non-ETC vehicle V determined by the vehicle type identification device 29 or the surveillance officer, and towing information indicating whether or not it is towed. In addition, the vehicle information D12 includes one or more vehicle images captured by the surveillance camera 28.

[0123] In this way, the roadside device 1 can issue an invoice D4 with the vehicle type classification of the non-ETC vehicle V printed on it. This allows users to know which vehicle type classification their vehicle was determined to be and how the toll was calculated, in cases where the toll varies depending on the vehicle type classification. In addition, by including the vehicle image captured by the surveillance camera 28 in the vehicle information D12, users can visually confirm the vehicle specifications (such as the number of axles) and whether or not the vehicle is towed, which are used to determine the vehicle type classification of the non-ETC vehicle V.

[0124] Furthermore, the printing unit 34 prints on the invoice D4 URL information D46 for accessing a web page (viewing data D3) where at least one of the following pieces of information—traffic information D13, user information D11, vehicle information D12, and payment information D14—can be viewed.

[0125] In this way, the roadside device 1 reduces the amount of information printed on invoice D4 and allows users to view all the information on a web page.

[0126] Furthermore, the printing unit 34 prints the URL information D46 in the form of a two-dimensional code.

[0127] In this way, users can easily access web pages without having to manually enter the URL.

[0128] Furthermore, the post-collection system 100 includes a roadside device 1 and a monitoring device 4. The monitoring device 4 includes a print request unit 444 that requests the roadside device 1 to issue an invoice D4 containing at least one of the following information: traffic information D13 of a non-ETC vehicle V, user information D11, vehicle information D12, and payment information D14; and a post-collection data creation unit 445 that creates post-collection data D1 containing traffic information D13, user information D11, vehicle information D12, and payment information D14.

[0129] In this way, the post-payment collection system 100 can provide all information to the toll road operator using the post-payment collection data D1. Furthermore, by printing at least some of the information on the invoice D4, the system can provide users with an invoice D4 containing only the minimum necessary information, while also allowing them to recognize that user information, vehicle information, etc., are recorded as evidence.

[0130] Furthermore, the post-collection system 100 includes a server 5 in addition to the roadside device 1 and the monitoring device 4. The server 5 includes a storage 53 for recording the post-collection data D1 created by the monitoring device 4, and a viewing data creation unit 512 for creating viewing data D3, which is data for a web page that allows viewing of at least a portion of the post-collection data D1, with some of the information displayed on the web page hidden so that the user and vehicle cannot be identified by anyone other than the user.

[0131] In this way, the post-payment collection system 100 can provide all information to the toll road operator using post-payment collection data D1, while providing users with viewable data D3, which hides some of the information from post-payment collection data D1 that could identify users and vehicles. This allows the toll road operator to identify users and send reminders if there are delays in toll payment, thus enabling more reliable toll collection. Furthermore, even if someone other than the user views the viewable data D3, it is possible to suppress the identification of users and vehicles, thus protecting user privacy.

[0132] Furthermore, the post-collection data creation unit 445 of the monitoring device 4 creates post-collection data D1, which further includes recorded data of the conversation between the user and the monitoring officer. The viewing data creation unit 512 of the server 5 creates viewing data D3, which further includes the recorded data.

[0133] In this way, the post-payment system 100 can record the audio data as evidence that the user received an explanation from the supervisor about the post-payment (later payment) of the toll fee.

[0134] Furthermore, the vehicle information D12 in the post-collection data D1 includes NP information for non-ETC vehicles V. Server 5 further includes a traffic information creation unit 511 that retrieves NP information for non-ETC vehicles V from the all-vehicle information table D2, which stores NP information read by NP readers installed at toll booths and passage determination points on toll roads, creates traffic information D13 that can identify the toll booths and passage determination points that non-ETC vehicles V have passed through, and updates the post-collection data D1.

[0135] In this way, the post-collection system 100 can retrospectively add or correct information based on the all-vehicle information table D2 on the server 5, even if there are omissions or errors in the traffic information, for example, when a traffic monitor manually enters traffic information based on information gathered from users. Furthermore, the post-collection system 100 can identify the travel route of non-ETC vehicles V and collect the correct toll, even if the toll differs depending on the travel route (toll booths and checkpoints passed through).

[0136] Furthermore, the roadside device 1 is further equipped with a password acquisition unit 353 that acquires a password for viewing the viewing data D3. The viewing data creation unit 512 of the server 5 records the created viewing data D3, associating it with the password.

[0137] In this way, the post-payment collection system 100 can restrict users to accessing the viewing data D3 only when they correctly enter their PIN. This prevents, for example, someone who finds an invoice D4 that a user has dropped from accessing the viewing data D3 via the URL information D46 printed on the invoice D4.

[0138] Furthermore, the PIN acquisition unit 353 of the roadside device 1 acquires the PIN set by the user.

[0139] In this way, the post-payment collection system 100 makes it difficult for others to guess the PIN set by the user. As a result, it is possible to more reliably prevent others from viewing the viewing data D3.

[0140] Furthermore, the PIN acquisition unit 353 of the roadside device 1 acquires the automatically generated PIN.

[0141] In this way, the post-collection system 100 can reduce the effort and time required for users to set a PIN. The PIN acquisition unit 353 may set a predetermined PIN common to all users, or it may set a randomly generated PIN for each user. Even if the PIN generated by the PIN acquisition unit 353 is common to all users, it is possible to prevent it from being known to others who do not use post-collection by notifying only the user from the monitor or the display unit 39 of the roadside device 1 (printing device 3). Furthermore, by automatically acquiring information that only the user knows (such as the certificate number or part of the NP information) as the PIN, it is possible to make it difficult for others to guess the PIN.

[0142] <Other Embodiments> Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to that described above, and various design changes are possible. In other embodiments, the order of the above-described processes may be changed as appropriate. Also, some processes may be executed in parallel.

[0143] Furthermore, while the above-described embodiments have explained examples in which the vehicle image acquisition unit consists of an NP reader 22, a surveillance camera 28, or a combination of the NP reader 22 and the surveillance camera 28, the invention is not limited to these. In other embodiments, the vehicle image acquisition unit may include, in place of or in addition to the NP reader 22 or the surveillance camera 28, a laser sensor that measures the amount of reflected light from the vehicle body and the distance to the reflection position using laser light, or a 3D LiDAR. In this case, the vehicle image acquired by the vehicle image acquisition unit includes reflected light amount images and distance images obtained from the laser sensor or the like.

[0144] In yet another embodiment, the roadside device 1 (printing device 3) may include, in addition to the certificate scanning unit 32, an IC card reader that reads user information recorded on the IC chip of the official certificate using short-range wireless communication or the like. In this case, the data processing unit 351 of the roadside device 1 reads the information on the official certificate from the IC chip of the user's official certificate via the IC card reader.

[0145] <Note> The post-payment collection system and post-payment collection method described in the above-described embodiment can be understood, for example, as follows.

[0146] (1) According to the first embodiment, the post-collection system 100 is a post-collection system 100 that collects tolls for non-ETC vehicles V that cannot be automatically collected by ETC when they arrive at an ETC lane L at a toll booth on a toll road, and comprises a roadside device 1 installed in the ETC lane L, a monitoring device 4 operated by a monitor who remotely monitors the ETC lane L to create post-collection data D1 for non-ETC vehicles V, and a server 5 that stores the post-collection data D1. The roadside device 1 comprises a vehicle image acquisition unit 22, 28 that photographs a non-ETC vehicle V when it arrives at the ETC lane L, a certificate photographing unit 32 that photographs an official certificate held by a user riding in the non-ETC vehicle V, and a printing unit 34 that issues an invoice D4 for the tolls of the non-ETC vehicle V in accordance with the request of the monitoring device 4. The monitoring device 4 includes a user information acquisition unit 441 that acquires user information D11 read from a certificate image taken by a certificate imaging unit 32, a vehicle information acquisition unit 442 that acquires vehicle information D12 read from a vehicle image taken by vehicle image acquisition units 22, 28, a traffic information acquisition unit 443 that acquires traffic information that can identify the travel route of a non-ETC vehicle V on a toll road, a print request unit 444 that requests the roadside device 1 to issue an invoice D4 containing at least one of the following information: user information D11, vehicle information D12, traffic information D13, and payment information D14 regarding the payment of tolls, and a post-collection data creation unit 445 that creates post-collection data D1 containing user information D11, vehicle information D12, traffic information D13, and payment information D14. Server 5 includes a storage 53 that records the post-collection data D1 created by the monitoring device 4, and a viewing data creation unit 512 that creates viewing data D3 for a web page that allows viewing of at least a portion of the post-collection data D1, with some of the information displayed on the web page hidden so that the user and vehicle cannot be identified by anyone other than the user.

[0147] In this way, the post-payment collection system 100 can provide all information to the toll road operator using post-payment collection data D1, while providing users with viewable data D3, which hides some of the information from post-payment collection data D1 that could identify users and vehicles. This allows the toll road operator to identify users and send reminders if there are delays in toll payment, thus enabling more reliable toll collection. Furthermore, even if someone other than the user views the viewable data D3, it is possible to suppress the identification of users and vehicles, thus protecting user privacy.

[0148] (2) According to the second embodiment, in the post-collection system 100 according to the first embodiment, the post-collection data creation unit 445 of the monitoring device 4 creates post-collection data D1 which further includes recorded data D15 of the conversation between the user and the monitoring officer, and the viewing data creation unit 512 of the server 5 creates viewing data D3 which further includes recorded data D35.

[0149] In this way, the post-payment system 100 can record the audio data as evidence that the user received an explanation from the supervisor about the post-payment (later payment) of the toll fee.

[0150] (3) According to the third embodiment, in the post-collection system 100 according to the first embodiment, the vehicle information D12 includes the license plate information of non-ETC vehicles V, and the server 5 further includes a traffic information creation unit 511 that searches for the license plate information of non-ETC vehicles V from the total vehicle information table D2 which stores the license plate information read by license plate readers installed at toll booths and passage determination points on toll roads, creates traffic information D12 that can identify the toll booths and passage determination points that non-ETC vehicles V have passed through, and updates the post-collection data D1.

[0151] In this way, the post-collection system 100 can retrospectively add or correct information based on the all-vehicle information table D2 on the server 5, even if there are omissions or errors in the traffic information, for example, when a traffic monitor manually enters traffic information based on information gathered from users. Furthermore, the post-collection system 100 can identify the travel route of non-ETC vehicles V and collect the correct toll, even if the toll differs depending on the travel route (toll booths and checkpoints passed through).

[0152] (4) According to the fourth embodiment, in the post-collection system 100 according to the second embodiment, the vehicle information D12 includes the license plate information of non-ETC vehicles V, and the server 5 further includes a traffic information creation unit 511 that searches for the license plate information of non-ETC vehicles V from the total vehicle information table D2 which stores the license plate information read by license plate readers installed at toll booths and passage determination points on toll roads, creates traffic information D12 that can identify the toll booths and passage determination points that non-ETC vehicles V have passed through, and updates the post-collection data D1.

[0153] In this way, the post-collection system 100 can retrospectively add or correct information based on the all-vehicle information table D2 on the server 5, even if there are omissions or errors in the traffic information, for example, when a traffic monitor manually enters traffic information based on information gathered from users. Furthermore, the post-collection system 100 can identify the travel route of non-ETC vehicles V and collect the correct toll, even if the toll differs depending on the travel route (toll booths and checkpoints passed through).

[0154] (5) According to the fifth embodiment, in the post-collection system 100 relating to any one of the first to fourth embodiments, the roadside device 1 further comprises a password acquisition unit 353 that acquires a password for viewing the viewing data D3, and the viewing data creation unit 512 of the server 5 records the created viewing data D3 in association with the password.

[0155] In this way, the post-payment collection system 100 can restrict users to accessing the viewing data D3 only when they correctly enter their PIN. This prevents, for example, someone who finds an invoice D4 that a user has dropped from accessing the viewing data D3 via the URL information D46 printed on the invoice D4.

[0156] (6) According to the sixth aspect, in the post-collection system 100 according to the fifth aspect, the PIN acquisition unit 353 of the roadside device 1 acquires the PIN set by the user.

[0157] In this way, the post-payment collection system 100 makes it difficult for others to guess the PIN set by the user. As a result, it is possible to more reliably prevent others from viewing the viewing data D3.

[0158] (7) According to the seventh aspect, in the post-collection system 100 according to the fifth aspect, the PIN acquisition unit 353 of the roadside device 1 acquires the automatically generated PIN and displays the generated PIN on the display unit 39 of the roadside device 1 to notify the user.

[0159] In this way, the post-payment collection system 100 can reduce the effort and time required for users to set a PIN. The PIN acquisition unit 353 may set a predetermined PIN that is common to all users, or it may set a randomly generated PIN for each user. Even if the PIN generated by the PIN acquisition unit 353 is common to all users, it is possible to prevent it from being known to others who do not use post-payment collection by notifying only the user via the display unit 39 of the roadside device 1 (printing device 3).

[0160] (8) According to the eighth aspect, in the post-collection system 100 according to the fifth aspect, the PIN acquisition unit 353 of the roadside device 1 acquires a PIN that is automatically generated using one or more pieces of information contained in the user information D11, and notifies the user of which information was used to generate the PIN by printing it on the invoice D4.

[0161] In this way, the post-payment collection system 100 can reduce the time and effort required for users to set a PIN by automatically generating a PIN using information that only the user knows (such as the certificate number or part of the NP information). Furthermore, in this way, users who know their own user information D11 can easily find the correct PIN by looking at the invoice D4. On the other hand, it is made difficult for others who do not know the user information D1 to guess the PIN by looking at the invoice D4.

[0162] (9) According to the ninth aspect, the post-collection method is a post-collection method in which, when a non-ETC vehicle V that cannot be processed by ETC arrives at an ETC lane L at a toll booth on a toll road, the post-collection system 100 comprises a roadside device 1 installed in the ETC lane L, a monitoring device 4 operated by a remote monitor monitoring the ETC lane L to create post-collection data D1 for the non-ETC vehicle V, and a server 5 that stores the post-collection data D1, wherein the roadside device 1 performs the steps of photographing the non-ETC vehicle V when the non-ETC vehicle V that cannot be processed by ETC arrives at the ETC lane L, photographing the official identification document held by the user in the non-ETC vehicle V, and issuing an invoice D4 for the non-ETC vehicle V's toll in accordance with the request of the monitoring device 4 operated by a remote monitor monitoring the ETC lane L. The monitoring device 4 performs the following steps: acquire user information D11 read from a certificate image taken by the roadside device 1; acquire vehicle information D12 read from a vehicle image taken by the roadside device 1; acquire traffic information D13 that can identify the toll road travel route of a non-ETC vehicle V; request the roadside device 1 to issue an invoice D4 containing at least one of the following information: user information D11, vehicle information D12, traffic information D13, and payment information D14 regarding toll payment; and create post-collection data D1 containing user information D11, vehicle information D12, traffic information D13, and payment information D14. The server 5 performs the following steps: record the post-collection data D1 created by the monitoring device 4; and create viewing data D3 for a web page that allows viewing of at least a portion of the post-collection data D1, with some of the information displayed on the web page hidden so that the user and vehicle cannot be identified by anyone other than the user. [Explanation of Symbols]

[0163] 100 Toll collection system (post-payment system) 1 Roadside equipment 2 ETC equipment 21. Approaching Vehicle Detector 22. License plate reader (vehicle image acquisition unit) 23 Roadside antenna 24. Communication vehicle detector 25-lane server 26. Launch control unit 27 Exit vehicle detector 28 Surveillance camera (vehicle image acquisition unit) 3 Printing device 31 Lane-side telephone unit 32 Certificate Photography Section 33 Input section 34 Printing Department 35 processors 351 Data Processing Unit 352 Print Processing Unit 353 PIN Acquisition Section 36 memory 37 Storage 38 Communication I / F 4 Monitoring device 41 Office-side telephone department 42 Operation section 43 Display section 44 processors 441 User information acquisition department 442 Vehicle Information Acquisition Unit 443 Traffic information acquisition department 444 Print request section 445 Data Creation Department for Post-Collection 45 memory 4 wireless storage 47 Communication I / F 5 Servers 51 processors 511 Traffic Information Creation Department 512 Data Creation Section for Viewing 52 memory 53 Storage 54 Communication I / F D1 Data for post-collection D2 All Vehicle Information Table D3 Viewable Data D4 Invoice L ETC lane V Non-ETC vehicles X1 Entry detection position X2 Communication termination position X3 Exit detection location

Claims

1. A post-payment collection system for toll roads where, if a non-ETC vehicle that cannot be automatically processed by ETC enters an ETC lane, the toll for that non-ETC vehicle is collected retroactively. The roadside device installed in the aforementioned ETC lane, A monitoring device operated by a monitor who remotely monitors the ETC lane and creates data for post-collection of fees for non-ETC vehicles, A server for storing the aforementioned data for post-collection, Equipped with, The roadside device is, When a non-ETC vehicle, which cannot be processed for automatic toll collection by ETC, arrives in the ETC lane, a vehicle image acquisition unit takes a photograph of the non-ETC vehicle. A certificate scanning unit for scanning official identification documents held by users riding in the aforementioned non-ETC vehicle, A printing unit that issues an invoice for the toll fee of the non-ETC vehicle in accordance with the request of the monitoring device, Equipped with, The aforementioned monitoring device is A user information acquisition unit that acquires user information read from the certificate image captured by the aforementioned certificate imaging unit, A vehicle information acquisition unit acquires vehicle information read from a vehicle image captured by the aforementioned vehicle image acquisition unit, A traffic information acquisition unit that acquires traffic information that can identify the travel route of the non-ETC vehicle on the toll road, A printing request unit requests the roadside device to issue an invoice containing at least one of the following: user information, vehicle information, traffic information, and payment information relating to the payment of tolls. A post-collection data creation unit creates post-collection data including the user information, vehicle information, traffic information, and payment information, Equipped with, The aforementioned server, A storage device for recording the post-collection data created by the monitoring device, A data creation unit for creating viewable data for a web page that allows viewing of at least a portion of the aforementioned post-collection data, wherein at least a portion of the strings included in the user information and vehicle information displayed on the web page, and at least a portion of the images included in the user information and vehicle information are processed so that they cannot be seen, in order to prevent the user and the vehicle from being identified by anyone other than the user. Equipped with, A system for collecting fees after the fact.

2. The post-collection data creation unit of the monitoring device creates the post-collection data which further includes recorded data of the conversation between the user and the monitoring officer. The data creation unit for viewing the server creates the data for viewing the recording data, which further includes the recording data. The post-payment collection system according to claim 1.

3. The vehicle information includes the license plate information of the non-ETC vehicle, The server further includes a traffic information creation unit that retrieves license plate information of non-ETC vehicles from a total vehicle information table that stores license plate information read by license plate readers installed at toll booths and passage determination points on the toll road, creates traffic information that can identify the toll booths and passage determination points that the non-ETC vehicles passed through, and updates the post-collection data. The post-payment collection system according to claim 1.

4. The vehicle information includes the license plate information of the non-ETC vehicle, The server further includes a traffic information creation unit that retrieves license plate information of non-ETC vehicles from a total vehicle information table that stores license plate information read by license plate readers installed at toll booths and passage determination points on the toll road, creates traffic information that can identify the toll booths and passage determination points that the non-ETC vehicles passed through, and updates the post-collection data. The post-payment collection system according to claim 2.

5. The roadside device further includes a password acquisition unit that acquires a password for accessing the data for viewing, The data creation unit for viewing on the server records the created data for viewing, associating it with the password. A post-payment collection system according to any one of claims 1 to 4.

6. The PIN acquisition unit of the roadside device acquires the PIN set by the user. The post-collection system according to claim 5.

7. The PIN acquisition unit of the roadside device acquires the automatically generated PIN, and displays the generated PIN on the display unit of the roadside device to notify the user. The post-collection system according to claim 5.

8. The PIN acquisition unit of the roadside device acquires a PIN automatically generated using one or more pieces of information included in the user information, and notifies the user of which information was used to generate the PIN by printing it on the invoice. The post-collection system according to claim 5.

9. A post-payment collection method for collecting tolls from a non-ETC vehicle that cannot be automatically collected by ETC at a toll booth on a toll road, by a post-payment collection system comprising: a roadside device installed in the ETC lane; a monitoring device operated by a remote monitor who monitors the ETC lane from a remote location to create data for post-payment collection of the non-ETC vehicle; and a server that stores the data for post-payment collection. The aforementioned roadside device, When a non-ETC vehicle, which cannot be processed for automatic toll collection by ETC, arrives in the ETC lane, the process includes the step of taking a photograph of the non-ETC vehicle, The steps include taking a photograph of the official identification document held by the user riding in the aforementioned non-ETC vehicle, The steps include issuing an invoice for the toll for the non-ETC vehicle in accordance with the request of a monitoring device operated by a monitor who remotely monitors the ETC lane, Execute, The aforementioned monitoring device The steps include: obtaining user information read from a certificate image captured by the roadside device; The steps include: acquiring vehicle information from vehicle images taken by the roadside device; The steps include: obtaining traffic information that can identify the route traveled on the toll road by the non-ETC vehicle; A step of requesting the roadside device to issue an invoice containing at least one of the following: user information, vehicle information, traffic information, and payment information relating to the payment of tolls. A step of creating data for post-payment collection, including the user information, the vehicle information, the traffic information, and the payment information; Execute, The aforementioned server, The steps include recording the post-collection data created by the monitoring device, The steps include creating hidden viewing data for a web page that allows viewing of at least a portion of the aforementioned post-collection data, wherein at least a portion of the strings included in the user information and vehicle information displayed on the web page, and at least a portion of the images included in the user information and vehicle information are processed so that they cannot be seen, in order to prevent the user and the vehicle from being identified by anyone other than the user; Execute Method of collecting fees after the fact.

Images