JP7366477B2 - Parking management systems and programs - Google Patents

Description

The present invention relates to technology for managing parking lots.

Parking lots with multiple parking positions for vehicles are already widespread. This type of parking lot can be classified from the perspective of the method of transporting the vehicle to the parking location: the user drives the vehicle himself and transports the vehicle to the parking location, and the other method involves mechanically moving pallets or cages to transport the vehicle. It is classified into mechanical type, which transports the car directly to the parking position. Further, the parking lot may be lent to the user free of charge or may be lent to the user for a fee. Paid parking lots are classified into monthly parking lots and hourly parking lots (including "daily parking lots") based on the length of time they are rented to users.

Hourly parking lots can be categorized from the perspective of payment methods, such as prepaid parking where the user pays the parking fee before parking starts (however, there is a possibility of paying the shortfall in the parking fee when leaving the parking lot). and deferred payment type, in which the user pays the parking fee in full at the end of parking.

In addition, hourly parking lots can be classified from the perspective of their management method: manned parking lots, where a person in charge of managing and monitoring the parking lot is permanently stationed in the parking lot, and 2) a manned parking lot in which a person in charge of managing and monitoring the parking lot is permanently stationed at the parking lot, and a parking lot with a person who is not permanently stationed in the parking lot. It is classified as an unmanned type, in which personnel are sporadically dispatched to the parking lot.

As a known document disclosing this type of parking lot and the equipment (including a ticket issuing machine) installed in the parking lot, there is, for example, Patent Document 1.

Patent Document 1 discloses a prepaid unmanned parking lot. This parking lot has a card issuing machine that issues a parking card for a fee that records the time you are allowed to park, an entrance gate that is always closed, and a parking machine installed at the entrance that allows parking cards to be inserted. , and a warehousing management device that opens the warehousing gate on the condition that the parking card is appropriate. Furthermore, this parking lot has an exit gate that is always closed, and an exit management device that is installed at the exit and opens the exit gate when a parking card is inserted, provided that the parking card is appropriate. will be installed.

In this way, Patent Document 1 discloses a technology in which when a user parks a car in an unmanned paid parking lot, the user uses an existing card (for example, a physical parking ticket) to park the car. .

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

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

According to the technology disclosed in Patent Document 2, the user can park in a parking lot without using a card, so there is an advantage that the user does not have to worry about losing the card. However, in order to implement the technology disclosed in Patent Document 2, special and expensive equipment must be installed in both the car and the parking lot in order to obtain information specific to the car that is going to be parked. For those who own parking lots or manage parking lots, it is important to consider the cost of the equipment itself, the cost and man-hours required to install the equipment in the parking lot, and the maintenance and inspection of the equipment. The disadvantage is that the cost and man-hours required for the work tend to increase.

Moreover, it is important for a parking lot manager who manages a parking lot to accurately grasp the fact that a user enters or exits a parking lot. Additionally, for users of hourly parking lots, it is important to improve the technology for paying parking fees.

Based on the above knowledge, the present invention provides a technology for managing a parking lot, which allows a user to pay a parking fee and/or a user to use a parking lot by using the user's communication device. This was done with the aim of improving the technology for determining whether or not the

To solve this problem, one aspect of the present invention provides a parking lot management system that includes:
a display unit installed in a parking lot that displays a code including a location code unique to the parking lot without using a physical parking ticket;
When exiting from the parking lot, if the code is received from the communication device of the user who is currently in the parking lot, based on the received code, the parking lot where the user is currently present and the user is about to leave the parking lot is determined. a parking lot identification unit that identifies parking lot identification units;
When leaving the parking lot, if user information that can identify the user's vehicle parked in one of the parking spaces in the parking lot is received from the communication device, the user information that is stored in advance with the received user information is received from the communication device. a payment unit that enables payment of the parking fee to be charged to the user for the specified parking lot by electronic payment when the verification with the user information is completed;
A parking lot management system including:
According to another aspect of the present invention, the parking lot management system includes the display unit installed in the parking lot and a management server installed in a remote location. A program executed by a computer of a communication device of a user using a parking lot,
The management server includes the parking lot specifying unit and the payment unit,
The communication device has multiple functions:
a function of transmitting the code to the management server when leaving the parking lot;
A function of transmitting user information that can identify the user's vehicle parked in any parking space in the parking lot to the management server when leaving the parking lot;
a function of receiving payment completion data from the management server indicating that the payment of the parking fee is completed when the parking fee charged to the user for the parking lot is settled by electronic payment;
including;
A program is provided that is executed by the computer to implement the plurality of functions.
According to another aspect of the present invention, there is provided a parking lot management system, comprising:
a display unit installed in a parking lot that displays a code including a location code unique to the parking lot without using a physical parking ticket;
When exiting the parking lot, when the code is received from the communication device of the user who is currently in the parking lot, based on the received code, the user is sent to the parking lot where the user is currently in the parking lot. a parking lot identification section that identifies what the person is about to leave;
a parking lot management unit that makes it possible to settle the parking fee to be charged to the user for the specified parking lot by electronic payment when leaving the parking lot and receiving the code; system is provided.

Further, according to the first aspect of the present invention, there is provided a parking lot management system, comprising:
a display unit installed in a parking lot and displaying a code including a location code unique to the parking lot without using a physical parking ticket;
a personal authentication unit that performs personal authentication on the user based on user information of the user himself/herself received from a communication device of a user currently in the parking lot when leaving the parking lot;
When exiting the parking lot, when the code is received from the communication device of the user who is currently in the parking lot, based on the received code, the user is sent to the parking lot where the user is currently in the parking lot. a parking lot identification section that identifies what the person is about to leave;
an exit time estimation unit that estimates a time when the user leaves the parking lot when the user leaves the parking lot and receives the code;
a parking fee calculation unit that calculates the amount of parking fee to be charged to the user for the specified parking lot based on the estimated exit time;
A parking lot management system is provided, including: a settlement unit for settling the calculated parking fee for the specified parking lot by electronic payment when the personal authentication is successful.

Further, according to a second aspect of the present invention, there is provided a parking lot management system, comprising:
a display unit installed in a parking lot and displaying a code including a location code unique to the parking lot without using a physical parking ticket;
When exiting from the parking lot and receiving the code from the communication device of the user who is currently in the parking lot, based on the location code of the received codes, it is determined that the user is currently in the parking lot. a parking lot specifying unit that specifies a parking lot from which the user is about to exit;
When the code is received, the user's exit time from the specified parking lot is estimated based on the reception time of the code, or if the code includes a time code representing the current time, the received A leaving time estimation unit that estimates the leaving time of the user from the specified parking lot based on the time code among the codes;
A parking lot management system is provided, comprising: an electronic payment unit that allows a parking fee to be charged to the user for the specified parking lot to be settled by electronic payment.

Further, according to an aspect of the present invention, there is provided a parking lot management system for managing a parking lot in a ticketless and cashless manner without using physical parking tickets, comprising:
a display unit installed in the parking lot and displaying a code including a location code unique to the parking lot without using a physical parking ticket;
a management server that manages the parking lot at a remote location,
The management server is
a personal authentication unit that performs personal authentication on the user based on user information of the user himself/herself received from a communication device of a user currently in the parking lot when leaving the parking lot;
When leaving the parking lot, if the code is received from the communication device of the user who is currently in the parking lot, based on the code, the user will be able to exit from the parking lot where the user is currently in the parking lot. a parking lot identification unit that identifies parking lot identification units;
A parking lot management system is provided, comprising: an electronic payment unit that allows a parking fee to be charged to the user for the specified parking lot to be settled by electronic payment when the personal authentication is successful.

According to another aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets, comprising:
a display unit installed in the parking lot and displaying a code including a location code unique to the parking lot without using a physical parking ticket;
When exiting from the parking lot, if the code is received from the communication device of a user who is currently in the parking lot, based on the code, the user is about to leave the parking lot in which the user is currently in the parking lot. a calculating unit that specifies a parking lot, estimates a time when the user leaves the parking lot, and calculates a parking fee to be charged to the user based on the estimated time of leaving the parking lot;
A parking lot management system is provided, including: a settlement unit for settling the calculated parking fee by electronic payment.

Further, according to one aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
Displaying parking-related information installed in the parking lot and related to parking for users using the parking lot, including information that allows the parking lot to be identified, without using a physical parking ticket. A display section;
a management server that manages the parking lot at a remote location,
The user's communication device is:
a personal information transmitting unit that transmits information about the user as personal information to the management server while the user is in the parking lot;
a parking-related information transmitting unit that transmits parking-related information displayed on the display unit and/or other parking-related information related thereto to the management server while in the parking lot;
The management server is
a personal authentication unit that, upon receiving the personal information from the communication device, performs personal authentication on the user based on the personal information;
a parking lot specifying unit that, upon receiving the parking-related information from the communication device after the personal authentication is established, specifies the parking lot where the user is currently located based on the parking-related information;
an electronic payment unit that settles the parking fee charged to the user by electronic payment;
A parking lot management system is provided, including: a payment completion data transmitter that transmits payment completion data indicating that the parking fee payment has been completed to the communication device.

According to the first aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
including a management server that manages the parking lot at a remote location,
The management server includes a registration unit that assigns a unique number to the user indicating that the user is eligible to use the parking lot and registers it in the memory in association with the user;
The management server is capable of communicating with communication devices of users in the parking lot,
The communication device accesses the management server when exiting the parking lot, thereby transmitting the user ID of the user to the management server, and a unique number assigned to the user in advance by the management server. a transmitter that transmits the information to the management server;
The parking lot management system is
a personal authentication unit that performs personal authentication for the user of the communication device based on the user ID received from the communication device;
a verification determination unit that determines whether or not a verification is established between the unique number received from the communication device and the unique number registered in advance in the memory by the management server in association with the user;
A parking lot management system is provided, comprising: a fee calculation unit that calculates a parking fee to be charged to the user when the personal authentication is successful and the verification is established.

According to a second aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
including a management server that manages the parking lot at a remote location,
The management server includes a registration unit that assigns a unique number to the user indicating that the user is eligible to use the parking lot and registers it in the memory in association with the user;
The management server is capable of communicating with communication devices of users in the parking lot,
The communication device accesses the management server when entering the parking lot, thereby transmitting the user ID of the user to the management server, and a unique number assigned to the user in advance by the management server. a transmitter that transmits the information to the management server;
The parking lot management system is
a personal authentication unit that performs personal authentication for the user of the communication device based on the user ID received from the communication device;
a verification determination unit that determines whether or not a verification is established between the unique number received from the communication device and the unique number registered in advance in the memory by the management server in association with the user;
A parking lot management system is provided, including: a usage permission unit that allows the user to use the parking lot when the personal authentication is successful and the verification is established.

According to a third aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
including a management server that manages the parking lot at a remote location,
The management server includes a registration unit that assigns a unique number to the user indicating that the user is eligible to use the parking lot and registers it in the memory in association with the user;
The management server is capable of communicating with communication devices of users in the parking lot,
The communication device accesses the management server when entering or exiting the parking lot, thereby transmitting the user ID of the user to the management server, and the management server including a transmitting unit that transmits a unique number given to the user in advance to the management server,
The parking lot management system is
When the user enters the parking lot or leaves the parking lot, the user's communication device acquires information from the parking lot or the current position measured by the user's communication device using its positioning function. a parking lot specifying unit that specifies the parking lot for entering or leaving the parking lot;
a personal authentication unit that performs personal authentication for the user of the communication device based on the user ID received from the communication device;
a verification determination unit that determines whether or not a verification is established between the unique number received from the communication device and the unique number registered in advance in the memory by the management server in association with the user;
a parking fee calculation unit that calculates a parking fee to be charged to the user when the parking lot where the user actually enters or exits the parking lot is specified, the personal authentication is successful, and the verification is completed; A parking lot management system is provided.

Further, according to the first aspect of the invention, there is provided a parking lot management system for managing a parking lot using a ticketless method and a cashless method that does not use physical parking tickets,
including a management server that manages the parking lot at a remote location,
The management server gives the user a unique number indicating that the user is eligible to use the parking lot, and registers it in the memory in association with the user,
The management server is capable of communicating with communication devices of users in the parking lot,
The communication device accesses the management server when exiting the parking lot, thereby transmitting the user ID of the user to the management server, and a unique number assigned to the user in advance by the management server. to the management server,
The parking lot management system is
a personal authentication unit that performs personal authentication for the user of the communication device based on the user ID received from the communication device;
a verification determination unit that determines whether or not a verification is established between the unique number received from the communication device and the unique number registered in advance in a memory by the management server;
A parking lot management system is provided, comprising: a fee calculation unit that calculates a parking fee to be charged to the user when the personal authentication is successful and the verification is established.

According to a second aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
including a management server that manages the parking lot at a remote location,
The management server gives the user a unique number indicating that the user is eligible to use the parking lot, and registers it in the memory in association with the user,
The management server is capable of communicating with communication devices of users in the parking lot,
The communication device accesses the management server when entering the parking lot, thereby transmitting the user ID of the user to the management server, and a unique number assigned to the user in advance by the management server. to the management server,
The parking lot management system is
a personal authentication unit that performs personal authentication for the user of the communication device based on the user ID received from the communication device;
a verification determination unit that determines whether or not a verification is established between the unique number received from the communication device and the unique number registered in advance in a memory by the management server;
A parking lot management system is provided, including: a usage permission unit that allows the user to use the parking lot when the personal authentication is successful and the verification is established.

Further, according to a third aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
a location information output unit that outputs location information that makes it possible to specify the parking lot where the user is located without using a physical parking ticket at the location of the parking lot;
a management server that manages the parking lot at a remote location,
The management server gives the user a unique number indicating that the user is eligible to use the parking lot, and registers it in the memory in association with the user,
The management server is capable of communicating with communication devices of users in the parking lot,
The communication device accesses the management server when leaving the parking lot, and thereby transmits the user ID of the user to the management server, as well as a unique number previously assigned to the user by the management server. to the management server,
The parking lot management system is
a parking lot identifying unit that identifies the parking lot where the user is located based on the location information output from the location information output unit;
a personal authentication unit that performs personal authentication for the user of the communication device based on the user ID received from the communication device;
a verification determination unit that determines whether or not a verification is established between the unique number received from the communication device and the unique number registered in advance in a memory by the management server;
A parking lot management system is provided, comprising: a fee calculation unit that calculates a parking fee to be charged to the user when the parking lot where the user is located is specified and the personal authentication is successful and the verification is completed. Ru.

According to the first aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
including a management server that manages the parking lot at a remote location,
The management server is capable of communicating with communication devices of users in the parking lot,
The communication device accesses the management server when exiting the parking lot, thereby transmitting a unique number given to the user in advance by the management server to the management server,
The management server is
a verification determination unit that determines whether or not a verification is established between the unique number received from the communication device and the unique number registered in advance in a memory by the management server;
a fee calculation unit that calculates a parking fee to be charged to the user when the verification is established;
A parking lot management system is provided in which the calculated parking fee is settled by electronic payment.

According to a second aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
including a management server that manages the parking lot at a remote location,
The management server is capable of communicating with communication devices of users in the parking lot,
The communication device accesses the management server when entering the parking lot, thereby transmitting a unique number given to the user in advance by the management server to the management server,
The management server is
a verification determination unit that determines whether or not a verification is established between the unique number received from the communication device and the unique number registered in advance in a memory by the management server;
If the verification is successful, a parking lot management system is provided, including: a usage permission section that allows the user to use the parking lot.

According to a third aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
a location information output unit that outputs location information that makes it possible to specify the parking lot where the user is located without using a physical parking ticket at the location of the parking lot;
a management server that manages the parking lot at a remote location,
The management server is capable of communicating with communication devices of users in the parking lot,
The communication device accesses the management server when leaving the parking lot, and thereby transmits a unique number given to the user in advance by the management server to the management server,
The management server is
a parking lot identifying unit that identifies the parking lot where the user is located based on the location information output from the location information output unit;
a verification determination unit that determines whether or not a verification is established between the unique number received from the communication device and the unique number registered in advance in a memory by the management server;
a fee calculation unit that calculates a parking fee to be charged to the user when the parking lot where the user is located is specified and the verification is completed;
A parking lot management system is provided in which the calculated parking fee is settled by electronic payment.

Further, according to one aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
Displaying parking-related information installed in the parking lot and related to parking for users using the parking lot, including information that allows the parking lot to be identified, without using a physical parking ticket. A display section;
a management server that manages the parking lot at a remote location,
The communication device of the user in the parking lot transmits the parking fee to the parking-related information displayed on the display unit and/or other information related thereto in order for the user to pay the parking fee when exiting the parking lot. sending parking related information to the management server;
The management server calculates the parking fee to be charged to the user based on the parking-related information received from the communication device, and when the calculated parking fee is settled by electronic payment, the calculation is performed. A parking lot management system is provided in which data representative of the parking lot management system is transmitted to the communication device.

Further, according to an aspect of the present invention, there is provided a parking lot management system for managing a parking lot in a ticketless and cashless manner without using physical parking tickets, comprising:
Displaying parking-related information installed in the parking lot and related to parking for users using the parking lot, including information that allows the parking lot to be identified, without using a physical parking ticket. A display section;
a management server that manages the parking lot at a remote location;
The communication device of the user in the parking lot transmits the parking-related information displayed on the display unit and/or another parking-related information related thereto to the management server,
The management server includes a fee calculation unit that calculates the parking fee to be charged to the user as a parking fee to be settled by electronic payment based on the parking related information received from the communication device, and the calculated parking fee is A parking lot management system is provided in which fees are settled through electronic payment.

Further, according to one aspect of the present invention, there is provided a parking lot management system for managing a ticketless and cashless parking lot that does not use physical parking tickets,
Parking-related information installed in the parking lot and related to parking for users using the parking lot, including information that allows the location of the parking lot to be specified, without using a physical parking ticket. a display section to display;
a management server that manages the parking lot at a remote location;
a communication device of a user in the parking lot, which transmits parking-related information displayed on the display unit and/or other parking-related information related thereto to the management server;
A parking lot management system is provided in which the management server includes a payment unit for paying the parking fee charged to the user by electronic payment based on parking related information received from the communication device.

Further, according to an aspect of the present invention, there is provided a parking lot management system for managing a parking lot, comprising:
A device installed in the parking lot and outputting fee information related to parking fees;
a management server that manages the parking lot at a remote location;
a communication device of a user in the parking lot, which inputs the output fee information and transmits the fee information or information based thereon to the management server;
A parking lot management system is provided in which the management server includes a payment unit for paying the parking fee by electronic payment in response to a request from a user via the communication device.

Further, according to one aspect of the present invention, a user accesses a management server of a parking lot manager online from any location via a communication device, and thereby obtains an electronic parking ticket from the parking lot manager. , a cardless parking management method that allows a user to park in a parking lot selected by the user using the electronic parking ticket, the method comprising:
When the communication device transmits an issuance request in order for the user to request the parking lot manager to issue the electronic parking ticket, the management server receives the issuance request from the communication device;
After receiving the information, the management server issues the electronic parking ticket to the user and displays the electronic parking ticket, which includes electronic parking ticket identification data for identifying the electronic parking ticket. transmitting something to the communication device;
When the user enters the parking lot, the communication terminal transmits a usage request and the electronic parking ticket identification data in order to start parking in the parking lot using the issued electronic parking ticket. , a step in which the management server receives the usage request and the electronic parking ticket identification data from the communication device;
After receiving the information, the management server verifies that the electronic parking ticket of the user is valid by comparing the received electronic parking ticket identification data with the electronic parking ticket identification data registered in advance in the memory of the management server. and, if it is determined that the electronic parking ticket is not valid, transmitting information indicating that the use of the electronic parking ticket is not permitted to the communication device.

According to another aspect of the present invention, a user accesses the management server of a parking lot manager online from any location via a communication device, thereby purchasing an electronic parking ticket from the parking lot manager. A cardless parking management method that enables a user to park in a parking lot selected by the user using the electronic parking ticket, the method comprising:
When the communication device transmits an issuance request in order for the user to request the parking lot manager to issue the electronic parking ticket, the management server receives the issuance request from the communication device;
After receiving the parking fee, when the user pays a parking fee corresponding to the length of the scheduled parking time specified by the user, the management server issues the electronic parking ticket to the user. transmitting data to be displayed that includes electronic parking ticket identification data for identifying the electronic parking ticket to the communication device;
When the user enters the parking lot, the communication terminal transmits a usage request and the electronic parking ticket identification data in order to start parking in the parking lot using the issued electronic parking ticket. , a step in which the management server receives the usage request and the electronic parking ticket identification data from the communication device;
After receiving the information, the management server verifies that the electronic parking ticket of the user is valid by comparing the received electronic parking ticket identification data with the electronic parking ticket identification data registered in advance in the memory of the management server. and, if it is determined that the electronic parking ticket is not valid, transmitting information indicating that the use of the electronic parking ticket is not permitted to the communication device.

According to one aspect of the present invention, a user accesses a parking lot manager's management server online from any location via a mobile terminal, thereby purchasing an electronic parking ticket from said parking lot manager, and purchasing an electronic parking ticket from said parking lot manager. A cardless parking management method that allows a user to park in a parking lot selected by the user using an electronic parking ticket, the method comprising:
a step in which the management server receives a request from the user's mobile terminal in order for the user to request the parking lot manager to issue the electronic parking ticket;
After receiving the parking fee, when the user pays a parking fee corresponding to the length of the scheduled parking time specified by the user, the management server issues the electronic parking ticket to the user. transmitting data to a user's mobile device for display;
When the user enters the parking lot, the management server receives the electronic parking ticket from the user's mobile terminal in order to start parking in the parking lot using the issued electronic parking ticket;
After receiving the information, the management server determines whether or not the electronic parking ticket of the user is valid. If it is determined that the electronic parking ticket is not valid, the management server sends information to the user's mobile phone indicating that the use of the electronic parking ticket is not permitted. The process of transmitting to the terminal,
If the length of the actual continuous parking time by the user exceeds the length of the scheduled parking time, the management server receives from the user's mobile terminal when the user leaves the parking lot;
After receiving the information, the management server calculates an additional parking fee corresponding to the length of the excess time, and when the user pays off the additional parking fee, the management server sends data indicating that the payment has been made to the user. A cardless parking management method is provided, including the steps of transmitting data to a mobile terminal.

Further, according to one aspect of the present invention, the parking lot is installed in each of a plurality of parking lots and displays a time code in which the current time is encoded differently from a time code displayed in other parking lots. A time code display device for use,
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 left the corresponding parking lot,
A parking lot time code display device is provided in which the time code has a location identification ability that can uniquely identify the location of the parking lot where the time code is displayed.

According to another aspect of the present invention, a time code in which the current time is encrypted is displayed in each of the plurality of parking lots differently from a time code displayed in other parking lots. A time code display method, comprising:
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 left the corresponding parking lot,
A parking lot time code display method is provided in which the time code has a location identification ability that can uniquely identify the location of the parking lot where the time code is displayed.

According to yet another aspect of the present invention, there is provided a time code display device for a parking lot that displays a time code in which the current time is encrypted in a parking lot,
The time code can be read and reproduced by a user of the parking lot as a known letter, number, symbol, or figure, or a combination thereof, and cannot be deciphered by the user but can be deciphered by the manager of the parking lot. Provided is a parking lot time code display device that can perform the present invention and, by deciphering the code, restore the information representing the current time.

The following aspects can be obtained by the present invention. Each aspect is divided into sections, each section is numbered, and the numbers of other sections are cited as necessary. This is to facilitate understanding of some of the technical features that can be adopted by the present invention and their combinations, and the technical features that can be adopted by the present invention and their combinations are limited to the following aspects. It should not be interpreted as such. That is, it should be interpreted that technical features not described in the following embodiments but described in this specification may be appropriately extracted and adopted as technical features of the present invention.

Furthermore, it should be noted that the description of each section in the form of quoting the numbers of other sections does not necessarily prevent the technical features described in each section from being separated and independent from the technical features described in other sections. It should be interpreted that the technical features described in each section can be made independent as appropriate depending on the nature of the technical features described in each section.

(1) A parking lot management method for managing a parking lot, comprising:
In the parking lot,
A clock and
A time code that allows the user of the parking lot to read and reproduce the current time measured by the clock as known characters, numbers, symbols, figures, or a combination thereof through encryption; an encryption unit that converts the code into a code that cannot be decrypted but can be decrypted by the parking lot manager;
A parking lot time code generation/display device is installed, including a display unit that displays the time code generated by the encryption unit.
The parking lot management method is
Information for identifying the electronic parking ticket transmitted by the user via a communication device in order to park in the parking lot using the electronic parking ticket when entering the parking lot; a receiving step at the time of parking, in which a communication unit receives a time code displayed on the display unit when entering the parking lot;
The processor decodes the time code received at the time of warehousing by referring to the decoding table, and based on the decoding result, estimates the time represented by the received time code as the warehousing time, and calculates the estimated warehousing time. is within a predetermined tolerance range determined with respect to the reception time at which the processor receives the time code, thereby determining whether the estimated warehousing time is appropriate. a time validity determination step;
a parking permitting step of permitting the user to use the parking lot if the estimated parking time is determined by the processor to be appropriate.

Throughout this specification, the term "electronic parking ticket" refers to a virtual parking ticket that does not exist, and in order for the user to use the electronic parking ticket, the information on the electronic parking ticket can be transferred to other media. means a form of parking ticket that does not require printing or display on the person to be presented to the other party.

(2) A parking lot management method for managing a parking lot, comprising:
In the parking lot,
A time code generated by encrypting the current time, which the user of the parking lot can read and reproduce as known letters, numbers, symbols, figures, or a combination thereof; A display is installed that displays information that cannot be deciphered but can be deciphered by the parking lot manager.
The parking lot management method is
Information for identifying the electronic parking ticket transmitted by the user via a communication device in order to park in the parking lot using the electronic parking ticket when entering the parking lot; a receiving step at the time of parking, in which a communication unit receives a time code displayed on the display unit when entering the parking lot;
The processor decodes the time code received at the time of warehousing by referring to the decoding table, and based on the decoding result, estimates the time represented by the received time code as the warehousing time, and calculates the estimated warehousing time. is within a predetermined tolerance range determined with respect to the reception time at which the processor receives the time code, thereby determining whether the estimated warehousing time is appropriate. a time validity determination step;
a parking permitting step of permitting the user to use the parking lot if the estimated parking time is determined by the processor to be appropriate.

(3) Furthermore,
Information for identifying the electronic parking ticket transmitted by the user via the communication device when exiting the parking lot, and a time code displayed on the display unit when exiting the parking lot. and a step of receiving the information at the time of leaving the warehouse in the communication unit;
The processor decodes the time code received at the time of leaving the warehouse by referring to the decryption table, and based on the decoding result, estimates the time represented by the received time code as the leaving time, and Determine whether the exit time is within a predetermined tolerance range determined with respect to the reception time when the processor receives the time code, thereby determining whether the estimated exit time code is valid. a step of determining the validity of the delivery time;
When the processor determines that the estimated parking time is appropriate, the length of time elapsed from the estimated parking time to the estimated parking time is determined as the parking time by the user. The parking lot management method according to item (1) or (2), including the step of calculating parking time.

(4) Furthermore,
an issuance request receiving step in which the communication unit receives an issuance request sent by the user via the communication device to request the parking manager to issue the electronic parking ticket;
The processor, in response to the received issuance request, issues the electronic parking ticket to the user and transmits it to the user's communication device, provided that the user prepays a predetermined amount of the fee. The parking lot management method according to any one of paragraphs (1) to (3), including the step of issuing an electronic parking ticket.

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

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

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

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

According to the present invention, it is possible to provide a service that allows users to park in a parking lot without a card, 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 of the ticket issuing machine shown in FIG. 1. FIG. 3 is a perspective view of the ticket issuing machine shown in FIG. 2 with the door open. FIG. 4 is a block diagram showing the component configuration of the ticket issuing machine shown in FIG. 2. FIG. 5 is a flowchart conceptually representing the ticket issuing/settlement program executed by the computer shown in FIG. 6(a) to 6(d) are front views showing a plurality of images displayed on the screen of the display device shown in FIG. 2. FIG. FIG. 7(a) is a front view showing an example of a parking ticket and receipt issued by the ticket issuing machine shown in FIG. 2 after payment of a prepaid parking fee, and FIG. FIG. 4 is a front view showing an example of a receipt issued by the parking lot after payment of an additional parking fee. FIG. 8(a) is a vertical cross-sectional view showing the parking ticket shown in FIG. 7(a) immediately after it is issued, and FIG. 8(b) is a vertical cross-sectional view showing the parking ticket shown in FIG. FIG. FIG. 9(a) is a side sectional view showing the parking ticket shown in FIG. 7(a) attached to the back of the windshield of a parked vehicle, and FIG. 9(b) is a side sectional view showing the parking ticket shown in FIG. , is a perspective view showing a part of the display sheet peeled off from the separator and folded. FIG. 10 is a perspective view showing how the parking ticket shown in FIG. 7(a) is attached to the back surface of the windshield of a parked vehicle. 11(a) to (c) show the structure of an example of the encrypted data printed on the receipt shown in FIGS. 7(a) and (b), the corresponding real data, and the conversion from the real data to the encrypted data. FIG. 3 is a diagram for explaining a conversion process. FIG. 12 shows how a user uses his or her mobile phone to communicate the encrypted data printed on the receipt shown in FIGS. 7(a) and 7(b) to a parking lot manager located in a remote location. FIG. 3 is a perspective view for explaining how the parking lot manager converts received encrypted data into real data. FIGS. 13(a) to 13(c) are diagrams for conceptually explaining the process of generating and displaying time codes, which are parts of the ticket issuing machine shown in FIG. 4 that are related to the parking lot management method. 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 processes shown in FIGS. 13(a) to 13(c) (time code generation and display). It is a flowchart. FIG. 15 is a conceptual system diagram for explaining the entire system in which the parking lot management method is implemented. FIG. 16 is a flowchart conceptually representing a first subprogram that is part of the electronic parking ticket processing program executed in the management server shown in FIG. 15. FIG. 17 is a flowchart conceptually representing a second subprogram that 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 representing a third subprogram that is yet another part of the electronic parking ticket processing program executed in the management server shown in FIG. 15. FIG. 19 is a diagram conceptually representing the member DB shown in FIG. 15. FIG. 20 is a diagram conceptually representing the electronic parking ticket DB shown in FIG. 15. FIG. 21 is a diagram showing an example of an electronic parking ticket issued by executing the electronic parking ticket processing program. FIG. 22 is a sequence diagram for explaining the process of member registration performed by executing the electronic parking ticket processing program. FIG. 23 is a sequence diagram for explaining the process of issuing an electronic parking ticket performed by executing the electronic parking ticket processing program. FIG. 24 is a sequence diagram for explaining the process of permitting the use of an electronic parking ticket, which is performed by executing the electronic parking ticket processing program. FIG. 25 is a diagram showing an example of a receipt issued by executing the electronic parking ticket processing program. FIG. 26 is a sequence diagram for explaining the process of settling the parking fee for extended parking, which is performed by executing the electronic parking ticket processing program. FIG. 27 is a sequence diagram for explaining the process of prompting for exit, which is executed in the management server shown in FIG. 15. FIG. 28 shows a second subprogram that replaces the second subprogram shown in FIG. 17 in the electronic parking ticket processing program executed in the management server to execute the parking lot management method according to the second exemplary embodiment of the present invention. 4 is a flowchart conceptually representing four subprograms. FIG. 29 is a flowchart conceptually representing a fifth subprogram that replaces the third subprogram shown in FIG. 18 in the electronic parking ticket processing program in the second embodiment. FIG. 30 is a sequence diagram for explaining the process of permitting parking using an electronic parking ticket, which is performed by executing the electronic parking ticket processing program in the second embodiment. FIG. 31 is a sequence diagram for explaining the process of paying the fee at the end of parking using an electronic parking ticket, which is performed by executing the electronic parking ticket processing program in the second embodiment. FIG. 32 is a diagram showing an example of a receipt issued by executing the electronic parking ticket processing program in the second embodiment. FIG. 33 is a sequence diagram for explaining the process of prompting for exit, which is executed by the management server in the second embodiment.

Hereinafter, parking lot management methods according to some exemplary embodiments of the present invention will be described in detail based on the drawings.

<First embodiment>

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

This parking lot 10 has a plurality of parking positions (parking spaces) that enable simultaneous parking of a plurality of cars. A single ticket issuing machine (generally referred to as a "settlement machine") 20 is installed near the only entrance 12 (both an entrance and an exit) of this parking lot 10 for multiple parking lots. Commonly located at all locations, these machines are installed as centralized ticket issuing machines. This parking lot 10 is an unmanned parking lot where there is no full-time resident who manages the parking lot, and the user who is the driver pays the parking fee to the ticket issuing machine 20.

In this embodiment, the user is in the parking lot 10 and can purchase an electronic parking ticket (usually not for one parking trip) at any location without being requested access to the parking lot manager from there. , a parking ticket that allows you to park multiple times, and is equivalent to a coupon ticket for transportation such as trains and buses) from the parking lot manager online, and use that electronic parking ticket to park at this parking lot. It is possible to park at 10.

However, in the present embodiment, instead of parking in this manner, each time the user attempts to use the parking lot 10, the user selects the planned parking location for the current parking prior to parking (when entering the parking lot). By specifying the length of time and paying the corresponding parking fee as a prepaid parking fee to the ticket issuing machine 20, you can receive a parking ticket printed on paper (i.e., a physical ticket, an actual ticket or It is also possible to purchase a paper parking ticket (card) from the ticket issuing machine 20 and park in this parking lot 10 using the paper parking ticket.

In other words, in this embodiment, the user can purchase new parking (cashless and cardless) using an electronic parking ticket (virtual ticket) that can be purchased by online access to the parking lot manager from any location. (hereinafter referred to as "cardless parking")"), and regular parking using a physical parking ticket that can only be purchased from the ticket issuing machine 20 installed in the parking lot 10 (both cash and physical tickets). (hereinafter referred to as "normal parking") depending on your preference.

Additionally, regarding the definition of the term "vehicle", in this "Detailed Description of the Invention" section, the term "vehicle" only means an automobile; , the term "vehicle" should be interpreted to include not only automobiles but also all types of moving objects such as bicycles and motorcycles.

There are two types of parking sections on the site of the parking lot 10. There is a section for renting parking spaces (temporary storage section or daily rental section) to each vehicle user on a daily basis, and a monthly parking section for each vehicle user, subject to a prior contract. This is a section for renting out parking spaces (monthly section). The ticket issuing machine 20 is used for the temporary storage section. Hereinafter, when the parking lot 10 is simply referred to as the parking lot 10, it means only the temporary storage section, that is, the area where the ticket issuing machine 20 is used.

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

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

2 shows the ticket issuing machine 20 in a front view, FIG. 3 shows the ticket issuing machine 20 in a perspective view with the door 24 open, and FIG. 4 shows the ticket issuing machine 20 in a front view. The configuration of 20 parts is shown in a block diagram. FIG. 5 conceptually shows a flowchart of the ticket issuing/settlement program executed by the computer 100 in the control board 34 shown in FIG. 6(a) to 6(d) show front views of a plurality of images displayed on the screen of the display device 36 shown in FIG. 2.

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

The parking lot 10 is a prepaid unmanned parking lot with a plurality of parking positions, and is equipped with devices (for example, an exit gate device, a wheel drive system, etc.) for preventing vehicles from leaving the parking lot (preventing exit from the parking lot 10). The vehicle does not have a stopping device (for example, a flap type or a retractable type), and the user can freely select any one of the plurality of parking positions to park his/her vehicle (selection). (The parked parking location is not monitored by the ticket issuing machine 20). The ticket issuing machine 20 is used for the parking lot 10 configured in this manner.

Here, the ticket issuing machine 20 will be explained in more detail. This ticket issuing machine 20 has a fee settlement function, but does not have a change function or a communication function. This ticket issuing machine 20 requires the user to pay the parking fee only in coins rather than banknotes. The ticket issuing machine 20 also allows the user to input a user identification number, input vehicle identification information (for example, vehicle number) about the user's vehicle, and specify which parking location the user selects from among a plurality of parking locations. , do not request.

The ticket issuing machine 20 has a ticket issuing button 70 and a fee settlement button 74, as shown in FIG. When the user presses the ticket issuing button 70 after paying the prepaid parking fee prior to starting parking, the ticket issuing machine 20 issues a parking ticket 80 indicating that parking is permitted (see FIG. 7(a)) and a prepaid parking ticket. It has a ticket issuing function that issues a receipt 81a (see FIG. 7(a)) indicating that the fee has been settled in two sheets. Furthermore, when the user presses the fee settlement button 74 after completing parking and paying the additional parking fee, the ticket issuing machine 20 generates a receipt 81b (see FIG. 7(b)) indicating that the additional parking fee has been paid. ) has a fee settlement function that issues a fee.

In this embodiment, the two-page parking ticket issued after payment of the prepaid parking fee consists of the parking ticket 80 and the receipt 81a. Separated from each other, only the parking ticket 80 can be left in the parked vehicle, and the receipt 81a can be carried. As will be described later, the receipt 81a has the end time of the valid parking time (the time period during which the user is permitted to park) printed thereon, and the user can cancel the end of the valid parking time at any time when he or she is away from the parked vehicle. It is convenient for the user to carry this receipt 81a with him so that he can refer to the time.

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

As shown in FIG. 3, this ticket issuing machine 20 includes a coin processing unit 30, a safe 32, a control board 34, a display 36, and a printer 40 that prints and issues a parking ticket 80 and receipts 81a and 81b. It is configured to have the following. Among these parts, only the coin processing unit 30 is attached to the back of the door 24, and the remaining parts are attached inside 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 prints on continuous sheets that are fed from the roller 42 one sheet at a time. After the printer 40 finishes printing, the printer 40 cuts the continuous sheet with a cutter (not shown) at any time, and after the prepaid parking fee is paid, the printer 40 cuts the continuous sheet into two sheets, a parking ticket 80 and a receipt 81a, for additional parking. After paying the fee, one receipt 81b is cut off. However, as shown in FIG. 7(a), a tear line 89 is formed between the parking ticket 80 and the receipt 81a, which are bound in two sheets, and the user can cut them out along the tear line 89. Parking ticket 80 and receipt 81a can be easily separated from each other.

The cutter has a cutting blade (not shown), and cuts the continuous sheet in the width direction by moving the cutting blade in the width direction of the continuous sheet. Further, the cutter can adopt a method of completely cutting the continuous sheet in the width direction, or a method of cutting the continuous sheet in the width direction leaving only a part in the width direction.

As shown in FIGS. 2 and 4, the coin processing unit 30 includes a coin input slot 50, a return lever 52, and a coin selector (which determines the type of coin inserted and determines whether the inserted coin is a counterfeit coin). 54 and a coin return slot 56. Among the inserted coins, those that are not returned to the user through the coin return port 56 are stored in the safe 32. As shown in FIG. 4, a control board 34 is connected to the coin selector 54 for data communication. A signal indicating the number of sheets (including information as to whether or not there are sheets) and the number of sheets are received.

As shown in FIG. 2, the front surface of the door 24 includes a transmission window 60 through which display light from the screen of the display 36 (for example, a liquid crystal display) passes, a coin slot 50, a return lever 52, and a coin return slot 56. and a discharge port 64 for discharging the parking ticket 80 and receipts 81a, 81b printed and discharged by the printer 40. The transparent window 60 also has the 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. There is. The ticket issuing button 70 and the fare 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.

Both the ticket issuing button 70 and the fee settlement button 74 are configured as real physical switches, but are not limited to this, and for example, virtual switches ( For example, it may be configured as a button, key, icon).

The control board 34 is mainly configured with a computer 100. This control board 34 has a built-in clock 102, and can always obtain the current date and time (for example, the date and time when the ticket issue button 70 was pressed, and the date and time when the fee settlement button 74 was pressed). This control board 34 further has a built-in memory 104. An encrypted table, which will be described later, is stored in the memory 104 in a state where it can be rewritten only by an authorized person.

It should be noted that the control board 34 can have a format in which the same functions as the computer 100 are realized by a sequencer (sequence control).

Furthermore, although not shown, the ticket issuing machine 20 has a power supply unit. The power supply unit is a power source (for example, a commercial power source, a generator such as a solar cell or a wind power generator installed in the parking lot 10, a rechargeable battery installed in the parking lot 10, and a commercial power source or a generator). It has a power source (such as one charged by a power source), and supplies power from the power source to each electric/electronic component in the ticket issuing machine 20, thereby operating the ticket issuing machine 20. This power supply unit additionally has a backup circuit having a power storage function, for example, so that even if the power supply from the power source is temporarily stopped, the operation of the ticket issuing machine 20 is not affected by it. . This ensures that the ticket issuing machine 20 is always operational.

When the ticket issuing/settlement program shown in FIG. 5 is executed by the computer 100, first, in step S1, an initial screen shown in FIG. 6(a) is displayed on the screen of the display 36. Next, in step S2, it is determined based on the signal from the coin selector 54 whether or not the user has inserted a coin. If no coins have 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 up to that point is calculated as the inserted amount.

Next, in step S4, from the calculated input amount, the parking time corresponding to the input amount is calculated as the parking time (if the parking fee paid this time is a prepaid parking fee, it means the valid parking time). , if the parking fee paid this time is an additional parking fee, it is calculated as an extended parking time). Since the relationship between the input amount and the length of the parking time, that is, the hourly rate setting is known to the computer 100, the computer 100 can calculate the parking time from the input amount according to the rate setting. Regarding the fee setting, for example, the parking lot manager can input it individually for each hour by operating the touch panel of the display 36.

According to an example of the above price setting, continuous parking time is 300 yen for up to 2 hours, 400 yen for up to 4 hours, 500 yen for up to 6 hours, 1000 yen for up to 12 hours, and 1500 yen for up to 24 hours. be. Under the fee settings in this example, if the user pays 400 yen as a prepaid parking fee, for example, as in the example shown in FIG. 7, the computer 100 will calculate 4 hours as the valid parking time. Furthermore, if the user pays 300 yen as an additional parking fee, two hours will be calculated as the extended parking time.

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

Subsequently, in step S6, it is determined whether the ticket issue button 70 has been pressed. If the ticket issue 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 coin insertion is started, steps S2 to S7 are repeated until either the ticket issuing button 70 or the fee settlement button 74 is pressed. As a result, each time the user inserts a coin into the coin slot 50, the total amount of coins inserted by the user from the start of insertion to the present time is calculated as the input amount, and from the calculated input amount, The parking time commensurate with the input amount is calculated, and the calculated input amount and parking time (valid parking time or extended parking time) are displayed on the screen of the display 36.

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

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

In this embodiment, the encrypted data 130 is defined by a symbol of nine digits (more or fewer digits may be used) arranged in a row, as shown in FIG. 11(a). has been done. The symbol of each digit is selected, for example, as one of ten numbers from 0 to 9 and a plurality of alphabets. The multi-digit symbol is divided into multiple groups and printed on the receipt 81a, and adjacent groups are connected with a hyphen, allowing the user to pronounce the multi-digit symbol at once in one breath. Instead of ``,'', several punctuation marks are added to make it easier and more accurate to pronounce the pronunciation.

An example of the general structure of the actual data (in order to reduce the number of digits in the actual data, the notation of the Western calendar is omitted) is as shown in Figure 11(b). However, the length of the valid parking time is TT time.'' As shown in FIG. 11(c), this 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 the parking time (if the applicable receipt is for a prepaid parking fee, it means the valid parking time; if the applicable receipt is for an additional parking fee, it means the extended parking time); It has five elements, the number TT representing.

As shown in FIG. 11(c), the encryption table includes a monthly encryption table that is referenced to encrypt the number MM representing the month, and a monthly encryption table that is referenced to encrypt the number DD representing the day. a daily encryption table that is referenced to encrypt the number hh representing the hour of the time, and a time unit encryption table that is referenced to encrypt the number mm that represents the minute of the time. The parking lot has a minute-by-minute encryption table, and a time-based encryption table, which is referred to in order to encrypt the number TT representing the length of the parking time. The above five elements are each encrypted by referring to the corresponding encryption table, thereby creating nine-digit encrypted data 130.

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

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

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

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

Specifically, as shown in FIG. 7(a), the parking ticket 80 includes information for specifying the end time of the valid parking time corresponding to the amount of the prepaid parking fee paid by the user and the location of the parking lot 10. is printed. Furthermore, the receipt 81a is printed with the parking time, the amount of the prepaid parking fee paid by the user, the end time of the valid parking time, and a display for specifying the location of the parking lot 10. Encrypted data 130 exemplified as "ABC-DEF-ABC" is also printed on the receipt 81a. This encrypted data 130, as shown in text in FIG. (This is equivalent to the time when the ticket was issued.) and the length of the valid parking time (This is equivalent to the amount of prepaid parking fee paid.) is encrypted.

On the other hand, when the fare settlement button 74 is pressed instead of the ticket issue button 70, a 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's operation of 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 the extended parking time.

Subsequently, in step S12, similarly to step S9, the time when the receipt 81b was issued because the user paid the additional parking fee (this is equivalent to the time when the user paid the additional parking fee) and the above-mentioned Actual data representing the length of the extended parking time (which is equivalent to the amount of additional parking fee paid) is converted to encrypted data 140 by referring to the encrypted table.

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

Specifically, as shown in FIG. 7(b), the receipt 81b includes an indication for specifying the date and time when the receipt 81b was issued, the amount of the additional parking fee, and the location of the parking lot 10. is printed.

Furthermore, encrypted data 140 exemplified as "123-456-789" is also printed on the receipt 81b. This encrypted data 140 is encrypted actual data representing the date and time when the receipt 81b was issued and the length of the extended parking time.

FIG. 7A shows a front view of a two-page parking ticket 80 and a receipt 81a, while FIG. 7B shows a front view of a receipt 81b. The two parking ticket 80 and receipt 81a correspond to two parking tickets 80, and in the two parking ticket 80 and receipt 81a, the parking ticket 80 and the receipt 81a have the same size and structure. Further, the receipt 81b corresponds to one parking ticket 80, and has the same size and configuration as the parking ticket 80. Hereinafter, in order to simplify the explanation, only the configuration of the parking ticket 80 will be representatively explained.

The parking ticket 80 includes a display sheet (printed 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, which are laminated in this 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. When the display sheet 82 is peeled off from the surface of the separator 84, the adhesive of the adhesive layer 83 is applied to the surface of the separator 84. It does not adhere to.

As shown in FIG. 7A, in one parking ticket 80, the outer periphery of the display sheet 82 is located inside the outer periphery of the separator 84. The original fabric to be wound around the roller 42 is composed of a continuous separator 84 and a plurality of display sheets 82 (blank) arranged in a row with gaps between them and adhered to each other.

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 sheets 82 are not cut. On the other hand, no glue is attached to the surface of the portion of the separator 84 that is exposed in the gap between the display sheets 82 .

Therefore, according to the present embodiment, the adhesive of the adhesive layer 83 does not adhere to the cutting blade when cutting a continuous sheet, and a manager dispatched to the site once or several times a day (for example, The frequency of maintenance of the cutter by service personnel, workers who patrol multiple parking lots, and patrolling supervisors is reduced, and as a result, the personnel costs incurred by the administrator are reduced.

However, in this embodiment, for the receipt 81b, the separator 84 is completely cut by the cutter to the length of one sheet, whereas for the receipt 81b, the separator 84 is cut for the length of two sheets. completely cut to length. However, as described above, for the two-sheet binding, as shown in FIG. 7(a), the separator 84 is partially cut between the parking ticket 80 and the receipt 81a by the cutter, Thereby, a perforation 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 exists to allow a user to peel 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. 8(b), when the user peels off a part of the display sheet 82 (the area surrounded by the cutting line 90) from the separator 84 and bends it along the 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 coated on 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 the parking by the user is not illegal parking, the user places the parking ticket 80 received in exchange for coin insertion at the front desk of the parked vehicle, as shown in FIG. 9(b). It is required to attach it to the back side of the glass 110. Therefore, as shown in FIG. 9(a), the user locally cuts a designated part of the parking ticket 80 (the area surrounded by the cutting line 90 and which will eventually become the folded part 92). After peeling it off and bending it, 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. 9(b). As a result, as shown in FIG. display for identifying the location of the vehicle) can be visually observed from the outside at any time.

The user is required to pay an additional parking fee if the actual parking time exceeds the valid parking time. However, as described above, the parking lot 10 is unmanned and does not have a device that prevents parked vehicles from leaving the parking lot unless the necessary additional parking fee is paid. , the fact that the necessary additional parking fee has been paid is notified from a location such as the parking lot 10, inside the car, or at home to a parking lot manager located at a remote management center using a communication device such as a mobile phone or landline phone. required.

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

Upon receiving the voice representing the encrypted data 130, 140 uttered by the user, the parking lot manager located at the management center operates the input device (for example, keyboard, touch screen, mouse, etc.) of the decryptor 180. , enter the symbol that corresponds to the user's voice. The encrypted data 130, 140 are input, and the decryptor 180 converts the input encrypted data 130, 140 into a decryption table that is compatible with the encryption table and is installed in the decryptor 180. Restore to real data according to the information given.

As a result, the parking lot manager can determine the length of the actual parking time (for example, , the length of elapsed time from the parking time specified by the encrypted data 130 to the time when the additional parking fee was paid, specified by the encrypted data 140), and furthermore, it is possible to know the length of time elapsed from the parking time specified by the encrypted data 130 to the time when the additional parking fee was paid, which is specified by the encrypted data 140. It is also possible to know the total amount (for example, the sum of the amount of the prepaid parking fee specified by the encrypted data 130 and the amount of the additional parking fee specified by the encrypted data 140), and by extension, the total amount of the parking fee is , it is possible to correctly judge whether or not the parking time is insufficient in relation to the length of the actual parking time.

Since the decryption table stored in the decryptor 180 cannot be known by anyone, even the parking lot manager, unless he has authority, the security of the decryption table is high.

As is clear from the above description, according to the present embodiment, at the time of issuing the receipts 81a and 81b, the encrypted data 130 and 140 are written in symbols that can be pronounced by the user on each of the receipts 81a and 81b. By simply requesting the user to print the encrypted data 130, 140 and to transmit the encrypted data 130, 140 to the parking lot manager by voice, the parking manager can correctly determine whether there is a shortage of parking fees. Therefore, the user is able to safely park the vehicle beyond the valid parking time without being burdened with a large burden, and the usability of the parking lot 10 and thus the operating rate are improved.

Additionally, in this embodiment, the user transmits the encrypted data 130 and 140 by voice input, but for example, instead of the voice input, data input (for example, real or virtual This can be done by key input using a key or image input using an image reader).

Normal parking has been explained above, but next, cardless parking will be explained.

As is clear from the above description, in this embodiment, neither the parking lot 10 nor the ticket issuing machine 20 has equipment for detecting the fact that each user has entered or exited the parking lot 10. In addition, in the case of cardless parking, as will be detailed later, the user can use his or her communication device (e.g., mobile phone or smart phone) to initiate parking using his or her electronic parking ticket. However, at that time, neither the parking lot 10 nor the ticket issuing machine 20 can detect the fact that the user is actually parking in the parking lot 10. If the user simply uses his/her own communication device, for example, unless the user uses the GPS function of the communication device, the fact that the user has actually entered the parking lot 10 cannot be detected.

On the other hand, in this embodiment, the ticket issuing machine 20 uses the current time measured by the clock 102 as real data, as shown in FIG. (stored in the memory 104 of the computer), thereby obtaining the time code 190 as encrypted data. The time code 190 cannot be deciphered by the user but can be deciphered by the parking lot manager (for example, similar to the encrypted codes 130 and 140, the time code 190 cannot be deciphered by the user but can be pronounced uniquely). be.

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

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

The ticket issuing machine 20 further displays a location code 192 unique to the parking lot 10, indicating the location of the parking lot 10, on the screen of the display 36 along with the time code 190, as shown in FIG. 13(a). Designed to display something that is identifiable.

FIG. 14 conceptually shows a flowchart of a code display program executed by the computer 100 of the ticket issuing machine 20 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.

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

By repeatedly executing this code display program, the time code 190 and the location code 192 are displayed on the screen of the display 36 on the same screen as illustrated in FIG. 13(a) and as illustrated in FIG. displayed at all times in a position that does not obscure the message being sent.

Here, to explain the time code 190 in detail, the time code 190 has time dependence because it is generated differently at different times on the same day.

Further, the time code 190 is generated in such a way that it cannot be deciphered by any user of the parking lot 10, even though the user is not actually entering or exiting the parking lot 10 at any time. Or, an attempt is made to impersonate a user who entered or left the parking lot 10 at a certain time, even though the user actually entered or left the parking lot 10 at a different time, and the display 36 displays the message at that certain time. Even if the user tries to predict the time code 190 that should be true, the user cannot obtain the true time code 190. Therefore, the time code 190 also has confidentiality for the user.

Further, the time code 190 is only displayed on the display 36 of the parking lot 10 where the user is actually attempting to park or is parked, so the user must: I have to go to the site called parking lot 10. Therefore, the time code 190 has location dependence.

In this way, the time code 190 has time dependence, confidentiality to the user, and location dependence. Therefore, the time code 190 that the user actually saw in the parking lot 10 can be viewed on the display. As long as the time code 190 is sent to the management server 202 at a time that is not significantly delayed from the time displayed in the time code 36 (a time that is within the set allowable range), the time code 190 will not indicate the fact that the user actually entered or left the parking lot 10. This will serve as strong evidence to support it.

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

In an exemplary scenario where the same parking lot manager manages multiple parking lots (including parking lot 10) and a time of day code 190 is to be displayed in each of those parking lots, the time of day code 190 is 190 is preferably generated differently depending on the location of the parking lot even if the time is the same. In this preferred embodiment, the time code 190 displayed in the parking lot 10 has location identification.

Here, the term "place identification ability" may be defined only by the feature that the time code 190 differs depending on the location, but not by 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 it differs depending on the location, but also the feature that the location can be uniquely identified from the time code 190.

However, in this embodiment, in order for the management server 202 to identify the location of the parking lot 10 that the user is using from the information received from the user, the time code 190 does not have location identification ability. Good too. This is because, in this embodiment, the location code 192 having location identification power is also displayed to the user in the parking lot 10 together with the time code 190.

Therefore, the correct time code 190 for the parking lot 10 that the user is about to use cannot be obtained unless the user is actually in the parking lot 10 and observes the screen of the display 36. Therefore, if the user sends the observed time code 190 together with the location code 192 to the parking lot manager at a remote location when entering the parking lot, the parking lot manager can It becomes possible to estimate at what time the vehicle entered the warehouse.

Specifically, the time code 190 and the location code 192 are communicated by the user to the parking lot manager via his/her own communication device at the time of parking. Upon receiving the time code 190 and location code 192, the parking lot manager converts the time code 190 into real data by referring to the decryption table 234 (see FIG. 15) that matches the time encryption table. Convert to 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.

The parking lot manager further uses the current time obtained by decoding 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 (the parking lot manager If the difference from the reception time when the user received the time code 190 is within the set tolerance range (for example, 30 minutes), the user actually receives the current time obtained by decrypting the time code 190 (FIG. 13). As exemplified in (c), if there is a time range, the user may enter the site at any time between the earliest time within that time range and the current time measured by the parking lot manager. It is possible to estimate the fact that the vehicle has entered the parking lot 10 (parking in the parking lot 10 has started).

On the other hand, the parking lot manager may not be able to successfully decipher the received time code 190, or even if the parking lot manager is able to successfully decipher the code, the current time obtained thereby and the time code 190 measured by the parking lot manager may be different from each other. If it is determined that the difference from the current time exceeds the setting allowable range, the time code 190 sent by the user to the parking lot manager does not exist as a time code 190 in the ticket issuing machine 20, or Or, even if there is, the time the user sent the time code 190 to the parking lot manager is much later than the time the user observed the time code 190 on the display 36, so the user may Even if it is valid, parking using it will be refused by the parking lot manager.

In addition, if the length of the allowable setting time is set to be long, the time when the user observed the time code 190 on the display 36 and the time code 190 will be transmitted to the parking lot manager. This means that the time gap between the two times may be long to some extent. This increases the range in which the user can choose the transmission time, which in turn brings the following advantages.

That is, for example, when a user parks his/her own vehicle in the parking lot 10 and is about to walk out of the parking lot 10, the user memorizes the time code 190 displayed on the display 36, and then If you need to walk from parking lot 10 to the nearest station, etc., and then use a means of transportation such as a train or bus, after getting on that means of transportation, remember the time code 190 and return to the parking lot. Sending to the administrator is permitted.

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

The characteristic elements of the ticket issuing machine 20 for cardless parking have been explained in detail above, but below, with reference to FIGS. 15 to 27, the service for issuing electronic parking tickets to users will be explained in detail. Explain the content.

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

In the system 200, a plurality of users and a plurality of persons in charge (each person is assigned to the parking lot 10 managed by the parking lot manager and other plural parking lots) work according to the instructions of the parking lot manager. The management server 202 is connected wirelessly or by wire to the management server 202 via the Internet 204, which is an example of a global communication network. There is.

In order to perform transmission and reception, the management server 202 includes a transmitter 210 that transmits signals or data to an external destination, and a receiver 212 that receives signals or data from an external source.

Management server 202 further includes a processor 220 and storage 222 (eg, ROM, RAM). In order to provide the above-mentioned service, the processor 220 executes the electronic parking ticket processing program illustratively and conceptually shown in the flowcharts of 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 further includes a member database (hereinafter referred to as "DB", the same applies in the figure) 230 illustrated in FIG. 19, and an electronic parking ticket database (hereinafter referred to as "DB") illustrated in FIG. ) 232 and the decryption table 234.

Although not shown, the management server 202 has an internal clock for measuring the current time, similar to the ticket issuing machine 20, or can use the measurement results of an external clock.

First, to briefly explain the contents of this service, according to this service, in response to an issuance request from a user, the management server 200 issues a request to the user on the condition that the user pays a predetermined amount of parking fee in advance. In response, an electronic parking ticket 250 illustrated in FIG. 21 is issued. When the user plans to park in the parking lot 10 using the issued electronic parking ticket 250, the user will receive a parking permission request and the time code 190 displayed on the display 36 when entering the parking lot 10. is sent to the management server 202, the management server 202 decodes the received time code 190 by referring to the decryption table 234, and based on the decryption result, the warehousing time represented by the received time code 190 is The management server 202 determines whether or not the time code 190 is within a predetermined permissible range determined based on the reception time at which the time code 190 is received, thereby determining whether the received time code 190 is valid.

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

[Member registration]

To explain more specifically, this service includes a process of registering a user as a member in order to acquire qualifications for using the electronic parking ticket 250, a process of issuing the electronic parking ticket 250 to the user, and a process when parking starts. A process of permitting the user to use the electronic parking ticket 250, and only if the user has extended parking, at the end of parking, an additional parking fee corresponding to the length of the extended parking time is paid and settled by electronic payment. The steps for doing so are performed in that order.

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

[Issuance of electronic parking ticket]

Next, the user accesses the management server 202, as illustrated in the sequence diagram of FIG. 23, in order to request the parking lot manager to issue the electronic parking ticket 250. After that, the user transmits the user ID and password to the management server 202, and then the management server 202 performs personal authentication. Subsequently, the user transmits the number of points he/she wishes to obtain to the management server 202, and the management server 202 calculates the fee required to obtain the number of points. When the user pays the fee, the management server 202 assigns a unique ticket number to the electronic parking ticket 250 to be issued, and further assigns the number of valid points, and stores this information as illustrated in FIG. Register in the electronic parking ticket DB 232. After that, the management server 202 issues an electronic parking ticket 250 illustrated in FIG. 21 to the user.

[Permission to use electronic parking ticket]

After that, when the user enters the parking lot 10, in order to start parking in the parking lot 10 using the issued electronic parking ticket 250, the user uses the management server 202 as illustrated in the sequence diagram in FIG. access. Thereafter, the user transmits the unique ticket number assigned to the electronic parking ticket 250 that the user wishes to use 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 location code 192 displayed on the display 36 to the management server 202. The management server 202 decrypts the received time code 190 to estimate the user's warehousing time, and compares it with the current time measured by the management server 202 to confirm the validity of the estimated warehousing time. do.

Thereafter, the user transmits the parking conditions to the management server 202. The parking conditions include the length of time the user wishes to park in the parking lot 10 from now on. Subsequently, the management server 202 calculates the number of usage points required to grant the user that parking time. The management server 202 further calculates the number of remaining points by subtracting the number of used points from the current number of valid points, and when confirming that the number of remaining points is not 0, the management server 202 determines the valid parking time allowed to the user. Calculate the length of. After that, the management server 202 issues a receipt 260 illustrated in FIG. 25 and sends it to the user.

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

As shown in the lower part of FIG. 24, the fact that the current user is permitted to park is communicated not only to the user himself/herself but also to the aforementioned multiple persons in charge. The person in charge can be contacted by the management server 202 sending an e-mail containing information regarding parking permission to each person individually (active contact), or by sending a message to a person who can view the information on the management server 202. A method in which information regarding parking permits is posted on a homepage with limited access (a homepage exclusively for businesses), and information regarding parking permits is communicated to the person in charge through individual access to the homepage (passive). You may also do so by contacting us.

[Payment of additional fees for extended parking]

If the length of the actual continuous parking time by the user exceeds the above-mentioned valid parking time length (the continuous parking time permitted by the user when entering the parking lot in exchange for the consumption of the usage points), in other words, the user has engaged in extended parking. In this case, when leaving the parking lot 10, the user accesses the management server 202, as illustrated in the sequence diagram of FIG.

Thereafter, the user transmits the unique ticket number assigned to the electronic parking ticket 250 used this time to the management server 202, and the management server 202 confirms the validity of the electronic parking ticket 250. Subsequently, the user transmits the time code 190 and location code 192 displayed on the display 36 to the management server 202. The management server 202 decrypts the received time code 190 to estimate the user's leaving time, and compares it with the current time measured by the management server 202 to confirm the validity of the estimated leaving time. do.

After that, the management server 202 calculates the length of time that has elapsed from the end time of the valid parking time recorded in the electronic parking ticket DB 232 to the estimated exit 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 that corresponds to the amount of the additional parking fee, and calculates the number of remaining points by subtracting the number of points used from the current number of valid points. After that, the management server 202 issues a payment receipt (not shown) and sends it to the user.

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

The electronic parking ticket processing program is configured to include a first subprogram shown in FIG. 16, a second subprogram shown in FIG. 17, and a third subprogram shown in FIG. 18. The first sub-program is for member registration and issuance of electronic parking tickets, the second sub-program is for permission to use electronic parking tickets, and the third sub-program is for extended parking. This is the part for paying the parking fee.

[Member registration]

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

Subsequently, in step S103, a unique user ID is assigned to the current user. Thereafter, in step S<b>104 , the receiving unit 212 receives the password set by the user himself/herself, which is transmitted from the user's communication device. In this step S104, other user information additionally transmitted from the user's communication device (for example, as illustrated in FIG. 19, the vehicle number, vehicle model name, and body color of the vehicle that the user plans to park) etc.) are also received via the receiving unit 212.

Subsequently, in step S105 of FIG. 16, user information about the current user is registered in the member DB 230, and thereby the current user is registered as a member. Thereafter, in step S106, a registration completion message indicating that membership registration has been completed for the current user is sent back to the user via the transmitter 210. This completes the current execution of this electronic parking ticket processing program.

[Issuance of electronic parking ticket]

The scenario in which the management server 202 receives a membership registration request from a user has been described above, but instead, in a scenario in which the management server 202 receives an electronic parking ticket issuance request, the determination in step S101 is NO and the determination in step S107 is The determination is YES, and the process moves to step S108.

In this step S108, the user's user ID and PIN sent from the user's communication device are checked against the member database 230 to determine whether or not the current user is a member, that is, eligible to receive this service. It is determined whether or not it has. That is, personal authentication is performed, and if this personal authentication is successful, in step S109, the data representing the number of points that the user wants to earn this time, transmitted from the user's communication device, is received 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 to obtain the number of points that the user wants to obtain is determined in advance between the number of points and the fee. It is calculated by referring to the rate table or function formula that expresses 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 the electronic payment has been successfully completed. If the electronic payment by the user is not successfully completed, the determination in step S113 is NO, and in step S113a, an issuance disallowance message indicating that issuance of the electronic parking ticket 250 is not permitted is returned to the user. Ru. This completes the current execution of this electronic parking ticket processing program.

On the other hand, this time, assuming that the electronic payment by the user has been successfully completed, the determination in step S113 is YES, and in step S114, a ticket specific to the electronic parking ticket 250 to be issued to the current user is determined. A number will be assigned. 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 awarded 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. sent to. This completes the current execution of this electronic parking ticket processing program.

[Permission to use electronic parking ticket]

The scenario in which the management server 202 receives an electronic parking ticket issue request from the user has been described above, but instead, in a scenario in which the management server 202 receives an electronic parking ticket usage request, the determination in step S101 in FIG. The determination in S107 is also NO, the determination in Step S118 of FIG. 17 is YES, and the process moves to Step S119.

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

After that, in step S121, it is determined whether or not the electronic parking ticket 250 that the current user wishes 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, in step S122, a usage denial message indicating that usage of the electronic parking ticket 250 is not permitted is returned to the user's communication device. This completes the current execution of this electronic parking ticket processing program.

On the other hand, this time, assuming that the electronic parking ticket 250 that the user wishes to use is valid, the time code 190 and location code 192 transmitted from the user's communication device are sent to the receiving unit 212 in step S123. is received via. Subsequently, in step S124, the received time code 190 is decoded 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 the estimated warehousing time is within a predetermined tolerance range determined based on the reception time when the management server 202 receives the time code 190. It is determined whether code 190 is valid.

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

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

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

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

Subsequently, in step S131, processing is performed to notify all the persons in charge of the received desired parking conditions (for example, the desired parking conditions may be communicated individually to the persons in charge by e-mail, or the desired parking conditions are communicated to all persons in charge). (Contact the person in charge by posting the conditions on the company's dedicated website). This completes the current execution of this electronic parking ticket processing program.

[Payment 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, but instead, in a scenario in which the management server 202 receives an extended parking payment 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, and the determination in step S132 in FIG. 18 is YES, and the process moves to step S133.

The steps from step S133 to step S138 have the same execution contents as the steps from step S119 to step S124 shown in FIG. 17, so a redundant explanation will be omitted.

In step S139 of FIG. 18, the user's exit time is estimated based on the result of decoding the time code 190 transmitted from the user's communication device in step S137. Subsequently, in step S140, it is determined whether the estimated leaving time is within a predetermined tolerance range determined based on the reception time when the management server 202 receives the time code 190. It is determined whether code 190 is valid.

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

On the other hand, this time, assuming that the received time code 190 is valid, the determination in step S140 becomes YES, and in step S141, from the estimated exit time, the valid parking ticket recorded in the electronic parking ticket DB 232 is The length of the extended parking time is calculated by subtracting the end time of the time. The estimated exit time is recorded in the electronic parking ticket DB 232, as illustrated in FIG.

Subsequently, in step S142, an additional parking fee corresponding to the calculated extended parking time is calculated by referring to a predetermined conversion table. Thereafter, in step S143, the number of points to be used corresponding to the calculated additional parking fee amount 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. The electronic parking ticket DB 232 also records data indicating that the user has paid an additional parking fee by partially consuming the number of valid points, as illustrated in FIG. 20 . Thereafter, in step S145, a payment receipt (not shown) representing 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, a process is performed to notify all persons in charge that the additional parking fee has been settled by the user, in accordance with step S131 in FIG. 17. This completes the current execution of this electronic parking ticket processing program.

[Automatic sending of exit reminder message]

In this embodiment, as described above, the management server 202 determines the parking time for each user who parks using the electronic parking ticket 250 at the time of parking based on the parking time and the length of the valid parking time. It also knows the calculated expected delivery time. Therefore, as shown in FIG. 27, in this embodiment, the management server 202 notifies the user who parks using the electronic parking ticket 250 that the scheduled departure time will arrive soon, or A separate email message will be sent to the user's communication device to warn them that the time has passed and to remind them to pay for extra parking if the scheduled exit time has passed. Designed.

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

The exit reminder message includes, for example, a statement to the effect that ``If the scheduled exit time has passed, the user must access the management server and pay the additional parking fee when exiting.'' It will be done. Thereby, when the scheduled leaving time has passed, the user is reminded not to forget to access the management server 202 and settle the additional parking fee when leaving the parking lot.

Furthermore, the management server 202 determines for each user whether or not the scheduled exit time has arrived, and if the scheduled exit time has arrived, the user can pay the additional parking fee by referring to the electronic parking ticket DB 232. Determine whether or not. If the payment of the additional parking fee has not been completed, the management server 202 displays a description that "the scheduled departure time has passed" and "When leaving the parking lot, the user accesses the management server and pays the additional parking fee. This includes a statement to the effect that "it is necessary to settle the payment." The management server 202 sends the exit reminder message to the corresponding user's communication device by e-mail. The management server 202 sends the same exit reminder message to the user who sent the exit reminder message every time a set time (for example, one hour) passes until the user accesses the management server 202 and settles the additional parking fee. Send repeatedly.

It should be noted that in this embodiment, both normal parking and cardless parking are possible in the same parking lot 10, so that the ticket issuing machine 20 not only has its original ticket issuing function, but also has the time code 190. It is also designed to have a time code generation/display function that generates a time code by encryption and displays it on the screen of the display 36. However, in the present invention, for example, only cardless parking is possible in the same parking lot 10, and instead of the ticket issuing machine 20, a clock 102 and an encoder ( For example, a time code generation system that includes at least a computer (for example, a computer that executes a program that generates the time code 190 by referring to the time encryption table) and a display 36 that displays the time code 190 generated by the encryption. It is possible to implement the display device in a manner that it is installed in the parking lot 10.

As is clear from the above description, in this embodiment, for convenience of explanation, the clock 102 constitutes an example of the "clock" in the above section (1), and the steps shown in FIG. The part that executes S32 constitutes an example of the "encryption section" in the same section, the display 36 constitutes an example of the "display section" in the same section, and the time code 190 of the ticket issuing machine 20 constitutes an example of the "encryption section" in the same section. The part that generates and displays constitutes an example of the "parking lot time code generation/display device" in the same section, and the display device 36 constitutes an example of the "display section" in the above section (2) and the part that generates and displays the above. It is possible to consider that each of them constitutes an example of a "parking lot time code display device" according to item (5).

Furthermore, in this embodiment, for convenience of explanation, steps S120 and S123 shown in FIG. Steps S124 to S126 constitute an example of the "parking time validity determination step" in the same section, and step S130a shown in the figure constitutes an example of the "parking permission step" in the same section. It is possible to consider that the section 210 and the receiving section 212 together constitute an example of the "communication section" in the same section.

Furthermore, in this embodiment, for convenience of explanation, steps S134 and S137 shown in FIG. can be considered to constitute an example of the "leaving time validity determination step" in the same section, and step S141 shown in the figure can be considered to constitute an example of the "parking time calculation step" in the same section. It is.

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

<Second embodiment>

Next, a parking lot management method according to a second exemplary embodiment of the present invention will be described. However, elements common to the first embodiment will be referred to using the same reference numerals or names to omit redundant explanation, and only different elements will be explained in detail.

In the first embodiment, each time a user who wants to perform cardless parking attempts to use the parking lot 10, he/she specifies the length of the scheduled parking time for which he/she wishes to perform the current parking prior to parking (at the time of entering the parking lot). However, out of the number of valid points, the number of points corresponding to the prepaid parking fee commensurate with the length of the scheduled parking time is consumed. When the user leaves the parking lot 10 before the scheduled parking time has elapsed, that is, when the user does not perform extended parking, it is not necessary to access the management server 202 at the time of leaving the parking lot. That is, the user does not need to access the management server 202 when leaving the parking lot unless extended parking is performed. As a result, unless the user performs extended parking, communication with the management server 202 is only necessary when entering the parking lot each time the user parks the vehicle, thereby saving the user's effort.

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

In contrast, in this embodiment, the user has to access the management server 202 not only when entering the warehouse but also when leaving the warehouse, which adds effort to the user. Instead, the parking time is calculated all at once when leaving the parking lot and the number of points is consumed, so that the number of points consumed is calculated to be exactly commensurate with the actual parking time. As a result, according to this embodiment, the user does not have to waste points, which is economical.

Next, the parking lot management method according to this embodiment will be described with reference to FIGS. 28 to 33. The 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 (membership registration and issuance of electronic parking ticket 250) shown in FIG. 17, the fourth subprogram that replaces the second subprogram (permission to use electronic parking ticket 250) shown in FIG. and a fifth sub-program that replaces the third sub-program (settlement of additional parking fee for extended parking) shown in FIG.

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 by a flowchart in FIG. 28. Further, the fifth subprogram is executed in the management server 202 in order for the user to settle the parking fee by consuming points at the end of parking using the electronic parking ticket 250, and is conceptually represented in a flowchart in FIG. 29. .

Hereinafter, the electronic parking ticket processing program in this embodiment will be described, but redundant explanations of processes common to those of the first embodiment will be omitted, and only different processes will be explained in detail.

[Permission to park using electronic parking ticket]

When entering the parking lot 10, the user accesses the management server 202, as illustrated in the sequence diagram of FIG. 30, in order to request permission from the parking manager for parking using the electronic parking ticket 250. . Thereafter, the user transmits the ticket number assigned to the electronic parking ticket 250 that the user wishes to use 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 location code 192 displayed on the display 36 to the management server 202. The management server 202 decrypts the received time code 190 to estimate the user's warehousing time, and compares it with the current time measured by the management server 202 to confirm the validity of the estimated warehousing time. do.

If the estimated parking time is appropriate, the management server 202 allows the user to park and sends a parking permission message to the user. The management server 202 informs not only the user himself/herself but also the plurality of persons in charge of the fact that parking has been permitted to the user this time, in the same manner as in the first embodiment.

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

In step S126, if it is determined that the parking time estimated by decoding the time code 190 received from the user this time is valid, in step S302, a parking permission message indicating that the user is permitted to park is sent. A reply is sent to the user's communication device. Thereafter, in step S303, information indicating that the user is permitted to park in the parking lot 10 is communicated to all the persons in charge. This completes the current execution of the fourth subprogram.

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

When leaving the parking lot 10, the user accesses the management server 202 to settle the parking fee, as illustrated in the sequence diagram of FIG. 31. 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 location code 192 displayed on the display 36 to the management server 202. The management server 202 decrypts the received time code 190 to estimate the user's leaving time, and compares it with the current time measured by the management server 202 to confirm the validity of the estimated leaving time. do.

Thereafter, in step S402 shown in FIG. 29, 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 exit time. The estimated leaving time is recorded in the electronic parking ticket DM 232, as illustrated in FIG. 20.

Subsequently, in step S403, a parking fee corresponding to the calculated length of parking time is calculated by referring to a predetermined conversion table. Thereafter, in step S404, the number of points to be used corresponding to the calculated parking fee amount 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. The electronic parking ticket DB 232 also records data indicating that the user has settled the parking fee by partially consuming the number of valid points, as illustrated in FIG. 20 . 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, processing is performed to notify all persons in charge that the parking fee has been settled by the user. This completes the current execution of the fifth subprogram.

[Automatic sending of exit reminder message]

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

Therefore, in this embodiment, as shown in the sequence diagram in FIG. 33, the management server 202 sequentially calculates the length of parking time for each user whose parking fee has not yet been settled, and The number of points used is also calculated for the length of parking time. The management server 202 further determines whether or not the number of remaining points is insufficient in relation to the length of the parking time even if the number of used points is to be consumed at that time. If the number of remaining points is insufficient, the management server 202 creates a message urging the user to leave the warehouse immediately, and sends the message to the corresponding user via email. Send to device.

As is clear from the above description, in this embodiment, for convenience of explanation, steps S120 and S123 shown in FIG. , Steps S124 to S126 shown in the same figure constitute an example of the "warehousing time validity determination step" in the same section, and step S302 shown in the same figure constitutes an example of the "parking permission step" in the same section. It is possible to think that it consists of

Furthermore, in this embodiment, for convenience of explanation, steps S134 and S137 shown in FIG. can be considered to constitute an example of the "leaving time validity determination step" in the same section, and step S402 shown in the figure can be considered to constitute an example of the "parking time calculation step" in the same section. It is.

Additionally, in some of the embodiments described above, the ticket issuing machine 20 is an independent type that does not have the function of communicating with the parking lot manager (management server 202), and the ticket issuing machine Although it is advantageous to minimize equipment costs for ticket machine 20, the invention can be implemented in such a manner that ticket issuing machine 20 has its communication capabilities.

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

Several embodiments of the present invention have been described above in detail based on the drawings, but these are merely illustrative, and based on the knowledge of those skilled in the art, including the aspects described in the above [Summary of the Invention] column. It is possible to implement the present invention in other forms with various modifications and improvements.

Claims (9)

A parking lot management system,
a display unit installed in a parking lot and displaying a code including a location code unique to the parking lot without using a physical parking ticket;
When leaving the parking lot, if the code is received from the communication device of the user who is currently in the parking lot, based on the received code, the user will be able to leave the parking lot in the parking lot where the user is currently in the parking lot. a parking lot identification section that identifies what the person is trying to do;
When leaving the parking lot, if user information that can identify the user's vehicle parked in any parking space in the parking lot is received from the communication device, the received user information and the stored information in advance A parking lot management system comprising: a payment unit that makes it possible to settle the parking fee to be charged to the user for the specified parking lot by electronic payment when the verification with the user information that is specified is completed . The code is represented as an image,
The communication device has an image reader,
The parking lot management system according to claim 1, wherein the parking lot specifying unit receives the image read by the image reader from the communication device as the code. The parking lot management system according to claim 1, wherein the display unit displays the code on a screen. A program for causing a computer to function as the parking lot specifying section according to claim 1. A program for causing a computer to function as the payment unit according to claim 1. 2. The parking lot management system according to claim 1, wherein the parking lot management system includes the display unit installed in the parking lot and a management server installed in a remote location. A program executed by a computer of a communication device,
The management server includes the parking lot specifying unit and the payment unit,
The communication device has multiple functions:
a function of transmitting the code to the management server when leaving the parking lot;
A function of transmitting user information that can identify the user's vehicle parked in any parking space in the parking lot to the management server when leaving the parking lot;
a function of receiving payment completion data from the management server indicating that the parking fee payment has been completed when the parking fee charged to the user for the parking lot is settled by electronic payment;
including;
A program executed by the computer to implement the plurality of functions . A recording medium on which the program according to claim 4 is recorded in a computer-readable manner. A recording medium on which the program according to claim 5 is recorded in a computer-readable manner. A recording medium on which the program according to claim 6 is recorded in a computer-readable manner.

Images