Parking lot barrier, system and program

Abstract

To provide a technology that enables parking in a parking lot more reliably and easily.SOLUTION: A second processor causes a mobile terminal 20 to execute a step of requesting permission to transition the operation state of a parking lot barrier 10 from a locked state to an unlocked state. A first processor causes a server 30 to execute a step of granting permission in response to the request for permission to transfer the operation state of the parking lot barrier 10 from a locked state to an unlocked state, a step of confirming that the operation state of the parking lot barrier 10 is in a locked state, and a step of sending an unlock instruction to the parking lot barrier 10 to transition the operation state of the parking lot barrier 10 from the locked state to the unlocked state. A third processor causes the parking lot barrier 10 to execute a step of receiving the unlock instruction, and a step of transferring the operation state of the parking lot barrier 10 from the locked state to the unlocked state.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to parking lot barriers, systems and programs for managing parking lots. [Background technology]

[0002] Conventionally, parking lots are installed in various places in cities. Some of these parking lots are operated unmanned by using various sensors. For example, a user parks a vehicle in a parking space. After entering the parking space, the vehicle is locked so that it cannot be taken out. When the user pays, the lock is released and the vehicle can be taken out.

[0003] There is also a technology that allows users to check whether a parking space is available or full via the Internet. For example, Patent Document 1 discloses a parking management system that allows users to reserve a parking space via the Internet. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2002-175374 A Summary of the Invention [Problem to be solved by the invention]

[0005] When a user searches for a parking lot with an available car via the Internet, the user may arrive at the parking lot only to find that another user has parked there, making it impossible for the user to park the car.

[0006] Patent Document 1 discloses a technology for making reservations in advance. However, there is a problem in that the reservation procedure is complicated and not convenient for users.

[0007] Therefore, the present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide technology that enables parking in a parking lot more reliably and easily. [Means for solving the problem]

[0008] The system according to the first aspect is a parking management system including a parking barrier arranged in each of a plurality of parking spaces, a server, and a mobile terminal, and the parking barrier, the server, and the mobile terminal are capable of communicating with each other. The parking barrier has at least two operating states: a locked state that prevents a vehicle from entering the parking space, and an unlocked state that does not prevent a vehicle from entering the parking space. The server has a first processor. The mobile terminal has a second processor. The parking barrier has a third processor. The second processor causes the mobile terminal to execute the steps of transmitting first user information about a user to the server, and requesting permission to transition the operating state of the parking barrier from the locked state to the unlocked state. The first processor causes the server to execute the steps of receiving the first user information from the mobile terminal, granting permission to the request for permission to transition the operating state of the parking barrier from the locked state to the unlocked state, confirming that the operating state of the parking barrier is in the locked state, and transmitting an unlock instruction to the parking barrier to transition the operating state of the parking barrier from the locked state to the unlocked state. The third processor causes the parking lot barrier to execute the steps of receiving an unlocking instruction and, when the unlocking instruction is received, transitioning the operation state of the parking lot barrier from a locked state to an unlocked state.

[0009] This parking management system can remotely switch the parking barrier between locked and unlocked states, allowing users to enter and exit parking spaces reliably and easily. Effect of the Invention

[0010] According to the present disclosure, parking in a parking lot can be performed more reliably and easily. [Brief description of the drawings]

[0011] [Figure 1] 1 is a diagram showing an unlocked state of the parking lot barrier 10 of the first embodiment. FIG. [Diagram 2] 1 is a diagram showing a locked state of the parking lot barrier 10 of the first embodiment. FIG. [Diagram 3] 2 is another diagram showing the locked state of the parking lot barrier 10 of the first embodiment. FIG. [Figure 4] 1 is a diagram showing the arrangement of a parking lot barrier 10 in a first embodiment. [Diagram 5] 1 is a conceptual diagram of a parking lot management system PS1 in the present disclosure. [Figure 6] 11 is a flowchart showing a process of the management system PS1 of the first embodiment. [Figure 7] FIG. 1 illustrates an example of a parking lot in accordance with the present disclosure. [Figure 8] A diagram showing the relationship between each part of a parking lot management system PS1 in the present disclosure. [Figure 9] FIG. 2 is a diagram showing a functional configuration realized by the hardware configuration of the parking lot barrier 10. [Figure 10] FIG. 2 is a diagram showing a functional configuration realized by the hardware configuration of the mobile terminal 20. [Figure 11] FIG. 2 is a diagram showing a functional configuration realized by the hardware configuration of the server 30. [Figure 12] 2 is a diagram showing a functional configuration realized by the hardware configuration of a management terminal 40. FIG. [Figure 13] FIG. 2 is a block diagram showing the functional configuration of a parking lot barrier 10. [Figure 14] FIG. 2 is a block diagram showing the functional configuration of a mobile terminal 20. [Figure 15] FIG. 2 is a diagram illustrating a functional configuration of a server 30. [Figure 16]3 is a diagram illustrating an example of the data structure of a user information DB 3021 stored in a storage unit 302 of a server 30. FIG. [Figure 17] 3 is a diagram illustrating an example of the data structure of a parking lot DB 3022 stored in the storage unit 302 of the server 30. FIG. [Figure 18] 3 is a diagram illustrating an example of the data structure of a parking information DB 3023 stored in a storage unit 302 of a server 30. FIG. [Figure 19] 13 is a diagram showing an example of a screen for confirming the intention to use a parking lot, which is displayed on the display 241 of the output device 24 of the mobile terminal 20. FIG. [Figure 20] 11 is a diagram showing an example of a list of parking lots displayed on the display 241 of the output device 24 of the mobile terminal 20. FIG. [Figure 21] 1 is a diagram illustrating an example of a parking lot map displayed on a display 241 of an output device 24 of a mobile terminal 20. FIG. [Figure 22] 13 is a diagram illustrating an example of a parking lot map selection screen displayed on the display 241 of the output device 24 of the mobile terminal 20. FIG. [Figure 23] 1 is a relationship diagram for explaining the relationship between the processing performed by a parking lot barrier 10, a mobile terminal 20, and a server 30. FIG. [Figure 24] 10 is a flowchart showing the processing carried out by the parking lot barrier 10, the mobile terminal 20, and the server 30. [Diagram 25] 1 is a diagram showing the arrangement of weight sensors 141 in the four corner areas inside a parking space 1. FIG. [Figure 26] 13 is a block diagram showing a case where the barrier portion 12 has an LED 121. FIG. [Figure 27] FIG. 13 is a diagram illustrating an example of the data structure of a parking lot DB 3022 in the third embodiment. [Figure 28] FIG. 13 is a diagram illustrating an example of a data structure of a parking information DB 3023 in the third embodiment. [Figure 29] 13 is a diagram showing an example of a reservation screen displayed on the display 241 of the mobile terminal 20. FIG. [Diagram 30]1 is a first flowchart showing the processing performed by the parking lot barrier 10, the mobile terminal 20, and the server 30 when a user makes a reservation for a parking lot. [Diagram 31] 11 is a second flowchart showing the processing performed by the parking lot barrier 10, the mobile terminal 20, and the server 30 when a user makes a reservation for a parking space. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In all the drawings explaining the embodiment, the same reference numerals are given to common components, and repeated explanations are omitted. Note that the following embodiment does not unduly limit the contents of the present disclosure described in the claims. In addition, not all of the components shown in the embodiment are essential components of the present disclosure. In addition, each figure is a schematic diagram and is not necessarily illustrated strictly.

[0013] In the following description, a "processor" refers to one or more processors. The at least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may be another type of processor such as a GPU (Graphics Processing Unit). The at least one processor may be a single-core or multi-core.

[0014] Furthermore, the at least one processor may be a processor in the broad sense, such as a hardware circuit (for example, a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC)) that performs part or all of the processing.

[0015] In addition, in the following explanation, the processing may be described with the "program" as the subject, but since the program is executed by a processor to perform a specified processing step by appropriately using a memory unit and / or an interface unit, etc., the subject of the processing may be the processor (or a device such as a controller having the processor).

[0016] The program may be installed in a device such as a computer, or may be, for example, in a program distribution server or a computer-readable (e.g., non-transitory) recording medium. In the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0017] The functions performed by the components described herein may be implemented in circuitry or processing circuitry, including general purpose processors, application specific processors, integrated circuits, ASICs, CPUs, conventional circuits, and / or combinations thereof, programmed to perform the functions described. Processors include transistors and other circuits and are considered to be circuitry or processing circuitry. A processor may be a programmed processor that executes a program stored in a memory.

[0018] In this specification, a circuitry, unit, or means is hardware that is programmed to realize or performs the described functions, which may be any hardware disclosed in this specification or any hardware known to be programmed to realize or perform the described functions.

[0019] If the hardware is a processor considered to be a type of circuitry, the circuitry, means, or unit is a combination of the hardware and software used to configure the hardware and / or processor.

[0020] In the following description, identification numbers are used as identification information for various objects, but other types of identification information (for example, identifiers including alphabetic characters or symbols) may be used instead.

[0021] In addition, in the following description, when describing elements of the same type without distinguishing between them, reference signs (or common signs among the reference signs) may be used, and when describing elements of the same type with distinction between them, the identification numbers (or reference signs) of the elements may be used.

[0022] In the following description, the control lines and information lines are those that are considered necessary for the description, and not all control lines and information lines in the product are necessarily shown. All components may be connected to each other.

[0023] <First embodiment> <Parking lot barriers> FIG. 1 is a diagram showing an unlocked state of the parking lot barrier 10 of the first embodiment. The parking lot barrier 10 is arranged in a parking space 1 of a parking lot. The parking lot barrier 10 has a barrier body 11, a barrier portion 12, a fixing portion 13, and a motor 14. The barrier body 11 is the main body of the parking lot barrier 10, and is fixed to the parking space 1 by the fixing portion 13. The barrier portion 12 can rotate around a rotation axis 15 by receiving a rotation drive from the motor 14. The barrier portion 12 has a character string "NO PARKING" displayed on it. In the state shown in FIG. 1, the barrier portion 12 is lowered to the ground side. At this time, the barrier portion 12 does not hinder parking, so the user can park the vehicle in this parking space. That is, FIG. 1 shows an unlocked state in which the parking lot barrier 10 is unlocked. Note that the barrier portion 12 does not come into contact with the barrier body 11 during the rotation of the barrier portion 12. The motor 14 may be a stepping motor or a servo motor.

[0024] The parking barrier 10 can be remotely controlled using wireless communication from another device to adjust its position to prevent or allow entry to or exit from a parking space. The parking barrier 10 can also connect to a cloud server to display its current status and change its physical orientation remotely.

[0025] FIG. 2 is a diagram showing the locked state of the parking lot barrier 10 of the first embodiment. The barrier body 11 of the parking lot barrier 10 is fixed to the parking space 1, and the barrier portion 12 is raised upward. At this time, the display surface of the barrier portion 12 indicating "NO PARKING" is disposed almost vertically to the ground. Therefore, the user can visually confirm that parking in the locked parking space 1 is not possible. In FIG. 2, the barrier portion 12 is in a raised state. At this time, the upper end of the barrier portion 12 is sufficiently higher than the height of the bottom of the vehicle. When the vehicle attempts to enter the parking space 1, the barrier portion 12 is located at a height where it will come into contact with the vehicle. Therefore, the user cannot park the vehicle in the parking space 1.

[0026] Fig. 3 is another diagram showing the locked state of the parking lot barrier 10 of the first embodiment. Fig. 3 is a diagram showing the appearance of the parking lot barrier 10 seen from an angle different from that of Fig. 2. As shown in Fig. 2, the barrier portion 12 is in an upwardly raised state. At this time, the upper end of the barrier portion 12 is located at a position higher than the normal bottom surface of the vehicle.

[0027] In this way, the parking lot barrier 10 can be in an operating state including a "locked state" as shown in Figures 2 and 3, and an "released state" as shown in Figure 1. Here, the "locked state" is a state in which the barrier portion 12 is raised, preventing a vehicle from entering the parking space 1. At this time, the user cannot park the vehicle in the parking space 1. The "released state" is a state in which the barrier portion 12 is lowered toward the ground, not preventing a vehicle from entering the parking space 1. At this time, the user can park the vehicle in the parking space 1.

[0028] The parking lot barrier 10 maintains the "released state" from the time when the server 30 issues an instruction to switch to the released state until the time when the server 30 issues an instruction to switch to the locked state. The parking lot barrier 10 maintains the "locked state" from the time when the server 30 issues an instruction to switch to the locked state until the time when the server 30 issues an instruction to switch to the released state. The motor 14 smoothly transitions between the "locked state" and the "released state."

[0029] <Location of parking lot barrier 10> 4 is a diagram showing the arrangement of the parking lot barrier 10 in the first embodiment. The parking lot barrier 10 is arranged near the center of the parking area 2. Even in this case, the parking lot barrier 10 can prevent vehicles from parking. In this way, the arrangement position of the parking lot barrier 10 only needs to be within the area of ​​the parking space 1.

[0030] <Overview of the parking management system PS1> FIG. 5 is a conceptual diagram of a parking lot management system PS1 in the present disclosure. The parking lot management system PS1 in the present disclosure provides a service of a parking lot where a user can park by accepting input from the user via application software. The parking lot management system PS1 has a parking lot barrier 10, a mobile terminal 20, a server 30, and a management terminal 40. The parking lot barrier 10 prevents a vehicle from entering a parking space 1, and allows a vehicle to enter the parking space 1 only when permission is granted. The mobile terminal 20 is for accepting input from the user and presenting the status of the parking lot to the user. The server 30 is a cloud server that performs various processes. The management terminal 40 is for the manager of the parking lot to grasp and manage the status of the parking lot. The server 30 and the management terminal 40 may be integrated.

[0031] The mobile terminal 20 can send instructions to the server 30. The server 30 relays instructions to the parking barrier 10 to lift or fold the parking barrier 10. The status of the parking barrier 10 can be viewed and controlled via the management terminal 40. The mobile terminal 20 can wirelessly communicate with the parking barrier 10 via any wireless communication protocol, including but not limited to Bluetooth, LoRaWAN, Wifi, etc. The parking barrier 10 has the capability to connect to the mobile terminal 20 via any wireless communication protocol. The parking barrier 10 may have the capability to connect to the server 30 via any wireless communication protocol, including but not limited to 4G, 5G, Wifi, and / or indirectly via a gateway.

[0032] <Operation of management system PS1> 6 is a flowchart showing the process of the management system PS1 of the first embodiment. In step S12, the program checks whether the user has permission to operate the parking lot barrier 10. If permission is given, the program proceeds to step S16. If permission is not given, the program requests the server 30 to grant permission in step S14.

[0033] In step S16, the user performs an operation to lower the parking lot barrier 10. The server 30 transmits an instruction to lower the parking lot barrier 10.

[0034] In step S18, upon receiving this instruction, the parking lot barrier 10 lowers the barrier portion 12. Then, the parking lot barrier 10 lowers the barrier portion 12 and notifies the server 30 that parking is now possible (step S20).

[0035] In step S22, calculation of the parking fee is started. The time when the vehicle becomes available for parking is set as the parking start time.

[0036] In step S24, the user parks the vehicle in the parking space 1. At this time, the parking lot barrier 10 is of course in the released state in which the vehicle can be parked.

[0037] In step S26, the user leaves the vehicle from the parking space 1. In step S28, sensors around the parking space 1 detect that the user's vehicle has left the parking space. Alternatively, the user inputs information to the mobile terminal 20 that the vehicle has left the parking space via the mobile terminal 20. The server 30 receives information that the vehicle has left the parking space.

[0038] In step S30, the server 30 transmits a lock command to the parking lot barrier 10 to lock the parking lot barrier 10. The parking lot barrier 10 receives the lock command and raises the barrier portion 12 to its original position. This prevents other vehicles from entering the parking space 1.

[0039] In step S32, the calculation of the fee is stopped, and in step S34, the parking fee is settled. In step S36, a message is sent to the server 30 indicating that the parking lot barrier 10 is in the locked state.

[0040] When the parking lot barrier 10 is to be locked, the parking lot barrier 10 may issue the lock instruction without going through the server 30.

[0041] Thus, the user starts the process by approaching the parking space 1, with or without a vehicle. The user can open an application software on the mobile terminal 20 and ask for user permission to unlock the parking space barrier 10. If permission is granted, the user can issue an instruction to lower the parking space barrier 10 by clicking a button. An unlock instruction to unlock the parking space barrier 10 is sent to the server 30 and then to the parking space barrier 10. Alternatively, the unlock instruction is sent directly to the parking space barrier 10 by short-range communication (e.g., Bluetooth (registered trademark)). This causes the parking space barrier 10 to lower the barrier portion 12. The server then updates the parking status. The management terminal 40 is connected to the server 30 and can view the parking status of the parking space barrier 10.

[0042] The parking status is updated, which starts the parking fee process and records the parking start time along with a start timestamp. The user parks the vehicle in the parking space 1. When the vehicle leaves the parking space 1, sensors around the parking barrier 10 detect it. The parking barrier 10 lifts the barrier portion 12 based on the detection result. A timestamp is recorded when the parking time ends. The parking fee is calculated. The parking status is communicated and updated to the server 30. The total parking fee amount is deducted from the customer's payment method.

[0043] In this way, the parking lot barrier of the first embodiment adjusts its position to prevent or allow entry to a parking space by remote control using wireless communication from another device. The parking lot barrier also connects to a cloud server, displays its current status, and can remotely change its physical orientation.

[0044] <Modification> <Mobile device> The mobile terminal 20 may be a mobile phone or other handheld device, and may be any communication device as long as it is capable of installing application software, has an input / output device, and is capable of communication.

[0045] <Approval> If the user does not have permission to park, the user sends a request to the server 30. An administrator operating the management terminal 40 manually approves the request. Alternatively, approval may be automatic. In this case, the user can raise and lower the parking lot barrier 10, similar to the flow chart of FIG. 6.

[0046] <Second embodiment> <Parking lot> FIG. 7 is a diagram illustrating a parking lot in the present disclosure. The parking lot is managed by a management system PS1. The management system PS1 manages a plurality of parking lots. A plurality of parking spaces 1 are arranged in a row in the parking lot. A parking lot barrier 10 is installed in each parking space 1. The parking lot barrier 10 is arranged on the vehicle entrance side of the parking space 1. As described below, the parking lot barrier 10 prevents the vehicle from entering and allows the vehicle to enter the parking space 1 if permission is granted. A user parks a vehicle in one of the plurality of parking spaces 1. The parking lot barrier 10 is fixed to the ground of the parking lot. In addition, a display unit 50 is provided in the parking lot. The display unit 50 is a screen for displaying to a user the vacant vehicle status in the parking lot, etc.

[0047] <Basic configuration of the parking lot management system PS1> 8 is a diagram showing the relationships between the various parts of the parking lot management system PS1 according to the present disclosure. The parking lot management system PS1 includes a parking lot barrier 10, multiple mobile terminals 20, a server 30, a management terminal 40, and a display unit 50, which are connected via a network. Here, the network indicates that the components are connected to each other via wired or wireless connections.

[0048] The parking lot barrier 10 is actually placed in a parking space 1 in a parking lot. The parking lot barrier 10 is a barrier that allows only vehicles permitted to park in the parking space 1 to enter the parking space 1. The parking lot barrier 10 is unlocked during the period when a vehicle permitted to park is parked there, and remains locked during other periods. The parking lot barrier 10 communicates with the mobile terminal 20 and the server 30, and takes either a locked state or an unlocked state based on the content of the communication.

[0049] The parking lot barrier 10 can communicate with the server 30 via wired or wireless communication. The parking lot barrier 10 can communicate wirelessly with the mobile terminal 20. The wireless communication between the parking lot barrier 10 and the mobile terminal 20 is, for example, short-range wireless communication such as Bluetooth (registered trademark).

[0050] The mobile terminal 20 is an information processing device operated by a user who uses the parking lot service. Application software for using the parking lot service is installed in the mobile terminal 20. The mobile terminal 20 may be, for example, a mobile terminal such as a smartphone or a tablet. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.

[0051] The mobile terminal 20 is capable of wireless communication with the server 30. The mobile terminal 20 is capable of wireless communication with the parking lot barrier 10.

[0052] The server 30 is an information processing device for managing the parking lot and providing vehicle parking services to users. The server 30 communicates with the mobile terminal 20 via a network, accepts input from the user, and presents options or necessary information to the user. The server 30 also communicates with the parking lot barrier 10 via the network, and instructs the operation of the parking lot barrier 10. The server 30 can calculate parking fees and settle parking fees.

[0053] The server 30 can communicate with the parking lot barrier 10 via wired or wireless communication. The server 30 can communicate with the mobile terminal 20 via wireless communication. The server 30 can communicate with the management terminal 40 via wired or wireless communication. The server 30 can communicate with the display unit 50 via wired or wireless communication.

[0054] The management terminal 40 is a terminal for an administrator who manages parking lots to access the server 30 via a network and check or manage the status of multiple parking lots.

[0055] The management terminal 40 can communicate with the server 30 via wired or wireless communication. The management terminal 40 can communicate with the parking lot barrier 10, the mobile terminal 20, and the display unit 50 via the server 30.

[0056] The display unit 50 is a display unit arranged in the parking lot. The display unit 50 displays, for example, either "full" or "vacant." The display unit 50 may display a parking lot map. In this case, the parking lot map shows an arrangement of multiple parking spaces 1. The parking lot map displays either "vacant" or "full" for each parking space 1.

[0057] The display unit 50 can communicate with the server 30 via wired or wireless communication. In response to an instruction from the server 30, the display unit 50 displays, for example, "full" or "vacant" to the user.

[0058] Each information processing device is configured by a computer equipped with a calculation device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the mobile terminal 20, the server 30, and the management terminal 40, explanations that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

[0059] The configuration and operation of each device will be described below.

[0060] <Functional composition of parking lot barrier 10> 9 is a diagram showing the functional configuration realized by the hardware configuration of the parking lot barrier 10. The parking lot barrier 10 includes a motor 14, a communication IF 16, a processor 17, a memory 18, a storage unit 19, and other units. Each unit has a barrier body 11, a barrier unit 12, and a fixed unit 13. The communication IF 16 is for communicating with external devices. The processor 17, the memory 18, and the storage unit 19 form a control system for the parking lot barrier 10. The control system for the parking lot barrier 10 raises and lowers the barrier unit 12 via the motor 14.

[0061] <Functional configuration of the mobile terminal 20> 10 is a diagram showing a functional configuration realized by the hardware configuration of the mobile terminal 20. The mobile terminal 20 has an input device 23, an output device 24, a communication IF 26, a processor 27, a memory 28, and a storage unit 29. The input device 23 accepts input from a user. The output device 24 displays information to the user. The communication IF 26 is for communicating with external devices. The processor 27, the memory 28, and the storage unit 29 form a control system.

[0062] <Server 30 Functional Configuration> FIG. 11 is a diagram showing a functional configuration realized by the hardware configuration of the server 30. The server 30 has an input / output IF 31, a communication IF 36, a processor 37, a memory 38, and a storage 39. The input / output IF 31 is an interface for receiving input and output from the outside. The communication IF 36 is an interface for communicating with the parking lot barrier 10, the mobile terminal 20, the management terminal 40, and the display unit 50. The processor 37 controls the server 30 and the management system PS1 as a whole. The memory 38 is used as appropriate when the processor 37 operates. The storage 39 stores a program for operating the management system PS1. The processor 37, the memory 38, and the storage 39 form a control system.

[0063] <Functional configuration of management terminal 40> FIG. 12 is a diagram showing a functional configuration realized by the hardware configuration of the management terminal 40. The management terminal 40 has an input device 41, an output device 42, a communication IF 46, a processor 47, a memory 48, and a storage unit 49. The input device 41 accepts input from an administrator. The output device 42 shows the results of processing by the processor 47 or the server 30 to the administrator. The communication IF 46 is an interface for communicating with the server 30. The processor 47 controls the management terminal 40. The memory 48 is used as appropriate when the processor 47 operates. The storage unit 49 stores programs and the like for operating the management terminal 40. The processor 47, the memory 48, and the storage unit 49 constitute a control system.

[0064] The processing performed by the parking lot management system PS1 will be described as being performed by the server 30. However, instead of the server 30, the management terminal 40 may perform the processing of the management system PS1.

[0065] In the following description, the server 30 and the management terminal 40 are assumed to be integrated into the server 30 as a single system.

[0066] <Configuration of each part of the parking lot barrier 10> 13 is a block diagram showing the functional configuration of the parking lot barrier 10. The parking lot barrier 10 has a communication IF 16, a control unit 170, a motor 14, and a storage unit 19. The control unit 170 is composed of a processor 17, a memory 18, and the storage unit 19.

[0067] The communication IF 16 has a server communication unit 161 and a wireless communication unit 162. The server communication unit 161 performs wired or wireless communication with the server 30. The wireless communication unit 162 performs short-range communication with the mobile terminal 20 using Bluetooth (registered trademark) or the like.

[0068] The control unit 170 has a communication control unit 171, a state notification unit 172, and a motor control unit 173. The communication control unit 171 controls the communication IF 16. The communication control unit 171 controls the server communication unit 161 and the wireless communication unit 162. The state notification unit 172 notifies the server 30 whether the parking lot barrier 10 is in a locked state or an unlocked state.

[0069] The motor control unit 173 controls the motor 14. The motor control unit 173 controls the direction, number of rotations, and rotation speed of the motor 14. Therefore, the motor control unit 173 raises and lowers the barrier unit 12 of the parking lot barrier 10 by controlling the rotation of the motor 14.

[0070] The memory unit 19 has a parking lot ID and a parking space ID. The parking lot ID is an ID assigned to each parking lot. For example, a common parking lot ID is assigned to the parking space barrier 10 of the first parking lot. The parking space ID is an ID assigned to each parking space 1. The parking lot ID and the parking space ID are transmitted, for example, when communicating with the mobile terminal 20 or the server 30.

[0071] <Configuration of each part of the mobile terminal 20> FIG. 14 is a block diagram showing a functional configuration of the mobile terminal 20. As shown in FIG. 14, the mobile terminal 20 has an antenna 211, an antenna 212, a first wireless communication unit 221, a second wireless communication unit 222, an input device 23, an output device 24, a voice processing unit 25, a microphone 251, a speaker 252, a control unit 270, and a storage unit 290. The control unit 270 appropriately uses a processor 27, a memory 28, and a storage unit 290 to control each unit. The mobile terminal 20 also has functions and configurations (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.) that are not particularly shown in FIG. 14. Each block included in the mobile terminal 20 is electrically connected by a bus or the like.

[0072] 10 includes an antenna 211, an antenna 212, a first wireless communication unit 221, and a second wireless communication unit 222. The first wireless communication unit 221 and the second wireless communication unit 222 correspond to the antenna 211 and the antenna 212, respectively.

[0073] The antenna 211 is an antenna for communicating with the base station or the server 30. The antenna 211 radiates a signal generated by the mobile terminal 20 as a radio wave. The antenna 211 also receives the radio wave from space and provides the received signal to the first wireless communication unit 221.

[0074] The antenna 212 is, for example, an antenna for Bluetooth (registered trademark). The antenna 212 radiates a signal emitted by the mobile terminal 20 as a radio wave. The antenna 212 also receives the radio wave from space and provides the received signal to the second wireless communication unit 222.

[0075] The first wireless communication unit 221 communicates with a base station or a server 30. The first wireless communication unit 221 performs modulation and demodulation processing and the like for transmitting and receiving signals via the antenna 211 so that the mobile terminal 20 communicates with other wireless devices.

[0076] The second wireless communication unit 222 wirelessly communicates with the mobile terminal 20. The second wireless communication unit 222 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 212 so that the mobile terminal 20 can communicate with other wireless devices.

[0077] The first wireless communication unit 221 and the second wireless communication unit 222 are communication modules including a tuner, a received signal strength indicator (RSSI) calculation circuit, a cyclic redundancy check (CRC) calculation circuit, a high-frequency circuit, etc. The first wireless communication unit 221 and the second wireless communication unit 222 perform modulation / demodulation and frequency conversion of wireless signals transmitted and received by the mobile terminal 20, and provide the received signals to the control unit 270.

[0078] The input device 23 has a touch sensitive device 231. The input device 23 has, for example, a capacitive touch panel. The input device 23 receives an input from a user when the user's finger or the like touches the touch panel. The input device 23 detects the contact position of the user's finger or the like.

[0079] The output device 24 has a display 241. The display 241 displays the processing results of the processor 27 to the user. The display 241 displays data such as images, videos, and text. The display 241 is realized by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

[0080] The microphone 251 receives a voice input and provides a voice signal corresponding to the voice input to the voice processing unit 25. The speaker 252 converts the voice signal provided by the voice processing unit 25 into voice and outputs the voice to the outside of the mobile terminal 20. The voice processing unit 25 modulates and demodulates the voice signal. The voice processing unit 25 modulates the signal provided by the microphone 251 and provides the modulated signal to the control unit 270. The voice processing unit 25 also provides the voice signal to the speaker 252. The voice processing unit 25 is realized by, for example, a processor for voice processing.

[0081] The control unit 270 reads a program 2902 stored in the storage unit 290 and executes instructions included in the program 2902 to control the operation of the mobile terminal 20. The program 2902 is application software pre-installed in the mobile terminal 20. The control unit 270 appropriately uses the processor 27, the memory 28, and the storage unit 290. The control unit 270 exerts functions as an input operation receiving unit 2701, a transmission / reception unit 2702, a data processing unit 2703, and a notification control unit 2704.

[0082] The input operation receiving unit 2701 performs processing for receiving an input operation from the user to the input device 23 .

[0083] The transmitting / receiving unit 2702 performs processing for the mobile terminal 20 to transmit and receive data to and from an external device such as the server 30 in accordance with a communication protocol. The transmitting / receiving unit 2702 controls the first wireless communication unit 221 and the second wireless communication unit 222. The transmitting / receiving unit 2702 also transmits user information including the terminal UUID 2901 to the server 30 as appropriate.

[0084] The data processing unit 2703 performs calculations on the data inputted by the mobile terminal 20 in accordance with the program 2902, and outputs the calculation results to a memory or the like.

[0085] The notification control unit 2704 performs a process of presenting information to the user. The notification control unit 2704 performs a process of displaying a display image on the display 241, a process of outputting sound from the speaker 252, and the like.

[0086] The storage unit 290 stores data and programs 2902 that are used as appropriate when the control unit 270 performs various processes. The storage unit 290 includes a volatile memory and a non-volatile memory. The storage unit 290 is, for example, a memory or a storage. The storage unit 290 stores a terminal UUID 2901, a program 2902, and a user ID 2903.

[0087] The storage unit 290 stores a terminal UUID 2901. The terminal UUID (Universally Unique Identifier) ​​2901 is identification information unique to each mobile terminal 20, which is assigned to each mobile terminal 20 in advance. The storage unit 290 also stores a program 2902. The program 2902 is application software that enables a user to receive services from the parking lot management system PS1. The storage unit 290 also stores a user ID 2903. This user ID 2903 is first user information, which will be described later. The user ID 2903 is assigned by the server 30 when the user registers.

[0088] <Functional configuration of Server 30>

[0089] Fig. 15 is a diagram showing the functional configuration of the server 30 constituting the parking lot management system PS1 of Fig. 8. As shown in Fig. 15, the server 30 has a communication unit 301, a storage unit 302, and a control unit 303. The communication unit 301 corresponds to the communication IF 36 of Fig. 11. The storage unit 302 includes the memory 38 and storage 39 of Fig. 11. The control unit 303 is composed of the processor 37, memory 38, and storage 39 of Fig. 11.

[0090] The communication unit 301 performs processing for the server 30 to communicate with external devices. The communication unit 301 performs wired or wireless communication with the parking lot barrier 10. The communication unit 301 performs wireless communication with the mobile terminal 20. The communication unit 301 performs wired or wireless communication with the management terminal 40.

[0091] The storage unit 302 is composed of, for example, a memory 38 and a storage 39. The storage unit 302 stores data and programs used by the server 30. The storage unit 302 stores a user information database (DB) 3021, a parking lot DB 3022, and a parking information DB 3023.

[0092] These user information DB 3021 and the like are databases. The database referred to here refers to a relational database, which is used to manage data sets called tables in a tabular format structurally defined by rows and columns, by associating them with each other. In a database, a table is called a table, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables can be set and associated.

[0093] Usually, a column that serves as a primary key for uniquely identifying a record is set in each table, but setting a primary key to a column is not essential. The control unit 303 can add, delete, or update records in a specific table stored in the storage unit 302.

[0094] As shown in FIG. 16, the user information DB 3021 is a database for managing data relating to users who use the parking lot management system PS1 in the second embodiment.

[0095] As shown in FIG. 17, the parking lot DB 3022 is a database for managing data relating to parking lots managed by the parking lot management system PS1 in the second embodiment.

[0096] As shown in FIG. 18, the parking information DB 3023 is a database for managing data relating to the state of the parking lot, including the entry and exit of vehicles, in the parking lot management system PS1 in the second embodiment.

[0097] The control unit 303 performs functions shown in various modules, such as a reception control module 3031, a transmission control module 3032, a user confirmation module 3033, a release permission module 3034, an operation instruction module 3035, a DB editing module 3036, a parking space selection module 3037, a parking fee calculation module 3038, and a payment transaction instruction module 3039, by the processor 37 of the server 30 performing processing according to a program. The control unit 303 may also perform other functions.

[0098] The reception control module 3031 controls the process in which the server 30 receives signals from external devices in accordance with a communication protocol. For example, the reception control module 3031 receives a terminal UUID 2901 from the mobile terminal 20. Also, for example, the reception control module 3031 receives a parking lot ID and a parking space ID from the parking lot barrier 10. The reception control module 3031 receives other signals.

[0099] The transmission control module 3032 controls the process in which the server 30 transmits signals to external devices in accordance with a communication protocol. The reception control module 3031 and the transmission control module 3032 provide the server 30 with the function of operating as a Web server for external devices including the parking lot barrier 10 and the mobile terminal 20 that have accessed via the network 80.

[0100] The user confirmation module 3033 judges whether the acquired user information matches the data in the storage unit 302. If the acquired user information matches the data in the storage unit 302, the user confirmation module 3033 notifies the release permission module 3034 that there is a match. If the acquired user information does not match the data in the storage unit 302, the user confirmation module 3033 notifies the release permission module 3034 that there is no match.

[0101] The user confirmation module 3033 judges whether the first user information acquired from the mobile terminal 20 matches the data in the user information DB 3021. Specifically, the user confirmation module 3033 collates the first user information received by the communication unit 301 of the server 30 with the user information DB 3021 in the storage unit 302. When the mobile terminal 20 requests the server 30 for permission to unlock the parking lot barrier 10, the communication unit 301 receives the user ID, terminal ID, and terminal UUID. The user confirmation module 3033 acquires the user ID, terminal ID, and terminal UUID from the communication unit 301. The user confirmation module 3033 collates the acquired user ID, terminal ID, and terminal UUID with the user ID, terminal ID, and terminal UUID stored in the user information DB 3021.

[0102] If the acquired user ID, terminal ID, and terminal UUID are included in the user ID, terminal ID, and terminal UUID stored in user information DB 3021, the release permission module 3034 is notified that the user information matches. If the acquired user ID, terminal ID, and terminal UUID are not included in the user ID, terminal ID, and terminal UUID stored in user information DB 3021, the release permission module 3034 is notified that the user information does not match.

[0103] Furthermore, the user confirmation module 3033 judges whether the second user information acquired from the parking lot barrier 10 matches the first user information of the user who has permitted the unlocking in the parking information DB 3023 or not.

[0104] Specifically, when the parking lot barrier 10 wirelessly communicates with the user's mobile terminal 20, the parking lot barrier 10 acquires second user information. The information acquired by the parking lot barrier 10 is, for example, a user ID, a terminal ID, and a terminal UUID. The parking lot barrier 10 transmits the user information to the server 30. The communication unit 301 receives the user information acquired by the parking lot barrier 10 and provides it to the user confirmation module 3033. Then, the user confirmation module 3033 compares the second user information acquired by the parking lot barrier 10 with the parking information DB3023. The parking information DB3023 contains first user information of the user who has permitted the parking lot barrier 10 to be unlocked.

[0105] The communication between the mobile terminal 20 and the parking lot barrier 10 is short-range wireless communication (e.g., Bluetooth (registered trademark)). Therefore, the mobile terminal 20 of the user is permitted to unlock the parking lot barrier 10, and is within a distance where short-range wireless communication is possible with the parking lot barrier 10.

[0106] When the second user information acquired from the parking lot barrier 10 is included in the user information of the parking information DB 3023, the first user information and the second user information match. That is, the user who requested the release permission and the user who is near the parking lot barrier 10 match.

[0107] If the first user information and the second user information match, the release status is "permitted," and a record exists that does not contain data on the time of entry, the user confirmation module 3033 notifies the operation instruction module 3035 that the user information acquired by the parking lot barrier 10 matches the user who authorized the unlocking.

[0108] If the first user information and the second user information match, the release status is "permitted," and there is no record that does not contain data on the time of entry, the user confirmation module 3033 notifies the operation instruction module 3035 that the user information acquired by the parking lot barrier 10 does not match the user who authorized the unlocking.

[0109] The first user information and the second user information include a user ID, a terminal ID, and a terminal UUID. If at least the user ID matches, the first user information and the second user information may be determined to match. If one user owns two or more mobile terminals 20, there may be cases where the terminal IDs and terminal UUIDs do not match.

[0110] The unlocking permission module 3034 receives a request from a user to unlock the parking lot barrier 10 and grants permission to the user to unlock the parking lot barrier 10.

[0111] The user confirmation module 3033 notifies the release permission module 3034 that the first user information received from the mobile terminal 20 matches the user information DB3021 stored in the storage unit 302. At this time, the release permission module 3034 grants permission to the mobile terminal 20 to release the lock on the parking lot barrier 10.

[0112] The user confirmation module 3033 notifies the release permission module 3034 that the first user information received from the mobile terminal 20 does not match the user information DB3021 stored in the storage unit 302. At this time, the release permission module 3034 does not grant permission to the mobile terminal 20 to release the lock on the parking lot barrier 10.

[0113] The operation instruction module 3035 instructs the parking lot barrier 10 to transition between the "locked state" and the "released state".

[0114] When the unlocking permission module 3034 grants permission to unlock and the first user information acquired from the mobile terminal 20 matches the second user information acquired from the parking lot barrier 10, the operation instruction module 3035 sends an unlocking instruction to the parking lot barrier 10 to lower the barrier portion 12 of the parking lot barrier 10.

[0115] Unless the unlocking permission module 3034 grants permission to unlock and the first user information obtained from the mobile terminal 20 matches the second user information obtained from the parking lot barrier 10, the operation instruction module 3035 does not send an unlocking instruction to the parking lot barrier 10 to lower the barrier portion 12 of the parking lot barrier 10.

[0116] When a sensor monitoring the parking space 1 detects that a vehicle inside the parking space 1 has left the parking space, the server 30 receives a notification to that effect. In this case, the operation instruction module 3035 transmits a lock instruction to the parking space barrier 10 to raise the barrier portion 12 of the parking space barrier 10. Here, the sensor monitoring the parking space 1 is, for example, a proximity sensor or a weight sensor.

[0117] The DB editing module 3036 edits the database in the storage unit 302 .

[0118] When the number of users of the application software increases, the DB editing module 3036 adds columns for the user ID, terminal ID, terminal UUID, and payment information to the user information DB 3021.

[0119] When the number of parking lots managed by the management system PS1 increases, the DB editing module 3036 adds records of the parking lot ID, parking space ID, parking status, release status, and barrier status to the parking lot DB 3022. Columns are added for each parking space 1.

[0120] When a request to unlock the parking lot barrier 10 is made from the user's mobile terminal 20, the DB editing module 3036 edits the parking information DB 3023. Columns for user ID, terminal ID, terminal UUID, parking lot ID, parking space ID, parking status, unlocking status, barrier status, entry time, exit time, and payment information are added. A column is added each time an unlocking request is made from the mobile terminal 20.

[0121] The DB editing module 3036 edits the user information DB 3021, the parking lot DB 3022, and the parking information DB 3023 as appropriate.

[0122] The DB editing module 3036 may move records in the parking information DB3023 for which payment has been completed to another database. This is because all procedures related to the parking of the vehicle are once completed after the payment is completed. The parking information DB3023 is in an active state from the time the server 30 receives an instruction from the user to unlock the parking information DB3023 and adds a new column to the parking information DB3023 until the payment is completed and information indicating that the payment has been completed is written to the parking information DB3023. Here, the active state is a state in which the flow executed by the management system PS1 in association with the parking of the user's vehicle has not been completed, and is a state that the management system PS1 should pay attention to when managing the parking lot. By moving inactive records to another database, the amount of data in the parking information DB3023 is reduced. For this reason, each module of the control unit 303 can quickly read the parking information DB3023.

[0123] The parking space selection module 3037 selects a parking space 1 in the parking lot where the user will park. The parking space selection module 3037 selects a parking space barrier 10 for which the operation instruction module 3035 instructs operation among the multiple parking space barriers 10 in the parking lot. The parking space selection module 3037 refers to the vacant space status in the parking lot DB 3022. The parking space selection module 3037 selects one parking space 1 from among the multiple parking spaces 1 that are "vacant."

[0124] Note that instead of the parking section selection module 3037 selecting the parking section 1, the selection of the parking section 1 by the user may be accepted.

[0125] The parking fee calculation module 3038 calculates the time from the entry time when the vehicle enters the parking space 1 to the exit time when the vehicle leaves the parking space 1 as the parking time. Here, the entry time is the time when the operation instruction module 3035 transmits an unlock instruction to the parking space barrier 10 to unlock it. The exit time is the time when the operation instruction module 3035 transmits a lock instruction to the parking space barrier 10 to lock it. The parking fee calculation module 3038 calculates the parking fee of the vehicle based on the time from the entry time to the exit time, based on a parking fee table or a parking fee calculation formula (not shown). The parking fee table or parking fee calculation formula may be different depending on at least one of the entry time and the exit time. The parking fee calculation module 3038 transmits the calculated parking fee to the payment transaction instruction module 3039.

[0126] The payment transaction instruction module 3039 settles the parking fee calculated by the parking fee calculation module 3038. The payment transaction instruction module 3039 instructs a payment system (not shown) external to the parking lot management system PS1 to perform a payment transaction under the user name. The payment information is stored in the user information DB 3021 and the parking information DB 3023. The payment transaction instruction module 3039 uses this payment information to instruct the payment system to perform a payment transaction.

[0127] <Database data structure> The storage unit 302 of the server 30 stores a user information DB 3021, a parking lot DB 3022, and a parking information DB 3023.

[0128] The user information DB3021 includes data showing information about users who use the parking lot management system PS1. In the user information DB3021, one column is basically assigned to each user. The user information DB3021 is generated when a user installs application software and creates an account for the application software. If a user registers multiple mobile terminals 20, multiple columns are assigned to each user.

[0129] The parking lot DB3022 includes data showing information about parking spaces 1 in parking lots managed by the parking lot management system PS1. In the parking lot DB3022, one column is assigned to one parking lot barrier 10. The parking lot DB3022 is updated each time a new parking lot is managed by the parking lot management system PS1.

[0130] The parking information DB 3023 includes data showing information on entry and exit managed by the parking lot management system PS1. In the parking information DB 3023, a new column is generated each time a user uses a parking lot.

[0131] FIG. 16 is a diagram illustrating an example of the data structure of the user information DB 3021 stored in the storage unit 302 of the server 30. As shown in FIG.

[0132] As shown in FIG. 16, each record of the user information DB 3021 includes an item "user ID", an item "terminal ID", an item "terminal UUID", an item "password", and an item "payment information".

[0133] The item "user ID" is information for identifying a user managed by the parking lot management system PS1.

[0134] The item "Terminal ID" is information for identifying the mobile terminal 20 managed by the parking lot management system PS1.

[0135] The item "Terminal UUID" is information indicating the terminal UUID stored in the storage unit 290 of the mobile terminal 20 identified by the item "Terminal ID".

[0136] The item "password" is information about a password preset by the user.

[0137] The item "payment information" is the payment information used by the user identified by the item "user ID." For example, this is registration information such as a credit card.

[0138] FIG. 17 is a diagram illustrating an example of the data structure of the parking lot DB 3022 stored in the storage unit 302 of the server 30. As shown in FIG.

[0139] As shown in FIG. 17, each record of the parking lot DB 3022 includes an item "parking lot ID", an item "parking space ID", an item "parking status", an item "release status", and an item "barrier status".

[0140] The item "Parking lot ID" is information for identifying a parking lot managed by the parking lot management system PS1. The item "Parking lot ID" is assigned to each of the multiple parking lots managed by the parking lot management system PS1.

[0141] The item "Parking Space ID" is information that identifies a parking space 1 in a parking lot managed by the parking lot management system PS1. The item "Parking Space ID" is assigned to each parking space 1 that belongs to multiple parking lots managed by the parking lot management system PS1.

[0142] The item "Parking status" is information that identifies whether or not a vehicle is parked in the parking space. The item "Parking status" includes "full" and "empty".

[0143] The item "Release Possibility Status" is information indicating whether the parking lot barrier 10 of parking space 1 in a parking lot managed by the parking lot management system PS1 is in a release possible state. In response to a request from a user, the server 30 gives permission to unlock the parking lot barrier 10. The item "Release Possibility Status" indicates either an "authorized state" or an "unauthorized state." The "authorized state" is a state in which the server 30 has given the user permission to operate the parking lot barrier 10 of the parking space 1. The "unauthorized state" is a state in which the server 30 has not given any user permission to operate the parking lot barrier 10 of the parking space 1.

[0144] The item "Barrier Status" is information indicating the status of the parking lot barrier 10 of the parking space 1 of the parking lot managed by the parking lot management system PS1. The item "Barrier Status" indicates either "Locked Status" or "Released Status." The "Locked Status" is a status in which the parking lot barrier 10 prevents vehicles from entering. The "Released Status" is a status in which the parking lot barrier 10 does not prevent vehicles from entering.

[0145] FIG. 18 is a diagram illustrating an example of the data structure of the parking information DB 3023 stored in the storage unit 302 of the server 30. As shown in FIG.

[0146] As shown in FIG. 18, each record in the parking information DB3023 includes the following items: "User ID", "Terminal ID", "Terminal UUID", "Parking lot ID", "Parking space ID", "Parking status", "Release status", "Barrier status", "Entry time", "Exit time", and "Payment information".

[0147] Here, the items “User ID”, “Terminal ID”, “Terminal UUID”, and “Payment Information” are the same as the items in the user information DB 3021. The items “Parking lot ID”, “Parking space ID”, “Parking status”, “Release status”, and “Barrier status” are the same as the items in the parking lot DB 3022.

[0148] The item "entry time" indicates the time when the parking lot barrier 10 of the parking space 1 in the parking lot managed by the parking lot management system PS1 became "released state." The entry time is, for example, the time when the operation instruction module 3035 sent an unlock instruction to the parking lot barrier 10 to unlock it.

[0149] The item "Exit time" indicates the time when the parking lot barrier 10 of the parking space 1 of the parking lot managed by the parking lot management system PS1 became "locked". The exit time is, for example, the time when the operation instruction module 3035 transmitted a lock instruction to the parking lot barrier 10.

[0150] <Display screen displayed on mobile terminal 20> FIG. 19 is a diagram showing an example of a screen displayed on the display 241 of the output device 24 of the mobile terminal 20 to confirm the intention to use a parking lot. The character string "Do you want to use a parking lot?" is displayed at the top of the screen. Below that, two selection acceptance displays, "Use" and "Do not use", are displayed. A map of the area around the destination is displayed at the bottom of the screen. The map shows parking lots around the destination, and indicates whether each parking lot is vacant or not. If the user taps "Use", a list of parking lots in FIG. 20 is displayed. If the user taps "Do not use", the provision of the service is discontinued.

[0151] FIG. 20 is a diagram illustrating a list of parking lots displayed on the display 241 of the output device 24 of the mobile terminal 20. A plurality of parking lots near the destination are listed at the top of the screen. A map of the area near the destination is displayed at the bottom of the screen. The user can understand the positional relationship between the destination and the parking lots by checking this map. In the list of parking lots at the top of the screen, a mark, a parking lot name, a vacant parking status, and a selection acceptance display are displayed from the left. For example, the notation P1 is a mark, the notation 1st parking lot is the parking lot name, the notation "vacant" indicates a vacant parking status, and the notation "park" indicates a selection acceptance display. The selection acceptance display is a display area on a touch panel that displays options to the user and accepts input from the user. When the user taps the display portion of "park", the control unit 270 of the mobile terminal 20 displays the screen of FIG. 21 on the display 241 of the output device 24.

[0152] FIG. 21 is a diagram illustrating a parking lot map displayed on the display 241 of the output device 24 of the mobile terminal 20. The parking lot map displays "Parking Lot No. 1," which is an example of the name of the parking lot. The parking lot map also displays parking spaces 1 in the parking lot surrounded by frames. The location corresponding to each parking space 1 is displayed with either "empty" or "full." "Empty" indicates that the parking space is empty. "Full" indicates that the parking space is full. In FIG. 21, the parking space 1 displayed as "full" is hatched. In practice, the mobile terminal 20 may display the characters "full" and "empty" in different colors on the display 241.

[0153] Fig. 22 is a diagram illustrating an example of a parking lot map selection screen displayed on the display 241 of the output device 24 of the mobile terminal 20. As shown in Fig. 22, a selection acceptance display is displayed with the character string "park".

[0154] <Initial registration> Before parking a vehicle using the parking lot management system PS1 of the second embodiment, the user performs user registration. At that time, the user downloads application software to the mobile terminal 20 and installs it on the mobile terminal 20. Then, the user creates an account. At that time, the user inputs information in the user information DB3021 shown in FIG. 16. For example, the user's name, password, and payment information. The program also transmits the terminal UUID2901 to the server 30. The server 30 issues a user ID and a terminal ID to the user. The DB editing module 3036 of the server 30 adds information about the new user to the user information DB3021. This completes the user registration. At that time, the server 30 assigns a user ID to the user. This user ID is a type of first user information. The user ID assigned by the server 30 is stored as a user ID2903 in the memory unit 290 of the mobile terminal 20.

[0155] <Operation of the parking management system PS1> Each process of the parking lot management system will be explained below. The parking lot barrier 10, the mobile terminal 20, and the server 30 communicate with each other to open and close the parking lot barrier 10. This allows the user to park in a specific parking space 1 in the parking lot and then start driving off.

[0156] Fig. 23 is a relationship diagram for explaining the relationship between the processing performed by the parking lot barrier 10, the mobile terminal 20, and the server 30. Fig. 24 is a flowchart showing the processing performed by the parking lot barrier 10, the mobile terminal 20, and the server 30.

[0157] A program 2902 for receiving parking lot services is installed in the mobile terminal 20. This program 2902 is application software that enables the user to use the parking lot.

[0158] In step S101, a login to the program 2902 is accepted from the user's mobile terminal 20. The user confirmation module 3033 of the server 30 receives a request including a user ID from the mobile terminal 20. This user ID may be input directly by the user, or the user ID 2903 stored in the storage unit 290 may be used. The user confirmation module 3033 confirms the user, for example, by the user ID and password. The user confirmation module 3033 searches the user information DB 3021 based on the user ID, and confirms whether the password is correct. If the acquired user ID and password match the information in the user information DB 3021, the user confirmation module 3033 continues to provide the service to the mobile terminal 20 of that user.

[0159] At this time, the user confirmation module 3033 may obtain license information including the expiration date of the license from the mobile terminal 20, and may check whether the current date and time is within the expiration date of the license before deciding whether to continue providing the service.

[0160] In step S102, the user requests permission to release the lock from the server 30. First, the user inputs the name of the destination facility or the address of the destination into the mobile terminal 20. Based on the input information, the server 30 causes the display 241 of the mobile terminal 20 to display, for example, the screen in FIG. 19. The user selects either "park" or "don't park." In other words, the user requests permission to release the parking lot barrier 10 from the application software of the mobile terminal 20. The server 30 receives a notification from the mobile terminal 20 that the user will be using the parking lot.

[0161] Here, the user's selection of "park" is synonymous with the user requesting permission to use the parking lot from the server 30. That is, in step S102, the user requests the server 30 to obtain permission to unlock the vehicle.

[0162] The release permission module 3034 of the server 30 causes the user confirmation module 3033 to confirm the identity of the user information. The user confirmation module 3033 acquires first user information from the storage unit 290 of the mobile terminal 20. The first user information includes a user ID, a terminal ID, and a terminal UUID. The first user information may be acquired when the user logs in. The user confirmation module 3033 collates the acquired user ID, terminal ID, and terminal UUID with data stored in the user information DB 3021 of the storage unit 302. If there is data in which the user ID, terminal ID, and terminal UUID acquired from the mobile terminal 20 match the user ID, terminal ID, and terminal UUID in the user information DB 3021, the user confirmation module 3033 notifies the release permission module 3034 that the user information matches. If there is no data that matches these, the user confirmation module 3033 notifies the release permission module 3034 that the user information does not match.

[0163] When the release permission module 3034 is notified from the user confirmation module 3033 that the user information matches, the release permission module 3034 grants permission to release the lock to that user ID. When the release permission module 3034 is notified from the user confirmation module 3033 that the user information does not match, the release permission module 3034 does not grant permission to release the lock to that user ID.

[0164] When granting permission to unlock to a user ID, specifically, the unlock permission module 3034 causes the DB editing module 3036 to update the parking information DB 3023. The DB editing module 3036 adds one column to the parking information DB 3023 of Fig. 18, and writes the user ID, terminal ID, terminal UUID, and payment information that have been granted permission to unlock based on the user information DB 3031. At this stage, the other items remain blank.

[0165] In step S103, the user selects a parking lot from among a plurality of parking lots. Upon receiving a request from the user, the parking space selection module 3037 of the server 30 receives an input of a destination name or address from the user. The user inputs a destination name or address. Here, the input address may be a representative place name.

[0166] The parking space selection module 3037 extracts parking spaces near the destination. Then, the parking space selection module 3037 refers to the parking space DB 3022 to extract whether there is an empty parking space 1. The parking space selection module 3037 also checks whether the operation state of each parking space barrier 10 in the parking space is locked or unlocked.

[0167] The parking space selection module 3037 of the server 30 displays the name of the destination, the address, and a map of the area around the representative address input by the user on the display 241 of the mobile terminal 20. For example, the screen of FIG. 20 is displayed on the display 241 of the mobile terminal 20. FIG. 20 displays a number of parking lots near the user's destination. FIG. 20 also displays the relative positions of a number of parking lots near the destination and whether they are vacant or full. A selection acceptance display of "park" is displayed on the row of a parking lot with vacant parking spaces. In addition to FIG. 20, an approximate distance from the destination may be displayed.

[0168] The mobile terminal 20 may have a GPS module. In that case, the GPS module acquires the current location. The GPS module may display the current location on the display screen of FIG.

[0169] The user checks the screen in Figure 20 and selects one of the parking lots. For example, the user taps the "Park" display area on the row of the first parking lot.

[0170] The parking space selection module 3037 displays the parking lot map shown in Fig. 21 on the display 241 of the mobile terminal 20. The user taps the selection acceptance display of the parking space 1 that is displayed as "empty". The parking space selection module 3037 accepts the selection from the user. The parking space selection module 3037 changes the display portion of the parking space 1 selected by the user from "empty" to "full".

[0171] The DB editing module 3036 changes the release possibility status of the parking lot DB 3022 in Fig. 17 to yes. When the release possibility status of the parking lot DB 3022 is yes, it indicates that the parking space 1 corresponding to that parking space ID has a parking plan from the user. Therefore, when the release possibility status is yes, it is sufficient to display "full" in Fig. 21 etc.

[0172] In step S104, the user issues an instruction to park the vehicle using the mobile terminal 20. At this time, the user and the vehicle are in the selected first parking lot. The parking space selection module 3037 displays a selection acceptance display of "park" as shown in Fig. 22. The user taps the selection acceptance display of "park".

[0173] The processor 27 of the mobile terminal 20 transmits to the server 30 that the selection acceptance display of "park" has been tapped. This is an unlock instruction. The communication unit 301 of the server 30 receives the unlock instruction.

[0174] In step S105, the second wireless communication unit 222 of the mobile terminal 20 wirelessly communicates with the wireless communication unit 162 of the parking lot barrier 10. This wireless communication is, for example, short-range communication such as Bluetooth (registered trademark). The mobile terminal 20 transmits a user ID, a terminal ID, and a terminal UUID to the parking lot barrier 10.

[0175] The communication between the mobile terminal 20 and the parking lot barrier 10 is short-range wireless communication. When the parking lot barrier 10 acquires user information such as a user ID from the mobile terminal 20, this means that the distance between the mobile terminal 20 of the user and the parking lot barrier 10 is short.

[0176] The server communication unit 161 of the parking lot barrier 10 transmits to the server 30 the user ID, terminal ID, and terminal UUID received from the mobile terminal 20, as well as the parking lot ID and parking space ID stored in the memory unit 19 of the parking lot barrier 10.

[0177] In this manner, the wireless communication unit 162 of the parking lot barrier 10 receives, via wireless communication, the second user information relating to the user from the mobile terminal 20. The parking lot barrier 10 transmits the second user information to the external server 30 before the step of accepting an unlock instruction.

[0178] In step S106, the user verification module 3033 of the server 30 verifies that the first user information of the user who requested unlocking permission from the mobile terminal 20 matches the second user information obtained via the parking lot barrier 10.

[0179] First, the communication unit 301 of the server 30 receives the second user information from the mobile terminal 20. The user confirmation module 3033 searches the parking information DB 3023 to confirm whether the user ID acquired via the parking lot barrier 10 is included in the parking information DB 3023. For example, it searches for a column where the user ID matches and where the entry time is not included.

[0180] If the user IDs match and there is a column that does not contain the entry time, the user confirmation module 3033 notifies the operation instruction module 3035 that the user IDs match.

[0181] If the user IDs match and there is no column that does not contain the entry time, the user confirmation module 3033 notifies the operation instruction module 3035 that the user IDs do not match.

[0182] In this manner, the communication unit 301 of the server 30 receives the second user information from the parking lot barrier 10. The user verification module 3033 of the server 30 compares the first user information with the second user information to verify whether there is at least one matching piece of information for the corresponding items.

[0183] In step S107, when the operation instruction module 3035 receives a notification that the user information matches, the operation instruction module 3035 of the server 30 sends an unlock instruction to the parking lot barrier 10 to unlock it. When the parking lot barrier 10 receives the unlock instruction, the motor control unit 173 of the parking lot barrier 10 operates the motor 14. As a result, the parking lot barrier 10 lowers the barrier unit 12. In other words, the parking lot barrier 10 transitions from a locked state to an unlocked state. At this stage, the user can park the vehicle in the parking space 1.

[0184] It should be noted that when the operation instruction module 3035 receives a notification that the user information does not match, the operation instruction module 3035 of the server 30 does not transmit an unlock instruction to the parking lot barrier 10. In this case, the operation instruction module 3035 may instruct the mobile terminal 20 to transmit some kind of error message.

[0185] In this way, in step S107, when the operation state of the parking lot barrier 10 is the locked state, the control unit 303 of the server 30 receives an unlock instruction from the outside via wireless communication to transition the operation state of the parking lot barrier 10 from the locked state to the unlocked state. Then, upon receiving the unlock instruction, the motor control unit 173 of the parking lot barrier 10 transitions the operation state from the locked state to the unlocked state. In this way, the operation instruction module 3035 of the server 30 transmits an unlock instruction to the parking lot barrier 10 when matching information exists for the corresponding item.

[0186] In step S108, the DB editing module 3036 of the server 30 writes the time when the operation instruction module 3035 sent the unlock instruction to unlock the parking lot barrier 10 as the entry time in the parking information DB 3023. In addition, the parking fee calculation module 3038 specifies the entry time as the parking start time.

[0187] The DB editing module 3036 changes the barrier status item in the parking information DB 3023 from "locked" to "released."

[0188] In addition, when the motor control unit 173 of the parking lot barrier 10 has normally finished operating the motor 14, the server communication unit 161 of the parking lot barrier 10 may notify the server 30 that the barrier unit 12 has been lowered.

[0189] In step S109, various sensors in the parking space 1 confirm that the user has parked the vehicle in the parking space 1. From this stage, the vehicle is parked in the parking space 1. The user is then able to start the vehicle at any time.

[0190] In step S110, the user starts the vehicle from the parking space 1. At this time, various sensors in the parking space 1 detect that the vehicle has started from the parking space 1. The various sensors then transmit to the server 30 that the vehicle has started. Note that since payment can be made on the application software, the user does not need to carry out payment processing before starting the vehicle.

[0191] Additionally, various sensors may notify the parking lot barrier 10 that the vehicle has left the parking space 1 .

[0192] In step S111, the operation instruction module 3035 of the server 30 receives a notification that the vehicle in the parking space 1 has started. The operation instruction module 3035 transmits a lock instruction to the parking lot barrier 10 to lock it. The motor control unit 173 of the parking lot barrier 10 drives the motor 14. The parking lot barrier 10 raises the barrier unit 12 to its original position. This prevents other drivers from parking their vehicles in the parking space 1 without unlocking it using the mobile terminal 20.

[0193] The DB editing module 3036 writes the time when the operation instruction module 3035 sent an instruction to lock the parking lot barrier 10 into the parking information DB 3023 as the departure time.

[0194] In addition, the DB editing module 3036 changes the release possibility status of the parking lot DB 3022 to "no", changes the barrier status to "locked", and changes the parking status to "vacant".

[0195] Thus, in step S111, when the operation state of the parking lot barrier 10 is the released state, the control unit 303 of the server 30 receives a lock instruction from the outside via wireless communication to transition the operation state of the parking lot barrier 10 from the released state to the locked state. Then, when the motor control unit 173 of the parking lot barrier 10 receives the lock instruction, it transitions the operation state of the parking lot barrier 10 from the released state to the locked state.

[0196] In step S112, the parking fee calculation module 3038 of the server 30 calculates the parking fee. The parking fee calculation module 3038 calculates the parking fee based on the entry time and exit time in the parking information DB 3023 and a fee table or a parking fee calculation formula.

[0197] In step S113, the payment transaction instruction module 3039 of the server 30 instructs the settlement of the parking fee calculated by the parking fee calculation module 3038. The payment transaction instruction module 3039 instructs a payment system (not shown) outside the parking lot management system PS1 to perform a payment transaction under the user name. Since the payment information is stored in the user information DB 3021, the payment transaction instruction module 3039 uses this payment information to instruct the payment system to perform a payment transaction.

[0198] Data for which payment has already been completed will not be used thereafter. For this reason, the DB editing module 3036 may transfer records for which payment has already been completed from the parking information DB 3023 to another database. This is because the time required to read the parking information DB 3023 is shortened, and the processing of the server 30 becomes faster.

[0199] Thus, the parking lot management system PS1 in the second embodiment is a system for managing a parking lot having parking lot barriers 10 arranged in each of a plurality of parking spaces 1, a server 30 capable of communication, and a mobile terminal 20 capable of communication. The parking lot barrier 10 has at least two operating states: a locked state that prevents a vehicle from entering the parking space 1, and an unlocked state that does not prevent a vehicle from entering the parking space 1. The server 30 has a processor 37. The mobile terminal 20 has a processor 27. The parking lot barrier 10 has a processor 17. The processor 27 of the mobile terminal 20 executes a step of transmitting first user information about a user to the server 30, and a step of requesting permission to transition the operating state of the parking lot barrier 10 from the locked state to the unlocked state. The processor 37 of the server 30 executes the steps of receiving first user information from the mobile terminal 20, granting permission to a request for permission to transition the operation state of the parking lot barrier 10 from a locked state to an unlocked state, confirming that the operation state of the parking lot barrier 10 is a locked state, and transmitting an unlock instruction to the parking lot barrier 10 to transition the operation state of the parking lot barrier 10 from the locked state to the unlocked state. The processor 17 of the parking lot barrier 10 executes the steps of accepting the unlock instruction, and transitioning the operation state of the parking lot barrier 10 from the locked state to the unlocked state when the unlock instruction is accepted.

[0200] <Advantages of the second embodiment> In this way, when the parking lot barrier 10 receives a lock instruction, the server 30 calculates the parking fee and settles the parking fee after executing the step of transitioning the operation state of the parking lot barrier 10 from the released state to the locked state. Therefore, the user can easily park the vehicle in the parking lot using the application software and easily settle the payment.

[0201] <Modification> <Parking space 1 sensor> <Weight sensor> As shown in Fig. 25, weight sensors 141 may be placed in the four corner areas inside the parking space 1. The weight sensor 141 may be placed in at least one of the areas where the four tires of the vehicle come into contact with the parking space 1. In other words, it is sufficient that only one weight sensor 141 is placed in Fig. 25. The weight sensor 141 can communicate with the parking lot barrier 10 or the server 30 by wired or wireless communication. The weight sensor 141 can notify the parking lot barrier 10 or the server 30 of the presence or absence of a vehicle.

[0202] The parking lot has a weight sensor 141 arranged within the area of ​​the parking space 1. The server 30 or the parking lot barrier 10 determines that the parking space 1 is full when the weight detected by the weight sensor is equal to or greater than a predetermined threshold, and determines that the parking space 1 is in a state other than full when the weight detected by the weight sensor is less than the predetermined threshold.

[0203] <Beacon> A beacon may be used as a sensor to detect the presence or absence of a vehicle inside the parking space 1.

[0204] <Radar sensor> A radar sensor may be used as a sensor for detecting the presence or absence of a vehicle inside the parking space 1.

[0205] <Lock Instruction from Mobile Terminal 20> The management system PS1 may receive an instruction to lock the parking lot barrier 10 from the mobile terminal 20. In this case, the control unit 270 of the mobile terminal 20 receives a lock instruction to transition the operation state of the parking lot barrier 10 from the release state to the lock state when the operation state of the parking lot barrier 10 is in the release state. Then, the control unit 270 transmits the lock instruction to the parking lot barrier 10. The control unit 170 of the parking lot barrier 10 receives the lock instruction. When the control unit 170 receives the lock instruction, the control unit 170 transitions the operation state of the parking lot barrier 10 from the release state to the lock state. The control unit 170 of the parking lot barrier 10 transmits to the server 30 that the operation state of the parking lot barrier 10 has transitioned from the release state to the lock state. The control unit 303 of the server 30 receives that the operation state of the parking lot barrier 10 has transitioned from the release state to the lock state. The DB editing module 3036 edits the parking lot DB 3022 and the parking information DB 3023.

[0206] <Lighting of the barrier section 12> As shown in FIG. 26, the barrier unit 12 may have an LED 121. The LED 121 is a lighting unit. In this case, the control unit 170 has a lighting control unit 175. After the parking lot barrier 10 receives an unlocking instruction, the processor 17 of the parking lot barrier 10 turns on the LED 121. This allows the user to easily identify the parking space 1 in which to park the vehicle. This is particularly effective at night.

[0207] <Display the parking lot address> The mobile terminal 20 may display on the display 241 the address of the parking lot selected by the user.

[0208] <Parking lot address transfer> The mobile terminal 20 or the server 30 may transfer the address of the parking lot selected by the user to the car navigation system of the vehicle.

[0209] <Type of wireless communication> The wireless communication performed by the mobile terminal 20 includes Bluetooth (registered trademark), WiFi, and LoRaWAN. The wireless communication performed by the mobile terminal 20 may be other than the above.

[0210] <Lock status> In the second embodiment, the state in which the barrier portion 12 is raised is the locked state, and the state in which the barrier portion 12 is lowered is the released state. However, a barrier other than the parking lot barrier 10 may be used. In that case, regardless of whether the barrier is raised or lowered, the locked state is a state in which a vehicle cannot enter the parking space 1, and the released state is a state in which a vehicle can enter the parking space 1.

[0211] <Third embodiment> A third embodiment will now be described. In the third embodiment, the user can reserve a parking space by inputting information into the mobile terminal 20.

[0212] <Parking lot DB3022> FIG. 27 is a diagram illustrating an example of the data structure of the parking lot DB3022 in the third embodiment. In the parking lot DB3022 in FIG. 27, the item "Parking status" indicates the parking status of the parking space 1. The parking status is either "Full status", "Vacant status", or "Reserved status". The full status is a status in which a vehicle is parked. The vacant status is a status in which no vehicle is parked and no reservation has been made. The reserved status is a status in which no vehicle is parked and a reservation has been made. The parking status may include a "maintenance status" in some cases.

[0213] <Parking information DB3023 when reservations are made> 28 is a diagram illustrating an example of the data structure of the parking information DB 3023 in the third embodiment. Each record of the reservation DB includes an item "user ID", an item "terminal ID", an item "terminal UUID", an item "parking lot ID", an item "parking space ID", an item "parking status", an item "release status", an item "barrier status", an item "reception time", an item "reservation time", an item "entry time", an item "exit time", and an item "payment information".

[0214] Here, the item "reception time" is the time when the server 30 accepts the user's reservation for the parking lot from the mobile terminal 20. The item "reservation time" is the time when the user plans to enter the parking lot. The item "reservation time" is input by the user.

[0215] <Display screen> Fig. 29 is a diagram illustrating an example of a reservation screen displayed on the display 241 of the mobile terminal 20. As will be described later, when a user selects a parking space 1 in a parking lot, a screen such as that shown in Fig. 29 is displayed on the display 241 of the mobile terminal 20.

[0216] The server 30 transmits the parking lot map to the mobile device 20, and displays the characters "Full," "Vacant," and "Pre-arranged" in the area of ​​the parking lot map that corresponds to parking space 1. Here, the character "Full" indicates that the parking space 1 is in a parked state. The character "Vacant" indicates that the parking space 1 is in an empty state. The character "Pre-arranged" indicates that the parking space 1 is in a reserved state. Of these characters, the user can only park a vehicle in a parking space 1 that has the character "Vacant" displayed.

[0217] Of course, instead of the above, character strings such as "Full", "Vacant", and "Reserved" may be displayed.

[0218] <Operation of the parking management system PS1> Each process of the parking lot management system will be explained below. The parking lot barrier 10, the mobile terminal 20, and the server 30 communicate with each other to open and close the parking lot barrier 10. This allows the user to park in a specific parking space 1 in the parking lot and then start driving off.

[0219] Fig. 30 is a first flowchart showing the processing performed by the parking lot barrier 10, the mobile terminal 20, and the server 30 when a user makes a reservation for a parking lot. Fig. 31 is a second flowchart showing the processing performed by the parking lot barrier 10, the mobile terminal 20, and the server 30 when a user makes a reservation for a parking lot.

[0220] Steps S201 to S203 in FIG. 30 are basically the same as steps S101 to S103 in FIG.

[0221] Steps S207 to S216 in FIGS. 30 and 31 are basically the same as steps S104 to S113 in FIG.

[0222] In step S201, the user logs into an account, similar to step S101.

[0223] In step S202, the user obtains permission to release the lock, similarly to step S102.

[0224] In step S203, the user determines a parking lot in the same manner as in step S103.

[0225] In step S204, the parking space selection module 3037 of the server 30 refers to the parking DB 3022 in Fig. 27 to search for a parking space ID whose parking status is "vacant". The parking space selection module 3037 extracts the parking status of each parking space 1.

[0226] In step S205, the user selects and reserves a parking space 1. First, the parking space selection module 3037 transmits the parking status of each parking space 1 in the parking lot to the mobile terminal 20. The control unit 270 of the mobile terminal 20 displays a display screen as shown in FIG.

[0227] The user selects a parking space 1 that is "vacant" from the parking lot map presented to him. The input operation reception unit 2701 of the mobile terminal 20 receives input from the user. The transmission / reception unit 2702 of the mobile terminal 20 transmits information on the selected parking space 1 to the server 30.

[0228] The DB editing module 3036 edits the parking DB 3022 of Fig. 27. The DB editing module 3036 changes the item "parking status" of the reserved parking space ID in the parking DB 3022 from "vacant" to "reserved."

[0229] The DB editing module 3036 edits the parking information DB 3023 of Fig. 28. At this time, the release possibility status of the reserved parking space 1 is "Yes", and the barrier status is "Locked". The DB editing module 3036 writes the time into the reception time and reservation time.

[0230] In step S206, after the DB editing module 3036 edits the parking lot DB 3022, the operation instruction module 3035 checks the parking lot DB 3022. The operation instruction module 3035 extracts the parking space ID that is newly reserved. The operation instruction module 3035 keeps the parking lot barrier 10 of that parking space ID in a locked state until the user issues an entry instruction in step S207.

[0231] In step S207, the user issues a storage instruction in the same manner as in step S104.

[0232] In step S208, similarly to step S105, the mobile terminal 20 and the parking lot barrier 10 communicate wirelessly.

[0233] In step S209, similarly to step S106, it is confirmed whether the user identified by the first user information and the user identified by the second user information match.

[0234] In step S210, the barrier portion 12 of the parking lot barrier 10 is lowered in the same manner as in step S107.

[0235] In step S211, measurement of the parking time starts in the same manner as in step S108.

[0236] In step S212, the entrance of the vehicle is detected in the same manner as in step S109.

[0237] In step S213, the departure of the vehicle from the garage is detected in the same manner as in step S110.

[0238] In step S214, similarly to step S111, the barrier portion 12 of the parking lot barrier 10 is raised to its original position. At this time, a lock instruction to return the parking lot barrier 10 to the locked state may be transmitted by the mobile terminal 20 or may be transmitted by the server 30. Also, the server 30 may relay the lock instruction from the mobile terminal 20 and transmit it to the parking lot barrier 10.

[0239] In step S215, the parking fee is calculated in the same manner as in step S112. The parking fee calculation module 3038 may also calculate the reservation fee from the time elapsed from the time of reception to the time the vehicle enters the parking space. In this case, the total amount of the parking fee and the reservation fee is the amount to be charged.

[0240] In step S216, the parking fee is settled in the same manner as in step S113. At this time, the total amount of the parking fee and the reservation fee is the amount charged. The reservation fee may also be set to be free.

[0241] In this way, in the parking lot management system PS1 of the third embodiment, the processor 27 of the mobile terminal 20 executes the steps of accepting the selection of one parking lot from a plurality of parking lots, accepting the input of a reservation time indicating the plan to enter the parking lot, and transmitting the selected parking lot, the reservation time, and the reception time at which the input of the reservation time was accepted to the server. The processor 37 of the server 30 executes the steps of receiving the parking lot, the reservation time, and the reception time, confirming whether the parking status of each parking barrier of the parking lot is a full state where a vehicle is parked, an empty state where a vehicle is not parked, or a reserved state where a reservation for parking of a vehicle has been made, and transmitting information on the parking status of each parking section of the parking lot to the mobile terminal. The processor 27 of the mobile terminal 20 executes the steps of receiving information on the parking status of each parking section of the parking lot, outputting information on the parking status of each parking section of the parking lot, accepting the selection of one empty parking section, and transmitting information on the selected parking section to the server. The processor 37 of the server 30 executes the steps of receiving information on the selected parking space and issuing an instruction to maintain the locked state of the parking space barrier of the selected parking space during the period from the reception time to the step of transmitting an unlock instruction to the parking space barrier.

[0242] <Modification> <Cancellation of reservation> When a predetermined time has elapsed since the reserved time and an unlocking instruction has not been received from the mobile terminal, the server 30 may execute a step of canceling the reservation of the parking space and determining that the parking space is vacant. The predetermined time may be, for example, 30 minutes or 1 hour. In this case, if the user does not enter the parking space, the management system PS1 may cancel the reservation of the parking space.

[0243] <Change reservation time> Before the reservation time has elapsed, the mobile terminal 20 may accept a change to the reservation time from the mobile terminal 20. In this case, the DB editing module 3036 changes the reservation time in the parking information DB 3023.

[0244] <Determining whether a vehicle is vacant> The control unit 303 of the server 30 may designate one of the parking lot barriers 10 that is in a locked state, instruct the parking lot barrier 10 to unlock, and when it is confirmed that the parking lot barrier 10 has been locked again, it may determine that the parking space 1 equipped with that parking lot barrier 10 is in an empty state.

[0245] <When specifying parking space 1 to be reserved by management system PS1> The management system PS1 may specify the parking space 1 where the user parks. In this case, the control unit 270 of the mobile terminal 20 executes the steps of accepting the selection of one parking space from a plurality of parking spaces, accepting the input of a reservation time indicating the plan to enter the parking space, and transmitting the selected parking space, the reservation time, and the reception time at which the input of the reservation time was accepted to the server 30. The control unit 303 of the server 30 executes the steps of receiving the parking space, the reservation time, and the reception time, confirming for each parking space barrier 10 of the parking space whether the parking state is a full state where a vehicle is parked, an empty state where a vehicle is not parked, or a reserved state where a reservation has been made for parking the vehicle, specifying one parking space 1 that is in an empty state, and issuing an instruction to maintain the lock state of the parking space barrier 10 of the specified parking space 1 during the period from the reception time to the step of transmitting an unlock instruction to the parking space barrier 10.

[0246] <Additional Notes> The matters described in the above embodiments will be supplemented below. (Appendix 1) The parking barrier (10) is remotely controlled using wireless communication from another device to adjust its position to prevent or allow entry to or exit from a parking space. (Appendix 2) The parking barrier (10) can connect to a cloud server, display current status and change physical orientation remotely. (Appendix 3) A parking lot barrier (10) is placed in a parking space (1) in a parking lot, the parking lot barrier (10) having at least two operational states: a locked state that prevents a vehicle from entering the parking space (1), and an unlocked state that does not prevent a vehicle from entering the parking space (1). The parking lot barrier (10) has a processor (17), which causes the parking lot barrier (10) to execute the following steps: when the parking lot barrier (10) is in a locked state, receiving an unlock instruction from outside via wireless communication to transition the operation state of the parking lot barrier (10) from the locked state to the unlocked state; and, upon receiving the unlock instruction, transitioning the operation state from the locked state to the unlocked state. (Appendix 4) The processor (17) further causes the parking lot barrier (10) to execute the steps of receiving a lock instruction from the outside via wireless communication when the parking lot barrier (10) is in a released state, for transitioning the operation state of the parking lot barrier (10) from the released state to a locked state, and transitioning the operation state from the released state to the locked state when the lock instruction is received. (Appendix 5) The processor (17) further causes the parking lot barrier (10) to execute a step of receiving user information about the user from the mobile terminal (20) via wireless communication, and a step of transmitting the user information to the outside before the step of accepting an unlock instruction. (Appendix 6) The parking lot management system includes a parking lot barrier (10) arranged in each of a plurality of parking spaces (1), a server (30), and a mobile terminal (20), and the parking lot barrier (10), the server (30), and the mobile terminal (20) are capable of communicating with each other, and the parking lot barrier (10) has at least two operating states of a locked state that prevents a vehicle from entering the parking space and an unlocked state that does not prevent a vehicle from entering the parking space, the server (30) has a first processor (37), the mobile terminal (20) has a second processor (27), the parking lot barrier (10) has a third processor (17), and the second processor (27) transmits to the mobile terminal (20) a first user information relating to a user to the server, and a step of setting the operating state of the parking lot barrier (10) to a locked state. the first processor (37) causes the server (30) to execute a step of receiving first user information from the mobile terminal (20), a step of granting permission in response to the request for permission to transition the operation state of the parking lot barrier (10) from the locked state to the unlocked state, a step of confirming that the operation state of the parking lot barrier (10) is the locked state, and a step of sending an unlock instruction to the parking lot barrier to transition the operation state of the parking lot barrier (10) from the locked state to the unlocked state; and the third processor (17) causes the parking lot barrier (10) to execute a step of receiving the unlock instruction, and a step of transitioning the operation state of the parking lot barrier (10) from the locked state to the unlocked state when the unlock instruction is received. (Appendix 7) The third processor (17) further causes the parking lot barrier (10) to execute the steps of receiving a lock instruction from the outside via wireless communication when the parking lot barrier (10) is in a released state, for transitioning the operation state of the parking lot barrier (10) from the released state to a locked state, and transitioning the operation state from the released state to the locked state when the lock instruction is received. (Appendix 8) The second processor (27) further causes the mobile terminal (20) to execute the steps of receiving a lock instruction for transitioning the operation state of the parking lot barrier (10) from the released state to the locked state when the operation state of the parking lot barrier (10) is in the released state, and transmitting the lock instruction to the parking lot barrier; the third processor (17) further causes the parking lot barrier (10) to execute the steps of receiving a lock instruction, transitioning the operation state from the released state to the locked state when the lock instruction is received, and transmitting to the server (30) information that the operation state has transitioned from the released state to the locked state; and the first processor (37) further causes the server (30) to execute the step of receiving information that the operation state has transitioned from the released state to the locked state. (Appendix 9) The third processor (17) further causes the parking lot barrier (10) to execute the steps of receiving second user information including information about the user from the mobile terminal (20) and transmitting the second user information to the server (30), and the first processor (37) further causes the server (30) to execute the steps of receiving the second user information from the parking lot barrier (10), comparing the first user information with the second user information to confirm whether or not there is at least one matching information for the corresponding items, and transmitting an unlock instruction to the parking lot barrier if there is matching information for the corresponding items. (Appendix 10) The second processor (27) further causes the mobile terminal (20) to execute the steps of accepting selection of one parking lot from a plurality of parking lots, accepting input of a reservation time indicating the planned entry of the vehicle into the parking lot, and transmitting the selected parking lot, the reservation time, and the reception time at which the input of the reservation time was accepted to the server. The first processor (37) further causes the server (30) to execute the steps of receiving the parking lot, the reservation time, and the reception time, confirming, for each parking lot barrier (10) of the parking lot, whether the parking status is a full state in which a vehicle is parked, an vacant state in which a vehicle is not parked, or a reserved state in which a reservation has been made for parking the vehicle, a designating one parking space (1) that is in an vacant state, and a designating step of issuing an instruction to maintain the locked state of the parking lot barrier (10) of the designated parking space during the period from the reception time to the step of transmitting an unlock instruction to the parking lot barrier (10). (Appendix 11) The second processor (27) further causes the mobile terminal (20) to execute the steps of accepting selection of one parking lot from a plurality of parking lots, accepting input of a reservation time indicating a plan to park the vehicle in the parking lot, and transmitting to the server (30) the selected parking lot, the reservation time, and the reception time at which the input of the reservation time was accepted. The first processor (37) further causes the server (30) to receive the parking lot, the reservation time, and the reception time, and to confirm whether the parking status of each parking lot barrier (10) in the parking lot is one of a full state in which a vehicle is parked, an empty state in which a vehicle is not parked, or a reserved state in which a reservation for parking of a vehicle has been made, and to transmit information on the parking status for each parking space (1) in the parking lot to the mobile terminal (20). The second processor (27) further causes the mobile terminal (20) to execute the steps of receiving information on the parking status for each parking space (1) in the parking lot, outputting information on the parking status for each parking space (1) in the parking lot, accepting the selection of one vacant parking space (1), and sending information on the selected parking space (1) to the server (30), and the first processor (37) further causes the server (30) to execute the steps of receiving the information on the selected parking space (1) and issuing an instruction to maintain the locked state of the parking space barrier (10) of the selected parking space (1) during the period from the acceptance time until the step of sending an unlock instruction to the parking space barrier (10). (Appendix 12) The first processor (37) further causes the server (30) to execute a step of designating one of the parking lot barriers (10) that is in a locked state, instructing the parking lot barrier (10) to unlock, and, if it is confirmed that the parking lot barrier (10) is again in a locked state, determining that the parking space (1) equipped with the parking lot barrier (10) is in an empty state. (Appendix 13) The first processor (37) further causes the server (30) to execute a step of designating one of the parking lot barriers (10) that is in a locked state, instructing the parking lot barrier (10) to unlock, and, if it is confirmed that the parking lot barrier (10) is again in a locked state, determining that the parking space (1) equipped with the parking lot barrier (10) is in an empty state. (Appendix 14) The first processor (37) further instructs the server (30) to calculate a reservation fee based on the elapsed time from the reception time to the entry time of the vehicle into the parking space (1); Execute the command. (Appendix 15) The first processor (37) further causes the server (30) to execute a step of calculating a reservation fee from the elapsed time from the reception time to the entry time when the vehicle is parked in the parking space (1). (Appendix 16) The first processor (37) further causes the server (30) to execute a step of canceling the reservation status of the parking space (1) and determining that the parking space (1) is vacant when a predetermined time has elapsed since the reserved time and an instruction to unlock the parking space has not been received from the mobile terminal. (Appendix 17) The first processor (37) further causes the server (30) to execute a step of canceling the reservation status of the parking space (1) and determining that the parking space (1) is vacant when a predetermined time has elapsed since the reserved time and an instruction to unlock the parking space has not been received from the mobile terminal (20). (Appendix 18) The system (PS1) further has a weight sensor arranged within the area of ​​the parking space (1), and the first processor (37) or the third processor (17) further causes the server (30) or the parking lot barrier (10) to execute a step of determining that the parking space (1) is full when the weight detected by the weight sensor is equal to or greater than a predetermined threshold, and determining that the parking space (1) is in a state other than full when the weight detected by the weight sensor is less than the predetermined threshold. (Appendix 19) The parking lot barrier (10) has a lighting unit, and the third processor further causes the parking lot barrier (10) to execute a step of lighting the lighting unit after receiving an unlock instruction. (Appendix 20) The third processor (17) further causes the parking lot barrier (10) to execute a step of transitioning the operating state from an unlocked state to a locked state when a lock instruction is received, and then the first processor further causes the server (30) to execute a step of calculating a parking fee and a step of settling the parking fee. (Appendix 21) The third processor (17) further causes the parking lot barrier (10) to execute a step of transitioning the operating state from an unlocked state to a locked state when a lock instruction is received, and then the first processor (37) further causes the server (30) to execute a step of calculating a parking fee and a step of settling the parking fee. (Appendix 22) The parking lot management program includes a parking lot barrier (10) arranged in each of a plurality of parking spaces (1), a server (30), and a mobile terminal (20), and the parking lot barrier (10), the server (30), and the mobile terminal (20) are capable of communicating with each other, and the parking lot barrier (10) has at least two operating states, a locked state in which a vehicle is prevented from entering the parking space (1), and an unlocked state in which a vehicle is not prevented from entering the parking space (1), the server (30) has a first processor (37), the mobile terminal (20) has a second processor (27), and the parking lot barrier (10) has a third processor (17), and the second processor (27) controls the mobile terminal (20) to transmit first user information about a user to the server (30), and to control the operation of the parking lot barrier (10). The first processor (37) causes the server (30) to execute a step of receiving first user information about the user from the mobile terminal (20), a step of granting permission in response to the request for permission to transition the operation state of the parking lot barrier (10) from the locked state to the unlocked state, a step of confirming that the operation state of the parking lot barrier (10) is a locked state, and a step of sending an unlock instruction to the parking lot barrier (10) to transition the operation state of the parking lot barrier (10) from the locked state to the unlocked state, and the third processor (17) causes the parking lot barrier (10) to execute a step of receiving the unlock instruction, and a step of transitioning the operation state of the parking lot barrier (10) from the locked state to the unlocked state. [Explanation of symbols]

[0247] PS1 management system, 10 parking barriers, 20 mobile terminals, 30 servers, 40 management terminals

Claims

1. remotely controlling the vehicle using wireless communication from another device to adjust its position to prevent or allow entry into or exit from a parking space; Parking lot barrier.

2. Connect to the cloud server Shows the current status, It is possible to change the physical orientation remotely. Parking lot barrier.

3. A parking barrier disposed in a parking space of a parking lot, The parking lot barrier comprises: a locked state that prevents a vehicle from entering the parking space; a release state in which the vehicle is not prevented from entering the parking space; the parking barrier has a processor; The processor may include: receiving, from an external device via wireless communication, an unlock instruction to transition the operation state of the parking lot barrier from the locked state to the unlocked state when the operation state of the parking lot barrier is the locked state; transitioning the operating state from the locked state to the unlocked state when the unlock instruction is received; Parking lot barrier that allows you to

4. The processor may further configure the parking barrier to: receiving, from an external device via wireless communication, a lock instruction to transition the operation state of the parking lot barrier from the release state to the lock state when the operation state of the parking lot barrier is the release state; transitioning the operating state from the released state to the locked state when the lock instruction is received; 4. The parking lot barrier according to claim 3, wherein the barrier is configured to:

5. The processor may further configure the parking barrier to: receiving user information about the user from the mobile terminal via wireless communication; a step of transmitting the user information to an external device before the step of receiving the unlock instruction; 4. The parking lot barrier according to claim 3, wherein the barrier is configured to:

6. A parking lot management system comprising parking lot barriers arranged in each of a plurality of parking spaces, a server, and a mobile terminal, wherein the parking lot barriers, the server, and the mobile terminal are capable of communicating with each other; The parking lot barrier comprises: a locked state that prevents a vehicle from entering the parking space; a release state in which the vehicle is not prevented from entering the parking space; The server a first processor; The mobile terminal a second processor; The parking lot barrier comprises: a third processor; The second processor causes the mobile terminal to sending first user information about a user to the server; requesting permission to transition the operational state of the parking lot barrier from the locked state to the unlocked state; Execute The first processor instructs the server to: receiving the first user information from the mobile terminal; granting permission to a request for permission to transition the operational state of the parking lot barrier from the locked state to the unlocked state; confirming that the operational state of the parking lot barrier is the locked state; transmitting an unlock instruction to the parking lot barrier to transition the operational state of the parking lot barrier from the locked state to the unlocked state; Execute The third processor may be configured to: receiving the unlock instruction; When the unlock instruction is received, the operation state of the parking lot barrier is changed from the locked state to the unlocked state. A system that executes the following.

7. The third processor further configures the parking barrier to: receiving, from an external device via wireless communication, a lock instruction to transition the operation state of the parking lot barrier from the release state to the lock state when the operation state of the parking lot barrier is the release state; transitioning the operating state from the released state to the locked state when the lock instruction is received; The system of claim 6 , wherein the system executes the following:

8. The second processor further configures the mobile terminal to: receiving a lock instruction to transition the operation state of the parking lot barrier from the release state to the lock state when the operation state of the parking lot barrier is in the release state; transmitting the locking instruction to the parking lot barrier; Execute The third processor further configures the parking barrier to: receiving the lock indication; transitioning the operating state from the released state to the locked state when the lock instruction is received; transmitting to the server that the operational state has transitioned from the unlocked state to the locked state; Execute The first processor further instructs the server to: receiving a transition of the operational state from the unlocked state to the locked state; The system of claim 6 , wherein the system executes the following:

9. The third processor further configures the parking barrier to: receiving second user information from the mobile terminal, the second user information including information about the user; sending the second user information to the server; Execute The first processor further instructs the server to: receiving the second user information from the parking barrier; comparing the first user information with the second user information to determine whether there is at least one matching piece of information for a corresponding item; If there is a match for the corresponding item, transmitting the unlock instruction to the parking lot barrier; The system of claim 6 , wherein the system executes the following:

10. The second processor further configures the mobile terminal to: accepting a selection of one of a plurality of parking lots; receiving an input of a reservation time indicating a planned entry time for the vehicle into the parking lot; a step of transmitting the selected parking lot, the reservation time, and the reception time at which the input of the reservation time was received to the server; Execute The first processor further instructs the server to: receiving the parking lot, the reservation time, and the reception time; determining whether the parking status of each of the parking barriers in the parking lots is full (the vehicle is parked), vacant (the vehicle is not parked), or reserved (the vehicle has been reserved for parking); designating one of the parking spaces that is vacant; a step of issuing an instruction to maintain the locked state of the parking lot barrier of the designated parking space during a period from the reception time until the step of transmitting the unlock instruction to the parking lot barrier; The system of claim 6 , wherein the system executes the following:

11. The second processor further configures the mobile terminal to: accepting a selection of one of a plurality of parking lots; receiving an input of a reservation time indicating a planned entry time for the vehicle into the parking lot; a step of transmitting the selected parking lot, the reservation time, and the reception time at which the input of the reservation time was received to the server; Execute The first processor further instructs the server to: receiving the parking lot, the reservation time, and the reception time; determining whether the parking status of each of the parking barriers in the parking lots is full (the vehicle is parked), vacant (the vehicle is not parked), or reserved (the vehicle has been reserved for parking); transmitting the parking status information for each parking space in the parking lot to the mobile terminal; Execute The second processor further configures the mobile terminal to: receiving information about the parking status for each parking stall in the parking lot; outputting information on the parking status for each parking space in the parking lot; accepting a selection of one of the vacant parking spaces; transmitting information of the selected parking space to the server; Execute The first processor further instructs the server to: receiving information about the selected parking space; a step of issuing an instruction to maintain the locked state of the parking lot barrier of the selected parking space during a period from the reception time until the step of transmitting the unlock instruction to the parking lot barrier; The system of claim 6 , wherein the system executes the following:

12. The first processor further instructs the server to: When one of the parking lot barriers in the locked state is designated, the unlock instruction is given to the parking lot barrier, and it is confirmed that the parking lot barrier is again in the locked state, determining that the parking space equipped with the parking barrier is in the vacant state; The system of claim 10 ,

13. The first processor further instructs the server to: When one of the parking lot barriers in the locked state is designated, an instruction to unlock the parking lot barrier is given, and it is confirmed that the parking lot barrier has been locked again, determining that the parking space equipped with the parking barrier is in the vacant state; The system of claim 11 , wherein the system executes the following:

14. The first processor further instructs the server to: calculating a reservation fee based on the elapsed time from the time of reception to the time when the vehicle enters the parking space; The system of claim 10 ,

15. The first processor further instructs the server to: calculating a reservation fee based on the elapsed time from the time of reception to the time when the vehicle enters the parking space; The system of claim 11 , wherein the system executes the following:

16. The first processor further instructs the server to: If a predetermined time has elapsed since the scheduled time and an instruction to unlock the mobile terminal has not been received, canceling the reservation status of the parking space and determining that the parking space is vacant; The system of claim 10 ,

17. The first processor further instructs the server to: If a predetermined time has elapsed since the scheduled time and an instruction to unlock the mobile terminal has not been received, canceling the reservation status of the parking space and determining that the parking space is vacant; The system of claim 11 , wherein the system executes the following:

18. The system further includes a weight sensor disposed within the area of ​​the parking stall; The first processor or the third processor further controls the server or the parking barrier to: When the weight detected by the weight sensor is equal to or greater than a predetermined threshold, determining that the parking space is full; When the weight detected by the weight sensor is less than a predetermined threshold, determining that the parking space is in a state other than a full state; The system of claim 6 , wherein the system executes the following:

19. The parking lot barrier comprises: It has a lighting part, The third processor further configures the parking barrier to: a step of turning on the lighting unit after receiving the unlock instruction; The system of claim 6 , wherein the system executes the following:

20. The third processor further configures the parking barrier to: after executing a step of transitioning the operation state from the release state to the lock state when the lock instruction is received, The first processor further instructs the server to: calculating a parking fee; paying the parking fee; The system of claim 7 , wherein the system executes the following:

21. The third processor further configures the parking barrier to: after executing a step of transitioning the operation state from the release state to the lock state when the lock instruction is received, The first processor further instructs the server to: calculating a parking fee; paying the parking fee; The system of claim 8 , wherein the system executes the following:

22. A parking lot management program comprising parking lot barriers arranged in each of a plurality of parking spaces, a server, and a mobile terminal, wherein the parking lot barriers, the server, and the mobile terminal are capable of communicating with each other; The parking lot barrier comprises: a locked state that prevents a vehicle from entering the parking space; a release state in which the vehicle is not prevented from entering the parking space; The server a first processor; The mobile terminal a second processor; The parking lot barrier comprises: a third processor; The second processor causes the mobile terminal to sending first user information about a user to the server; requesting permission to transition the operational state of the parking lot barrier from the locked state to the unlocked state; Execute The first processor instructs the server to: receiving the first user information about a user from the mobile terminal; granting permission to a request for permission to transition the operational state of the parking lot barrier from the locked state to the unlocked state; confirming that the operational state of the parking lot barrier is the locked state; transmitting an unlock instruction to the parking lot barrier to transition the operational state of the parking lot barrier from the locked state to the unlocked state; Execute The third processor may be configured to: receiving the unlock instruction; transitioning the operational state of the parking lot barrier from the locked state to the unlocked state; A program that executes.

Images