Parking lot management system and program

Abstract

To provide a technology for reducing an installation burden imposed on a parking lot.SOLUTION: When a user enters any parking lot with user's own vehicle, a server 50 of a system that manages a plurality of parking lots receives parking lot information (S106) for specifying the any parking lot and vehicle information (S110) for specifying the user's own vehicle from an information processing terminal 90 of the user, determines that any parking lot specified by the received parking lot information is a current parking lot, and registers a vehicle specified by the received vehicle information in a memory in association with the current parking lot (S207). When the user exits any parking lot with the user's own vehicle, the system further transmits parking fee data representing a parking fee to the information processing terminal 90 in a case in which the user's own vehicle matches any of vehicles registered in the memory and in which an exit request is received from the information processing terminal 90.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to a technique for managing parking lots, and in particular to a technique for reducing the equipment burden imposed on parking lots. [Background technology]

[0002] Parking lots with multiple parking spaces (or "car spaces") for vehicles are already in widespread use. From the viewpoint of the method of transporting a vehicle to a target parking space, this type of parking lot can be classified into a type in which a user drives a vehicle to the target parking space, and a mechanical type in which a pallet or cage is mechanically moved to mechanically transport the vehicle to the target parking space.

[0003] In addition, the parking lot may be rented to the user free of charge or 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 the parking lot is rented to the user.

[0004] Hourly parking lots can be classified according to the management method used; they are manned, where a person is always present on-site to manage and monitor the lot, and unmanned, where no such person is always present, but is dispatched to the lot sporadically.

[0005] In addition, hourly parking lots can be classified according to the payment method of the parking fee into prepaid types, where the user pays a parking fee corresponding to the planned parking time when entering the parking lot, and postpaid types, where the user pays a parking fee corresponding to the actual parking time when leaving the parking lot.

[0006] Several prior art documents were found which disclose some of the types of parking lots described above.

[0007] Patent Document 1 discloses technology that makes it possible to completely automate the entry and exit process for a parking lot using a GPS, computer, and communication device installed in the vehicle, without installing any dedicated equipment in the parking lot, and without requiring the user to operate their own mobile terminal or any equipment in the lot.

[0008] Specifically, Patent Document 1 discloses a technology that measures the current location of the vehicle using a GPS-based positioning function installed in the vehicle in which the user is riding, rather than in the user's communication device, and when the vehicle's location transitions from a state in which it does not match any parking lot location to a state in which it matches any parking lot location, automatically detects the user's entry into that parking lot, and when the vehicle's subsequent position transitions from a state in which it matches the parking lot location to a state in which it does not match, automatically detects the user's exit from that parking lot.

[0009] Furthermore, Patent Document 2 discloses a technology that requires the installation of a wireless station within a parking lot, while acquiring a user's location information and behavior information using a GPS and acceleration sensor mounted on the user's mobile terminal, and using this information to detect the user's entry and exit from the parking lot in which the user is currently located, thereby making it possible to completely automate the entry and exit process for the parking lot.

[0010] Incidentally, a prepaid hourly parking system is already known as a parking management system. According to this management system, in the entry stage where a user enters a parking lot to park his / her vehicle, the user is granted the right to use the parking lot on the condition that the user specifies a valid parking time in hours, which is the time period during which the user wishes to park the vehicle in the parking lot, and pays in advance a parking fee equivalent to the length of the valid parking time.

[0011] Patent Document 3 describes a conventional example of a prepaid parking lot. This parking lot is equipped with a fee settlement device that allows users to prepay parking fees, and an exit gate management device that opens the exit gate and allows users to exit the parking lot on the condition that it is confirmed at the time of exit that the regular parking fee has been paid at the time of entry.

[0012] When entering the parking lot, a user who uses the parking lot predicts the length of time that the vehicle needs to be continuously parked there as an effective parking time, and pays a parking fee corresponding to the effective parking time. [Prior art documents] [Patent documents]

[0013] [Patent Document 1] JP 2001-202542 A [Patent Document 2] JP 2013-256380 A [Patent Document 3] JP 2010-250734 A Summary of the Invention [Problem to be solved by the invention]

[0014] Theoretically, the technology described in Patent Document 1 makes it possible to completely automate the entry and exit process for a parking lot. However, in order to adopt the technology described in Patent Document 1, the vehicle must be equipped with a positioning device (positioning function) such as a GPS, a computer (signal processing function), and a communication device (communication function) for communicating with an external server, that is, the vehicle must be highly functional (for example, intelligent).

[0015] In contrast, the technology described in Patent Document 2 uses a user's mobile terminal that has a signal processing function, a communication function, a positioning function, and a behavior detection function, instead of installing special equipment in the vehicle. Today, mobile terminals equipped with such functions have become widespread, and the technology described in Patent Document 2 makes it possible to completely automate the entry and exit process for a parking lot without requiring the vehicle to have high functionality (for example, intelligence).

[0016] However, the technology described in Patent Document 1 only focuses on the relationship between the location information of the mobile terminal and the location information of the parking lot, and attempts to identify the parking lot where the user entered after getting in, which poses a practical problem in that the system is highly susceptible to malfunction.

[0017] In addition, the technology described in Patent Document 2 attempts to identify the parking lot where the user entered by focusing on user behavioral information in addition to the location information of the mobile device. However, there is a practical problem in that the system is still highly likely to malfunction because the positioning accuracy of mobile devices is limited and the user behavioral information that is focused on is not specific to the parking lot.

[0018] Furthermore, when constructing the prepaid parking lot described in Patent Document 3, it is necessary to install in the parking lot a fee settlement device that allows users to prepay parking fees, and an exit gate device that monitors the time when users leave the parking lot and checks whether the valid parking time has not yet expired. Therefore, constructing this parking lot requires a large capital investment.

[0019] Based on the above findings, the present invention relates to a technique for managing parking lots, and in particular, has been made with the objective of providing a technique for reducing the equipment burden imposed on parking lots. [Means for solving the problem]

[0020] In order to solve the problem, according to a first aspect of the present invention, A parking management system for managing a plurality of parking lots, a server capable of communicating with an information processing terminal of a user who uses the parking lot; The server is a registration unit that receives parking lot information for identifying one of the parking lots and vehicle information for identifying the user's vehicle from the information processing terminal when the user enters one of the parking lots with the user's vehicle, and that sets one of the parking lots identified by the received parking lot information as a current parking lot, and registers the vehicle identified by the received vehicle information in a memory in association with the current parking lot; a parking fee data transmission unit that transmits parking fee data representing a parking fee to the information processing terminal when the user leaves any of the parking lots together with the user's vehicle and the user's vehicle matches any of the vehicles registered in the memory and a request for leaving the parking lot is received from the information processing terminal; Includes A parking management system is provided.

[0021] According to a second aspect of the present invention, A program executed by a computer of the information processing terminal of the user who uses any one of the plurality of parking lots managed by the parking lot management system, The information processing terminal has a plurality of functions, an information transmission function that transmits to the server, when the user enters a parking lot with the user's vehicle, parking lot information for identifying the parking lot and vehicle information for identifying the user's vehicle; a parking fee data receiving function for receiving the parking fee data from the server when the user leaves any of the parking lots with his / her vehicle and the user's vehicle matches any of the vehicles registered in the memory and the user transmits the leaving request to the server; Including, A program executed to realize the functions. is provided.

[0022] The present invention provides the following embodiments. Each embodiment is divided into clauses, each clause is numbered, and other clause numbers are cited as necessary. This is to facilitate understanding of some of the technical features that the present invention may employ and their combinations, and should not be construed as limiting the technical features and combinations that the present invention may employ to the following embodiments. In other words, it should be construed that technical features that are not described in the following embodiments but are described in this specification may be appropriately extracted and employed as technical features of the present invention.

[0023] Furthermore, describing each section in a form that refers to the number of other sections does not necessarily mean that the technical features described in each section are prevented from being separated and made independent from the technical features described in other sections, and it should be interpreted that the technical features described in each section can be made independent as appropriate depending on their nature.

[0024] (1) A method for managing a plurality of prepaid parking lots using an information processing terminal of a user who selects one of the plurality of prepaid parking lots to use and a management server that centrally manages the plurality of parking lots, comprising: a parking lot display step in which the information processing terminal and / or the management server, in a parking entry stage in which the user enters a parking lot together with the vehicle, selects from the plurality of parking lots those located near the current location, which is acquired using a location acquisition unit of the information processing terminal, as a plurality of candidate parking lots, and displays the candidate parking lots on a screen of the information processing terminal; a parking lot selection process in which, when a user issues a first instruction to the information processing terminal to select one of the parking lots, the information processing terminal and / or the management server selects one of the plurality of candidate parking lots as the parking lot that the user wishes to use; an entry permission step in which, when a user instructs the information processing terminal to pay a prepaid parking fee corresponding to the length of the desired parking time at the parking lot and inputs identification information unique to the user and / or the vehicle, the information processing terminal and / or the management server grant the user authority to enter the parking lot; an exit confirmation step of, when the user issues a second instruction to the information processing terminal to confirm that the user has exited from the parking lot at an exit stage where the user's vehicle exits the parking lot, confirming that the user has exited from the parking lot together with the vehicle; A parking lot management method comprising:

[0025] (2) the parking lot selection step is performed in a state in which the first instruction is not accepted unless a distance between the current position of the information processing terminal and the parking lot to be used is equal to or less than a tolerance value in the entrance stage; The parking lot management method described in paragraph (1), wherein the exit confirmation process is carried out in a state in which the second instruction is accepted at the exit stage, regardless of whether the distance from the parking lot to be used of the current location of the information processing terminal is within the allowable value.

[0026] (3) A parking lot management method as described in paragraph (1), in which at least one of the following is adopted: the parking lot selection process is performed in a state in which the first instruction is not accepted unless the distance from the current location of the information processing terminal to the parking lot to be used is within an allowable value at the entry stage; and the exit confirmation process is performed in a state in which the second instruction is accepted regardless of whether the distance from the current location of the information processing terminal to the parking lot to be used is within the allowable value.

[0027] (4) The parking lot management method according to any one of (1) to (3), further comprising an extension step of extending the desired parking time when the information processing terminal and / or the management server receives a third instruction from the information processing terminal to extend the desired parking time and an instruction to pay an extension fee commensurate with the extension of the desired parking time before the expiration of the desired parking time.

[0028] (5) A parking lot management method as described in (4), in which the extension process is performed in a state in which the third instruction is accepted regardless of whether the distance from the parking lot to be used is within the allowable value.

[0029] (6) A parking lot management method described in any of (1) to (5), wherein the identification information includes at least one of a user ID, an identification number of the user's vehicle, and an identification number of a parking space in which the user's vehicle is parked among multiple parking spaces in the parking lot.

[0030] (7) A parking lot management method described in any of (1) to (6), wherein the identification information includes a combination of multiple types of identification information that each identify a plurality of different entities that are related to a user.

[0031] The use of a combination of the multiple types of identification information in this section improves security in authenticating a user or a vehicle compared to the use of a single type of identification information. Here, examples of "multiple different entities related to a user" include the user himself / herself, the user's vehicle, one of the multiple parking spaces in the parking lot that the user uses, the user's information processing terminal, etc.

[0032] (8) A program executed by a computer of an information processing terminal to realize the information processing terminal according to any one of (1) to (7).

[0033] In this application, the term "program" may be interpreted to mean, for example, a combination of instructions executed by a computer to perform a function, and may also be interpreted to include not only the combination of instructions, but also files and data that are processed in accordance with each instruction, but is not limited thereto.

[0034] Furthermore, this program may be executed by a computer alone to achieve the intended purpose, or may be executed by a computer together with other programs to achieve the intended purpose, but is not limited thereto. In the latter case, the program according to this section may be, but is not limited to, one that mainly consists of data.

[0035] (9) A program executed by the computer of the management server to realize the management server according to any one of (1) to (7).

[0036] (10) A recording medium having the program described in (8) or (9) recorded thereon in a computer-readable manner.

[0037] In this application document, the recording medium represented by the term "recording medium" may take various forms, including, but not limited to, magnetic recording media such as flexible disks, optical recording media such as CDs and CD-ROMs, magneto-optical recording media such as MOs, and non-removable storage such as ROMs. [Brief description of the drawings]

[0038] [Figure 1]FIG. 1 is a plan view showing an example of one of a number of parking lots centrally managed by a parking management system according to an exemplary embodiment of the present invention. [Diagram 2] FIG. 2 is a plan view showing a part of each of the vehicle compartments shown in FIG. 1 with a vehicle stopped in each of the vehicle compartments. [Diagram 3] FIG. 3 is a perspective view showing an example of communication between mobile terminals of users in each parking lot and a management server in a remote management center in the parking lot management system shown in FIG. [Figure 4] FIG. 4 is a conceptual diagram showing long-distance two-way communication between the user's mobile terminal shown in FIG. 3 and the management server shown in the same figure. [Diagram 5] FIG. 5 is a functional block diagram conceptually showing the mobile terminal shown in FIG. [Figure 6] FIG. 6 is a functional block diagram conceptually showing the management server shown in FIG. [Figure 7] FIG. 7 is a time chart conceptually showing an exemplary parking sequence realized by the parking lot management system. [Figure 8] FIG. 8 is a flowchart conceptually illustrating an example of a program executed by the mobile terminal, the management server, and the payment server, respectively, in order to assist a user in performing parking entry processing at a parking lot in the parking lot management system. [Figure 9] FIG. 9 is a flowchart conceptually illustrating an example of a program executed by the mobile terminal, the management server, and the payment server, respectively, in the parking lot management system to extend the valid parking time in response to an extension request from the user after the user enters a parking lot. [Figure 10] FIG. 10 is a flowchart conceptually illustrating an example of a program executed by a mobile terminal, a management server, and a payment server, respectively, in the parking lot management system to assist a user in performing the exit process after entering a parking lot. [Figure 11]FIG. 11 is a diagram conceptually showing a management list stored in the memory of the management server shown in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0039] Hereinafter, one of several exemplary embodiments of the present invention will be described in detail with reference to the drawings.

[0040] First, referring to Figures 1 and 2, a parking lot management system (hereinafter simply referred to as the "system") 10 according to an exemplary embodiment of the present invention is a system for managing a number of parking lots 20 (only a representative parking lot 20 among those parking lots 20 is shown in Figure 1), each of which can accommodate a number of vehicles (including automobiles, bicycles, and motorcycles, but in the example shown in Figure 2, automobiles).

[0041] In this system 10, a parking lot management method according to an exemplary embodiment of the present invention is implemented in which a management server 50 at a remote location centrally manages multiple parking lots 20 through communication with multiple users' mobile terminals (an example of the "information processing terminals") 90.

[0042] In one example, the system 10 allows a user to use the parking lot 20 on the condition that the user uses his / her mobile terminal 90 as a parking ticket and pays a prepaid parking fee that corresponds to the length of the planned parking time (desired parking time, valid parking time).

[0043] Fig. 1 shows a plan view of a parking lot 20. The parking lot 20 has a number of car compartments (an example of the parking space) 22 that allow multiple vehicles to be parked at the same time. The parking lot 20 has a single entrance / exit 24 (which is both an entrance and an exit). Fig. 2 shows some of the car compartments 22 with vehicles parked in each car compartment 22.

[0044] This parking lot 20 is unmanned, and furthermore, this parking lot 20 is not equipped with a gate device that opens and closes as appropriate to prevent unauthorized vehicles from leaving through the entrance / exit gate 24 of the parking lot 20, a car stopper device that appears and disappears as appropriate to prevent unauthorized vehicles from leaving from the parking space 22, a ticket issuing machine for issuing parking tickets to users who are drivers, and a payment machine for users to pay parking fees.

[0045] With regard to the definition of the term "vehicle," the term should be construed as including not only automobiles but also all kinds of moving objects such as bicycles and motorcycles.

[0046] As shown in Fig. 1, there are two types of parking spaces on the premises of parking lot 20. These are spaces for renting parking spaces 22 to vehicle users on a daily basis (temporary parking spaces or daily rental spaces), and spaces for renting parking spaces 22 to vehicle users on a monthly basis on the premise of a prior contract (monthly parking spaces). Hereinafter, when we simply say "parking lot 20," we mean only the temporary parking spaces of parking lot 20.

[0047] This system 10 employs the centralized management method described above as its parking lot management method. Specifically, as shown in Fig. 3, the system includes a mobile terminal 90 of each user in each parking lot 20, and a management server 50 installed in a management center 40 that centrally manages the multiple parking lots 20.

[0048] The management center 40 is operated by a parking lot manager (for example, the owner of the land used as parking lot 20 who manages the parking lot 20 himself, or a parking lot management company entrusted by the owner of someone else's land to manage the land as parking lot 20).

[0049] The user's mobile terminal 90 is a device that is carried by the user and has a wireless communication function, such as a mobile phone, a smartphone, a laptop computer, a tablet computer, or a PDA.

[0050] The portable terminal 90 is an example of the aforementioned "information processing terminal," but is a type of information processing terminal that is not necessarily carried by a user at all times. The portable terminal 90 may be carried by a user outside a vehicle, but may not be carried by a user inside the vehicle.

[0051] As shown in FIG. 4, the mobile terminal 90 has, as an essential function, a positioning function for receiving GPS (Global Positioning System) signals from multiple artificial satellites in outer space and measuring the current position (ground position) of the mobile terminal 90 on a map.

[0052] Furthermore, in an optional embodiment, the mobile terminal 90 receives, in addition to a GPS signal (one example of an off-site transmitter), a signal indicating the location coordinates of a base station (another example of an off-site transmitter) and a signal from a transmitter (also called an "on-site transmitter") 30 installed in the parking lot 20 that indicates a transmitter ID unique to each transmitter 30.

[0053] In this optional aspect, the mobile terminal 90 converts the transmitter ID represented by the signal received from each transmitter 30 into a corresponding parking lot ID that identifies the parking lot 30 in which the transmitter 30 is supposed to be installed, according to predefined rules (e.g., a conversion table) to represent the correspondence between the two.

[0054] As a result, the mobile terminal 90 distinguishes the currently detected transmitter 30 from other transmitters 30 and measures the position of the currently detected transmitter 30 (e.g., its position on a map, the position of the parking lot in which it is installed, etc.) and / or measures the distance between the currently detected transmitter 30 and the mobile terminal 90 by measuring the strength of the signal received from the currently detected transmitter 30.

[0055] The transmitter 30 is generally a device known as a beacon device, a radio beacon, or the like that transmits a beacon signal as an identification signal. In one example, the transmitter 30 generates an identification signal representing a corresponding transmitter ID (or parking lot ID) by modulating an original signal, and locally transmits the generated identification signal as an IR signal, a Bluetooth (registered trademark) signal, an NFC (near field wireless communication) signal, or the like.

[0056] As shown in Fig. 4, the mobile terminal 90 performs long-distance two-way wireless communication with the management server 50 of the management center 40. In addition, in a mode in which the transmitter 30 is installed in the parking lot 20, as shown in Fig. 4, the mobile terminal 90 receives the above-mentioned identification signal from the transmitter 30 installed in the parking lot 20 that the user is currently visiting, in a contact state or a non-contact state with the transmitter 30, by a short-distance one-way wireless communication method.

[0057] 2, the user can operate the mobile terminal 90 in the vehicle to receive signals for positioning (such as GPS reception, reception from a base station, and reception from the in-parking transmitter 30) and communicate with the management server 50. According to this embodiment, the user can operate the mobile terminal 90 for entry (including payment in the case of prepaid parking) and exit (including payment in the case of deferred parking) in the vehicle, and is not bothered by weather such as cold and hot, wind and rain.

[0058] 3, the user can operate the mobile terminal 90 outside the vehicle to receive signals for positioning and communicate with the management server 50. This embodiment is useful, for example, when the user needs to approach the mobile terminal 90 and hold it over or touch it to the in-vehicle transmitter 30.

[0059] Next, the hardware configuration of mobile terminal 90 will be explained with reference to functional block diagram FIG. 5. Mobile terminal 90 is mainly composed of computer 134 having processor 130 and memory 132 that stores a plurality of programs (also called "applications") executed by processor 130.

[0060] The mobile terminal 90 further has a display unit (e.g., an LCD display) 136 for displaying information, a receiving unit 138 for receiving signals from the transmitter 30 and the management server 50, and a transmitting unit 140 for generating signals and transmitting the signals to the management server 50.

[0061] The mobile terminal 90 further includes an input unit 150 for inputting data and commands from the user.

[0062] The input unit 150 has, for example, an operation unit operable by a user to input desired information (e.g., commands, data, etc.) to the mobile terminal 90. The operation unit may be, but is not limited to, a touch screen that displays icons operable by the user (e.g., virtual buttons, such as an entry button, exit button, and extension request button described below), a physical operation unit operable by the user (e.g., a keyboard, keypad, button, switch, etc.), and a microphone that detects voice.

[0063] The mobile terminal 90 further includes a GPS (Global Positioning System) receiver 152. As is well known, the GPS receiver 152 receives a plurality of GPS signals from a plurality of GPS satellites, and measures the position (latitude, longitude, and altitude) of the GPS receiver 152 on the earth by triangulation based on the GPS signals.

[0064] Alternatively or additionally, the mobile terminal 90 may determine its position on the earth (latitude and longitude) by triangulation using the positions of multiple base stations.

[0065] In other words, the positioning unit (an example of the “location acquisition unit”) of the mobile terminal 90 may be a GPS positioning unit or a base station positioning unit, each of which is an outside-area transmitter, or may be an inside-area transmitter 30.

[0066] The mobile terminal 90 further includes an acceleration sensor 154 that detects its own acceleration (for example, the acceleration when the mobile terminal 90 undergoes translational motion). Since the acceleration sensor 154 is mounted on the mobile terminal 90, it vibrates together with the mobile terminal 90, and as a result, the acceleration sensor 154 detects the acceleration acting on the mobile terminal 90 as being equivalent to the acceleration acting on the mobile terminal 90.

[0067] The type of this acceleration sensor 154 is, for example, a semiconductor piezoresistance type, a capacitance type, a thermal detection type, etc. In one example, this acceleration sensor 154 can be designed to detect accelerations Gx, Gy, Gz in three axial directions, namely, the X-axis, the Y-axis, and the Z-axis, respectively, and output one representative acceleration as a composite value Gr of the three detected values ​​Gx, Gy, Gz.

[0068] When a user is carrying a mobile terminal 90, this acceleration sensor 154 detects an acceleration that is approximate to the acceleration acting on the user, and when the user is in a vehicle, it detects an acceleration that is approximate to the acceleration acting on the vehicle (e.g., forward / rear acceleration, forward / rear deceleration).

[0069] Theoretically, the acceleration acting on the mobile terminal 90 can be calculated by calculating the speed by time-differentiating the position measured based on the above-mentioned GPS signal, and then further differentiating the speed with respect to time. However, in terms of accuracy, the acceleration detected by the acceleration sensor 154 may be superior. In any case, the acceleration sensor 154 is an example of an acceleration acquisition unit that detects or estimates the axial acceleration of the vehicle.

[0070] This mobile terminal 90 can further optionally incorporate, although not shown, a light sensor that detects light (e.g., sunlight) exposed to the mobile terminal 90, a sound sensor that detects sound (e.g., a vehicle engine sound) exposed to the mobile terminal 90, a proximity sensor that detects the approach of an object (e.g., a vehicle) to the mobile terminal 90, etc.

[0071] Next, the hardware configuration of the management server 50 will be explained with reference to the functional block diagram of FIG. 6. The management server 50 is mainly composed of a computer 164 having a processor 160 and a memory 162 that stores a plurality of applications executed by the processor 160.

[0072] This management server 50 further has a display unit (e.g., a liquid crystal display) 166 that displays information, a receiving unit 168 that receives signals from the mobile terminal 90, a transmitting unit 170 that generates signals and transmits the signals to the mobile terminal 90, and a clock 172. This management server 50 does not directly receive information from the transmitter 30, but in effect receives information via the mobile terminal 90.

[0073] <Parking sequence example>

[0074] 7 is a time chart showing an example of a parking sequence realized by using the system 10. A specific description will be given below.

[0075] In the parking sequence shown in the figure, after a user has parked their vehicle in a certain parking lot 20, before the expiration of the valid parking time, the user performs an exit operation on the mobile terminal 90 (for example, the user taps a virtual "exit button" displayed on the screen of the mobile terminal 90 (or, for example, touches, presses, selects, gives voice instructions)), and then the user gets into their vehicle and leaves (exits) the parking lot 20.

[0076] The entry stage begins with the user entering a certain parking lot 20 for the purpose of entry (the vehicle entering the parking lot) and ends with the user exiting the parking lot 20. When the user inputs a parking request (or an entry request) to the mobile terminal 90, at that time or at a later time, the remaining time out of the valid parking time starts to be subtracted (counted down) and the actual parking time starts to be increased (counted up).

[0077] In contrast, the exit stage begins with the user entering the parking lot 20 where the entry was made for the purpose of exiting (the vehicle leaving the parking lot), and ends with the user exiting the parking lot 20.

[0078] In the parking sequence shown in the figure, the user exits the parking lot 20 before the valid parking time expires, and before the exit, the user performs the exit operation. As a result, the actual parking time starts from "entering (occurrence of a parking request, entering operation)" and ends with "leaving operation." Therefore, in this parking sequence, the exit of the user (together with the vehicle) in the exit stage means actual leaving (actual leaving).

[0079] <Warehousing process>

[0080] In FIG. 8, a stocking process program executed by the mobile terminal 90, a stocking process program executed by the management server 50, and a payment program executed by the payment server 60 are shown.

[0081] It is desirable that the entry processing program of the mobile terminal 90 be started either manually by the user or automatically when the user enters any of the parking lots 20 to enter the vehicle and parks the vehicle in any of the vacant parking spaces 22 within the parking lot 20.

[0082] Here, in order to automatically start the entry processing program, for example, the mobile terminal 90 can determine whether or not the measured current position of the mobile terminal 90 is in any of the parking lots 20, and after determining that the position of the mobile terminal 90 is present in any of the parking lots 20, if the position of the mobile terminal 90 does not change for a predetermined period of time or more (or the amount of change is below a reference value), it can determine that the vehicle has entered any of the vehicle compartments 22, and the mobile terminal 90 can automatically start the entry processing program.

[0083] In the same manner, the unloading process program can be started automatically.

[0084] 8, in step S101, the mobile terminal 90, in response to a manual or voice input (login request) from the user, transmits a request for logging in to a website operated by the management server 50 together with the user ID to the management server 50. Upon receiving the login request, the management server 50 establishes communication between the mobile terminal 90 and the management server 50.

[0085] In this embodiment, in order to identify the user and the vehicle, the user is forced to input the user ID and the vehicle number into the mobile terminal 90, but it is also possible to input only the vehicle number. This is because, if there is a one-to-one relationship between a vehicle and a user, identifying the vehicle by the vehicle number will also identify the user.

[0086] Next, in step S201, the management server 50 searches in the memory 162 for multiple parking lot data (individual parking lot position data) representing the map positions (longitude and latitude) of multiple parking lots (managed parking lots) 20 that are centrally managed by the management center 40, and transmits the multiple parking lot data thus obtained to the mobile terminal 90.

[0087] Thereafter, in step S102, the mobile terminal 90 measures the current position (longitude and latitude) of the user based on the GPS signal received by the GPS receiver 152 from the outside (or the identification signal received from the in-house transmitter 30).

[0088] Next, in step S103, the mobile terminal 90 extracts, from among the multiple parking lots (managed parking lots) 20 represented by the multiple parking lot data received from the management server 50, those whose distance from the measured current location is less than or equal to an allowable value (e.g., 100 m, 200 m, 300 m, 400 m, 500 m, etc., also referred to as a "set value"), thereby narrowing down the multiple parking lots (managed parking lots) 20 to multiple candidate parking lots 20 that are simply predicted to be used by the user based on the geographical information.

[0089] Thereafter, in step S104, the mobile terminal 90 displays on the screen a partial map located near the current position out of the entire map.

[0090] Next, in step S105, the mobile terminal 90 displays on the screen a number of markers, e.g., pins, each representing one of the candidate parking lots 20, associated with the location of the corresponding candidate parking lot 20, and overlaid on the partial map.

[0091] Next, in step S106, the mobile terminal 90 allows the user to select one of the multiple candidate parking lots 20 displayed on the screen as the parking lot 20 that the user would like to use, for example, by tapping the corresponding marker or pin.

[0092] In response to only that selection, or in response to additional input from the user (for example, tapping the "enter" button on the screen), the mobile terminal 90 transmits the parking lot ID as identification information of the selected parking lot 20 to the management server 50 together with the user ID and the entry request. Here, the "user's operation to select any parking lot" or the "user's operation of tapping the enter button" is an example of the "first instruction (selection operation to select a parking lot)."

[0093] The user can only select a parking lot 20 that he / she wishes to use from among the multiple candidate parking lots 20 displayed on the screen of the mobile terminal 90. In other words, the user cannot select a parking lot 20 that he / she wishes to use from among the multiple parking lots (managed parking lots) 20 that are located far from the user's current location, or more precisely, from the current location of the mobile terminal 90.

[0094] On the other hand, in the entry stage, the user usually enters one of the parking lots (the parking lot that the user wishes to use) 20 while in his / her vehicle with his / her mobile terminal 90.

[0095] Therefore, the fact that the user can only select the parking lot 20 he or she wishes to use from among the multiple candidate parking lots 20 narrowed down as described above means that the user is automatically restricted to performing parking entry processing only at the site of one of the parking lots 20 where the user is likely to actually be staying. Therefore, according to this embodiment, location authentication regarding the parking lot 20 (determination of which parking lot 20 the user is actually staying at) is performed, and the user can only use the parking lot 20 where the user is likely to actually be staying at.

[0096] On the other hand, for the parking lots 20, the determination of whether there is a vacant parking space 22 or whether the parking lot 20 is full is omitted. Therefore, the user is required to actually go to the parking lot 20 that he / she wants to use and determine for himself / herself whether the parking lot 20 is full or not. Nevertheless, if the user is permitted to reserve the parking lot 20 at an arbitrary location away from the parking lot 20 that he / she wants to use, there is a possibility that the user will reserve a parking lot 20 that is actually full. Therefore, in this embodiment, the user is prohibited from reserving the parking lot 20 at an arbitrary location away from the parking lot 20 that he / she wants to use.

[0097] As a result, even if a user attempts to input a request for entry into the mobile terminal 90 when the user is in a location far from the desired parking lot 20, the mobile terminal 90 will not accept the request. Similarly, when the user is in a location far from the desired parking lot 20, the user cannot even select the desired parking lot 20 on the mobile terminal 90.

[0098] In order to accurately measure the latest current position of the mobile terminal 90, i.e., the latest current position of the user, regardless of the amount of movement of the user after execution of step S102, it is desirable for the mobile terminal 90 to be designed to obtain the latest current position using the positioning unit immediately before executing step S106, measure the distance between the current position and each representative point of the multiple candidate parking lots 20, and permit execution of step S106 if all distances are equal to or less than the allowable value. If execution of step S106 is not permitted, the user is not authorized to use the parking lot 20 that he or she wishes to use.

[0099] Alternatively, the mobile terminal 90 is preferably designed to, for example, obtain the latest current location using the positioning unit immediately after executing step S106, measure the distance between the current location and a representative point of one of the multiple candidate parking lots 20 provisionally selected by the user, and validate the provisional selection of the parking lot 20 by the user if the distance is equal to or less than an allowable value, but invalidate the provisional selection of the parking lot 20 by the user if the distance is longer than the allowable value. If the provisional selection is invalidated, the user is not authorized to use the parking lot 20 that he or she wishes to use.

[0100] When the parking lot ID is received from the mobile terminal 90, the management server 50 searches the memory 162 for parking lot information corresponding to the parking lot ID in step S202. Here, the "parking lot information" includes the name, location, fee table data, etc. of the corresponding parking lot 20. After the search, the management server 50 transmits the parking lot information acquired by the search to the mobile terminal 90.

[0101] Thereafter, in step S107, the mobile terminal 90 displays on the screen the parking lot information received from the management server 50, excluding the price list data.

[0102] Next, in step S108, the mobile terminal 90 displays on the screen the fee table data from the parking lot information received from the management server 50. The fee table data indicates the relationship between the length of time the vehicle will be parked in the current parking lot 20 (valid parking time, desired parking time) and the parking fee (prepaid fee). As a result, a plurality of parking times and a plurality of fees are displayed on the screen of the mobile terminal 90 in a visually associated manner.

[0103] Thereafter, in step S109, the mobile terminal 90 selects one of the multiple fees in response to an input from the user.

[0104] Next, in step S110, the mobile terminal 90 displays on the screen of the mobile terminal 90 a web page for assisting the user in inputting the vehicle number of the user's vehicle (the vehicle license plate number, e.g., a four-digit number) into the mobile terminal 90. The user then inputs the vehicle number of the user's vehicle. Here, the "vehicle number" is an example of the aforementioned "identification information unique to the user and / or vehicle," and another example is image data unique to the vehicle that the user has photographed with a digital camera built into the mobile terminal 90.

[0105] Next, in step S111, the mobile terminal 90 measures the current time as the entry time to request the user to make a final confirmation of the input contents, adds the valid parking time corresponding to the selected fee amount to the entry time to calculate the scheduled exit time, and displays the scheduled exit time and the entered vehicle number on the screen. When the user inputs into the mobile terminal 90 that he or she has confirmed the displayed contents, the mobile terminal 90 transmits necessary parking information including the entry time, scheduled exit time, vehicle number, and fee (prepaid parking fee) to the management server 50 together with confirmation display data indicating this and the user ID. The entry time, scheduled exit time, vehicle number, and fee are stored in the memory 132 of the mobile terminal 90.

[0106] When the management server 50 receives the necessary parking information from the mobile terminal 90, the management server 50 stores the entrance time included in the necessary parking information in the memory 162 in association with the user ID in step S203.

[0107] Next, in step S204, the management server 50 stores in the memory 162 the planned departure time included in the parking requirement information in association with the user ID.

[0108] Thereafter, in step S205, the management server 50 stores the vehicle number included in the parking information in the memory 162 in association with the user ID.

[0109] It should be noted that the measurement of the entry time and / or the calculation of the scheduled departure time may be performed in the management server 50 instead of in the mobile terminal 90.

[0110] In addition, the entry time may be measured as the occurrence time of a specified event, and may be measured as a time equal to the occurrence time of any one of a number of events, such as an event in which the mobile terminal 90 sends an entry request, an event in which the management server 50 receives an entry request, an event in which the user selects one of the parking lots 20, an event in which the user makes the final confirmation, or an event in which the user completes payment.

[0111] After executing step S111, the mobile terminal 90 proceeds to a processing stage for electronic payment in response to an input (payment request) from the user in step S112. Specifically, the mobile terminal 90 transmits a payment request to the payment server 60.

[0112] Then, in step S301, the payment server 60 searches the memory of the payment server 60 for payment screen data representing a payment web page for assisting the user in making an electronic payment, and transmits the payment screen data obtained as a result to the mobile terminal 90.

[0113] Next, in step S113, the mobile terminal 90 displays a payment web page on the screen based on the payment screen data received from the payment server 60.

[0114] Thereafter, in step S114, when the user inputs information (including the user ID) for electronic payment into the payment web page, the mobile terminal 90 transmits the payment information together with a payment instruction (payment request, electronic payment request) and the user ID to the payment server 60. Here, the "payment instruction" is an example of the "payment instruction".

[0115] Then, in step S302, the payment server 60 performs electronic payment based on the payment information received from the mobile terminal 90, and when the payment is completed, it sends payment completion data indicating this to the mobile terminal 90, and at that time, sends the payment completion data to the management server 50 together with the user ID.

[0116] In response to this, in step S206, the management server 50 grants the current user the authority to use the current parking lot 20, thereby permitting the user to enter the parking lot.

[0117] Next, in step S207, management server 50 registers the above-mentioned user ID, vehicle number, entry time, scheduled exit time, and the presence or absence of exit confirmation, which will be described later, in the management list shown in Fig. 11 and stored in memory 162. After this registration, management server 50 transmits entry permission data, which indicates that entry is permitted, to mobile terminal 90.

[0118] When the entry permission data is received from the management server 50, the mobile terminal 90 outputs a message indicating that entry has been permitted by image or sound in step S115.

[0119] In the example shown in Fig. 8, steps S301 and S302 constitute the above-mentioned payment program executed by the payment server 60. This payment program is the same regardless of whether it is for warehousing processing, extension request processing, or warehousing processing. However, for convenience of explanation, only step S302 is shown in Fig. 9 and Fig. 10.

[0120] <Extension request processing>

[0121] In FIG. 9, an extension request processing program executed by the mobile terminal 90, an extension request processing program executed by the management server 50, and a payment program executed by the payment server 60 are shown.

[0122] As shown in FIG. 9, in step S121, the mobile terminal 90 transmits an extension request to extend the valid parking time before it expires together with the vehicle number (or together with the user ID and vehicle number) to the management server 50 in response to manual or voice input from the user (for example, tapping the "extension request button" on the screen). If an extension request is input by the user after the valid parking time has expired, the mobile terminal 90 does not accept it and rejects it. Here, the "user's operation of tapping the extension request button" is an example of the "third instruction (extension request operation to extend the valid parking time)".

[0123] In the extension request process, unlike the entry process, no location authentication is performed for the parking lot 20. This allows the user to request an extension of the valid parking time and pay the extension fee at any location away from the parking lot 20 being used.

[0124] As a result, if the user inputs an extension request into the mobile terminal 90 at a location away from the parking lot 20 being used, the mobile terminal 90 will accept the extension request.

[0125] When the extension request is received, in step S221, the management server 50 compares the vehicle number received from the mobile terminal 90 with a plurality of vehicle numbers registered in the management list shown in Fig. 11, and determines whether a vehicle number matching the received vehicle number has already been registered. If it has already been registered, the management server 50 searches the memory 162 for fee table data (the relationship between the length of extension time from the valid parking time that is commensurate with the amount of the fee that has already been paid and the amount of the extension fee) corresponding to the corresponding parking lot 20, and transmits the fee table data obtained as a result to the mobile terminal 90.

[0126] Next, in step S122, the mobile terminal 90 displays the received fee table data on the screen.

[0127] Then, in step S123, when the user selects one of the extension times, the mobile terminal 90 calculates an updated scheduled departure time in accordance with the selection result, stores it in memory 132, and then transmits data representing the scheduled departure time to the management server 50 together with an extension request.

[0128] In response to this, the management server 50 stores the received scheduled departure time in the memory 162 in step S222.

[0129] Then, in step S124, the mobile terminal 90 moves to a processing stage for electronic payment in response to an input (payment request) from the user. Specifically, the mobile terminal 90 transmits a payment request to the payment server 60. Then, the payment server 60 transmits the payment screen data to the mobile terminal 90.

[0130] Next, in step S125, the mobile terminal 90 displays a payment web page on the screen based on the payment screen data received from the payment server 60.

[0131] Thereafter, in step S126, when the user inputs information (including the user ID) for electronic payment into the payment web page, the mobile terminal 90 transmits the payment information to the payment server 60 together with a payment instruction (payment request) and the user ID.

[0132] Then, in step S302, the payment server 60 performs electronic payment based on the payment information received from the mobile terminal 90, and when the payment is completed, it sends payment completion data indicating this to the mobile terminal 90, and at that time, sends the payment completion data to the management server 50 together with the user ID.

[0133] In response to this, the management server 50 permits the user to extend the valid parking time in step S223.

[0134] Next, in step S224, the management server 50 updates the planned departure time in the management list shown in Fig. 11 so that the extended planned departure time is reflected. After the update, the management server 50 transmits extension permission data indicating that the extension of the valid parking time has been permitted to the mobile terminal 90.

[0135] When the extension permission data is received from the management server 50, in step S127, the mobile terminal 90 displays on the screen and / or outputs audibly through the speaker the fact that the valid parking time has been extended and the updated scheduled departure time.

[0136] <Shipping process>

[0137] FIG. 10 shows a delivery processing program executed by the mobile terminal 90, a delivery processing program executed by the management server 50, and the settlement program executed by the settlement server 60.

[0138] 10, in step S141, the mobile terminal 90 transmits a request for leaving together with the vehicle number (or together with the user ID and the vehicle number) to the management server 50 in response to manual or voice input from the user (for example, tapping the "leave button" on the screen). Here, the "user's operation of tapping the leave button" is an example of the "second instruction (leave operation to confirm leaving)".

[0139] In the exit process, unlike the entry process, no location authentication is performed for the parking lot 20. Therefore, the user can perform the exit process at any location away from the parking lot 20 being used.

[0140] As a result, if the user inputs a request to leave the parking lot into the mobile terminal 90 at a location away from the parking lot 20 being used, the request to leave the parking lot will be accepted.

[0141] However, such a user's exit operation is equivalent to the user impersonating the user who actually left the parking lot 20 and making a false notification to the management server 50, even though the vehicle is actually still parked in the parking lot 20, and therefore constitutes fraudulent activity.

[0142] In response to this, the management center 40 periodically dispatches an operator to the parking lot 20, and the operator detects vehicles that are still parked in the parking lot 20 after the scheduled departure time by comparing the vehicle number of the vehicle with the vehicle numbers in the management list that have passed the scheduled departure time. Therefore, it is expected that users will refrain from committing such fraudulent acts due to the guilt and shame of being detected.

[0143] When the leaving request is received, in step S241, the management server 50 checks the vehicle number received from the mobile terminal 90 against a plurality of vehicle numbers registered in the management list shown in Fig. 11, and determines whether a vehicle number matching the received vehicle number has already been registered. If the vehicle number has already been registered, in step S242, the management server 50 measures the current time and determines the leaving time to be equal to that time.

[0144] Thereafter, in step S243, the management server 50 refers to the management list to determine whether the corresponding scheduled departure time is earlier than the determined departure time, i.e., whether the actual parking time exceeds the valid parking time.

[0145] Assuming that the actual parking time has not exceeded the valid parking time this time, the determination in step S243 will be NO, and the management server 50 will confirm in step S244 that the user has left the current parking lot 20.

[0146] Next, in step S245, the management server 50 updates the management list shown in Figure 11 to indicate that an exit confirmation exists for the corresponding vehicle number, and further transmits exit confirmation data to the mobile terminal 90 indicating that the exit confirmation has been completed.

[0147] When the delivery confirmation data is received from the management server 50, the mobile terminal 90 displays the fact that delivery has been confirmed on the screen and / or outputs the same by voice from the speaker in step S145.

[0148] On the other hand, if it is assumed that the actual parking time exceeds the valid parking time, the determination in step S243 becomes YES, and the management server 50 calculates the amount of the additional fee to be paid by the user based on the difference between the actual departure time and the scheduled departure time in step S246. In one example, the additional fee is calculated to be higher than the above-mentioned extension fee in the sense of imposing a penalty on the user.

[0149] Thereafter, in step S247, management server 50 transmits to mobile terminal 90 additional fee billing data indicating that the user is to be billed for the additional fee.

[0150] Upon receiving the additional fee billing data, the mobile terminal 90 proceeds to a processing stage for electronic payment in response to an input (payment request) from the user in step S142. Specifically, the mobile terminal 90 transmits a payment request to the payment server 60. Thereafter, the payment server 60 transmits the payment screen data to the mobile terminal 90.

[0151] Next, in step S143, the mobile terminal 90 displays a payment web page on the screen based on the payment screen data received from the payment server 60.

[0152] Thereafter, in step S144, when the user inputs information (including the user ID) for electronic payment into the payment web page, the mobile terminal 90 transmits the payment information to the payment server 60 together with a payment instruction (payment request) and the user ID.

[0153] Then, in step S302, the payment server 60 performs electronic payment based on the payment information received from the mobile terminal 90, and when the payment is completed, it sends payment completion data indicating this to the mobile terminal 90, and at that time, sends the payment completion data to the management server 50 together with the user ID.

[0154] In response to this, the management server 50 confirms the payment of the additional fee by the user and the withdrawal by the user in step S248. Then, the management server 50 proceeds to step S245, and the above-mentioned processing is executed.

[0155] [Some exemplary effects obtained by the above-described embodiment]

[0156] 1. Reduction in the costs and labor that parking lot managers must bear regarding the facilities of parking lot 20

[0157] According to this embodiment, instead of using the equipment installed in the parking lot 20, the user can use his / her mobile terminal 90 to carry out procedures for entering, leaving, and extending parking time.

[0158] Therefore, according to this embodiment, it is easy to reduce the cost and labor required for manufacturing or purchasing, installing, and maintaining and inspecting the equipment to be installed in the parking lot 20.

[0159] 2. Preventing erroneous selection of parking lot 20 during the entry stage

[0160] According to this embodiment, while the selection of one of the parking lots 20 is made using the positioning function of the mobile terminal 90, the final selection depends on the user's operation, thereby reliably preventing erroneous selection of a parking lot 20 due to insufficient accuracy of the positioning function.

[0161] 3. Reduces the discomfort felt by users who use a parking lot 20 whose occupancy status is not monitored.

[0162] In this embodiment, the vacant / full status of the parking lot 20 is not monitored, so the user is required to actually go to the parking lot 20 that he / she wants to use and visually look for vacant spaces 22. In order to make the request obvious, the user is prohibited from carrying out procedures for entering the parking lot 20, that is, making a so-called reservation for the parking lot 20, on the mobile terminal 90 when he / she is away from the parking lot 20 that he / she wants to use.

[0163] As a result, a situation in which a user reserves a parking lot 20 that is far away from the parking lot 20 that the user desires to use, but when the user actually arrives at the parking lot 20, there are no vacant spaces 22, and the user is unable to park, resulting in discomfort, is avoided.

[0164] 4. The user has a high degree of freedom in selecting the location where the outgoing operation can be performed.

[0165] According to this embodiment, the user can perform the exit operation at any location on the mobile terminal 90. If the valid parking time has not yet expired, the user can perform the exit operation normally without paying an additional fee, and if the valid parking time has already expired, the user can perform the exit operation normally by paying the additional fee.

[0166] Thus, according to this embodiment, if a user inadvertently neglects to perform the exit operation at a parking lot 20, the exit operation can be performed on the mobile terminal 90 at a location away from the parking lot 20, which is convenient for the user.

[0167] It should be noted that the above-described embodiments are some specific examples of the present invention applied to a communication environment in which a user's portable terminal 90, which may be carried by the user or may be left in the vehicle, is used as the "user information processing terminal" of the present invention. Alternatively, the present invention can also be applied to a communication environment in which, for example, a computer installed in the user's vehicle and having a communication function and a vehicle behavior information acquisition function is used as the "user information processing terminal" of the present invention.

[0168] That is, the "user information processing terminal" in the present invention may be an information processing terminal of a type intended to be carried by a user, or an information processing terminal of a type intended to be mounted in a vehicle.

[0169] Additionally, in this embodiment, all or part of the processing executed in the mobile terminal 90 may be executed in the management server 50 instead, and conversely, all or part of the processing executed in the management server 50 may be executed in the mobile terminal 90 instead. This is because which device executes the processing to be executed is usually determined by the circumstances at the time, such as the amount and type of data to be handled, the processing speed and storage capacity of each device, etc.

[0170] Although several embodiments of the present invention have been described in detail above with reference to the drawings, these are merely examples, and it is possible to embody the present invention in other forms that incorporate various modifications and improvements based on the knowledge of those skilled in the art, including the aspects described in the "Summary of the Invention" section above.

Claims

1. A parking management system for managing a plurality of parking lots, a server capable of communicating with an information processing terminal of a user who uses the parking lot; The server is a registration unit that receives parking lot information for identifying one of the parking lots and vehicle information for identifying the user's vehicle from the information processing terminal when the user enters one of the parking lots with the user's vehicle, and that sets one of the parking lots identified by the received parking lot information as a current parking lot, and registers the vehicle identified by the received vehicle information in a memory in association with the current parking lot; a parking fee data transmission unit that transmits parking fee data representing a parking fee to the information processing terminal when the user leaves any of the parking lots together with the user's vehicle and the user's vehicle matches any of the vehicles registered in the memory and a request for leaving the parking lot is received from the information processing terminal; Parking management system including.

2. The server further comprises: an electronic payment unit that processes electronic payment for the parking fee; a payment completion data transmission unit that transmits payment completion data indicating the completion of the electronic payment to the information processing terminal when the electronic payment is completed; The parking lot management system according to claim 1 .

3. The parking lot management system according to claim 1 , wherein the vehicle information includes the license plate number of the vehicle and / or image data unique to the vehicle.

4. A program executed by a computer of the information processing terminal of the user who uses any one of the plurality of parking lots managed by the parking lot management system according to claim 1, The information processing terminal has a plurality of functions, an information transmission function that transmits to the server, when the user enters a parking lot with the user's vehicle, parking lot information for identifying the parking lot and vehicle information for identifying the user's vehicle; a parking fee data receiving function for receiving the parking fee data from the server when the user leaves any of the parking lots with his / her own vehicle and the user's own vehicle matches any of the vehicles registered in the memory and the user transmits the leaving request to the server; Including, A program executed to realize the above-mentioned functions.

5. A recording medium on which the program according to claim 4 is recorded so as to be readable by a computer.

6. A program for functioning as the server according to any one of claims 1 to 3.

7. A recording medium on which the program according to claim 6 is recorded so as to be readable by a computer.

Images