JP7804375B2 - Parking lot management system and program - Google Patents

Description

The present invention relates to technology for managing parking lots.

Parking lots with multiple parking locations for vehicles are already widespread. These types of parking lots can be classified based on the method used to transport vehicles to the parking location: either a system where the user drives the vehicle to the parking location, or a mechanical system where a pallet or cage is mechanically moved to transport the vehicle to the parking location. Furthermore, such parking lots may be rented to users free of charge or for a fee. Paid parking lots can be classified based on the length of time the space is rented to users: monthly or hourly (including daily).

Hourly parking lots can be classified by the payment method used to pay the parking fee: prepaid, where the user pays the parking fee before starting to park (although this includes the possibility of paying any remaining parking fee when leaving the lot), and deferred payment, where the user pays the parking fee in full when parking is finished.

Hourly parking lots can also be classified by their management method: manned parking lots, where a person who manages and monitors the parking lot is permanently stationed at the parking lot, and unmanned parking lots, where a person who is not permanently stationed at the parking lot is dispatched to the parking lot sporadically.

Patent document 1, for example, is a publicly known document that discloses this type of parking lot and the equipment (including ticket issuing machines) installed therein.

Patent Document 1 discloses a prepaid unmanned parking lot. This parking lot is equipped with a card issuing machine that issues, for a fee, parking cards that record the time parking is permitted, an entrance gate that is always closed, and an entrance management device installed at the entrance that opens the entrance gate when a parking card is inserted, provided that the parking card is valid. The parking lot is also equipped with an exit gate that is always closed, and an exit management device installed at the exit that opens the exit gate when a parking card is inserted, provided that the parking card is valid.

In this way, Patent Document 1 discloses technology that allows a user to park a vehicle in an unmanned paid parking lot using a real card (e.g., a physical parking ticket).

In response to this, Patent Document 2 discloses technology that allows a user to park a vehicle in an unmanned paid parking lot using a cardless system.

Japanese Patent Application Laid-Open No. 2006-146325 Japanese Patent Application Publication No. 8-111000

The technology disclosed in Patent Document 2 allows users to park in a parking lot without using a card, which has the advantage of eliminating the need to worry about losing the card. However, implementing the technology disclosed in Patent Document 2 requires the installation of specialized and expensive equipment in both the vehicle and the parking lot to obtain information specific to the vehicle attempting to park in the parking lot. This has the disadvantage that it can increase the cost of the equipment itself, the cost and labor required to install that equipment in the parking lot, and the cost and labor required to maintain and inspect that equipment for the owner or manager of the parking lot.

In addition, it is important for parking lot managers to accurately track when users enter and exit the parking lot. Furthermore, it is important for hourly parking lot users to improve the technology for settling parking fees.

Based on the above findings, the present invention aims to improve parking lot management technology, which allows users to settle parking fees using their communication devices and/or technology for determining whether a user is permitted to use a parking lot.

In order to solve this problem, according to one aspect of the present invention, there is provided a parking lot management system,
a display unit that is installed in the parking lot and displays the encrypted data without using a physical parking ticket;
a management server located in a remote location from the parking lot;
The management server is
a parking lot identification unit that, when exiting the parking lot, receives first information from the communication device of the user currently in the parking lot to identify the parking lot from which the user is about to exit by communicating with the management server using the displayed encrypted data, and identifies the parking lot based on the received first information;
a user-specific information identification unit that receives second information for identifying a number unique to the user from the communication device when the vehicle leaves the parking lot, and that is capable of identifying user-specific information unique to the user based on the received second information;
and an electronic payment unit that, when the parking lot and the user- specific information are identified upon exiting the parking lot, enables the parking fee for the identified parking lot to be settled by electronic payment through communication with the communication device.

According to another aspect of the present invention, there is provided a program executed by a computer of a communication device of a user who is currently in the parking lot managed by the parking lot management system, the program comprising:
The communication device has a plurality of functions,
a first transmission function that, when the user leaves the parking lot, communicates with the management server using the displayed encrypted data to transmit the first information from the user to the management server;
a second transmission function of transmitting the second information from the user to the management server when the user leaves the parking lot;
and a settlement completion data receiving function for receiving, when the parking fee has been settled by electronic payment by the management server at the time of exiting the parking lot, settlement completion data indicating that the settlement of the parking fee has been completed from the management server,
A program is provided that is executed by the computer to realize the functions.

The present invention provides the following aspects. Each aspect is divided into paragraphs, each numbered, and described in a format that cites the numbers of other paragraphs as necessary. This is to facilitate understanding of some of the technical features and combinations thereof that may be employed by the present invention, and should not be construed as limiting the technical features and combinations thereof that may be employed by the present invention to the following aspects. In other words, it should be understood that technical features that are not described in the following aspects but are described in this specification may be appropriately extracted and employed as technical features of the present invention.

Furthermore, describing each paragraph in a format that references the number of another paragraph does not necessarily mean that the technical features described in each paragraph cannot be separated and made independent from the technical features described in other paragraphs, and it should be interpreted that the technical features described in each paragraph can be made independent as appropriate depending on their nature.

(1) A parking lot management method for managing a parking lot, comprising:
The parking lot includes:
A clock and
an encryption unit that converts the current time measured by the clock into a time code that can be read and reproduced by a user of the parking lot as a known letter, number, symbol, or graphic, or a combination thereof, and that is indecipherable to the user but decipherable to the manager of the parking lot;
a display unit that displays the time code generated by the encryption unit; and
The parking lot management method is as follows:
a receiving step at the time of entry, in which the communication unit receives information for identifying the electronic parking ticket, which the user transmitted via a communication device when entering the parking lot in order to park in the parking lot using the electronic parking ticket, and a time code displayed on the display unit when the user entered the parking lot;
a warehousing time validity determination step in which a processor decodes the time code received at the time of warehousing by referring to a decode table, estimates the time represented by the received time code as the warehousing time based on the decoded result, and determines whether the estimated warehousing time is within a predetermined allowable range determined for the reception time at which the processor received the time code, thereby determining whether the estimated warehousing time is valid;
a parking permission step of permitting the user to use the parking lot if the processor determines that the estimated entry time is valid.

Throughout this specification, the term "electronic parking ticket" refers to a non-existent, virtual parking ticket that does not require the user to print or display the information on the electronic parking ticket on another medium and present it to the other party in order to use the electronic parking ticket.

(2) A parking lot management method for managing a parking lot, comprising:
The parking lot includes:
a display unit is provided which displays a time code generated by encrypting the current time, which can be read and reproduced by a user of the parking lot as a known letter, number, symbol, or figure, or a combination thereof, and which cannot be deciphered by the user but can be deciphered by the manager of the parking lot;
The parking lot management method is as follows:
a receiving step at the time of entry, in which the communication unit receives information for identifying the electronic parking ticket, which the user transmitted via a communication device when entering the parking lot in order to park in the parking lot using the electronic parking ticket, and a time code displayed on the display unit when the user entered the parking lot;
a warehousing time validity determination step in which a processor decodes the time code received at the time of warehousing by referring to a decode table, estimates the time represented by the received time code as the warehousing time based on the decoded result, and determines whether the estimated warehousing time is within a predetermined allowable range determined for the reception time at which the processor received the time code, thereby determining whether the estimated warehousing time is valid;
a parking permission step of permitting the user to use the parking lot if the processor determines that the estimated entry time is valid.

(3) Furthermore,
a receiving step at the time of exit, in which the communication unit receives information for identifying the electronic parking ticket, which the user transmitted via the communication device when exiting the parking lot, and a time code displayed on the display unit when the user exited the parking lot;
a departure time validity determination step in which the processor decodes the time code received at the time of departure by referring to the decode table, estimates the time represented by the received time code as the departure time based on the decoded result, and determines whether the estimated departure time is within a predetermined allowable range determined for the reception time at which the processor received the time code, thereby determining whether the estimated departure time code is valid;
and a parking time calculation step of calculating, when the processor determines that the estimated exit time is valid, the length of time elapsed from the estimated entry time to the estimated exit time as the parking time by the user.

(4) Furthermore,
an issuance request receiving step of receiving, in the communication unit, an issuance request transmitted by the user via the communication device to request the parking manager to issue the electronic parking ticket;
A parking lot management method described in any of (1) to (3), which includes an electronic parking ticket issuance process in which the processor responds to the received issuance request and issues the electronic parking ticket to the user and transmits it to the user's communication device, on the condition that the user pays a predetermined amount of fee in advance.

(5) Installed and used in a parking lot,
A time code display device for a parking lot displays a time code generated by encrypting the current time, which can be read and reproduced by a user of the parking lot as a known letter, number, symbol or figure, or a combination thereof, and which cannot be deciphered by the user but can be deciphered by the manager of the parking lot.

(6) A time code display device for a parking lot described in paragraph (5), which also displays a location code unique to the parking lot along with the time code.

(7) A management server that is communicatively connected to the user's communication device via a communication network and that executes the parking lot management method described in any one of items (1) to (4) by computer.

(8) A program executed by a computer to implement the parking lot management method described in any one of (1) to (4).

The present invention makes it possible to provide a service that allows users to park in a parking lot using a cardless system, without the need to install special and expensive equipment in the parking lot.

FIG. 1 is a plan view showing an example of a parking lot managed by a parking lot management method according to a first exemplary embodiment of the present invention. FIG. 2 is a front view showing the ticket issuing machine shown in FIG. FIG. 3 is a perspective view of the ticket issuing machine shown in FIG. 2 with the door open. FIG. 4 is a block diagram showing the component configuration of the ticket issuing machine shown in FIG. FIG. 5 is a flowchart conceptually showing the ticket issuing and fare adjustment program executed by the computer shown in FIG. 6(a) to 6(d) are front views showing a plurality of images displayed on the screen of the display device shown in FIG. Figure 7(a) is a front view showing an example of a parking ticket and receipt issued by the ticket issuing machine shown in Figure 2 after payment of the advance parking fee, and Figure 7(b) is a front view showing an example of a receipt issued by the ticket issuing machine shown in Figure 2 after payment of the additional parking fee. Figure 8(a) is a vertical cross-sectional view of the parking ticket shown in Figure 7(a) immediately after it has been issued, and Figure 8(b) is a vertical cross-sectional view of the parking ticket with a portion peeled off and folded. Figure 9(a) is a side cross-sectional view showing the parking ticket shown in Figure 7(a) attached to the back of the windshield of a parked vehicle, and Figure 9(b) is a perspective view showing the parking ticket with part of its display sheet peeled off from the separator and folded. FIG. 10 is a perspective view showing the parking ticket shown in FIG. 7(a) stuck to the back of the windshield of a parked vehicle. Figures 11(a)-(c) are diagrams for explaining the structure of an example of encrypted data to be printed on the receipts shown in Figures 7(a) and (b), respectively, the corresponding actual data, and the process of converting the actual data into encrypted data. Figure 12 is an oblique view illustrating how a user communicates the encrypted data printed on the receipts shown in Figures 7(a) and (b) to a parking lot manager in a remote location using his or her mobile phone, and how the parking lot manager converts the received encrypted data into actual data. 13(a)-(c) are diagrams for conceptually explaining the process of generating and displaying a time code, which are parts of the ticket issuing machine shown in FIG. 4 that are related to the parking lot management method. FIG. 14 is a flowchart conceptually illustrating a code display program executed by the computer of the ticket issuing machine shown in FIG. 4 to perform the processing shown in FIGS. 13(a)-(c) (generation and display of time codes). FIG. 15 is a conceptual system diagram for explaining the entire system in which the parking lot management method is implemented. FIG. 16 is a flowchart conceptually showing a first subprogram, which is part of the electronic parking ticket processing program executed in the management server shown in FIG. FIG. 17 is a flowchart conceptually showing a second subprogram, which is another part of the electronic parking ticket processing program executed in the management server shown in FIG. FIG. 18 is a flowchart conceptually showing a third subprogram, which is yet another part of the electronic parking ticket processing program executed in the management server shown in FIG. FIG. 19 is a diagram conceptually showing the member DB shown in FIG. FIG. 20 is a diagram conceptually showing the electronic parking ticket DB shown in FIG. FIG. 21 is a diagram showing an example of an electronic parking ticket issued by executing the electronic parking ticket processing program. FIG. 22 is a sequence diagram for explaining the process of member registration performed by executing the electronic parking ticket processing program. FIG. 23 is a sequence diagram for explaining the process of issuing an electronic parking ticket, which is performed by executing the electronic parking ticket processing program. FIG. 24 is a sequence diagram for explaining the process of permitting use of an electronic parking ticket, which is performed by executing the electronic parking ticket processing program. FIG. 25 is a diagram showing an example of a receipt issued by executing the electronic parking ticket processing program. FIG. 26 is a sequence diagram for explaining the process of settling the parking fee when parking for an extended period, which is carried out by executing the electronic parking ticket processing program. FIG. 27 is a sequence diagram for explaining the process of urging delivery executed by the management server shown in FIG. Figure 28 is a flowchart conceptually showing a fourth subprogram that replaces the second subprogram shown in Figure 17 among the electronic parking ticket processing programs executed in the management server to execute a parking lot management method according to an exemplary second embodiment of the present invention. FIG. 29 is a flowchart conceptually showing a fifth subprogram that replaces the third subprogram shown in FIG. 18 in the electronic parking ticket processing program in the second embodiment. FIG. 30 is a sequence diagram for explaining the process of permitting parking using an electronic parking ticket, which is performed by executing the electronic parking ticket processing program in the second embodiment. FIG. 31 is a sequence diagram for explaining the process of settling fees at the end of parking using an electronic parking ticket, which is performed by executing the electronic parking ticket processing program in the second embodiment. FIG. 32 is a diagram showing an example of a receipt issued by executing the electronic parking ticket processing program in the second embodiment. FIG. 33 is a sequence diagram for explaining the step of urging delivery, which is executed by the management server in the second embodiment.

The following describes in detail parking lot management methods according to some exemplary embodiments of the present invention, with reference to the accompanying drawings.

<First embodiment>

Figure 1 shows a plan view of a parking lot 10 managed by a parking lot management method according to a first exemplary embodiment of the present invention.

This parking lot 10 has multiple parking locations (parking spaces) that allow multiple vehicles to park simultaneously. Near the parking lot's 10's only entrance/exit 12 (which serves as both an entrance and an exit), a single ticket dispenser (commonly known as a "payment machine") 20 is installed as a centralized ticket dispenser shared by multiple parking locations. This parking lot 10 is unmanned, with no dedicated staff on-site to manage it; drivers pay their parking fees at the ticket dispenser 20.

In this embodiment, a user can purchase an electronic parking ticket (which typically allows multiple parking sessions rather than a single session, and is equivalent to a coupon ticket for public transport such as trains or buses) online from the parking lot manager at any location in advance, without being required to access the parking lot manager from within the parking lot 10, and can then use that electronic parking ticket to park in the parking lot 10.

However, in this embodiment, instead of parking in this way, each time a user wishes to use this parking lot 10, the user specifies the length of time they intend to park for, prior to parking (when entering the parking lot), and pays the corresponding parking fee as an advance parking fee to the ticket issuing machine 20. This allows the user to purchase a parking ticket printed on paper (i.e., a physical ticket, actual ticket or card) from the ticket issuing machine 20, and then use that paper parking ticket to park in this parking lot 10.

In other words, in this embodiment, users can choose between a new type of parking (cashless and cardless, hereinafter referred to as "cardless parking") that uses an electronic parking ticket (virtual ticket) that can be purchased by online access to the parking lot manager from any location, and regular parking (requiring both cash and a physical ticket, hereinafter referred to as "regular parking") that uses a physical parking ticket that can only be purchased from the ticket issuing machine 20 installed in the parking lot 10, depending on their preference.

As an additional note regarding the definition of the term "vehicle," in this "Description of the Invention" section, the term "vehicle" refers only to automobiles, but elsewhere in this specification, the term "vehicle" should be interpreted as including not only automobiles but also all types of moving objects, such as bicycles and motorcycles.

There are two types of parking spaces on the premises of parking lot 10. These are spaces where parking spaces are rented out to vehicle users on a daily basis (temporary parking spaces or daily rental spaces), and spaces where parking spaces are rented out to vehicle users on a monthly basis, subject to a prior contract (monthly parking spaces). Ticket dispensers 20 are used in temporary parking spaces. Hereinafter, when we simply refer to "parking lot 10," we mean only the temporary parking spaces within parking lot 10, i.e., the areas where ticket dispensers 20 are used.

To use the parking lot 10, the user (driver) drives their vehicle into the entrance/exit gate 12 from an adjacent road, continues driving past the ticket issuing machine 20, and then drives their vehicle to one of the parking spaces (parking positions) of their choice and parks there.

When performing the normal parking, the user parks their vehicle in one of the parking spaces, gets out of their vehicle, walks to the ticket dispenser 20 at the entrance/exit 12, and pays the parking fee to the ticket dispenser 20.

Figure 2 shows a front view of the ticket dispenser 20, Figure 3 shows a perspective view of the ticket dispenser 20 with the door 24 open, and Figure 4 shows a block diagram of the components of the ticket dispenser 20. Figure 5 shows a conceptual flowchart of the ticket issuing and fare adjustment program executed by the computer 100 in the control board 34 shown in Figure 4. Figures 6(a)-(d) show front views of multiple images displayed on the screen of the display 36 shown in Figure 2.

In exchange for paying the parking fee, the user receives a parking ticket 80, shown in Figures 7(a) and 8, from the ticket issuing machine 20. The user then attaches the parking ticket 80 to the back of the windshield 110 (an example of a vehicle's "window glass") of their vehicle, as shown in Figures 9 and 10. Because the parking ticket 80 is placed inside the parked vehicle, it will not be exposed to the elements and will not be lost.

Parking lot 10 is a prepaid, unmanned parking lot with multiple parking locations. It does not have any devices (e.g., exit gate devices or wheel chock devices (e.g., flap-type or retractable)) to prevent vehicles from leaving the parking lot (preventing vehicles from leaving parking lot 10), and users can freely select any of the multiple parking locations to park their vehicle in (the selected parking location is not monitored by ticket dispenser 20). Ticket dispenser 20 is used for parking lots 10 configured in this manner.

Now, we will explain the ticket dispenser 20 in more detail. This ticket dispenser 20 has a fee settlement function but does not have a change function or a communication function. This ticket dispenser 20 requires the user to pay the parking fee only with coins, not with paper money. Furthermore, this ticket dispenser 20 does not require the user to input a user identification number, input vehicle identification information about the user's vehicle (e.g., vehicle number), or specify which of multiple parking locations the user will select.

As shown in FIG. 2, the ticket dispenser 20 has a ticket button 70 and a fee settlement button 74. When a user presses the ticket dispenser button 70 after paying the prepaid parking fee prior to starting parking, the ticket dispenser 20 has a ticket issuing function that issues two documents: a parking ticket 80 (see FIG. 7(a)) indicating that parking has been permitted, and a receipt 81a (see FIG. 7(a)) indicating that the prepaid parking fee has been settled. The ticket dispenser 20 also has a fee settlement function that issues a receipt 81b (see FIG. 7(b)) indicating that the additional parking fee has been settled, when the user presses the fee settlement button 74 after paying the additional parking fee after parking has ended.

In this embodiment, the two-piece parking ticket issued after payment of the prepaid parking fee consists of a parking ticket 80 and a receipt 81a. The user can separate the parking ticket 80 and receipt 81a, leaving only the parking ticket 80 in the parked vehicle and carrying the receipt 81a with them. As described below, the receipt 81a has the end time of the valid parking time (the time period during which the user is permitted to park) printed on it. It is convenient for the user to carry this receipt 81a with them so that they can refer to the end time of the valid parking time at any time, even when they are away from the parked vehicle.

As shown in Figure 3, this ticket dispenser 20 is constructed with a vertically long, box-shaped casing 22 to which a door 24 is attached at one side so that it can be opened and closed. Figure 3 shows a perspective view of the internal structure of this ticket dispenser 20 with the door 24 open. Figure 4 shows a block diagram of the components of this ticket dispenser 20.

As shown in Figure 3, the ticket dispenser 20 is configured to include a coin processing unit 30, a safe 32, a control board 34, a display 36, and a printer 40 that prints and issues parking tickets 80 and receipts 81a and 81b. Of these components, only the coin processing unit 30 is attached to the back of the door 24, while the remaining components are attached inside the casing 22.

As shown in FIG. 3, printer 40 is equipped with roller 42, around which the continuous sheet before printing is wound and stored. Printer 40 prints on the continuous sheet, which is fed from roller 42 one sheet at a time. After printing is complete, printer 40 cuts the continuous sheet with a cutter (not shown) as needed, and separates a pair of sheets, consisting of a parking ticket 80 and a receipt 81a, from the continuous sheet after the prepaid parking fee has been paid, and a single receipt 81b after the additional parking fee has been paid. However, as shown in FIG. 7(a), a perforation line 89 is formed between the pair of parking ticket 80 and receipt 81a, allowing the user to easily separate the parking ticket 80 and receipt 81a from each other along perforation line 89.

The cutter has a cutting blade (not shown) that moves across the width of the continuous sheet to cut the continuous sheet across the width. The cutter can either completely cut the continuous sheet across the width, or cut the continuous sheet across the width, leaving only a portion of it.

As shown in Figures 2 and 4, the coin processing unit 30 has a coin slot 50, a return lever 52, a coin selector 54 (which determines the type of coin inserted and whether the inserted coin is counterfeit) and a coin return slot 56. Inserted coins that are not returned to the user through the coin return slot 56 are stored in the safe 32. As shown in Figure 4, a control board 34 is connected to the coin selector 54 so as to be able to communicate data, and the control board 34 receives signals from the coin selector 54 indicating the type and number of inserted coins (including the denomination of the coin and information on whether the coin is counterfeit).

As shown in FIG. 2, the front of the door 24 is provided with a transparent window 60 through which display light from the screen of the display 36 (e.g., a liquid crystal display) passes, a coin slot 50, a coin return lever 52, a coin return slot 56, and an outlet 64 for discharging the parking ticket 80 and receipts 81a and 81b printed and discharged by the printer 40. The transparent window 60 also serves to mechanically protect the display 36 by preventing direct access to the display 36 from the outside.

The ticket dispenser 20 is further configured to have the aforementioned ticket issue button 70, which the user presses after paying the prepaid parking fee, and the aforementioned fee settlement button 74, which the user presses after paying the additional parking fee. The ticket issue button 70 and fee settlement button 74 are mounted on the front of the door 24 of the ticket dispenser 20, as shown in FIG. 2. The ticket issue button 70 and fee settlement button 74 are electrically connected to the control board 34, as shown in FIG. 4.

The ticket issuing button 70 and the fare settlement button 74 are both configured as actual physical switches, but are not limited to this and may be configured, for example, as virtual switches (e.g., buttons, keys, icons) displayed on the screen of the display 36.

The control board 34 is primarily composed of a computer 100. This control board 34 has a built-in clock 102, which allows it to constantly acquire the current date and time (for example, the date and time when the ticket issue button 70 was pressed, or the date and time when the fare adjustment button 74 was pressed). This control board 34 also has built-in memory 104. This memory 104 stores an encryption table, described below, in a state that can only be rewritten by authorized personnel.

In addition, the control board 34 can be configured to achieve the same functions as the computer 100 using a sequencer (sequence control).

Furthermore, although not shown, the ticket dispenser 20 has a power supply unit. This power supply unit has a power source (e.g., a commercial power source, a solar cell installed in the parking lot 10, a generator such as a wind turbine, or a rechargeable battery installed in the parking lot 10 that is charged by a commercial power source or generator) and supplies power from this power source to each electrical and electronic component within the ticket dispenser 20, thereby operating the ticket dispenser 20. This power supply unit may, for example, additionally have a backup circuit with a power storage function, so that even if the power supply from the above power source is temporarily interrupted, this will not affect the operation of the ticket dispenser 20. This ensures that the ticket dispenser 20 will always operate.

When the ticket issuance and settlement program shown in Figure 5 is executed by the computer 100, first, in step S1, the initial screen shown in Figure 6(a) is displayed on the screen of the display 36. Next, in step S2, it is determined based on a signal from the coin selector 54 whether or not the user has inserted a coin. If no coin has been inserted, the process returns to step S2. However, if a coin has been inserted, in step S3, the total amount of coins inserted by the user up to that point is calculated as the inserted amount.

Next, in step S4, the parking time corresponding to the calculated deposit amount is calculated as the parking time (if the parking fee paid this time is a prepaid parking fee, this means valid parking time, but if the parking fee paid this time is an additional parking fee, this means extended parking time) from the calculated deposit amount. Since the relationship between the deposit amount and the length of parking time, i.e., the hourly fee setting, is known to computer 100, computer 100 can calculate the parking time from the deposit amount in accordance with the fee setting. The fee setting can be set by the parking lot manager, for example, by operating the touch panel on display 36, and can be entered individually for each hourly unit.

According to the above pricing example, continuous parking is 300 yen for up to two hours, 400 yen for up to four hours, 500 yen for up to six hours, 1000 yen for up to 12 hours, and 1500 yen for up to 24 hours. Under this pricing example, for example, as shown in Figure 7, if a user pays 400 yen as an advance parking fee, computer 100 will calculate four hours as valid parking time. Furthermore, if a user pays 300 yen as an additional parking fee, two hours will be calculated as extended parking time.

Then, in step S5, the coin insertion screen shown in Figure 6(b) is displayed on the display 36. At this time, the calculated inserted amount and the length of parking time (valid parking time or extended parking time) are displayed.

Next, in step S6, it is determined whether the ticket issue button 70 has been pressed. If the ticket issue button 70 has not yet been pressed, it is determined in step S7 whether the fare settlement button 74 has been pressed. If the fare settlement button 74 has also not yet been pressed, the process returns to step S2.

After coin insertion begins, steps S2-S7 are repeated until either the ticket issue button 70 or the fee settlement button 74 is pressed. As a result, each time the user inserts coins into the coin insertion slot 50, the total amount of coins inserted by the user from the start of insertion to the current time is calculated as the inserted amount, the parking time corresponding to that amount is calculated from that calculated inserted amount, and the calculated inserted amount and parking time (valid parking time or extended parking time) are displayed on the screen of the display 36.

When the ticket issue button 70 is pressed, in step S8, the parking ticket/receipt issue screen shown in Figure 6(c) is displayed on the display 36. At this time, the parking fee amount confirmed by the user's operation of the ticket issue button 70 is displayed as the prepaid parking fee amount. In this case, the parking time calculated in the preceding step S4 means the valid parking time.

Next, in step S9, actual data that can be directly deciphered by the user, representing the time the user entered the parking lot 10 (or the date and time the user paid the prepaid parking fee, the time the parking ticket 80 was issued, the start time of the parking period, etc.) and the length of the valid parking period (or the amount of the prepaid parking fee paid by the user, etc.), is converted into encrypted data 130 that cannot be deciphered by the user but can be pronounced unambiguously, by referring to the encryption table. Encryption is performed, and encrypted data 130 is created.

In this embodiment, the encrypted data 130 is defined by a string of nine digits (the number of digits may be more or less) as shown in FIG. 11(a). The symbol for each digit is selected, for example, from one of the ten numbers from 0 to 9 or one of several alphabetic characters. The multi-digit symbols are divided into several groups and printed on the receipt 81a, with adjacent groups connected by hyphens. This allows the user to pronounce the multi-digit symbols more easily and accurately, with several breaks between them, rather than having to pronounce them all in one breath.

An example of a typical configuration of actual data (year notation has been omitted to reduce the number of digits in the actual data) is the data shown in Figure 11(b) as follows: "Entered at hh:mm on DD day of MM month, and the valid parking time is TT hours." As shown in Figure 11(c), this actual data has five elements: MM, which represents the month; DD, which represents the day; hh, which represents the hour of the time; mm, which represents the minute of the time; and TT, which represents the length of parking time (if the receipt is for prepayment, this represents valid parking time, but if the receipt is for additional parking fees, this represents extended parking time).

As shown in FIG. 11(c), the encryption tables include a monthly encryption table referenced to encrypt the number MM representing the month, a daily encryption table referenced to encrypt the number DD representing the day, an hourly encryption table referenced to encrypt the number hh representing the hour of the time, a minute encryption table referenced to encrypt the number mm representing the minute of the time, and a time encryption table referenced to encrypt the number TT representing the length of parking time. Each of the five elements described above is encrypted by referencing the corresponding encryption table, thereby creating nine-digit encrypted data 130.

In this embodiment, the encryption table is updated daily, but it is also possible to adopt a method in which the encryption table is updated every time a period longer than 24 hours has passed (the encryption table is not updated within the same period), or a method in which the encryption table is updated every day within a period longer than 24 hours (the pattern of daily updates of the encryption table is common between periods within one period and periods within another period).

In one example, if the encryption table is updated daily in memory 104, the encryption table set, which is one month's worth of encryption tables, is updated monthly. In this case, the encryption table set is updated by the manager, for example, every month when the manager visits the parking lot 10.

In one example, for each of the five elements MM, DD, hh, mm, and TT, the relationship between the actual data and encrypted data in the encryption table, i.e., the correspondence between the number before encryption (e.g., "2" representing "February") and the code after encryption, is generated by generating a random number for each number before encryption and using that random number as the code after encryption.

Once encryption is complete in step S9 shown in Figure 5, the parking ticket 80 and receipt 81a are printed and issued by printer 40 in step S10. As shown in Figure 7(a), the receipt 81a contains the same information regarding at least one of the date and time, amount, and length of parking time related to the payment of the parking fee or the parking time, printed both as actual data that the user can decipher and as encrypted data 130 that the user cannot decipher. This completes the current execution of the ticket issuance and settlement program.

Specifically, as shown in FIG. 7(a), the parking ticket 80 is printed with the end time of the valid parking time equivalent to the amount of the prepaid parking fee paid by the user, as well as a display identifying the location of the parking lot 10. The receipt 81a is also printed with the time of entry, the amount of the prepaid parking fee paid by the user, the end time of the valid parking time, and a display identifying the location of the parking lot 10. The receipt 81a also has encrypted data 130, exemplified by "ABC-DEF-ABC." As shown in text form in FIG. 11(b), this encrypted data 130 is encrypted actual data representing the time of entry (which is equivalent to the time the prepaid parking fee was paid, the start time of the parking time, and the time the parking ticket 80 and receipt 81a were issued) and the length of the valid parking time (which is equivalent to the amount of the prepaid parking fee paid).

In contrast, if the fee settlement button 74 is pressed instead of the ticket issue button 70, the payment receipt issuance screen shown in FIG. 6(d) is displayed on the display 36 in step S11. At this time, the parking fee amount confirmed by the user's operation of the fee settlement button 74 is displayed as the additional parking fee amount. In this case, the parking time calculated in the preceding step S4 means the extended parking time.

Next, in step S12, similar to step S9, the actual data representing the time when the receipt 81b was issued because the user paid the additional parking fee (which is equivalent to the time the additional parking fee was paid) and the length of the extended parking time (which is equivalent to the amount of the additional parking fee paid) is converted into encrypted data 140 by referencing the encryption table.

Then, in step S13, receipt 81b is printed and issued by printer 40. As shown in Figure 7(b), receipt 81b contains the same information regarding at least one of the date and time, amount, and length of parking time related to the payment of the parking fee or the parking time, printed both as actual data that the user can decipher and as encrypted data 140 that the user cannot decipher. This completes the current execution of the ticket issuance and settlement program.

Specifically, as shown in Figure 7(b), the receipt 81b is printed with the date and time the receipt 81b was issued, the amount of the additional parking fee, and an indication to identify the location of the parking lot 10.

In addition, receipt 81b also includes encrypted data 140, for example, "123-456-789." This encrypted data 140 is encrypted actual data indicating the date and time receipt 81b was issued and the length of the extended parking time.

Figure 7(a) shows a front view of a set of two parking tickets, parking ticket 80 and receipt 81a, while Figure 7(b) shows a front view of receipt 81b. The set of two parking tickets, parking ticket 80 and receipt 81a, corresponds to two parking tickets 80, and in this set, parking ticket 80 and receipt 81a have the same size and structure. Receipt 81b corresponds to one parking ticket 80, and has the same size and structure as parking ticket 80. For simplicity's sake, only the structure of parking ticket 80 will be described below as a representative example.

The parking ticket 80 is composed of a display sheet (printing paper) 82 as the surface layer, an adhesive layer 83 (glue layer) as the middle layer, and a separator (separation sheet, release paper) 84 as the back layer, layered in that order. The adhesive layer 83 is applied to the back surface of the display sheet 82 so that it does not easily peel off; when the display sheet 82 is peeled off from the surface of the separator 84, the glue of the adhesive layer 83 does not adhere to the surface of the separator 84.

As shown in Figure 7(a), in one parking ticket 80, the outer periphery of the display sheet 82 is positioned inside the outer periphery of the separator 84. The raw sheet wound around the roller 42 is composed of a continuous separator 84 to which multiple display sheets 82 (blank) are adhered, spaced apart and arranged in a row.

The continuous sheet (continuous separator 84) in the printer 40 is cut by the cutter at the gaps between the display sheets 82, and the display sheets 82 are not cut. On the other hand, no adhesive is attached to the surface of the separator 84 that is exposed in the gaps between the display sheets 82.

Accordingly, according to this embodiment, the adhesive layer 83 does not adhere to the cutting blade when cutting the continuous sheet, reducing the frequency of cutter maintenance by managers (e.g., service personnel, workers who patrol multiple parking lots, or patrol watchmen) who are dispatched to the site once or several times a day, thereby reducing labor costs for managers.

However, in this embodiment, for receipt 81b, the separator 84 is completely cut by the cutter to the length of one sheet, whereas for the two-sheet set, the separator 84 is completely cut to the length of two sheets. However, as mentioned above, for the two-sheet set, as shown in Figure 7(a), the separator 84 is partially cut by the cutter between the parking ticket 80 and the receipt 81a, thereby forming a cut line 89.

As shown in Figure 7(a), the display sheet 82 of the parking ticket 80 further includes a cut line 90 (open) with both ends just above the characters "Parking Ticket." This cut line 90 exists so that a user can peel a portion of the display sheet 82 from the separator 84 while leaving the remaining portion adhered to the separator 84. As shown in Figure 8(b), when a user peels a portion of the display sheet 82 (the area surrounded by the cut line 90) from the separator 84 and folds it along the straight line connecting both ends of the cut line 90, the surface of the resulting folded portion 92 (the portion of the adhesive layer 83 applied to the back surface of the folded portion 92) is exposed as an adhesive surface. Figure 9(a) shows the folded portion 92 in a perspective view.

In this embodiment, to prove that the user's parking is not illegal, the user is required to attach the parking ticket 80 received in exchange for inserting a coin to the back of the windshield 110 of the parked vehicle, as shown in FIG. 9(b). To do this, the user locally peels off and folds a designated portion of the parking ticket 80 (the area surrounded by the cutting line 90 that will eventually become the folded portion 92), as shown in FIG. 9(a), and then attaches the surface of the folded portion 92 to the back of the windshield 110 of the parked vehicle, as shown in FIG. 9(b). This allows the contents of the parking ticket 80 (particularly, information specifying the end time of the user's permitted parking time slot and an indication specifying the location in the parking lot 10 where the parking ticket 80 is valid) to be visually inspected from the outside at any time, as shown in FIG. 10.

If the actual parking time exceeds the valid parking time, the user is required to pay an additional parking fee. However, as mentioned above, the parking lot 10 is unmanned and does not have a device that prevents a parked vehicle from leaving unless the required additional parking fee is paid. Therefore, as shown in Figure 12, the user is required to notify the parking lot manager at a remote management center that the required additional parking fee has been paid using a communication device such as a mobile phone or landline phone from the parking lot 10, their car, or their home.

At this time, the user is required to read out loud both the encrypted data 130 printed on the receipt 81a issued upon entry and the encrypted data 140 printed on the receipt 81b issued upon exit, and transmit this audio to the parking lot manager via the communication device.

Upon receiving the user's voice representing the encrypted data 130, 140, the parking lot manager at the management center operates the input device (e.g., keyboard, touch screen, mouse, etc.) of the decryptor 180 to input the symbols corresponding to the user's voice. The encrypted data 130, 140 is then input, and the decryptor 180 restores the input encrypted data 130, 140 to the actual data according to a decryption table that matches the encryption table and is installed in the decryptor 180.

This allows the parking lot manager, while at the management center, which is geographically distant from the parking lot 10 under management, to know the actual parking time, which is the time the user actually parked (e.g., the length of time elapsed from the time of entry specified by encrypted data 130 to the time the additional parking fee was paid specified by encrypted data 140), and further, the total amount of parking fees paid by the user (e.g., the sum of the amount of prepaid parking fee specified by encrypted data 130 and the amount of additional parking fee specified by encrypted data 140), and ultimately allows the manager to correctly determine whether the total amount of parking fees is sufficient in relation to the actual parking time.

The decryption table stored in the decryptor 180 cannot be accessed by anyone, even the parking lot manager, unless authorized to do so, providing high security for the decryption table.

As is clear from the above explanation, according to this embodiment, when receipts 81a and 81b are issued, encrypted data 130, 140 are printed on each receipt 81a and 81b using symbols that the user can pronounce. Furthermore, by simply requesting the user to transmit the encrypted data 130, 140 aloud to the parking lot manager, the parking lot manager can correctly determine whether the parking fee is insufficient. This allows users to safely park beyond the valid parking time without imposing a significant burden, improving the usability of parking lot 10 and ultimately its utilization rate.

It should be noted that in this embodiment, the user transmits the encrypted data 130 and 140 by voice input, but it is also possible to transmit the encrypted data 130 and 140 by data input (e.g., key input using real or virtual keys, or image input using an image reader) instead of voice input.

We've explained regular parking above, but next we'll explain cardless parking.

As is clear from the above explanation, in this embodiment, neither the parking lot 10 nor the ticket issuing machine 20 has any equipment for detecting the fact that each user has entered or exited the parking lot 10. Furthermore, in the case of cardless parking, as will be described in detail later, the user uses their own communication device (e.g., a mobile phone or smartphone) to send a message to the parking lot manager requesting that parking begin using their electronic parking ticket. However, neither the parking lot 10 nor the ticket issuing machine 20 can detect that the user is actually parking in the parking lot 10 at that time. Furthermore, unless the user simply uses their own communication device, for example, by using the GPS function of that communication device, it cannot detect that the user has actually entered the parking lot 10.

In contrast, in this embodiment, the ticket dispenser 20 is designed to use the current time measured by the clock 102 as real data, as shown in Figure 13(b), encrypt this real data using a time encryption table (stored in the memory 104 of the ticket dispenser 20), thereby obtaining a time code 190 as encrypted data. This time code 190 cannot be deciphered by the user but can be deciphered by the parking lot manager (for example, similar to encryption codes 130 and 140, it cannot be deciphered by the user but can be pronounced unambiguously).

In one example, as shown in Figure 13(c), the time code 190 is updated discretely, i.e., at set time intervals (e.g., 15 minutes).

The ticket issuing machine 20 is further designed to display the time code 190 on the screen of the display 36 in a manner that is updated sequentially over time, as shown in Figure 13(a).

The ticket issuing machine 20 is further designed to display, on the screen of the display 36, a location code 192 unique to the parking lot 10, which allows the location of the parking lot 10 to be identified, together with a time code 190, as shown in FIG. 13(a).

Figure 14 conceptually shows a flowchart of a code display program executed by the computer 100 of the ticket dispenser 20 to display the time code 190 and location code 192. This code display program is executed repeatedly while the ticket dispenser 20 is in operation.

When this code display program is executed each time, first, in step S31, the current time is measured by the clock 102. Next, in step S32, the measured current time is encrypted into a time code 190 by referencing the time encryption table. Next, in step S33, the generated time code 190 and the location code 192 stored in memory 104 are displayed on the screen of the display 36. This completes the current execution of this code display program.

By repeatedly executing this code display program, the time code 190 and location code 192 are always displayed on the screen of the display 36, as illustrated in Figure 13(a), in a position that does not obscure any messages displayed on the same screen, as illustrated in Figure 6.

Here, to explain the time code 190 in more detail, the time code 190 is generated differently at different times within the same day, and is therefore time-dependent.

Furthermore, because the time code 190 is generated so that it cannot be deciphered by any user of the parking lot 10, even if a user attempts to impersonate a user who entered or exited the parking lot 10 at a certain time, even though the user did not actually enter or exit the parking lot 10 at that time, or even though the user actually entered or exited the parking lot 10 at a different time, and tries to guess the time code 190 that should be displayed on the display 36 at that certain time, the user will not be able to obtain the authentic time code 190. Therefore, the time code 190 is also confidential to the user.

Furthermore, the time code 190 is only displayed on the display 36 of the parking lot 10 where the user is actually attempting to park or has parked, so the user must go to the parking lot 10 in person to obtain the required time code 190. Thus, the time code 190 is location-dependent.

In this way, the time code 190 is time-dependent, confidential to the user, and location-dependent. Therefore, as long as the user transmits the time code 190 that they actually saw in the parking lot 10 to the management server 202 at a time that is not significantly later than the time it was displayed on the display 36 (within a set tolerance range), that time code 190 will be strong evidence to support the fact that the user actually entered or exited the parking lot 10.

Now, to explain the time encryption table in more detail, the time encryption table is updated periodically, for example, daily, just like the encryption table shown in Figure 11. This increases the likelihood that the time code 190 will be different even if the time is the same on a different date, thereby preventing the misuse of the time code 190.

In an exemplary scenario in which the same parking lot manager manages multiple parking lots (including parking lot 10) and time codes 190 are displayed at each of those parking lots, it is desirable that time codes 190 be generated so that they are different for different parking lot locations even at the same time. In this desirable aspect, time codes 190 displayed at parking lot 10 have location-identifying power.

Here, the term "location identification ability" may be defined to mean only that the time code 190 differs depending on the location, and not that the location can be uniquely identified from the time code 190, or it may be defined to mean not only that the time code 190 differs depending on the location, but also that the location can be uniquely identified from the time code 190.

However, in this embodiment, the time code 190 does not need to have location identification capability, so that the management server 202 can identify the location of the parking lot 10 that the user is using from the information received from the user. This is because, in this embodiment, the location code 192, which has location identification capability, is also displayed to the user in the parking lot 10 along with the time code 190.

Therefore, the correct time code 190 for the parking lot 10 the user is about to use cannot be obtained unless the user is actually present in that parking lot 10 and observes the screen of the display 36. Therefore, if the user transmits the observed time code 190 together with the location code 192 to a parking lot manager in a remote location when entering the parking lot, the parking lot manager will be able to estimate which parking lot 10 the user entered and at what time.

Specifically, the time code 190 and location code 192 are communicated by the user to the parking lot manager via the user's communication device when the user enters the parking lot. Upon receiving the time code 190 and location code 192, the parking lot manager converts the time code 190 into actual data, the current time, by referencing a decryption table 234 (see FIG. 15) that matches the time encryption table. By using the received location code 192, the parking lot manager can infer that the user has actually entered the parking lot 10 identified by the location code 192.

Furthermore, if the difference between the current time obtained by decrypting the time code 190 (e.g., the observation time when the user observes the display 36) and the current time measured by the parking lot manager (the reception time when the parking lot manager receives the time code 190) is within a set tolerance range (e.g., 30 minutes), the parking lot manager can infer that the user actually entered the parking lot 10 (started parking in the parking lot 10) at some time between the current time obtained by decrypting the time code 190 (the earliest time within a time range, if there is one, as illustrated in Figure 13(c)) and the current time measured by the parking lot manager.

In contrast, if the parking lot manager is unable to successfully decrypt the received time code 190, or if the parking lot manager successfully decrypts it but determines that the difference between the current time obtained thereby and the current time measured by the parking lot manager exceeds the set tolerance range, the time code 190 sent by the user to the parking lot manager will not exist as time code 190 in the ticket issuing machine 20, or even if it does exist, the time when the user sent the time code 190 to the parking lot manager will be significantly later than the time when the user observed the time code 190 on the display 36, and the parking lot manager will deny the user parking using the electronic parking ticket even if it is valid.

In addition, if the length of the settable allowable time is set long, the time gap between the time the user observes the time code 190 on the display 36 and the time that time code 190 is transmitted to the parking lot manager can be somewhat long. This increases the range of transmission times that the user can choose, which in turn brings about the following advantages:

For example, a user may park their vehicle in a parking lot 10, memorize the time code 190 displayed on the display 36 when they are about to walk out of the parking lot 10, and then, if they walk from the parking lot 10 to the nearest station or the like and need to use public transportation such as a train or bus, they may remember the time code 190 after boarding the public transportation and send it to the parking lot manager.

This reduces the time and mental burden on the user compared to when the parking lot 10 is constantly required to send the time code 190 to the parking lot manager regardless of whether the user has enough time or not, and ultimately improves the usability of the parking lot 10.

The above provides a detailed explanation of the distinctive elements of the ticket issuing machine 20 that enable cardless parking. Below, we will explain the details of the service that issues electronic parking tickets to users by referring to Figures 15 to 27.

This service is provided by the management server 202 in the system 200 shown in Figure 15, which implements an exemplary parking lot management method according to this embodiment.

In system 200, multiple users and multiple staff members who work under the instructions of the parking lot manager (each staff member is tasked with patrolling and monitoring parking lot 10 and multiple other parking lots managed by the parking lot manager several times a day) are communicatively connected to management server 202 via the Internet 204, an example of a global communications network, wirelessly or via a wired connection.

To perform transmission and reception, the management server 202 has a transmitting unit 210 that transmits signals or data to external destinations, and a receiving unit 212 that receives signals or data from external sources.

The management server 202 further includes a processor 220 and storage 222 (e.g., ROM, RAM). In order to provide the above-mentioned services, the processor 220 executes an electronic parking ticket processing program, which is illustratively and conceptually represented in the flowcharts of Figures 16 to 18, and performs various processes. The storage 222 temporarily or permanently stores the electronic parking ticket processing program and data.

The management server 202 further includes a member database (hereinafter referred to as "DB" throughout the figures) 230, an example of which is shown in Figure 19, an electronic parking ticket database (hereinafter referred to as "DB" throughout the figures) 232, an example of which is shown in Figure 20, and the decryption table 234.

Note that, although not shown, the management server 202, like the ticket issuing machine 20, either has an internal clock that measures the current time, or is able to use the measurement results of an external clock.

To briefly explain the content of this service, in response to a user's request for issuance, management server 200 issues an electronic parking ticket 250, as illustrated in FIG. 21, to the user, provided the user prepays a specified parking fee. When the user plans to park in parking lot 10 using the issued electronic parking ticket 250, the user sends a parking permit request and the time code 190 displayed on display 36 upon entry into parking lot 10 to management server 202. Management server 202 then decodes the received time code 190 by referencing decryption table 234. Based on the decryption results, management server 202 determines whether the entry time represented by the received time code 190 is within a predetermined tolerance range determined for the time at which management server 202 received the time code 190, thereby determining whether the received time code 190 is valid.

If the received time code 190 is determined to be valid, the management server 202 permits the user to use the parking lot 10 and sends a parking permission message indicating this to the user.

[Member Registration]

More specifically, this service involves, in order, a process of registering the user as a member to obtain eligibility to use the electronic parking ticket 250, a process of issuing the electronic parking ticket 250 to the user, a process of allowing the user to use the electronic parking ticket 250 at the start of parking, and, if the user extends parking, a process of paying and settling the additional parking fee corresponding to the length of the extended parking time via electronic payment at the end of parking.

To explain more specifically, in this service, a user first accesses the management server 202 and registers as a member, as illustrated in the sequence diagram in Figure 22. When the user sends the user information required for member registration to the management server 202, the management server 202 registers the received user information for each user in the member DB 230, illustrated in Figure 19.

[Issuance of electronic parking tickets]

Next, the user accesses the management server 202 to request the issuance of an electronic parking ticket 250 from the parking lot manager, as illustrated in the sequence diagram of FIG. 23. The user then transmits their user ID and PIN to the management server 202, which then performs personal authentication. The user then transmits the number of points they wish to earn to the management server 202, and the management server 202 calculates the fee required to earn those points. Once the user pays the fee, the management server 202 assigns a unique ticket number to the electronic parking ticket 250 to be issued, and further assigns the number of valid points, and registers this information in the electronic parking ticket DB 232, as illustrated in FIG. 20. The management server 202 then issues the electronic parking ticket 250, as illustrated in FIG. 21, to the user.

[Electronic Parking Ticket Use Permission]

Then, when entering the parking lot 10, the user accesses the management server 202 to begin parking in the parking lot 10 using the issued electronic parking ticket 250, as illustrated in the sequence diagram of FIG. 24. The user then transmits the unique ticket number assigned to the electronic parking ticket 250 they wish to use to the management server 202, and the management server 202 confirms the validity of the electronic parking ticket 250. The user then transmits the time code 190 and location code 192 displayed on the display 36 to the management server 202. The management server 202 estimates the user's entry time by decrypting the received time code 190 and confirms the validity of the estimated entry time by comparing it with the current time measured by the management server 202.

The user then sends the parking conditions to the management server 202. The parking conditions include the length of time the user wishes to park in the parking lot 10. The management server 202 then calculates the number of points used to allow the user that parking time. The management server 202 then calculates the number of remaining points by subtracting the number of points used from the current number of valid points, and if it confirms that the number of remaining points is not 0, it calculates the length of valid parking time allowed to the user. The management server 202 then issues a receipt 260, an example of which is shown in Figure 25, and sends it to the user.

In this embodiment, the user is required to specify the planned exit time (equivalent to the length of the planned parking time) when entering the parking lot, and considering that the number of valid points is then deducted, this parking can be considered to be classified as prepaid parking. Furthermore, as shown in FIG. 25, receipt 260 lists the length of valid parking time permitted to the user, along with the end time of that valid parking time. Therefore, by looking at receipt 260, the user can know by what time they must exit the parking lot.

As shown at the bottom of Figure 24, the fact that the user has been granted permission to park is not only communicated to the user himself, but also to the multiple personnel mentioned above. The personnel may be contacted by the management server 202 individually sending an email containing information about the parking permission to each personnel (active contact), or by posting information about the parking permission on a homepage of the management server 202 that is accessible only to a limited number of people (a homepage for dealers), and the personnel may individually access the homepage and communicate the information about the parking permission to the personnel (passive contact).

[Settlement of additional fees for extended parking]

If the actual length of continuous parking time by the user exceeds the above-mentioned valid parking time (the continuous parking time permitted to the user upon entry in exchange for consuming the usage points), i.e., if extended parking is performed, the user will access the management server 202 upon leaving the parking lot 10, as illustrated in the sequence diagram in Figure 26.

The user then transmits the unique ticket number assigned to the electronic parking ticket 250 used this time to the management server 202, and the management server 202 confirms the validity of the electronic parking ticket 250. Next, the user transmits the time code 190 and location code 192 displayed on the display 36 to the management server 202. The management server 202 estimates the user's departure time by decrypting the received time code 190, and confirms the validity of the estimated departure time by comparing it with the current time measured by the management server 202.

Then, the management server 202 calculates the length of extended parking time as the length of time elapsed from the end time of the valid parking time recorded in the electronic parking ticket DB 232 to the estimated departure time, and then calculates an additional parking fee equivalent to the length of the extended parking time. The management server 202 then calculates the number of points used equivalent to the amount of the additional parking fee, and calculates the number of remaining points by subtracting the number of points used from the current number of valid points. The management server 202 then issues a settlement receipt (not shown) and sends it to the user.

Next, the contents of the electronic parking ticket processing program will be explained in more detail with reference to Figures 16 to 18. This electronic parking ticket processing program is repeatedly executed by the processor 220 of the management server 202.

The electronic parking ticket processing program is configured to include a first subprogram shown in FIG. 16, a second subprogram shown in FIG. 17, and a third subprogram shown in FIG. 18. The first subprogram is for member registration and issuing electronic parking tickets, the second subprogram is for granting permission to use the electronic parking ticket, and the third subprogram is for settling parking fees when parking for extended periods.

[Member Registration]

When this electronic parking ticket processing program is executed each time, first, in step S101 of FIG. 16, it is determined whether the user who has logged in to the management server 202 has sent a membership registration request to the management server 202. Assuming that the user has sent a membership registration request this time, the determination in step S101 is YES, and in step S102, the user information of the user (e.g., the user's name, address, email address, etc.) sent from the user's communication device is received via the receiving unit 212.

Next, in step S103, a unique user ID is assigned to the current user. Then, in step S104, the PIN number set by the user himself/herself is transmitted from the user's communication device and received via the receiving unit 212. In this step S104, other user information additionally transmitted from the user's communication device (for example, as illustrated in FIG. 19, the vehicle number, model name, body color, etc. of the vehicle the user plans to park) is also received via the receiving unit 212.

Next, in step S105 of FIG. 16, user information about the current user is registered in the member DB 230, thereby registering the current user as a member. After that, in step S106, a registration completion message indicating that member registration for the current user has been completed is returned to the user via the transmission unit 210. This completes the current execution of the electronic parking ticket processing program.

[Issuance of electronic parking tickets]

The above describes a scenario in which management server 202 receives a membership registration request from a user. However, in an alternative scenario in which management server 202 receives an electronic parking ticket issuance request, the determination in step S101 will be NO and the determination in step S107 will be YES, and the process will proceed to step S108.

In step S108, the user's user ID and PIN sent from the user's communication device are compared with the member DB 230 to determine whether the current user is a member, i.e., whether the user is eligible to receive this service. In other words, personal authentication is performed, and if this personal authentication is successful, in step S109, data sent from the user's communication device indicating the number of points the user wishes to earn this time is received via the receiving unit 212.

Then, in step S110, the fee (prepaid fee) that the user must pay to the parking lot manager in order to acquire the number of points the user desires is calculated by referencing a fee table or function formula that represents a predetermined relationship between the number of points and the fee. Next, in step S111, data representing the fee that the user must pay is transmitted to the user. Then, in step S112, the user makes an electronic payment to the parking lot manager.

Next, in step S113, it is determined whether the electronic payment was completed successfully. If the user's electronic payment was not completed successfully, the determination in step S113 is NO, and in step S113a, an issuance denial message indicating that issuance of the electronic parking ticket 250 is not permitted is returned to the user. This concludes the current execution of the electronic parking ticket processing program.

In contrast, assuming that the user's electronic payment has been completed successfully this time, the determination in step S113 is YES, and in step S114, a unique ticket number is assigned to the electronic parking ticket 250 to be issued to the current user. The assigned ticket number is associated with the user ID and registered in the electronic parking ticket DB 232, as shown in FIG. 20. Next, in step S115 of FIG. 16, valid points are assigned to the current user. The assigned valid points are associated with the user ID and registered in the electronic parking ticket DB 232 in step S116, as shown in FIG. 20.

Then, in step S117 of FIG. 16, as illustrated in FIG. 21, an electronic parking ticket 250 is issued to the current user, and data representing the electronic parking ticket 250 is transmitted from the transmission unit 210 to the current user's communication device. This completes the current execution of the electronic parking ticket processing program.

[Electronic Parking Ticket Use Permission]

The above describes a scenario in which the management server 202 receives a request to issue an electronic parking ticket from a user. However, in an alternative scenario in which the management server 202 receives a request to use an electronic parking ticket, the determinations at steps S101 and S107 in Figure 16 are both NO, and the determination at step S118 in Figure 17 is YES, and the process proceeds to step S119.

In step S119, similar to step S108 in FIG. 16, personal authentication is performed based on the user's user ID and PIN number transmitted from the user's communication device. If this personal authentication is successful, in step S120, a single ticket number transmitted from the user's communication device, which is data for identifying the electronic parking ticket 250 that the user wishes to use, is received via the receiving unit 212.

Then, in step S121, the received ticket number for the current user is compared with the electronic parking ticket DB 232 to determine whether the electronic parking ticket 250 that the current user wishes to use is valid. If the current electronic parking ticket 250 is not valid, in step S122, a usage denial message indicating that usage of the electronic parking ticket 250 is not permitted is returned to the user's communication device. This completes the current execution of the electronic parking ticket processing program.

In contrast, assuming that the electronic parking ticket 250 that the user wishes to use is valid, in step S123, the time code 190 and location code 192 transmitted from the user's communication device are received via the receiver 212. Next, in step S124, the received time code 190 is decrypted by referring to the decryption table 234. Then, in step S125, the user's entry time is estimated based on the decryption results. Next, in step S126, it is determined whether the estimated entry time is within a predetermined tolerance range determined for the reception time when the management server 202 received the time code 190, and thereby whether the received time code 190 is valid.

Assuming that the received time code 190 is not valid this time, the determination in step S126 is NO, and in step S122, a usage denial message indicating that the user is not permitted to use the electronic parking ticket 250 (to park in parking lot 10) is sent to the user's communication device.

In contrast, assuming that the received time code 190 is valid this time, the determination in step S126 is YES, and in step S127, the user's desired parking conditions are received from the user's communication device. These desired parking conditions include, for example, the length of time the user wants to park.

Next, in step S128, the number of points to be used to realize the received desired parking conditions is calculated. The number of points to be used is calculated, for example, by referring to a predetermined conversion table so that the number of points to be used increases according to the length of time the user desires free parking. Then, in step S129, the number of valid points is updated by subtracting the calculated number of points to be used this time from the current value of the number of valid points. The update to the number of valid points is reflected in the electronic parking ticket DB232.

Next, in step S130, the valid parking time, which is the length of parking time permitted to the user in exchange for consuming the above-mentioned number of points, is calculated based on the received data representing the desired parking conditions. Then, in step S130a, a receipt 260, as shown in FIG. 25, is issued to inform the user that parking using the electronic parking ticket 250 is permitted. Data representing the issued receipt 260 is sent to the user's communication device.

Next, in step S131, processing is performed to communicate the received desired parking conditions to all staff members (for example, the desired parking conditions are communicated to each staff member individually by email, or by posting the desired parking conditions on the company's dedicated homepage). This completes the current execution of the electronic parking ticket processing program.

[Parking fee settlement for extended parking]

The above describes a scenario in which management server 202 receives a request to use an electronic parking ticket from a user. However, in an alternative scenario in which management server 202 receives a request to settle for extended parking, the judgments of steps S101 and S107 in Figure 16 are both NO, the judgment of step S118 in Figure 17 is NO, and step S132 in Figure 18 is YES, and the process proceeds to step S133.

The execution contents of steps S133 to S138 are the same as those of steps S119 to S124 shown in Figure 17, so duplicate explanations will be omitted.

In step S139 of FIG. 18, the user's departure time is estimated based on the results of decoding the time code 190 transmitted from the user's communication device in step S137. Next, in step S140, it is determined whether the estimated departure time is within a predetermined tolerance range determined for the reception time at which the management server 202 received the time code 190, thereby determining whether the received time code 190 is valid.

Assuming that the received time code 190 is not valid this time, the determination in step S140 is NO, and in step S136, a usage denial message indicating that the user is not permitted to use the electronic parking ticket 250 (to park in the parking lot 10) is sent to the user's communication device.

In contrast, assuming that the received time code 190 is valid this time, the determination in step S140 is YES, and in step S141, the length of the extended parking time is calculated by subtracting the end time of the valid parking time recorded in the electronic parking ticket DB 232 from the estimated exit time. The estimated exit time is recorded in the electronic parking ticket DB 232, as shown in the example in FIG. 20.

Next, in step S142, an additional parking fee corresponding to the calculated extended parking time is calculated by referencing a predetermined conversion table. Then, in step S143, the number of points used corresponding to the calculated additional parking fee is calculated. Then, in step S144, the number of remaining points is calculated by subtracting the calculated number of points used from the current number of valid points. The number of remaining points is reflected in the electronic parking ticket DB 232. The electronic parking ticket DB 232 also records data indicating that the user has paid the additional parking fee by partially consuming the valid points, as shown in FIG. 20. Then, in step S145, a payment receipt (not shown) indicating that the additional parking fee has been paid by the user is issued, and data representing the payment receipt is sent to the user's communication device.

Next, in step S146, processing similar to step S131 in Figure 17 is performed to notify all staff members that the additional parking fee has been paid by the user. This completes the current execution of the electronic parking ticket processing program.

[Automatically send shipping reminder messages]

In this embodiment, as described above, for each user parking using an electronic parking ticket 250, the management server 202 knows both the entry time and the scheduled exit time calculated from the entry time and the valid parking time at the time of entry. Therefore, as shown in FIG. 27, in this embodiment, the management server 202 is designed to send individual messages by email to the user's communication device to notify the user parking using an electronic parking ticket 250 that the scheduled exit time is approaching, to warn the user that the scheduled exit time has passed, and to remind the user that they must pay for extended parking if the scheduled exit time has passed.

Specifically, as shown in FIG. 27, the management server 202 calculates the scheduled exit time (end time of valid parking time) for each user by referencing the data in the electronic parking ticket DB 232, and further calculates the exit reminder time to be a set time (e.g., one hour) earlier than the scheduled exit time. When the exit reminder time arrives, the management server 202 creates an exit reminder message that includes a statement that "less than one hour remains until the scheduled exit time," and sends the exit reminder message by email to the communication device of the corresponding user.

The exit reminder message may also include, for example, a statement that "if the scheduled exit time has passed, the user will need to access the management server and settle any additional parking fees upon exiting." This alerts the user not to forget to access the management server 202 and settle any additional parking fees upon exiting if the scheduled exit time has passed.

Furthermore, management server 202 determines for each user whether the scheduled exit time has arrived, and if so, by referencing electronic parking ticket DB 232, determines whether the user has paid the additional parking fee. If the additional parking fee has not been paid, management server 202 includes a statement that "the scheduled exit time has passed" and a statement that "when leaving the parking lot, the user must access the management server to pay the additional parking fee." Management server 202 sends the exit reminder message by email to the communication device of the corresponding user. Management server 202 repeatedly sends the same exit reminder message to the user who sent the exit reminder message every time a set time (e.g., one hour) has elapsed, until the user accesses management server 202 and pays the additional parking fee.

It should be noted that in this embodiment, both regular parking and cardless parking are possible in the same parking lot 10. For this reason, the ticket dispenser 20 is designed to have not only its original ticket issuing function but also a time code generation and display function that generates a time code 190 by encryption and displays it on the screen of the display 36. However, the present invention can also be implemented in an embodiment where only cardless parking is possible in the same parking lot 10, and instead of the ticket dispenser 20, a time code generation and display device is installed in the parking lot 10 that includes at least a clock 102, an encryption device that encrypts the current time measured by the clock (e.g., a computer that executes a program that references the time encryption table to generate the time code 190), and a display 36 that displays the time code 190 generated by encryption.

As is clear from the above explanation, in this embodiment, for the sake of convenience, the clock 102 constitutes an example of the "clock" in section (1) above, the portion of the control board 34 that executes step S32 shown in FIG. 14 constitutes an example of the "encryption unit" in the same section, the display 36 constitutes an example of the "display unit" in the same section, the portion of the ticket dispenser 20 that generates and displays the time code 190 constitutes an example of the "parking lot time code generation and display device" in the same section, and the display 36 can be considered to constitute an example of the "display unit" in section (2) above and an example of the "parking lot time code display device" in section (5) above.

Furthermore, in this embodiment, for the sake of convenience, steps S120 and S123 shown in FIG. 17 constitute an example of the "entry time reception process" in paragraph (1) or (2) above, steps S124 to S126 shown in the same figure constitute an example of the "entry time validity determination process" in the same paragraph, step S130a shown in the same figure constitutes an example of the "parking permission process" in the same paragraph, and the transmitter 210 and receiver 212 can be considered to cooperate with each other and constitute an example of the "communication unit" in the same paragraph.

Furthermore, in this embodiment, for the sake of convenience, steps S134 and S137 shown in Figure 18 constitute an example of the "receiving process at the time of leaving" in section (3) above, steps S138 to S140 shown in the same figure constitute an example of the "departure time validity determination process" in the same section, and step S141 shown in the same figure constitutes an example of the "parking time calculation process" in the same section.

Furthermore, in this embodiment, for the sake of convenience, step S107 shown in Figure 16 constitutes an example of the "issuance request receiving process" in section (4) above, and steps S110 to S117 shown in the same figure can be considered to constitute an example of the "electronic parking ticket issuing process" in the same section.

<Second embodiment>

Next, we will explain a parking lot management method according to an exemplary second embodiment of the present invention. However, elements that are common to the first embodiment will be referred to using the same symbols or names, and duplicate explanations will be omitted, and only the different elements will be explained in detail.

In the first embodiment, a user who wishes to use cardless parking specifies the length of the planned parking time they wish to use prior to parking (when entering the parking lot 10) each time they intend to park, and consumes a number of available points equivalent to the prepaid parking fee corresponding to the length of the planned parking time. When the user leaves the parking lot 10 before the planned parking time has elapsed, i.e., if they are not extending their parking, there is no need to access the management server 202 when leaving. In other words, unless they are extending their parking, the user does not need to access the management server 202 when leaving. As a result, unless they are extending their parking, the user only needs to communicate with the management server 202 when entering the parking lot, eliminating the need for the user to do any extra work.

However, in the first embodiment, even if the user's actual parking time is shorter than the planned parking time, the same number of points will be consumed as if the user had parked for the same amount of time as the planned parking time.

In contrast, in this embodiment, the user has to access the management server 202 not only when entering but also when leaving the parking lot, which requires additional effort on the part of the user. However, points are not consumed when entering the parking lot, and instead the parking time is calculated and points are consumed all at once when leaving the parking lot. As a result, the number of points consumed is calculated to exactly match the actual parking time. As a result, this embodiment saves the user from wasting points, making it more economical.

Next, the parking lot management method according to this embodiment will be described with reference to Figures 28 to 33. The electronic parking ticket processing program executed in the management server 202 to execute this method includes the same first subprogram (membership registration and issuance of electronic parking ticket 250) as shown in Figure 16, a fourth subprogram that replaces the second subprogram (permission to use electronic parking ticket 250) shown in Figure 17, and a fifth subprogram that replaces the third subprogram (settlement of additional parking fees when parking for extended periods) shown in Figure 18.

The fourth subprogram is executed by the management server 202 to permit the start of parking using the electronic parking ticket 250, and is conceptually represented in a flowchart in FIG. 28. The fifth subprogram is executed by the management server 202 to allow the user to settle the parking fee by consuming points at the end of parking using the electronic parking ticket 250, and is conceptually represented in a flowchart in FIG. 29.

The electronic parking ticket processing program for this embodiment will be explained below, but duplicate explanations of processes common to the first embodiment will be omitted, and only the different processes will be explained in detail.

[Parking permission using an electronic parking ticket]

When entering parking lot 10, the user accesses management server 202 to request permission to park using electronic parking ticket 250 from the parking lot manager, as illustrated in the sequence diagram of Figure 30. The user then transmits the ticket number assigned to the electronic parking ticket 250 they wish to use to management server 202, and management server 202 confirms the validity of the electronic parking ticket 250. Next, the user transmits the time code 190 and location code 192 displayed on display 36 to management server 202. Management server 202 estimates the user's entry time by decrypting the received time code 190, and compares this with the current time measured by management server 202 to confirm the validity of the estimated entry time.

If the estimated entry time is valid, the management server 202 permits the user to park and sends a parking permission message to the user. Similar to the first embodiment, the management server 202 notifies not only the user but also the aforementioned multiple responsible persons that the user has been permitted to park.

To execute this process, the management server 202 executes the fourth subprogram shown in FIG. 28. When this fourth subprogram is executed, first, in step S301, it is determined whether a parking permit request has been received from the user's communication device. In this case, assuming that a parking permit request has been received, the determination in step S301 is YES, and steps S119 to S126 are executed in the same manner as in the first embodiment.

If, in step S126, it is determined that the entry time estimated by decrypting the time code 190 currently received from the user is valid, in step S302, a parking permission message indicating that the user has been permitted to park is returned to the user's communication device. Then, in step S303, information indicating that the user has been permitted to park in parking lot 10 is communicated to all staff members. This concludes the current execution of this fourth subprogram.

[Paying parking fees when using an electronic parking ticket]

When the user leaves the parking lot 10, the user accesses the management server 202 to settle the parking fee, as illustrated in the sequence diagram in Figure 31. The user then transmits the ticket number assigned to the electronic parking ticket 250 used this time to the management server 202, and the management server 202 confirms the validity of the electronic parking ticket 250. The user then transmits the time code 190 and location code 192 displayed on the display 36 to the management server 202. The management server 202 estimates the user's departure time by decrypting the received time code 190, and confirms the validity of the estimated departure time by comparing it with the current time measured by the management server 202.

Then, in step S402 shown in FIG. 29, the management server 202 calculates the length of parking time by subtracting the entry time recorded in the electronic parking ticket DB 232 from the estimated exit time. The estimated exit time is recorded in the electronic parking ticket DM 232, as shown in the example in FIG. 20.

Next, in step S403, a parking fee corresponding to the calculated length of parking time is calculated by referencing a predetermined conversion table. Then, in step S404, the number of points used corresponding to the calculated parking fee is calculated. Next, in step S405, the number of remaining points is calculated by subtracting the calculated number of points used from the current number of valid points. The number of remaining points is reflected in the electronic parking ticket DB 232. The electronic parking ticket DB 232 also records data indicating that the user has paid the parking fee by partially consuming the valid points, as shown in FIG. 20. Then, in step S406, a receipt 270 indicating that the parking fee has been paid by the user is issued, and data representing the receipt 270 is sent to the user's communication device.

Next, in step S407, processing is performed to notify all staff members that the parking fee has been paid by the user. This completes the current execution of this fifth subprogram.

[Automatically send shipping reminder messages]

In this embodiment, as described above, the management server 202 knows the entry time of a user who parks using an electronic parking ticket 250 at the time of entry, but unlike the first embodiment, it does not know the planned exit time. However, the management server 202 can sequentially calculate the elapsed time from the entry time to the current time, i.e., the user's parking time up to the current time, and can also sequentially calculate the number of points used corresponding to the length of that parking time. This allows the management server 202 to notice that, even if the number of points used at that time is attempted to be used, the number of remaining points is insufficient in relation to the length of the parking time, and therefore the parking fee cannot be paid in full.

In this embodiment, as shown in the sequence diagram in Figure 33, the management server 202 sequentially calculates the length of parking time for each user who has not yet paid their parking fee, and also calculates the number of points used that corresponds to the length of parking time. The management server 202 also determines whether the number of remaining points is insufficient in relation to the length of parking time even if the number of points used at that time is to be consumed. If the number of remaining points is insufficient, the management server 202 creates an exit prompt message to urge the user to exit the parking lot promptly, and sends the exit prompt message by email to the communication device of the relevant user.

As is clear from the above explanation, in this embodiment, for the sake of convenience, steps S120 and S123 shown in Figure 28 constitute an example of the "entry time reception process" in section (1) or (2) above, steps S124 to S126 shown in the same figure constitute an example of the "entry time validity determination process" in the same section, and step S302 shown in the same figure can be considered to constitute an example of the "parking permission process" in the same section.

Furthermore, in this embodiment, for the sake of convenience, steps S134 and S137 shown in Figure 29 constitute an example of the "receiving process at the time of leaving" in section (3) above, steps S138 to S140 shown in the same figure constitute an example of the "departure time validity determination process" in the same section, and step S402 shown in the same figure constitute an example of the "parking time calculation process" in the same section.

It should be noted that in some of the embodiments described above, the ticket dispenser 20 is a standalone device that does not have the function of communicating with the parking lot manager (management server 202), which is advantageous in minimizing the equipment costs of the ticket dispenser 20. However, the present invention can also be implemented in a form in which the ticket dispenser 20 has this communication function.

In this embodiment, for example, the management server 202 is equipped with a clock 102 and a time encryption unit (a part where a computer references the time encryption table shown in Figure 13(b) to generate a time code 190) that encrypts the current time measured by the clock 102. The management server 202 measures the current time, encrypts it, generates a time code 190, and transmits the time code 190 to the ticket dispenser 20. The display 36 of the ticket dispenser 20 then displays the received time code 190. According to this embodiment, the ticket dispenser 20 does not need to have a clock 102 or the time encryption unit, but instead has the communication function.

Although several embodiments of the present invention have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be implemented in other forms, including those described in the "Summary of the Invention" section above, with various modifications and improvements based on the knowledge of those skilled in the art.

Claims (7)

A parking lot management system,
a display unit that is installed in the parking lot and displays the encrypted data without using a physical parking ticket;
a management server located in a remote location from the parking lot;
The management server is
a parking lot identification unit that, when exiting the parking lot, receives first information from the communication device of the user currently in the parking lot to identify the parking lot from which the user is about to exit by communicating with the management server using the displayed encrypted data, and identifies the parking lot based on the received first information;
a user-specific information identification unit that receives second information for identifying a number unique to the user from the communication device when the vehicle leaves the parking lot, and that is capable of identifying user-specific information unique to the user based on the received second information;
and an electronic payment unit that, when the parking lot and the user- specific information are identified upon exiting the parking lot, enables the parking fee for the identified parking lot to be settled by electronic payment through communication with the communication device. The management server further
2. The parking lot management system of claim 1, further comprising a settlement completion data transmission unit that transmits settlement completion data to the communication device indicating that settlement of the parking fee has been completed when the parking fee is settled by electronic payment upon exiting the parking lot. The parking lot management system according to claim 1 , wherein the user specific information includes a vehicle number of the user's vehicle. A program executed by a computer of a communication device of a user currently present in the parking lot managed by the parking lot management system according to any one of claims 1 to 3,
The communication device has a plurality of functions,
a first transmission function that, when the user leaves the parking lot, communicates with the management server using the displayed encrypted data to transmit the first information from the user to the management server;
a second transmission function of transmitting the second information from the user to the management server when the user leaves the parking lot;
and a settlement completion data receiving function for receiving, when the parking fee has been settled by electronic payment by the management server at the time of exiting the parking lot, settlement completion data indicating that the settlement of the parking fee has been completed from the management server,
A program executed by the computer to realize the functions. A program for causing a computer to function as the management server described in any one of claims 1 to 3. A computer-readable recording medium on which the program described in claim 4 is recorded. A computer-readable recording medium on which the program described in claim 5 is recorded.