JP6348618B2 - Cardless parking management method - Google Patents

Description

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

  Parking lots having a plurality of parking positions for vehicles are already widely used. This type of parking lot is classified in terms of the method of transporting the vehicle to the parking position. The user drives the vehicle by itself and transports it to the parking position, and mechanically moves the pallet and cage to move the vehicle. It is classified as a mechanical type that is transported to a parking position. Moreover, the parking lot may be lent to the user free of charge, or may be rented for a fee. Toll parking lots are classified into monthly and hourly lending (including “daily lending”) in terms of the length of time lending to users.

  If rented parking lots are classified in terms of a parking fee payment method, a prepayment method in which a user pays a parking fee prior to the start of parking (however, there is a possibility of paying a shortage of the parking fee at the time of delivery). And a post-payment method in which the user pays the parking fee together at the end of parking.

  In addition, if you categorize the time-rented parking lot in terms of its management method, the person in charge who manages and monitors the parking lot is resident in the parking lot at the site, and the person who is not resident in the parking lot It is classified as an unmanned system in which a person is dispatched to a parking lot on the spot.

  As a publicly known document disclosing this type of parking lot and facilities (including a ticketing machine) installed in the parking lot, for example, Patent Literature 1 exists.

  Patent Document 1 discloses a prepaid unmanned parking lot. In this parking lot, when a parking card is inserted, a card issuing machine that issues a parking card recording the time allowed for parking for a fee, a garage gate that is always closed, and a garage entrance are installed. And a warehousing management device that opens the warehousing gate on condition that the parking card is appropriate. Furthermore, in this parking lot, an exit gate that is always closed, and an exit management device that is installed at the exit and opens the exit gate on condition that the parking card is appropriate when a parking card is inserted. And are installed.

  Thus, patent document 1 is disclosing the technique in which a user parks using a real card (for example, physical parking ticket), when a user parks a motor vehicle in an unattended paid parking lot. .

  On the other hand, patent document 2 is disclosing the technique in which a user parks by a cardless system, when a user parks a motor vehicle in an unattended paid parking lot.

JP 2006-146325 A JP-A-8-111000

  According to the technique disclosed in Patent Document 2, since the user can park in the parking lot without using a card, there is an advantage that there is no need to worry about loss of the card. However, in order to implement the technique disclosed in Patent Document 2, special and expensive equipment is installed in both the car and the parking lot in order to obtain information specific to the car to be parked in the parking lot. For those who own the parking lot and those who manage the parking lot, the cost of the equipment itself, the cost and man-hours required to install the equipment in the parking lot, and maintenance and inspection of the equipment There is a drawback that the cost and man-hour 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 enters or leaves the parking lot.

Against the background of the above knowledge, the present invention is a technique for managing a parking lot, and an object of the present invention is to improve a technique for a user to park in a cardless manner .

In order to solve this problem , 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, whereby the parking lot manager A cardless parking management method for purchasing an electronic parking ticket and allowing the user to park in the parking lot selected by the user using the electronic parking ticket,
The management server receiving 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 parking fee of the amount corresponding to the length of the scheduled parking time designated by the user is paid by the user, the management server issues the electronic parking ticket to the user, and the electronic parking ticket is Transmitting data for display to the user's mobile terminal;
The management server receives from the user's mobile terminal to start parking at the parking lot using the issued electronic parking ticket when the user enters the parking lot;
After the reception, the management server determines whether or not the user's electronic parking ticket is valid. If the management server determines that the user's electronic parking ticket is not valid, information indicating that the use of the electronic parking ticket is not permitted Sending to the terminal;
When the length of the actual continuous parking time by the user exceeds the length of the scheduled parking time, when the user leaves the parking lot, the management server receives from the user's mobile terminal; and
After the reception, the management server calculates an additional parking fee corresponding to the excess length of time, and when the user settles the additional parking fee, data indicating that the settlement has been performed is stored in the user's mobile phone. Sending to the terminal and
A cardless parking management method is provided.

Further , according to one aspect of the present invention, a parking lot that is installed in each of a plurality of parking lots and displays a time code in which the current time is encrypted differently from a time code displayed in another parking lot. A time code display device,
The time code is used by an administrator who manages the plurality of parking lots in order to obtain the fact that the user has entered or exited the corresponding parking lot,
The time code is provided with a parking time code display device having a place discriminating power that can uniquely identify the parking place where the time code is displayed.

According to another aspect of the present invention, for each of a plurality of parking lots, for a parking lot that displays a time code in which the current time is encrypted differently from a time code displayed in another parking lot. A time code display method,
The time code is used by an administrator who manages the plurality of parking lots in order to obtain the fact that the user has entered or exited the corresponding parking lot,
The time code is provided with a parking time code display method having a place discriminating power that can uniquely identify a parking place where the time code is displayed.

According to still another aspect of the present invention, in a parking lot, a parking time code display device that displays a time code in which the current time is encrypted,
The time code can be read and reproduced by a user of the parking lot as a known letter, number, symbol or figure, or a combination thereof, and cannot be decoded by the user but can be decoded by the parking lot manager. A parking lot time code display device capable of restoring the information representing the current time by decoding is provided.

  The following aspects are obtained by the present invention. Each aspect is divided into sections, each section is given a number, and is described in a form that cites other section numbers as necessary. This is to facilitate understanding of some of the technical features that the present invention can employ and combinations thereof, and the technical features that can be employed by the present invention and combinations thereof are limited to the following embodiments. Should not be interpreted. That is, it should be construed that it is not impeded to appropriately extract and employ the technical features described in the present specification as technical features of the present invention although they are not described in the following embodiments.

  Further, 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 from the technical features described in the other sections. It should not be construed as meaning, but it should be construed that the technical features described in each section can be appropriately made independent depending on the nature.

(1) A parking lot management method for managing a parking lot,
In the parking lot,
Watch and
A time code that allows a user of the parking lot to read and reproduce the current time measured by the clock as a known character, number, symbol, figure, or a combination thereof by encryption. Can not be decrypted but the administrator of the parking lot converts to something that can be decrypted, and
A parking time code generation / display device including a display unit for displaying the time code generated by the encryption unit, and
The parking lot management method is
Information for specifying the electronic parking ticket transmitted through a communication device in order to perform parking in the parking lot using an electronic parking ticket when the user enters the parking lot; The receiving process at the time of warehousing which receives in the communication part the time code displayed on the display part at the time of warehousing to the parking lot,
The processor decodes the time code received at the time of warehousing with reference to the decryption table, estimates the time represented by the received time code as the warehousing time based on the decryption result, and the estimated warehousing time Is determined to determine whether or not the processor is within a predetermined allowable range determined with respect to the reception time when the time code is received, thereby determining whether or not the estimated storage time is appropriate A time validity judgment process;
A parking lot management method including: a parking permission step for permitting the user to use the parking lot when the processor determines that the estimated entry time is appropriate.

  Throughout this specification, the term “electronic parking ticket” refers to a virtual parking ticket that does not actually exist, and in order for the user to use the electronic parking ticket, the description items on the electronic parking ticket are transferred to other media. It means a parking ticket that is not required to be printed or displayed on the card and presented to the other party.

(2) A parking lot management method for managing a parking lot,
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 a known character, number, symbol or figure, or a combination thereof, There is a display unit that displays what the parking lot manager can decrypt but cannot decrypt,
The parking lot management method is
Information for specifying the electronic parking ticket transmitted through a communication device in order to perform parking in the parking lot using an electronic parking ticket when the user enters the parking lot; The receiving process at the time of warehousing which receives in the communication part the time code displayed on the display part at the time of warehousing to the parking lot,
The processor decodes the time code received at the time of warehousing with reference to the decryption table, estimates the time represented by the received time code as the warehousing time based on the decryption result, and the estimated warehousing time Is determined to determine whether or not the processor is within a predetermined allowable range determined with respect to the reception time when the time code is received, thereby determining whether or not the estimated storage time is appropriate A time validity judgment process;
A parking lot management method including: a parking permission step for permitting the user to use the parking lot when the processor determines that the estimated entry time is appropriate.

(3) Furthermore,
Information for identifying the electronic parking ticket transmitted by the user via the communication device when leaving the parking lot, and a time code displayed on the display unit when leaving the parking lot And at the time of delivery receiving step to receive in the communication unit,
The processor decodes the time code received at the time of delivery with reference to the decryption table, and based on the decryption result, estimates the time represented by the received time code as the delivery time. 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. A delivery time validity judgment process for judging,
When it is determined by the processor that the estimated delivery time is appropriate, the length of elapsed time from the estimated delivery time to the estimated delivery time is set as the parking time by the user. The parking lot management method according to (1) or (2), including a parking time calculation step to calculate.

(4) Furthermore,
An issuance request receiving step for receiving, in the communication unit, an issuance request for requesting the parking manager to issue the electronic parking ticket transmitted by the user via the communication device;
In response to the received issuance request, the processor issues the electronic parking ticket to the user and transmits it to the user's communication device on condition that the user prepays a predetermined amount of charge. The parking lot management method according to any one of (1) to (3), including an electronic parking ticket issuing step.

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

In order to solve the problem, according to one aspect of the present invention, the user accesses the management server of the parking lot manager from an arbitrary location via the mobile terminal, and thereby, from the parking lot manager. A cardless parking management method for purchasing an electronic parking ticket and allowing the user to park in the parking lot selected by the user using the electronic parking ticket,
When the user's portable terminal transmits an issuance request to request the parking lot manager to issue the electronic parking ticket, the management server receives the issuance request from the user's portable terminal. When,
After the reception, when the parking fee of the amount corresponding to the length of the scheduled parking time designated by the user is paid by the user, the management server issues the electronic parking ticket to the user, and the electronic parking ticket is Transmitting data to the user's mobile terminal that includes data for display and includes electronic parking ticket specifying data for specifying the electronic parking ticket;
When the user's portable terminal transmits a use request to start parking at the parking lot using the issued electronic parking ticket when the user enters the parking lot, the management server Receiving the usage request from a mobile terminal of
After the reception, when the user's mobile terminal transmits parking ticket specifying data for specifying the electronic parking ticket, the management server receives the electronic parking ticket specifying data received from the user's mobile terminal, and the electronic parking The electronic parking ticket that the user desires to use this time is verified by comparing data that is unique to the ticket and registered in the memory of the management server, and determining whether or not it is successful. Determining whether it is valid, and determining that it is not valid, a step of transmitting to the user's mobile terminal information indicating that the user does not permit the use of the electronic parking ticket that the user wishes to use this time;
When the length of the actual continuous parking time by the user exceeds the length of the scheduled parking time, when the user's mobile terminal transmits a settlement request when the user leaves the parking lot, the management server Receiving the payment request from a mobile terminal of;
After the reception, the management server calculates an additional parking fee corresponding to the excess length of time, and when the user settles the additional parking fee, data indicating that the settlement has been performed is stored in the user's mobile phone. Sending to the terminal and
A cardless parking management method is provided.
The following aspects are obtained by the present invention. Each aspect is divided into sections, each section is given a number, and is described in a form that cites other section numbers as necessary. This is to facilitate understanding of some of the technical features that the present invention can employ and combinations thereof, and the technical features that can be employed by the present invention and combinations thereof are limited to the following embodiments. Should not be interpreted. That is, it should be construed that it is not impeded to appropriately extract and employ the technical features described in the present specification as technical features of the present invention although they are not described in the following embodiments.

(7) A management server that is communicably connected to the communication device of the user via a communication network, and that 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).

  The time code in the present invention is time-dependent because it is generated differently at different times on the same day.

  In addition, the time code is generated so that it cannot be deciphered by any user of the parking lot, so that the user does not actually enter or leave the parking lot at any time, or The time when the display should display at a certain time, trying to impersonate a user who entered or left the parking lot at a certain time, even though it actually entered or left the parking lot at a different time Even if the user tries to predict the code, the user cannot obtain a genuine time code. Therefore, the time code has confidentiality for the user.

  Furthermore, the time code is only displayed on the display section of the parking lot where the user is actually parking or parked, so that the user can use the parking lot in order to obtain the necessary time code. Have to go to. Therefore, the time code has location dependency.

  In this way, the time code has time dependency, confidentiality to the user, and location dependency. Therefore, the time code actually viewed by the user on the display unit of the parking lot is displayed on the display unit. As long as it is transmitted to the parking lot manager at a time that is not significantly delayed from the time displayed in the, the time code is a powerful proof for supporting the fact that the user actually entered or exited the parking lot.

  Based on such knowledge, according to the present invention, when the user enters the parking lot, in order to perform parking in the parking lot using the electronic parking ticket, information for specifying the electronic parking ticket and When the time code displayed on the display unit is transmitted via the communication device when entering the parking lot, the parking lot manager receives the information and the time code.

  Furthermore, the parking lot manager interprets the time code received at the time of the warehousing by referring to the decryption table, and based on the decryption result, estimates the time represented by the received time code as the warehousing time, It is determined whether or not the estimated warehousing time is within a predetermined allowable range determined with respect to the reception time at which the parking lot manager has received the time code, so that the estimated warehousing time is reasonable. It is determined whether or not.

  Furthermore, if the parking lot manager determines that the estimated storage time is appropriate, the parking lot manager permits the user to use the parking lot.

  Therefore, according to the present invention, it is possible to provide a service that allows 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 the parking lot management method according to the first exemplary embodiment of the present invention. FIG. 2 is a front view showing the ticket issuing machine shown in FIG. FIG. 3 is a perspective view 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 showing a ticket issuing / settlement program executed by the computer shown in FIG. 6A to 6D are front views showing a plurality of images displayed on the screen of the display shown in FIG. FIG. 7A is a front view showing an example of a parking ticket and a receipt issued after payment of a prepaid parking fee by the ticket issuing machine shown in FIG. 2, and FIG. 7B is a ticket issuing shown in FIG. It is a front view which shows an example of the receipt issued after payment of an additional parking fee with a machine. Fig. 8 (a) is a longitudinal sectional view showing the parking ticket shown in Fig. 7 (a) in a state immediately after issuance, and Fig. 8 (b) is a part of the parking ticket that is peeled off and bent. It is the longitudinal cross-sectional view shown in the state. Fig.9 (a) is side sectional drawing which shows the parking ticket shown in FIG.7 (a) in the state affixed on the back surface of the windshield of a parked vehicle, FIG.9 (b) shows the parking ticket. It is a perspective view shown in the state where a part of the display sheet was peeled off from the separator and bent. FIG. 10 is a perspective view showing a state where the parking ticket shown in FIG. 7A is affixed to the back surface of the windshield of the parked vehicle. FIGS. 11A to 11C show examples of the configuration of encrypted data printed on the receipts shown in FIGS. 7A and 7B, the corresponding actual data, and the actual data to the encrypted data. It is a figure for demonstrating a conversion process. FIG. 12 shows how the user communicates the encrypted data printed on the receipts shown in FIGS. 7 (a) and 7 (b) to a parking lot manager at a remote location using his / her mobile phone, It is a perspective view for demonstrating that the parking lot manager converts the received encryption data into real data. FIGS. 13A to 13C are portions related to the parking lot management method in the ticket issuing machine shown in FIG. 4, and are diagrams for conceptually explaining processing of time code generation and display. It 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 processing (time code generation and display) shown in FIGS. 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 showing a first subprogram which is a part of the electronic parking ticket processing program executed in the management server shown in FIG. FIG. 17 is a flowchart conceptually showing a second subprogram which is another part of the electronic parking ticket processing program executed in the management server shown in FIG. 15. FIG. 18 is a flowchart conceptually showing a third subprogram which is still another part of the electronic parking ticket processing program executed in the management server shown in FIG. FIG. 19 is a diagram conceptually showing the member DB shown in FIG. FIG. 20 is a diagram conceptually showing the electronic parking ticket DB shown in FIG. FIG. 21 is a diagram illustrating 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 member 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 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 paying a parking fee during extended parking, which is performed by executing the electronic parking ticket processing program. FIG. 27 is a sequence diagram for explaining a process called urging reminder executed in the management server shown in FIG. FIG. 28 shows a second replacement of the second subprogram shown in FIG. 17 among the electronic parking ticket processing programs executed in the management server in order to execute the parking lot management method according to the second exemplary embodiment of the present invention. 4 is a flowchart conceptually showing four subprograms. FIG. 29 is a flowchart conceptually showing a fifth subprogram for replacing the third subprogram shown in FIG. 18 among the electronic parking ticket processing programs in 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 charge settlement 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 reminder executed in 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 is a plan view showing a parking lot 10 managed by the parking lot management method according to the first exemplary 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 “accounting machine”) 20 is parked in the vicinity of the only entrance / exit 12 (which is also an entrance and exit) of the parking lot 10. It is installed as a central ticketing machine in common with the location. This parking lot 10 has no full-time staff who is resident and manages it, and a user who is a driver is an unmanned system in which a parking fee is paid 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 there. This is a parking ticket that can be parked multiple times and is equivalent to a coupon ticket for transportation such as trains and buses). 10 can be parked.

  However, in this embodiment, instead of such parking method, every time the user intends to use this parking lot 10, prior to the parking (at the time of warehousing), the user wants to perform the current parking. By specifying the length of time and paying the ticketing machine 20 as a prepaid parking fee for an amount corresponding to the parking fee, a parking ticket printed on a paper medium (ie, a physical ticket, a real ticket or a Card) can be purchased from the ticketing machine 20 and parked in the parking lot 10 using the paper parking ticket.

  That is, in the present embodiment, the user can perform new parking (cashless and cardless) using an electronic parking ticket (virtual ticket) that can be purchased by online access to a parking lot manager from an arbitrary location. Yes, hereinafter referred to as “cardless parking”))) and normal parking using physical parking tickets that can only be purchased from the ticketing machine 20 installed in the parking lot 10 (both cash and physical tickets) Can be selected as desired according to preference.

  In addition, in addition to the definition of the term “vehicle”, in this “Mode for Carrying Out the Invention” column, the term “vehicle” means only an automobile, but other parts of the present specification. In this context, the term “vehicle” should be interpreted as a term encompassing not only automobiles but also all kinds of moving bodies such as bicycles and motorcycles.

  There are two types of parking areas on the site of the parking lot 10. It is based on a premise for a section for lending a parking space to a user of each vehicle on a daily basis (a temporary storage section or a daily lending section) and for each vehicle user on a monthly basis. It is a section for renting a parking space (monthly section). The ticket issuing machine 20 is used for a temporary deposit section. Hereinafter, the term “parking lot 10” means only a temporary deposit area, that is, an area where the ticketing machine 20 is used in the parking lot 10.

  In order to use the parking lot 10, a driver who is a user drives his / her vehicle, enters the entrance / exit 12 from an adjacent road, continues to drive and passes through the ticketing machine 20, and further Drive to one of the parking spaces (parking positions) you have chosen and park there.

  When carrying out the normal parking, the user stops his / her vehicle in one of the parking spaces, then gets out of his / her vehicle and walks to the ticketing machine 20 at the entrance / exit 12 and parks there. Pay the fee to the ticket issuing machine 20.

  2 is a front view of the ticketing machine 20, FIG. 3 is a perspective view of the ticketing machine 20 with the door 24 open, and FIG. Twenty component configurations are shown in a block diagram. FIG. 5 conceptually shows a ticket issuing / settlement program executed by the computer 100 in the control board 34 shown in FIG. 6A to 6D are front views showing a plurality of images displayed on the screen of the display 36 shown in FIG.

  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. Thereafter, as shown in FIGS. 9 and 10, the user affixes the parking ticket 80 to the back surface of the windshield 110 of his / her own vehicle (which is an example of the “window glass” of the vehicle). Since the parking ticket 80 is placed in the room of 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 example, a delivery gate device or a wheel) for preventing the vehicle from leaving (blocking the exit from the parking lot 10). There is no stopping device (for example, a flap type or a retractable type), and the user can freely select one of the plurality of parking positions and park his / her vehicle (selection). The parked parking position is not monitored by the ticketing machine 20). The ticket issuing machine 20 is used for the parking lot 10 configured as described above.

  Here, the ticket issuing machine 20 will be described more specifically. This ticket-issuing machine 20 has a charge settlement function but does not have a change function or a communication function. This ticket-issuing machine 20 requests that the user pay the parking fee only with coins, not banknotes. In addition, the ticket issuing machine 20 can input a user identification number, input vehicle identification information (for example, a vehicle number) on the user's vehicle, and specify what a user selects from a plurality of parking positions. , Do not request.

  As shown in FIG. 2, the ticket issuing machine 20 includes a ticket issuing button 70 and a fee settlement button 74. When the user presses the ticketing button 70 after paying the prepaid parking fee prior to the start of parking, the ticketing machine 20 includes a parking ticket 80 (see FIG. 7A) indicating that parking is permitted, and prepaid parking. It has a ticket issuing function for issuing a receipt 81a (see FIG. 7A) indicating that the fee has been settled. When the user presses the charge settlement button 74 after paying the additional parking fee after the parking is completed, the ticket issuing machine 20 receives a receipt 81b (see FIG. 7B) indicating that the additional parking fee has been settled. ) Is issued.

  In the present embodiment, the two-sheet parking ticket issued after payment of the prepaid parking fee is a two-sheet parking ticket 80 and a receipt 81a, but the user uses the parking ticket 80 and the receipt 81a. Only the parking ticket 80 is separated from each other and placed 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 end the effective parking time at any time away from the parked vehicle. In order to be able to refer to the time, it is convenient for the user to carry this receipt 81a.

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

  As shown in FIG. 3, the ticket issuing machine 20 is a printer 40 that 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 comprised so that. 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 on which a continuous sheet before printing is wound and stored. The printer 40 performs printing on a continuous sheet fed from the roller 42 by one length. After the printing is completed, the printer 40 cuts the continuous sheet from time to time with a cutter (not shown), and after the prepaid parking fee is paid, the parking ticket 80 and the receipt 81a are bound, and additional parking is performed. After payment of the fee, the receipt 81b for one sheet is cut off. However, as shown in FIG. 7 (a), a cut line 89 is formed between the parking ticket 80 and the receipt 81a, which are spelled in two sheets, and the user can move 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 blade (not shown), and moves the cutting blade in the width direction of the continuous sheet to cut the continuous sheet in the width direction. 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, a coin selector (determination of the type of inserted coin, and whether or not the inserted coin is a forged coin. ) 54 and a coin return port 56. Among the inserted coins, those that have not been returned to the user from the coin return slot 56 are accommodated in the safe 32. As shown in FIG. 4, a control board 34 is connected to the coin selector 54 so as to be able to perform data communication. The control board 34 is connected to the coin selector 54 by the type of coins inserted (in coin units and counterfeit coins). And a signal indicating the number of images are received.

  As shown in FIG. 2, on the front surface of the door 24, a transmission window 60 through which display light from a 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 slot 56. A parking ticket 80 printed by the printer 40 and discharged, and a discharge port 64 for discharging the receipts 81a and 81b. The transmissive window 60 also has a function of mechanically protecting the display 36 by preventing direct access to the display 36 from the outside.

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

  Each of the ticket issuing button 70 and the fee settlement button 74 is configured as an actual physical switch, but is not limited to this, for example, a virtual switch (displayed on the screen of the display 36) ( For example, it may be configured as a button, key, icon).

  The control board 34 is composed mainly of the 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 and the date and time when the fee settlement button 74 is pressed). The control board 34 further incorporates a memory 104. The memory 104 stores an encryption table, which will be described later, in a state where only authorized persons can rewrite it.

  In addition, the control board 34 can be configured to realize the same function as the computer 100 by a sequencer (sequence control).

  In addition, 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 the like, and the electric power from the power source is supplied to each electrical / electronic component in the ticketing machine 20, thereby operating the ticketing machine 20. This power supply unit additionally has, for example, a backup circuit having a power storage function, and even if the power supply from the power supply is temporarily stopped, the influence thereof 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 ticket issuing / settlement program shown in FIG. 5 is executed by the computer 100, first, an initial screen shown in FIG. 6A is displayed on the screen of the display 36 in step S1. Next, in step S2, based on the signal from the coin selector 54, it is determined whether or not a user has inserted coins. If no coin has been inserted, the process returns to step S2, but if a coin has been inserted, in step S3, the total amount of coins that have been inserted by the user is calculated as the amount to be inserted.

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

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

  Thereafter, in step S5, a coin-inserting 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 ticket issuing button 70 has been pressed. If the ticket issuing button 70 has not been pressed yet, it is determined in step S7 whether or not the fee settlement button 74 has been pressed. If the fee settlement button 74 has not been pressed yet, the process returns to step S2.

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

  When the ticket issuing button 70 is pressed, the parking ticket / receipt issue 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 user operating the ticketing button 70 is displayed as the amount of the prepaid parking fee. In this case, the parking time calculated in the preceding step S4 means an effective parking time.

  Subsequently, in step S9, the time when the user enters 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 The 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 can be decrypted by referring to the encryption table. It is converted into encrypted data 130 that cannot be pronounced uniquely but cannot be pronounced. Encryption is performed, whereby encrypted data 130 is created.

  In the present embodiment, as shown in FIG. 11A, the encrypted data 130 is defined by symbols of 9 digits arranged in a line (the number of digits may be larger or smaller than that). Has been. The symbol of each digit is selected, for example, as one of 10 numbers from 0 to 9 and a plurality of alphabets. The multi-digit symbols are divided into a plurality of groups and printed on the receipt 81a. Adjacent groups are connected with a hyphen so that the user can pronounce the multi-digit symbols at once. Instead of a few breaks, you can pronounce more easily and accurately.

  As shown in FIG. 11B, an example of a general configuration of actual data (notation of the year is omitted to reduce the number of digits in the actual data) is “goods receipt at hh hour mm on MM month DD day”. And the length of the effective parking time is TT time. " As shown in FIG. 11C, the actual data includes a number MM representing the month, a number DD representing the day, a number hh representing the hour of the time, and a number mm representing the minute of the time. , The length of parking time (if the receipt is for prepayment, it means valid parking time, whereas if the receipt is for additional parking fee, it means extended parking time) It has five elements, the number TT representing.

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

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

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

  In one example, for each of the five elements MM, DD, hh, mm, and TT, the relationship between the actual data and the encrypted data in the encryption table, that is, a number before encryption (for example, “2 "2" for "month") and the correspondence between 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 Is 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. In the receipt 81a, as shown in FIG. 7 (a), the same information regarding at least one of the date and time, the amount of money, and the length of the parking time for the payment of the parking fee or the parking time can be decoded by the user. And the encrypted data 130 that cannot be deciphered by the user. This completes the current execution of this ticketing / settlement program.

  Specifically, as shown in FIG. 7 (a), the parking ticket 80 specifies 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. Will be printed. In addition, the receipt 81a is printed with the entry time, the amount of the prepaid parking fee paid by the user, the end time of the effective parking time, and a display for specifying the location of the parking lot 10. The receipt 81a is also printed with encrypted data 130 exemplified by “ABC-DEF-ABC”. As shown in FIG. 11 (b), the encrypted data 130 includes the warehousing time (which includes the parking ticket 80 and the receipt 81a, both the time when the prepaid parking fee is paid and the parking time start time). The actual data representing the time at which the ticket is issued and the length of the effective parking time (this is equivalent to the amount of the prepaid parking fee paid) are encrypted.

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

  Subsequently, in step S12, in the same manner as in step S9, the time when the receipt 81b is 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 (this is equivalent to the amount of the additional parking fee paid) is converted into the encrypted data 140 by referring to the encryption table.

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

  Specifically, as shown in FIG. 7 (b), the receipt 81b shows the date and time when the receipt 81b was issued, the amount of the additional parking fee, and a display for specifying the location of the parking lot 10. And are printed.

  Further, the encrypted data 140 exemplified by “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 is issued and the length of the extended parking time.

  FIG. 7A shows a front view of a two-sheet spelling of a parking ticket 80 and a receipt 81a, while FIG. 7B shows a receipt 81b in a front view. The double spelling of the parking ticket 80 and the receipt 81a corresponds to two parking tickets 80. In the double spelling, the parking ticket 80 and the receipt 81a have the same size and configuration. The receipt 81 b corresponds to one parking ticket 80 and has the same size and configuration as the parking ticket 80. Hereinafter, in order to simplify the description, only the configuration of the parking ticket 80 will be representatively described.

  The parking ticket 80 includes 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 in that order. Has been configured. The adhesive layer 83 is applied to the back surface of the display sheet 82 so as not to be easily peeled off. In the state where the display sheet 82 is peeled off from the surface of the separator 84, the adhesive of the adhesive layer 83 is the surface of the separator 84. It does not adhere to.

  As shown in FIG. 7A, in one parking ticket 80, the outer periphery of the display sheet 82 is positioned inside the outer periphery of the separator 84. The raw material wound around the roller 42 is formed by adhering a plurality of display sheets 82 (in a blank state) aligned in a row with a gap 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, no glue is attached to the surface of the portion of the separator 84 exposed in the gap between the display sheets 82.

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

  However, in this embodiment, the receipt 81b is completely cut by the cutter with a length of one sheet by the cutter, whereas the two-sheet binding is equivalent to two separators 84. Completely cut with a length of. However, as described above, as shown in FIG. 7A, the separator 84 is partially cut between the parking ticket 80 and the receipt 81a by the cutter, as shown in FIG. Thereby, a cut line 89 is formed.

  As shown in FIG. 7A, the display sheet 82 of the parking ticket 80 further includes a cutting line 90 having both ends (not closed) immediately above the character string “parking ticket”. The cut line 90 is present to allow the user to remove a portion of the display sheet 82 from the separator 84 while the remaining portion remains adhered to the separator 84. As shown in FIG. 8B, when the user peels a part of the display sheet 82 (the region 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 that is applied to the back surface of the bent portion 92) is exposed as a glue surface. FIG. 9 (a) shows the bent portion 92 in a perspective view.

  In this embodiment, in order to prove that parking by the user is not illegal parking, the user receives the parking ticket 80 received in exchange for coin insertion, as shown in FIG. 9B. It is required to be pasted on the back surface of the glass 110. Therefore, as shown in FIG. 9A, the user locally places a designated portion (a portion surrounded by the cutting line 90 and finally a bent portion 92) in the parking ticket 80. 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. Thus, as shown in FIG. 10, the contents of the parking ticket 80 (particularly, information for specifying the end time of the parking time zone permitted for the user and the parking lot 10 in which the parking ticket 80 is valid). It is possible to visually check the display) for specifying the location of the user at any time from the outside.

  The user is required to pay an additional parking fee if the actual parking time exceeds the effective parking time. However, since the parking lot 10 is unmanned as described above and does not have a device that prevents the parked vehicle from being delivered unless the necessary additional parking fee is paid, as shown in FIG. The fact that the necessary additional parking fee has been paid is notified from the parking lot 10, in-car, home, etc. to the parking lot manager in the remote management center by means of communication devices such as mobile phones and fixed phones. Is required to.

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

  When receiving the voice representing the encrypted data 130, 140 issued by the user, the parking lot manager in the management center operates the input device (for example, keyboard, touch screen, mouse, etc.) of the decryptor 180. A symbol corresponding to the user's voice is input. Then, the encrypted data 130 and 140 are input. Then, the decryption device 180 is installed in the decryption device 180 with the input encrypted data 130 and 140 being a decryption table conforming to the encryption table. Restore the actual data according to the data.

  As a result, the parking lot manager can stay at the management center far away from the parking lot 10 to be managed, and the actual parking time length (for example, the time the user has actually parked) (for example, , The length of elapsed time from the warehousing time specified by the encrypted data 130 to the time when the additional parking fee is paid, which is specified by the encrypted data 140), and 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 encryption data 130 and the amount of the additional parking fee specified by the encryption data 140). It is possible to correctly determine whether there is a shortage in relation to the length of the actual parking time.

  Since the decryption table accommodated in the decryption device 180 cannot be known even by a parking lot administrator unless authorized, the security of the decryption table is high.

  As is clear from the above description, according to the present embodiment, at the time when the receipts 81a and 81b are issued, the encrypted data 130 and 140 are displayed on the receipts 81a and 81b with symbols that can be pronounced by the user. Only by printing and further requesting the user to send the encrypted data 130 and 140 to the parking lot manager by voice, the parking manager can correctly determine whether or not the parking fee is insufficient. Therefore, the user can safely park the vehicle after the effective parking time without imposing a heavy burden, and the usability of the parking lot 10 and the operation rate are improved.

  In addition, in the present embodiment, the user transmits the encrypted data 130 and 140 by voice input. For example, instead of the voice input, the user inputs data (for example, real or virtual). Key input using a key, image input using an image reader).

  The normal parking has been described above. Next, cardless parking will be described.

  As is apparent from the above description, in this embodiment, neither the parking lot 10 nor the ticket issuing machine 20 has facilities for detecting the fact that each user has entered and exited the parking lot 10. In the case of cardless parking, as described later in detail, the user starts parking using his / her electronic parking ticket using his / her communication device (for example, a mobile phone or a smart phone). Message to request the parking lot manager, but the fact that the user is actually parked in the parking lot 10 at that time neither the parking lot 10 nor the ticketing machine 20 can detect, and the user The fact that the user has actually entered the parking lot 10 cannot be detected unless the user simply uses his / her communication device, for example, using the GPS function of the 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 actual data, and uses the actual data as a time encryption table (ticketing machine 20 Is stored in the memory 104), and the time code 190 is obtained as encrypted data. The time code 190 cannot be decrypted by the user but can be decrypted by the parking lot manager (for example, as with the encryption codes 130 and 140, the user cannot decrypt but can uniquely pronounce it). is there.

  In one example, as shown in FIG. 13C, the time code 190 is updated discretely, that is, every set time interval (for example, 15 minutes).

  Further, as shown in FIG. 13A, the ticket issuing machine 20 is designed to display the time code 190 on the screen of the display device 36 in a state of being sequentially updated as time elapses.

  Further, as shown in FIG. 13A, the ticket issuing machine 20 displays a location code 192 unique to the parking lot 10 along with the time code 190 on the screen of the display 36, and indicates the position of the parking lot 10. Designed to display what is identifiable.

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

  In each execution of the code display program, first, the current time is measured by the clock 102 in step S31. Next, in step S32, the measured current time is encrypted into the time code 190 by referring to the time encryption table. Subsequently, in step S <b> 33, 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 is the end of the current execution of the code display program.

  By repeatedly executing the code display program, the time code 190 and the location code 192 are displayed on the same screen as illustrated in FIG. 6 on the screen of the display 36 as illustrated in FIG. Always displayed at a position where the message to be hidden is not covered.

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

  Furthermore, since the time code 190 is generated so that it cannot be deciphered by any user of the parking lot 10, the user does not actually enter or leave the parking lot 10 at any time. Or, the display 36 is displayed at a certain time to impersonate a user who has entered or exited the parking lot 10 at a certain time even though the parking lot 10 has actually entered or exited at another time. Even if the user attempts to predict the time code 190 that should have been, the user cannot obtain the authentic time code 190. Therefore, the time code 190 also has confidentiality for the user.

  Furthermore, the time code 190 is only displayed on the display 36 of the parking lot 10 where the user is actually trying to park or 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 has location dependency.

  Thus, the time code 190 has time dependency, secrecy to the user, and location dependency. Therefore, the time code 190 actually viewed by the user in the parking lot 10 is displayed on the display device. As long as the time code 190 is transmitted to the management server 202 at a time that is not greatly delayed from the time displayed in 36 (a time within the setting allowable range), the time code 190 indicates that the user actually entered or left the parking lot 10. It will be strong evidence to support.

  Here, the time encryption table will be described in detail. The time encryption table is updated regularly, for example, every day, like the encryption table shown in FIG. As a result, when the dates are different, there is a high possibility that the time code 190 is different even if the time is the same. As a result, the abuse 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 those parking lots, the time code It is desirable that 190 be generated differently at different parking locations even at the same time. In this desirable mode, the time code 190 displayed on the parking lot 10 has place discriminating power.

  Here, the term “location discriminating power” may be defined in such a way that only the feature that the time code 190 differs depending on the location, but not the feature 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 differs depending on the place but also the feature that the place can be uniquely identified from the time code 190.

  However, in this embodiment, in order for the management server 202 to specify 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 location identification power. Also good. This is because, in the present embodiment, the location code 192 having location identification 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 going 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 in the remote place at the time of warehousing, the parking lot manager It becomes possible to estimate at which time the goods arrived.

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

  In addition, the parking lot manager further obtains the current time obtained by decrypting the time code 190 (for example, the observation time when the user observed the display 36) and the current time measured by the parking lot manager (parking lot management). If the difference from the reception time when the user received the time code 190 is within a setting allowable range (for example, 30 minutes), the user actually acquires the current time obtained by decrypting the time code 190 (FIG. 13). As illustrated in (c), if there is a time width, the user is at any time between 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 at the parking lot 10 has started).

  On the other hand, even if the parking lot manager cannot decrypt the received time code 190 normally or can decrypt it correctly, it is measured by the parking lot manager and the current time acquired by the parking lot manager. When the time code 190 transmitted by the user to the parking lot manager is not present as the time code 190 in the ticket issuing machine 20 when it is determined that the difference from the current time exceeds the allowable setting range, Or, even if it exists, since the time when the user transmitted the time code 190 to the parking lot manager is considerably later than the time when the user observed the time code 190 on the display device 36, the user has his / her own electronic parking ticket. Even if it is valid, parking using the parking lot is refused by the parking lot manager.

  In addition, if the length of the setting allowable time is set 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 interval between the times may be long to some extent. This increases the range of selection of the transmission time allowed for the user, and thus brings the following advantages.

  That is, for example, when the user parks his / her vehicle in the parking lot 10 and walks out of the parking lot 10, the user stores the time code 190 displayed on the display 36, and then If you need to walk from the parking lot 10 to the nearest station, etc., and use transportation such as trains or buses, you will be reminded of the time code 190 after boarding the transportation. It is allowed to send to the administrator.

  As a result, for the user, regardless of whether there is time allowance or not, it is more time-consuming and mental than the case where it is always required to transmit the time code 190 from the parking lot 10 to the parking lot manager. The burden is reduced, and as a result, the usability of the parking lot 10 is improved.

  As described above, the characteristic elements for performing cardless parking have been described in detail for the ticket issuing machine 20. Hereinafter, referring to FIGS. 15 to 27, a service for issuing an electronic parking ticket to the user will be described. Explain the contents.

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

  In the system 200, a plurality of users and a plurality of persons in charge who perform work in accordance with instructions from the parking lot manager (each person in charge is a parking lot 10 managed by the parking lot manager and a plurality of other parking lots. And has a task of monitoring the parking lot several times a day) via a wireless or wired connection to the management server 202 via the Internet 204, which is an example of a global communication network. Yes.

  The management server 202 includes 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 in order to perform transmission / reception.

  The management server 202 further includes a processor 220 and a storage 222 (for example, ROM, RAM). In order to provide the service, the processor 220 executes an electronic parking ticket processing program that is exemplarily and conceptually represented by flowcharts 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 referred to as “DB” illustrated in FIG. 19 and the same in the figure) 230 and an electronic parking ticket database (hereinafter referred to as “DB”) illustrated in FIG. The same applies to the figure.) 232 and the decryption table 234.

  In addition, although not shown, the management server 202 has a clock for measuring the current time inside, or can use a measurement result of an external clock, as is the case with the ticket issuing machine 20.

  First, the contents of this service will be schematically described. According to this service, the management server 200 responds to an issuance request from the user and the management server 200 provides the user with a pre-payment of a predetermined amount of parking fee. On the other hand, the electronic parking ticket 250 illustrated in FIG. 21 is issued. When the user will perform parking in the parking lot 10 using the issued electronic parking ticket 250 from now on, the parking permission request and the time code 190 displayed on the display 36 at the time of entering the parking lot 10 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 It is determined whether or not the management server 202 is within a predetermined allowable range determined with respect to the reception time at which the time code 190 is received, thereby determining whether or not the received time code 190 is valid.

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

[Member registration]

  More specifically, in this service, in order to acquire the use qualification of the electronic parking ticket 250, a step of registering the user as a member, a step of issuing the electronic parking ticket 250 to the user, and parking Only when the user permits the use of the electronic parking ticket 250 at the start and when the user performs extended parking, at the end of parking, an additional parking fee corresponding to the length of the extended parking time is paid by electronic settlement. And the process for settlement are performed in that order.

  More specifically, in this service, first, as illustrated in the sequence diagram of FIG. 22, the user accesses the management server 202 to register as a member. When the user transmits 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.

[Issuing an electronic parking ticket]

  Next, in order to request the parking lot manager to issue the electronic parking ticket 250, the user accesses the management server 202 as illustrated in the sequence diagram of FIG. Thereafter, the user transmits the user ID and password 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 a fee necessary for acquiring the number of points. When the user pays the fee, the management server 202 gives a unique ticket number to the electronic parking ticket 250 to be issued, further gives the number of valid points, and the information thereof is illustrated in FIG. Register in the electronic parking ticket DB 232. Thereafter, the management server 202 issues an electronic parking ticket 250 illustrated in FIG. 21 to the user.

[Permission to use electronic parking ticket]

  Then, in order to start parking at the parking lot 10 using the issued electronic parking ticket 250 when the user enters the parking lot 10, as shown in the sequence diagram of FIG. To access. Thereafter, the user transmits a unique ticket number assigned to the electronic parking ticket 250 desired 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. To do.

  Thereafter, 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 used points necessary for permitting the user of the parking time. The management server 202 further calculates the remaining point number by subtracting the used point number from the current valid point number, and confirms that the remaining point number is not 0. Calculate the length of. Thereafter, the management server 202 issues a receipt 260 illustrated in FIG. 25 and transmits it to the user.

  In the present embodiment, when the user is required to specify the scheduled delivery time (equivalent to the length of the planned parking time) at the time of warehousing, and then paying attention to the fact that the number of valid points is subtracted, this time Can be considered to be classified as prepaid parking. As shown in FIG. 25, the receipt 260 describes the length of the effective parking time permitted by the user together with the end time of the effective parking time. Therefore, the user can know by what time the goods should be delivered by looking at the receipt 260.

  As shown in the lower part of FIG. 24, the fact that the current user is permitted to park is notified not only to the user himself / herself, but also to the above-mentioned multiple persons in charge. The person in charge can be contacted by a method (active communication) in which the management server 202 individually sends an e-mail describing information on parking permission to each person in charge, or a person who can view the management server 202. Information on parking permission is posted on a limited website (trader-specific website), and information on parking permission is communicated to the person in charge through individual access to the website (passive) Contact).

[Settlement of extra charges for extended parking]

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

  Thereafter, the user transmits a 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. To do.

  Thereafter, the management server 202 calculates the length of time that has elapsed from the end time of the effective parking time recorded in the electronic parking ticket DB 232 to the estimated delivery time as the length of the extended parking time, Furthermore, an additional parking fee corresponding to the length of the extended parking time is calculated. 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. Thereafter, the management server 202 issues a payment receipt (not shown) and transmits it to the user.

  Next, the contents of the electronic parking ticket processing program will be described more specifically with reference to FIGS. 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 for registering members and issuing electronic parking tickets, the second subprogram is for permitting the use of electronic parking tickets, and the third subprogram is extended parking It is a part for paying the parking fee at the time.

[Member registration]

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

  Subsequently, in step S103, a unique user ID is given to the current user. Thereafter, in step S <b> 104, the personal identification number set by the user and transmitted from the user's communication device is received via the receiving unit 212. In this step S104, other user information additionally transmitted from the user's communication device (for example, as exemplified in FIG. 19, the vehicle number, the model name, the vehicle body color of the vehicle that the user plans to park) And the like are also received via the receiving unit 212.

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

[Issuing an electronic parking ticket]

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

  In this step S108, whether or not the current user is a member by collating the user ID and personal identification number transmitted from the user's communication device with the member DB 230, that is, the qualification for receiving this service is provided. It is determined whether or not That is, personal authentication is performed. When this personal authentication is established, in step S109, data indicating the number of points that the user wants to acquire this time is transmitted via the receiving unit 212. Received.

  Thereafter, 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 determined in advance between the number of points and the fee. It is calculated by referring to a charge table or function expression that represents the relationship. Subsequently, in step S111, data representing the fee to be paid by the user is transmitted to the user. Thereafter, 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 normally completed. If the electronic payment by the user is not completed normally, the determination in step S113 is NO, and in step S113a, an issuance disapproval message indicating that issuance of the electronic parking ticket 250 is not permitted is returned to the user. The This is the end of the current execution of this electronic parking ticket processing program.

  On the other hand, assuming that the electronic payment by the user has been normally completed this time, the determination in step S113 is YES, and in step S114, a ticket unique to the electronic parking ticket 250 to be issued to the current user. A number is given. The assigned ticket number is registered in the electronic parking ticket DB 232 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 current user. In step S116, the given number of valid points is registered in the electronic parking ticket DB 232 in association with the user ID as illustrated in FIG.

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

[Permission to use electronic parking ticket]

  As described above, the scenario in which the management server 202 receives an electronic parking ticket issue request from the user has been described. Instead, in the scenario in which the management server 202 receives an electronic parking ticket use request, the determination in step S101 in FIG. 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, as in step S108 in FIG. 16, personal authentication is performed based on the user ID and personal identification number transmitted from the user's communication device. If this personal authentication is established, in step S120, the receiving unit 212 receives data for identifying the electronic parking ticket 250 that the user wants to use this time, which is one ticket number transmitted from the user's communication device. Received via.

  Thereafter, in step S121, it is determined whether or not the electronic parking ticket 250 that the current user desires to use is valid by comparing the received ticket number with the electronic parking ticket DB 232 for the current user. . If the current electronic parking ticket 250 is not valid, a use disapproval message indicating that use of the electronic parking ticket 250 is not permitted is returned to the user's communication device in step S122. This is the end of 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 desires to use is valid, in step S123, the time code 190 and the location code 192 transmitted from the user's communication device are received by the receiving unit 212. Received via. Subsequently, in step S124, the received time code 190 is decrypted with reference to the decryption table 234. Thereafter, in step S125, the user's warehousing time is estimated based on the decoding result. Subsequently, in step S126, it is determined whether or not the estimated storage time is within a predetermined allowable range determined with respect to the reception time at which the management server 202 receives the time code 190. A determination is made whether code 190 is valid.

  This time, assuming that the received time code 190 is not valid, the determination in step S126 is NO, indicating that the use of the electronic parking ticket 250 by the user (parking in the parking lot 10) is not permitted in step S122. A use disapproval message is transmitted 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 the user's desired parking condition is received from the user's communication device in step S127. The desired parking condition includes, for example, the length of the parking time desired by the user.

  Subsequently, in step S128, the number of used points used for realizing the received desired parking condition is calculated. The number of points used is calculated with reference to a predetermined conversion table so that the number of points used increases, for example, according to the length of parking time that the user desires for free parking. Thereafter, in step S129, the number of valid points is updated by subtracting the calculated number of used points 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 DB 232.

  Subsequently, in step S130, based on the received data indicating the desired parking condition, an effective parking time that is the length of the parking time permitted to the user as a price for the consumption of the above-mentioned used points is calculated. Thereafter, in step S130a, a receipt 260 illustrated in FIG. 25 is issued including the meaning of allowing the user to permit parking using the electronic parking ticket 250. Data representing the issued receipt 260 is transmitted to the user's communication device.

  Subsequently, in step S131, processing for notifying all the persons in charge of the received desired parking conditions is performed (for example, the desired parking conditions are individually notified to the persons in charge by e-mail, or the desired parking conditions are set). Contact the person in charge by posting the conditions on the vendor-specific website). This is the end of 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 an electronic parking ticket use request from the user has been described above. Instead, in the scenario in which the management server 202 receives an extended parking settlement request, the determination in step S101 in FIG. The determination in S107 is also NO, the determination in step S118 in FIG. 17 is NO, 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.

  In step S139 of FIG. 18, the user's delivery time is estimated based on the decoding result of the time code 190 transmitted from the user's communication device in step S137. Subsequently, in step S140, it is determined whether or not the estimated delivery time is within a predetermined allowable range determined with respect to the reception time at which the management server 202 has received the time code 190. A determination is made whether code 190 is valid.

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

  On the other hand, assuming that the received time code 190 is valid this time, the determination in step S140 is YES, and in step S141, the effective parking recorded in the electronic parking ticket DB 232 from the estimated delivery time. 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 corresponding to the calculated length of the extended parking time is calculated by referring to a predetermined conversion table. Thereafter, in step S143, the number of used points corresponding to the calculated 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 used points. The number of remaining points is reflected in the electronic parking ticket DB 232. In the electronic parking ticket DB 232, data indicating that the user has settled the additional parking fee by partial consumption of the number of valid points is also recorded as illustrated in FIG. Thereafter, in step S145, a payment receipt (not shown) indicating that the additional parking fee has been paid by the user is issued, and data representing the payment receipt is transmitted to the user's communication device.

  Subsequently, in step S146, in accordance with step S131 of FIG. 17, processing for notifying all persons in charge that the additional parking fee has been settled by the user is performed. This is the end of the current execution of this electronic parking ticket processing program.

[Automatic transmission of a message to issue a delivery]

  In the present embodiment, as described above, the management server 202 uses the electronic parking ticket 250 for parking, and at the time of warehousing, the management server 202 also determines the warehousing time from the warehousing time and the length of the effective parking time. Also knows the estimated shipping time 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 will soon arrive, In order to warn that the time has elapsed and to pay attention to paying for the extended parking whenever the scheduled departure time has passed, send a message individually to the user's communication device by e-mail Designed.

  Specifically, as shown in FIG. 27, the management server 202 calculates the planned delivery time (the end time of the effective parking time) with reference to the data in the electronic parking ticket DB 232 for each user, A time earlier than the delivery time by a set time (for example, 1 hour) 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 has passed one hour”, and sends the exit reminder message by e-mail. Send to the corresponding user's communication device.

  The delivery reminder message includes, for example, a description “if the scheduled delivery time has passed, the user needs to access the management server and settle the additional parking fee when leaving”. It is. As a result, when the scheduled delivery time has elapsed, the user's attention is alerted so as not to forget to access the management server 202 and pay the additional parking fee when leaving.

  Furthermore, the management server 202 determines whether or not the scheduled delivery time has arrived for each user, and when it arrives, the user pays the additional parking fee by referring to the electronic parking ticket DB 232. It is determined whether or not. When the payment of the additional parking fee has not been completed, the management server 202 displays a description that “scheduled shipping time has passed” and “when leaving, 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 electronic mail. The management server 202 sends the same delivery reminder message to the user who sent the delivery notification message every time a set time (for example, 1 hour) elapses until the user accesses the management server 202 and settles the additional parking fee. Send repeatedly.

  In addition, in the present embodiment, both the normal parking and the cardless parking are possible for the same parking lot 10, so that the ticket issuing machine 20 has not only the original ticket issuing function but also the time code 190. It is designed to have a time code generation / display function for generating the code by encryption and displaying it on the screen of the display 36. However, in the present invention, for example, only cardless parking is possible for the same parking lot 10, and instead of the ticketing machine 20, a clock 102 and an encryptor that encrypts the current time measured by the clock 102 ( For example, a time code generator / computer including at least a display 36 for displaying the time code 190 generated by the encryption) and a computer that executes a program for generating the time code 190 with reference to the time encryption table. It is possible to implement in a mode in which the display device is installed in the parking lot 10.

  As is clear from the above description, in the present embodiment, for convenience of description, the timepiece 102 constitutes an example of the “timepiece” in the above item (1), and the steps shown in FIG. 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 part” 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 “parking time code generation / display device” in the same section, and the display 36 includes an example of the “display section” in the section (2) and It can be considered that each example of the “parking time code display device” according to the item (5) is configured.

  Furthermore, in this embodiment, for convenience of explanation, steps S120 and S123 shown in FIG. 17 constitute an example of the “reception process at the time of warehousing” in the item (1) or (2), and are shown in FIG. Steps S124 to S126 constitute an example of the “entry 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 paragraph, and transmission It can be considered that the unit 210 and the receiving unit 212 constitute an example of the “communication unit” in the same term in cooperation with each other.

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

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

Second Embodiment

  Next, a parking lot management method according to the second exemplary embodiment of the present invention will be described. However, elements that are the same as those in the first embodiment are referred to by using the same reference numerals or names, and redundant description is omitted, and only different elements will be described in detail.

  In the first embodiment, each time a user who wants to perform cardless parking attempts to use the parking lot 10, prior to the parking (at the time of warehousing), the user specifies the length of the planned parking time to perform the current parking. Then, the number of points corresponding to the prepaid parking fee of the amount commensurate with the length of the scheduled parking time is consumed among the number of valid points. When the user leaves the parking lot 10 before the scheduled parking time elapses, that is, when extended parking is not performed, it is not necessary to access the management server 202 when leaving. That is, it is unnecessary for the user to access the management server 202 at the time of delivery unless extended parking is performed. As a result, unless the user performs extended parking, the user only needs to communicate with the management server 202 at the time of warehousing, and the user's effort is omitted.

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

  On the other hand, in the present embodiment, the user's trouble is added such that the management server 202 is accessed not only at the time of warehousing but also at the time of warehousing. Without doing so, the parking time is calculated together at the time of delivery and the number of points is consumed, so that the number of points consumed is calculated just to match the actual parking time. As a result, according to the present embodiment, the user does not have to waste useless points and is economical.

  Next, a parking lot management method according to the present embodiment will be described with reference to FIGS. 28 to 33. An electronic parking ticket processing program executed in 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 (use permission of the electronic parking ticket 250) shown in FIG. 17, and FIG. And a fifth subprogram that replaces the third subprogram (settlement of additional parking fee at the time of extended parking).

  The fourth subprogram is executed in the management server 202 in order to permit the start of parking using the electronic parking ticket 250, and is conceptually represented in a flowchart in FIG. Further, the fifth subprogram is executed in the management server 202 so that the user can settle the parking fee with point consumption at the end of parking using the electronic parking ticket 250, and is conceptually represented in a flowchart in FIG. .

  Hereinafter, although the electronic parking ticket processing program in the present embodiment will be described, redundant description of processes common to the first embodiment will be omitted, and only different processes will be described in detail.

[Permission for parking using electronic parking ticket]

  The user accesses the management server 202 as illustrated in the sequence diagram of FIG. 30 in order to request the parking manager to permit parking using the electronic parking ticket 250 when entering the parking lot 10. . Thereafter, the user transmits the ticket number assigned to the electronic parking ticket 250 desired 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. To do.

  When the estimated warehousing time is appropriate, the management server 202 permits parking by the user and transmits a parking permission message to the user. The management server 202 notifies the fact that the user has been allowed to park in the same manner as in the first embodiment, not only to the user himself / herself, but also to the above-mentioned multiple persons in charge.

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

  In step S126, when it is determined that the warehousing time estimated by the decryption of the time code 190 received this time from the user is appropriate, in step S302, a parking permission message indicating that the user is permitted to park is displayed. Returned to the user's communication device. Thereafter, in step S303, the person in charge is notified to the user of information indicating that parking at the parking lot 10 is permitted. Thus, the current execution of the fourth subprogram ends.

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

  The user accesses the management server 202 at the time of delivery from the parking lot 10 as illustrated in the sequence diagram of FIG. 31 in order to settle the parking fee. Thereafter, 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. To do.

  Thereafter, the management server 202 calculates the length of the parking time by subtracting the entry time recorded in the electronic parking ticket DB 232 from the estimated delivery time in step S402 shown in FIG. The estimated delivery time is recorded in the electronic parking ticket DM232 as illustrated in FIG.

  Subsequently, in step S403, a parking fee corresponding to the calculated length of the parking time is calculated by referring to a predetermined conversion table. Thereafter, in step S404, the number of used points corresponding to the calculated amount of 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 used points. The number of remaining points is reflected in the electronic parking ticket DB 232. In the electronic parking ticket DB 232, data representing that the user has settled the parking fee by partial consumption of the number of valid points is also recorded as illustrated in FIG. Thereafter, 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 persons in charge that the parking fee has been settled by the user is performed. Thus, the current execution of the fifth subprogram ends.

[Automatic transmission of a message to issue a delivery]

  In this embodiment, as described above, the management server 202 knows the warehousing time at the time of warehousing for a user who parks using the electronic parking ticket 250, but unlike the first embodiment. , I do not know the scheduled shipping time. However, the management server 202 can sequentially calculate the elapsed time from the warehousing time to the current time, that is, the user's parking time up to the current time, and the number of used points corresponding to the length of the parking time is also sequentially calculated. Can be calculated. Then, at each time, even if the management server 202 tries to consume the number of used points at that time, the remaining points are insufficient in relation to the length of the parking time, and the fact that the parking fee cannot be settled in full. You can notice.

  Therefore, in the present embodiment, as shown in the sequence diagram of FIG. 33, the management server 202 sequentially calculates the length of the parking time for each user for whom the payment of the parking fee has not been completed, The number of points used corresponding to the length of parking time is also calculated. Further, the management server 202 determines whether or not the remaining point number 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 remaining number of points is insufficient, the management server 202 creates a delivery reminder message for prompting the user to exit quickly, and the delivery reminder message is transmitted to the corresponding user by e-mail. Send to device.

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

  Furthermore, in the present embodiment, for the sake of convenience of explanation, steps S134 and S137 shown in FIG. 29 constitute an example of the “reception process at the time of delivery” in the item (3), and steps S138 to S140 shown in FIG. However, it can be considered that it constitutes an example of the “departure time validity determination step” in the same paragraph, and that step S402 shown in the figure constitutes an example of the “parking time calculation step” in the same paragraph. It is.

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

  In this aspect, for example, a timepiece 102 and a time encryption unit that encrypts the current time measured by the timepiece 102 (the computer refers to the time encryption table shown in FIG. 190 is mounted on the management server 202, and the management server 202 measures the current time and encrypts it to generate a time code 190, and the time code 190 is sent 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 need to have the clock 102 and the time encryption unit in place of having the communication function.

  As mentioned above, although several embodiment of this invention was described in detail based on drawing, these are illustrations and are based on the knowledge of those skilled in the art including the aspect as described in the above-mentioned [summary of invention] column. The present invention can be implemented in other forms with various modifications and improvements.

Claims (5)

The user accesses the management server of the parking lot manager from any location via the mobile terminal, thereby purchasing an electronic parking ticket from the parking lot manager and using the electronic parking ticket by the user. A cardless parking management method that allows a user to park in a selected parking lot,
When the user's portable terminal transmits an issuance request to request the parking lot manager to issue the electronic parking ticket, the management server receives the issuance request from the user's portable terminal. When,
After the reception, when the parking fee of the amount corresponding to the length of the scheduled parking time designated by the user is paid by the user, the management server issues the electronic parking ticket to the user, and the electronic parking ticket is Transmitting data to the user's mobile terminal that includes data for display and includes electronic parking ticket specifying data for specifying the electronic parking ticket ;
When the user's portable terminal transmits a use request to start parking at the parking lot using the issued electronic parking ticket when the user enters the parking lot, the management server Receiving the usage request from a mobile terminal of
After the reception, when the user's portable terminal transmits the electronic parking ticket identification data to the management server, the management server is unique to the electronic parking ticket identification data received from the user's portable terminal and the electronic parking ticket. The electronic parking ticket that the user desires to use this time is valid by comparing the data registered in the memory of the management server and determining whether or not it is successful. Determining whether or not and determining that it is not valid, the step of transmitting to the user's mobile terminal information indicating that the user does not permit the use of the electronic parking ticket that the user wishes to use this time ;
When the length of the actual continuous parking time by the user exceeds the length of the scheduled parking time, when the user's mobile terminal transmits a settlement request when the user leaves the parking lot , the management server Receiving the payment request from a mobile terminal of;
After the reception, the management server calculates an additional parking fee corresponding to the excess length of time, and when the user settles the additional parking fee, data indicating that the settlement has been performed is stored in the user's mobile phone. A cardless parking management method including a step of transmitting to a terminal. In each parking lot available to the user, a location identification information output device that outputs information for identifying the location of the parking lot is installed,
The cardless parking management method is
further,
When the management server receives the use request from the user's mobile terminal when the user enters the parking lot, the user inputs the information output from the location identification information output device to the user's mobile terminal. The cardless parking management method according to claim 1 , wherein the management server includes a step of receiving the information output from the location identification information output device from a user's mobile terminal. The user accesses the management server of the parking lot manager from any location via the mobile terminal, thereby purchasing an electronic parking ticket from the parking lot manager and using the electronic parking ticket by the user. A cardless parking management method that allows a user to park in a selected parking lot,
A step in which the user's mobile terminal transmits an issue request to the management server in order for the user to request the parking lot manager to issue the electronic parking ticket;
After the transmission, when the user is paid a parking fee corresponding to the length of the scheduled parking time specified by the user and the management server issues the electronic parking ticket to the user, the user's mobile terminal Receiving from the management server data for displaying the electronic parking ticket and including electronic parking ticket specifying data for specifying the electronic parking ticket;
A step of transmitting a use request to the management server by the user's mobile terminal in order to start parking at the parking lot using the issued electronic parking ticket when the user enters the parking lot;
After the transmission, the user's portable terminal transmits the electronic parking ticket identification data to the management server, whereby the management server receives the electronic parking ticket identification data received from the user's portable terminal, and the electronic parking The electronic parking ticket that the user desires to use this time is verified by comparing data that is unique to the ticket and registered in the memory of the management server, and determining whether or not it is successful. If it is determined whether or not it is valid, and it is determined that it is not valid, information indicating that the user's portable terminal does not permit the use of the electronic parking ticket that the user wants to use this time is received from the management server. Receiving, and
When the length of the actual continuous parking time by the user exceeds the length of the scheduled parking time, when the user leaves the parking lot, the user's mobile terminal transmits a settlement request to the management server;
After the transmission, the management server calculates an additional parking fee corresponding to the length of the excess time, and when the user settles the additional parking fee, the user's mobile terminal confirms that the settlement has been performed. Receiving data representing the management server;
A program executed by a computer of the mobile terminal so that the user's mobile terminal performs each step in the cardless parking management method . Program managing server process according to claim 1 or 2 is executed by the management server of the computer to implement.   The recording medium which recorded the program of Claim 3 or 4 so that computer reading was possible.

Images