Parking management server and computer program
The parking management server and computer programs automate parking fee reimbursement and reward point distribution based on user purchases, addressing inefficiencies in existing systems and enhancing user convenience and store management.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- PAAKU NIJUYON
- Filing Date
- 2024-10-29
- Publication Date
- 2026-05-15
AI Technical Summary
Existing parking fee reimbursement systems at partner stores are inconvenient and inefficient, especially when using a pre-payment method, as they require manual collection of receipts and do not account for varying store-specific rewards or congestion levels.
A parking management server and associated computer programs that facilitate the exchange of data between entry gates, partner stores, and user terminals to calculate and transmit reward points or rebates directly to users, based on their purchases, and optionally provide congestion information.
Enables convenient and efficient parking fee reimbursement at partner stores, even with pre-payment methods, by automating the reward calculation and distribution process, enhancing user satisfaction and store management.
Smart Images
Figure 2026078684000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to information and communication technology for enhancing the convenience of parking lots and facilities around parking lots for both users and operators.
Background Art
[0002] The parking services provided by parking lots are roughly classified into time-based rental, where the vehicle interior is rented out on a monthly lease basis, and hourly rental, where the vehicle interior is rented out on an hourly basis. The present invention relates to the latter hourly rental parking lot.
[0003] Hourly rental parking lots are divided into a "post-payment method (settlement at the time of departure)" in which the user of the vehicle interior pays the fee according to the usage time of the vehicle interior later, and a "pre-payment method (settlement at the time of entry)" in which the user of the vehicle interior pays a fixed fee for each vehicle interior used in advance (see Fig. 1).
[0004] In the "post-payment method (settlement at the time of departure)", typically, the settlement amount is determined on a per-unit-of-use basis according to the usage time of the vehicle interior, so users have a high sense of acceptance. However, equipment for measuring the usage time and equipment for requesting the user to pay the amount corresponding to the measuring equipment and performing the settlement are required, so the facility burden on the parking lot operator side is large.
[0005] On the other hand, the "pre-payment method (settlement at the time of entry)" requires a flat fee from the user, so equipment for measuring the usage time is not necessary, and the equipment for requesting the user to pay the fee and performing the settlement also becomes simple. Therefore, the facility burden on the parking lot operator side is reduced. However, it has the drawback that it is difficult for users to feel a sense of acceptance.
[0006] It is also common to visit a commercial facility adjacent to a parking lot by private car and use the parking lot during the time when the commercial facility is being used. Therefore, it is often the case that the commercial facility provides a service to the parking lot user, such as partially or fully bearing the parking lot usage fee. This service and the parking fee settlement method are more user-friendly in the post-payment method than in the pre-payment method.
[0007] Patent Document 1 discloses a parking fee payment method that can improve the convenience of applying discounts or reductions to parking fees when processing payment of parking fees for vehicles entering a parking lot using ETC.
[0008] Patent Document 2 discloses a parking management technology that makes it easy to reflect discount information corresponding to payment settlement at stores in the settlement of parking fees, and that enables smooth entry and exit from the parking lot. [Prior art documents] [Patent Documents]
[0009] [Patent Document 1] Patent No. 7433139 [Patent Document 2] Patent No. 6952829 [Overview of the project] [Problems that the invention aims to solve]
[0010] A complementary business relationship often exists between a parking lot and the shops surrounding it. This complementary relationship means that, for the parking lot, the presence of many shops nearby increases the number of customers who use the parking lot when visiting those shops, while for the shops, the existence and use of the parking lot makes it more convenient for customers to visit. Therefore, shops surrounding a parking lot often enter into contracts with the parking lot in advance, becoming partner shops, and providing services such as covering part or all of the parking fees that users would otherwise pay if they generate sales from the parking lot users.
[0011] Specifically, when customers at partner stores pay for goods or services, the system will write data indicating that the parking fee has been paid onto the parking ticket that proves the use of the parking lot. Alternatively, it will provide the customer with a ticket that can be used as payment at the payment machine installed at the exit gate. If parking tickets are in electronic form, the procedure involves a terminal at the partner store transmitting data to the electronic parking ticket installed on the user's smartphone, indicating that the store will cover part or all of the parking fee.
[0012] As mentioned above, the payment method upon exit is suitable for operating a parking fee reimbursement service at partner stores. In other words, it is difficult to adopt an payment method upon entry if the parking fee reimbursement service at partner stores is assumed. For example, Patent Document 1 discloses an embodiment employing a pre-payment method, but the parking fee reimbursement service at partner stores is not considered.
[0013] Furthermore, if there are multiple partner stores, parking users may make small purchases at several of these stores. In such cases, the amount spent at a single partner store may not be enough to cover the parking fee. For example, if the parking fee is 550 yen, but the amount spent at the partner store is also 550 yen, it is impossible to cover the parking fee.
[0014] To address this situation, it is common practice for parking users to collect shopping receipts from each store, have the total amount paid at the last participating store they visited combine, and then have the parking fee covered. Naturally, this is inconvenient for both parking users and participating stores. However, Patent Document 2 does not disclose any means to resolve the inconvenience of this situation.
[0015] On the other hand, partner stores offer services to customers who intend to return, regardless of whether they use the parking lot. Specifically, these services include store-specific point reward programs and the issuance of stamp cards (including electronic ones). Partner stores also have a latent need to separate these store-specific services from the parking fee reimbursement service for parking users only. This is because the products and services offered differ from store to store, so a uniform policy such as "free parking for sales of 3,000 yen or more excluding tax" is not rational for stores with low profit margins and those with higher profit margins. Furthermore, it's likely that parking users would find it more satisfying if the store's own points earned through shopping were separated from the burden of parking fees.
[0016] The problem that this invention aims to solve is to provide information processing technology that enables the provision of a parking fee reimbursement service at partner stores, even when a payment system is adopted at the time of entry. [Means for solving the problem]
[0017] To address the aforementioned challenges, we developed a parking management server capable of receiving and transmitting various data from the entry gates that support payment upon entry, as well as various data with partner stores, and a dedicated application program for use by parking users on their mobile devices.
[0018] (First invention) The first invention relates to a parking management server for managing parking lots that use an entry-based payment system. In other words, a means for receiving parking information receives parking information from an entrance gate installed at the entrance of the parking lot, which is obtained by linking user identification data pertaining to the paid data indicating that the parking lot user has completed payment upon entry, with the payment data indicating that the parking lot user has completed payment upon entry. A parking management database that stores management data for the aforementioned parking lot and also stores the aforementioned parking entry information, It is equipped with (see Figure 2), When the parking lot user makes a payment at the affiliated store of the parking lot, store payment information reception means for receiving, from the store terminal related to the affiliated store, store payment information in which the user identification data is associated with the amount data that is the payment amount and the store identification data for identifying the affiliated store; A store management database that accumulates management data related to the affiliated store and accumulates the store payment information; Reduction point calculation means for calculating a reduction amount to be returned to the parking lot user based on the store payment information; Reduction point data transmission means for transmitting reduction point data corresponding to the reduction amount calculated by the reduction point calculation means to a communication terminal (user terminal) related to the parking lot user; It is provided with (refer to Fig. 4).
[0019] (Term Explanation) The "parking lot management server" is a computer. Therefore, it is provided with a data receiving device as a data input device, a random access memory, a data storage device, an arithmetic device (CPU), a data transmitting device as a data output device, and the like.
[0020] The "affiliated store of the parking lot" is a store or commercial facility close to the parking lot. When a passenger car or a passenger vehicle parking at the parking lot contributes to the sales of the store or the commercial facility, a contract to the effect of prior affiliation is concluded. That contract is a contract to provide a service that bears part or all of the parking fee for the parking lot user according to the sales and profits of the store or the commercial facility. Note that the above-mentioned "affiliation" means that the operation of the parking lot and the store are separate operations, and the amount paid by the parking lot user to the parking lot may be exchanged in some form between the operation entity of the parking lot and the operation entity of the store. Alternatively, the operation of the parking lot and the store may be an operation based on the same entity or a relationship such as affiliated companies with a capital relationship.
[0021] "User identification data" refers to data for identifying a parking lot user. The vehicle number of the vehicle attempting to enter is typical. When the parking lot user has already completed membership registration with the parking lot management server, a member ID recognizable by the parking lot management server may also be used.
[0022] "Store identification data" refers to information for identifying a store when a parking lot user gets out of the vehicle parked in the parking lot and visits a neighboring store.
[0023] "Amount data" refers to information regarding the amount spent by a parking lot user as the consideration for using the parking lot. The form of payment is not limited. It may be cash, credit card, debit card, electronic money, or any other form.
[0024] "Store payment information" refers to information regarding the amount paid by a parking lot user at a partnered store. Payment, similar to the above amount data, is not limited in its form. Also, types of payment include the price of shopping, consideration for receiving services, various public charges, and other payment surrogates, regardless of the purpose of the payment.
[0025] "Rebate point data" refers to electronic data equivalent to the "rebate amount" calculated by the rebate point calculation means and usable for economic transactions. When the calculated rebate amount is equal to or more than the settlement amount at the time of entry, it may be data indicating cancellation of the settlement at the time of entry. When the calculated rebate amount does not reach the settlement amount at the time of entry, it may be data indicating that, after canceling the settlement amount at the time of entry, the amount was recharged to a new amount obtained by subtracting the rebate amount from the settlement amount.
[0026] (Function) When the settlement at the time of entry by the parking lot user is completed, the entry information receiving means of the parking lot management server receives entry information indicating that the settlement at the time of entry has been completed from the entry gate. This entry information includes user identification data and the paid data related to the above settlement at the time of entry, and is stored in the parking lot management database.
[0027] Suppose a parking lot user makes a purchase or payment for a service at a partner store of the parking lot. The store payment information receiving means receives store payment information related to that payment from the store terminal of the partner store. This store payment information includes the user identification data, store identification data to identify the store, and data on the amount paid by the parking lot user. The store management database of the parking lot management server stores management data related to partner stores, and also stores store payment information.
[0028] Then, based on the store payment information, the reward point calculation means calculates the amount of reward to be given to the parking user, and the reward point data transmission means transmits the reward point data corresponding to the calculated amount to the communication terminal (user terminal) related to the parking user.
[0029] Parking users can get some or all of their prepaid parking fees back by paying at participating stores. For partner stores, this service allows them to cover the parking fees prepaid by parking users, contributing to attracting more customers and securing repeat business.
[0030] (Second invention) The second invention also relates to a parking management server for managing parking lots that use an entry-based payment system. In other words, a means for receiving parking information receives parking information from an entrance gate installed at the entrance of the parking lot, which is obtained by linking user identification data pertaining to the paid data indicating that the parking lot user has completed payment upon entry, with the payment data indicating that the parking lot user has completed payment upon entry. A parking management database that stores management data for the aforementioned parking lot and also stores the aforementioned parking entry information, It is equipped with (see Figure 2), When a parking user makes a payment at a partner store of the aforementioned parking lot, the store payment information receiving means receives from the store terminal of the partner store as store payment information, which links the amount data of the payment and the user identification data to store identification data for identifying the partner store. A store management database that stores management data related to the aforementioned partner stores and store payment information, A reward point calculation means that calculates the amount of reward to be returned to the parking user based on the aforementioned store payment information, A reward point data transmission means transmits reward point data corresponding to the reward amount calculated by the aforementioned reward point calculation means to the aforementioned store terminal, It is equipped with (see Figures 6 and 7).
[0031] The difference between the first and second inventions lies in the destination to which the reward point data transmission means transmits the reward point data. In the first invention, the reward point data is transmitted to a communication terminal related to the parking lot user, while in the second invention, the reward point data is transmitted to a store terminal (see Figures 4 and 6).
[0032] The store terminal that receives the reward points data may either transmit the reward points data to the communication terminal related to the parking user (see Figure 6) or provide a cashback to the parking user (Figure 7).
[0033] (Variation 1 of the first and second inventions) The first and second inventions may be configured as follows: In other words, the aforementioned store management database stores data on the percentage of reward points awarded for the amount data at each affiliated store. The aforementioned reward point calculation means calculates the reward point data using the aforementioned reward rate data as well (see Figure 8).
[0034] (Explanation of terms) "Rebate rate data" refers to a percentage, such as 10% or 5% of the sales amount excluding tax. This rebate rate data can be determined for each partner store or standardized across all partner stores. Furthermore, allowing for variations based on the day of the week, date, or time of day contributes to the flexibility and diversity of services offered at partner stores.
[0035] (action) Partner stores can determine the reward rate data, which contributes to rational business management from the perspective of the partner stores.
[0036] (Variation 2 of the first and second inventions) The first and second inventions may be configured as follows: In other words, a store congestion determination means that determines the level of congestion at a partner store (A) using store payment information stored in the aforementioned store management database, A congestion data transmission means transmits the store congestion data, which is the result of the store congestion determination means, to a communication terminal related to a parking user (Z) other than the aforementioned parking user (Y), It will be equipped with the following (see Figure 11).
[0037] (Explanation of terms) The "congestion determination" algorithm in the "store congestion determination means" determines that a store is congested if, for example, the time interval between the payment data stored in the store management database is shorter than the time interval immediately preceding it. Alternatively, the system may analyze past data stored in the store management database to derive empirical rules and determine whether or not a store is congested. If a store is not determined to be crowded, the store congestion data may not be sent, or information may be sent indicating that the store is not currently crowded.
[0038] (action) Using store payment information stored in the store management database, the store congestion determination means determines the level of congestion at the partner store. The congestion data transmission means transmits the resulting store congestion data to a communication terminal belonging to a parking user (Z) who is different from the parking user (Y) related to the aforementioned store payment information.
[0039] Mobile devices of parking users (e.g., Z) other than parking user (Y) who has already paid at partner store (A) can receive information that "Store A is currently crowded." For user (Z), this information can help them decide whether or not to go to store (A), and if so, when to go. Mobile devices of parking user (Y) are excluded from receiving store congestion data because it is not particularly necessary (unnecessary) information for parking user (Y) who has already finished their shopping.
[0040] (Third invention) The third invention relates to a computer program for controlling the parking management server according to the first invention. In other words, the procedure for receiving parking information involves receiving parking information from an entrance gate installed at the entrance of the parking lot, which is obtained by linking user identification data related to the parking lot user with payment data indicating that the parking lot user has completed payment upon entry, A procedure for accumulating parking information, which involves accumulating management data for the aforementioned parking lot and accumulating the aforementioned parking information in a parking lot management database, When a parking user makes a payment at a partner store of the aforementioned parking lot, the store payment information receiving procedure receives the amount data of the payment, the store identification data for identifying the partner store, and the user identification data from the store terminal of the partner store as store payment information, and A procedure for accumulating store payment information, which involves accumulating management data related to the aforementioned partner stores and accumulating the aforementioned store payment information in a store management database, A procedure for calculating reward points, which calculates the amount of reward money to be returned to the parking lot user based on the store payment information mentioned above, A reward point data transmission procedure that transmits reward point data equivalent to the reward amount calculated in the above reward point calculation procedure to the communication terminal (user terminal) related to the parking user, This is a computer program that is executed by the aforementioned parking management server (see Figures 2 and 4).
[0041] (Fourth invention) The fourth invention relates to a computer program for controlling a parking management server according to the second invention. In other words, the procedure for receiving parking information involves receiving parking information from an entrance gate installed at the entrance of the parking lot, which is obtained by linking user identification data related to the parking lot user with payment data indicating that the parking lot user has completed payment upon entry, A procedure for accumulating parking information, which involves accumulating management data for the aforementioned parking lot and accumulating the aforementioned parking information in a parking lot management database, When a parking user makes a payment at a partner store of the aforementioned parking lot, the store payment information receiving procedure receives the amount data of the payment, the store identification data for identifying the partner store, and the user identification data from the store terminal of the partner store as store payment information, and A procedure for accumulating store payment information, which involves accumulating management data related to the aforementioned partner stores and accumulating the aforementioned store payment information in a store management database, A procedure for calculating reward points, which calculates the amount of reward money to be returned to the parking lot user based on the store payment information mentioned above, A reward point data transmission procedure that transmits reward point data equivalent to the reward amount calculated in the above reward point calculation procedure to the above store terminal, This is a computer program that is executed by the aforementioned parking management server (see Figures 6 and 7).
[0042] (Variation 1 of the third and fourth inventions) The third and fourth inventions may be configured as follows: In other words, the aforementioned store management database stores data on the percentage of reward points awarded for the amount data at each affiliated store. In the aforementioned procedure for calculating reward points, the aforementioned reward rate data is also used to calculate the reward point data (see Figure 8).
[0043] (Variations 2 of the third and fourth inventions) The third and fourth inventions may be configured as follows: In other words, a store congestion determination procedure that determines the level of congestion at a partner store (A) using store payment information accumulated in the aforementioned store management database, A congestion data transmission procedure that transmits the store congestion data, which is the result of the store congestion judgment procedure, to a communication terminal related to a parking lot user (Z) other than the aforementioned parking lot user (Y), This is a computer program that causes the aforementioned parking management server to execute (see Figure 11).
[0044] (Fifth invention) The fifth invention relates to a computer program executed on a mobile terminal carried by a parking lot user, which communicates bidirectionally with the parking lot management server according to the first invention. In other words, a parking fee payment data transmission procedure that sends payment data indicating that payment has been completed upon entry by a parking user intending to use the parking lot, linked to user identification data for identifying the aforementioned parking user, to the parking lot entrance gate, A procedure for receiving paid parking data, which involves receiving the aforementioned paid data from the aforementioned parking management server, A procedure for transmitting payment data, in which, when a parking user makes a payment at a partner store of the aforementioned parking lot, the amount of payment data is transmitted as payment data linked to the aforementioned user identification data, and A procedure for receiving reward points, which involves receiving reward point data based on the payment data at the aforementioned partner stores from the aforementioned parking management server, This is a computer program designed to be executed on the aforementioned mobile device (see Figure 9).
[0045] A "mobile terminal" is a computer. Therefore, it is equipped with a data receiving device as a data input device, random access memory, a data storage device, a processing unit (CPU), and a data transmission device as a data output device.
[0046] (The sixth invention) The sixth invention relates to a computer program executed on a mobile terminal carried by a parking lot user, which communicates bidirectionally with a parking lot management server relating to the second invention. In other words, a parking fee payment data transmission procedure that sends payment data indicating that payment has been completed upon entry by a parking user intending to use the parking lot, linked to user identification data for identifying the aforementioned parking user, to the parking lot entrance gate, A procedure for receiving paid parking data, which involves receiving the aforementioned paid data from the aforementioned parking management server, A procedure for transmitting payment data, in which, when a parking user makes a payment at a partner store of the aforementioned parking lot, the amount of payment data is transmitted as payment data linked to the aforementioned user identification data, and A procedure for receiving reward points, in which reward point data based on the shopping payment data at the aforementioned partner store is received from a terminal related to the aforementioned partner store transmitted from the parking management server, This is a computer program designed to be executed on the aforementioned mobile device (see Figure 10).
[0047] The computer programs relating to the fifth and sixth inventions include not only "application programs" that are downloaded in advance to a mobile terminal and executed, but also "programs" that are executed via the Web while the mobile terminal and a predetermined server communicate bidirectionally.
[0048] (Variation 1 of the fifth and sixth inventions) The fifth and sixth inventions may be constructed as follows: In other words, the procedure for transmitting parking reservation data includes the aforementioned user identification data and planned usage date and time data. This is a computer program that is intended to be executed on the aforementioned mobile device (see Figure 9).
[0049] (Variations 2 of the fifth and sixth inventions) The fifth and sixth inventions may be constructed as follows: In other words, the parking management server uses the purchased payment data to determine the level of congestion at the affiliated store (A), and the resulting store congestion data is transmitted to a communication terminal belonging to a parking user (Z) other than the aforementioned parking user (Y). This is a computer program designed to be executed on the aforementioned mobile device. (See Figure 10).
[0050] It is also possible to transmit the computer programs relating to the third to sixth inventions from a computer storing them to other terminal devices via a communication line. They may also be provided via the internet, on a so-called cloud platform.
[0051] Furthermore, computer programs relating to the third and fourth inventions can also be provided by storing them on a recording medium. Here, "recording medium" refers to a medium capable of carrying a program that cannot occupy space on its own. Examples include flexible disks, hard disks, CD-Rs, DVD-Rs, and USB memory sticks. [Effects of the Invention]
[0052] According to the first and second inventions, it was possible to provide a parking management server that can offer a parking fee reimbursement service at partner stores, even when a payment method is adopted at the time of entry. According to the third and fourth inventions, it was possible to provide a computer program for controlling a parking management server that can provide a parking fee reimbursement service at partner stores, even when a payment method is adopted at the time of entry. According to the fifth and sixth inventions, it was possible to provide a computer program that controls an information terminal that communicates bidirectionally with a parking management server, which enables the provision of a parking fee reimbursement service at affiliated stores, even when a payment method is adopted at the time of entry. [Brief explanation of the drawing]
[0053] [Figure 1] This is a conceptual diagram illustrating the payment method used in typical hourly parking lots. [Figure 2] This is a conceptual diagram illustrating embodiments of the present invention. [Figure 3] This is a conceptual diagram showing the data that a user terminal should input and transmit when receiving goods into storage, according to an embodiment of the present invention. [Figure 4] This is a conceptual diagram illustrating the exchange of data between a parking management server that manages a parking lot, a partner store, and a user terminal related to a parking lot user who has made a purchase at that partner store, according to an embodiment of the present invention. [Figure 5] This is a conceptual diagram illustrating the data exchange procedure for point redemption between the user terminal, the parking management server, and the store terminal. [Figure 6] This is a conceptual diagram illustrating the data exchange procedure for point redemption between the user terminal, the parking management server, and the store terminal. [Figure 7] This is a conceptual diagram illustrating the procedure for receiving a partial or full cashback on parking fees from partner stores. [Figure 8] This is a conceptual diagram illustrating how points are credited to the user terminal of a parking lot user who has made purchases at multiple partner stores. [Figure 9] This is a conceptual diagram showing the necessary functions for a user terminal related to parking lot users. [Figure 10] This is a conceptual diagram illustrating the procedure for transmitting the congestion status of partner stores to user terminals related to parking lot users. [Figure 11] This is a conceptual diagram illustrating the procedure for managing the entry and exit of a vehicle using a van equipped with an entry and exit gate system. [Modes for carrying out the invention]
[0054] The present invention will be described below based on the drawings and embodiments. The drawings used herein are Figures 2 to 11. Solid arrows indicate wired communication, dashed arrows indicate wireless communication, and dotted lines indicate dashed lines. Figure 1 illustrates the prior art and may be referred to as needed.
[0055] (Figure 2) Figure 2 shows the relationship between vehicles entering the parking lot, the entrance and exit gates installed in the parking lot, and the parking management server that manages the parking lot's data.
[0056] At the entrance gate, the driver of the entering vehicle (parking user) pays the parking fee in advance. User identification data is required to identify the parking user when paying the parking fee. In the following embodiment, vehicle license plate data acquired by a camera installed at the entrance gate is used as the user identification data (see Figure 3). The vehicle license plate is vehicle identification data that can identify the vehicle, and is also user identification data that can identify the user.
[0057] In addition to vehicle license plate data, other "user-identifying data" includes, for example, the member ID if the user has already registered as a member to use this parking lot. Furthermore, if a reservation has been made to use this parking lot, the reservation ID that identifies the reservation details, and payment-specific data (for example, credit card data if paying by credit card) indicating the promise to pay when executing that reservation, can also be considered user-identifying data.
[0058] Once the prepayment procedure for parking fees is complete, the gate opens, and the vehicle can enter the parking lot. Electronic payment is preferred for parking fees because it allows for easy linking with the aforementioned user identification data.
[0059] The parking gate combines the payment data linked to user identification data with the parking time data to create parking information, which is then sent to the parking management server. The parking management server receives the aforementioned parking information via a parking information receiving device. The received parking information is then stored in the parking management database and also in the user database.
[0060] For vehicles attempting to exit the parking lot, the exit gate is opened upon detection of the vehicle's approach. A camera capable of photographing the license plate of approaching vehicles is installed in front of the exit gate, and detection and acquisition of the license plate are performed by photographing the vehicle. The parking management server may also verify that the license plate exists in the entry information. If verified, since the vehicle associated with that license plate has already paid the parking fee in advance, the server instructs the opening of the exit gate. Once the exit gate is opened, the exit time data, which is the time of exit, is combined with the license plate captured by the aforementioned camera to form exit information, and transmitted to the parking management server.
[0061] The parking management server receives exit information transmitted from the exit gate via an exit data receiving device and stores it in the parking management database and the user database.
[0062] (Figure 3) Figure 3 illustrates the screen display when a parking user enters a parking lot, where the driver of the vehicle inputs vehicle identification data and transmits data indicating that the parking fee has been paid. Note that, as explained below, it is assumed that a dedicated application program, as shown in Figure 9, is pre-installed on the user terminal; however, the pre-installation of this dedicated application program is not mandatory.
[0063] The top of the screen on the user terminal is illustrated as the screen after entering the vehicle number. Although the input screen is not illustrated, the camera installed at the entrance gate acquires image data, performs character recognition on the vehicle number portion, converts it to text, and sends it to the user terminal. The converted vehicle number and a confirmation screen are then displayed, and the parking user is given the option to select either "OK" or "Edit". If the parking user taps the "Edit" button, although not illustrated, the parking user enters the vehicle number on the text input screen of their smartphone.
[0064] The bottom of the screen displays the parking fee, along with a text message indicating that it is prepaid. It then shows the parking user tapping the "Pay" button. If the parking user taps the "Return to previous screen" button, a screen for selecting available electronic payment methods on the user's terminal is displayed (though this is not shown in the diagram).
[0065] When a parking user taps the "Pay" button, payment data linked to vehicle identification data is sent from the user's terminal to the entrance gate. The entrance gate then sends the user identification data (which serves as vehicle identification data), payment data, and entrance time data as entrance information to the parking management server.
[0066] (Figure 4) Figure 4 is a conceptual diagram illustrating the information processing procedures before and after a parking user completes parking in a parking lot, moves to a partner store of that parking lot, and completes payment at the partner store. The numbers in italics and parentheses between each component indicate the data processing steps.
[0067] For parking users who have used the parking lot and prepaid the parking fee, the parking fee payment data is transmitted to the user terminal from the parking management server's parking fee data transmission means (1). This parking fee payment data includes payment data linked to vehicle identification data as user identification data, and entry time data.
[0068] Suppose a parking user enters partner store A and, in response to a payment request from partner store A, completes the payment electronically using the user terminal. The store terminal (cash register) then receives payment data from the user terminal, which includes user identification data (vehicle identification data), payment data indicating that the amount requested has been paid, and entry time data, which is the time the vehicle related to the parking user entered the parking lot (2).
[0069] The store terminal transmits store payment information related to payments made by the parking user at affiliated store A to the parking management server. Store payment information includes user identification data (vehicle identification data), payment data for payments made in response to payment requests from affiliated store A, store identification data, and payment time data (3).
[0070] The store payment information receiving means in the parking management server receives the aforementioned store payment information. The store payment information is then received by the shopping data receiving means in the parking management server, and the necessary data is stored in the parking management database, the store management database, and the user database (4).
[0071] The parking management server checks whether the user identification data in the aforementioned store payment information matches the data in the user database and whether the data matches the data in the parking management database. Then, using data such as the reward rate at partner store A stored in the store management database, the reward point calculation means calculates reward points to compensate the parking user for the prepaid parking fee (5, 6).
[0072] The calculated reward points are converted into data and sent to the user terminal by the reward point data transmission means (7). Whether the reward points data received by the user terminal is added to the wallet used to pay the parking fee or stored in another point accumulation wallet can be determined by the parking user's settings.
[0073] (Figure 5) Figure 5 details the functions of the user terminal and the store terminal, which were simplified in Figure 4. The numbers of the data processing steps, written in italics between each configuration requirement, correspond to those in Figure 4.
[0074] The parking fee payment data transmitted from the parking management server's parking fee data transmission means is received by the payment data receiving means on the user terminal (1). The parking fee payment data received by the payment data receiving means includes user identification data, which is used when making payments at affiliated stores.
[0075] When a parking user visits partner store A, for example, to make a purchase and pays using electronic payment via a user terminal, the store payment information transmission means transmits the store payment information to the store terminal (2). The store payment information includes user identification data that was included in the parking fee payment data. Therefore, partner store A (at its store terminal) can determine that the person who made the payment used the parking lot to visit the store.
[0076] Once the parking user has completed payment, the store payment information transmission means sends the store payment information to the parking management server (3). The parking management server receives the store payment information via the store payment information reception means. The procedure from this point onward is the same as shown in Figure 4, so the explanation will be omitted.
[0077] (Figure 6) Unlike the embodiment shown in Figure 5, Figure 6 shows that the transmission of reward point data to the user terminal is performed from the store terminal. The steps up to (6) in Figure 5 are the same, so the explanation is omitted.
[0078] The parking management server's reward point data transmission means receives the reward point data via the store terminal's reward point receiving means (7). The received reward point data is refunded as refund data to the user terminal of the parking user who made the payment at partner store A, via the electronic refund means of store terminal A.
[0079] For parking lot users, the advantage is that they can receive refund data on the spot at the partner store A where they made their purchase.
[0080] (Figure 7) Figure 7 is an alternative version of the store rebates shown in Figure 6. The part up to (7) in Figure 6 is the same.
[0081] Store terminals that receive reward point data via the reward point receiving method will refund the points to parking users in cash, rather than as electronic data.
[0082] (Figure 8) Figure 8 shows how reward points are generated for each payment made at multiple partner stores and then returned to the parking user.
[0083] Partner store A offers a parking fee rebate rate of 5% of the pre-tax price. Partner store B offers a parking fee rebate rate of 20% of the pre-tax price. In this way, partner stores can set their own rates, increasing their freedom in store management.
[0084] Parking users can receive reward points separately, such as Reward Point Data A (50 points) and Reward Point Data B (200 points). This eliminates the hassle of the traditional system, where you have to carry a physical parking ticket, get it stamped each time you pay at a participating store, and only get a refund if the total payment exceeds the parking fee.
[0085] (Figure 9) Figure 9 is a conceptual diagram showing the functions required for a user terminal related to parking lot users. These are functions that are implemented by a dedicated application program. Although this explanation assumes that a dedicated application program has been downloaded in advance, the functions required on the user terminal are the same even if the program is in the form of processing information with a designated site on the web.
[0086] First, there is a means for inputting vehicle identification data. In addition to direct input by the parking lot user, the means for inputting vehicle identification data also includes means for verifying the input vehicle identification data, such as a camera that photographs the license plate number as shown in Figure 3. Furthermore, as mentioned above, since the primary purpose is to identify the user, identification is not limited to the license plate number, but may also be done using the user ID related to the parking lot user's payment of fees, etc.
[0087] Furthermore, a payment data input method is used to input payment data for parking users to pay parking fees or to make payments at stores, and this data is linked to vehicle identification data to prepare for payment.
[0088] At the entrance gate, the parking fee, which has been paid in advance, is paid using the parking fee payment data transmission means. Specifically, payment data linked to vehicle identification data is transmitted to a designated device at the entrance gate (1). The entrance gate then transmits the payment data linked to vehicle identification data to the parking management server (not shown in the diagram), and the parking fee payment data receiving means at the user terminal receives the payment data from the parking management server (2).
[0089] Suppose a parking user, having paid the parking fee and completed parking their vehicle, gets out of the vehicle and goes to a partner store, where they make a payment. In this case, the payment, along with user identification data, store ID as store identification data, and amount data, is transmitted as store payment information to the partner store's terminal (3). This store payment information is then transmitted from the store terminal to the parking management server (not shown in the diagram). Based on the store payment information, reward points are calculated, and the reward point data is received by the reward point receiving means via the reward point data transmission means (4).
[0090] To reserve a parking space, the user identifies the desired date and time of use and creates a parking reservation data linked to the vehicle identification data. Then, the reservation data is sent to the parking management server using the parking reservation data transmission method (0).
[0091] (Figure 10) Figure 10 shows an embodiment in which the congestion status of partner stores is estimated based on factors such as the frequency of obtaining store payment information, and this information is distributed to parking lot users.
[0092] When a parking user Y makes a payment using their own user terminal Y, payment information is sent from store terminal A to the parking management server. By verifying how frequently this payment information is received per hour using data stored in the store management database, it is possible to estimate the level of congestion at partner store A.
[0093] The aforementioned estimation is performed by the store congestion determination means of the parking management server, and the estimation result is transmitted to user terminal Z of parking user Z other than parking user Y via the congestion data transmission means. Parking user Z can know the estimated congestion level of affiliated store A in advance. For example, this can be used as information to decide whether to kill time before going if it is crowded, or to go first if it does not seem crowded.
[0094] (Figure 11) Figure 11 shows an embodiment using a parking gate wagon equipped with an entry gate and an exit gate.
[0095] A parking gate van is a vehicle used to temporarily set up equipment, mainly entrance gates, exit gates, and payment machines, in spaces that lack the necessary parking facilities. It is used when land normally used for other purposes is temporarily utilized as a parking lot.
[0096] The entrance and exit gates shown in Figure 2 appear when the rear door of the parking gate wagon shown in Figure 11 is opened. The cameras installed on the entrance and exit gates shown in Figure 2 are omitted in Figure 11 for illustrative purposes, but they are also mounted on the parking gate wagon. The other configurations are the same as in Figure 2, so their explanation is omitted.
[0097] According to the embodiments described above, even if a payment method is adopted at the time of entry, it will be possible to provide a service that covers parking fees at partner stores. This is convenient for parking users who actively use electronic payments, and convenient for companies that manage parking lots because it reduces the likelihood of unpaid parking fees. Furthermore, partner stores of parking lots can continue to cover parking fees as before without incurring significant additional costs. [Industrial applicability]
[0098] The present invention has potential applications in the parking lot management industry, the manufacturing industry of information and communication equipment necessary for the operation of parking lots and affiliated stores, the software service industry that creates application programs used in parking lot management servers, and the information and communication service industry that creates and provides application programs used by parking lot users on their mobile terminals.
Claims
1. A parking management server for managing parking lots that use an entry-based payment system, An entry information receiving means receives entry information from an entry gate installed at the entrance of the aforementioned parking lot, which is obtained by linking user identification data pertaining to payment data indicating that a parking lot user has completed payment upon entry when intending to use the aforementioned parking lot, A parking management database that stores management data for the aforementioned parking lot and also stores the aforementioned parking entry information, In addition to being equipped, When a parking user makes a payment at a partner store of the aforementioned parking lot, the store payment information receiving means receives from the store terminal of the partner store as store payment information, which links the amount data of the payment and the user identification data to store identification data for identifying the partner store. A store management database that stores management data related to the aforementioned partner stores and store payment information, A reward point calculation means that calculates the amount of reward to be returned to the parking user based on the aforementioned store payment information, A reward point data transmission means transmits reward point data corresponding to the reward amount calculated by the aforementioned reward point calculation means to a communication terminal relating to the parking user. A parking management server equipped with the following features.
2. A parking management server for managing parking lots that use an entry-based payment system, An entry information receiving means receives entry information from an entry gate installed at the entrance of the aforementioned parking lot, which is obtained by linking user identification data pertaining to payment data indicating that a parking lot user has completed payment upon entry when intending to use the aforementioned parking lot, A parking management database that stores management data for the aforementioned parking lot and also stores the aforementioned parking entry information, In addition to being equipped, When a parking user makes a payment at a partner store of the aforementioned parking lot, the store payment information receiving means receives from the store terminal of the partner store as store payment information, which links the amount data of the payment and the user identification data to store identification data for identifying the partner store. A store management database that stores management data related to the aforementioned partner stores and store payment information, A reward point calculation means that calculates the amount of reward to be returned to the parking user based on the aforementioned store payment information, A reward point data transmission means transmits reward point data corresponding to the reward amount calculated by the aforementioned reward point calculation means to the aforementioned store terminal, A parking management server equipped with the following features.
3. The aforementioned store management database stores data on the percentage of reward points awarded for the aforementioned monetary data at each partner store. The aforementioned reward point calculation means calculates the reward point data using the aforementioned reward rate data as well. A parking management server according to either claim 1 or claim 2.
4. A store congestion determination means that determines the level of congestion at partner stores using store payment information accumulated in the aforementioned store management database, The system also includes a congestion data transmission means that transmits the store congestion data, which is the result of the store congestion determination means, to a communication terminal related to a parking user other than the aforementioned parking user. A parking management server according to either claim 1 or claim 2.
5. A procedure for receiving parking information from the entrance gate installed at the entrance of the aforementioned parking lot, which links user identification data related to the parking lot user with payment data indicating that the parking lot user has completed payment upon entry, A procedure for accumulating parking information, which involves accumulating management data for the aforementioned parking lot and accumulating the aforementioned parking information in a parking lot management database, When a parking user makes a payment at a partner store of the aforementioned parking lot, the store payment information receiving procedure receives the amount data of the payment, the store identification data for identifying the partner store, and the user identification data from the store terminal of the partner store as store payment information, and A procedure for accumulating store payment information, which involves accumulating management data related to the aforementioned partner stores and accumulating the aforementioned store payment information in a store management database, A procedure for calculating reward points, which calculates the amount of reward money to be returned to the parking lot user based on the store payment information mentioned above, A procedure for transmitting reward point data, which involves sending reward point data equivalent to the reward amount calculated in the above-mentioned reward point calculation procedure to the communication terminal (user terminal) related to the parking user, A computer program that instructs the parking management server to execute a command.
6. A procedure for receiving parking information from the entrance gate installed at the entrance of the aforementioned parking lot, which links user identification data related to the parking lot user with payment data indicating that the parking lot user has completed payment upon entry, A procedure for accumulating parking information, which involves accumulating management data for the aforementioned parking lot and accumulating the aforementioned parking information in a parking lot management database, When a parking user makes a payment at a partner store of the aforementioned parking lot, the store payment information receiving procedure receives the amount data of the payment, the store identification data for identifying the partner store, and the user identification data from the store terminal of the partner store as store payment information, and A procedure for accumulating store payment information, which involves accumulating management data related to the aforementioned partner stores and accumulating the aforementioned store payment information in a store management database, A procedure for calculating reward points, which calculates the amount of reward money to be returned to the parking lot user based on the store payment information mentioned above, A reward point data transmission procedure that transmits reward point data equivalent to the reward amount calculated in the above reward point calculation procedure to the above store terminal, A computer program that instructs the parking management server to execute a command.
7. The aforementioned store management database stores data on the percentage of reward points awarded for the aforementioned monetary data at each partner store. In the aforementioned procedure for calculating reward points, the aforementioned reward rate data is also used to calculate the reward point data. The computer program according to claim 5 or claim 6.
8. A store congestion determination procedure that uses store payment information stored in the aforementioned store management database to determine the level of congestion at partner stores, The parking management server was instructed to execute a congestion data transmission procedure, which involves sending the store congestion data, which is the result of the store congestion determination procedure, to a communication terminal belonging to a parking user other than the aforementioned parking user. The computer program according to claim 5 or claim 6.
9. A computer program that runs on a mobile terminal carried by a parking user to communicate bidirectionally with a parking management server, A parking fee payment data transmission procedure that transmits payment data indicating that the aforementioned parking user has completed payment upon entry to the entrance gate of the aforementioned parking lot, linked to user identification data for identifying the aforementioned parking user, and A procedure for receiving paid parking data, which involves receiving the aforementioned paid data from the aforementioned parking management server, A procedure for transmitting payment data, in which, when a parking user makes a payment at a partner store of the aforementioned parking lot, the amount of payment data is transmitted as payment data linked to the aforementioned user identification data, and A procedure for receiving reward points, which involves receiving reward point data based on the payment data at the aforementioned partner stores from the aforementioned parking management server, A computer program that is intended to be executed on the aforementioned mobile device.
10. A computer program that runs on a mobile terminal carried by a parking user to communicate bidirectionally with a parking management server, A parking fee payment data transmission procedure that transmits payment data indicating that the aforementioned parking user has completed payment upon entry to the entrance gate of the aforementioned parking lot, linked to user identification data for identifying the aforementioned parking user, and A procedure for receiving paid parking data, which involves receiving the aforementioned paid data from the aforementioned parking management server, A procedure for transmitting shopping payment data, in which, when a parking user makes a payment at a partner store of the aforementioned parking lot, the amount of the payment is transmitted as payment data linked to the aforementioned user identification data, and A procedure for receiving reward points, in which reward point data based on the payment data at the aforementioned partner store is received from a terminal related to the aforementioned partner store transmitted from the parking management server, A computer program that is intended to be executed on the aforementioned mobile device.
11. The procedure for transmitting parking reservation data includes the aforementioned user identification data and planned usage date and time data. This was to be executed on the aforementioned mobile device. A computer program according to claim 9 or claim 10.
12. The aforementioned parking management server uses the aforementioned payment data to determine the level of congestion at partner stores, and the resulting store congestion data is transmitted to a communication terminal belonging to a parking user other than the aforementioned parking user. This was to be executed on the aforementioned mobile device. A computer program according to claim 9 or claim 10.