JP3087810U - Parking lot management system - Google Patents

Abstract

(57) [Summary] [Problem] To provide a parking lot billing system that enables short-term parking lot lending to an unspecified number of people without special capital investment such as a parking lot entrance gate and a start prevention device, The purpose is to promote the advanced use of long-term rental parking lots, such as monthly rentals, which were previously low in usage, and parking lots of commercial facilities. An application terminal capable of inputting a vehicle number and an application signal indicating an intention to apply for a parking lot, storage means for storing an application state of a parking lot in association with a vehicle number, and an application state of a parking lot, Availability determination means for determining availability of the parking lot, parking availability transmission means for transmitting the availability of the parking lot to the application terminal, and a vehicle number of a vehicle applied to the parking lot at the current time. An application status display terminal for displaying a list.

Description

[Detailed description of the invention]

[0001]

[Technical field to which the invention belongs]

 The present invention relates to a technology for reducing the cost of installing a parking lot entrance / exit gate and a start prevention device in a small parking lot, particularly in a parking lot operation and billing system.

[0002]

[Prior art]

 Conventionally, in a large-scale parking lot, a gate provided with a barrier or the like is provided at an entrance of the parking lot, and a billing system using a ticket issued at the gate is widely used. In other words, there is an empty space in the parking lot and entry is allowed on condition that the ticket issued at the entrance gate is received, and when leaving the exit, the parking time is calculated from the ticket at the exit gate, and it is determined by the parking time Exit is permitted on the condition that a fee corresponding to the amount has been paid.

[0003] Even in a small-sized parking lot where it is difficult to install a gate at an entrance, there is known a technique in which a start preventing device is provided in each parking basin. Japanese Unexamined Patent Publication No. 06-349000 has a vehicle presence / absence detection sensor for detecting whether or not there is a parked vehicle in each of the parking cavities. A technology is disclosed in which a start prevention device is operated for each parking basin after elapse.

Japanese Patent Application Laid-Open No. 09-16898 discloses that a management computer is used to manage the use status and reservation status, accept a reservation from a user, and transmit the reservation information to an entrance / exit gate of a parking lot. A method is disclosed for receiving a user who makes a reservation separately from a general user who uses the parking lot without making a reservation. In other words, using the ledger in the management computer, the reservation and current usage status of each parking lot are managed, and when a parking lot application is received from a parking lot user, the reservation status of the application period is stored in the management computer. Check in the ledger and let us know if you can use it. The user is instructed on the location of the parking basin to be used at the entrance gate of the parking lot, which is the window of the parking lot on the day of use.

Japanese Patent Application Laid-Open Nos. Hei 11-130445 and 09-16898 describe a parking system provided with a settlement means for invoicing a reserved parking fee to a financial institution designated by a user for settlement. A parking lot reservation device is disclosed.

[0006]

[Problems to be solved by the invention]

 However, the installation cost of a gate or a device such as a start prevention device disclosed in Japanese Patent Application Laid-Open No. 06-349000 is generally high at several million to tens of million yen. In particular, in small-scale parking lots in which a start prevention device is installed for each individual parking space, the installation cost per parking space becomes large. Therefore, in rural areas far from urban areas, it is often used as a monthly parking lot that does not require special equipment. In addition, parking lots of facilities such as banks and hospitals are often closed without being used on business holidays.

[0007] Also, according to Japanese Patent Application Laid-Open No. 09-16898, the use status and the reservation status are managed using a management computer, but guidance to a destination parking space, exclusion of unparkable vehicles when full, The gates at the entrance and exit of the parking lot are used to charge for leaving vehicles and to refuse to leave vehicles that do not pay, and therefore no reduction in installation and operation costs can be expected.

Further, in JP-A-11-130445 and JP-A-09-16898, the settlement unit is used as a substitute for a charging unit for a vehicle leaving the gate device. The gate at the entrance of the parking lot is used to guide to the destination parking basin, to eliminate vehicles that cannot be parked when full, and to refuse exiting vehicles that do not pay. Entrance gates are indispensable equipment for the operation of parking lots, and the use of these technologies does not change the equipment costs and operating costs required for parking lot operation.

In a local or suburban city, a parking lot around a station is of great environmental and social significance as a park and ride that encourages the use of railways. In other words, one-day rental parking lots around the station can improve the convenience of travelers traveling by rail and promote the use of railroads, thereby reducing the environmental load and traffic congestion caused by passenger cars. high. However, short-term parking lots such as one-day rentals require large capital investment such as entrance gates and start-up prevention equipment, or require managers. In rural areas or suburban cities, parking fees are low, so it is difficult to recover the costs required for capital investment, and they are often used as long-term lending parking lots, such as on a monthly basis that does not require capital investment. This tendency is more pronounced in smaller or slightly more inconvenient parking lots.

[0010] In addition, the monthly parking lot does not generate revenue if there is no contractor. However, the monthly parking lot has no means for actively seeking new users besides installing a signboard. There are many parking casks that are left unattended for a long time. Furthermore, even if the parking lot of commercial facilities such as financial institutions is rented out as a short-term parking lot only on the holidays, it will not be possible to recover the investment of the facilities, so it will be closed on the holidays. Alternatively, even in urban areas, land whose use period is limited, such as for resale, is difficult to recover, so it is often used as a monthly parking lot that does not require equipment.

Accordingly, the present invention proposes a parking lot management system that enables a short-term lending of a parking lot to an unspecified number of people without special capital investment such as a parking lot entrance gate and a departure prevention device. The aim is to promote the advanced use of monthly parking lots and parking lots for commercial facilities, which were previously underutilized, and to promote the supply of scarce parking lots in urban areas and around railway stations.

[0012]

[Means and effects for solving the problem]

 In order to achieve the above object, a parking lot management system (1) according to the present invention provides a parking lot management system that manages a parking lot having a plurality of parking pits, wherein an application signal indicating a vehicle number and an intention to apply for a parking lot. An application terminal capable of inputting a parking lot, storage means for storing the application status of the parking lot in association with the vehicle number, availability judging means for judging the availability of the parking lot based on the application status of the parking lot, and the application A parking lot availability transmission means for transmitting the availability of the parking lot to the terminal, and an application status display terminal for displaying a list of vehicle numbers of the vehicles applied to the parking lot at the current time. I have.

According to the parking lot management system (1), even in a small-scale parking lot, equipment for physically restricting the movement of vehicles, such as a start-stop device and an entrance gate, is not provided, and capital investment is reduced. It allows the establishment of almost no short-term rental parking lots. In other words, the parking lot can be applied for by the application terminal, the vehicle number that identifies the applied vehicle is stored by the storage means, and the vehicle number of the vehicle that has been applied to the parking lot at the current time is stored. By displaying the list, it is possible for the patrol manager to easily discriminate between authorized and illegally parked vehicles.

The application terminal and the application status display terminal can be realized using, for example, a mobile phone or an Internet-compatible mobile phone such as i-mode. With the application terminal, users can apply for a parking lot at the planning stage of the trip, and do not have to worry about finding a parking lot when traveling.

[0015] The vehicle number is a symbol such as a vehicle registration number or a number issued on a sticker issued to a member or the like and attached to the vehicle, for a third party to identify each vehicle.

The parking lot management system (2) according to the present invention is based on the parking lot management system (1), and has storage means for storing the number of parking lots and the application period of the number of parking lots, and the application status of the parking lot. Availability determining means for determining the availability of the parking lot based on the number of parking lots and the application period of the number of parking lots, a list of vehicle numbers of a plurality of vehicles applied to the parking lot at the current time, and And an application status display terminal for displaying the number of parked vehicles in the country.

According to the parking lot management system (2), the parking lot management system (2) is provided with availability judging means for judging the availability of the parking lot from the application state of the parking lot, the number of parked vehicles, and the application period of the number of parked vehicles. For example, it is possible to change the daily number of parked vehicles. In addition, the application status display terminal displays a list of vehicle numbers of multiple vehicles that have been applied to the parking lot at the current time and the number of vehicles in service at the current time. The correct measure can be recognized without error.

For example, in a commercial facility or the like, the number of customers differs depending on the time zone and the day of the week. Since parking lots are set during busy seasons, they are often vacant at other times. With conventional parking gates, it is difficult to share such parking lots with commercial facility users and parking lot users. In other words, as a commercial facility, during the busy season, we would like to give priority to the parking facilities to the users of the commercial facilities themselves. It cannot be determined whether the user is a parking lot user. After entering, it is possible to distribute parking lot tickets to users of commercial facilities, but it is not possible to exclude users who only use parking lots.

According to the above-mentioned parking lot management system (2), the parking means to be used by the parking lot user during the busy season and at other times by the storage means for storing the number of parked cars and the application period of the number of parked cars. The upper limit of the number of casks can be set as the number of cars in service, and the remaining parking casks can be reserved for users of the original commercial facilities. Since the number of parked vehicles is displayed on the application status display terminal together with a list of the application vehicle numbers, the patrol manager can correctly recognize the parking lot to be managed. As a result, it is possible to operate the parking lot without installing facilities such as parking gates.

[0020]

【Example】

 Hereinafter, an embodiment of a parking lot management system according to the present invention will be described in detail with reference to the drawings.

As shown in FIG. 1, the parking lot management system according to the present embodiment includes a management computer (30), an application terminal (32), and an application status display terminal (33). . In each parking lot to be managed, a plate indicating the parking lot ID is attached to the parking lot where each vehicle is parked, and the parking lot entrance is managed by the same system as the parking lot name. A map showing the location of the parking lot is posted.

The management computer (30) is connected to a plurality of application terminals (32) and a plurality of application status display terminals (33) via a communication line such as the Internet (31) so as to enable bidirectional data communication. ing. Furthermore, the management computer (30) is also connected to the computer of the payment receiving organization (not shown) via the Internet.

Next, the hardware configuration of the management computer (30) will be described with reference to FIG. The management computer (30) is connected to the CPU (11), ROM (16), RAM (17), keyboard (15), CRT (12), LAN port (13), and hard disk (14) via the bus (19). And are configured to allow mutual data transmission. This configuration is the same as the configuration of a general computer. The LAN port (13) is connected to the Internet (31) via a router (20) connected to the LAN (21). Using the Internet (31), the management computer (30) performs data communication with the application terminal (32) and the application status display terminal (33). The hard disk (14) stores a program for the management computer to perform the operations shown in the flowcharts of FIGS. 6 to 13 and a data table showing the contents in FIGS. 14 to 23. Then, the CPU (11) reads out the program therefrom and executes it. The application terminal (32) stores the program shown in the flowcharts of FIGS. 2, 3, and 4, and the application status display terminal (33) stores the program shown in the flowchart of FIG. I have. In the following embodiments, the conditional branch display in the flowchart is indicated by a “?” Mark attached to the text in the frame in the figure.

1. The data table management computer (30) manages a data table indicating the application status of a plurality of parking lots, and a data table storing contact codes and vehicle numbers of each user. These data are managed by a DBM (Data Base Management system), and data records can be inserted and deleted, and necessary data records can be deleted by requests from the application terminal (32) and the application status display terminal (33). A search is performed.

The data tables will be described in more detail. The parking lot data table (FIG. 14), the parking lot data table (FIG. 15), the parking lot application data table (FIG. 16), the regional data table (FIG. 17), the user data There is a table (FIG. 18). Each data table stores multiple data records containing the items shown in the table. For example, in the case of the parking cascade data table (FIG. 15), the data record stores data relating to one parking basin, and in the case of the user data table (FIG. 18), the data record stores data relating to one user.

FIG. 14 shows a parking lot data table. The parking lot name (101) contains the name of the parking lot. The parking lot ID (102) contains a unique number for each parking lot. This code is also displayed on the signboard of each parking lot, and is also used to confirm the application status of each parking lot. The area ID (103) contains a numerical code of the area such as the municipalities where the parking lot is located. The numerical code is a numerical value stored in the area data table (FIG. 17), and the table shows the correspondence between the area name and the area ID. The parking lot position coordinates (104) contain the parking lot position coordinates measured by GPS. The position coordinates are transmitted to the application terminal (32), and when the application terminal (32) has GPS, the position of the application terminal (32) and the position of the parking lot are displayed on the same map. The parking lot map (105) is image data containing a map including a parking lot. Parking manager name (106), parking manager phone number (107), parking account number (108), parking manager password (109), parking manager email address (110) Here is the contact information for the parking lot manager. The parking lot manager can access the management computer (30) using the parking lot manager telephone number and the password to know the parking lot application status and the deposit status. Monthly parking fees are aggregated and paid for the parking account number (108).

Parking time unit price (day) (111), parking time unit price (night) (112), parking one day unit price (weekdays) (113), parking one day unit price (holiday) (114), parking The parking unit price per day (applied on the day after 12:00) (115) contains the unit price of the parking lot according to the period of use and the date of use. Of these, the parking unit price per day (application on the day after 12:00) is the parking fee applied after 12:00 noon on the day, and is the price when renting from the application time until the end of use of the day. is there. These pricing settings may be further refined. For example, the charge setting may be changed for each day of the week and for each time zone.

The number of parking pits (121) is the number of parking pits provided in the parking lot. The parking number array (119) stores data on the number of vehicles that can be parked every day. More specifically, this data is an array having elements of 365 × 2 for two years, and the number of parked vehicles per day is indicated by a numerical value. This figure is a value set in advance by the parking lot manager by estimating the usage situation. In the case of a commercial facility, the number is set according to the day of the week and the season. In the case of a parking lot dedicated, the same number as the number of parking basins (121) is set.

The parking lot empty space number array (120) indicates the number of available empty parking space spaces which have not received an application. When the number-of-parking-uses array (119) is set, the same numerical value is stored as an initial value, and the value is increased or decreased at the time of application and at the time of application cancellation. If the number becomes 0, parking is not possible on that day. Since parking lots can be reserved for 10 days from now, for the 10 days from now, when the number of parking lots arranged (119) is changed and increased / decreased from the current value, parking lot vacancy It is also added to and subtracted from the numeric array (120). At this time, a modification in which the number of parking vacancies array (120) becomes smaller than 0 or exceeds the number of parking basins (121) cannot be added to the parking number array (119).

These arrays are managed based on a reference date determined by the system as the number of days from the reference date. If the reference date is February 1, February 1 is indicated by the first element of the array, and February 3 is indicated by the third element of the array. The reference date is updated once a month, and each array is shifted by one month. As a result, the future parking lot schedule for 13 months is always stored in the array.

The parking cascade data table (FIG. 15) stores data of each parking basin. The parking basin ID (201) is a unique number for each parking basin. The parking lot ID (202) indicates the ID of the parking lot to which the parking lot belongs, and contains the same number as the number used for the parking lot ID in the parking lot data table (FIG. 14). The parking basin application array (203) is an array having 365 x 2 elements for two years, and is managed based on the reference date determined by the system as the number of days from the reference date, and contains the application data ID of the daily application. Have been. The parking basin application sequence (203) indicates the daily application state of the parking basin. The application data ID contains the same number as the application data ID (301) in the parking basin application data table (FIG. 16), and indicates a data record of the parking basin application data table (FIG. 16). When a new application is made, a new data record is inserted into the application data table (FIG. 16), and the same number as the application data ID (301) of the data record is stored in the parking lot application array (203). It is stored in the position corresponding to the application date. For example, in the case of an application for three days, the same application data ID (301) numerical value is stored in the array corresponding to the use date, and indicates the same data record in the parking lot application data table (FIG. 16). When there is no application, the value of the parking day application array (203) for the corresponding day is “NULL”.

If the value of the parking lot application array (203) is 'NULL' and the value of the parking lot number array (119) of the parking lot data table (FIG. 14) is larger than 0, the parking lot on that day is one day. It can be used as a parking lot or hourly parking lot. Even when the parking lot is applied for a one-day parking lot or a time-rental parking lot, the parking lot application array (203) contains application data of a newly generated data record in the parking lot application data table (FIG. 16). The same number as the ID (301) is stored. When a plurality of days are applied in succession, the same application data ID is stored.

The parking basin application data table (FIG. 16) stores data for each application. The application data ID (301) is a unique number in the system assigned by the management computer (30) when the user makes an application, and is used to determine each application. The parking basin ID (302) is the ID of the parking basin to be rented out in this application. The parking basin ID (201) in the parking basin data table (FIG. 15) is used to distinguish the individual parking basins. I do. The user ID (303) is the ID of the user who has subscribed, and uses the same numerical value as the user ID (501) in the user data table (FIG. 18) to distinguish individual users.

The application type (304) indicates the type of application by three flags of “1 day”, “time”, and “overuse”. The applied use date is indicated in the parking lot application array (203) of the parking lot data table (Fig. 15). If the type of application is 'time' or 'excess use', The use time is described in the use start time (305) and the use end time (306). In the case of the “1 day” application type, the area of the use start time (305) and the use end time (306) are not used. Note that an application for 'time' use over a two-day period is stored using two application data at the time of application.

In the application point price (307), a price for each parking lot is calculated and stored at the time of application, based on the application period and the application type. The payment ID (308) is a code for confirming with a payment receiving organization such as a convenience store. The user presents the payment ID (308) to the branch of the payment receiving institution and pays the specified amount. Payment details, such as the period of use and parking lots, are transmitted to the payment accepting organization along with the payment ID (308), and when the user pays, the payment details are presented to the user and mutual confirmation is made. Take. The payment is notified by the payment receiving organization to the system using the payment ID.

The paid flag (309) is a flag indicating whether or not payment has been made, and is set to "paid" from "payment not received" upon receipt of a notification from the payment receiving organization. The payment term (310) contains date data indicating the term required for payment. The parking lot manager fee (311) indicates the price that the parking lot manager receives for this parking lot use. Used when collecting and paying consideration.

The area data table (FIG. 17) is data of an area where a parking lot exists. The region ID (401) is a unique ID for each region in the system. The area name (402) shows the name of the area. The local parking map (403) shows the positions of the parking lots existing in the area.

The user data table (FIG. 18) manages user data. The user ID (501) is a unique ID for each user in the system. The user contact telephone number (502), user contact e-mail address (503), user vehicle number (504), user vehicle size (505), and user vehicle model (506) are entered at the time of application. Is stored according to the data. The user password (507) is a password set by the user, and is used to omit the user's data entry or to correct the contents of the application at the second and subsequent applications.

The used parking lot ID 1 (508), the used parking lot ID 2 (510), and the used parking lot ID 3 (512) indicate the IDs of parking lots that have already been used. It will be displayed the next time you apply, and will help you choose a parking lot. If the parking lot has never been used, 'NULL' is assigned to the variable. Parking evaluation 1 (509), parking evaluation 2 (511), and parking evaluation 3 (513) are evaluations of the parking lot set by the user.The display order at the time of application is changed according to the evaluation content. Again, it helps the user to choose a parking lot.

The use point (514) is a point added according to the number of times the user has used the system or the amount of money. Although not described in detail here, services such as discounts of charges can be received according to the point. .

A data record is added to these data tables for each individual data. For example, a data record containing the respective items for each new user is added to the user data table (FIG. 18).

Further, by using items common to a plurality of data tables, the relation between the data tables can be known. For example, when a user wants to know the telephone number of a user who is using a parking lot from a certain parking lot ID, a parking lot ID (302) that matches the parking lot ID is obtained from the parking lot application data table (FIG. 16). Search for data records that have. The user ID (303) of the retrieved data record is the user ID of the user who uses the parking lot. This value is assigned to the variable Xuser. Next, a data record having a user ID (501) that matches Xuser is searched from the user data table (FIG. 18). The user contact telephone number (502) of the data record is the telephone number of the user using the parking lot.

Xuser is a unique ID for each user in the user data table (FIG. 18), and is key data in the table. The data record of the user data table (FIG. 18) having the user ID (501) that matches the Xuser is described as the data record indicated by the Xuser. The same description is made for other unique data in the table, such as a parking lot ID and a parking lot ID.

2. Parking application The parking lot managed by the system is provided with a plurality of parking pits. The system indicates to the user whether or not the parking lot can be used, and receives an application from the user, and receives the individual parking pits. Of the parking basin ID is transmitted. Without unnecessarily disclosing an empty parking basin, it is possible to notify the vacant parking basin only to the user who has applied. Hereinafter, the flow of the program of the system, such as when applying from the application terminal (32), will be described. The subscription terminal (32) is connected to the management computer (30) via the Internet (31), either wirelessly or by wire.

2.1. Confirmation of User / Registration of User The flowcharts of the processing of the application terminal (32) are shown in FIGS. The user selects and displays a “use application screen” on the application terminal (32) (S201). On the “Usage application screen”, a contact telephone number and a user password can be entered, and there are “Next” button, “First use” button, and “Cancel” button. The “Cancel” button is used to cancel the procedure from the terminal by pressing the button, and is displayed on all screens below. The “Cancel” button is omitted from the following description to avoid complication.

When the user presses the "use for the first time" button (S202), the application terminal (32) displays a "user parameter input screen" (S203). On the "user parameter input screen", the contact telephone number, contact e-mail address, user vehicle number, user vehicle size, user vehicle model, user password can be entered, and each data can be entered. Thereafter, when the “next” button is pressed (S204), the application terminal (32) transmits the input parameters and the “user registration request” signal to the management computer (30) (S205). In the case of the second or subsequent use, the user inputs the contact telephone number and the user password on the “use application screen” (S206), and presses the “next” button. When the “Next” button is pressed (S207), the application terminal (32) transmits the input parameters and the “user confirmation request” signal to the management computer (30) (S208).

Upon receiving a signal from the application terminal (32), the management computer (30) establishes a session with the application terminal (32). This session is maintained until it is disconnected by the application terminal (32) or the management computer, and for each application terminal with which it has communicated, the transmitted data and intermediate parameters obtained by the management computer (30) Save. For example, if the management computer (30) stores the user ID of the user of the application terminal (32) in the variable Xuser as a result of the communication from the application terminal (32), the variable Xuser becomes It is stored as a variable Xuser relating to the session of the application terminal (32), and is not used for communication from another application terminal (32). The session is disconnected when the processing of the management computer (30) ends or when there is no communication from the terminal for a certain period of time, and the stored intermediate parameters and the like are discarded.

Upon receiving the "user confirmation request" signal (S804), the management computer (30) receives the user contact telephone number (502) and the user password (507) in the user data table (FIG. 18). ), The consistency between the telephone number and the user password is confirmed (S805). That is, the user data table (FIG. 18) is searched to find a data record having the same user contact telephone number (502) as the input telephone number. Next, it is determined whether the input user password is the same as the user password (507) of the retrieved data record.

If they are the same, the user ID (501) of the data record is substituted for the variable Xuser (S810), and the user data is converted into a message and transmitted to the application terminal (32) (S901). The same user ID as that of Xuser is searched from the parking lot application data table (Fig. 16), and if the searched application data has passed the payment deadline (S902), the message "The payment for the previous use has been completed. No "and the payment ID of the application data are converted to a message and transmitted to the application terminal (32) (S903). If the payment is overdue and the delay of the payment is beyond a certain range (S904), a message saying "Please use this card after the previous payment" is sent, and the "Unavailable" Is transmitted to the application terminal (32) (S905). If there is no application data in which the payment deadline exceeds a certain range, a “user confirmation” signal is transmitted to the terminal (32) (S906).

If they are not the same, a message "Do you want to send the user password by e-mail" and a "password transmission question" signal are transmitted to the application terminal (32) (S806). Thereafter, when a "password transmission request" signal is received from the application terminal (S807), the password is sent to the user contact mail address (503) stored in the data record of the user data table (FIG. 18) indicated by Xuser. Is transmitted by e-mail (S808), and the process ends. Here, the mail refers to an electronic mail via the Internet. Hereinafter, the electronic mail is referred to as a mail. In this case, the telephone number was entered from the application terminal even if it was used twice or more times. A code corresponding to a number or the like may be input as a contact code.

When the management computer (30) receives the "user registration request" signal (S802), the data record of the same user contact mail address (503) as the received contact mail address is stored in the user data. It is searched whether it is already registered in the table (FIG. 18) (S1001), and if it is registered, the user ID (501) of the data record is substituted for the variable Xuser (S1002). A data record having the same user ID as the Xuser is searched from the parking lot application data table (FIG. 16), and the payment deadline (310) of the matched data record is confirmed (S1003). If the record has expired, the message “Payment was not completed at the time of previous use” and the payment ID of the application data are sent as a message to the application terminal (32) (S1004). ) Further, a message “Please use after the previous payment” and a “unavailable” signal are transmitted to the application terminal (32) (S1005), and the process ends.

If the "unavailable" signal is not transmitted, the management computer (30) generates a new user ID and adds a new data record to the user data table (FIG. 18). (S1006). The destination telephone number (502), the user contact mail address (503), the user vehicle number (504), and the usage data record include the generated user ID and the received parameters as the user contact user. The vehicle size (505), the user vehicle type (506), and the user password (507) are recorded, and a "user registration confirmation" signal is transmitted to the application terminal (32) (S1008). 'NULL' is substituted for used parking lot ID1 (508), used parking lot ID2 (510), used parking lot ID3 (512), usage point (514), refund amount (515), additional usage 0 is substituted for the amount (516). The generated user ID is assigned to a variable Xuser (S1007).

2.2. Display of Parking Parking Availability Decision The application terminal (32) displays a received message after transmitting a "user registration request" or "user confirmation request" signal (S209). Next, when “unavailable” is received (S210), the “usage application screen” ends (S211). If a "Password transmission question" is accepted, it indicates that the password should be sent to the e-mail address according to the message received. When the YES button is pressed (S213), the telephone number input to the management computer (30) and the "password transmission request" signal are transmitted (S214), and the process ends.

Upon receiving the "user registration confirmation" or "user confirmation" signal (S216), the application terminal (32) displays a "use date input screen" (S301). On the “Usage Date Entry Screen”, you can enter either “hour” or “1 day” application type and application due date, and the “Next” button is displayed. In the case of 'time' application, the start of use is the current time, and the user enters only the end time of use. In the case of '1 day', enter the use start date and use period. In the case of the 'one day' application type, the start date of use is limited to three days from now, and the application period is limited to seven days or less. When the user presses the “Next” button (S303), the application terminal (32) issues a “use date and time determination” signal, the input application type, and the end time of use if the application type is “time”, In the case of “1 day”, the use start date and the use period are transmitted to the management computer (30) (S304).

When the management computer (30) receives the "use date / time decision" signal (S1103), the received use start date is set to the variable Xday_begin, the use period is set to the variable Xdays, the application type is set to Xtype, and the use ends. Substitute the time into Xtime_end. Also, the time at which the "use date and time determined" signal is received is substituted for a variable Xtime_now. When the application type is “time”, Xday_begin is the day of communication and Xdays is one day (S1104).

Further, in order to prohibit duplicate reservations, all data records whose user ID (303) matches Xuser are searched from the parking basin application data table (FIG. 16), and furthermore, parking of the data records is performed. From the element of the parking basin application array (203) of the parking basin data table (FIG. 15) indicated by the basin ID (302), the utilization date for which the subscription has been made is detected (S1105). From Xday_begin, if there is a parking lot that the user has already applied for during Xdays, a new parking lot cannot be applied for. In this case, send a message to the application terminal (32) saying "There is a parking basin that has already been applied, cancel the previous application and apply." And apply for the "unavailable" signal. The message is transmitted to the terminal (32) (S1106), and the process ends (S1107).

If there is no duplicate reservation, the management computer (30) searches the user data table (FIG. 18) for a data record in which the user ID (501) matches the variable Xuser. If the data of the used parking lot ID1 (508), used parking lot ID2 (510), and used parking lot ID3 (512) of the retrieved data record is not 'NULL', it is determined whether each parking lot can be used. . For the determination of the availability of the parking lot, see 2.4. This is described in detail in section.

When there is a parking lot available among the used parking lot ID1 (508), the used parking lot ID2 (510), and the used parking lot ID3 (512), the evaluation of the available parking lots 1 (509), parking lot evaluation 2 (511), parking lot evaluation 3 (513), and parking lot name (101), parking lot ID (102), parking lot position coordinates (104), parking lot of each parking lot The parking lot map (105), the usage fee corresponding to the application type and the usage period are searched from the parking lot data table (FIG. 14) and transmitted to the application terminal (32) (S1108).

Further, the refund amount (515) is obtained from the data record of the user data table (FIG. 18) indicated by Xuser, and the amount is also transmitted to the application terminal (32) (S1109). If the application is canceled after payment of the fee, the management computer (30) stores a part of the paid fee, and the amount obtained by subtracting the refund amount from the usage fee is This is the amount you need to pay. Next, the management computer (30) uses the area data table (FIG. 17) to send the area IDs (401) and area names (402) of all the stored areas and the “area list transmission” signal to the application terminal ( (S1110).

The application terminal (32) displays the received message (S305), and when it receives “unavailable” (S306), ends the “usage application screen”. When a “region list transmission” signal is received (S308), a region selection screen is displayed (S309). On the area selection screen, the received area name is displayed, along with a selection menu for selecting the area name, the availability of the parking lot used in the past, parking evaluation of the parking lot, usage fee, user refund Amount, "Apply for parking" button, and "Select new parking" button are displayed.

When the user selects a parking lot that has been used in the past (S310) and presses the “Apply for parking lot” button (S311), the parking lot of the selected parking lot is displayed in the management computer (30). The ID, the usage fee, and the "application" signal are transmitted (S312). When the area name is selected (S310) and the “Select new parking lot” button is pressed (S313), the application terminal (32) transmits the area ID and the “area selection” signal corresponding to the selected area name. The data is transmitted to the management computer (30) (S314).

When the management computer (30) receives the "area selection" signal (S1201), the area ID (103) matches the area ID sent from the application terminal (32) from the parking lot data table (FIG. 14). A data record indicating the parking lot to be used is searched, and the availability of the parking lot is determined from the parking lot ID of the data record (S1202).

Next, a parking lot availability transmission process is performed (S1203). In other words, according to the parking lot name (101), parking lot ID (102), parking lot location coordinates (104), parking lot map (105), application type and usage period of each available parking lot The usage fee retrieved from the parking lot data table (FIG. 14) is transmitted to the application terminal (32), and at the same time, a local parking map (403) corresponding to the received local ID is transmitted. In addition, a “parking lot use availability transmission” signal is transmitted. When there is no available parking lot, the parking lot name (101) and the parking lot ID (102) are not transmitted, and only the “parking lot availability transmission” signal is transmitted.

2.3. Application Process and Parking Masu ID Transmission Process When receiving the “parking lot availability transmission” (S401), the application terminal (32) displays a “parking lot application screen” (S402). On the “parking lot application screen”, the received parking lot name is displayed, and a selection menu for selecting the parking lot name is displayed, along with the availability of the parking lot and the usage fee. When the application terminal (32) has map data, each parking position is displayed according to the received parking position coordinates. Alternatively, if the application terminal (32) has a graphic display function, the received local parking map is displayed. A map of each parking lot may be displayed. When the user selects a parking lot and presses the "Apply for parking lot" button (S404), the management computer (30) selects the parking lot ID of the selected parking lot, the usage fee, and the "Apply" signal. Is transmitted (S405).

Upon receiving the "application signal" (S1204), the management computer (30) substitutes the received parking lot ID into Xpark and the usage fee into Xprice. From the parking lot data table (Fig. 14), a data record whose parking lot ID (102) matches Xpark is searched, and the parking lot number (119) that is the smallest in the parking lot number array (119) for all the use days applied for The number of in-service units is obtained, and this is set as X_min_bn_day. In addition, the numerical value of the parking lot empty cell number array (120) on all the use days applied is subtracted (S1205). Next, from the parking basin data table (FIG. 15), a data record in which the parking lot ID (202) matches Xpark is searched in ascending order of the parking basin ID. Among the parking cascades whose order is smaller than X_min_bn_day, in all the use days, the value of the parking cascade application array (203) is 'NULL'. An optimum parking space is searched for according to the reservation status before and after the use date and the application use period, and the parking space ID (201) is substituted into a variable Xslot (S1206).

If the application spans a plurality of days, it is highly likely that the scheduled use date will be extended because the use involves accommodation. In this case, (a1) a parking lot that is vacant both before and after the application, (b1) a parking lot that is available one day before the application and one day after the application, and (c1) a day that the day before the application is one day and the application The parking masu to be used in the order of the parking masu that will be used one day at a later date, (d1) other parking masu will be determined.

If the application is for only one day, the user does not plan to stay, and it is unlikely that the use date will be extended. Even if the use period of the user on the previous day is extended, In addition, it is easier to secure alternative parking lots and parking lots than when applying for multiple days. A parking basin that will be used to secure a parking lot with good conditions in preparation for the application for multiple days expected in the future will be determined. If there is more than a certain number of vacancies on the day before the application or a certain number of parking quotas per day, it can be determined that there is still enough room in the parking lot. At this time, (a2) the parking lot that is used all day before the application, (b2) the parking lot that is vacant the day before the application, (c2) the parking lot that is used every day before the application, (d2) other parking lots The parking basin to be used at the site is determined. If the vacancy the day before the application or the number of parking slots used for one day is less than a certain number, it can be determined that there is no room in the parking lot. At this time, (a 3) the day before the application is a parking cascade that is used every day, (b3) the day before the application is a parking yard that is used all day, (c 3) the parking yard that is vacant the day before the application, (d3) the other The parking lots to be used are determined in order.

In order to use the parking lot, the user's past refund amount is first used. The refund amount is the amount accumulated according to the usage fee when the usage fee is canceled after the payment of the usage fee. The refund amount (515) is obtained from the data record of the user data table (FIG. 18) indicated by Xuser. The amount obtained by subtracting the refund amount from the usage fee Xprice is the billing amount that must be paid for this use. Substitute this amount for Xprice2. If the refund amount is larger than Xprice, the user does not need to pay this time. 0 is substituted for the charge amount Xprice2 (S1 207). Xprice is subtracted from the refund amount (515) of the data record indicated by Xuser. If the result is negative, 0 is substituted (S1208). If the payment accepting organization requests a certain transaction fee and cannot charge a small amount, the refund amount may not be used in full and the charged amount Xprice2 may be equal to or more than a certain amount.

Further, a new unique application data ID Xorder and a payment ID Xpay are newly generated, and a new data record is added to the parking lot application data table (FIG. 16) (S1209). Xorder for application data ID (301) for new data record, Xpay for payment ID (308), Xslot for parking basin ID (302), Xtype for application type (304), user ID (303) Substitute the value of Xuser for the price at the time of application (307), and the value of the price Xprice2 for the application. If the Xtype is 'time', Xtime_now is substituted for the start time (305) and Xtime_end is substituted for the end time (306). In 310), the date 30 days from now is substituted.

Next, the parking of all the usage periods Xday = {Xday_start, Xday_start + 1,..., Xday_start + Xdays-1} in the data slot of the parking lot data table (FIG. 15) indicated by the variable Xslot. Xorder is substituted into the measure application array (203) (S1210).

Next, the management computer (30) performs a parking basin ID transmission process. That is, the user contact mail address (503) is searched from the data record of the user data table (FIG. 18) indicated by Xuser, and the payment ID Xpay, the billing amount Xprice2, the payment term, The parking lot name, the parking lot ID Xslot, and the usage periods Xday, Xdays, and Xtime_end are converted to a message and transmitted (S1211).

Further, from Xpark, the used parking lot ID1 (508), used parking lot ID2 (510), used parking lot ID3 (512), parking lot evaluation 1 (509), The parking lot evaluation 2 (511) and the parking lot evaluation 3 (513) are updated. The parking lot evaluation is the number of times the parking lot has been used, and is incremented by one for this application.

Further, when the charge amount Xprice2 is not 0 (S1212), the management computer (30) sends the payment ID Xpay and the charge amount Xprice2, the user name, the parking lot name to the payment receiving organization. The use period is transmitted by e-mail (S1213). When the user pays the fee to the payment receiving organization, the payment receiving organization sends an e-mail to the management computer (30) to the effect that the payment has been completed using the payment ID. Upon receipt of the mail, the management computer (30) searches the payment ID (308) of the parking lot application data table (FIG. 16), and sets the paid flag (309) of the searched data record to 'payment completed'. Set to.

After these processes, the management computer (30) completes the application procedure to the application terminal (32) and sends a message to the effect that the parking lot ID has been sent by e-mail, and a message "Application acceptance". The signal is transmitted, and the process is terminated (S1214). After displaying the received message (S406), the application terminal (32) waits for reception of an "application accepted" signal. After receiving the "application acceptance" signal (S407), the process ends. In the present embodiment, the parking lot name list is displayed based on the area name, but the parking lot ID may be directly input from the application terminal (32). After arriving at the parking lot, the ID displayed on the parking lot may be input using a portable terminal or the like.

2.4. Parking Lot Availability Determination Process This section describes how to determine whether a parking lot is available based on the parking lot ID of the parking lot and the type of application for 'time' and '1 day'. The management computer (30) searches the parking lot data table (FIG. 14) for a data record that matches the used parking lot ID, and determines whether there is an available parking lot. That is, it is determined whether there is a parking lot available in the parking lot from the parking lot empty cell number array (120) of the retrieved data record. First, in order to be able to park, the value of the parking lot empty cell array needs to be greater than 0 on all use days that are applied.

Next, it is confirmed whether or not there is a parking space that can be used continuously. Find the smallest number of parked cars in the number of parked cars array (119) for all subscribed use days. Let this be X_min_bn_day. From the parking basin data table (FIG. 15), data records having the same parking lot ID (202) are searched in the order of the parking basin ID. Among the parking cascades whose order is smaller than X_min_bn_day, find the parking cascade whose parking cascade application array value is 'NULL' for all use days. If there is a parking lot, the parking lot is available. Otherwise, the parking lot is unavailable.

3. Confirmation of Usage Status In order to prevent unauthorized use of the parking lot, the parking lot is patrolly monitored by a patrol manager. The parking lot manager browses in a list the correspondence between the vehicle number of the vehicle that has permission to use the parking lot and the parking lot ID at the present time, and determines an unauthorized user.

FIG. 5 shows a flowchart of the processing of the application status display terminal (33). The parking lot manager selects and displays the "use status confirmation" screen from the application status display terminal (33) (S502), inputs the parking lot ID and the parking lot administrator password (S503), and clicks the "confirm" button. push. When the confirmation button is pressed (S504), the application state display terminal (33) transmits the inputted parking lot ID, parking lot manager password, and "use status confirmation request" signal to the management computer (30). (S505).

When the management computer (30) receives the "use status confirmation request" (S803), it substitutes the received parking lot ID into Xpark2 (S1302). Next, the parking manager password (109) of the data record indicated by Xpark2 is obtained from the parking data table (FIG. 14). When the parking lot manager password (109) is different from the received parking lot manager password (S1303), a message to the effect that "the password is incorrect" is transmitted (S1304), and the process ends.

When the password is correct (S1303), the number of today's parking units is obtained from the parking number array (119) of the data record indicated by Xpark2 from the parking lot data table (FIG. 14), and this is set to X_min_bn_day2. Substitute (S1305). Further, a message is created to the effect that today's parking number is X_min_bn_day2 (S1306). Next, a data record whose parking lot ID (202) matches Xpark2 is searched from the parking basin data table (FIG. 15) in ascending order of parking basin ID (S1401). A message is created for each data record of the parking lot whose order is smaller than X_min_bn_day2 (S1402). First, the parking lot ID (201) of the data record of the parking lot is added to the message (S1404). Next, an application ID corresponding to today is obtained from the parking cascade application sequence (203) of the parking cascade data record, and is substituted into Xorder2. When Xorder2 is 'NULL', since there is no application to the parking lot (S1405), “empty” is added to the message (S1406), and processing for the next parking lot starts. When Xorder2 is not 'NULL', a data record of the parking lot application data table (FIG. 16) indicated by Xorder2 is obtained. When the application type (304) is “time” (S1407) and the current time is before the use start time (305) (S1408), the message “planned to enter” is added to the message (S1409). When the application type (304) is “time” (S1407) and the current time is after the use end time (306) (S1410), “previous car” is added to the message (S1411). Next, from the data record of the user data table (FIG. 18) indicated by the user ID (303), a user vehicle number (504), a user vehicle size (505), and a user vehicle type (506) are respectively obtained in the message. The process is added (S1412), and processing for the next parking space starts. When all the message creation processes for the parking lot data records whose order is smaller than X_min_bn_day2 are completed (1402), the created message is transmitted to the application status display terminal (33) (1403), and the process ends. The application status display terminal (33) displays the received message (S506) and ends the process.

In this example, the number of parked vehicles is shown as a numerical value. However, for example, the parking frame ID is displayed regardless of the presence or absence of an application, and the number of parked vehicles is indicated by the number of displayed parking frame IDs. good. Alternatively, the number of available parking spaces may be indirectly indicated by indicating the number of available parking spaces after displaying the application user. The number of parking cavities may be indicated indirectly by indicating the number of parking pits as a whole and indicating the number of non-service cabs.

Although not described in detail here, the use can be canceled from the application terminal (32). The user inputs a contact telephone number, a user password, and a cancellation date from the application terminal (32). The management computer (30) inserts 'NULL' in the value of the canceled application date in the parking casser application array (203) of the data record of the parking casser data table (FIG. 15) according to the input parameters. Then, the parking lot empty cell number array (120) in the parking lot data table (FIG. 14) adds 1 to the value of the canceled application date.

[0083] 6. On-time processing The management computer (30) generates an interrupt every 10 minutes and searches the parking lot application data table (FIG. 16). A data record whose application type (304) is 'time' is detected, the use end time (306) of the record is compared with the present time, and if 10 minutes have passed from the use end time, the parking space ID ( The value of today in the parking cascade application array (203) of the data record of the parking cascade data table (FIG. 15) indicated by 302) is set to 'NULL' to make the parking cascade array available.

The management computer (30) generates an interrupt once a month and performs the following processing. FIG. 13 is a flowchart showing the contents of the processing. A data record in which the paid flag (309) in the parking basin application data table (FIG. 16) is 'payment completed' and the application type (304) is '1 day' or 'time' is searched ( S1702). A certain percentage of this parking fee is collected as a system usage fee, and the balance is paid to the parking operator. This parking lot management consideration is tabulated for each parking lot (S1704). The totalized amount is paid to the parking lot payment account number (108) in the parking lot data table (FIG. 14). After the aggregation, the data record whose paid flag (309) is “paid” is deleted (1705).

Further, the application data corresponding to the application data whose payment period has expired is dealt with. That is, a data record in which the paid flag (309) of the parking basin application data table (FIG. 16) is 'not paid' and the payment term (310) exceeds the present time is searched, and the user ID ( Using the data record of the user data table (FIG. 18) indicated by 303), an e-mail for urging the unpaid user to pay is transmitted (1706).

Here, the application terminal (32) and the application status display terminal (33) have been described as different terminals, but the same terminal may have both functions. Alternatively, the terminal has only a browser function of displaying a text described in, for example, HTML (Hyper Text Markup Language), and uses a technology such as CGI (Comm on Gateway Interface) on the management computer (30). The script may be executed, and the result may be converted to HTML and transmitted.

In the embodiment, first, input of data for identifying a user, such as a user's telephone number, is requested, and then the availability of the parking lot according to the usage date is displayed. If the communication capacity of the application terminal, the display function of the application terminal, and the calculation function are sufficient, the availability of the parking lot according to the date of use at the beginning or the availability of the parking lot of the day is displayed, and the user is identified at the time of application afterwards You may be required to input data to be performed. In addition, the number of empty parking lots is displayed first, and after the user enters a use date, the presence or absence of continuously available parking lots is determined, and the correct parking lot availability is displayed. Is also good.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a parking lot management system.

FIG. 2 is a flowchart relating to a use application by an application terminal according to the first embodiment.

FIG. 3 is a continuation of the flowchart relating to use application by the application terminal of the first embodiment.

FIG. 4 is a continuation of the flowchart relating to a use application by the application terminal according to the first embodiment.

FIG. 5 is a flowchart relating to confirmation of a usage status by an application status display terminal according to the first embodiment.

FIG. 6 is a flowchart regarding processing of a management computer.

FIG. 7 is a continuation of the flowchart relating to the processing of the management computer.

FIG. 8 is a continuation of the flowchart relating to the processing of the management computer.

FIG. 9 is a continuation of the flowchart relating to the processing of the management computer.

FIG. 10 is a continuation of the flowchart relating to the processing of the management computer.

FIG. 11 is a continuation of the flowchart relating to the processing of the management computer.

FIG. 12 is a continuation of the flowchart relating to the processing of the management computer.

FIG. 13 is a continuation of the flowchart relating to the processing of the management computer.

FIG. 14 shows the contents of a data record of a parking lot data table.

FIG. 15 shows the contents of a data record of a parking lot data table.

FIG. 16 shows the contents of a data record of a parking basin application data table.

FIG. 17 shows the contents of a data record of a regional data table.

FIG. 18 shows the contents of a data record of a user data table.

[Explanation of symbols]

11 ... CPU, 12 ... CRT, 13 ... LAN board, 14 ... hard disk, 15 ... keyboard, 16 ... ROM, 17 ... RAM, 19 ...
Internal bus, 20… Router, 21… LAN, 30… Management computer, 31… Internet, 32… Application terminal, 33
… Application status display terminal

Claims (2)

[Utility model registration claims] In a parking lot management system for managing a parking lot having a plurality of parking pits, an application terminal capable of inputting a vehicle number and an application signal indicating an intention to apply for a parking lot, and an application state of the parking lot, Storage means for storing in association with the vehicle number, availability determination means for determining availability of the parking lot based on the application status of the parking lot, and parking availability transmission means for transmitting the availability of the parking lot to the application terminal And an application status display terminal for displaying a list of vehicle numbers of vehicles applied to the parking lot at the current time. 2. The parking lot management system according to claim 1,
Storage means for storing the number of parking lots and the application period of the number of parking lots, and availability judging means for judging the availability of the parking lot from the application state of the parking lot, the number of parking lots and the application period of the number of parking lots, A parking lot management system comprising: a list of vehicle numbers of a plurality of vehicles applied to a parking lot at a current time; and an application status display terminal for displaying the number of parked vehicles at the current time.