JP6905725B2 - Parking lot management system - Google Patents

Description

The present invention relates to a technique for managing a parking lot.

Parking lots with multiple parking positions for vehicles are already widespread. This type of parking lot is classified from the viewpoint of the method of transporting the vehicle to the parking position. The user drives the vehicle by himself / herself to transport the vehicle to the parking position, and the pallet or cage is mechanically moved to move the vehicle. It is classified as a mechanical type that transports the vehicle to the parking position. In addition, the parking lot may be rented to the user free of charge, or may be rented for a fee. Paid parking lots are classified into monthly rentals and hourly rentals (including "daily rentals") from the viewpoint of the length of time they are rented to users.

Hourly parking lots are classified from the viewpoint of parking fee payment method, and are prepaid type in which the user pays the parking fee prior to the start of parking (however, the possibility of paying the shortage of the parking fee at the time of leaving the parking lot is included). And, it is classified into a postpaid type in which the user pays the parking fee in a lump sum at the end of parking.

In addition, hourly rental parking lots are classified into manned type in which the person in charge of managing and monitoring the parking lot is resident in the parking lot, which is the site, and the person in charge who is not resident in the parking lot. It is classified as an unmanned type in which people are sporadically dispatched to the parking lot at the site.

As a publicly known document that discloses a parking lot of this type and equipment (including a ticket issuing machine) installed in the parking lot, for example, Patent Document 1 exists.

Patent Document 1 discloses a prepaid unmanned parking lot. In this parking lot, there is a card issuing machine that issues a parking card that records the time when parking is permitted, a warehousing gate that is always closed, and a parking card that is installed at the warehousing entrance and when the parking card is inserted. , A warehousing management device that opens the warehousing gate on condition that the parking card is appropriate is installed. In addition, this parking lot has an exit gate that is always closed, and an exit management device that is installed at the exit and opens the exit gate when a parking card is inserted, provided that the parking card is appropriate. And are installed.

As described above, Patent Document 1 discloses a technique in which a user parks a car in an unmanned toll parking lot using an existing card (for example, a physical parking ticket). ..

On the other hand, Patent Document 2 discloses a technique in which a user parks a car in an unmanned pay parking lot in a cardless manner.

Japanese Unexamined Patent Publication No. 2006-146325 Japanese Unexamined Patent Publication No. 8-111000

According to the technique disclosed in Patent Document 2, since the user can park in the parking lot without using the card, there is an advantage that the user does not have to worry about losing the card. However, in order to implement the technique disclosed in Patent Document 2, special and expensive equipment is installed in both the automobile and the parking lot in order to acquire information unique to the automobile to be parked in the parking lot. For those who own a parking lot or manage a parking lot, the cost of the equipment itself, the cost and manpower required to install the equipment in the parking lot, and the maintenance and inspection of the equipment. There is a drawback that the cost and labor required for the work to be performed are likely to increase.

In addition, it is important for the parking lot manager who manages the parking lot to accurately grasp the fact that the user has entered or exited the parking lot. It is also important for users of hourly parking lots to improve their technology for reimbursing parking fees.

Based on the above findings, the present invention is a technique for managing a parking lot, and has been made as an object to improve a technique for a user to settle a parking fee.

In order to solve this problem , according to one aspect of the present invention, it is a parking lot management system that manages a parking lot that is a ticketless system and a cashless system that does not use a physical parking ticket.
Parking-related information related to parking for a user who is installed in the parking lot and uses the parking lot and includes information capable of identifying the position of the parking lot without using a physical parking ticket. The display part to display and
A management server that manages the parking lot in a remote location,
A communication device of a user in the parking lot that transmits parking settlement-related information and / or other parking-related information displayed on the display unit to the management server.
Including
The management server is provided with a parking lot management system having a settlement unit for settling the parking fee charged to the user by electronic payment based on the parking-related information received from the communication device.
Further, according to an aspect of the present invention, it is a parking lot management system that manages a parking lot.
A device installed in the parking lot that outputs charge information related to parking charges, and
A management server that manages the parking lot in a remote location,
A communication device of a user in the parking lot, including a device for inputting the output charge information and transmitting the charge information or information based on the input to the management server.
The management server responds to a request from a user via the communication device, and provides a parking lot management system having a settlement unit for settlement of the parking fee by electronic payment.
Further, according to one aspect of the present invention, the user accesses the parking lot manager's management server online from any place via a communication device, thereby obtaining an electronic parking ticket from the parking lot manager. , A cardless parking management method that allows a user to park in a parking lot selected by the user using the electronic parking ticket.
When the communication device transmits an issuance request in order for the user to request the parking lot manager to issue the electronic parking ticket, the management server receives the issuance request from the communication device.
After the reception, the management server issues the electronic parking ticket to the user, and includes data for displaying the electronic parking ticket and including electronic parking ticket identification data for specifying the electronic parking ticket. The process of transmitting a thing to the communication device and
When the communication terminal transmits a usage request and the electronic parking ticket specific data in order to start parking in the parking lot using the issued electronic parking ticket when the user enters the parking lot. , The process in which the management server receives the usage request and the electronic parking ticket specific data from the communication device, and
After the reception, the management server collates the received electronic parking ticket identification data with the electronic parking ticket identification data registered in advance in the memory of the management server, and the user's electronic parking ticket is valid. A cardless parking management method including a step of transmitting information indicating that the use of the electronic parking ticket is not permitted to the communication device is provided.

Further, according to another aspect of the present invention, the user accesses the parking lot manager's management server online from any place via a communication device, thereby purchasing an electronic parking ticket from the parking lot manager. A cardless parking management method that allows a user to park in a parking lot selected by the user using the electronic parking ticket.
When the communication device transmits an issuance request in order for the user to request the parking lot manager to issue the electronic parking ticket, the management server receives the issuance request from the communication device.
After receiving the data, when the user pays a parking fee commensurate with the length of the scheduled parking time specified by the user, the management server issues the electronic parking ticket to the user and issues the electronic parking ticket. A step of transmitting data to be displayed including electronic parking ticket specific data for specifying the electronic parking ticket to the communication device, and
When the communication terminal transmits a usage request and the electronic parking ticket specific data in order to start parking in the parking lot using the issued electronic parking ticket when the user enters the parking lot. , The process in which the management server receives the usage request and the electronic parking ticket specific data from the communication device, and
After the reception, the management server collates the received electronic parking ticket identification data with the electronic parking ticket identification data registered in advance in the memory of the management server, and the user's electronic parking ticket is valid. A cardless parking management method including a step of transmitting information indicating that the use of the electronic parking ticket is not permitted to the communication device is provided.

According to an aspect of the present invention, a user accesses a parking lot manager's management server online from any location via a mobile terminal, thereby purchasing an electronic parking ticket from the parking lot manager. A cardless parking management method that allows a user to park in a parking lot selected by the user using an electronic parking ticket.
A process in which the management server receives from the user's mobile terminal in order for the user to request the parking lot manager to issue the electronic parking ticket.
After the reception, when the user pays a parking fee of an amount commensurate with the length of the scheduled parking time specified by the user, the management server issues the electronic parking ticket to the user and issues the electronic parking ticket. The process of sending data for display to the user's mobile terminal,
A process of receiving from the user's mobile terminal by the management server in order to start parking in the parking lot using the issued electronic parking ticket when the user enters the parking lot.
After receiving the reception, the management server determines whether or not the electronic parking ticket of the user is valid, and if it is determined that the electronic parking ticket is not valid, the user carries information indicating that the use of the electronic parking ticket is not permitted. The process of sending to the terminal and
When the length of the actual continuous parking time by the user exceeds the length of the scheduled parking time, the process of receiving from the user's mobile terminal by the management server when the user leaves the parking lot.
After the reception, the management server calculates an additional parking fee commensurate with the length of the excess time, and when the user pays the additional parking fee, the user carries data indicating that the settlement has been performed. A cardless parking management method is provided that includes a process of sending to a terminal.

Further, according to one aspect of the present invention, a parking lot installed in each of a plurality of parking lots and displaying an encrypted time code different from the time code displayed in other parking lots. Time code display device
The time code is used by an administrator who manages the plurality of parking lots in order to acquire the fact that the user has entered or exited the corresponding parking lot.
As the time code, a parking lot time code display device having a location discriminating ability that can uniquely identify the location of the parking lot on which the time code is displayed is provided.

Further, according to another aspect of the present invention, for parking lots, in each of a plurality of parking lots, the time code in which the current time is encrypted is displayed so as to be different from the time code displayed in other parking lots. It is a time code display method
The time code is used by an administrator who manages the plurality of parking lots in order to acquire the fact that the user has entered or exited the corresponding parking lot.
As the time code, a parking lot time code display method having a location discriminating ability that can uniquely identify the location of the parking lot on which the time code is displayed is provided.

Further, according to still another aspect of the present invention, it is a parking lot time code display device that displays a time code in which the current time is encrypted in a parking lot.
The time code can be read and reproduced by the user of the parking lot as a known character, number, symbol or figure or a combination thereof, and can not be deciphered by the user but can be deciphered by the manager of the parking lot. Provided is a time code display device for a parking lot, which can be deciphered and can restore the information representing the current time.

According to the present invention, the following aspects can be obtained. Each aspect shall be divided into sections, each section shall be numbered, and the numbers of other sections shall be cited as necessary. This is to facilitate understanding of some of the technical features that can be adopted by the present invention and combinations thereof, and the technical features that can be adopted by the present invention and combinations thereof are limited to the following aspects. Should not be interpreted as. That is, it should be interpreted that it is not hindered from appropriately extracting and adopting the technical features described in the present specification as the technical features of the present invention, which are not described in the following aspects.

Furthermore, describing each section in the form of quoting the numbers of the other sections does not necessarily prevent the technical features described in each section from being separated and independent from the technical features described in the other sections. It does not mean, and it should be interpreted that the technical features described in each section can be made independent as appropriate according to their properties.

(1) A parking lot management method for managing parking lots.
In the parking lot
With a clock
A time code that allows the user of the parking lot to read and reproduce the current time measured by the clock as known characters, numbers, symbols or figures or a combination thereof by encryption. Is not decipherable, but the administrator of the parking lot converts it into something that can be deciphered.
A parking lot time code generator / display device including a display unit that displays the time code generated by the encryption unit is installed.
The parking lot management method is
Information for identifying the electronic parking ticket transmitted by the user via a communication device in order to park in the parking lot using the electronic parking ticket at the time of entering the parking lot. A receiving process at the time of warehousing, in which the communication unit receives the time code displayed on the display unit at the time of warehousing in the parking lot.
The processor decodes the time code received at the time of warehousing by referring to the decryption table, estimates the time represented by the received time code as the warehousing time based on the decryption result, and estimates the warehousing time. Determines whether or not the processor is within a predetermined permissible range determined with respect to the reception time when the time code is received, thereby determining whether or not the estimated receipt time is appropriate. Time validity judgment process and
A parking lot management method including a parking permission step of permitting the user to use the parking lot when the processor determines that the estimated warehousing time is appropriate.

Throughout this specification, the term "electronic parking ticket" is a non-existent virtual parking ticket in which the information on the electronic parking ticket is used in other media for the user to use the electronic parking ticket. It means a parking ticket in a format that is not required to be presented to the other party by printing or displaying it on the parking lot.

(2) A parking lot management method that manages parking lots.
In the parking lot
A time code generated by encrypting the current time, which can be read and reproduced by the user of the parking lot as known characters, numbers, symbols or figures or a combination thereof, and the user can reproduce it. Although it cannot be deciphered, the parking lot manager has a display unit that displays what can be deciphered.
The parking lot management method is
Information for identifying the electronic parking ticket transmitted by the user via a communication device in order to park in the parking lot using the electronic parking ticket at the time of entering the parking lot. A receiving process at the time of warehousing, in which the communication unit receives the time code displayed on the display unit at the time of warehousing in the parking lot.
The processor decodes the time code received at the time of warehousing by referring to the decryption table, estimates the time represented by the received time code as the warehousing time based on the decryption result, and estimates the warehousing time. Determines whether or not the processor is within a predetermined permissible range determined with respect to the reception time when the time code is received, thereby determining whether or not the estimated receipt time is appropriate. Time validity judgment process and
A parking lot management method including a parking permission step of permitting the user to use the parking lot when the processor determines that the estimated warehousing time is appropriate.

(3) Furthermore
Information for identifying the electronic parking ticket transmitted by the user via the communication device at the time of leaving the parking lot, and a time code displayed on the display unit at the time of leaving the parking lot. And the receiving process at the time of delivery, which is received by the communication unit.
The processor decodes the time code received at the time of delivery by referring to the decryption table, estimates the time represented by the received time code as the delivery time based on the decryption result, and estimates the time code. It is determined whether or not the delivery time is within a predetermined allowable range determined with respect to the reception time when the processor receives the time code, thereby determining whether or not the estimated delivery time code is valid. Departure time validity judgment process to be judged and
When the processor determines that the estimated warehousing time is appropriate, the length of the elapsed time from the estimated warehousing time to the estimated warehousing time is defined as the parking time by the user. The parking lot management method according to item (1) or (2), which includes a parking time calculation step to be calculated.

(4) Furthermore
An issuance request receiving process in which the communication unit receives an issuance request for requesting the parking manager to issue the electronic parking ticket transmitted by the user via the communication device.
The processor issues the electronic parking ticket to the user and transmits the electronic parking ticket to the user's communication device, provided that the user pays a predetermined amount of the fee in advance in response to the received issuance request. The parking lot management method according to any one of (1) to (3), which includes an electronic parking ticket issuing process.

(5) Installed and used in the parking lot,
A time code generated by encrypting the current time, which can be read and reproduced by the user of the parking lot as known characters, numbers, symbols or figures or a combination thereof, and the user can reproduce it. A parking time code display device that displays items that cannot be deciphered but can be deciphered by the parking lot manager.

(6) The parking lot time code display device according to item (5), which displays a location code unique to the parking lot together with the time code.

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

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

According to the present invention, it is possible to provide a service that enables a user to park in a parking lot in a cardless manner without installing 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 an exemplary first 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 showing the ticket issuing machine shown in FIG. 2 in a state where the door is open. FIG. 4 is a block diagram showing a component configuration of the ticket issuing machine shown in FIG. FIG. 5 is a flowchart conceptually representing the ticketing / payment program executed by the computer shown in FIG. 6 (a)-(d) are front views showing a plurality of images displayed on the screen of the display shown in FIG. 2. FIG. 7 (a) is a front view showing an example of a parking ticket and a receipt issued after payment of the prepaid parking fee by the ticket issuing machine shown in FIG. 2, and FIG. 7 (b) is a front view showing an example of the ticket issuance shown in FIG. It is a front view which shows an example of the receipt issued by the machine after payment of an additional parking fee. FIG. 8 (a) is a vertical cross-sectional view showing the parking ticket shown in FIG. 7 (a) in a state immediately after issuance, and FIG. 8 (b) shows the parking ticket partially peeled off and bent. FIG. 9 (a) is a side sectional view showing the parking ticket shown in FIG. 7 (a) attached to the back surface of the windshield of the parked vehicle, and FIG. 9 (b) shows the parking ticket. , Is a perspective view showing a part of the display sheet thereof peeled off from the separator and bent. FIG. 10 is a perspective view showing how the parking ticket shown in FIG. 7A is attached to the back surface of the windshield of the parked vehicle. 11 (a)-(c) show the configuration of an example of the encrypted data printed on the receipt shown in FIGS. 7 (a) and 7 (b), the corresponding actual data, and the actual data to the encrypted data. It is a figure for demonstrating the conversion process. FIG. 12 shows a state in which the user communicates the encrypted data printed on the receipts shown in FIGS. 7 (a) and 7 (b) to the parking lot manager at a remote location using his / her mobile phone. It is a perspective view for explaining how the parking lot manager converts the received encrypted data into actual data. 13 (a)-(c) is a portion of the ticket issuing machine shown in FIG. 4 related to the parking lot management method, and is a diagram for conceptually explaining a process of generating and displaying a time code. Is. FIG. 14 conceptually represents a code display program executed by the computer of the ticket issuing machine shown in FIG. 4 in order to execute the processes (time code generation and display) shown in FIGS. 13 (a) to 13 (c). It is a flowchart. 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 representing a first subprogram that is a part of the electronic parking ticket processing program executed by the management server shown in FIG. FIG. 17 is a flowchart conceptually representing a second subprogram, which is another part of the electronic parking ticket processing program executed by the management server shown in FIG. FIG. 18 is a flowchart conceptually representing a third subprogram, which is yet another part of the electronic parking ticket processing program executed by the management server shown in FIG. FIG. 19 is a diagram conceptually representing the member DB shown in FIG. FIG. 20 is a diagram conceptually representing 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 a process of membership registration performed by executing the electronic parking ticket processing program. FIG. 23 is a sequence diagram for explaining a process of issuing an electronic parking ticket performed by executing the electronic parking ticket processing program. FIG. 24 is a sequence diagram for explaining a process of permitting the use of an electronic parking ticket 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 a process of settlement of the parking fee at the time of extended parking, which is performed by executing the electronic parking ticket processing program. FIG. 27 is a sequence diagram for explaining a process of issuing a reminder, which is executed on the management server shown in FIG. FIG. 28 replaces the second subprogram shown in FIG. 17 of the electronic parking ticket processing programs executed on the management server to execute the parking lot management method according to the exemplary second embodiment of the present invention. 4 It is a flowchart which represents a subprogram conceptually. FIG. 29 is a flowchart conceptually representing a fifth subprogram that replaces the third subprogram shown in FIG. 18 among the electronic parking ticket processing programs according to the second embodiment. FIG. 30 is a sequence diagram for explaining a 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 a process of paying a fee 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 a process of urging the goods to be delivered, which is executed by the management server in the second embodiment.

Hereinafter, a parking lot management method according to some exemplary embodiments of the present invention will be described in detail with reference to the drawings.

<First Embodiment>

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

The parking lot 10 has a plurality of parking positions (parking spaces) that enable simultaneous parking of a plurality of automobiles. A single ticketing machine (generally also referred to as a "payment machine") 20 is parked in a plurality of parking lots 10 in the vicinity of the only entrance / exit 12 (which is both the entrance / exit) of the parking lot 10. Commonly located, it is installed as a centralized ticketing machine. The parking lot 10 is an unmanned type in which there is no full-time person who is resident and manages the parking lot 10, and the user who is the driver pays the parking fee to the ticket issuing machine 20.

In the present embodiment, the user is in the parking lot 10 and is not required to access the parking lot manager from the parking lot 10 in advance, and an electronic parking ticket (usually, not one parking lot) is used at any place. , A parking ticket that allows parking for multiple times, which is equivalent to a coupon ticket for transportation such as trains and buses) is purchased online from the parking lot manager, and the electronic parking ticket is used for this parking lot. It is possible to park at 10.

However, in the present embodiment, instead of such a parking method, every time the user tries to use the parking lot 10, the scheduled parking that he / she wants to park this time prior to the parking (at the time of warehousing). By specifying the length of time and paying the ticketing machine 20 a parking fee commensurate with it as a prepaid parking fee, the parking ticket printed on paper (ie, a physical ticket, an existing ticket or It is also possible to purchase a card) from the ticket issuing machine 20 and use the paper parking ticket to park in the parking lot 10.

That is, in the present embodiment, the user uses an electronic parking ticket (virtual ticket) that can be purchased by online access to the parking lot manager from any location to perform new parking (cashless and cardless). Yes, hereinafter referred to as "cardless parking") ") and normal parking using a physical parking ticket that can only be purchased from the ticketing machine 20 installed in the parking lot 10 (both cash and physical tickets). It is possible to select one of (hereinafter referred to as "normal parking") according to preference.

In addition to the definition of the term "vehicle", in the column of "mode for carrying out the invention", the term "vehicle" means only an automobile, but other parts of the present specification. In, the term "vehicle" should be interpreted as a term that includes not only automobiles but also all kinds of moving objects such as bicycles and motorcycles.

There are two types of parking lots on the site of the parking lot 10. It is a lot for renting parking space to users of each vehicle on a daily basis (temporary storage lot or lot for daily rental) and a lot for each vehicle user on a monthly basis, assuming a prior contract. It is a section for renting out parking space (monthly section). The ticketing machine 20 is used for the temporary storage area. Hereinafter, the term "parking lot 10" simply means only the temporary storage area, that is, the area where the ticket issuing machine 20 is used, in the parking lot 10.

In order to use the parking lot 10, the driver, who is a user, drives his / her own vehicle, enters the entrance / exit 12 from the adjacent road, and then continues to drive through the ticketing machine 20. Drive the vehicle to one of the parking spaces (parking position) of your choice and park there.

In the case of the above-mentioned normal parking, the user stops his / her own vehicle in one of the parking spaces, then gets out of his / her own vehicle, walks to the ticket issuing machine 20 at the entrance / exit 12, and parks there. The fee is paid to the ticket issuing machine 20.

FIG. 2 shows the ticketing machine 20 in a front view, FIG. 3 shows the ticketing machine 20 in a perspective view with the door 24 open, and FIG. 4 shows the ticketing machine 20 in a perspective view. The 20 component configurations are shown in the block diagram. FIG. 5 is conceptually represented by a flowchart of a ticketing / payment program executed by the computer 100 in the control board 34 shown in FIG. 6 (a)-(d) show a plurality of images displayed on the screen of the display 36 shown in FIG. 2 in a front view.

The user receives the parking ticket 80 shown in FIGS. 7A and 8 from the ticket issuing machine 20 in exchange for payment of the parking fee. The user then attaches the parking ticket 80 to the back of the windshield 110 of his vehicle (an example of a "window glass" of the vehicle), as shown in FIGS. 9 and 10. Since the parking ticket 80 is placed inside the parked vehicle, it is not exposed to rain and wind and is not lost.

The parking lot 10 is a prepaid unmanned parking lot having a plurality of parking positions, and is a device for blocking the exit of a vehicle (preventing the exit from the parking lot 10) (for example, a exit gate device or a wheel). It does not have a stop device (for example, a flap type or a haunting type), and the user can freely select one of the plurality of parking positions to park his / her own vehicle (selection). The parking position is not monitored by the ticketing machine 20). The ticket issuing machine 20 is used for the parking lot 10 configured in this way.

Here, the ticket issuing machine 20 will be described more specifically. The ticket issuing machine 20 has a charge settlement function but does not have a change function or a communication function. The ticket issuing machine 20 requires the user to pay the parking fee only in coins, not in banknotes. Further, the ticket issuing machine 20 can input a user identification number to the user, input vehicle identification information (for example, a vehicle number) about the user's vehicle, and specify a plurality of parking positions selected by the user. , Do not request.

As shown in FIG. 2, the ticket issuing machine 20 has a ticketing button 70 and a charge settlement button 74. The ticketing machine 20 includes a parking ticket 80 (see FIG. 7A) indicating that parking is permitted when the user presses the ticketing button 70 after paying the prepaid parking fee prior to the start of parking, and prepaid parking. It has a ticketing function to issue a receipt 81a (see FIG. 7A) indicating that the fee has been settled in two sheets. The ticket issuing machine 20 further receives a receipt 81b (see FIG. 7B) 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 the parking is completed. ) Has a charge settlement function to issue.

In the present embodiment, the two-sheet parking slip issued after payment of the prepaid parking fee is a two-sheet parking ticket 80 and a receipt 81a, but the user can use the parking ticket 80 and the receipt 81a. Separated from each other, only the parking ticket 80 is left in the parked vehicle, and the receipt 81a can be carried. As will be described later, the receipt 81a is printed with the end time of the effective parking time (the time zone in which the user is allowed to park), and the user can always end the effective parking time at a place away from the parked vehicle. It is convenient for the user to carry this receipt 81a so that the time can be referred to.

As shown in FIG. 3, the ticket issuing machine 20 is configured such that a door 24 is attached to a vertically long box-shaped casing 22 so as to be openable and closable on one side thereof. FIG. 3 shows the internal configuration of the ticket issuing machine 20 in a perspective view with the door 24 open. FIG. 4 shows a block diagram of the component configuration of the ticket issuing machine 20.

As shown in FIG. 3, the ticket issuing machine 20 prints and issues a coin processing unit 30, a safe 32, a control board 34, a display 36, a parking ticket 80, and receipts 81a and 81b. It is configured to have and. Of these parts, only the coin processing unit 30 is attached to the back surface of the door 24, and the remaining parts are attached to the inside of the casing 22.

As shown in FIG. 3, the printer 40 is equipped with a roller 42 around which a continuous sheet before printing is wound and accommodated. The printer 40 prints on a continuous sheet fed from the roller 42 by the length of one sheet. After the printing is completed, the printer 40 cuts the continuous sheet at any time with a cutter (not shown), and after paying the prepaid parking fee, spells two sheets of the parking ticket 80 and the receipt 81a for additional parking. After paying the fee, one receipt 81b is separated. However, as shown in FIG. 7A, a cut line 89 is formed between the two-sheet parking ticket 80 and the receipt 81a, and the user can use them along the cut line 89. The parking ticket 80 and the receipt 81a can be easily separated from each other.

The cutter has a cutting edge (not shown), and the cutting edge is moved in the width direction of the continuous sheet to cut the continuous sheet in the width direction. Further, the cutter can adopt a method of completely cutting the continuous sheet in the width direction, or a method of cutting the continuous sheet in the width direction while leaving only a part in the width direction.

As shown in FIGS. 2 and 4, the coin processing unit 30 includes a coin insertion slot 50, a return lever 52, and a coin selector (determination of the type of inserted coin and whether or not the inserted coin is a counterfeit coin). It has 54 and a coin return port 56. Among the inserted coins, those that have not been returned to the user through the coin return port 56 are stored in the safe 32. As shown in FIG. 4, a control board 34 is connected to the coin selector 54 so that data communication is possible, and the control board 34 is a coin type (a coin unit and a counterfeit coin) inserted from the coin selector 54. (Including information on whether or not there is) and a signal indicating the number of coins is received.

As shown in FIG. 2, on the front surface of the door 24, there is a transmission window 60 through which display light from the screen of a display 36 (for example, a liquid crystal display) is transmitted, a coin insertion slot 50, a return lever 52, and a coin return port 56. And the parking ticket 80 printed and discharged by the printer 40 and the discharge port 64 for discharging the receipts 81a and 81b are arranged. The transparent window 60 also has a function of mechanically protecting the display 36 by blocking direct access to the display 36 from the outside.

The ticketing machine 20 is further configured to have the aforementioned ticketing button 70 pressed after the user has paid the prepaid parking fee and the aforementioned fee settlement button 74 pressed after the user has paid the additional parking fee. There is. As shown in FIG. 2, the ticket issuing button 70 and the charge settlement button 74 are mounted on the front surface of the door 24 of the ticket issuing machine 20. The ticketing button 70 and the charge settlement button 74 are electrically connected to the control board 34 as shown in FIG.

Both the ticketing button 70 and the charge settlement button 74 are configured as existing physical switches, but the present invention is not limited to this, and for example, a virtual switch (for example, a virtual switch displayed on the screen of the display 36). For example, it may be configured as a button, a key, an icon).

The control board 34 is mainly composed of a computer 100. The control board 34 has a built-in clock 102, and can always acquire the current date and time (for example, the date and time when the ticketing button 70 is pressed, the date and time when the charge settlement button 74 is pressed). The control board 34 further contains a memory 104. The encryption table, which will be described later, is stored in the memory 104 in a state where it can be rewritten only by an authorized person.

In addition, the control board 34 can be in a form in which the same functions as those of the computer 100 are realized by a sequencer (sequence control).

Further, the ticket issuing machine 20 has a power supply unit (not shown). The power supply unit is a power source (for example, a commercial power source, a solar cell installed in the parking lot 10, a generator such as a wind power generator, a rechargeable battery installed in the parking lot 10, and is a commercial power source or a generator. (Such as those charged by), and the electric power from the power source is supplied to each electric / electronic component in the ticket issuing machine 20, thereby operating the ticketing machine 20. This power supply unit has, for example, an additional backup circuit having a power storage function so that even if the power supply from the power supply is temporarily stopped, its influence does not affect the operation of the ticket issuing machine 20. .. As a result, the ticket issuing machine 20 is guaranteed to operate at all times.

When the ticketing / payment program shown in FIG. 5 is executed by the computer 100, first, in step S1, the initial screen shown in FIG. 6A is displayed on the screen of the display 36. Next, in step S2, it is determined whether or not the user has inserted coins based on the signal from the coin selector 54. If no coins have been inserted, the process returns to step S2, but if coins have been inserted, the total amount of coins inserted by the user up to that point is calculated as the inserted amount in step S3.

Subsequently, in step S4, from the calculated input amount, the parking time corresponding to the input amount means the parking time (when the parking fee paid this time is the prepaid parking fee, it means the effective parking time. , If the parking fee paid this time is an additional parking fee, it means extended parking time). Since the relationship between the input amount and the length of the parking time, that is, the hourly charge setting is known to the computer 100, the computer 100 can calculate the parking time from the input amount according to the charge setting. The charge setting can be input individually for each hour by, for example, the parking lot manager operating the touch panel of the display 36.

According to an example of the above charge setting, the continuous parking time is 300 yen for up to 2 hours, 400 yen for up to 4 hours, 500 yen for up to 6 hours, 1000 yen for up to 12 hours, and 1500 yen for up to 24 hours. be. Under the charge setting of this example, for example, as in the example shown in FIG. 7, when the user pays 400 yen as the prepaid parking charge, the computer 100 calculates 4 hours as the effective parking time. If the user pays 300 yen as an additional parking fee, 2 hours will be calculated as an extended parking time.

After that, in step S5, the coin insertion screen shown in FIG. 6B is displayed on the screen of the display 36. At this time, the calculated input amount and the length of the parking time (effective parking time or extended parking time) are displayed.

Subsequently, in step S6, it is determined whether or not the ticketing button 70 has been pressed. If the ticketing button 70 has not been pressed yet, it is determined in step S7 whether or not the charge settlement button 74 has been pressed. If the charge settlement button 74 has not been pressed yet, the process returns to step S2.

After the start of coin insertion, the execution of steps S2-S7 is repeated until either the ticketing button 70 or the charge settlement button 74 is pressed. As a result, each time the user inserts a coin into the coin insertion slot 50, the total amount of coins inserted by the user from the start of insertion to the present time is calculated as the insertion amount, and the calculated insertion amount is used as the insertion amount. The parking time corresponding to the input amount is calculated, and the calculated input amount and the parking time (effective parking time or extended parking time) are displayed on the screen of the display 36.

When the ticketing button 70 is pressed, the parking ticket / receipt issuing screen shown in FIG. 6C is displayed on the screen of the display 36 in step S8. At this time, the amount of the parking fee determined by the operation of the ticketing button 70 by the user is displayed as the amount of the prepaid parking fee. In this case, the parking time calculated in the preceding step S4 means the effective parking time.

Subsequently, in step S9, the warehousing time when the user entered the parking lot 10 (or the date and time when the user paid the prepaid parking fee, the time when the parking ticket 80 was issued, the start time of the parking time, etc.) and the effective parking time. Actual data representing the length (or the amount of the prepaid parking fee paid by the user) that can be directly decrypted by the user cannot be decrypted by the user by referring to the encryption table. It is converted into encrypted data 130 that cannot be pronounced but can be uniquely pronounced. Encryption is performed, which creates encrypted data 130.

In the present embodiment, as shown in FIG. 11A, the encrypted data 130 is defined by a symbol of 9 digits arranged in a row (the number of digits may be larger than that or the number of digits may be smaller than that). Has been done. The symbol for each digit is selected, for example, as one of ten numbers from 0 to 9 and a plurality of alphabets. The multi-digit symbol is divided into a plurality of groups and printed on the receipt 81a, and adjacent groups are connected by a hyphen, whereby the user pronounces the multi-digit symbol at once in a breath. Instead, I put some breaks in it to make it easier and more accurate to pronounce.

An example of the general structure of the actual data (the notation in the Christian era is omitted to reduce the number of digits in the actual data) is as shown in FIG. 11 (b). However, the length of the effective parking time is the TT time. " As shown in FIG. 11 (c), the actual data includes a number MM representing the month, a number DD representing the day, a number hh representing the time in the time, and a number mm representing the minute in the time. , Length of parking time (meaning valid parking time if the corresponding receipt is for prepaid, while meaning extended parking time if the corresponding receipt is for additional parking fees) It has five elements, the number TT representing.

As shown in FIG. 11 (c), the encryption table is referred to for encrypting the monthly encryption table referred to for encrypting the number MM representing the month and the number DD representing the day. A daily encryption table, a time unit encryption table referred to for encrypting the number hh representing the time of the time, and a reference for encrypting the number mm of the minute of the time. It has a minute-by-minute encryption table and a time-time encryption table that is referred to for encrypting the number TT representing the length of parking time. Each of the above five elements is encrypted by referring to the corresponding encryption table, whereby the 9-digit encrypted data 130 is created.

In the present embodiment, the encryption table is updated every day, but a method of updating every time a period longer than 24 hours elapses (the encryption table is not updated within the same period) is adopted. A method of updating the encryption table every day within the same cycle, with a period longer than 24 hours as one cycle (between a period within one cycle and a period within another cycle, the encryption table is updated daily. It is possible to adopt the pattern that is common).

In one example, in the memory 104, when the encryption table is updated every day, the encryption table set, which is the encryption table for one month, is updated every month. In this case, the encrypted table set is updated by the administrator every month, for example, every time the administrator goes to the parking lot 10.

Further, in one example, for each of the above-mentioned five elements MM, DD, hh, mm and TT, the relationship between the actual data and the encrypted data in the encryption table, that is, the number before encryption (for example, "2"). The correspondence between "2") representing "month" and the code after encryption is generated by generating a random number for each number before encryption and adopting that random number as the code after encryption. Will be done.

When the encryption is completed in step S9 shown in FIG. 5, the parking ticket 80 and the receipt 81a are printed and issued by the printer 40 in step S10. As shown in FIG. 7A, the receipt 81a contains actual data in which the user can decipher the same information regarding at least one of the date and time and amount of parking fee payment or parking time and the length of parking time. And the encrypted data 130 that cannot be deciphered by the user. This completes the current execution of this ticketing / payment program.

Specifically, as shown in FIG. 7A, the parking ticket 80 is used to specify the end time of the effective parking time corresponding to the amount of the prepaid parking fee paid by the user and the location of the parking lot 10. Is printed. Further, the receipt 81a is printed with the warehousing time, the amount of the prepaid parking fee paid by the user, the end time of the effective parking time, and the display for specifying the location of the parking lot 10. The receipt 81a is also printed with the encrypted data 130 exemplified by "ABC-DEF-ABC". As shown in the text of FIG. 11B, the encrypted data 130 has the parking ticket 80 and the receipt 81a at the warehousing time (this is the time when the prepaid parking fee is paid and the parking time start time). The actual data representing the time when the ticket was issued (which is also equivalent to the time when the ticket was issued) and the length of the effective parking time (which is equivalent to the amount of the prepaid parking fee paid) is encrypted.

On the other hand, when the charge settlement button 74 is pressed instead of the ticketing button 70, the settlement receipt issuance screen shown in FIG. 6D is displayed on the screen of the display 36 in step S11. At this time, the amount of the parking fee determined by the operation of the charge settlement button 74 by the user is displayed as the amount of the additional parking fee. In this case, the parking time calculated in the preceding step S4 means the extended parking time.

Subsequently, in step S12, in the same manner as in step S9, the time when the receipt 81b was issued because the user paid the additional parking fee (this is equivalent to the time when the additional parking fee was paid) and the above. The actual data representing the length of the extended parking time (which is equivalent to the amount of the additional parking fee paid) is converted into the encrypted data 140 by referring to the encryption table.

Then, in step S13, the receipt 81b is printed and issued by the printer 40. Receipt 81b contains real data that the user can decipher the same information about at least one of the date and time and amount of parking fee payment or parking time and the length of parking time, as shown in FIG. 7 (b). And the encrypted data 140 that cannot be deciphered by the user. This completes the current execution of this ticketing / payment program.

Specifically, as shown in FIG. 7B, the receipt 81b shows the date and time when the receipt 81b was issued, the amount of the additional parking fee, and the location for specifying the location of the parking lot 10. Is printed.

Further, the encrypted data 140 exemplified in "123-456-789" is also printed on the receipt 81b. The encrypted data 140 is obtained by encrypting actual data representing the date and time when the receipt 81b was issued and the length of the extended parking time.

FIG. 7A shows a front view of the parking ticket 80 and the receipt 81a, while FIG. 7B shows the receipt 81b in the front view. The two-sheet spelling of the parking ticket 80 and the receipt 81a corresponds to two sheets of the parking ticket 80, and in the two-sheet spelling, the parking ticket 80 and the receipt 81a have the same size and composition. Further, the receipt 81b corresponds to one parking ticket 80, and has the same size and configuration as the parking ticket 80. Hereinafter, for the sake of simplicity, only the configuration of the parking ticket 80 will be typically described.

In the parking ticket 80, a display sheet (printing paper) 82 as a surface layer, an adhesive layer 83 (glue layer) as an intermediate layer, and a separator (separation sheet, release paper) 84 as a back layer are laminated in this order. It is composed of. The adhesive layer 83 is applied to the back surface of the display sheet 82 so as not to be easily peeled off. When the display sheet 82 is peeled off from the surface of the separator 84, the adhesive of the adhesive layer 83 is applied to the surface of the separator 84. Does not adhere to.

As shown in FIG. 7A, in one parking ticket 80, the outer circumference of the display sheet 82 is located inside the outer circumference of the separator 84. The original fabric wound around the roller 42 is formed by adhering a plurality of display sheets 82 (blank state) arranged in a row with a gap between them to a continuous separator 84.

The continuous sheet (continuous separator 84) in the printer 40 is cut by the cutter, and the cutting is performed at the position of the gap between the display sheets 82, and the display sheet 82 is not cut. On the other hand, glue does not adhere to the surface of the portion of the separator 84 that is exposed in the gap between the display sheets 82.

Therefore, according to the present embodiment, when cutting the continuous sheet, the glue of the adhesive layer 83 does not have to adhere to the cutting edge, and the manager dispatched to the site once or several times a day (for example, The frequency of maintenance of the cutter by the service person, the worker who patrols a plurality of parking lots, and the observer of the patrol) is reduced, and the labor cost for the manager is reduced.

However, in the present embodiment, for the receipt 81b, the separator 84 is completely cut to the length of one sheet by the cutter, whereas for the two-sheet spelling, the separator 84 is for two sheets. It is completely cut at the length of. However, as described above, with respect to the two-sheet spelling, as shown in FIG. 7A, the separator 84 is partially cut between the parking ticket 80 and the receipt 81a by the cutter. As a result, the cut line 89 is formed.

As shown in FIG. 7A, the display sheet 82 of the parking ticket 80 further has a cutting line 90 having both ends (not closed) immediately above the character string “parking ticket”. The cutting line 90 exists to allow the user to peel off a portion of the display sheet 82 from the separator 84 while the rest remains adhered to the separator 84. As shown in FIG. 8B, when the user peels off a part of the display sheet 82 (the area surrounded by the cutting line 90) from the separator 84 and bends it along a straight line connecting both ends of the cutting line 90, The surface of the bent portion 92 formed as a result (the portion of the adhesive layer 83 coated on the back surface of the bent portion 92) is exposed as a glue surface. FIG. 9A shows the bent portion 92 in a perspective view.

In the present embodiment, in order to prove that the parking by the user is not illegal parking, the user receives the parking ticket 80 in exchange for coin insertion, as shown in FIG. 9B, at the front of the parked vehicle. It is required to be attached to the back surface of the glass 110. Therefore, as shown in FIG. 9A, the user locally localizes the designated portion of the parking ticket 80 (the region surrounded by the cutting line 90 and finally becomes the bent portion 92). After being peeled off and bent, the surface of the bent portion 92 is attached to the back surface of the windshield 110 of the parked vehicle as shown in FIG. 9B. As a result, as shown in FIG. 10, the contents of the parking ticket 80 (in particular, information for specifying the end time of the parking time zone permitted to the user and the parking lot 10 in which the parking ticket 80 is valid). The display for identifying the location of the) can be visually observed from the outside at any time.

The user is required to pay an additional parking fee when the actual parking time exceeds the effective parking time. However, as described above, the parking lot 10 is unmanned and does not have a device for blocking the exit of the parked vehicle unless the necessary additional parking fee is paid. Therefore, as shown in FIG. 12, the user can use the parking lot 10. , Notify the parking lot manager at a remote management center from a location such as parking lot 10, in the car, or at home by using a communication device such as a mobile phone or landline phone to notify the fact that the necessary additional parking fee has been paid. Is required.

At this time, the user reads out both the encrypted data 130 printed on the receipt 81a issued at the time of warehousing and the encrypted data 140 printed on the receipt 81b issued at the time of warehousing, and emits a voice. The voice is required to be transmitted to the parking lot manager by the above communication device.

Upon receiving the voice representing the encrypted data 130 and 140 emitted by the user, the parking lot manager in the management center operates the input device (for example, keyboard, touch screen, mouse, etc.) of the decryption device 180. , Enter the code corresponding to the user's voice. The encryption data 130 and 140 are input, and then the decryption device 180 mounts the input encryption data 130 and 140 in the decryption device 180, which is a decryption table suitable for the encryption table. Restore to actual data according to the above.

As a result, the parking lot manager can use the length of the actual parking time (for example, the time actually parked by the user) while staying at the management center located away from the parking lot 10 to be managed (for example,). , The length of time elapsed from the warehousing time specified by the encrypted data 130 to the time when the additional parking fee is paid specified by the encrypted data 140), and further, the parking fee paid by the user It is also possible to know the total amount (for example, the sum of the amount of the prepaid parking fee specified by the encrypted data 130 and the amount of the additional parking fee specified by the encrypted data 140), and by extension, the total amount of the parking fee. , It is possible to correctly judge whether or not there is a shortage in relation to the actual length of parking time.

Since the decryption table housed in the decryption device 180 cannot be known even by the parking lot manager unless he / she has the authority, the security of the decryption table is high.

As is clear from the above description, according to the present embodiment, at the time of issuing the receipts 81a and 81b, the encrypted data 130 and 140 are printed on the receipts 81a and 81b, respectively, with symbols that can be pronounced by the user. The parking manager can correctly determine whether or not the parking fee is insufficient simply by printing and further requesting the user to transmit the encrypted data 130 and 140 to the parking lot manager by voice. Therefore, the user can safely park the parking lot exceeding the effective parking time without imposing a heavy burden, and the usability of the parking lot 10 and the operating rate are improved.

In addition, in the present embodiment, the user transmits the encrypted data 130 and 140 by voice input, but for example, instead of the voice input, data input (for example, real or virtual) is performed. It can be performed by key input using a key or image input using an image reader).

The normal parking has been described above, but next, the cardless parking will be described.

As is clear from the above description, in the present embodiment, neither the parking lot 10 nor the ticket issuing machine 20 has a facility for detecting the fact that each user has entered / exited the parking lot 10. Further, in the case of cardless parking, as will be described in detail later, the user starts parking using his / her own electronic parking ticket using his / her own communication device (for example, a mobile phone or a smart phone). A message is sent to the parking lot manager to request, but neither the parking lot 10 nor the ticketing machine 20 can detect the fact that the user is actually parked in the parking lot 10 at that time, and the user It is not possible to detect the fact that the user actually entered the parking lot 10 unless, for example, the GPS function of the communication device is used by simply using his / her own communication device.

On the other hand, in the present embodiment, as shown in FIG. 13B, the ticket issuing machine 20 uses the current time measured by the clock 102 as the actual data, and uses the actual data as the time encryption table (ticketing machine 20). It is designed to be encrypted by using (stored in the memory 104 of the), thereby acquiring the time code 190 as encrypted data. The time code 190 cannot be deciphered by the user but can be deciphered by the parking lot manager (for example, like the encryption codes 130 and 140, the user cannot decipher it but can pronounce it uniquely). be.

In one example, as shown in FIG. 13 (c), the time code 190 is updated in a time discrete manner, that is, at set time intervals (for example, 15 minutes).

As shown in FIG. 13A, the ticket issuing machine 20 is further designed to display the time code 190 on the screen of the display 36 in a state of being sequentially updated with the passage of time.

As shown in FIG. 13A, the ticket issuing machine 20 further displays the position of the parking lot 10 on the screen of the display 36 together with the time code 190, which is a location code 192 unique to the parking lot 10. It is designed to display what is identifiable.

In FIG. 14, a code display program executed by the computer 100 of the ticket issuing machine 20 to display the time code 190 and the place code 192 is conceptually represented by a flowchart. This code display program is repeatedly executed during the operation of the ticket issuing machine 20.

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

By iteratively executing this code display program, the time code 190 and the location code 192 are displayed on the screen of the display 36 on the same screen as illustrated in FIG. 13 (a). It is always displayed in a position that does not obscure the message to be sent.

Here, the time code 190 will be described in detail. Since the time code 190 is generated differently on the same day at different times, it has a time dependence.

Further, since the time code 190 is generated so as not to be decrypted by any user of the parking lot 10, even though the user has not actually entered or exited the parking lot 10 at any time. Or, even though the parking lot 10 was actually entered or exited at another time, the display 36 is displayed at that time in an attempt to impersonate a user who entered or exited the parking lot 10 at a certain time. Even if the user tries to predict the time code 190 that should be, the user cannot obtain the authentic time code 190. Therefore, the time code 190 also has confidentiality to the user.

Further, the time code 190 is only displayed on the indicator 36 of the parking lot 10 where the user is actually trying to park or is parked, so that the user can obtain the required time code 190. I have to go to the parking lot 10. Therefore, the time code 190 is location-dependent.

As described above, the time code 190 has time dependence, confidentiality to the user, and location dependence, so that the time code 190 actually seen by the user in the parking lot 10 can be displayed by the display device. As long as the time code 190 is transmitted to the management server 202 at a time not significantly delayed from the time displayed on 36 (a time within the allowable setting range), the time code 190 indicates the fact that the user actually entered or exited the parking lot 10. It is a powerful proof to support.

Here, to elaborate on the time encryption table, the time encryption table is updated periodically, for example, every day, like the encryption table shown in FIG. As a result, if the dates are different, there is a high possibility that the time code 190 will be different even if the time is the same, and as a result, misuse of the time code 190 is prevented.

In an exemplary scenario where the same parking lot manager manages multiple parking lots (including parking lot 10) and the time code 190 is displayed in each of these parking lots, the time code It is desirable that 190 is generated differently at the same time but at different parking lot locations. In this preferred embodiment, the time code 190 displayed on the parking lot 10 has location discriminating power.

Here, the term "location discriminating power" may be defined so as not to mean that the time code 190 differs depending on the location, but does not mean that the location can be uniquely identified from the time code 190. For example, it may be defined to mean not only the feature that it differs depending on the place but also the feature that the place can be uniquely specified from the time code 190.

However, in the present embodiment, in order for the management server 202 to identify the location of the parking lot 10 used by the user from the information received from the user, the time code 190 does not have the location discriminating power. May be good. This is because, in the present embodiment, the place code 192 having the place discriminating power is displayed to the user in the parking lot 10 together with the time code 190.

Therefore, the correct time code 190 for the parking lot 10 that the user is about to use cannot be obtained unless the user is actually in the 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 the parking lot manager at a remote location at the time of warehousing, the parking lot manager can send the observed time code 190 to any of the parking lots 10. It is possible to estimate at which time the goods were received.

Specifically, the time code 190 and the place code 192 are communicated by the user to the parking lot manager via his / her own communication device at the time of warehousing. Upon receiving the time code 190 and the location code 192, the parking lot manager uses the time code 190 as actual data by referring to the decryption table 234 (see FIG. 15) that matches the time encryption table. Convert to the current time. By using the received location code 192, the parking lot manager can estimate the fact that the user actually entered the parking lot 10 specified by the location code 192.

The parking lot manager further increases the current time obtained by decrypting the time code 190 (for example, the observation time when the user observes the display 36) and the current time measured by the parking lot manager (parking lot management). The current time (FIG. 13) actually obtained by the user by decrypting the time code 190 when the difference from the reception time when the person received the time code 190 is within the set allowable range (for example, 30 minutes). As illustrated in (c), if there is a time width, the user can use it at any time between (the earliest time of the time width) and the current time measured by the parking lot manager. It can be estimated that the vehicle has entered the parking lot 10 (parking in the parking lot 10 has started).

On the other hand, even if the parking lot manager cannot normally decrypt the received time code 190, or even if the parking lot manager can successfully decrypt the received time code 190, the current time obtained by the code and the current time obtained by the parking lot manager are measured by the parking lot manager. If it is determined that the difference from the current time exceeds the allowable setting range, the time code 190 transmitted by the user to the parking lot manager may not exist as the time code 190 in the ticket issuing machine 20. Or, even if it exists, the time when the user sends the time code 190 to the parking lot manager is considerably later than the time when the user observes the time code 190 on the display 36, so that the user can use his / her own electronic parking ticket. Even if it is valid, parking using it will be refused by the parking lot manager.

In addition, if the length of the allowable setting time is set to be long, the time when the time code 190 on the display 36 is observed and the time code 190 are transmitted to the parking lot manager. The time gap between the time and the time may be long to some extent. This increases the range of choices of transmission time allowed for the user, which in turn provides the following advantages.

That is, for example, when the user parks his / her own vehicle in the parking lot 10 and tries to walk out of the parking lot 10, the time code 190 displayed on the display 36 is stored, and then the time code 190 is stored. If you need to walk from parking lot 10 to the nearest station and use transportation such as trains and buses, after boarding that transportation, remember the time code 190 and park. It is permissible to send to the administrator.

Then, the user is more time-consuming and mentally burdened than when the parking lot 10 is always required to send the time code 190 from the parking lot 10 to the parking lot manager regardless of whether or not there is time to spare. The burden is reduced, and the usability of the parking lot 10 is improved.

The characteristic elements of the ticket issuing machine 20 for performing cardless parking have been described in detail above. However, by referring to FIGS. 15 to 27 below, a service for issuing an electronic parking ticket to a user. Explain the contents.

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

In the system 200, a plurality of users and a plurality of persons in charge of performing work according to the instructions of the parking lot manager (each person in charge is the parking lot 10 managed by the parking lot manager and a plurality of other parking lots). It has the task of patrolling and monitoring the parking lot several times a day) and is wirelessly or wiredly connected to the management server 202 via the Internet 204, which is an example of a global communication network. There is.

The management server 202 has a transmission unit 210 that transmits a signal or data to an external destination and a reception unit 212 that receives a signal or data from an external transmission source for transmission / reception.

The management server 202 further includes a processor 220 and storage 222 (eg, ROM, RAM). In order to provide the service, the processor 220 executes an electronic parking ticket processing program, which is exemplified and conceptually shown in the flowchart in FIGS. 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 is further represented by a member database (hereinafter, “DB”) 230 illustrated in FIG. 19 and an electronic parking ticket database (hereinafter, “DB”) illustrated in FIG. The same applies to the figure.) It has 232 and the decryption table 234.

As an additional note, although not shown, the management server 202 has a clock for measuring the current time inside, or can use the measurement result of the external clock, like the ticket issuing machine 20.

To briefly explain the contents of this service, according to this service, the management server 200 gives the user a predetermined amount of parking fee in advance in response to an issue request from the user. On the other hand, the electronic parking ticket 250 illustrated in FIG. 21 is issued. When the user is going to park in the parking lot 10 using the issued electronic parking ticket 250, the parking permission request and the time code 190 displayed on the display 36 at the time of entering the parking lot 10 are displayed. Is transmitted to the management server 202, the management server 202 decrypts the received time code 190 with reference to the decryption table 234, and based on the decryption result, the warehousing time represented by the received time code 190 is set. The management server 202 determines whether or not the time code 190 is within a predetermined allowable range determined with respect to the received reception time, and thereby determines whether or not the received time code 190 is appropriate.

When it is determined that the received time code 190 is appropriate, the management server 202 permits the user to use the parking lot 10, and sends a parking permission message indicating that to the user.

[Member registration]

More specifically, in this service, in order to acquire the usage qualification of the electronic parking ticket 250, a process of registering the user as a member, a process of issuing the electronic parking ticket 250 to the user, and parking. The process of allowing the user to use the electronic parking ticket 250 at the start, and only when the user has extended parking, at the end of parking, an additional parking fee commensurate with the length of the extended parking time is paid by electronic payment. The steps for settlement are carried out in that order.

More specifically, in this service, first, as illustrated in the sequence diagram in FIG. 22, the user accesses the management server 202 and registers as a member. When the user transmits the user information necessary for the member registration to the management server 202, the management server 202 registers the received user information in the member DB 230 illustrated in FIG. 19 for each user.

[Issuance of electronic parking ticket]

Next, the user accesses the management server 202 as illustrated in the sequence diagram in FIG. 23 in order to request the parking lot manager to issue the electronic parking ticket 250. After that, the user transmits the user ID and the personal identification number to the management server 202, and then the management server 202 performs personal authentication. Subsequently, the user transmits the number of points to be acquired to the management server 202, and the management server 202 calculates the fee required to acquire the number of points. When the user pays the fee, the management server 202 assigns a unique ticket number to the electronic parking ticket 250 to be issued, further assigns the number of valid points, and exemplifies the information in FIG. 20. Register in the electronic parking ticket DB232. After that, the management server 202 issues the electronic parking ticket 250 illustrated in FIG. 21 to the user.

[Permission to use electronic parking ticket]

After that, when the user enters the parking lot 10, the management server 202 is illustrated in the sequence diagram in FIG. 24 in order to start parking in the parking lot 10 by using the issued electronic parking ticket 250. To access. After that, the user transmits the unique ticket number assigned to the electronic parking ticket 250 to be used this time to the management server 202, and the management server 202 confirms the validity of the electronic parking ticket 250. Subsequently, the user transmits the time code 190 and the location code 192 displayed on the display 36 to the management server 202. The management server 202 estimates the user's warehousing time by decrypting the received time code 190, and confirms the validity of the estimated warehousing time by comparing it with the current time measured by the management server 202. do.

After that, the user transmits the parking condition to the management server 202. The parking condition includes the length of time that the user wants to park in the parking lot 10 from now on. Subsequently, the management server 202 calculates the number of points used to allow the parking time to the user. The management server 202 further calculates the number of remaining points by subtracting the number of used points from the current number of valid points, and when it is confirmed that the number of remaining points is not 0, the valid parking time allowed to the user. Calculate the length of. After that, the management server 202 issues the receipt 260 illustrated in FIG. 25 and transmits it to the user.

In the present embodiment, it is noted that the user is required to specify the scheduled delivery time (equivalent to the length of the scheduled parking time) at the time of warehousing, and then the number of valid points is subtracted. Parking can be considered to be classified as prepaid parking. Further, as shown in FIG. 25, the receipt 260 describes the length of the effective parking time permitted to the user together with the end time of the effective parking time. Therefore, the user can know by what time the receipt must be delivered by looking at the receipt 260.

As shown in the lower part of FIG. 24, the fact that the user is permitted to park this time is notified not only to the user himself / herself but also to the above-mentioned plurality of persons in charge. The person in charge can be contacted by a method in which the management server 202 sends an e-mail containing information on parking permission individually for each person in charge (active contact), or a person who can view the management server 202. A method of posting information on parking permission on a limited homepage (homepage dedicated to vendors) and contacting the person in charge with information on parking permission by individual access from the person in charge to the homepage (passive). You may do it by contact).

[Settlement of additional charges for extended parking]

When the length of the actual continuous parking time by the user exceeds the above-mentioned length of the effective parking time (the continuous parking time permitted to the user at the time of warehousing in exchange for the consumption of the points used), that is, extended parking is performed. In this case, the user accesses the management server 202 at the time of leaving the parking lot 10, as illustrated in the sequence diagram in FIG.

After that, the user 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. Subsequently, the user transmits the time code 190 and the location code 192 displayed on the display 36 to the management server 202. The management server 202 estimates the user's delivery time by decrypting the received time code 190, and confirms the validity of the estimated delivery time by comparing it with the current time measured by the management server 202. do.

After that, the management server 202 calculates the length of time elapsed from the end time of the effective parking time recorded in the electronic parking ticket DB232 to the estimated delivery time as the length of the extended parking time. In addition, an additional parking fee is calculated that is commensurate with the length of the extended parking time. The management server 202 further calculates the number of points used corresponding to the amount of the additional parking fee, and calculates the number of remaining points by subtracting the current number of valid points by the number of points used. After that, the management server 202 issues a settlement receipt (not shown) and sends it to the user.

Next, the contents of the electronic parking ticket processing program will be described more specifically with reference to FIGS. 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. The first subprogram is a part for membership registration and issuance of an electronic parking ticket, the second subprogram is a part for permitting the use of an electronic parking ticket, and the third subprogram is an extended parking. It is a part to settle the parking fee at the time.

[Member registration]

At each execution of this electronic parking ticket processing program, first, in step S101 of FIG. 16, it is determined whether or not the user logged in to the management server 202 has transmitted the member registration request to the management server 202. .. This time, assuming that the user has transmitted the member registration request, the determination in step S101 is YES, and in step S102, the user information of the user himself / herself (for example, the user's name, address, etc.) transmitted from the user's communication device. The e-mail address, etc.) is received via the receiver 212.

Subsequently, in step S103, a unique user ID is assigned to the current user. After that, in step S104, the personal identification number set by the user himself / herself, which is transmitted from the communication device of the user, is received via the receiving unit 212. In step S104, further, other user information additionally transmitted from the user's communication device (for example, as illustrated in FIG. 19, the vehicle number, the vehicle model name, and the vehicle body color of the vehicle to be parked by the user). Etc.) are also received via the receiving unit 212.

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

[Issuance of electronic parking ticket]

The scenario in which the management server 202 receives the member registration request from the user has been described above. Instead, in the scenario in which the management server 202 receives the electronic parking ticket issuance request, the determination in step S101 is NO, and the determination in step S107 is The determination is YES, and the process proceeds to step S108.

In this step S108, whether or not the user this time is a member, that is, the qualification to receive the provision of this service, is determined by collating the user ID and PIN of the user himself / herself transmitted from the communication device of the user with the member DB 230. It is determined whether or not the user has. That is, personal authentication is performed, and if this personal authentication is established, data representing the number of points that the user wants to acquire this time, which is transmitted from the user's communication device, is transmitted via the receiving unit 212 in step S109. Received.

After that, in step S110, a fee (prepaid fee) that the user should pay to the parking lot manager in order for the user to acquire the number of points that the user wants to acquire is predetermined between the number of points and the fee. It is calculated by referring to the charge table and function formula that represent the relationship. Subsequently, in step S111, data representing a fee payable by the user is transmitted to the user. After that, in step S112, the user makes an electronic payment to the parking lot manager.

Subsequently, in step S113, it is determined whether or not the electronic payment has been completed normally. If the electronic payment by the user is not completed normally, the determination in step S113 becomes NO, and in step S113a, an issuance disapproval message indicating that the issuance of the electronic parking ticket 250 is not permitted is returned to the user. NS. This completes the current execution of this electronic parking ticket processing program.

On the other hand, this time, assuming that the electronic payment by the user is completed normally, the determination in step S113 is YES, and in step S114, the ticket unique to the electronic parking ticket 250 to be issued to the user this time. Numbers are given. The assigned ticket number is registered in the electronic parking ticket DB232 in association with the user ID, as illustrated in FIG. Subsequently, in step S115 of FIG. 16, the number of valid points is given to the user this time. In step S116, the number of valid points given is registered in the electronic parking ticket DB 232 in association with the user ID, as illustrated in FIG.

After that, 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 communication device of the current user. Is sent to. This completes the current execution of this electronic parking ticket processing program.

[Permission to use electronic parking ticket]

The scenario in which the management server 202 receives the electronic parking ticket issuance request from the user has been described above. Instead, in the scenario in which the management server 202 receives the electronic parking ticket use request, the determination in step S101 of FIG. 16 is also performed. The determination in S107 is also NO, the determination in step S118 in FIG. 17 is YES, and the process proceeds to step S119.

In step S119, personal authentication is performed based on the user ID and personal identification number of the user himself / herself transmitted from the communication device of the user in the same manner as in step S108 of FIG. When this personal authentication is established, in step S120, the receiving unit 212 contains one ticket number transmitted from the user's communication device and data for identifying the electronic parking ticket 250 that the user wants to use this time. Received via.

After that, in step S121, it is determined for the current user whether or not the electronic parking ticket 250 desired to be used by the current user is valid by collating the received ticket number with the electronic parking ticket DB232. .. If the electronic parking ticket 250 this time is not valid, in step S122, a usage disapproval message indicating that the use of the electronic parking ticket 250 is not permitted is returned to the user's communication device. This completes the current execution of this electronic parking ticket processing program.

On the other hand, this time, assuming that the electronic parking ticket 250 that the user wants to use is valid, in step S123, the time code 190 and the place code 192 transmitted from the user's communication device are received in the receiver 212. Received via. Subsequently, in step S124, the received time code 190 is decrypted with reference to the decryption table 234. Then, in step S125, the warehousing time of the user is estimated based on the decoding result. Subsequently, in step S126, it is determined whether or not the estimated warehousing time is within a predetermined permissible range determined with respect to the reception time when the management server 202 receives the time code 190, whereby the reception time is determined. It is determined whether the code 190 is valid or not.

This time, assuming that the received time code 190 is not valid, the determination in step S126 becomes NO, indicating that the user is not allowed to use the electronic parking ticket 250 (parking in the parking lot 10) in step S122. A disapproval message is sent to the user's communication device.

On the other hand, this time, assuming that the received time code 190 is valid, the determination in step S126 is YES, and in step S127, the user's desired parking condition is received from the user's communication device. The desired parking condition includes, for example, the length of parking time desired by the user.

Subsequently, in step S128, the number of points used to realize the received desired parking condition is calculated. The number of points used is calculated with reference to a predetermined conversion table, for example, so as to increase according to the length of parking time that the user desires free parking. After that, in step S129, the number of valid points is updated by subtracting the calculated number of points used this time from the current value of the number of valid points. The update of the number of valid points is reflected in the electronic parking ticket DB232.

Subsequently, in step S130, the effective parking time, which is the length of the parking time permitted to the user in exchange for the consumption of the number of points used, is calculated based on the received data representing the desired parking condition. After that, in step S130a, the receipt 260 illustrated in FIG. 25 is issued, including the meaning of informing the user that parking using the electronic parking ticket 250 is permitted. The data representing the issued receipt 260 is transmitted to the user's communication device.

Subsequently, in step S131, a process for notifying all the persons in charge of the received desired parking condition is performed (for example, the desired parking condition is individually notified to the person in charge by e-mail, or the desired parking is performed. Contact the person in charge by posting the conditions on the website dedicated to the vendor). This completes the current execution of this electronic parking ticket processing program.

[Settlement of parking fee for extended parking]

The scenario in which the management server 202 receives the electronic parking ticket usage request from the user has been described above. Instead, in the scenario in which the management server 202 receives the extended parking settlement request, the determination in step S101 of FIG. 16 is also performed. The determination in S107 is also NO, the determination in step S118 in FIG. 17 is NO, the determination in step S132 in FIG. 18 is YES, and the process proceeds to step S133.

Since the steps from step S133 to step S138 have the same execution contents as the steps from step S119 to step S124 shown in FIG. 17, duplicate description will be omitted.

In step S139 of FIG. 18, the departure time of the user is estimated based on the decoding result of the time code 190 transmitted from the communication device of the user in step S137. Subsequently, in step S140, it is determined whether or not the estimated delivery time is within a predetermined permissible range determined with respect to the reception time when the management server 202 receives the time code 190, whereby the reception time is determined. It is determined whether the code 190 is valid or not.

This time, assuming that the received time code 190 is not valid, the determination in step S140 is NO, indicating that the user is not allowed to use the electronic parking ticket 250 (parking in the parking lot 10) in step S136. A disapproval message is sent to the user's communication device.

On the other hand, this time, assuming that the received time code 190 is appropriate, the determination in step S140 is YES, and the effective parking recorded in the electronic parking ticket DB232 from the estimated delivery time in step S141. By subtracting the end time of the time, the length of the extended parking time is calculated. The estimated delivery time is recorded in the electronic parking ticket DM232 as illustrated in FIG.

Subsequently, in step S142, an additional parking fee of an amount commensurate with the calculated length of the extended parking time is calculated by referring to a predetermined conversion table. Then, in step S143, the number of points used corresponding to the calculated amount of the additional parking fee is calculated. Subsequently, in step S144, the number of remaining points is calculated by subtracting the current number of valid points by the calculated number of points used. The number of remaining points is reflected in the electronic parking ticket DB232. In the electronic parking ticket DB232, data indicating that the user has settled the additional parking fee by partially consuming the number of valid points is also recorded as illustrated in FIG. Then, in step S145, a settlement receipt (not shown) indicating that the additional parking fee has been settled by the user is issued, and data representing the settlement receipt is transmitted to the user's communication device.

Subsequently, in step S146, a process for notifying all the persons in charge that the additional parking fee has been settled by the user is performed according to step S131 of FIG. This completes the current execution of this electronic parking ticket processing program.

[Automatic sending of delivery reminder message]

In the present embodiment, as described above, the management server 202 is a user who parks using the electronic parking ticket 250, and at the time of warehousing, the warehousing time is also based on the warehousing time and the length of the effective parking time. We also know the estimated delivery time to be calculated. Therefore, as shown in FIG. 27, in the present embodiment, the management server 202 notifies the user who parks using the electronic parking ticket 250 that the scheduled delivery time is about to arrive, or the scheduled delivery time is reached. E-mail a separate message to the user's communication device to warn that the time has passed and to be aware that the extended parking will be settled whenever the scheduled departure time has passed. It is designed.

Specifically, as shown in FIG. 27, the management server 202 calculates the scheduled delivery time (end time of the effective parking time) for each user by referring to the data in the electronic parking ticket DB232, and further, the schedule. A time earlier than the set time (for example, 1 hour) from the delivery time is calculated as the delivery reminder time. When the delivery reminder time arrives, the management server 202 creates a delivery reminder message including a description that "the remaining time until the scheduled delivery time is less than one hour", and sends the delivery reminder message by e-mail. Send to the communication device of the corresponding user.

The delivery reminder message also includes, for example, a description stating, "If the scheduled delivery time has passed, the user must access the management server and settle the additional parking fee at the time of delivery." Is done. As a result, when the scheduled delivery time has passed, the user's attention is drawn so as not to forget to access the management server 202 and settle the additional parking fee at the time of delivery.

Further, the management server 202 determines for each user whether or not the scheduled delivery time has arrived, and if so, the additional parking fee is settled by the user by referring to the electronic parking ticket DB232. Determine if it is. If the settlement of the additional parking fee has not been completed, the management server 202 describes that "the scheduled delivery time has passed" and "at the time of delivery, the user accesses the management server to perform additional parking. It is necessary to settle the fee. " The management server 202 transmits the delivery reminder message to the communication device of the corresponding user by e-mail. The management server 202 sends the same delivery reminder message to the user who sent the delivery reminder message every time the set time (for example, 1 hour) elapses until the management server 202 is accessed and the additional parking fee is settled. Send repeatedly.

In addition, in the present embodiment, both normal parking and cardless parking are possible for the same parking lot 10, so that the ticket issuing machine 20 has not only its original ticketing function but also the time code 190. Is designed to have a time code generation / display function of generating the clock by encryption and displaying it on the screen of the display 36. However, according to the present invention, for example, only cardless parking is possible for the same parking lot 10, and instead of the ticket issuing machine 20, a clock 102 and an encryption device that encrypts the current time measured by the clock 102 ( For example, a time code generation that includes at least a computer that executes a program that generates a time code 190 by referring to the time encryption table) and a display 36 that displays the time code 190 generated by the encryption. It can be implemented in such a manner that the display device is installed in the parking lot 10.

As is clear from the above description, in the present embodiment, for convenience of explanation, the clock 102 constitutes an example of the “clock” in the above item (1), and among the control boards 34, the step shown in FIG. 14 The part that executes S32 constitutes an example of the "encryption unit" in the same paragraph, the display 36 constitutes an example of the "display unit" in the same paragraph, and the time code 190 of the ticket issuing machine 20 The part that generates and displays the above constitutes an example of the "time code generation / display device for parking lots" in the same paragraph, and the display 36 constitutes an example of the "display unit" in the above paragraph (2) and the above. It can be considered that each example of the "time code display device for parking lot" according to the item (5) is configured.

Further, in the present embodiment, for convenience of explanation, steps S120 and S123 shown in FIG. 17 constitute an example of the “reception step at the time of warehousing” in the above paragraph (1) or (2), and are also shown in the figure. Steps S124 to S126 constitute an example of the “receipt time validity determination step” in the same paragraph, and step S130a shown in the figure constitutes an example of the “parking permission step” in the same paragraph, and transmission is performed. It can be considered that the unit 210 and the receiving unit 212 jointly form an example of the “communication unit” in the same paragraph.

Further, in the present embodiment, for convenience of explanation, steps S134 and S137 shown in FIG. 18 constitute an example of the “delivery time receiving step” in the above item (3), and steps S138 to S140 shown in the same figure. However, it can be considered that an example of the “delivery time validity determination process” in the same paragraph is configured, and step S141 shown in the figure constitutes an example of the “parking time calculation process” in the same paragraph. Is.

Further, in the present embodiment, for convenience of explanation, step S107 shown in FIG. 16 constitutes an example of the “issuing request receiving step” in the above item (4), and steps S110 to S117 shown in FIG. It can be considered that it constitutes an example of the "electronic parking ticket issuing process" in the same section.

<Second Embodiment>

Next, a parking lot management method according to an exemplary second embodiment of the present invention will be described. However, with respect to the elements common to the first embodiment, by quoting using the same reference numerals or names, duplicate explanations will be omitted, and only different elements will be described in detail.

In the first embodiment, the user who wants to perform cardless parking specifies the length of the scheduled parking time for which he / she wants to park this time prior to the parking (at the time of warehousing) each time he / she tries to use the parking lot 10. However, out of the number of valid points, the number of points corresponding to the prepaid parking fee of the amount commensurate with the length of the scheduled parking time is consumed. When the user leaves the parking lot 10 before the scheduled parking time elapses, that is, when the extended parking is not performed, it is not necessary to access the management server 202 at the time of leaving the parking lot. That is, the user does not need to access the management server 202 at the time of leaving the garage unless the extended parking is performed. As a result, unless the user performs extended parking, communication with the management server 202 is only required at the time of warehousing for each parking, and the user's trouble is saved.

However, in the first embodiment, even if the actual parking time of the user is shorter than the scheduled parking time, the same number of points as when parking as much as the scheduled parking time is consumed.

On the other hand, in the present embodiment, the user has to take the trouble of accessing the management server 202 not only at the time of warehousing but also at the time of warehousing, while consuming the number of points at the time of warehousing. Instead, the parking time is calculated collectively at the time of delivery and the number of points is consumed, so that the number of points consumed is calculated exactly according to the actual parking time. As a result, according to the present embodiment, the user does not have to consume a wasteful number of points, which is economical.

Next, a parking lot management method according to the present embodiment will be described with reference to FIGS. 28 to 33, and the electronic parking ticket processing program executed on the management server 202 to execute this method is shown in FIG. The same as the first subprogram (member registration and issuance of the electronic parking ticket 250) shown in FIG. 17, the fourth subprogram replacing the second subprogram (permission to use the electronic parking ticket 250) shown in FIG. 17, and FIG. Includes a fifth subprogram that replaces the third subprogram (payment of additional parking fees for extended parking) shown in.

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

Hereinafter, the electronic parking ticket processing program in the present embodiment will be described, but the process common to the first embodiment will be omitted in duplicate, and only the different processes will be described in detail.

[Parking permission using electronic parking ticket]

The user accesses the management server 202 as illustrated in the sequence diagram in FIG. 30 in order to request the parking manager for permission to park using the electronic parking ticket 250 at the time of entering the parking lot 10. .. After that, the user transmits the ticket number assigned to the electronic parking ticket 250 to be used this time to the management server 202, and the management server 202 confirms the validity of the electronic parking ticket 250. Subsequently, the user transmits the time code 190 and the location code 192 displayed on the display 36 to the management server 202. The management server 202 estimates the user's warehousing time by decrypting the received time code 190, and confirms the validity of the estimated warehousing time by comparing it with the current time measured by the management server 202. do.

If the estimated warehousing time is reasonable, the management server 202 permits the user to park and sends a parking permission message to the user. The management server 202 notifies not only the user himself but also the above-mentioned plurality of persons in charge of the fact that the user is permitted to park this time in the same manner as in the first embodiment.

To execute this process, the management server 202 executes the fourth subprogram shown in FIG. 28. When the fourth subprogram is executed, first, in step S301, it is determined whether or not a parking permission request has been received from the user's communication device. This time, assuming that the parking permission request is 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 it is determined in step S126 that the warehousing time estimated by decryption of the time code 190 received this time from the user is appropriate, a parking permission message indicating that the user is permitted to park is displayed in step S302. It is returned to the user's communication device. Then, in step S303, the user is informed to all the persons in charge of the information indicating that the parking lot 10 is permitted to park. This completes the current execution of this fourth subprogram.

[Payment of parking fee for parking using electronic parking ticket]

At the time of leaving the parking lot 10, the user accesses the management server 202 as illustrated in the sequence diagram in FIG. 31 in order to settle the parking fee. After that, the user 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. Subsequently, the user transmits the time code 190 and the location code 192 displayed on the display 36 to the management server 202. The management server 202 estimates the user's delivery time by decrypting the received time code 190, and confirms the validity of the estimated delivery time by comparing it with the current time measured by the management server 202. do.

After that, in step S402 shown in FIG. 29, the management server 202 calculates the length of the parking time by subtracting the warehousing time recorded in the electronic parking ticket DB232 from the estimated warehousing time. The estimated delivery time is recorded in the electronic parking ticket DM232 as illustrated in FIG.

Subsequently, in step S403, an amount of parking fee commensurate with the calculated length of parking time is calculated by referring to a predetermined conversion table. Then, in step S404, the number of points used corresponding to the calculated amount of the parking fee is calculated. Subsequently, in step S405, the number of remaining points is calculated by subtracting the current number of valid points by the calculated number of points used. The number of remaining points is reflected in the electronic parking ticket DB232. In the electronic parking ticket DB232, data indicating that the user has settled the parking fee by partially consuming the number of valid points is also recorded as illustrated in FIG. Then, in step S406, a receipt 270 indicating that the parking fee has been settled by the user is issued, and data representing the receipt 270 is transmitted to the user's communication device.

Subsequently, in step S407, a process for notifying all the persons in charge that the parking fee has been settled by the user is performed. This completes the current execution of this fifth subprogram.

[Automatic sending of delivery reminder message]

In the present embodiment, as described above, the management server 202 knows the warehousing time for the user who parks using the electronic parking ticket 250 at the time of warehousing, but is different from the first embodiment. , I don't know the scheduled delivery time. However, the management server 202 can sequentially calculate the elapsed time from the warehousing time to the current time, that is, the parking time of the user up to the current time, and further, the number of points used corresponding to the length of the parking time is also sequentially calculated. Can be calculated. Then, even if the management server 202 tries to consume the number of points used at that time at each time, the number of remaining points is insufficient in relation to the length of the parking time, so the parking fee cannot be fully settled. Can be noticed.

Therefore, in the present embodiment, as shown in the sequence diagram in FIG. 33, the management server 202 sequentially calculates the length of the parking time for each user whose parking fee has not been settled, and further, the length of the parking time is calculated. Also calculate the number of points used for the length of parking time. The management server 202 further determines whether or not the number of remaining points is insufficient in relation to the length of the parking time even if the number of used points is to be consumed at that time. When the number of remaining points is insufficient, the management server 202 creates a delivery reminder message for prompting the user to leave the goods promptly, and the delivery reminder message is communicated by the corresponding user by e-mail. Send to device.

As is clear from the above description, in the present embodiment, for convenience of explanation, steps S120 and S123 shown in FIG. 28 constitute an example of the "reception step at the time of warehousing" in the above (1) or (2). Further, steps S124 to S126 shown in the figure constitute an example of the “receipt time validity determination step” in the same paragraph, and step S302 shown in the figure constitutes an example of the “parking permission step” in the same paragraph. It is possible to think that it constitutes.

Further, in the present embodiment, for convenience of explanation, steps S134 and S137 shown in FIG. 29 constitute an example of the “delivery time receiving step” in the above item (3), and steps S138 to S140 shown in the same figure. However, it can be considered that the step S402 shown in the figure constitutes an example of the "parking time calculation process" in the same paragraph. Is.

In addition, in some of the embodiments described above, the ticket issuing machine 20 is a self-supporting type that does not have a function of communicating with the parking lot manager (management server 202), and is a ticket issuing machine. Although advantageous in minimizing the equipment cost of 20, the present invention can be implemented in a manner in which the ticket issuing machine 20 has its communication function.

In this aspect, for example, the clock 102 and the time encryption unit that encrypts the current time measured by the clock 102 (the computer refers to the time encryption table shown in FIG. 13B) and the time code. The part that generates 190) is mounted on the management server 202, and the management server 202 measures the current time, encrypts it, generates a time code 190, and transfers the time code 190 to the ticket issuing machine 20. Then, the display 36 of the ticket issuing machine 20 displays the received time code 190. According to this aspect, the ticket issuing machine 20 does not have to have the clock 102 and the time encryption unit instead of having the communication function.

Although some embodiments of the present invention have been described in detail with reference to the drawings, these are examples, and are based on the knowledge of those skilled in the art, including the embodiments described in the [Summary of Invention] column. It is possible to carry out the present invention in other forms with various modifications and improvements.

Claims (7)

A parking lot management system that manages parking lots that are both ticketless and cashless without using physical parking tickets.
Parking-related information related to parking for a user who is installed in the parking lot and uses the parking lot and includes information capable of identifying the position of the parking lot without using a physical parking ticket. The display part to display and
A management server that manages the parking lot in a remote location,
A communication device of a user in the parking lot, including a parking settlement-related information displayed on the display unit and / or another parking- related information related thereto is transmitted to the management server.
The management server is a parking lot management system having a settlement unit for electronically settlement the parking fee charged to the user based on the parking- related information received from the communication device. The parking- related information is represented as an image.
The communication device includes an image reader, parking management according to claim 1 for transmitting the parking related information acquiring the parking related information by reading the image by using the image reader to the management server system. The parking lot management system according to claim 1 or 2, wherein the parking-related information includes a location code unique to the parking lot. The parking lot management system according to any one of claims 1 to 3, wherein the parking-related information includes information that differs depending on the parking lot or information that can uniquely identify any of the parking lots in order to identify the parking lot. .. A program for operating a computer as a communication device according to any one of claims 1 to 4. A program for operating a computer as a management server according to any one of claims 1 to 4. A recording medium in which the program according to claim 5 or 6 is recorded in a computer-readable manner.

Images