JP7522015B2 - Parking lot server, parking fee settlement method, and program - Google Patents

Description

The present invention relates to a parking lot server, a parking fee settlement method, and a program.

For example, Patent Document 1 is an example of a conventional parking lot management system. The parking lot management system of Patent Document 1 includes a measurement unit that determines the entry time based on a signal of the vehicle's entry by a detection means and measures the parking time from the entry time, a reading means that reads the vehicle number from the vehicle image, a recording unit that correlates and records the vehicle number, the vehicle image, and the entry time, a panel unit that has an operation unit for input operations and a display unit that displays the vehicle number and the vehicle image, a settlement unit for settling the parking fee, a first control unit for settling based on the vehicle number, and a second control unit for settling based on the entry time. The first control unit displays multiple images based on the input vehicle number, and the second control unit displays multiple images based on the input entry time, thereby providing a judgment on whether the vehicle is the one being settled.

By using the above configuration, the initial capital investment and maintenance costs have been significantly reduced, resulting in a parking management system that is easy for users to use.

Patent No. 6588875

The parking management system in Patent Document 1 requires users to input their vehicle number in order to realize a ticketless parking service, and in order to reduce the burden on users, sometimes users are only required to input a four-digit designated number. However, users often do not remember their own vehicle number accurately, and there are cases where an incorrect vehicle number is input.

For example, if the correct serial number for a vehicle belonging to a certain user (hereinafter, User A) is "22-08", but User A mistakenly remembers it as "20-28 (hereinafter, the "-" will be omitted)", and User A enters the incorrect serial number "2028", if a vehicle belonging to a user (hereinafter, User B) with the serial number "2028" is parked during the same time period, User A will settle the parking fee that should be paid by User B.

Therefore, the present invention aims to provide a parking server that can reduce incorrect payments made by users.

The parking lot server of the present invention includes an entrance vehicle number receiving unit, a settlement request receiving unit, an exit vehicle number receiving unit, a parking fee determination unit, and a payment execution unit.

The entry vehicle number receiving unit receives the entry vehicle number, which is the vehicle number of a vehicle that has entered the parking lot, from the entry vehicle number reader. The settlement request receiving unit receives a parking fee settlement request including a partial vehicle number, which is a part of the vehicle number, and a payment method from the user's mobile terminal. The exit vehicle number receiving unit receives the exit vehicle number, which is the vehicle number of a vehicle that has exited the parking lot, from the exit vehicle number reader. The parking fee determination unit determines the parking fee based on the reception time of the entry vehicle number and the reception time of the corresponding exit vehicle number. If there is only one unsettled settlement request including the corresponding partial vehicle number by the reception time of the exit vehicle number that matches the partial vehicle number, the settlement execution unit executes the settlement according to the corresponding settlement request, and if there are multiple unsettled settlement requests including the corresponding partial vehicle number by the reception time of the exit vehicle number that matches the partial vehicle number, the settlement execution unit executes the settlement according to the settlement request with the latest time among the corresponding settlement requests.

The parking lot server of the present invention can reduce incorrect payment by users.

FIG. 1 is a block diagram showing the device configuration of a parking fee settlement system according to a first embodiment. FIG. 2 is a block diagram showing the functional configuration of the parking lot server according to the first embodiment. 11 is a flowchart showing an entrance vehicle number processing flow of the parking lot server of the first embodiment. 11 is a flowchart showing a settlement request processing flow of the parking lot server of the first embodiment. 13A and 13B are diagrams illustrating an incorrect payment request and a correct payment request where partial vehicle numbers match. 11 is a flowchart showing an exit car number processing flow of the parking lot server of the first embodiment. A diagram showing six patterns (P1 to P6) of the sequence of event occurrence and the processing results for two settlement requests with matching partial vehicle numbers. 11 is a flowchart showing a settlement request inspection process flow of the parking lot server of the first embodiment. 11 is a flowchart showing a settlement request deletion process flow of the parking lot server of the first embodiment. FIG. 2 is a diagram showing an example of the functional configuration of a computer.

The following describes in detail an embodiment of the present invention. Components having the same functions are given the same numbers, and duplicate explanations will be omitted.

The device configuration of the parking fee settlement system of the first embodiment will be described below with reference to FIG. 1. As shown in the figure, the parking fee settlement system 1 of the present embodiment includes a parking lot server 11, an entering vehicle number reader 12, a store terminal 13, a mobile terminal 14, an exiting vehicle number reader 15, and a payment server 16.

The functional configuration of the parking lot server 11 of this embodiment will be described below with reference to FIG. 2. As shown in the figure, the parking lot server 11 of this embodiment includes an entering vehicle number receiving unit 1105, an entering vehicle number memory unit 1110, a settlement request receiving unit 1115, a settlement request memory unit 1120, an exiting vehicle number receiving unit 1125, a parking fee determination unit 1130, a payment execution unit 1135, a settlement request inspection unit 1140, an error transmission unit 1145, a withdrawal request receiving unit 1150, and a settlement request deletion unit 1155. Note that the settlement request inspection unit 1140, the error transmission unit 1145, the withdrawal request receiving unit 1150, and the settlement request deletion unit 1155 are optional functional configurations.

Below, with reference to Figures 3 to 9, we will specifically explain the operation of each component of the parking lot server 11 in this embodiment, while clarifying the relationship with user behavior and the operation of other devices.

[User action: Enter parking lot]
A user enters a parking lot by car. An entrance vehicle number reader 12 is installed at the entrance of the parking lot, and the entrance vehicle number reader 12 reads the vehicle number of the user's vehicle.

[Entrance car number receiving unit 1105]
The entrance vehicle number receiving unit 1105 receives the entrance vehicle number, which is the vehicle number of the user who has entered the parking lot, from the entrance vehicle number reader 12 (S1105).

[Entry car number storage unit 1110]
The entrance car number storage unit 1110 stores the received entrance car number in association with the reception time (S1110).

[User Action: Settlement Request]
The user operates his/her mobile terminal 14 at any time to specify a partial vehicle number, which is a part of the vehicle number, and a payment method for the parking fee, for example, from an input form on a dedicated application. At this time, if there is discount information, the discount information can be specified.

Discount information is information that is sent from the store terminal 13 to the mobile terminal 14 when purchasing a product or service at a store. Discount information may, for example, indicate a discount amount for parking fees, or may indicate information about the time during which the parking lot can be used free of charge.

The user's mobile terminal 14 generates a payment request based on the specified partial vehicle number and payment method (and discount information), and sends the generated payment request to the parking lot server 11.

[Settlement request receiving unit 1115]
The payment request receiving unit 1115 receives a payment request for the parking fee, including a partial vehicle number, which is a part of the vehicle number, and a payment method, from the user's mobile terminal 14 (S1115).

The partial vehicle number may be, for example, a four-digit serial number. In the example of FIG. 5, the four-digit serial number "2028" is specified. In addition, the partial vehicle number may be, for example, the serial number plus a character (area name) indicating the inspection and registration office. An example of a serial number plus an area name is "Shinagawa 2028". In addition, the partial vehicle number may be the serial number plus one hiragana character (discriminating character) that distinguishes between private use and rental use. An example of a serial number plus a discriminating character is "sa 2028". In addition, the classification number + serial number = partial vehicle number may be used, or three or four of these elements (serial number, area name, discriminating character, classification number) may be combined to form the partial vehicle number.

The payment method may be, for example, a credit card number used for payment, specification of credit card information, or linking to an electronic money account.

As described above, the payment request may include discount information, which is information regarding discounts on parking fees, in addition to the partial vehicle number and payment method.

[Payment request storage unit 1120]
The settlement request storage unit 1120 stores the settlement request received from the user's mobile terminal 14 (S1120).

[User action: exiting parking lot]
The user exits the parking lot in his/her car. An exiting vehicle number reader 15 is installed at the entrance of the parking lot, and the exiting vehicle number reader 15 reads the vehicle number of the user's vehicle.

[Participating car number receiving unit 1125]
The exiting vehicle number receiving unit 1125 receives, from the exiting vehicle number reader 15, the exiting vehicle number, which is the vehicle number of the user's vehicle that has exited from the parking lot (S1125).

[Parking fee determination unit 1130]
The parking fee determination unit 1130 determines the parking fee based on the time of reception of the user's entry vehicle number and the time of reception of the corresponding user's exit vehicle number (S1130). As described above, the parking fee determination unit 1130 may determine the parking fee based on the time of reception of the user's entry vehicle number, the time of reception of the user's exit vehicle number, and discount information included in the user's payment request.

[Payment Execution Unit 1135]
If there is only one unsettled settlement request including the corresponding partial car number by the time of receiving the exit car number that matches the partial car number, the settlement execution unit 1135 executes the settlement according to the corresponding settlement request, and if there are multiple unsettled settlement requests including the corresponding partial car number by the time of receiving the exit car number that matches the partial car number, the settlement execution unit 1135 executes the settlement according to the settlement request with the latest time among the corresponding settlement requests (S1135). The operation of step S1135 will be explained below using a specific case as an example.

<Case: Multiple settlement requests generated for the same partial vehicle number due to user error>
For example, as shown in the example of Fig. 5, assume that the partial vehicle number (here, only the serial number is specified as the partial vehicle number) entered by user A is incorrect. A typical case is when the partial vehicle number (serial number) of user A's car is "2208", but user A misremembers and thinks that the partial vehicle number (serial number) of his/her car is "2028", and makes an incorrect payment request. In this case, as shown in the figure, consider the case where the partial vehicle number (serial number) of user B's car is "2028", and user B correctly enters the partial vehicle number (serial number) of his/her car and makes a correct payment request.

In this case, there will be multiple claims for the same partial vehicle number. As mentioned in step S1135, the timing for processing the settlement request is the time when the exiting vehicle number is received, so it is important to note that neither settlement request will be processed and will remain in limbo until the time when the exiting vehicle number is received. Here, six patterns P1 to P6 are assumed according to each user's settlement request and the order of exit from the parking lot, and are summarized in Figure 7. Below, the operation of the system in the six patterns P1 to P6 will be explained in detail.

<P1: A makes a payment request (incorrect) and enters the game, B makes a payment request (correct) and enters the game>
In this pattern, user A makes an incorrect payment request (for example, partial vehicle number "2028") and heads to the exit gate. The exiting vehicle number reader 15 reads the vehicle number of user A's vehicle (a vehicle number including the correct partial vehicle number "2208") and sends it to the parking lot server 11. The parking lot server 11 searches for a payment request corresponding to the partial vehicle number "2208", but since user A made an incorrect payment request, no corresponding payment request is found. Therefore, user A leaves the incorrect payment request in limbo, and attempts to exit the parking lot without paying his parking fee (*1 in FIG. 7).

For example, in the case of a gateless parking lot, user A will exit the parking lot without paying his/her parking fee. In this case, the parking lot server 11 can store the unpaid parking fee in association with the corresponding vehicle number (the complete vehicle number read by the exiting vehicle number reader 15) and charge the previous parking fee the next time user A uses the parking lot.

In the case of a gated parking lot, if a matching payment request is not found, an error may be processed, the gate may not be opened, and an attendant may respond to User A individually.

Meanwhile, user B makes a correct settlement request (for example, partial vehicle number "2028") and heads to the exit. The exit vehicle number reader 15 reads the vehicle number of user B's car (a vehicle number including the correct partial vehicle number "2028") and sends it to the parking lot server 11. The parking lot server 11 searches for settlement requests corresponding to the partial vehicle number "2028", which is part of the vehicle number that it read, and finds two settlement requests: user A's settlement request (incorrect) and user B's settlement request (correct). In this case, the settlement execution unit 1135 of the parking lot server 11 executes the settlement according to the most recent settlement request of the two applicable settlement requests, i.e., user B's settlement request.

Therefore, the new request, the settlement request of user B, is treated as correct (*2 in the figure), and the settlement request of user B is processed and the payment of user B is completed normally (*3 in the figure). Therefore, the payment of user B in this case is correct.

<P2: A requests settlement (incorrect), B requests settlement (correct), A participates, B participates>
In this case, User A leaves the erroneous payment request in limbo, and then attempts to exit the parking lot without paying his/her own parking fee (*1), and User B's new payment request is treated as correct (*2), User B's payment request is processed, and User B's payment is normally completed (*3). This is the same as P1.

<P3: A requests settlement (incorrect), B requests settlement (correct), B participates, A participates>
In this case, User A leaves the erroneous payment request in limbo, and then attempts to exit the parking lot without paying his/her parking fee (*1), and User B's new payment request is treated as correct (*2), User B's payment request is processed, and User B's payment is normally completed (*3). This is the same as P1 and P2.

<P4: B requests settlement (correct), A requests settlement (incorrect), A participates, B participates>
In this case, User A leaves the erroneous payment request in limbo, and then attempts to exit the parking lot without paying his/her own parking fee (*1), and the new payment request from User A is treated as correct (*4), and when User B exits, User A's payment request is processed and User A's payment is completed (*5). The situation in *5 indicates an error in which User A pays for User B's parking fee instead of User B.

The error in *1 is a minor error compared to the error in *5, assuming that the parking fee can be recharged when user A re-enters the parking lot, and that the parking fee is not strictly collected in the first place. On the other hand, it is desirable to prevent the error in *5 as much as possible. One of the causes of the error in *5 is that the time between the settlement request and the exit is too long. In the case of P4, the time between user B's settlement request (correct) and the exit of the parking lot was too long, and during this time user A's settlement request (incorrect) was made, which caused the error in *5. Therefore, if the time between the settlement request and the corresponding vehicle's exit can be controlled to be shorter, this type of error is expected to decrease. For example, it is possible to reduce the error in *5 by sending a time-exceeded error (described later) to the mobile terminal 14 corresponding to the settlement request for which a certain time has passed since it was received, among the settlement requests for which settlement has not been executed, and invalidating the settlement request.

<P5: B requests settlement (correct), A requests settlement (incorrect), B participates, A participates>
In this case, User A leaves the erroneous payment request in limbo, and then tries to exit the parking lot without paying his/her parking fee (*1), and the new payment request from User A is treated as correct (*4), and when User B exits, User A's payment request is processed and User A's payment is completed (*5). This is the same as P4. By sending a time-exceeded error (described later) and invalidating the payment request, it is possible to reduce the error in *5.

<P6: B makes a payment request (correct) and participates, A makes a payment request (incorrect)>
In this case, since there is only one unsettled settlement request including the partial vehicle number of user B (only the correct settlement request by user B), the settlement request of user B is processed and the settlement of user B is completed normally (*3). After that, user A makes an incorrect settlement request (partial vehicle number 2028), but since the car of user B corresponding to partial vehicle number 2028 has already left the lot, the settlement request of user A is rejected as there is no corresponding vehicle number (*6).

[Settlement Request Inspection Unit 1140 (optional)]
The settlement request inspection unit 1140 inspects for the following three errors (duplication error, incorrect input error, and time-exceeded error) (S1140).

<Check for duplicate errors>
The payment request inspection unit 1140 checks whether there are multiple unpaid entry vehicle numbers that match the partial vehicle number included in the payment request. This error is notified when there is a partial vehicle number overlap between cars in the parking lot, and is unrelated to the error caused by the user error described above.

<Check for input errors>
The settlement request inspection unit 1140 inspects whether the partial vehicle number included in the settlement request for which settlement has not been executed matches any of the partial vehicle numbers included in other settlement requests for which settlement has not been executed. If a duplication error and an input error occur simultaneously, the duplication error takes precedence.

<Checking for time-exceeded errors>
The settlement request checking unit 1140 checks whether or not there is any settlement request for which a predetermined time has passed since it was received, among the settlement requests for which settlement has not yet been executed.

[Error sending unit 1145 (optional)]
The error transmission unit 1145 transmits the above three errors (duplication error, incorrect input error, and time-exceeded error) to the corresponding mobile terminal 14 (S1145).

<Send duplicate error>
When there are multiple unsettled entry car numbers that match the partial car number included in the settlement request, the error sending unit 1145 sends a duplication error to the mobile terminal 14 that sent the most recent settlement request among the relevant settlement requests. The content of the duplication error that is sent can be a notification of a temporary change in the definition of the partial car number. For example, when only the sequential designation number is defined as the partial car number as the initial setting, a notification can be sent to encourage re-entering the partial car number that has been redefined by adding the area name to the sequential designation number because a duplication has occurred.

<Send due to incorrect input error>
When the partial vehicle number included in the unsettled settlement request matches any of the partial vehicle numbers included in other unsettled settlement requests, the error sending unit 1145 sends an erroneous input error to all mobile terminals 14 that sent the corresponding settlement request. The settlement request inspection unit 1140 frequently checks for erroneous input errors and sends the erroneous input error in a short time, which increases the possibility of notifying the user who made the erroneous input while they are still in the parking lot.

For example, the situation indicated by the star in Figure 7 indicates a situation in which both the settlement request by user A and the settlement request by user B are pending and user A has not yet entered the race, making it highly likely that the incorrect input error can be notified before user A enters the race. In this case, an incorrect input error is sent to both user A and user B. The content of the incorrect input error that is sent could include a notification that an incorrect input may have occurred, or a notification encouraging the user to withdraw the settlement request and re-enter the partial car number to generate a new settlement request.

<Send time exceeded error>
The error sending unit 1145 sends a time-exceeded error to the mobile terminal 14 that sent a settlement request for which a predetermined time has passed since it was received, among the settlement requests for which settlement has not been executed. The content of the time-exceeded error to be sent may be a notification indicating that the settlement request has become invalid due to the time-exceeded period, a notification urging the user to execute the settlement request again, etc.

[User action: Withdraw settlement request]
When the user realizes that his/her payment request is incorrect (typically, the user realizes this error by receiving a notification of an incorrect input error), the user may withdraw the payment request. In this case, a withdrawal request is generated on the mobile terminal 14 based on the user's input, and the generated withdrawal request is transmitted to the parking lot server 11.

[Withdrawal Request Receiving Unit 1150 (Optional)]
The withdrawal request receiving unit 1150 receives a withdrawal request for the settlement request from the user's mobile terminal 14 (S1150).

[Settlement request deletion unit 1155 (optional)]
The settlement request deletion unit 1155 deletes the corresponding settlement request based on the received withdrawal request (S1155).

<Additional Notes>
The device of the present invention has, as a single hardware entity, an input section to which a keyboard or the like can be connected, an output section to which a liquid crystal display or the like can be connected, a communication section to which a communication device (for example, a communication cable) capable of communicating with the outside of the hardware entity can be connected, a CPU (which may also have a central processing unit, cache memory, registers, etc.), memories such as RAM and ROM, an external storage device such as a hard disk, and a bus connecting the input section, output section, communication section, CPU, RAM, ROM, and external storage device so that data can be exchanged between them. If necessary, the hardware entity may also be provided with a device (drive) capable of reading and writing recording media such as a CD-ROM. A physical entity equipped with such hardware resources is, for example, a general-purpose computer.

The external storage device of the hardware entity stores the programs required to realize the above-mentioned functions and the data required in the processing of these programs (not limited to the external storage device, for example the programs may be stored in a ROM, which is a read-only storage device). In addition, the data obtained by the processing of these programs is appropriately stored in the RAM, the external storage device, etc.

In a hardware entity, each program stored in an external storage device (or ROM, etc.) and the data required to process each program are loaded into memory as needed, and interpreted, executed, and processed by the CPU as appropriate. As a result, the CPU realizes a specified function (each of the components represented as the above, ... unit, ... means, etc.).

The present invention is not limited to the above-described embodiment, and can be modified as appropriate without departing from the spirit of the present invention. Furthermore, the processes described in the above-described embodiment are not limited to being executed chronologically in the order described, but may be executed in parallel or individually depending on the processing capacity of the device executing the processes or as necessary.

As mentioned above, when the processing functions of the hardware entities (the devices of the present invention) described in the above embodiments are realized by a computer, the processing contents of the functions that the hardware entities should have are described by a program. Then, by executing this program on a computer, the processing functions of the hardware entities are realized on the computer.

The various processes described above can be implemented by loading a program that executes each step of the above method into the recording unit 10020 of the computer shown in FIG. 10 and operating the control unit 10010, input unit 10030, output unit 10040, etc.

The program describing the processing contents can be recorded on a computer-readable recording medium. Examples of computer-readable recording media include magnetic recording devices, optical disks, magneto-optical recording media, and semiconductor memories. Specifically, for example, hard disk drives, flexible disks, magnetic tapes, etc. can be used as magnetic recording devices; DVDs (Digital Versatile Discs), DVD-RAMs (Random Access Memory), CD-ROMs (Compact Disc Read Only Memory), and CD-Rs (Recordable)/RWs (ReWritable) can be used as optical disks; MOs (Magneto-Optical discs) can be used as magneto-optical recording media; and EEP-ROMs (Electrically Erasable and Programmable-Read Only Memory) can be used as semiconductor memories.

The program may be distributed, for example, by selling, transferring, or lending portable recording media such as DVDs or CD-ROMs on which the program is recorded. Furthermore, the program may be stored in a storage device of a server computer, and the program may be distributed by transferring the program from the server computer to other computers via a network.

A computer that executes such a program, for example, first stores the program recorded on a portable recording medium or the program transferred from a server computer in its own storage device. Then, when executing a process, the computer reads the program stored on its own recording medium and executes the process according to the read program. As another execution form of this program, the computer may read the program directly from the portable recording medium and execute the process according to the program, or may execute the process according to the received program each time a program is transferred from the server computer to this computer. In addition, the server computer may not transfer the program to this computer, but may execute the above-mentioned process by a so-called ASP (Application Service Provider) type service that realizes the processing function only by issuing an execution instruction and obtaining the results. Note that the program in this form includes information used for processing by an electronic computer that is equivalent to a program (such as data that is not a direct command to the computer but has properties that specify the processing of the computer).

In addition, in this embodiment, a hardware entity is configured by executing a specific program on a computer, but at least a portion of the processing content may be realized by hardware.

Claims (13)

an entrance vehicle number receiving unit that receives an entrance vehicle number, which is the vehicle number of a vehicle that has entered the parking lot, from the entrance vehicle number reader;
a payment request receiving unit that receives a payment request for a parking fee including a partial vehicle number that is a part of the vehicle number and a payment method from a user's mobile terminal;
an exit car number receiving unit that receives an exit car number, which is the car number of a vehicle that has exited from a parking lot, from the exit car number reader;
a parking fee determination unit that determines a parking fee based on the reception time of the entry car number and the reception time of the corresponding exit car number;
A parking lot server including a payment execution unit which, if there is only one unsettled settlement request including the corresponding partial vehicle number by the time of receiving the exiting vehicle number that matches the partial vehicle number, executes payment in accordance with the corresponding settlement request, and, if there are multiple unsettled settlement requests including the corresponding partial vehicle number by the time of receiving the exiting vehicle number that matches the partial vehicle number, executes payment in accordance with the settlement request with the latest time among the corresponding settlement requests. 2. The parking lot server according to claim 1,
A settlement request inspection unit that inspects whether or not there are a plurality of entrance vehicle numbers that match the partial vehicle number included in the settlement request among the entrance vehicle numbers for which settlement has not been executed;
The parking lot server includes an error sending unit that, when there are multiple unpaid entering vehicle numbers that match the partial vehicle number included in the settlement request, sends a duplication error to the mobile terminal that sent the most recent settlement request among the corresponding entering vehicle numbers. 3. The parking lot server according to claim 2,
The settlement request inspection unit
Check whether the partial vehicle number included in the settlement request for which settlement has not been performed matches any of the partial vehicle numbers included in other settlement requests for which settlement has not been performed;
The error transmission unit is
A parking lot server that, when the partial vehicle number included in the settlement request for which payment has not yet been made matches any of the partial vehicle numbers included in other settlement requests for which payment has not yet been made, sends an incorrect input error to all of the mobile terminals that sent the corresponding settlement request. 4. The parking lot server according to claim 3,
The duplicate error may include:
Contains notification of temporary changes to the definition of partial vehicle numbers,
The above-mentioned input errors include:
The parking server includes a notification to prompt the user to re-enter the partial vehicle number. The parking lot server according to claim 3 or 4,
The settlement request inspection unit
Checking whether there is a settlement request for which a predetermined time has elapsed since it was received, among the settlement requests for which settlement has not yet been executed;
The error transmission unit is
The parking lot server transmits a time-exceeded error to the mobile terminal that transmitted the settlement request for which a predetermined time has elapsed since receipt, among the settlement requests for which settlement has not yet been executed. 6. The parking lot server according to claim 1,
The settlement request is
In addition to the partial vehicle number and the payment method, discount information is information regarding a discount on the parking fee,
The parking fee determination unit
a parking lot server that determines the parking fee based on the reception time of the entering car number, the reception time of the exiting car number corresponding to the entering car number, and the discount information. an entrance vehicle number receiving step of receiving an entrance vehicle number, which is the vehicle number of a vehicle that has entered the parking lot, from an entrance vehicle number reader;
A payment request receiving step of receiving a payment request for a parking fee including a partial vehicle number that is a part of the vehicle number and a payment method from a mobile terminal of a user;
an exit vehicle number receiving step of receiving an exit vehicle number, which is the vehicle number of a vehicle that has exited from a parking lot, from an exit vehicle number reader;
a parking fee determination step for determining a parking fee based on the reception time of the entry car number and the reception time of the corresponding exit car number;
The parking fee settlement method includes a payment execution step of, if there is only one unsettled settlement request including the corresponding partial vehicle number by the time of receiving the exiting vehicle number that matches the partial vehicle number, executing payment according to the corresponding settlement request, and, if there are multiple unsettled settlement requests including the corresponding partial vehicle number by the time of receiving the exiting vehicle number that matches the partial vehicle number, executing payment according to the settlement request with the latest time among the corresponding settlement requests. The parking fee settlement method according to claim 7,
a payment request checking step of checking whether or not there are a plurality of entry vehicle numbers that match the partial vehicle number included in the payment request among the entry vehicle numbers for which payment has not been executed;
A parking fee settlement method including an error sending step of sending a duplication error to the mobile terminal that sent the most recent settlement request among the corresponding unpaid entry vehicle numbers when there are multiple entry vehicle numbers that match the partial vehicle number included in the settlement request. The parking fee settlement method according to claim 8,
The settlement request checking step includes:
Check whether the partial vehicle number included in the settlement request for which settlement has not been performed matches any of the partial vehicle numbers included in other settlement requests for which settlement has not been performed;
The error transmission step includes:
A parking fee settlement method in which, when the partial vehicle number included in the settlement request for which payment has not been made matches any of the partial vehicle numbers included in other settlement requests for which payment has not been made, an incorrect input error is sent to all of the mobile terminals that sent the corresponding settlement requests. The parking fee settlement method according to claim 9,
The duplicate error may include:
Contains notification of temporary changes to the definition of partial vehicle numbers,
The above-mentioned input errors include:
A parking payment method that includes a notification to re-enter the partial vehicle number. The parking fee settlement method according to claim 9 or 10,
The settlement request checking step includes:
Checking whether there is a settlement request for which a predetermined time has elapsed since it was received, among the settlement requests for which settlement has not yet been executed;
The error transmission step includes:
The parking fee settlement method includes transmitting a time-exceeded error to the mobile terminal that transmitted the settlement request for which a predetermined time has elapsed since receipt, among the settlement requests for which settlement has not yet been executed. A parking fee settlement method according to any one of claims 7 to 11, comprising:
The settlement request is
In addition to the partial vehicle number and the payment method, discount information is information regarding a discount on the parking fee,
The parking fee determination step includes:
and determining the parking fee based on the reception time of the entrance car number, the reception time of the exit car number corresponding to the entrance car number, and the discount information. A program that causes a computer to function as a parking lot server according to any one of claims 1 to 6.

Images