Parking management system, parking management method, and program

Abstract

To provide a parking management system, a parking management method, and a program that can effectively respond to the occurrence of abnormalities. [Solution] A parking management system according to one embodiment of the present invention comprises a sensor unit, a determination unit, and a selection unit. The sensor unit is placed in the parking lot. The determination unit determines the type of abnormality that has occurred in or around the parking lot based on the detection result of the sensor unit. The selection unit selects a target to be notified of the occurrence of the abnormality from among the users of the parking lot, the owner of the parking lot, and the management organization that manages the parking lot, based on the determined type of abnormality.

Description

Technical Field

[0001] The present invention relates to a parking lot management system, a parking lot management method, and a program.

Background Art

[0002] Conventionally, as a method for detecting abnormalities in a parking lot during time periods when no supervisor is present, such as at night, a method is known in which a supervisor remotely monitors video captured by a surveillance camera installed in the parking lot.

[0003] Further, Patent Document 1 discloses a technique of installing an unauthorized parking prevention device in a parking lot, which is for preventing unauthorized parking in parkable areas such as private parking lots and monthly contracted parking lots.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] There is a demand for a technology capable of taking effective countermeasures against abnormalities that occur in parking lots in this manner.

[0006] In view of the circumstances as described above, an object of the present invention is to provide a parking lot management system, a parking lot management method, and a program that can effectively respond to the occurrence of an abnormality.

Means for Solving the Problems

[0007] To achieve the above object, a parking lot management system according to an aspect of the present invention includes a sensor unit, a determination unit, and a selection unit. The sensor unit is disposed in the parking lot. The determination unit determines the type of abnormality that occurred in or around the parking lot based on the detection result of the sensor unit. Based on the determined type of abnormality, the selection unit selects a target for notification of the occurrence of the abnormality from among the users of the parking lot, the owner of the parking lot, and the management organization that manages the parking lot.

[0008] The selection unit may further select at least one of the following as the recipient of notification: the police, fire department, security company, cleaning company, local government, and facilities surrounding the parking lot.

[0009] The selection unit may select, as the notification target, a user who has parked a vehicle in the parking lot at the time the abnormality occurs, or a user who has parked a vehicle near the location where the abnormality occurred.

[0010] The parking management system may further include a notification management unit that manages notifications to selected notification recipients.

[0011] The parking management system may further include a user information management unit that manages user information, including information on recipients of notifications entered by the user. In this case, if the user who entered the recipient information is selected as the recipient of the notification, the notification management unit may notify the user of the occurrence of the abnormality based on the recipient information.

[0012] The parking management system may further include a payment device that accepts a payment operation for parking fees, including the input of vehicle information by the user. In this case, the selection unit may determine, based on the vehicle information input to the payment device, whether or not the user who entered the payment operation has been selected as a notification target. The notification management unit may also notify the user of the occurrence of the abnormality via the payment device if the user who entered the payment operation has been selected as a notification target.

[0013] The payment device may be at least one of the following: a parking fee payment device located in the parking lot, and a user terminal for the user.

[0014] The determination unit may determine the type of abnormality using a machine learning model trained based on a machine learning algorithm, so as to output the type of abnormality in response to input information including the detection result of the sensor unit.

[0015] The selection unit may select the notification target using a machine learning model trained based on a machine learning algorithm, so as to output the notification target in response to input information including the detection result of the sensor unit.

[0016] The determination unit may determine the type of abnormality and the notification target using a machine learning model trained based on a machine learning algorithm, in response to input information including the detection result of the sensor unit. In this case, the selection unit may select the notification target using the machine learning model.

[0017] The sensor unit may include at least one of an imaging device, a temperature sensor, and a smoke sensor.

[0018] A parking lot management method according to one embodiment of the present invention is a parking lot management method executed by a computer system, which includes determining the type of abnormality that occurred in or around the parking lot based on the detection results of a sensor unit placed in the parking lot. Based on the determined type of abnormality, the recipients of notification of the occurrence of the abnormality are selected from among the users of the parking lot, the owner of the parking lot, and the management organization that manages the parking lot.

[0019] A program according to one embodiment of the present invention causes a computer system to execute the parking lot management method described above. [Effects of the Invention]

[0020] As described above, according to the present invention, it is possible to effectively respond to the occurrence of an abnormality. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] [Figure 1] It is a schematic diagram showing a configuration example of a parking lot management system according to an embodiment of the present invention. [Figure 2] It is a schematic diagram showing a configuration example near the entrance and exit of a parking lot. [Figure 3] It is a schematic diagram showing an overall configuration example of a parking lot. [Figure 4] It is a block diagram showing a hardware configuration example of a pre-payment device. [Figure 5] It is a block diagram showing a functional configuration example of a pre-payment device. [Figure 6] It is a block diagram showing a functional configuration example of a parking lot control device. [Figure 7] It is a flowchart showing a basic operation example of a parking lot management device. [Figure 8] It is a block diagram showing a detailed functional configuration example of a parking lot management device. [Figure 9] It is a diagram showing an example of parking lot information. [Figure 10] It is a diagram showing an example of owner information. [Figure 11] It is a diagram showing an example of user information. [Figure 12] It is a diagram showing an example of parked vehicle information. [Figure 13] It is a diagram showing an example of notification destination information. [Figure 14] It is a diagram showing an example of abnormality type information. [Figure 15] It is a diagram showing an example of abnormality history information. [Figure 16] It is a schematic diagram showing an example of abnormality type determination. [Figure 17] It is a flowchart showing an operation example when a vehicle enters the parking lot. [Figure 18] It is a flowchart showing an operation example when a vehicle exits the parking lot. [Figure 19] This flowchart shows an example of anomaly monitoring by a parking management system. [Figure 20] This flowchart shows an example of a notification to users of nearby vehicles. [Figure 21] This flowchart shows an example of the operation when a non-member user makes a prepayment using the prepayment device. [Figure 22] This flowchart shows an example of the process when a non-member user uses a user terminal to make a payment. [Figure 23] This is a schematic diagram showing an example of an image captured by an on-site camera. [Figure 24] This is a schematic diagram showing an example of an image captured by an on-site camera. [Figure 25] This figure shows an example of a monitoring GUI displayed on the management agency terminal and the staff terminal. [Figure 26] This figure shows an example of a monitoring GUI displayed on the management agency terminal and the staff terminal. [Figure 27] This is a schematic diagram illustrating an example of notifying members of an anomaly via email. [Figure 28] This figure shows an example of the GUI displayed on the touch panel of the pre-payment device 27 (exit payment device 32). [Figure 29] This is a schematic diagram showing an example of a GUI displayed on a user's terminal. [Figure 30] This is a schematic diagram showing an example of a GUI displayed on a user's terminal. [Figure 31] This block diagram shows an example of a computer hardware configuration that can be used as a user terminal, parking management device, etc. [Modes for carrying out the invention]

[0022] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0023] [Parking Management System] Figure 1 is a schematic diagram showing an example configuration of a parking management system according to one embodiment of the present invention.

[0024] The parking management system 1 includes a user terminal 2, an owner terminal 3, a management agency terminal 4, a parking management device 5, a payment server device (not shown) owned by the payment agency 6, and a communication device (not shown) owned by the notification recipient agency 7. The parking management system 1 also includes a parking control device 9 located in the parking lot 8.

[0025] As shown in Figure 1, these devices are connected to each other via network 10 so that they can communicate with one another. Network 10 is constructed using, for example, the Internet or a wide-area communication network. In addition, any WAN (Wide Area Network) or LAN (Local Area Network) may be used, and the protocol for constructing network 10 is not limited.

[0026] User terminal 2 is a terminal used by user 11 who uses parking lot 8. Typically, a mobile device such as a smartphone is used as user terminal 2. Various PDAs (Personal Digital Assistants), such as tablet devices, can be used as user terminal 2.

[0027] Owner terminal 3 is a terminal used by the owner 12 of parking lot 8. Any computer, such as a smartphone, tablet, or various PCs (personal computers), may be used as owner terminal 3.

[0028] The management agency terminal 4 is used by an operator 14 of the management agency 13, which has been entrusted with the management of parking lot 8 by the owner 12 of parking lot 8. The operator 14 handles tasks such as responding to daily inquiries, assisting users, and providing information on maintenance work in case of malfunctions of various devices installed in parking lot 8. The operator 14 also handles tasks related to responding to abnormalities that occur in parking lot 8. The management agency terminal 4 can be a PC or a tablet device.

[0029] The parking management device 5 is a device that manages the parking lot 8, and can provide the parking management service (abnormality notification service) according to this embodiment as a web service.

[0030] The parking management device 5 has hardware necessary for a computer, such as a processor (CPU, GPU, DSP, etc.), memory (ROM, RAM, etc.), and storage devices (HDD, etc.).

[0031] The parking management device 5 also has a communication unit for communicating with other terminals and devices via the network 10. The communication unit can be, for example, a wireless LAN module such as WiFi, or communication equipment such as a modem or router. The parking management device 5 can be any computer, such as a PC.

[0032] As shown in Figure 1, a database (DB) 15 is connected to the parking management device 5. DB 15 functions as a storage unit and stores various information related to this parking management service. For example, it is possible to construct various databases within DB 15, such as a parking information DB, owner information DB, user information DB, parked vehicle information DB, anomaly history information DB, anomaly type information DB, notification destination information DB, and various history information DBs.

[0033] Various databases are comprehensively managed by the parking management device 5, which performs tasks such as registering and storing information on users 11 who use the parking management service, registering and storing owner information for each parking lot 8, recording and storing operational revenue and expenditure information, and recording and storing information on abnormalities occurring in the parking lot 8.

[0034] In this embodiment, a web page is generated by the parking management device 5. The generated web page is displayed on the screens of the user terminal 2, owner terminal 3, management agency terminal 4, payment server device of the payment agency 6, and communication device of the notification recipient agency 7 via the network 10 shown in Figure 1, using web browsers installed in these devices.

[0035] For example, users 11, owners 12, and operators 14 can access various web pages and use various web applications related to the parking lot 8 by operating user terminal 2, owner terminal 3, and management agency terminal 4.

[0036] This parking management service may be provided via a native application. In this case, the parking management application program is downloaded to the user terminal 2, the owner terminal 3, and the management organization terminal 4. Various other forms of using the parking management application may also be employed.

[0037] The payment institution 6 is, for example, a bank or a credit company, and processes the payment (settlement) of parking fees via bank transfer, credit card payment, etc. The parking management device 5 issues instructions to the payment server device of the payment institution 6 for the settlement of parking fees, and queries for settlement information such as whether the settlement has been completed. The payment institution 6 may also include institutions that provide various code payment services.

[0038] In this embodiment, it is also possible to settle parking fees using pre-payment devices and exit payment devices located in parking lot 8. This will be discussed later.

[0039] The notification recipient organization 7 is a schematic representation of an example of a recipient of notification regarding the occurrence of an anomaly in or around the parking lot 8. Recipients of notification regarding the occurrence of an anomaly include, for example, the user 11, owner 12, and operator 14, as shown in Figure 1, and the notification recipient organization 7.

[0040] Examples of notifiable organizations 7 include the police, fire department, security companies, cleaning companies, local governments, and facilities surrounding the parking lot 8. Surrounding facilities include any facilities located in the vicinity, such as nearby shops and community centers. Notifiable organizations can also be called notifiable related organizations.

[0041] In applying the present invention, the method of notifying the occurrence of an abnormality is not limited, and any notification method can be adopted, such as any communication using the network 10, including email and chat applications, telephone, and communication using a dedicated line.

[0042] For example, by employing notification methods such as telephone or dedicated lines, it is possible to notify the notification recipient organization 7 of the occurrence of an anomaly without going through the network 10 shown in Figure 1. In other words, when applying the present invention, it is possible to adopt a configuration in which the communication equipment of the notification recipient organization 7 is not connected to the network 10.

[0043] Figures 2 and 3 are schematic diagrams showing specific configuration examples of parking lot 8. Figure 2 is a schematic diagram showing the configuration near the entrance and exit of parking lot 8. Figure 3 is a schematic diagram showing the overall configuration example of parking lot 8.

[0044] As shown in Figure 2, the parking lot 8 has an entrance 17 and an exit 18. As shown in Figure 2, a central island 20 is installed between the entrance 17 and the exit 18. In addition, an entrance island 21 and an exit island 22 are installed on either side of the central island 20.

[0045] The area between Central Island 20 and Entrance Island 21 will be the entrance lane 23 of Parking Lot 8. The area between Central Island 20 and Exit Island 22 will be the exit lane 24 of Parking Lot 8.

[0046] Within the premises 25 of parking lot 8, a parking control device 9, an attendant terminal 26, a pre-payment device 27, a pre-payment monitoring camera 28, and a guidance device 29 are installed.

[0047] Additionally, the central island 20 is equipped with an entrance gate 30, an exit gate 31, an exit payment device 32, an entrance camera 33, and an exit camera 34.

[0048] The parking control device 9 can comprehensively control the operation of each device installed within the parking lot 8. Furthermore, the parking control device 9 can collect various information and data from each device installed within the parking lot 8 and transmit it to the parking management device 5, etc. The parking control device 9 can also receive various information from the parking management device 5, etc., and perform various operations.

[0049] The parking control device 9 has hardware necessary for a computer, such as a processor (CPU, GPU, DSP, etc.), memory (ROM, RAM, etc.), and storage devices (HDD, etc.).

[0050] The parking control device 9 also has a communication unit for communicating with other terminals and devices via the network 10. The communication unit can be, for example, a wireless LAN module such as WiFi, or communication equipment such as a modem or router. The parking control device 9 can be any computer, such as a PC.

[0051] As shown in Figure 1, DB35 is connected to the parking control device 9. DB35 functions as a memory unit and stores various information related to the management and control of each device in the parking lot 8. Information stored in DB15 of the parking management device 5 may also be stored in DB35 in common. The information and data stored in common are managed in a synchronized manner.

[0052] The attendant terminal 26 is a terminal used by the attendant of the parking lot 8. Any computer, such as a smartphone, tablet, or various PCs, may be used as the attendant terminal 26. By operating the attendant terminal 26, the attendant can view various web pages related to the management of the parking lot 8 and use various web applications.

[0053] The pre-payment device 27 is a device for users 11 to pre-pay parking fees. The pre-payment monitoring camera 28 is positioned to photograph users 11 making pre-payments. The exit payment device 32 is a device for users 11 who have not yet paid to pay parking fees while remaining in their vehicles when exiting the parking area.

[0054] In this embodiment, the pre-payment device 27 and the exit payment device 32 have substantially the same configuration and function. The pre-payment device 27 and the exit payment device 32 can also be collectively referred to as a parking fee payment device that performs the settlement of parking fees.

[0055] The guidance device 29 is a device for providing various information about the parking lot 8 and various information about the parking lot management system 1. For example, a device that has a display device or the like and can display guidance information is used as the guidance device 29.

[0056] Entrance gate 30 is a device for restricting vehicle entry into parking lot 8. Exit gate 31 is a device for restricting vehicle exit from parking lot 8.

[0057] The entrance camera 33 is positioned to capture images of vehicles 37 entering the entrance lane 23 (hereinafter referred to as "entering vehicle images"). The entering vehicle images are captured when vehicles enter the parking lot 8.

[0058] The exit camera 34 is positioned to capture images of exiting vehicles 38 entering exit lane 24 (hereinafter referred to as exiting vehicle images). The exiting vehicle images are captured when vehicles exit parking lot 8.

[0059] For the pre-payment monitoring camera 28, entrance camera 33, and exit camera 34, digital cameras equipped with image sensors such as CMOS (Complementary Metal-Oxide Semiconductor) sensors or CCD (Charge Coupled Device) sensors are used. Other types of cameras may also be used.

[0060] The parking control device 9, staff terminal 26, pre-payment monitoring camera 28, pre-payment device 27, guidance device 29, entrance gate 30, exit payment device 32, exit gate 31, entrance camera 33, and exit camera 34 are connected by internal wiring 39 (see Figure 1) installed within the parking lot 8 premises 25. Instead of internal wiring 39, a local network using wireless communication may be constructed.

[0061] In addition, an entrance loop coil 40 is embedded in the entrance lane 23 to detect the presence and passage of an entering vehicle 37. An exit loop coil 41 is embedded in the exit lane 24 to detect the presence and passage of an exiting vehicle 38.

[0062] As shown in Figure 3, the parking lot 8's premises 25 are equipped with premises passageways 43, multiple parking spaces 44, and multiple on-site cameras 45. In addition, in the parking lot 8 shown in Figure 3, a pre-payment device 27, a pre-payment monitoring camera 28, and a guidance device 29 are also located in a different location (lower left in the figure) from the entrance 17 and exit 18.

[0063] The internal passageway 43 is a passageway used by vehicles that have entered the parking lot 8. It is also a passageway used by drivers and other pedestrians who have disembarked from parked vehicles. As shown in Figure 3, signs (arrows, etc.) indicating the direction of vehicle travel may be provided along the internal passageway 43. A separate passageway for pedestrians may also be provided.

[0064] Vehicles are parked in multiple parking spaces 44. Although not shown in Figure 3, each parking space 44 is marked with a space number such as "A1" or "B2".

[0065] Multiple on-site cameras 45 are positioned to capture the on-site pathways 43 and parking spaces 44. In this embodiment, 10 on-site cameras 45 are positioned to capture the entire on-site area 25 of the parking lot 8 (white circles in the figure).

[0066] For the on-site camera 45, a digital camera equipped with an image sensor such as a CMOS sensor or CCD sensor can be used. Other types of cameras may also be used.

[0067] In this embodiment, the sensor unit 47 shown in Figure 1 is composed of the pre-payment monitoring camera 28 shown in Figure 2, the entrance camera 33, the exit camera 34, and a plurality of in-park cameras 45 shown in Figure 3. The sensor unit 47 is one embodiment of a sensor unit arranged in a parking lot according to the present invention.

[0068] The sensor unit 47 is constructed as a system capable of monitoring the parking lot 8 and its surroundings. The pre-payment monitoring camera 28, the entrance camera 33, the exit camera 34, and the multiple in-parking cameras 45 shown in Figure 3 can each also be referred to as monitoring cameras.

[0069] The devices installed as the sensor unit 57 (monitoring system) are not limited to imaging devices such as the on-site camera 45, but may also be any sensors such as temperature sensors or smoke sensors. It is also possible to measure temperature or detect smoke based on images (including video) captured by the on-site camera 45, etc. In this case, the imaging device can be said to be functioning as a temperature sensor or smoke sensor.

[0070] Figure 4 is a block diagram showing an example of the hardware configuration of the pre-payment device 27. The pre-payment device 27 has a processor 50 such as a CPU, a memory 51, and an interface 53 connected to these via a bus 52. The memory 51 is composed of, for example, ROM, RAM, flash memory, etc., and stores various programs and various parking data. Of course, the pre-payment device 27 may also be equipped with a storage device such as an HDD.

[0071] Interface 53 is connected to a private network communication unit 54, a code image reader 55, a card reader 56, a banknote and coin management unit 57, a receipt printer 58, a touch panel 59, a speaker 60, and a human presence sensor 61. The operation of each block is controlled by a processor 50 that operates according to a program.

[0072] The premises communication unit 54 is equipped with a communication circuit for communicating with other devices within the premises and is connected to other devices via premises wiring 39 so as to be able to communicate with them.

[0073] The code image reader 55 is composed of, for example, an optical reading device that incorporates a laser scanner. The code image reader 55 can read a code image held over a reading opening located on the front of the device by scanning a laser beam outwards from the reading opening. For example, the code image reader 55 can read QR codes (registered trademark) and barcodes used in code payments.

[0074] The card reader 56 is configured to support electronic money payments. For example, the card reader 56 can be a multi-type IC card reader capable of reading various contactless IC cards with electronic money functionality, such as transportation-related electronic money and retail-related electronic money. Of course, it is also possible to configure the card reader 56 to be able to read various credit cards and house cards.

[0075] The banknote and coin management unit 57 receives banknotes and coins inserted into the banknote and coin slots located on the front of the device, counts them, and calculates the total amount inserted. It also counts any change required for settlement and dispenses it through the coin / receipt dispenser.

[0076] The receipt printer 58 prints and issues receipts on receipt paper, including the settlement amount and date. The issued receipts can be retrieved from the coin / receipt slot located on the front of the device.

[0077] The touch panel 59 has an image display function and a function to accept various touch operations from the user 11. The speaker 60 has an audio output function. The specific configuration of the touch panel 59 and speaker 60 is not limited, and any configuration may be adopted.

[0078] The motion sensor 61 detects a person standing in front of the pre-payment device 27. The specific configuration of the motion sensor 61 is not limited, and any configuration may be used. For example, a pyroelectric sensor that utilizes changes in infrared radiation emitted by the human body may be used.

[0079] Figure 5 is a block diagram showing an example of the functional configuration of the pre-payment device 27. As shown in Figure 5, the pre-payment device 27 includes a payment processing unit 63, a display control unit 64, and an input receiving unit 65.

[0080] These blocks are formed when the processor 50 of the pre-payment device 27 executes a predetermined program and cooperates with hardware resources within the device, thereby realizing the processing necessary to implement the parking management method according to this embodiment. Dedicated hardware such as ICs (integrated circuits) may be used as appropriate to constitute each block.

[0081] The program is installed on the pre-payment device 27, for example, via various recording media. Alternatively, the program may be installed via the Internet or the like. The type of recording media on which the program is recorded is not limited, and any computer-readable recording media may be used. For example, any non-transient storage medium that is computer-readable may be used.

[0082] The settlement processing unit 63 performs processing related to the settlement of parking fees incurred by the user 11 using the parking lot 8. For example, the settlement processing unit 63 can send a request for inquiry about parking fees to the parking management device 5 via the parking control device 9.

[0083] Furthermore, the settlement processing unit 63 can perform settlement on the requested parking fee using the payment method selected by the user 11. For example, various settlement processes can be performed, such as credit card payment, electronic money payment, code image payment, debit card payment, and point settlement processing.

[0084] The display control unit 64 controls the display of images on the touch panel 59. For example, the display control unit 64 displays captured images such as images of entering vehicles, various GUI elements such as icons and buttons, on the touch panel 59.

[0085] The input reception unit 65 receives various inputs from the user 11 operating the pre-payment device 27. Based on the signals (operation signals) corresponding to the user 11's operation of the touch panel 59, the input reception unit 65 can determine what instructions or information have been entered.

[0086] In this embodiment, the exit payment device 32 also has the hardware configuration shown in Figure 4 and the functional configuration shown in Figure 5.

[0087] Figure 6 is a block diagram showing an example of the functional configuration of the parking control device 9. As shown in Figure 6, the parking control device 9 includes a vehicle detection unit 66, a sensor control unit 67, a gate control unit 68, an entry / exit processing unit 69, and a communication control unit 70.

[0088] These blocks are formed when the processor of the parking control device 9 executes a predetermined program and cooperates with hardware resources within the device, thereby realizing the processing necessary to implement the parking management method according to this embodiment. Dedicated hardware such as ICs (integrated circuits) may be used as appropriate to constitute each block.

[0089] The program is installed on the parking control device 9, for example, via various recording media. Alternatively, the program may be installed via the internet or the like. The type of recording media on which the program is stored is not limited; any computer-readable recording media may be used. For example, any non-transient storage medium that is computer-readable may be used.

[0090] The vehicle detection unit 66 detects the entry of vehicles 37 into the entrance lane 23 and the entry of vehicles 37 into the premises 25 based on signals output from the entrance loop coil 40. The vehicle detection unit 66 also detects the entry of vehicles 38 into the exit lane 24 and the exit of vehicles 38 to the outside based on signals output from the exit loop coil 41.

[0091] Furthermore, any other configuration may be used to detect vehicles entering the entrance lane 23 and the exit lane 24. For example, optical sensors using infrared light or the like may be used.

[0092] The sensor control unit 67 controls the operation of the sensor unit 47 shown in Figure 1. In this embodiment, the sensor control unit 67 controls the operation of the pre-payment monitoring camera 28, entrance camera 33, exit camera 34, and multiple in-house cameras 45 that constitute the sensor unit 47. In this embodiment, the sensor control unit 67 can also be called a camera control unit.

[0093] For example, the sensor control unit 67 transmits a trigger signal for shooting, and the entrance camera 33 and exit camera 34 take pictures of the entering vehicle 37 and the exiting vehicle 38.

[0094] This generates images of entering and exiting vehicles. The trigger signals may be, for example, the outputs of the inlet loop coil 40 and the outlet loop coil 41, which are used as trigger signals for the inlet camera 33 and the outlet camera 34, respectively, but a separate trigger sensor may also be installed.

[0095] Furthermore, the sensor control unit 67 may enable the execution of functions such as zoom control, focus control, gain control, pan control, tilt control, and auto-tracking control for the pre-payment monitoring camera 28, entrance camera 33, exit camera 34, and multiple in-house cameras 45.

[0096] The gate control unit 68 controls the operation of the entrance gate 30 and the exit gate 31. The entrance / exit processing unit 69 performs processing related to the entrance of the entrance vehicle 37 (such as transmitting images of the entrance vehicle) and processing related to the exit of the exit vehicle 38 (such as transmitting images of the exit vehicle). The communication control unit 70 controls communication with other terminals and devices via the network 10.

[0097] Furthermore, the pre-payment device 27 illustrated in Figures 4 and 5 may be equipped with the configuration and functions of the parking control device 9 shown in Figure 6. In other words, it is also possible to configure the pre-payment device 27 and the parking control device 9 as an integrated unit.

[0098] [Select who to notify about when an anomaly occurs] This parking management system 1 allows for the selection of notification targets for anomalies occurring in or around parking lot 8.

[0099] As schematically illustrated in Figure 1, in this embodiment, the processor of the parking management device 5 executes the program according to the present invention, thereby configuring the determination unit 72 and the selection unit 73 as functional blocks. Of course, dedicated hardware such as ICs (integrated circuits) may be used to realize each functional block.

[0100] The program is installed on the parking management device 5, for example, via various recording media. Alternatively, the program may be installed via the internet or the like. The type of recording media on which the program is stored is not limited, and any computer-readable recording media may be used. For example, any non-transient storage medium that is computer-readable may be used.

[0101] Figure 7 is a flowchart showing a basic example of the operation of the parking management device 5. First, the detection result of the sensor unit 47 is acquired by the determination unit 72 (step 101). In this embodiment, images captured by the pre-payment monitoring camera 28, the entrance camera 33, the exit camera 34, and the multiple in-parking cameras 45 are acquired. Note that the captured images include not only still images but also moving images.

[0102] Furthermore, the determination unit 72 determines the type of abnormality that occurred in or around the parking lot 8 based on the detection results of the sensor unit 47 (step 102). In this embodiment, the type of abnormality is determined based on the images captured by the pre-payment monitoring camera 28, the entrance camera 33, the exit camera 34, and the multiple in-parking cameras 45.

[0103] Based on the determined type of abnormality, the selection unit 73 selects the recipients to be notified of the occurrence of the abnormality (step 103). In this embodiment, first, the recipients to be notified of the occurrence of the abnormality are selected from among the users 11 of the parking lot 8, the owner 12 of the parking lot 8, and the management organization 13 that manages the parking lot 8.

[0104] In this embodiment, the operator 14 and the parking lot attendant 8 belong to the management organization 13. Therefore, notifications to the operator 14 and the attendant are included in notifications to the management organization 13.

[0105] In this embodiment, the selection unit 73 also allows for the selection of notification targets from among the notification recipient organizations 7 (police, fire department, security company, cleaning company, local government, and facilities surrounding the parking lot 8, etc.).

[0106] The following provides a detailed explanation of how to determine the type of anomaly shown in Figure 7 and how to select the target for notification.

[0107] Figure 8 is a block diagram showing a detailed functional configuration example of the parking management device 5. Figures 9 to 15 show examples of information stored in each of the following databases built within DB15: parking information DB, owner information DB, user information DB, parked vehicle information DB, anomaly history information DB, anomaly type information DB, and notification destination information DB.

[0108] As shown in Figure 8, the parking management device 5 includes a parking information management unit 75, an owner information management unit 76, a user information management unit 77, a vehicle information recognition unit 78, a parked vehicle information management unit 79, an abnormality determination unit 80, a notification target selection unit 81, a notification management unit 83, an abnormality-related information management unit 82, a settlement processing unit 84, a GUI generation unit 85, and a communication control unit 86.

[0109] These blocks are formed when the processor of the parking management device 5 executes a predetermined program and cooperates with hardware resources within the device, thereby realizing the processing necessary to implement the parking management method according to this embodiment.

[0110] The parking information management unit 75 manages information about the parking lots 8 that can be managed by the parking management system 1. In this embodiment, the parking information management unit 75 generates and manages the parking information shown in Figure 9.

[0111] As shown in Figure 9, in this embodiment, the following information (data) is stored as parking information.

[0112] "Parking No."... A number used to identify parking lot 8. "Parking lot name"... The name of parking lot 8. "Parking lot address"... The address of parking lot 8. "Phone number"...the phone number for parking lot 8.

[0113] "Map information (coordinates)"...Location information of parking lot 8. In this embodiment, the X and Y coordinates are stored (the coordinate system may be set as appropriate). Of course, latitude and longitude information may also be stored as location information of parking lot 8.

[0114] "Fee System"... Information regarding the fee system for parking lot 8. For example, this may include information such as hourly rates on weekdays, hourly rates on weekends and holidays, maximum daytime rates, and maximum nighttime rates. Links to the fee system information may also be stored.

[0115] "Usage Status Information"...Historical information regarding the current usage status of parking lot 8. In this embodiment, a usage status information database for parking lot 8 is constructed in DB15, and links (link UI) to the usage status information stored in the usage status information database are stored in "Usage Status Information".

[0116] The usage information stored in the usage information database includes arbitrary historical information regarding the usage status of parking lot 8, such as the number of parked cars and the number of available cars at a specified date and time or over a specified period.

[0117] The owner information management unit 76 manages information about the owner of the parking lot 8. In this embodiment, the owner information management unit 76 generates and manages the owner information shown in Figure 10.

[0118] As shown in Figure 10, in this embodiment, the following information (data) is stored as owner information.

[0119] "Owner Number"... A number assigned to each owner. "Name"... The owner's name. "Address 1"... The owner's home address (prefecture name). "Address 2"... The owner's home address (address below the prefecture level). "Email address"...an email address. In this embodiment, an email address that can receive and view emails on the owner terminal 3 is registered.

[0120] "Owned Parking Lot No."... The "Parking Lot No." of the 8 parking lots owned. "Management Information"... Information related to the management and administration of parking lot 8. In this embodiment, a management information database for parking lot 8 is constructed in DB15, and links (link MI) to the management information stored in the management information database are stored in "Management Information".

[0121] The management information stored in the management information database includes, for example, arbitrary information related to the management and operation of parking lot 8, such as its type, capacity, location, sales, maintenance costs, facilities, troubleshooting, management outsourcing, and handling of anomalies.

[0122] The user information management unit 77 manages information about users 11 who have registered for the parking management service. In this embodiment, the user information management unit 77 generates and manages the user information shown in Figure 11.

[0123] It is also possible to refer to users 11 who have registered for the parking management service as members. The user information shown in Figure 11 can also be considered member information. In this embodiment, users 11 who have entered into a contract for regular use of the parking lot 8 are registered as members.

[0124] For example, user 11 launches the user application to use this parking management service. Then, an application screen for applying for regular use of parking lot 8 opens. User 11 enters personal information, etc., as exemplified below, and applies for regular use. When a regular use contract is concluded, the following user information is generated and managed.

[0125] In this embodiment, non-member users 11 can also use the parking lot 8. Non-member users 11 pay the parking fee using the pre-payment device 27, the exit payment device 32, or the user terminal 2.

[0126] The present invention can also be applied when the users 11 include both regular members and non-members who rent by the hour.

[0127] As shown in Figure 11, in this embodiment, the following information (data) is stored as user information.

[0128] "Membership Number"... A number assigned to each member. "Name"... The member's name. "Address 1"... The member's home address (prefecture name). "Address 2"... The member's home address (address below the prefecture level). "Email address"... an email address. In this embodiment, an email address that can be received and viewed by the user terminal 2 is registered. "Email address" corresponds to one embodiment of the notification recipient information according to the present invention.

[0129] "Contracted Parking Lot No."... The "Parking Lot No." for parking lot 8, for which a contract for regular use has been made. "Contract start date"... The start date of the regular usage contract. "Contract end date"... The end date of the regular usage contract. "Vehicle Number"... The vehicle number of user 11's vehicle (a vehicle covered by a regular contract).

[0130] In this embodiment, the user information management unit 77 functions as one embodiment of the user information management unit according to the present invention, which manages user information including notification destination information entered by the user.

[0131] The vehicle information recognition unit 78 extracts vehicle information (hereinafter referred to as "entering vehicle information") related to the entering vehicle 37 from the entering vehicle image. The vehicle information recognition unit 78 also extracts vehicle information (hereinafter referred to as "exiting vehicle information") related to the exiting vehicle 38 from the exiting vehicle image.

[0132] For example, vehicle information may include at least some information about the vehicle number, vehicle name, body color, and vehicle manufacturer. Combined information or other information related to the vehicle may also be extracted as vehicle information.

[0133] At least some of the information on a vehicle license plate (such as the name of the Land Transport Bureau, classification number, hiragana characters, and a four-digit serial number) can be recognized using techniques such as image processing to extract a portion of the license plate or OCR (Optical Character Recognition) processing. Of course, any other technique may be used.

[0134] In this embodiment, the vehicle information recognition unit 78 extracts whether the vehicle type of the entering vehicle 37 is a gasoline vehicle, a hybrid vehicle, or an electric vehicle. This vehicle type information can be extracted from the entering vehicle image. Alternatively, it is possible to extract information about other vehicle types from the entering vehicle image and query an external vehicle information management organization's server device (not shown) via the network 10 to determine whether the entering vehicle 37 is a gasoline vehicle, a hybrid vehicle, or an electric vehicle.

[0135] The parking vehicle information management unit 79 generates and manages parking vehicle information regarding the parking status of the user's vehicle 11 in the parking lot 8. In this embodiment, the parking vehicle information management unit 79 generates and manages the parking vehicle information shown in Figure 12 in response to the vehicle entering the parking lot 8.

[0136] As shown in Figure 12, in this embodiment, the following information (data) is stored as parked vehicle information.

[0137] "Parking No."... A number used to identify Parking Lot 8. The "Parking No." of Parking Lot 8, into which user 11's vehicle entered, is stored here. "Vehicle Number"... The vehicle number of vehicle 37 that entered parking lot 8.

[0138] "Vehicle Type"... There are 37 types of vehicles that can enter the facility. For gasoline vehicles, "01" is stored. For hybrid vehicles, "02" is stored. For electric vehicles, "03" is stored. "Membership Number"... A number assigned to each member. The "Membership Number" of user 11 who entered parking lot 8 is stored here. If the user is not a member, the "Membership Number" will be blank.

[0139] "Entry Date and Time"... The entry date and time for vehicle 37. "Departure Date and Time"... Departure dates and times for the 38 participating vehicles. "Parking fee"...Parking fee incurred for using parking lot 8. "Settlement Date and Time"... The date and time for settling the parking fee. If user 11 is a member, it will be considered a regular user, so the "parking fee" and "settlement date and time" fields will be left blank.

[0140] The abnormality determination unit 80 corresponds to the determination unit 72 shown in Figure 1, and determines the type of abnormality that occurred in or around the parking lot 8 based on the detection results of the sensor unit 47. In this embodiment, the type of abnormality is determined based on the images captured by the pre-payment monitoring camera 28, the entrance camera 33, the exit camera 34, and the multiple in-parking cameras 45.

[0141] Examples of the types of abnormalities that may occur in or around parking lot 8 include the following: "Fire"...A fire occurring inside or around parking lot 8. Examples include fires originating from vehicles parked in parking space 44 as shown in Figure 3, or fires originating from facilities in parking lot 8. Other examples include fires occurring in facilities surrounding parking lot 8. Of course, these are not the only examples.

[0142] "Accident"... An accident occurring inside or around parking lot 8. For example, a personal injury or property damage accident occurring in the premises passageway 43 shown in Figure 3, or a traffic accident occurring on the road 87 facing parking lot 8, as shown in Figure 3. Of course, it is not limited to these.

[0143] "Obstacles"... Obstacles found inside or around parking lot 8 that obstruct the progress of vehicles. Examples include obstacles left in the premises passageway 43, or obstacles left near entrance 17 and exit 18. Of course, this is not limited to these.

[0144] "Congestion" refers to congestion occurring inside or around parking lot 8. Examples include congestion of users (pedestrians) and vehicles in the internal passageways 43, entrance 17, and exit 18, as well as traffic congestion on the road 87 facing parking lot 8. Of course, it is not limited to these examples.

[0145] "Dirt" refers to dirt that occurs inside or around parking lot 8. Examples include oil and gasoline stains in the internal passageways 43 and parking spaces 44, as well as abandoned trash. It also includes oil and gasoline stains and abandoned trash near entrance 17 and exit 18. Of course, it is not limited to these examples.

[0146] "Damage" refers to damage occurring inside or around parking lot 8. Examples include damage to vehicles parked in parking space 44, or damage to the facilities of parking lot 8. Graffiti is also included. Of course, it is not limited to these examples.

[0147] In addition, it is possible to determine the type of any abnormality that occurs in or around parking lot 8.

[0148] The specific algorithm for determining the type of anomaly occurring in or around parking lot 8 is not limited, and any algorithm may be used. For example, it is possible to determine the type of anomaly using an algorithm that employs a machine learning model constructed using a neural network or the like (machine learning algorithm).

[0149] For example, any machine learning algorithm using DNN (Deep Neural Network), RNN (Recurrent Neural Network), CNN (Convolutional Neural Network), etc. may be used. For example, by using AI (Artificial Intelligence) that performs deep learning, it becomes possible to determine the type of anomaly with high accuracy.

[0150] Figure 16 is a schematic diagram showing an example of anomaly type determination. In the example shown in Figure 16A, the anomaly determination unit 80 determines the type of anomaly using a machine learning model 90 trained based on a machine learning algorithm, so as to output an anomaly type 89 in response to input information 88 including the detection result of the sensor unit 47.

[0151] The machine learning model 90 can be trained using, for example, training data consisting of detection results (captured images) and correct information on the type of anomaly associated with the detection results (captured images). For example, training data can be generated based on anomaly history information managed by the anomaly-related information management unit 82, which will be described later.

[0152] For example, detection results (captured images) in which fire occurrences were previously determined can be used as training detection results (captured images), and training data can be generated in which the determined fires are the correct information for the type of anomaly. It is possible to train the machine learning model 90 using this training data. Of course, the learning method is not limited to this, and various learning methods may be employed.

[0153] Through learning, the parameters (coefficients) for calculating the correct answer (type of anomaly) are updated and generated as trained parameters. A program incorporating these generated trained parameters is created as the machine learning model 90. For example, the machine learning model 90 can be constructed using a neural network.

[0154] Figure 16B is a schematic diagram showing another example of determining the type of anomaly. As shown in Figure 16B, the type of anomaly 89 may be output by processing the input information 88, which includes the detection result of the sensor unit 47, using a rule-based algorithm 91. The specific algorithm executed as the rule-based processing is not limited, and any algorithm such as image analysis techniques may be used.

[0155] The application of the machine learning algorithm described with reference to Figure 16A may be performed on any process within this disclosure. In other words, machine learning-based processing may be performed on any process described within this disclosure.

[0156] The notification target selection unit 81 corresponds to the selection unit 73 shown in Figure 1, and selects the notification target to be notified of the occurrence of an abnormality based on the determined type of abnormality. In this embodiment, the notification target to be notified of the occurrence of an abnormality is selected from among the users 11 who use the parking lot 8, the owner 12 of the parking lot 8, and the manager who manages the parking lot 8. It is also possible to select the notification target from among the notification recipient organizations 7 (police, fire department, security company, cleaning company, local government, and facilities around the parking lot 8, etc.).

[0157] The specific algorithm for selecting notification targets based on the type of anomaly is not limited, and any algorithm may be used. For example, it is possible to select notification targets using a machine learning algorithm.

[0158] For example, the notification target selection unit 81 can select notification targets using a machine learning model trained based on a machine learning algorithm, so as to output notification targets in response to input information that includes the type of anomaly.

[0159] Furthermore, the notification target selection unit 81 can select notification targets using a machine learning model trained based on a machine learning algorithm so as to output notification targets in response to input information including the detection results of the sensor unit 47. In other words, it is also possible to construct and use a machine learning model trained to output notification targets in response to the input of the detection results of the sensor unit 47.

[0160] It is also possible to construct and use a machine learning model trained based on a machine learning algorithm so as to output both the type of anomaly and the notification target in response to input information including the detection results of the sensor unit 47. In this case, the anomaly determination unit 80 uses the machine learning model to determine the type of anomaly. The notification target selection unit 81 also uses the same machine learning model to select the notification target.

[0161] These machine learning models can be trained by generating training data from, for example, historical information about anomalies that have occurred and been reported in the past.

[0162] Of course, a rule-based algorithm may be used to select notification targets based on the type of anomaly. For example, it is possible to select notification targets by referring to a table or database that associates notification targets with anomaly types.

[0163] The anomaly-related information management unit 82 generates and manages information related to anomalies that occur in or around the parking lot 8. In this embodiment, the anomaly-related information management unit 82 generates and manages notification destination information shown in Figure 13, anomaly type information shown in Figure 14, and anomaly history information shown in Figure 15.

[0164] As shown in Figure 13, in this embodiment, the following information (data) is stored as notification destination information.

[0165] "Parking No."... A number used to identify parking lot 8. In this embodiment, it is possible to set a notification target for each parking lot 8, and the "Parking No." of the parking lot 8 for which a notification target is set is stored.

[0166] "Notification Recipient No."... A number used to identify the recipient of the notification. "Name of recipient of notification"... The name of the person to whom the notification will be sent. "Notification Contact Information"... This refers to the contact person to whom notifications will be sent. For example, it stores contact information for conducting communication via the internet (address information such as email addresses and URLs), telephone numbers, and dedicated line information.

[0167] In the example shown in Figure 13, the following notification targets are set. The "parking lot owner" is the owner 12 of parking lot 8, as illustrated in Figure 1.

[0168] "Parking lot manager," "management staff," "management supervisor," "sales representative," "branch manager," "support center," and "parking lot attendant" are individuals and organizations belonging to the management organization 13, which has been entrusted with the management of parking lot 8 by the owner 12 of parking lot 8. These notification contacts are included in the notification contacts for management organization 13.

[0169] In particular, the "Support Center" functions as a call center and is configured as the first point of contact for managing parking lot 8. It should be noted that in this disclosure, the management organization 13 is not limited to being established by a single company or entity. For example, if there are different companies or entities to which management operations are outsourced, these companies are collectively referred to as the management organization 13.

[0170] In this embodiment, the notification contact for the "Support Center" is the contact information for operator 14 shown in Figure 1. The notification contact for the "Parking Attendant" is the notification contact for the parking attendant at parking lot 8.

[0171] "X Town Police Station," "X Town Fire Station," "K Security Company," "X Town (Municipality)," "Commercial Facility S," "Owner-designated contractor," and "X Cleaning Company" are examples of variations of the seven notification recipient organizations illustrated in Figure 1.

[0172] "Users of nearby vehicles" are users of nearby vehicles parked near the location where the anomaly occurred at the time the anomaly occurred. Nearby vehicles can be extracted, for example, based on the captured images in which the anomaly was detected. For example, the license plates of vehicles visible in the captured images in which the anomaly was detected may be extracted. Alternatively, the license plates of vehicles within a predetermined distance from the location where the anomaly occurred may be extracted.

[0173] Based on the extracted "vehicle number," user information shown in Figure 11 is searched. If user information matching the "vehicle number" exists, user 11 (member) of that user information is extracted as a "user of a nearby vehicle." The extracted user 11 (member) is notified of the anomaly via email.

[0174] If no user information matching the "vehicle number" exists, the "user of a nearby vehicle" will be considered a non-member. Non-member users 11 will be notified of the abnormality via the pre-payment device 27 or the exit payment device 32.

[0175] The "predetermined distance" used to determine whether a vehicle is a nearby vehicle may be defined based on, for example, the type of abnormality or the location where the abnormality occurred. For example, in the case of "obstacles," "dirt," "damage," etc., vehicles located within a relatively narrow range (small predetermined distance) from the location where these abnormalities occurred will be designated as nearby vehicles. Furthermore, if these abnormalities occur in the premises passageway 43, vehicles in the vicinity of the premises passageway 43 will be designated as nearby vehicles.

[0176] For incidents such as "accidents" and "congestion," vehicles within a relatively wide range (a large predetermined distance) from the location where these anomalies occurred are designated as nearby vehicles. Furthermore, if these anomalies occur in the station passageway 43, vehicles in the vicinity (a slightly wider range) of the station passageway 43 are designated as nearby vehicles.

[0177] In the case of "fires," etc., vehicles within a wider range (a larger predetermined distance) from the location where these abnormalities occurred will be designated as nearby vehicles.

[0178] Furthermore, regarding "fires," etc., it is possible to designate all vehicles parked in parking lot 8 as "nearby vehicles" without specifying the distance from the location where the abnormality occurred. In other words, it is possible to designate all users 11 who have vehicles parked in parking lot 8 at the time the abnormality occurs as "users of nearby vehicles."

[0179] "Non-using members" are members who are not currently using Parking Lot 8, i.e., regular users 11 who are not using Parking Lot 8. For example, if Parking Lot 8 becomes unusable due to a "fire" or other reason, "non-using members" who are not using Parking Lot 8 will also be notified of the abnormality via email.

[0180] As shown in Figure 14, in this embodiment, the following information (data) is stored as abnormality type information.

[0181] "Parking No."... A number used to identify parking lot 8. In this embodiment, it is possible to define a type of abnormality for each parking lot 8, and the "Parking No." of the parking lot 8 for which the type of abnormality is defined is stored.

[0182] "Anomaly Type No."... A number used to identify the defined type of anomaly. "Anomaly Name"... The name of a defined anomaly. "Notification Recipient"... For each defined anomaly, the "Notification Recipient No." set in the notification recipient information in Figure 15 is stored sequentially starting from 01.

[0183] In the example shown in Figure 14, the following abnormalities are defined, and a notification destination is set for each abnormality.

[0184] "Fire 1" refers to a fire that occurred during a time when the "Support Center" could respond immediately. The "recipients of notification" are set to be "parking lot owners," "parking lot managers," "management staff," "management supervisors," "sales representatives," "branch managers," "support center," and "parking lot attendants" belonging to management organization 13, as well as "users of nearby vehicles" and "non-users." This setting assumes that notifications to the fire department, etc., will be made from the "Support Center."

[0185] "Fire 2" refers to a fire that occurred during hours when the "Support Center" is unavailable (e.g., late at night). The "recipients of notification" are designated as the "parking lot owner," the "parking lot manager," "parking lot supervisor," "management officer," "management supervisor," "sales representative," "branch manager," "support center," and "parking lot attendant" belonging to management organization 13, the "X Town Police Station," the "X Town Fire Station," "K Security Company," the "X Town (local government)," "users of nearby vehicles," and "non-users." In this way, during hours when the "Support Center" is unavailable, notification to the fire station, etc., will be carried out simultaneously with notification to the "Support Center."

[0186] "Accident 1" is an accident that occurred during a time when the "parking lot owner" or "support center" can respond immediately. The "recipients of notification" are set to the "parking lot owner," the "parking lot manager," "parking lot supervisor," "management officer," "management supervisor," "sales representative," "branch manager," "support center," and "parking attendant" belonging to management organization 13, as well as "users of nearby vehicles" and "non-user members." This setting assumes that notifications to police stations, etc., will be made by the "parking lot owner" or "support center."

[0187] "Accident 2" refers to an accident that occurred during a time when both the "parking lot owner" and the "support center" were unavailable (e.g., late at night). The "recipients of notification" are the "parking lot owner," the "parking lot manager," "parking lot supervisor," "management officer," "management supervisor," "sales representative," "branch manager," "support center," and "parking lot attendant" belonging to management organization 13, the "X Town Police Station," the "X Town Fire Station," "K Security Company," the "X Town (local government)," "users of nearby vehicles," and "non-user members." In this way, during times when both the "parking lot owner" and the "support center" are unavailable, notification to the police station, etc., will be carried out simultaneously with notification to the "parking lot owner" and the "support center."

[0188] In the example shown in Figure 14, it is assumed that the "parking lot owner" and the "support center" will be the initial responders when an anomaly is detected. In the case of a fire, if the "support center" is unable to respond due to its urgency, the parking lot management system 1 will also notify the fire department, etc.

[0189] In the event of an "accident," even if the "support center" is unable to respond, if the "parking lot owner" is able to respond immediately, the "parking lot owner" will be notified first. If both the "support center" and the "parking lot owner" are unable to respond, this parking management system 1 will also notify the police station, etc. Of course, in the case of an accident, as with a fire, if the "support center" is unable to respond, this parking management system 1 may also notify the police station, etc.

[0190] Furthermore, in the event of a fire or accident, parking lot 8, for example, may become unavailable, and "non-user members" will also be notified of the abnormality via email.

[0191] "Obstacle" is the type of anomaly detected when an object other than a vehicle (for example, a bicycle mistakenly parked by user 11, or a shopping cart left unattended by user 11) is detected in the premises passageway 43 or an empty parking space 44. The "recipients of notification" are set to be the "support center," "parking attendant," "K security company" to remove the obstacle, and "users of nearby vehicles."

[0192] "Congestion (Warning)" is an abnormality type that occurs when a large number of users 11 (pedestrians) are detected in areas such as the internal passageways 43 within the parking lot 8. The "recipients of notification" are set to "Support Center," "Parking Attendant," and "Users of nearby vehicles."

[0193] "Dirt"... This is an abnormality type when trash or liquids that do not disappear (do not evaporate) for a long time (such as oil) are detected in the internal passageway 43, etc., within Parking Lot 8. The "recipients of notification" are set to be the "Support Center," "Parking lot attendants," "X Cleaning Company" for cleaning, and "Users of nearby vehicles." If the "dirt" is oil, it is possible to set all vehicles parked in Parking Lot 8 as nearby vehicles and issue a warning, as it is dangerous as it can cause slipping while walking or driving.

[0194] As shown in Figure 15, in this embodiment, the following information (data) is stored as abnormal history information.

[0195] "Parking No."... A number used to identify Parking Lot 8. The "Parking No." of Parking Lot 8 where the anomaly occurred is stored here. "Anomaly Type No."... A number used to identify the type of anomaly that occurred. The "Anomaly Identification No." of the anomaly that occurred is stored here.

[0196] "Detection Date and Time"... The date and time when the anomaly was detected. In this embodiment, the time the detection result (captured image) in which the anomaly was detected is stored. Of course, the date and time when the anomaly was detected from the captured image may also be stored.

[0197] "Camera No."... A number used to identify each of the pre-payment monitoring cameras 28, entrance cameras 33, exit cameras 34, and the multiple on-site cameras 45 shown in Figure 3. The "Camera No." of the camera that captured the image in which an anomaly was detected is stored. Multiple "Camera Nos" may be stored.

[0198] "Notification Recipient"... The "Notification Recipient No." of the recipient to whom the abnormality was notified is stored sequentially starting from 01.

[0199] "Nearby Vehicles"... The license plate numbers of vehicles identified as nearby vehicles. When a notification is sent to the "Users of Nearby Vehicles" shown in Figure 13, the license plate numbers of the vehicles identified as nearby vehicles are stored.

[0200] The notification management unit 83 manages notifications to the notification targets selected by the notification target selection unit 81. The notification management unit 83 manages what kind of notifications to send to the notification targets and how to send them, and executes abnormality notifications.

[0201] For example, the notification management unit 83 determines the notification method, the notification content, and performs the notification process. For example, it performs various processes to realize notification of an anomaly occurring to the notification target, such as selecting a notification method from among arbitrary communications using the network 10, such as email or chat applications, telephone, or dedicated line communications, determining the text image to be notified, and designing a GUI for notifications.

[0202] For example, the notification management unit 83 manages notifications to target recipients by referring to notification destination information shown in Figure 13 and anomaly type information shown in Figure 14. Of course, machine learning algorithms may also be used.

[0203] The settlement processing unit 84 performs processing related to the settlement of parking fees incurred by the user 11 using the parking lot 8. For example, the settlement processing unit 84 can calculate the parking fee in response to an inquiry request from the pre-payment device 27 (exit payment device 32) and transmit it to the pre-payment device 27 (exit payment device 32).

[0204] Furthermore, the settlement processing unit 84 can perform the settlement of parking fees using the payment method selected by the user 11 in response to the request for settlement of parking fees transmitted from the user terminal 2. For example, various settlement processes can be performed, such as credit card payment, electronic money payment, code image payment, debit card payment, and point settlement processing.

[0205] The GUI generation unit 85 generates a user GUI for user 11 and sends it to user 11's user terminal 2.

[0206] The communication control unit 86 controls communication with other terminals and devices via the network 10.

[0207] [Specific examples of how the parking management system works] The specific operation examples of this parking management system 1 will be explained by referring to the flowcharts shown in Figures 17 to 22 and the GUIs displayed on each device shown in Figures 23 to 30.

[0208] (Vehicle entry) Figure 17 is a flowchart showing an example of the operation when a vehicle enters the parking lot. The vehicle detection unit 66 of the parking lot control device 9 monitors for the detection of an entering vehicle 37 (step 201). If an entering vehicle 37 is detected (YES in step 201), an image of the entering vehicle is taken by the entrance camera 33 (step 202).

[0209] The entrance gate 30 is opened (step 203). The vehicle detection unit 66 monitors whether or not the entering vehicle 37 has passed through the entrance gate 30 (step 204). If the entering vehicle 37 has passed through the entrance gate 30 (YES in step 204), an image of the entering vehicle is transmitted to the parking management device 5 along with the date and time of entry (step 205). Then the entrance gate 30 is closed (step 206).

[0210] The parking management device 5 receives an image of an entering vehicle (step 207). The vehicle information recognition unit 78 extracts the vehicle number as information about the entering vehicle (step 208).

[0211] The user information management unit 77 searches for user information shown in Figure 11 based on the extracted vehicle number (step 209). If user information matching the vehicle number exists, that user information is output to the parked vehicle information management unit 79.

[0212] The parking vehicle information management unit 79 generates the parking vehicle information shown in Figure 12 (step 210). Specifically, the "parking lot number," "vehicle number," "vehicle type," and "date and time of entry" are stored. If user 11 is a member, the "membership number" included in the user information output from the user information management unit 77 is also stored.

[0213] (Vehicle departure) Figure 18 is a flowchart showing an example of the operation when a vehicle exits the parking lot. The vehicle detection unit 66 of the parking lot control device 9 monitors for the detection of the exiting vehicle 38 (step 301). If the exiting vehicle 38 is detected (YES in step 301), the exit camera 34 takes an image of the exiting vehicle (step 302).

[0214] The entry / exit processing unit 69 of the parking control device 9 transmits an image of the exiting vehicle to the parking management device 5, and user information and payment information are checked (step 303).

[0215] The parking management device 5 determines whether the user is a member and whether payment has been completed (step 304). Specifically, the vehicle information recognition unit 78 extracts the vehicle number as exiting vehicle information from the exiting vehicle image. Based on the extracted vehicle number, the user information shown in Figure 11 is searched, and if user information matching the vehicle number exists, the user is determined to be a member. If no user information matching the vehicle number exists, the user is determined to be a non-member.

[0216] Furthermore, based on the extracted vehicle number, the parked vehicle information shown in Figure 12 is searched, and it is checked whether the "parking fee" and "settlement date and time" are stored. If the "parking fee" and "settlement date and time" are stored, it is determined that settlement has been completed. If the "parking fee" and "settlement date and time" are not stored, it is determined that settlement has not been completed.

[0217] Information regarding whether the user is a member and whether payment has been made is transmitted from the parking management device 5 to the parking control device 9. Then, the entry / exit processing unit 69 determines whether or not the user is allowed to exit (step 305).

[0218] If user 11 driving the exit vehicle 38 is a member, then user 11 is a regular user, and it is determined that they are allowed to exit (YES in step 305), and the exit gate 31 is opened (step 306).

[0219] If user 11 driving vehicle 38 is not a member and payment has been made, it is determined that they are allowed to exit (YES in step 305), and exit gate 31 is opened (step 306).

[0220] For example, if a non-member user 11 has already paid the parking fee for the exiting vehicle 38 using the pre-payment device 27 or user terminal 2, step 305 will be YES and the exit gate 31 will be opened.

[0221] If payment has not been made by user 11, who is a non-member, it is determined that they are not allowed to exit (NO in step 305), and the exit payment device 32 issues a notification of non-payment (step 307). For example, a display or voice output such as "Payment has not been made. Please pay using the exit payment device or your smartphone" is issued.

[0222] The system monitors whether user 11 completes payment at the exit payment device 32 (step 308). If payment is completed at the exit payment device 32 (YES in step 308), the exit gate 31 is opened (step 306).

[0223] Furthermore, payment of parking fees using the exit payment device 32 can be done in the same way as advance payment of parking fees using the advance payment device 27.

[0224] If the completion of payment at the exit payment device 32 has not been confirmed (NO in step 308), the process returns to step 303, and a request for payment information is made to the parking management device 5.

[0225] If user 11 pays the parking fee for the exiting vehicle 38 using user terminal 2, the vehicle can exit at step 305 and the exit gate 31 opens (step 306).

[0226] The vehicle detection unit 66 monitors whether the exiting vehicle 38 has passed through the exit gate 31 (step 309). If the exiting vehicle 38 has passed through the exit gate 31 (YES in step 309), exit information, including that the exiting vehicle 38 has exited and the date and time of exit, is transmitted to the parking management device 5 (step 310). Then, the exit gate 31 is closed (step 311).

[0227] The parking management device 5 receives exit information and updates the parked vehicle information (step 312). Specifically, the "exit date and time" is stored.

[0228] (Detection of anomalies) Figure 19 is a flowchart showing an example of monitoring for abnormalities by the parking management device 5. The abnormality determination unit 80 acquires the detection result from the sensor unit 47 (step 401). In this embodiment, images captured by the pre-payment monitoring camera 28, the entrance camera 33, the exit camera 34, and the multiple in-parking cameras 45 are acquired.

[0229] These cameras can be collectively referred to as surveillance cameras. Furthermore, the images captured by these cameras can be referred to as surveillance images.

[0230] The abnormality determination unit 80 determines the type of abnormality that occurred in or around the parking lot 8 based on the detection results of the sensor unit 47 (step 402). In this embodiment, the type of abnormality is determined based on the images captured by the pre-payment monitoring camera 28, the entrance camera 33, the exit camera 34, and the multiple in-parking cameras 45.

[0231] Figures 23 and 24 are schematic diagrams showing examples of images captured by the on-site camera 45. The captured image 92a shown in Figure 23A captures multiple vehicles 93 parked on either side of the on-site passageway 43, and three pedestrians 94. Captured image 92a is illustrated as an example of an image showing a state in which no particular abnormality has occurred.

[0232] The photograph 92b shown in Figure 23B captures smoke 95 rising from the front of the premises passageway 43. Photograph 92b is illustrated as an example of a photograph showing a "fire" in progress.

[0233] The image 92c shown in Figure 24A shows a bicycle 96 abandoned in the premises passageway 43. Image 92c is illustrated as an example of an image showing a state where an "obstacle" is present.

[0234] The captured image 92d shown in Figure 24B captures many pedestrians 94. Captured image 92d is illustrated as an example of an image that shows a state of "congestion".

[0235] Figures 25 and 26 are schematic diagrams showing examples of monitoring GUIs displayed on the management agency terminal 4 and the staff terminal 26.

[0236] In this embodiment, when an operator 14 of the management organization 13 operates the management organization terminal 4 and activates the monitoring mode, the monitoring screen 98 shown in Figure 25 can be displayed. Similarly, when an attendant of the parking lot 8 operates the attendant terminal 26 and activates the monitoring mode, the monitoring screen 98 shown in Figure 25 can be displayed.

[0237] A camera switching button 99 is provided on the monitoring screen 98. The operator 14 and staff can switch the captured image (monitoring image) 92 displayed on the monitoring screen 98 to a captured image (monitoring image) 92 taken by the desired camera by selecting the camera switching button 99 as appropriate.

[0238] In the example shown in Figure 25A, image 92a is displayed, showing no particular abnormality. If no particular abnormality occurs, in step 403 shown in Figure 19, it is determined that no abnormality is detected (NO) as a result of the abnormality type determination, and the process returns to step 401.

[0239] In the example shown in Figure 25A, a frame surrounding a pedestrian 94 is depicted in the captured image 92c as a result of the person detection process. Thus, in this embodiment, person detection and object detection are performed on the acquired captured image 92, and the detection results are displayed as a frame.

[0240] To make this point easier to understand intuitively, frames are shown in the captured images 92a to 92d in Figures 23 and 24, surrounding the pedestrian 94, smoke 95, and bicycle 96. These frames are displayed as a result of person detection and object detection performed by the anomaly detection unit 80. Of course, person detection and object detection are not essential for the application of the present invention.

[0241] If the type of abnormality is output in step 402, it is determined in step 403 that an abnormality has been detected (YES), and the notification target selection unit 81 selects the notification target to be notified of the occurrence of the abnormality based on the determined type of abnormality (step 404). In this embodiment, the notification target selection unit 81 refers to the notification destination information shown in Figure 13 and the abnormality type information shown in Figure 14, and selects the notification target.

[0242] Then, the notification management unit 83 sends a notification to the notification recipients selected by the notification recipient selection unit 81 (step 405). The notification management unit 83 may also display a message indicating that an abnormality has occurred on the guidance device 29 located in the parking lot 8, regardless of the type of abnormality. In addition to notifying of the occurrence of an abnormality, the notification management unit 83 may also trigger an alarm to the fire extinguishing equipment in the parking lot 8, etc.

[0243] If an image 92b showing smoke 95 rising, as shown in Figure 23B, is captured, the abnormality detection unit 80 determines in step 402 that a "fire" has occurred. In other words, "fire" is determined to be the type of abnormality that occurred in the parking lot 8. Here, it is assumed that "fire 2" is determined to be a fire that occurred during a time when the "support center" is unavailable (e.g., late at night).

[0244] If the type of abnormality is determined to be "Fire 2," the following will be selected as recipients of notification: "Parking lot owner," "Parking lot manager," "Management staff," "Management supervisor," "Sales staff," "Branch manager," "Support center," and "Parking attendant" belonging to Management Organization 13, "X Town Police Station," "X Town Fire Station," "K Security Company," "X Town (Municipality)," "Users of nearby vehicles," and "Non-user members."

[0245] As shown in Figure 25B, an alarm screen 100 indicating that a fire has been detected is displayed on the management agency terminal 4 (personnel terminal 26). The alarm screen 100 is a screen that is automatically displayed when an abnormality is detected, and a captured image 92b showing smoke 95 rising is automatically displayed. The alarm screen 100 also displays text indicating that a fire has been detected, along with the time the fire was detected.

[0246] Additionally, an icon containing the text "Anomaly Detection Information" is highlighted on the alarm screen 100. The alarm screen 100 also displays the notification history to other notification recipients. In the example shown in Figure 25B, it is displayed that notifications were automatically sent to "X Town Fire Station," "X Town Police Station," "X Town (Municipality)," "K Security Company," and "Users of Nearby Vehicles," along with the notification time.

[0247] Along with the display of alarm screen 100, an alarm sound or other audio signal may be output. Since "parking lot owner" is selected as the notification target, the same alarm screen will also be automatically displayed on owner terminal 3.

[0248] If an image 92c is taken showing a bicycle 96 abandoned in the premises passageway 43, as shown in Figure 24A, the abnormality determination unit 80 determines in step 402 that an "obstacle" has occurred. In other words, "obstacle" is determined to be the type of abnormality that occurred in the parking lot 8.

[0249] If the type of anomaly is determined to be "obstacle," the following will be selected as recipients of notification: "Support Center," "Parking Attendant," "K Security Company," and "Users of nearby vehicles."

[0250] As shown in Figure 25C, an alarm screen 100 containing information indicating that an obstacle has been detected is automatically displayed on the management agency terminal 4 (staff terminal 26). The alarm screen 100 automatically displays a photograph 92b showing a bicycle 96 left unattended in the premises passageway 43. The alarm screen 100 also displays text indicating that an obstacle has been detected, along with the time the obstacle was detected.

[0251] As shown in Figure 25C, the notification history for other recipients displays that notifications were automatically sent to "K Security Company" and "Users of nearby vehicles," along with the notification time.

[0252] If an image 92d is captured showing many pedestrians 94, as shown in Figure 24B, the abnormality determination unit 80 determines in step 402 that "congestion (warning)" has occurred. In other words, "congestion (warning)" is determined to be the type of abnormality that occurred in the parking lot 8.

[0253] If the type of abnormality is determined to be "congestion (warning)," the following will be selected as recipients of notification: "support center," "parking attendant," and "users of nearby vehicles."

[0254] As shown in Figure 26, an alarm screen 100 containing a message indicating that congestion has been detected is automatically displayed on the management agency terminal 4 (staff terminal 26). The alarm screen 100 automatically displays a captured image 92d showing many pedestrians 94. The alarm screen 100 also displays text indicating that congestion has been detected, along with the time the congestion was detected.

[0255] As shown in Figure 26, the notification history for other notification recipients displays that a notification was automatically sent to "users of nearby vehicles," along with the notification time.

[0256] (Notification to users of nearby vehicles) Figure 20 is a flowchart showing an example of notification to a user 11 of a nearby vehicle. First, a nearby vehicle is identified from the captured image 92 in which the anomaly was detected (step 501). As mentioned above, the "predetermined distance" used as the criterion for determining whether or not it is a nearby vehicle may be appropriately defined based on, for example, the type of anomaly or the location where the anomaly occurred.

[0257] The license plate numbers of identified nearby vehicles are extracted (step 502). First, the license plate numbers of nearby vehicles are extracted from the captured image 92 in which the anomaly was detected. However, depending on the angle from which the nearby vehicles are photographed and whether they overlap with other vehicles, it may not be possible to extract the license plate numbers of some nearby vehicles. In such cases, it is also possible to extract the license plate numbers of the nearby vehicles identified in step 501 from other captured images 92 taken by other cameras.

[0258] In the present embodiment, a "camera No." is assigned to each of the pre-payment monitoring camera 28, the entrance camera 33, the exit camera 34, and the plurality of on-site cameras 45, and the position information of each camera is retained. Therefore, based on the "camera No." of the camera that captured the captured image 92 in which an abnormality is detected, it is possible to search for other captured images 92 in which neighboring vehicles within the captured image 92 with the detected abnormality are captured. It is possible to extract the vehicle number of the neighboring vehicle based on the retrieved other captured images 92.

[0259] A neighboring vehicle is identified from another captured image 92 different from the captured image 92 in which the abnormality is detected (step 503). Depending on the type of abnormality and the position where the abnormality occurs, a vehicle that is not captured in the captured image 92 with the detected abnormality may fall under the neighboring vehicle.

[0260] For example, when an abnormality occurs in the on-site passage 43 or the like, and a vehicle adjacent to the on-site passage 43 is set as a neighboring vehicle, a vehicle that is not captured in the captured image 92 in which the abnormality is detected may fall under the neighboring vehicle.

[0261] Further, when all vehicles parked in the parking lot 8 are set as neighboring vehicles in the event of a "fire" or the like, a vehicle that is not captured in the captured image 92 in which the abnormality is detected may fall under the neighboring vehicle.

[0262] In step 502, such neighboring vehicles are identified from other captured images 92. Note that the identification of the neighboring vehicle in step 503 can be executed based on, for example, the "camera No." of the camera that captured the captured image 92 in which the abnormality is detected, the positions of other cameras, and the like.

[0263] The vehicle number of the neighboring vehicle identified from the other captured image 92 is extracted (step 504).

[0264] In steps 502 and 504, one vehicle number is selected from the extracted vehicle numbers (step 505). It is then determined whether the vehicle with the selected vehicle number belongs to a member (step 506).

[0265] Specifically, the parking vehicle information management unit 79 searches for user information shown in Figure 11 based on the selected vehicle number. If user information matching the vehicle number exists, it is determined to be the member's vehicle. If no user information matching the vehicle number exists, it is determined that it is not the member's vehicle.

[0266] If the vehicle with the selected license plate number belongs to a member (YES in step 506), the member is notified of the anomaly (step 507). In this embodiment, an email indicating the occurrence of an anomaly is sent to the "email address" in the user information from a dedicated email account for "○○ Station Front Parking Lot No. 1".

[0267] Figure 27 is a schematic diagram illustrating an example of an anomaly notification sent to a member via email. Figure 27A shows an anomaly notification email 102 when "congestion" is detected. Notification email 102 displays text to alert the user 11, including that the parking lot 8 is congested and a warning to be careful. Notification email 102 also has a photograph 92d showing the detected "congestion" attached for visual confirmation.

[0268] Figure 27B illustrates the notification email 102 for an abnormality that occurs when an "obstacle" is detected. The notification email 102 displays text to alert the user 11, including that an obstacle has been left in the passageway 43 of the parking lot 8 and a warning to be careful. The notification email 102 also has a photographic image 92b of the detected "obstacle" attached for visual confirmation.

[0269] If other anomalies are detected, notification emails will be sent to inform users of the occurrence of the anomalies, as illustrated in Figures 27A and 27B. The specific content of these anomaly notification emails is not limited and can be configured as desired.

[0270] In this embodiment, if a user 11 who has entered notification recipient information (email address) is selected as a notification recipient, the notification management unit 83 notifies the user 11 of the occurrence of the abnormality based on the notification recipient information (email address). This makes it possible to provide appropriate information to the member user 11, improving the convenience for the user 11.

[0271] Returning to Figure 20, if the vehicle with the selected vehicle number is not owned by a member (NO in step 506), the vehicle number is stored in DB15 as information to be notified of an anomaly (step 508). If the owner of the nearby vehicle is a non-member user 11, the email address is unknown, and the vehicle number to be notified is stored as information to be notified of an anomaly.

[0272] Step 509 determines whether all vehicle numbers extracted in steps 502 and 504 have been selected. If there are any unselected vehicle numbers remaining (step 509 NO), the process returns to step 505. If all vehicle numbers have been selected (step 509 YES), the process ends.

[0273] (Payment of parking fees by non-members) Figure 21 is a flowchart illustrating an example of operation when a non-member user 11 makes a prepayment using the prepayment device 27. The flowchart shown in Figure 21 will be explained while referring to the GUI displayed on the touch panel 59 of the prepayment device 27 (exit payment device 32) shown in Figure 28.

[0274] When the motion sensor 61 of the pre-payment device 27 detects a user 11 standing in front of the pre-payment device 27, the top screen 104 shown in Figure 28A is displayed.

[0275] When user 11 selects the "Payment button" on the top screen 104, the vehicle search screen 105 shown in Figure 28B is displayed. User 11 enters the vehicle number (4 digits) of the parked vehicle on the vehicle search screen 105 and selects the "Search button".

[0276] The settlement processing unit 63 of the pre-payment device 27 transmits a request for inquiry regarding parking fees, along with the vehicle number, to the parking management device 5 via the parking control device 9 (step 601).

[0277] The parking vehicle information management unit 79 of the parking management device 5 searches for the parking vehicle information shown in Figure 12 based on the received vehicle number (step 602). Then, parking vehicle information that matches the received vehicle number is extracted.

[0278] The method for searching for parked vehicles is not limited; for example, user 11 can input the date and time of entry, and the system can search for parked vehicles based on that input. Alternatively, the pre-payment device 27 can display candidate images of parked vehicles, and user 11 can select their own vehicle from the candidate images.

[0279] The parking fee is calculated by the settlement processing unit 84 of the parking management device 5. In this embodiment, the parking fee is calculated according to a predetermined fee system based on the "entry date and time" stored in the parked vehicle information and the date and time of receipt of the vehicle number. The calculated parking fee is transmitted to the pre-payment device 27 (step 603).

[0280] The parking fee is displayed on the touch panel 59 of the pre-payment device 27 (step 604). In this embodiment, the payment screen 106 shown in Figure 28C is displayed. The payment screen 106 displays the "Date and Time of Entry," "Image of the Entering Vehicle," "Parking Fee," buttons for selecting the payment method, and an "Electronic Receipt" button. By viewing the payment screen 106, the user 11 can confirm whether their vehicle has been correctly selected and to verify the parking fee.

[0281] User 11 pays the parking fee by any one of cash payment, credit card settlement (selection of the "Card" button), electronic money settlement (selection of the "Electronic Money" button), and code settlement (selection of the "Code" button).

[0282] The settlement processing unit 63 of the pre-settlement device 27 executes the settlement of the parking fee by the settlement method selected by the user 11. Further, the settlement processing unit 63 transmits, as the settlement information, information indicating that the settlement is completed, the settled parking fee, and the settlement date and time to the parking lot management device 5 (Step 605).

[0283] The parked vehicle information management unit 79 updates the parked vehicle information shown in FIG. 12 (Step 606). Specifically, "Parking Fee" and "Settlement Date and Time" are stored based on the information transmitted from the pre-settlement device 27.

[0284] The notification management unit 83 determines whether or not the vehicle number received in Step 602 is held as abnormality notification target information in Step 508 of FIG. 20 (Step 607).

[0285] When the received vehicle number is held as the abnormality notification target information (YES in Step 607), notification of occurrence of an abnormality is executed via the pre-settlement device 27 (Step 608). Specifically, data for notifying the non-member user 11 of the abnormality is generated and transmitted to the pre-settlement device 27.

[0286] When the received vehicle number is not held as the abnormality notification target information (NO in Step 607), the processing of the parking lot management device 5 ends.

[0287] The pre-settlement device 27 determines whether or not there is an abnormality notification (Step 609). When the data for notifying the abnormality is received from the parking lot management device 5, it is determined that there is an abnormality notification (YES). Then, the settlement completion screen 107 including the abnormality notification shown in FIG. 28D is displayed on the touch panel 59 of the pre-settlement device 27 (Step 610).

[0288] The settlement completion screen 107, which includes the anomaly notification, displays text indicating that the settlement has been completed. The settlement completion screen 107 also displays, for example, the captured image 92 in which the anomaly was detected, a description of the anomaly that occurred, and text to draw attention to the issue.

[0289] In the example shown in Figure 28D, the payment completion screen 107 displays text to alert the user 11, including a statement that the parking lot 8 is crowded and a warning to the user. The payment completion screen 107 also displays the captured image 92d in which "crowding" was detected. Of course, the specific configuration of the payment completion screen 107, including the abnormality notification, is not limited and can be designed arbitrarily.

[0290] Furthermore, the data used to notify of an anomaly can also be considered the data used to construct the settlement completion screen 107, which includes the anomaly notification, as shown in Figure 28D. The settlement completion screen, which includes the anomaly notification, can also be referred to as the anomaly notification screen.

[0291] If no data to notify of an abnormality is received from the parking management device 5, it is determined that there is no abnormality notification (NO). In this case, for example, a normal payment completion screen (not shown) that does not include an abnormality notification is displayed on the touch panel 59, and the processing of the pre-payment device 27 is completed (step 611).

[0292] Of course, the pre-payment device 27 may also inquire with the parking management device 5 about whether or not an abnormality notification has been sent.

[0293] Payment at the exit lane 24 using the exit payment device 32, while the vehicle 38 is still inside, can also be performed using a flow similar to that shown in Figure 21. Notification of abnormalities via the exit payment device 32 is particularly effective when notifying of abnormalities occurring around the parking lot 8. Of course, it is not limited to such cases.

[0294] Figure 22 is a flowchart illustrating an example of the operation when a non-member user 11 uses user terminal 2 for payment. The flowchart shown in Figure 22 will be explained while referring to the GUI displayed on user terminal 2 shown in Figures 29 and 30.

[0295] In this parking management system 1, the GUI generation unit 85 of the parking management device 5 provides the user 11 with a user GUI as exemplified in Figures 29 and 30. The user GUI is displayed on the touch panel of the user terminal 2 via a web browser.

[0296] First, non-member users 11 use user terminal 2 to scan a code image (such as a QR code) for parking fee payment displayed on the guidance device 29 or signs. As a result, the vehicle search screen 109 shown in Figure 29A is displayed on the touch panel of user terminal 2 as a user GUI.

[0297] User 11 enters the vehicle number (4 digits) of the parked vehicle into the vehicle search screen 109 and selects the "Search button". Then, a request for payment of parking fees, along with the vehicle number, is sent from the user terminal 2 to the parking management device 5 (step 701).

[0298] The parking vehicle information management unit 79 of the parking management device 5 searches for the parking vehicle information shown in Figure 12 based on the received vehicle number (step 702). Then, parking vehicle information that matches the received vehicle number is extracted.

[0299] The GUI generation unit 85 of the parking management device 5 generates a payment confirmation GUI and sends it to the user terminal 2 (step 703). The user terminal 2 receives the payment confirmation GUI and displays it on the touch panel (step 704).

[0300] In this embodiment, the vehicle verification screen 110 shown in Figure 29B is displayed first. The vehicle verification screen 110 displays the "entering vehicle image," "entry date and time," "entry gate," and "vehicle information (vehicle number)." After confirming that it is their vehicle, the user 11 selects the "Confirm" button.

[0301] This will display the payment confirmation screen 111 shown in Figure 29C. The payment confirmation screen 111 displays information such as "parking time," "parking fee," "parking lot name," "entry date and time," "vehicle information (vehicle number)," radio buttons for selecting the payment method, and "credit card" information.

[0302] User 11 can confirm the payment details by viewing the payment details confirmation screen 111. If there are no problems with the payment details, the user selects the appropriate payment method and then selects the "Pay" button. At this point, a payment instruction for the parking fee is sent from the user terminal 2 to the parking management device 5 (step 705).

[0303] The settlement processing unit 84 of the parking management device 5 processes the payment of the parking fee using the payment method selected by the user 11. The parking vehicle information management unit 79 also updates the parking vehicle information shown in Figure 12 (step 706). Specifically, the "parking fee" and "settlement date and time" are stored.

[0304] The notification management unit 83 determines whether the vehicle number received in step 702 is held as information subject to notification of an anomaly in step 508 of Figure 20 (step 707).

[0305] If the received vehicle number is retained as information to be notified of an anomaly (YES in step 707), notification of the occurrence of an anomaly is sent via the pre-payment device 27 (step 708).

[0306] If the received vehicle number is not stored as information to be notified of an anomaly (NO in step 707), the processing of the parking management device 5 ends.

[0307] The pre-payment device 27 determines whether or not there is an abnormality notification (step 709). If there is an abnormality notification from the parking management device 5 (YES in step 709), the payment completion screen 112, which includes the "Warning" button shown in Figure 29D, is displayed (step 710).

[0308] The payment completion screen 112, which includes a "Warning" button, displays text indicating that payment is complete, text urging the user to exit within 5 minutes, and an electronic receipt. The electronic receipt can be viewed in its entirety by scrolling as needed.

[0309] Non-member users 11 can display the abnormal notification screen 113 shown in Figure 30A by selecting the "Warning" button on the settlement completion screen 112.

[0310] In the example shown in Figure 30A, the abnormality notification screen 113 displays text to alert the user 11, including a statement that the parking lot 8 is crowded and a warning to be careful. The abnormality notification screen 113 also displays the captured image 92d in which "crowding" was detected. Of course, the specific configuration of the abnormality notification screen 113 is not limited and can be designed arbitrarily.

[0311] If there is no abnormality notification from the parking management device 5 (NO in step 709), a payment completion screen without the "Warning" button is displayed (step 711). For example, a screen is displayed that is the same as the payment completion screen 112 shown in Figure 29D, but with the "Warning" button removed.

[0312] In this embodiment, the parking management system 1 is equipped with a payment device that accepts payment operations for parking fees, including the input of vehicle information (vehicle number), by non-member users 11. In this embodiment, the pre-payment device 27 and the exit payment device 32, which are parking fee payment devices located in the parking lot 8, and the user terminal 2 of user 11 correspond to said payment devices.

[0313] The notification target selection unit 81 then determines, based on the vehicle information (vehicle number) entered into the payment device, whether or not the user 11 who entered the payment operation has been selected as a notification target. The notification management unit 83 also notifies the user 11 of the abnormality via the payment device if the user 11 who entered the payment operation has been selected as a notification target. This makes it possible to provide appropriate information to non-member users 11 as well, improving user convenience.

[0314] Figure 30B is a schematic diagram illustrating an example of an abnormality notification via email to "non-user members," who are members who are not currently using Parking Lot 8. For example, in the event of a fire or accident, Parking Lot 8 may become unusable, and "non-user members" who are not using Parking Lot 8 will also be notified of the abnormality via email.

[0315] Figure 30B illustrates the notification email 114 that appears when a "fire" is detected. The notification email 114 contains text indicating that a fire has broken out in parking lot 8, that parking lot 8 is closed, and that relevant authorities are responding to the fire. Furthermore, notification email 114 includes a clearly visible attached image 92b showing the detection of a "fire."

[0316] Of course, the specific content of the notification email sent to "non-user members" who do not use parking lot 8 is not limited and can be set arbitrarily. By notifying "non-user members" of the occurrence of an anomaly based on the type of anomaly, it is possible to improve the convenience of users 11.

[0317] Returning to Figure 19, the anomaly-related information management unit 82 generates the anomaly history information shown in Figure 15 and saves it to DB 15 (step 406). It is also possible to store the anomaly notification content and the captured image 92 in which the anomaly was detected as anomaly detection data.

[0318] For example, the captured images 92 taken by each surveillance camera are normally temporarily stored in a buffer and then deleted. If an anomaly is detected, the captured image 92 in which the anomaly was detected, as well as the captured images 92 within a predetermined time before and after the timing of the anomaly detection, are saved as anomaly detection data. In addition, captured images 92 from other cameras within a predetermined time before and after the timing of the anomaly detection may also be saved as anomaly detection data. Of course, a camera may be selected to save the captured images 92 as anomaly detection data based on the type of anomaly.

[0319] (Settings for abnormality types and variations in abnormality occurrence notifications) In the anomaly type information shown in Figure 14, the type of anomaly was set based on factors such as whether the "parking lot owner" or "support center" was available for immediate response during that time. In this way, it is possible to set different anomaly types based on time.

[0320] This is not limited to this; it is possible to appropriately define the type of anomaly based on the circumstances under which the anomaly occurs, its scale, location, and timing.

[0321] For example, regarding the occurrence of a fire, it is possible to set different types of anomalies depending on the scale and circumstances of the fire. For instance, if smoke 95 is captured in image 92 and the measured temperature is low, it can be set as "Fire 3". If flames are captured in image 92 and the measured temperature is high, it can be set as "Fire 4". Such types of anomaly settings are possible. By appropriately setting the notification targets for each anomaly type, it becomes possible to provide appropriate notifications according to the scale and circumstances of the fire.

[0322] Furthermore, regarding the occurrence of an accident, it is possible to set different types of anomalies depending on the scale and circumstances of the accident. For example, if the captured image 92 in which the accident was detected does not show any people and is determined to be a property damage accident, it will be set to "Accident 3". If the captured image 92 in which the accident was detected shows a person who was injured and is determined to be a personal injury accident, it will be set to "Accident 4". By appropriately setting the notification target for each type of anomaly, it is possible to achieve appropriate notifications according to the scale and circumstances of the accident.

[0323] Regarding notifications of abnormal occurrences, for example, notifications can first be sent to the "parking lot owner" or "support center." If, after a predetermined time has elapsed, no notification is received from the designated notification agencies 7 (such as the police or fire department), then the parking lot management system 1 will notify the agencies 7. Such settings are also possible. Whether or not a notification is received from the notification agencies 7 within the predetermined time can be determined, for example, by setting a threshold for response time. The specific value (time) of the threshold is not limited and can be set arbitrarily.

[0324] Regarding notifications of abnormal occurrences via email to "non-user members" who are not currently using parking lot 8, as illustrated in Figure 30B, it is also possible to send notifications of the suspension of parking lot 8 use along with information on alternative parking.

[0325] For example, by referring to the parking information shown in Figure 9 and the user information shown in Figure 11, it is possible to select a parking lot 8 near the parking lot 8 for which a regular usage contract has been concluded (parking lot 8 for which a notice of discontinuation of use has been received) as an alternative parking lot. Alternatively, it is also possible to select a parking lot 8 near the user's home as an alternative parking lot.

[0326] For user 11, the alternative parking lot is not under a regular usage contract and is not registered in the user information. For example, if user 11 is notified of the alternative parking lot, a temporary registration for regular use (registration in the user information) may be made (until the regular parking lot 8 becomes available) so that user 11 can use the alternative parking lot. Alternatively, it is possible to allow them to enter as a regular user and have the parking fee waived.

[0327] Thus, this parking management system 1 can automatically notify users of the occurrence of anomalies, such as suspending parking use or restricting entry and exit, based on the type of anomaly, and also guide them to other parking lots 8. This improves the convenience of users 11. It also improves the operational efficiency of parking lot 8.

[0328] If there are affiliated stores located near Parking Lot 8, it is possible to notify the staff of those stores of any abnormalities. This allows for a swift response to any abnormalities.

[0329] If the anomaly that occurs relates to a vehicle parked in parking space 44, the type of anomaly may be determined and the target of notification may be selected based on the type of parked vehicle. For example, the type of anomaly may be distinguished or the target of notification may be set differently depending on whether the vehicle involved in the anomaly is a gasoline vehicle, a hybrid vehicle, or an electric vehicle.

[0330] If the captured image 92 in which an anomaly was detected, or the captured images 92 within a predetermined time period before and after the timing of the anomaly detection, are saved as anomaly detection data, it is also possible to submit the anomaly detection data to the notification recipient organization 7 as needed. This enables the notification recipient organization to respond efficiently to the occurrence of anomalies.

[0331] In the parking management system 1 according to this embodiment, the type of abnormality that occurred in or around the parking lot 8 is determined based on the detection results of the sensor unit 47. Based on the determined type of abnormality, the notification recipients are selected from among the users 11 of the parking lot 8, the owners 12 of the parking lot 8, and the management organization 13 that manages the parking lot 8. This makes it possible to respond effectively to the occurrence of abnormalities.

[0332] By applying this invention, it becomes possible to respond quickly and appropriately to any abnormalities detected in or around parking lot 8. For example, it can solve problems caused by delays in detecting and notifying abnormalities during times when security personnel are absent, such as at night.

[0333] Furthermore, based on the AI's detection of anomalies, it becomes possible to efficiently and automatically notify relevant parties, warn users 11 of parking lot 8, restrict entry and exit to parking lot 8, and direct users to other parking lots, thereby enabling the proper operation of parking lot 8.

[0334] Furthermore, for example, in the management of parking lots in commercial facilities and office buildings, it is possible to streamline responses to abnormal situations at night or when security guards are absent, thereby improving management efficiency. In addition, because it has a function to quickly notify the police, fire department, parking lot owners, security companies, and cleaning companies, it can also be used for parking lot management at facilities and event venues that require safety and emergency response functions. In this way, the present invention can contribute to improving the efficiency and safety of parking lot operations in various industrial fields.

[0335] <Other Embodiments> The present invention is not limited to the embodiments described above, and various other embodiments can be realized.

[0336] It is also possible to incorporate some or all of the functions of the parking management device 5 shown in Figure 8 into the parking control device 9 located in the parking lot 8. For example, the abnormality determination unit 80, notification target selection unit 81, and abnormality-related information management unit 82 shown in Figure 8 may be incorporated into the parking control device 9. The parking control device 9 may then perform abnormality type determination and notification of abnormality occurrence.

[0337] The configuration of the parking lot 8 to which the present invention can be applied is not limited, and the present invention can be applied to any configuration of parking lot 8. For example, the present invention can be applied to a parking lot 8 that has a flap device (locking device) installed instead of a gate to restrict exit from a parking space without payment. The present invention can also be applied to gateless parking lots 8 that do not have a gate device, and to flapless parking lots 8 that do not have a flap device. Furthermore, the present invention is not limited to ticketless parking lots, but can also be applied to parking lots 8 that issue parking tickets.

[0338] In this disclosure, any moving object containing one or more wheels, such as an automobile, bicycle, motorcycle, tricycle, or electric scooter, is included in the definition of "vehicle." Furthermore, a facility where "vehicles" can be parked is included in the definition of "parking lot." Accordingly, a bicycle parking area where bicycles can be parked is included in the definition of "parking lot" according to the present invention.

[0339] Figure 31 is a block diagram showing an example of the hardware configuration of a computer 140 that can be used as a user terminal 2, a parking management device 5, etc.

[0340] The computer 140 includes a CPU 141, ROM 142, RAM 143, an input / output interface 145, and a bus 144 connecting these to each other. The input / output interface 145 is connected to a display unit 146, an input unit 147, a storage unit 148, a communication unit 149, and a drive unit 150, among others. The display unit 146 is a display device using, for example, liquid crystal, EL, etc. The input unit 147 is, for example, a keyboard, pointing device, touch panel, or other operating device. If the input unit 147 includes a touch panel, the touch panel may be integrated with the display unit 146. The storage unit 148 is a non-volatile storage device, such as an HDD, flash memory, or other solid-state memory. The drive unit 150 is a device capable of driving a removable recording medium 151, such as an optical recording medium or magnetic recording tape. The communication unit 149 is a modem, router, or other communication device that can connect to a LAN, WAN, etc., for communicating with other devices. The communication unit 149 may use either wired or wireless communication. The communication unit 149 is often used separately from the computer 140. Information processing by the computer 140 having the hardware configuration described above is realized through the cooperation of software stored in the memory unit 148 or ROM 142, etc., and the hardware resources of the computer 140. Specifically, the parking lot management method (information processing method) according to the present invention is realized by loading the programs constituting the software, which are stored in the ROM 142, etc., into the RAM 143, and then having the CPU 141 control and execute them. The program is installed on the computer 140, for example, via a recording medium 151. Alternatively, the program may be installed on the computer 140 via a global network or the like. In addition, any non-transient storage medium that is readable by a computer may be used.

[0341] Multiple computers connected to each other via a network or the like can collaborate to execute the parking management method and program according to the present invention, thereby constructing a parking management system or parking management device according to the present invention. In other words, the parking lot management method and program according to the present invention can be executed not only in a computer system consisting of a single computer, but also in a computer system in which multiple computers operate in conjunction. In this disclosure, "system" means a collection of multiple components (devices, modules (parts), etc.), regardless of whether all components are located in the same enclosure. Therefore, multiple devices housed in separate enclosures and connected via a network, and a single device containing multiple modules in one enclosure, are both considered systems.

[0342] The execution of the parking management method and program according to the present invention by a computer system includes both cases where, for example, the determination of the type of abnormality, the selection of notification targets, notification of abnormality occurrence, generation and management of each piece of information, and generation of each GUI are performed by a single computer, and cases where each process is performed by different computers. Furthermore, the execution of each process by a predetermined computer includes having another computer execute part or all of the process and obtaining the results. In other words, the parking lot management method and program according to the present invention can also be applied to a cloud computing configuration in which a single function is shared and processed jointly by multiple devices via a network.

[0343] The parking management system, user terminals, owner terminals, management agency terminals, parking management devices, parking control devices, pre-payment devices, exit payment devices, and other terminals and devices, as well as the configurations of the user GUI, the operations performed by the user terminals, owner terminals, management agency terminals, parking management devices, parking control devices, pre-payment devices, exit payment devices, etc., and the processing flows for generating various types of information, etc., as described with reference to the drawings, are merely embodiments and can be arbitrarily modified without departing from the spirit of the present invention. In other words, any other configurations or algorithms for carrying out the present invention may be adopted.

[0344] Furthermore, the technology of the present invention is not limited to the embodiments described above, and may be modified, substituted, or transformed in various ways without departing from the spirit of the technical idea. Moreover, if the technical idea can be realized in a different way by advances in the technology or by other derived technologies, it may be implemented by that method. Accordingly, the claims cover all embodiments that may fall within the scope of the technical idea.

[0345] In this disclosure, words such as "abbreviated," "almost," and "approximately" may be used as appropriate to facilitate understanding of the explanation. However, there is no clear distinction defined between when these words such as "abbreviated," "almost," and "approximately" are used and when they are not used. In other words, in this disclosure, concepts that define shape, size, positional relationship, state, etc., such as "center," "central," "uniform," and "equal," include concepts such as "substantially centered," "substantially central," "substantially uniform," and "substantially equal." For example, this includes states that fall within a predetermined range (e.g., a range of ±10%) based on criteria such as "perfectly centered," "perfectly central," "perfectly uniform," and "perfectly equal." Therefore, even if words like "abbreviated," "almost," or "approximately" are not added, the concept may still be included in what would typically be expressed with such words. Conversely, a state expressed with such words does not necessarily exclude a complete state.

[0346] In this disclosure, expressions using "greater than A" such as "greater than A" and "less than A" are expressions that comprehensively include both concepts that include cases where something is equivalent to A and concepts that do not include cases where something is equivalent to A. For example, "greater than A" is not limited to cases where something is not equivalent to A, but also includes "greater than or equal to A". Similarly, "less than A" is not limited to "less than A", but also includes "less than or equal to A". When implementing this technology, you should appropriately adopt specific settings and other elements from the concepts included in "greater than A" and "less than A" so that the effects described above are achieved.

[0347] It is also possible to combine at least two of the feature features of the present invention described above. In other words, the various feature features described in each embodiment may be combined arbitrarily without distinction between embodiments. Furthermore, the various effects described above are merely examples and are not limiting, and other effects may also be exhibited. [Industrial applicability]

[0348] As described above, the technology of the present invention is suitably applicable to paid parking facilities. [Explanation of Symbols]

[0349] 1…Parking management system 2…User terminal 3…Owner terminal 4…Administrative agency terminal 5…Parking management system 7… Recipient organization 8…Parking 9…Parking control system 10…Network 11……User 12…Owner 13…Administrative body 14…Operator 26... Staff terminal 27… Pre-payment device 28... Pre-payment surveillance camera 29… Guidance device 32...Exit payment device 33... Entrance camera 34… Exit Camera 37… Entering vehicles 38... Participating Vehicles 43...Campus passageway 44…Parking space 45...In-venue camera 59…Touch panel 87…road 90…Machine learning models 92... Photographed image 93... Vehicle 94…Pedestrian 95...smoke 96... Bicycle 98…Monitoring screen 100... Alarm screen 102, 114… Notification emails 113…Abnormal notification screen 140… Computer

Claims

1. The sensor unit is located in the parking lot, A determination unit that determines the type of abnormality that occurred in or around the parking lot based on the detection results of the sensor unit, Based on the determined type of abnormality, a selection unit selects a notification recipient from among the users of the parking lot, the owner of the parking lot, and the management organization that manages the parking lot, to notify them of the occurrence of the abnormality. A parking management system equipped with the following features.

2. A parking management system according to claim 1, The selection unit further selects at least one of the following as the recipient of the notification: the police, fire department, security company, cleaning company, local government, and facilities surrounding the parking lot. Parking management system.

3. A parking management system according to claim 1, The selection unit selects, at the time the abnormality occurs, the user who has parked a vehicle in the parking lot, or the user who has parked a vehicle near the location where the abnormality occurred, as the target of notification. Parking management system.

4. A parking management system according to claim 1, further, It comprises a notification management unit that manages notifications to the selected notification recipients. Parking management system.

5. A parking management system according to claim 1, further, The system includes a user information management unit that manages user information, including notification destination information entered by the user, The notification management unit, when the user who entered the notification recipient information is selected as the notification recipient, notifies the user of the occurrence of the abnormality based on the notification recipient information. Parking management system.

6. A parking management system according to claim 1, further, The system includes a payment device that accepts payment operations for parking fees, including the input of vehicle information by the user. The selection unit determines, based on the vehicle information input to the payment device, whether the user who entered the payment operation has been selected as the notification target. If the user who entered the settlement operation is selected as the notification recipient, the notification management unit will notify the user of the occurrence of the abnormality via the settlement device. Parking management system.

7. A parking management system according to claim 6, The payment device is at least one of the parking fee payment device located in the parking lot and the user terminal of the user. Parking management system.

8. A parking management system according to claim 1, The determination unit determines the type of abnormality using a machine learning model trained based on a machine learning algorithm, so as to output the type of abnormality in response to the input information including the detection result of the sensor unit. Parking management system.

9. A parking management system according to claim 1, The selection unit selects the notification target using a machine learning model trained based on a machine learning algorithm, so as to output the notification target in response to input information including the detection result of the sensor unit. Parking management system.

10. A parking management system according to claim 1, The determination unit determines the type of abnormality and the notification target using a machine learning model trained based on a machine learning algorithm, in order to output the type of abnormality and the notification target in response to the input information including the detection result of the sensor unit. The selection unit uses the machine learning model to select the notification target. Parking management system.

11. A parking management system according to claim 1, The sensor unit includes at least one of an imaging device, a temperature sensor, and a smoke sensor. Parking management system.

12. Based on the detection results of the sensor units installed in the parking lot, the type of abnormality that occurred in or around the parking lot is determined. Based on the determined type of abnormality, the system selects the recipients of notification from among the users of the parking lot, the owner of the parking lot, and the management organization that manages the parking lot. A parking management method performed by a computer system.

13. Based on the detection results of the sensor units installed in the parking lot, the type of abnormality that occurred in or around the parking lot is determined. Based on the determined type of abnormality, the system selects the recipients of notification from among the users of the parking lot, the owner of the parking lot, and the management organization that manages the parking lot. A program that causes a computer system to perform a task.

Images