Parking management system, parking management method, and program

Abstract

To provide a parking management system, a parking management method, and a program that enable improved convenience for parking lot users. [Solution] A parking management system according to one embodiment of the present invention comprises a group registration unit and a discount management unit. The group registration unit registers user groups whose group members are parking users who use the parking lot and facility users who use facilities affiliated with the parking lot. The discount management unit aggregates discount information regarding parking fees incurred by the use of the facilities by the group members of the user group, and determines the vehicles eligible for the discount and the discount to be applied.

Description

Technical Field

[0007] ,

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

Background Art

[0002] Recently, in parking lots annexed to commercial facilities and the like, a parking lot service has been realized in which users apply the discount information of the parking lot obtained at the commercial facility or the like to the settlement of the parking lot fee, thereby reducing the burden of the parking lot fee on the users.

[0003] Patent Document 1 discloses a parking lot management system capable of appropriately and simply aggregating the purchase amounts of all passengers and calculating the parking fee.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Thus, there is a need for a technology that can improve the convenience of parking lot users.

[0006] In view of the above circumstances, an object of the present invention is to provide a parking lot management system, a parking lot management method, and a program that can improve the convenience of parking lot users.

Means for Solving the Problems

[0007] To achieve the above object, a parking lot management system according to one embodiment of the present invention includes a group registration unit and a discount management unit. The aforementioned group registration unit registers user groups whose group members include parking users, who are users of the parking lot, and facility users, who are users of facilities affiliated with the parking lot. The discount management unit collects discount information regarding parking fees incurred by the use of the facility by the user group members, and determines which vehicles are eligible for the discount and what discounts to apply.

[0008] The group registration unit may register the facility users who register their vehicles as parking lot users and the user group.

[0009] The parking management system may further include a user information acquisition unit that acquires facility user information, including identification information, relating to facility users. In this case, the group registration unit may register the user groups based on the identification information included in the acquired facility user information.

[0010] The user information acquisition unit may acquire facility user information relating to facility users who register vehicles, and generate parking lot user information including vehicle information based on the identification information contained in the facility user information.

[0011] The discount management unit may determine multiple vehicles as vehicles eligible for the discount.

[0012] The discount management unit may determine the vehicles eligible for the discount from among the vehicles registered by the parking lot users who are members of the user group.

[0013] The discount management unit may determine that a vehicle registered by a parking lot user who is not a member of the user group, as designated by a member of the user group, is a vehicle eligible for the discount.

[0014] The discount management unit may determine which discount information to apply to the vehicle subject to the discount from among the discount information generated for each of the group members.

[0015] The discount management unit may divide the discount information generated for each of the group members and determine it as applicable discount information.

[0016] The discount management unit may change the owner of the discount information generated for each of the group members.

[0017] The discount management unit may change the owner of the discount information generated for a predetermined group member of the user group to another group member of the user group.

[0018] The discount management unit may change the owner of the discount information generated for each of the group members to a facility user who is not a group member, as specified by the group member.

[0019] The discount management unit may divide the discount information generated for a predetermined group member of the user group and assign it to other group members of the user group.

[0020] The discount management unit may divide the discount information generated for each of the group members and assign it to facility users who are not group members, as specified by the group members.

[0021] The parking management system may further include a GUI generation unit that generates a GUI (Graphical User Interface) for parking users and transmits it to the user terminal of the parking user.

[0022] The discount management unit may aggregate the discount information generated for each of the group members of the user group based on the identification information of each of the group members. In this case, the GUI generation unit may display the aggregated discount information on the GUI for parking lot users so that the owner of the discount information can be identified.

[0023] The GUI generation unit may display, on the GUI for parking lot users, as the vehicle to be settled, the vehicle registered by the parking lot user included in the user group that includes the group member who has input that they will settle the parking fee and is parked in the parking lot.

[0024] The group registration unit may register the user group, with the parking lot user who has input that they will create the user group as the representative and the facility user specified by the representative as the co-user.

[0025] Each of the user terminals of the parking lot users and the user terminals of the facility users may be capable of displaying a code image including the identification information and extracting the identification information from the code image. In this case, the group registration unit may register the facility user identified by the identification information extracted from the code image by the user terminal of the representative as the co-user in the user group.

[0026] The discount management unit may determine the discount target vehicle and the discount content based on the instructions of the group members of the user group.

[0027] The parking lot management system may further include a facility terminal that is arranged in the facility, extracts the identification information from a code image including the identification information displayed on the user terminal of the facility user, and transmits it as settlement information in association with the usage information regarding the usage of the facility by the facility user.

[0028] A parking management method according to one embodiment of the present invention is a parking management method executed by a computer system, which includes registering user groups whose group members are parking users who are users of a parking lot and facility users who are users of a facility affiliated with the parking lot. Discount information regarding parking fees incurred by the use of the facility by the group members of the user group is aggregated, and the vehicles eligible for the discount and the details of the discount to be applied are determined.

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

[0030] As described above, the present invention makes it possible to improve the convenience of parking lot users. [Brief explanation of the drawing]

[0031] [Figure 1] This is a schematic diagram showing an example configuration of a parking management system according to one embodiment of the present invention. [Figure 2] This is a schematic diagram showing a specific example of a parking lot configuration. [Figure 3] This is a block diagram showing an example of the hardware configuration of an exit payment device. [Figure 4] This is a block diagram showing an example of the hardware configuration of a pre-payment device. [Figure 5] This is a block diagram showing a functional configuration example of a parking control system. [Figure 6] This block diagram shows an example of a functional configuration for a store management system. [Figure 7] This figure shows an example of store user information. [Figure 8] This is a block diagram showing a functional configuration example of a parking management system. [Figure 9] This is a block diagram showing a functional configuration example of a parking management system. [Figure 10]This figure shows an example of group user information. [Figure 11] This figure shows an example of user vehicle information. [Figure 12] This figure shows an example of parked vehicle information. [Figure 13] This flowchart shows the basic operation of this parking management system. [Figure 14] This flowchart shows an example of store member registration. [Figure 15] This flowchart shows an example of parking lot membership registration. [Figure 16] This flowchart shows an example of the procedures when a vehicle enters the premises. [Figure 17] This flowchart shows an example of the procedures when a vehicle exits the station. [Figure 18] This flowchart shows an example of the process when making a payment using a user terminal. [Figure 19] A flowchart illustrating an example of adding a vehicle to the settlement process. [Figure 20] This is a flowchart showing the basic flow from vehicle entry to payment. [Figure 21] This is a schematic diagram showing an example of a GUI for store users. [Figure 22] This is a schematic diagram showing an example of a GUI for parking lot users. [Figure 23] This is a schematic diagram showing examples of GUIs for store users and parking lot users. [Figure 24] This is a schematic diagram showing an example of a GUI for parking lot users. [Figure 25] This is a schematic diagram showing an example of a GUI for parking lot users. [Figure 26] This is a schematic diagram showing an example of a GUI for parking lot users. [Figure 27] This is a schematic diagram showing an example of a GUI for parking lot users. [Figure 28] 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]

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

[0033] [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. The parking management system 1 includes user terminals 2 (2a to 2d), a parking management device 3, a store management device 4, a management institution terminal 5, a payment server device (not shown) owned by a payment institution 6, a store terminal 8 located in store 7, and an owner terminal 9. The parking management system 1 also includes a parking control device 11 located in parking lot 10.

[0034] As shown in Figure 1, these devices are connected to each other via network 12 so that they can communicate with one another. Network 12 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 12 is not limited.

[0035] User terminal 2 is a terminal used by user 13.

[0036] In this disclosure, users of parking lot 10 may be referred to as parking lot users, and users of store 7 may be referred to as store users. Store 7 is one embodiment of a facility that has a partnership with parking lot 10 regarding discount services. Store users are also one embodiment of facility users according to the present invention.

[0037] Furthermore, this technology can be applied to any facility that may not be classified as a retail store, such as hospitals and public facilities.

[0038] Parking users refer to users 13 who park their vehicles in parking lot 10. Store users refer to users 13 who shop or do other activities at stores 7 that are affiliated with the parking lot.

[0039] In this embodiment, in the parking management system 1, a user 13 whose parking user information is registered as a parking user is considered a parking user. Similarly, a user 13 whose store user information is registered as a store user is considered a store user.

[0040] For example, suppose user 13a, as shown in Figure 1, is registered as both a parking lot user and a store user. User 13a parks their vehicle in parking lot 10 and makes purchases at store 7. If a discount on parking fees is incurred due to user 13a's purchases at store 7, it is possible to settle the parking fees reflecting that discount.

[0041] For example, suppose user 13b, as shown in Figure 1, is a passenger in user 13a's vehicle. User 13b is not registered as a parking lot user, but only as a store user. User 13b gets out of user 13a's vehicle parked in parking lot 10 and goes shopping at store 7.

[0042] In this parking management system 1, if user 13b is registered in the same group as user 13a, it is possible to settle the parking fee for user 13b's vehicle by reflecting the discounts incurred from user 13b's purchases at store 7.

[0043] Furthermore, for example, suppose user 13c, as shown in Figure 1, goes to store 7 by train or other means and makes a purchase at store 7 (i.e., does not go to parking lot 10). User 13c is not registered as a parking lot user, but only as a store user.

[0044] In this parking management system 1, if user 13c is registered in the same group as user 13a, it is possible to settle the parking fee for user 13b's vehicle by reflecting the discounts incurred by user 13c's purchases at store 7.

[0045] Furthermore, it is assumed that user 13d, as shown in Figure 1, is also registered as both a parking lot user and a store user. User 13d parks their vehicle in parking lot 10 and makes a purchase at store 7.

[0046] In this parking management system 1, if user 13d is registered in the same group as user 13a, it is possible to adjust the parking fee for user 13a's vehicle by reflecting the discounts incurred by user 13d's purchases at store 7. Conversely, it is also possible to adjust the parking fee for user 13d's vehicle by reflecting the discounts incurred by user 13a's purchases at store 7.

[0047] Furthermore, it is possible to combine the discounts applied to user 13a and the discounts applied to user 13d and reflect them in the parking fee for user 13a's vehicle (or user 13d's vehicle).

[0048] Thus, by applying the group registration method according to the present invention, this parking management system 1 makes it possible to flexibly set which vehicles are eligible for discounts and what discounts are applied. As a result, it becomes possible to improve the convenience of parking lot users.

[0049] The group registration process according to the present invention will be explained in detail later.

[0050] User terminal 2 is typically a mobile device such as a smartphone. Various PDAs (Personal Digital Assistants), such as tablet devices, can also be used as user terminal 2.

[0051] The owner terminal 9 is a terminal used by the owner of the parking lot 10. Any computer, such as a smartphone, tablet, or various PCs (personal computers), may be used as the owner terminal 9.

[0052] The parking management device 3 is a device that manages the parking lot 10, and can provide the parking management service (group use service) according to this embodiment as a web service.

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

[0054] The parking management device 3 also has a communication unit for communicating with other terminals and devices via the network 12. 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 3 can be any computer, such as a PC.

[0055] As shown in Figure 1, a database (DB) 14 is connected to the parking management device 3. DB 14 functions as a storage unit and stores various information related to this parking management service. For example, it is possible to build various databases within DB 14, such as a group user database, user vehicle database, parked vehicle database, parking information database, parking lot database, store usage database, shopping information database, discount database, exit information database, owner information database, and various history databases.

[0056] Various databases are comprehensively managed by the parking management device 3, which performs tasks such as registering users 13 who use the parking management service, registering and storing owner information for each parking lot 10, and recording and storing operational revenue and expenditure information.

[0057] In this embodiment, a web page is generated by the parking management device 3. The generated web page is displayed on the screens of the user terminal 2, the parking management device 3, the store management device 4, the management institution terminal 5, the payment server device of the payment institution 6, the store terminal 8, and the owner terminal 9 via the network 12 shown in Figure 1, using web browsers installed in each of them.

[0058] For example, users 13 who use parking lot 10, and the owner of parking lot 10, can access various web pages related to parking lot 10 and use various web applications by operating user terminal 2 and owner terminal 9.

[0059] The parking management device 3 can also be called a parking application server.

[0060] The management agency terminal 5 is used by an operator of the management agency that has been entrusted with the management of parking lot 10 by the owner of parking lot 10. The operator handles tasks such as responding to daily inquiries, providing user support, and providing information on maintenance work in the event of malfunctions of various devices installed in parking lot 10. A PC or tablet device may be used as the management agency terminal 5.

[0061] In some cases, the owner of the parking lot 10 may also perform the management duties for the parking lot 10 themselves. In this case, the owner's terminal can function as the management agency terminal 5. Alternatively, a management agency entrusted with management duties may own the parking lot management device 3 and provide the parking lot management service according to this embodiment.

[0062] 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 3 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.

[0063] The store management device 4 is a device that manages the store 7, and it is possible to provide the store usage service according to this embodiment as a web service.

[0064] The store management device 4 has the necessary hardware for a computer, such as a processor like a CPU, GPU, or DSP, memory like ROM or RAM, and storage devices like an HDD.

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

[0066] As shown in Figure 1, DB15 is connected to the store management device 4. DB15 functions as a storage unit and stores various information related to store usage services. For example, it is possible to build various databases within DB15, such as a store user database, a store usage database, a store database, a product / service database, a shopping information database, a discount database, a parking database, and various history databases.

[0067] Various databases are comprehensively managed by the store management device 4, which performs tasks such as registering and canceling memberships of users 13 who use store services, and recording and storing operational revenue and expenditure information.

[0068] In this parking management system 1, it is possible that common information and data may be stored in both the DB14 of the parking management device 3 and the DB15 of the store management device 4. In this case, the information and data stored in common will be managed in a synchronized manner.

[0069] In this embodiment, a web page is generated by the store management device 4. The generated web page is displayed on the screens of the user terminal 2, the parking management device 3, the store management device 4, the management institution terminal 5, the payment server device of the payment institution 6, the store terminal 8, and the owner terminal 9 via the network 12 shown in Figure 1, using web browsers installed in each.

[0070] For example, a user 13 using store 7 can access various web pages related to store 7 and use various web applications by operating the user terminal 2.

[0071] The store management device 4 can also be called the store application server.

[0072] The store terminal 8 will be installed at store 7, which is partnered with parking lot 10. The partnership between parking lot 10 and store 7 could take the form of, for example, a discount service agreement between parking lot 10 and nearby commercial facilities, but it is not limited to this form.

[0073] For example, in a commercial facility adjacent to parking lot 10, if users 13 of parking lot 10 make purchases or other purchases within the commercial facility, a discount service is provided that reduces or waives parking fees depending on the amount spent.

[0074] For example, each store in a commercial facility has at least one cash register, and a cash register management system is installed to integrate them. The cash register management system may also be a POS server. Note that the cash register management system is not necessarily installed within the commercial facility.

[0075] In the example shown in Figure 1, a POS register with communication capabilities is used as the store terminal 8. A code image reader 16 is connected to the store terminal 8. The code image reader 16 is composed of, for example, an optical reading device with a built-in laser scanner and has the function of reading code images according to the present invention, which will be described later.

[0076] For example, the store terminal 8, parking management device 3, and store management device 4 can indirectly share information regarding parking fee discounts (discount rates, discount times, etc.) via a POS server or the like. The specific configuration and type of the store terminal 8 and the code image reader 16 are not limited.

[0077] Figure 2 is a schematic diagram showing a specific configuration example of the parking lot 10. The parking lot 10 has an entrance 18 and an exit 19. As shown in Figure 2, a central island 20 is installed between the entrance 18 and the exit 19. In addition, an entrance island 21 and an exit island 22 are installed on either side of the central island 20.

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

[0079] Within the premises 25 of parking lot 10, a parking control system 11 and a pre-payment system 26 are installed. In addition, an entrance gate 27, an exit payment system 28, an exit gate 29, an entrance camera 30, and an exit camera 31 are installed on the central island 20.

[0080] The parking control device 11 can comprehensively control the operation of each device installed within the parking lot 10. The parking control device 11 can also collect various information and data from each device installed within the parking lot 10 and transmit it to the parking management device 3, etc. Furthermore, the parking control device 11 can receive various information from the parking management device 3, the store management device 4, etc., and perform various operations.

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

[0082] The parking control device 11 also has a communication unit for communicating with other terminals and devices via the network 12. 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 11 can be any computer, such as a PC.

[0083] As shown in Figure 1, DB33 is connected to the parking control device 11. DB33 functions as a memory unit and stores various information related to the management and control of each device in the parking lot 10. Information stored in DB14 of the parking management device 3 and information stored in DB15 of the store management device 4 may be stored in common in DB33. Information and data stored in common are managed in synchronous manner.

[0084] The pre-payment device 26 is a device for users 13 to pre-pay parking fees. The exit payment device 28 is a device for users 13 who have not yet paid to pay parking fees while remaining in their vehicles when exiting the parking area.

[0085] Entrance gate 27 is a device for restricting vehicle entry into parking lot 10. Exit gate 29 is a device for restricting vehicle exit from parking lot 10.

[0086] The entrance camera 30 is positioned to capture images of vehicles 34 entering the entrance lane 23 (hereinafter referred to as "entering vehicle images"). The entering vehicle images are captured when vehicles enter the parking lot 10.

[0087] The exit camera 31 is positioned to capture images of exiting vehicles 35 entering the exit lane 24 (hereinafter referred to as "exiting vehicle images"). The exiting vehicle images are captured when vehicles exit from parking lot 10.

[0088] Furthermore, the exit camera 31 is positioned to capture images of the user 13 performing payment. The exit camera 31 can also capture images of the user 13 making voice inquiries to the exit payment device 28.

[0089] For the entrance camera 30 and the exit camera 31, 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.

[0090] The parking control device 11, pre-payment device 26, entrance gate 27, exit payment device 28, exit gate 29, entrance camera 30, and exit camera 31 are connected by internal wiring 36 (see Figure 1) installed within the premises 25 of the parking lot 10. Instead of internal wiring 36, a local network using wireless communication may be constructed.

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

[0092] Figure 3 is a block diagram showing an example of the hardware configuration of the exit payment device 28. The exit payment device 28 has a CPU 40, a memory 41, and an interface 43 connected to them via a bus 42. The memory 41 is composed of, for example, ROM, RAM, flash memory, etc., and stores various programs and various parking data. Of course, the exit payment device 28 may also be equipped with a storage device such as an HDD.

[0093] Interface 43 is connected to a private network communication unit 44, a code image reader 45, a banknote and coin management unit 46, a receipt printer 47, a touch panel 49, and a speaker 50. The operation of each block is controlled by a CPU 40 that operates according to a program.

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

[0095] The code image reader 45 is composed of, for example, an optical reading device that incorporates a laser scanner. The code image reader 45 can read a code image held over a reading opening provided on the front of the device by scanning a laser beam outwards from the reading opening. The code image reader 45 is configured to be able to read code images according to the present invention.

[0096] The banknote and coin management unit 46 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.

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

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

[0099] The exit payment device 28 can perform payment processing, including, for example, calculating parking fees, displaying them on the touch panel 49 and outputting audio from the speaker 50, counting inserted coins and banknotes, calculating whether or not change is needed, and dispensing change.

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

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

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

[0103] The code image reader 56 is composed of, for example, an optical reading device that incorporates a laser scanner. The code image reader 56 can read a code image held over a reading opening provided on the front of the device by scanning a laser beam outwards from the reading opening. The code image reader 56 is configured to be able to read code images according to the present invention.

[0104] The card reader 58 is configured to support electronic money payments. For example, 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, can be used as the card reader 58. Of course, it is also possible to configure the card reader 58 to be able to read various credit cards and house cards. The card reader 58 can also be mounted on the exit payment device 28.

[0105] The banknote and coin management unit 59, receipt printer 60, touch panel 61, and speaker 62 can be configured as those installed in the exit settlement device 28. Of course, other configurations may also be used.

[0106] The motion sensor 63 detects a person standing in front of the pre-payment device 26. The specific configuration of the motion sensor 63 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.

[0107] Figure 5 is a block diagram showing an example of the functional configuration of the parking control device 11. As shown in Figure 5, the parking control device 11 includes a vehicle detection unit 65, a camera control unit 66, a gate control unit 67, an entry / exit processing unit 68, and a communication control unit 69.

[0108] These blocks are formed when the processor of the parking control device 11 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.

[0109] The program is installed on the parking control device 11, 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.

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

[0111] 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.

[0112] The camera control unit 66 controls the operation of the entrance camera 30 and the exit camera 31. For example, the camera control unit 66 transmits a trigger signal for shooting, and the entrance camera 30 and the exit camera 31 photograph the entering vehicle 34 and the exit vehicle 35. This generates images of the entering vehicle and the exit vehicle. The trigger signal may be, for example, the output of the entrance loop coil 37 and the exit loop coil 38 used as trigger signals for the entrance camera 30 and the exit camera 31, respectively, but a separate trigger sensor may also be installed.

[0113] The gate control unit 67 controls the operation of the entrance gate 27 and the exit gate 29. The entrance / exit processing unit 68 performs processing related to the entrance of the entrance vehicle 34 (such as transmitting images of the entrance vehicle) and processing related to the exit of the exit vehicle 35 (such as checking payment information). The communication control unit 69 controls communication with other terminals and devices via the network 12.

[0114] Figure 6 is a block diagram showing an example of the functional configuration of the store management device 4. Figure 7 is a diagram showing an example of store user information stored in the store user information DB constructed within DB15.

[0115] As shown in Figure 6, the store management device 4 includes a store user information management unit 71, a discount information management unit 72, a usage history management unit 73, a code image generation unit 74, a store user GUI generation unit 75, and a communication control unit 76.

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

[0117] The program is installed on the store management device 4, 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.

[0118] The store user information management unit 71 manages information about the users 13 (store users) of store 7 who have registered for the store usage service. In this embodiment, the store user information management unit 71 generates and manages the store user information shown in Figure 7.

[0119] In the following, users 13 (store users) of store 7 who have registered for the store usage service may be referred to as store members. The store user information shown in Figure 7 can also be considered the member information of store 7.

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

[0121] "Membership Number"... A number assigned to each member at each store. "Name"... The name of the store member. "Password"...Login password. "Purchase amount"... The total amount spent at store 7. "Discount Information"... Discount information regarding parking fees incurred when using Store 7.

[0122] The "purchase amount" and "discount information" are stored together when user 13 makes a purchase at store 7. "Purchase information" and "discount information" are stored together when the numbers following the purchase amount and the numbers following the discount information are the same. In other words, for each user 13, sets of "purchase amount" and "discount information" are stored in chronological order.

[0123] The store user information shown in Figure 7 is one embodiment of facility user information, including identification information, relating to facility users according to the present invention. In addition, "membership number" is used as one embodiment of the identification information.

[0124] The discount information management unit 72 manages the discount information of each of the 13 users who are store members. The discount information management unit 72 retrieves the discount information from the store terminal 8 and stores it in the store user information.

[0125] The usage history management unit 73 manages the usage history information of each user 13 who is a store member, from the past to the present, regarding their use of store 7. The history information is stored in the usage history DB (not shown in the diagram).

[0126] The code image generation unit 74 generates a code image containing identification information that can identify the user 13 who has been registered as a member. In this embodiment, a code image containing the "member number" as the identification information is generated.

[0127] The GUI generation unit 75 for store users generates a GUI for store users for the user 13 (store user) who will become a store member, and sends it to the user terminal 2 of the user 13.

[0128] The communication control unit 76 controls communication with other terminals and devices via the network 12.

[0129] (Store usage) When a store member makes a purchase at store 7, the user terminal 2 displays the code image display screen 99 shown in Figure 23A (details will be described later). Then, the code image reader 16 connected to the store terminal 8 reads the code image 100 on the code image display screen 99.

[0130] The store terminal 8 extracts the "member number," which is identification information, from the code image 100. The store terminal 8 then associates the extracted "member number" with the user 13's usage information for store 7 (including purchase amount and discount date information), and transmits it to the store management device 4 as settlement information.

[0131] In the store management device 4, the discount information management unit 72 stores "purchase amount" and "discount information" in the store user information based on member information and store usage information from store 7.

[0132] In this embodiment, the store terminal 8 functions as one embodiment of a facility terminal according to the present invention, which is placed in a facility and extracts identification information from a code image containing identification information displayed on a user terminal of a facility user, associates it with usage information related to the facility user's use of the facility, and transmits it as settlement information.

[0133] Figures 8 and 9 are block diagrams showing an example of the functional configuration of the parking management device 3. Figures 10 to 12 show examples of information stored in the group user information DB, user vehicle DB, and parked vehicle DB, respectively, which are constructed within DB14.

[0134] As shown in Figure 8, the parking management device 3 includes a vehicle information recognition unit 78, a parking user information management unit 79, a parked vehicle information management unit 80, a discount management unit 81, a usage history management unit 82, a code image generation unit 83, a GUI generation unit for parking users 84, a settlement processing unit 85, and a communication control unit 86.

[0135] These blocks are formed when the processor of the parking management device 3 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.

[0136] The program is installed on the parking management device 3, 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.

[0137] The vehicle information recognition unit 78 extracts vehicle information (hereinafter referred to as "entering vehicle information") related to the entering vehicle 34 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 35 from the exiting vehicle image.

[0138] 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.

[0139] 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.

[0140] The Parking User Information Management Department 79 manages information regarding users 13 (parking users) of parking lots 10 registered with the parking management service (group use service). Hereinafter, users 13 (store users) of parking lots 10 registered with the parking management service (group use service) may be referred to as parking members.

[0141] As shown in Figure 9, the parking lot user information management unit 79 includes a user information acquisition unit 87 and a group registration unit 88 as functional blocks, and generates and manages group user information shown in Figure 10 and user vehicle information shown in Figure 11.

[0142] The user information acquisition unit 87 acquires store user information, including identification information (member number). In this embodiment, store user information of store members registered with the store usage service is acquired, and group user information shown in Figure 10 is generated based on the identification information (member number) included in the acquired store user information.

[0143] In other words, in this embodiment, the same identification information (membership number) is used to link the store user information shown in Figure 7 and the group user information shown in Figure 10. This also means that the same identification information (membership number) is used to link the parking management device 3 and the store management device 4.

[0144] The group registration unit 88 registers user groups whose group members are parking users (parking members) who are users of parking lot 10, and facility users (store members) who are users of stores 7 (facilities) affiliated with parking lot 10.

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

[0146] "Membership Number"... A number assigned to each store member (also used as a parking membership number). "Name"... The name of the parking lot member (store member). "Representative Flag"... If you are the representative of the user group, the representative flag should be 0. If you are a co-user of the user group, the representative flag should be 1. "Group No. / Name"... The number and name of the user group to which the user belongs. "Representative Member Number"... The member number of the representative of the user group to which you belong. If you are the representative, your own "Member Number" will be stored. "Discount Information"... Discount information regarding parking fees incurred when using Store 7.

[0147] The "Membership Number," "Name," and "Discount Information" are stored based on the store user information obtained by the user information acquisition unit 87 shown in Figure 9. The "Representative Flag," "Group No. / Name," and "Representative Membership Number" are stored by the group registration unit 88.

[0148] As shown in Figure 11, in this embodiment, the following information (data) is stored as user vehicle information. "Vehicle Number"... The vehicle number of vehicle belonging to user 13 (parking user) using parking lot 10. "Membership Number"... Parking membership number (= store membership number) "Representative Membership Number"... The membership number of the representative of the user group to which the group belongs. "Group No. / Name"... The number of the user group to which you belong. "Payment eligibility flag"... If payment is not required (vehicle has not entered parking lot 10), the payment eligibility flag is 0. If payment is required (vehicle has entered parking lot 10), the payment eligibility flag is 1. "Settler Flag"... If user 13 within the user group to which the user belongs is the settlementr, the settlementr flag = 0. If user 13 outside the user group to which the user belongs is the settlementr and the settlement is performed by proxy, the settlementr flag = 1. "Settlement Selection Flag"... If the vehicle is not selected as a vehicle subject to settlement, the settlement selection flag = 0. If the vehicle is selected as a vehicle subject to settlement, the settlement selection flag = 1.

[0149] As will be explained later, in this embodiment, the store member who registers the vehicle is registered as a parking lot member. In other words, it is assumed that the parking lot member is a store member. Of course, the application of the present invention is not limited to this form.

[0150] For users 13 who are included in the group user information shown in Figure 10 and who have registered their vehicle and become parking lot members, user vehicle information shown in Figure 11 is generated. The group user information and user vehicle information generated for users 13 who become parking lot members constitute one embodiment of parking lot user information, including vehicle information, which is generated based on identification information included in facility user information according to the present invention.

[0151] The parking vehicle information management unit 80 generates and manages the parking vehicle information shown in Figure 12 in response to vehicles entering the parking lot 10. This parking vehicle information can also be called occupancy information.

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

[0153] "Vehicle Number"... The vehicle number of vehicle 34 that entered parking lot 10. "Entry Date and Time"... Information on the entry date and time of the entering vehicle 34. For example, the date and time when the image of the entering vehicle was taken by the entrance camera 30 is stored as the entry date and time. Of course, it is not limited to this. "Exit Date and Time"... Information on the exit date and time of the exiting vehicle 35. For example, the date and time when the exit camera 31 captured an image of the exiting vehicle is stored as the exit date and time. Of course, it is not limited to this. "Payment Complete Flag"... If the parking fee has been paid, the payment complete flag = 0. If the parking fee has not been paid, the payment complete flag = 1.

[0154] The discount management unit 81 manages the discount information for each user 13. In this embodiment, the discount management unit 81 aggregates discount information regarding parking fees incurred when group members of a user group use the store 7 (facility), and determines which vehicles are eligible for the discount and what discounts to apply.

[0155] For example, the vehicles eligible for the discount and the discount amount are determined based on instructions from group members of a user group, which are entered via a GUI for parking lot users. However, the vehicles eligible for the discount and the discount amount may also be determined automatically by AI (artificial intelligence) or the like.

[0156] The usage history management unit 82 manages the usage history information of each user 13 regarding the parking lot 10, from the past to the present. The history information is stored in the usage history database (not shown in the diagram).

[0157] The code image generation unit 83 generates a code image containing identification information that can identify the user 13 who has been registered as a parking lot member. In this embodiment, a code image is generated in which the parking lot member number (= store member number) is stored as the identification information.

[0158] The parking user GUI generation unit 84 generates a parking user GUI for the user 13 (parking user) who becomes a parking member, and transmits it to the user terminal 2 of the user 13. The parking user GUI generation unit 84 is one embodiment of the GUI generation unit according to the present invention.

[0159] The settlement processing unit 85 performs settlement processing for the use of the parking lot 10 by user 13. For example, the settlement processing unit 85 calculates the usage fee for each user 13 and performs settlement processing. In this case, if a discount is applied due to the use of store 7, the usage fee reflecting the discount is calculated and settlement processing is performed. For example, various settlement processes such as point settlement processing, debit card payment, and electronic money payment may be performed.

[0160] Furthermore, the settlement processing unit 85 can calculate the parking fee based on requests from the parking control device 11 and the user terminal 2, and notify the parking control device 11 and the user terminal 2. Of course, if a discount is applied due to the use of store 7, it is possible to calculate the usage fee reflecting the discount and notify the parking control device 11 and the user terminal 2.

[0161] Furthermore, in this embodiment, it is possible to settle parking fees and apply discounts based on user groups.

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

[0163] [Basic Operation of Parking Management Systems] Figure 13 is a flowchart showing the basic operation of this parking management system. First, the group registration unit 88 of the parking management device 3 registers user groups whose members include parking members (parking users) and store members (store users) (step 101).

[0164] The discount management unit 81 of the parking management device 3 aggregates discount information regarding parking fees incurred when group members of a user group use the store 7, and determines which vehicles are eligible for the discount and what discounts to apply (step 102). This makes it possible to improve the convenience of users 13 who use the parking lot 10.

[0165] [Specific examples of how the parking management system works] A specific example of the operation of this parking management system 1 will be explained with reference to the flowcharts shown in Figures 14 to 20 and the GUIs shown in Figures 21 to 27.

[0166] [GUI for parking lot users and GUI for store users] In this parking management system 1, the GUI generation unit 84 for parking users of the parking management device 3 provides a GUI for parking members (parking users). In addition, the GUI generation unit 75 for store users of the store management device 4 provides a GUI for store members (store users).

[0167] Regarding the GUI examples shown in Figures 21 to 27, the GUI that displays "XXXX Parking Lot" at the top of the touch panel of user terminal 2 corresponds to the GUI for parking lot users. The GUI that displays "XXXX Shopping Street" at the top of the touch panel corresponds to the GUI for store users.

[0168] The GUI for parking lot users and the GUI for store users are displayed on the touch panel via the web browser on user terminal 2.

[0169] User 13 accesses the website providing the parking management service and the website providing the store usage service by, for example, entering a designated URL into the browser of user terminal 2 (or scanning a designated QR code (registered trademark)). This makes it possible to operate the parking user GUI and store user GUI described below on the web application.

[0170] Alternatively, the application can display a push notification screen to user terminal 2 to launch the application, and user 13 can access the website providing the parking management service and the website providing the store usage service by selecting a button to launch the application. After accessing the website, users can operate the GUI for parking users and the GUI for store users.

[0171] Of course, this is not the only option, and the parking management service and the store usage service may also be provided via native applications. In this case, the application program for the parking management service and the application program for the store usage service will be downloaded to the user terminal 2 of user 13. By launching the applications, user 13 will be able to operate the GUI for parking users and the GUI for store users. In addition, various other forms of operation for the GUI for parking users and the GUI for store users may be employed.

[0172] (Store Membership Registration) Figure 14 is a flowchart showing an example of store member registration. User 13 inputs new registration information for member registration via user terminal 2 (step 201). The input information is transmitted to the store management device 4 and output to the store user information management unit 71 of the store management device 4. The store user information management unit 71 then assigns a member number and generates the store user information shown in Figure 7 (step 202).

[0173] For example, as shown in Figure 21A, a push notification screen 89 prompting the user to launch the store user application is displayed on the user terminal 2. When the user 13 selects the "Launch App" button on the push notification screen 89, the processing menu screen 90 shown in Figure 21B is displayed.

[0174] In this embodiment, the processing menu screen 90 is provided with buttons for "Display QR Code," "Pay Parking Fee," "Register Joint User," "Register Vehicle," and "New Member Registration."

[0175] When user 13 selects the "New Member Registration" button, the registration information input screen 91 shown in Figure 21C is displayed. In the example shown in Figure 21C, the registration information input screen 91 has input fields for "Name," "Member Password (8 alphanumeric characters)," "Member Password (Confirmation)," "Card Number," and "Expiration Date." Once this information is entered and the "Register" button is selected, the registration completion screen 92 shown in Figure 21D is displayed.

[0176] The registration completion screen 92 displays text indicating that the store member registration is complete, along with the entered registration information. User 13 can then check their registration information. User 13 can also select the "Return to Menu" button to display the processing menu screen 90 shown in Figure 21B.

[0177] (Parking membership registration) Figure 15 is a flowchart showing an example of parking lot member registration. In this embodiment, the store member who has registered first enters their member number and password and logs in to the store usage application (step 301).

[0178] The entered membership number and password are transmitted to the store management device 4, and the store user information management unit 71 searches for the store user information shown in Figure 7 (step 302). Then, the authentication result for the membership number and password (whether or not matching store user information exists) is transmitted to the user terminal 2.

[0179] On user terminal 2, it is determined whether user 13, who entered their membership number and password, is a store member, and the authentication result for login is displayed (step 303). If no store user information matching the entered membership number and password exists, it is determined that the user is not a store member (No. in step 303), a message indicating login failure is displayed, and the process ends.

[0180] If store user information matching the entered membership number and password exists, the user is determined to be a store member (Yes in step 303), and the processing menu screen 90 shown in Figure 21B is displayed.

[0181] Vehicle information is entered by user 13, who is a store member (step 304). The entered vehicle information is transmitted to the parking management device 3 and output to the parking user information management unit 79 of the parking management device 3. The parking user information management unit 79 then generates the group user information shown in Figure 10 and the user vehicle information shown in Figure 11 (step 305).

[0182] When group user information and user vehicle information are generated, the "membership number," "name," and "discount information" included in the store user information acquired by the user information acquisition unit 87 shown in Figure 9 are stored. In addition, the "representative flag," "group no. / name," and "representative membership number" are stored by the group registration unit 88.

[0183] For example, when the "Register Your Vehicle" button on the processing menu screen 90 shown in Figure 21B is selected, the parking lot user application is launched, and the category selection screen 93 shown in Figure 22A is displayed as the parking lot user GUI.

[0184] In this parking management system 1, selecting the "Register Your Vehicle" button on the processing menu screen 90, which is the GUI for store users, launches the application for parking users. Then, the system automatically transitions from the processing menu screen 90, which is the GUI for store users, to the category selection screen 93, which is the GUI for parking users.

[0185] Furthermore, if you select the "Pay Parking Fees" button or the "Register Shared User" button on the processing menu screen 90, the parking user application will launch and you will be automatically redirected to the parking user GUI.

[0186] The category selection screen 93 shown in Figure 22A is provided with a category selection section 94. The user 13 can select and set a category according to the scene.

[0187] For example, if the vehicle you want to register is a company car, select "Company," and if it's a personal car, select "Home." Also, if the vehicle is used for children's school events, select "School," and if it's used for neighborhood association events, select "Neighborhood Association." Categories may be set by default, or users may be able to create their own categories. Of course, there may also be an option to select "No Category."

[0188] In the example shown in Figure 22A, "Home" is selected as the category.

[0189] When the "Next" button on the category selection screen 93 is selected, the vehicle information input screen 95 shown in Figure 22B is displayed. The vehicle information input screen 95 has input fields for "Vehicle Number (Name of Land Transport Bureau, Classification Number, Hiragana, 4-digit serial number)". Once this information is entered and the "Register" button is selected, the group user information shown in Figure 10 and the user vehicle information shown in Figure 11 are generated based on the entered information.

[0190] In this parking management system 1, when a user 13 who becomes a store member registers their vehicle, they are registered as a parking member, and group user information shown in Figure 10 and user vehicle information shown in Figure 11 are generated with the same membership number as the store member.

[0191] By linking the parking management device 3 and the store management device 4 with the same membership number, seamless integration between the store usage application and the parking management application is achieved. This reduces the burden on users 13 who use both applications, enabling greater convenience.

[0192] Furthermore, this parking management system 1 allows users 13 to register multiple vehicles. For example, by selecting the "Next" button on the vehicle information input screen 95 shown in Figure 22B, it becomes possible to register a second or subsequent vehicle. In this case, for example, a new category is selected on the category selection screen 93 shown in Figure 22A, and the "vehicle number (land transport bureau name, classification number, hiragana, 4-digit serial number)" for the second and subsequent vehicles is entered on the vehicle information input screen 95 shown in Figure 22B. Based on the entered information, the group user information shown in Figure 10 and the user vehicle information shown in Figure 11 are generated.

[0193] Since vehicles can be registered in each of multiple categories, it offers a high degree of convenience.

[0194] (Group creation (registration of co-users)) In step 306 shown in Figure 15, it is determined whether user 13, who has become a parking lot member, has entered an indication that they wish to register a co-user (step 306). In this embodiment, it is determined whether the "Register Co-User" button provided on the processing menu screen 90 shown in Figure 21B has been selected.

[0195] If the "Register Joint User" button is not selected (NO in step 306), the process ends.

[0196] If user 13 selects the "Register Joint User" button (Yes in step 306), the group name (category) selection screen 96 shown in Figure 22C will be displayed (transition from the store user GUI to the parking lot user GUI).

[0197] In the example shown in Figure 22C, the group name (category) selection screen 96 is provided with a group name (category) selection section 97. The user 13 can select and set a group name (category) according to the scene (step 307).

[0198] For example, if you want to create a group with members from the same company, select "Company," and if you want to create a group with family or relatives, select "Home." Similarly, if you want to create a group with parents or teachers from your child's school, select "School," and if you want to create a group with members of your neighborhood association, select "Neighborhood Association." The group name (category) may be set by default, or users may be able to create their own group names (categories).

[0199] In the example shown in Figure 22C, "Home" is selected as the group name (category).

[0200] Of course, when registering your vehicle on the category selection screen 93 in Figure 22A, you may select a category with the creation of a group (registration of co-users) in mind. In other words, it is possible to select the same category on the group name (category) selection screen 96 in Figure 22C as the category selected on the category selection screen 93 in Figure 22A. In this case, a group will be created with the category selected when registering your vehicle as its group name.

[0201] When the "Next" button on the group name (category) selection screen 96 is selected, the code image reading screen 98 shown in Figure 22D is displayed. The code image reading screen 98 displays the live camera image captured by the camera on the user terminal 2.

[0202] Figure 23A shows the code image display screen 99, which is displayed as a GUI for facility users. For example, a user 13 who wants to register as a co-user is asked to display the code image display screen 99. The requested user 13 displays the code image display screen 99 by selecting the "Display QR Code" button on the processing menu screen 90 shown in Figure 21B.

[0203] The code image display screen 99 displays a code image 100 containing the member number, which was generated by the code image generation unit 74 of the store management device 4. This code image 100 is also used when receiving parking discount services at store 7.

[0204] User 13, who registers as a joint user, operates user terminal 2 so that the code image 100 is included in the live camera image. This automatically captures the code image 100, making it possible to extract the membership number contained in the code image 100.

[0205] In this embodiment, a QR code that can be read relatively widely by user terminals 2, store terminals 8, etc., is used as the code image 100. Of course, the configuration of the code image 100 is not limited in the application of the present invention. Any configuration can be used as the code image 100, such as a one-dimensional code, a stacked two-dimensional code, a matrix two-dimensional code, etc.

[0206] Of course, if the reading capabilities of user terminals 2 and store terminals 8 improve, the configuration of the code image 100 suitable for the present invention will also change. For example, color codes such as Chameleon Code (registered trademark) are also considered to be perfectly usable.

[0207] Additionally, a code image display screen may be displayed as a GUI for parking lot users. For example, the code image generation unit 83 of the parking lot management device 3 may generate a code image including the member number, and the code image display screen may be displayed.

[0208] If the code image 100 is successfully read, the registration confirmation screen 101 shown in Figure 23B will be displayed. The registration confirmation screen 101 displays the "member number" and "name" of the user 13 to be registered as a joint user.

[0209] Furthermore, joint users are 13 users who use store 7 together with parking lot users, and it is possible to register both parking lot members (parking lot users) who have registered their cars and store members (store users) who have not registered their cars.

[0210] For example, if user 13, whose membership number is extracted from the code image, is a parking lot member (parking lot user) who has registered a car, the parking lot user information management unit 79 of the parking lot management device 3 can retrieve information such as "name" by searching for group user information from the "membership number".

[0211] If user 13, whose membership number was extracted from the code image, is a store member (store user) who has not registered a vehicle, the user information acquisition unit 87 of the parking management device 3 acquires store user information based on the "membership number". It is possible to obtain information such as "name" from the acquired store user information.

[0212] For example, it is possible to create a group with multiple parking members, each parking their vehicle in parking lot 10. Alternatively, a group can be created with only one parking member parking in parking lot 10, and the other members being store members, such as passengers. Of course, it is also possible to create a group with multiple parking members and multiple store members (who are not parking members).

[0213] When the "Register" button on the registration confirmation screen 101 shown in Figure 23B is selected, the registration of the joint user is entered (step 308). The entered registration information of the joint user is transmitted to the parking management device 3 and output to the parking user information management unit 79 of the parking management device 3. The parking user information management unit 79 then updates the group user information shown in Figure 10 and the user vehicle information shown in Figure 11 (step 309).

[0214] In this embodiment, user 13, who is a parking lot member and has registered other users 13 as co-users, is registered as the group representative. Therefore, when a co-user is registered, the "Representative Flag" in the group user information shown in Figure 10 is set to 0. The "Group No. / Name" and "Representative Member Number" are also stored.

[0215] For user 13, who is registered as a co-user, the "Representative Flag" is set to 1. In addition, the "Group No. / Name" field stores information about the registered group (the group to which the user belongs), and the "Representative Member Number" field stores the membership number of the representative of the group to which the user belongs.

[0216] In the example shown in Figure 10, "XXXX" with "Member Number" = 00001 is the representative of two groups: "0001 / Company" and "0002 / Home". In the "0001 / Company" group, "YYYY" with "Member Number" = 00010 and "ZZZZ" with "Member Number" = 00011 are registered as co-users. In the "0002 / Home" group, "AAAA" with "Member Number" = 00020 is registered as a co-user.

[0217] Additionally, "CCCC" with "Member Number" = 00030 is the representative of the "0003 / School" group. "BBBB" with "Member Number" = 00021 is registered as a co-user within the "0003 / School" group.

[0218] In the example shown in Figure 11, the vehicle numbers for "XXXX" with "Member Number" = 00001, "YYYY" with "Member Number" = 00010, and "ZZZZ" with "Member Number" = 00011 are registered. Therefore, all three users 13 are parking lot members, and the group "0001 / Company" is composed of these three parking lot members.

[0219] For "AAAA" with "Member Number" = 00020, the "Vehicle Number" is not registered. Therefore, "AAAA" is not a parking member, and the "0002 / Home" group consists of a parking member who is the representative and a store member. Note that the group user information for "AAAA" shown in Figure 10 is generated based on the store user information obtained by the user information acquisition unit 87 shown in Figure 9 when the registration of a joint user is performed.

[0220] For "CCCC" with "Member Number" = 00030 and "BBBB" with "Member Number" = 00021, a "Vehicle Number" is registered. Therefore, both of these users 13 are parking members, and the "0003 / School" group is composed of these two parking members.

[0221] Thus, in this embodiment, the group registration unit 88 registers a user group with the parking lot member who has entered the intention to create a user group as the representative, and the store members designated by the representative (including both users 13 who are parking lot members and users who are not parking lot members) as co-users.

[0222] The method for registering joint users utilizes the display function of a code image 100 containing identification information (membership number) and the extraction function of the code image 100 on the user terminal 2 of the parking member and store member.

[0223] The group registration unit 88 can register a user group as a joint user, which includes both users 13 who are parking lot members and users who are not, and store users identified by the identification information (member information) extracted from the code image by the representative user terminal 2.

[0224] In this embodiment, a user 13 (parking lot member) who is the representative of one group cannot be a co-user of another group. This prevents the processing of discounts and other related matters from becoming complicated, thereby improving convenience for user 13.

[0225] In the group name (category) selection screen 96 shown in Figure 22C, or the code image reading screen 98 shown in Figure 22D, etc., an explanation such as "When you register a co-user, you will become the representative. You cannot register another representative as a co-user" may be displayed.

[0226] Returning to Figure 15, it is determined whether there is input indicating the addition and registration of further co-users (step 310). In this embodiment, if the "Next" button provided on the registration confirmation screen 101 shown in Figure 23B is selected, step 310 becomes YES, and the process returns to step 308, where the input of co-users is performed.

[0227] If no joint users are added (NO in step 310), it is determined whether there is input indicating the creation of another group (step 311). For example, if the user returns to the processing menu screen 90 shown in Figure 21B and selects the "Register Joint Users" button, step 311 becomes YES, and the user returns to step 307 to select a group name (category).

[0228] It is possible to create multiple user groups with different categories to suit different situations, resulting in high convenience.

[0229] (Vehicle entry) Figure 16 is a flowchart showing an example of the operation when a vehicle enters the parking lot. The vehicle detection unit 65 of the parking lot control device 11 monitors for the detection of an entering vehicle 34 (step 401). If an entering vehicle 34 is detected (YES in step 401), an image of the entering vehicle is taken by the entrance camera 30 (step 402).

[0230] The entrance gate 27 is opened (step 403). The entrance loop coil 37 monitors whether or not the passage of the entering vehicle 34 through the entrance gate 27 has been detected (step 404). When the entering vehicle 34 passes through the entrance gate 27 (YES in step 404), an image of the entering vehicle is transmitted to the parking management device 3 along with the date and time of entry (step 405). Then, the entrance gate 27 is closed (step 406).

[0231] The parking management device 3 receives an image of an entering vehicle (step 407). The vehicle information recognition unit 78 extracts the vehicle number as information about the entering vehicle (step 408).

[0232] The parking vehicle information management unit 80 generates the parking vehicle information shown in Figure 12 (step 409). Specifically, the "vehicle number" and "entry date and time" are stored, and the "payment completion flag" is set to 1.

[0233] Step 410 determines whether the entering vehicle 34 is a user vehicle (a vehicle belonging to a parking member). This determination can be performed by searching for user vehicle information shown in Figure 11 from the extracted vehicle number.

[0234] If the entering vehicle is a user vehicle (YES in step 410), the user vehicle information shown in Figure 11 is updated (step 411). Specifically, the "Payment Target Flag" is set to 1. Both the Payer Flag and the Payment Selection Flag are set to 0.

[0235] (Vehicle departure) Figure 17 is a flowchart showing an example of the operation when a vehicle exits the parking lot. The vehicle detection unit 65 of the parking lot control device 11 monitors for the detection of the exiting vehicle 35 (step 501). If the exiting vehicle 35 is detected (YES in step 501), the exit camera 31 takes an image of the exiting vehicle (step 502).

[0236] The entry / exit processing unit 68 of the parking control device 11 transmits an image of the exiting vehicle to the parking management device 3, and the payment information is checked (step 503).

[0237] The parking management device 3 determines whether payment has been completed (step 504). 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 parked vehicle information shown in Figure 12 is searched and the "payment completion flag" is referenced (paid = 0 / not paid = 1).

[0238] Information regarding whether payment has been made is transmitted from the parking management device 3 to the parking control device 11. Then, the entry / exit processing unit 68 determines whether exit is possible (step 505). If payment has been made and exit is possible (YES in step 505), the exit gate 29 is opened (step 506).

[0239] For example, if the parking fee for the exiting vehicle 35 has already been paid using the pre-payment device 26 or the user terminal 2, step 505 will be YES and the exit gate will open.

[0240] As an example of a pre-payment method using the pre-payment device 26, the user 13 displays the code image display screen 99 shown in Figure 23A on the user terminal 2. Then, the code image 100 is read by the code image reader 56 of the pre-payment device 26.

[0241] The pre-payment device 26 performs an inquiry about the usage fee for the parking lot 10 via the parking control device 11. Specifically, the pre-payment device 26 reads the identification information, the "member number," from the code image 100 and transmits the read "member number" to the payment processing unit 85 of the parking management device 3.

[0242] The settlement processing unit 85 calculates the usage fee (parking fee) for the user 13's use of parking lot 10 based on the received "membership number" and transmits it to the pre-payment device 26. If a discount is available at the affiliated store 7 based on the purchase, the usage fee reflecting the discount may be calculated and transmitted to the pre-payment device 26. The pre-payment device 26 displays the parking fee to the user 13, and the user 13 makes the pre-payment.

[0243] If payment is outstanding and exit is not possible (NO in step 505), the exit payment device 28 will issue a notification of outstanding payment (step 507). For example, a display or voice output such as "Payment has not been completed. Please pay using the exit payment device or your smartphone" will be issued.

[0244] The system monitors whether user 13 completes payment at the exit payment device 28 (step 508). If payment is completed at the exit payment device 28 (YES in step 508), the exit gate is opened (step 506).

[0245] Furthermore, as a pre-payment method using the pre-payment device 26, it is possible to employ a method similar to the pre-payment method using the pre-payment device 26, in which the code image 100 is read by the code image reader 45 of the exit payment device 28.

[0246] If the completion of payment at the exit payment device 28 has not been confirmed (NO in step 508), the process returns to step 503, and a request for payment information is made to the parking management device 3.

[0247] If user 13 pays the parking fee for the exiting vehicle 35 using user terminal 2, the vehicle can exit at step 505 and the exit gate opens (step 506).

[0248] Furthermore, in this parking management system 1, settlement of payments for exiting vehicles 35 using the user terminal 2 is possible based on user groups. For example, settlement can be performed by the user 13 (parking member) driving the vehicle, by a user 13 (parking member / store member) belonging to the same user group, or by a user 13 (parking member / store member) not belonging to the same user group. This point will be explained later.

[0249] The exit loop coil 38 monitors whether or not the exit vehicle 35 has passed through the exit gate 29 (step 509). When the exit vehicle 35 passes through the exit gate 29 (YES in step 509), exit information, including that the exit vehicle 35 has exited and the date and time of exit, is transmitted to the parking management device 3 (step 510). Then, the exit gate 29 is closed (step 511).

[0250] The parking management device 3 receives exit information and updates the parked vehicle information (step 512). Specifically, the exit date and time are stored and the "payment completion flag" is set to 0.

[0251] (Payment using user terminals) Figure 18 is a flowchart showing an example of the operation during payment using the user terminal 2. First, the user terminal 2 sends an inquiry to the parking management device 3 regarding the vehicle to be paid for (step 601). The parking management device 3 extracts the vehicle to be paid for, and the extraction result is sent to the user terminal 2 (step 602).

[0252] In this embodiment, when the "Pay Parking Fee" button on the processing menu screen 90 shown in Figure 21B is selected, information indicating that the parking fee will be paid is transmitted to the parking management device 3. The parking management device 3 searches for group user information and vehicle information based on the "member number" included in the user 13's login information. The user group to which user 13 belongs is then extracted and transmitted to the user terminal 2.

[0253] On user terminal 2, the group selection screen 102 shown in Figure 23C is displayed. The group selection screen 102 displays the user groups to which user 13 belongs. If user 13 belongs to multiple user groups, it is possible to select a user group by using the pull-down menu.

[0254] If user 13 has decided on a user group, or if user 13 who is not a member of the user group (user 13 who is not the representative user or co-user) wants to settle the payment for their vehicle, they select the "Next" button. This will display the vehicle selection screen 103 shown in Figure 23D.

[0255] The vehicle selection screen 103 is provided with a vehicle selection section 104. The vehicle selection section 104 displays the vehicles subject to payment, which are extracted by the parking management device 3 in step 602 (step 603).

[0256] In step 602, the parking management device 3 extracts vehicles belonging to group members of the user group selected by user 13 from the user vehicle information. The "settlement target flag" of the extracted vehicles is then referenced.

[0257] Vehicles with a "Payment Eligibility Flag" of 0 are vehicles that have not entered parking lot 10 and are therefore not subject to payment. Vehicles with a "Payment Eligibility Flag" of 1 are vehicles that have entered parking lot 10 and are subject to payment.

[0258] Based on the vehicles extracted by the parking management device 3 and the results of the "settlement target flag," a vehicle selection image 105 is generated and sent to the user terminal 2. The vehicle selection image 105 sent to the user terminal 2 is displayed on the vehicle selection unit 104. Selecting the V mark displayed at the bottom of the vehicle selection unit 104 will cause scrolling, allowing the lower part of the vehicle selection image 105 to be displayed.

[0259] As shown in Figure 23D, for vehicles extracted as belonging to a group member of a user group and whose "Payment Target Flag" is 1, the following information is displayed: "Entry Vehicle Image," "Entry Date and Time," "Entry Gate Name," "Icon Representing the User Group," and "Vehicle Number."

[0260] As shown in Figure 23D, for vehicles extracted as belonging to a group member of a user group and whose "Settlement Target Flag" is 0, the text "Not Entered" is displayed, and the "User Group Icon" and "Vehicle Number" are displayed in a form that cannot be selected (e.g., grayed out). Note that there are no "Entered Vehicle Images" and therefore none are displayed, but if there are images that were taken in the past and saved in DB14, etc., those images may be displayed.

[0261] User 13 can determine which vehicle to pay for by selecting a vehicle from the vehicle selection image 105. Of course, it is also possible to select multiple vehicles as the vehicles to be selected.

[0262] Thus, in this parking lot management system 1, for the settler (either the representative or the co-user) who wishes to perform the settlement using the user terminal 2, the user group to which the settler belongs is searched and displayed on the user terminal 2 so that the user group can be switched. Further, when the user group is determined, the vehicles of the parking lot members belonging to the user group and parked in the parking lot 10 are displayed on the user terminal 2 so that they can be selected.

[0263] That is, in this parking lot management system 1, the vehicle registered by the parking lot member (parking lot user) included in the user group including the group member (settler) who has input the intention to settle the parking fee is the vehicle parked in the parking lot 10, and is displayed on the GUI for parking lot users as the vehicle to be settled.

[0264] As a result, it is not necessary to search for the vehicle to be settled, and the reduction of scroll display is also realized, and high convenience is exhibited.

[0265] Returning to FIG. 18, it is determined whether or not an input has been made to add the vehicle to be settled (step 604). In the present embodiment, when the "Add" button on the vehicle selection screen 103 shown in FIG. 23D is selected, step 603 becomes YES, and the addition / display of the vehicle to be settled, which will be described later, is executed (step 605).

[0266] When the "Next" button on the vehicle selection screen 103 shown in FIG. 23D is selected, step 603 becomes NO, and the vehicle to be settled is determined (step 606). Then, an inquiry of discount information is executed from the user terminal 2 to the parking lot management device 3 (step 607).

[0267] The discount management unit 81 of the parking lot management device 3 refers to the group user information, and the discount information generated for each of the group members of the user group is aggregated (step 608).

[0268] The aggregated discount information is sent to user terminal 2. The discount information is then displayed on user terminal 2 (step 609).

[0269] In this embodiment, when the "Next" button on the vehicle selection screen 103 shown in Figure 23D is selected, the payment information display screen 106 shown in Figure 24A is displayed. The payment information display screen 106 displays the following information.

[0270] "Total Parking Time"... The total parking time of the selected vehicles subject to payment. "Total Parking Fee"... The total parking fee for the selected vehicle subject to payment. "Discount"... Information on applicable discounts.

[0271] The settlement information display screen 106 is also equipped with a points display section 107. The points display section 107 displays "Points used this time" and "Total points carried over." The 3000 points used this time make the total parking fee of 3000 yen free, and 10 hours of free parking is displayed.

[0272] The "Points Used This Time" and "Total Points Carried Over" displayed in the points display unit 107 are displayed based on discount information compiled by the discount management unit 81.

[0273] When the "Point Usage Information" button on the settlement information display screen 106 is selected, the point usage information screen 108 shown in Figure 24B is displayed. The point usage information screen 108 is provided with a point details display section 109.

[0274] The points details display section 109 displays the name of each group member of the user group and the discount information (points) that will be applied to each group member. In addition, the discount information (points) that will be applied to each purchase will be displayed individually for the same group member.

[0275] The discount information (points) for each group member displayed in the points details display unit 109 is discount information aggregated by the discount management unit 81, and corresponds to "Discount Information 1," "Discount Information 2," etc. in the group user information shown in Figure 10.

[0276] Of course, discount information (points) for all group members will be displayed, regardless of whether the group member is a parking member or not. Furthermore, it does not matter whether the vehicle of a group member who is a parking member has entered parking lot 10. Note that group members for whom no discount information (points) has been generated do not need to be displayed in the points details display section 109.

[0277] In this parking management system 1, the discount management unit 81 aggregates discount information for each member of a user group based on the identification information (member information) of each group member. The parking user GUI generation unit 84 then displays the aggregated discount information on the parking user GUI (point details display unit 109) so that the owner of the discount information can be identified.

[0278] This makes it easy for the person making the payment to understand the discount information status for the entire user group to which they belong.

[0279] User 13 can determine the applicable discount by selecting the discount information (points) in the points details display unit 109. In the example shown in Figure 24B, 3300P of "XXXX" is selected. In this way, it is possible to select the applicable discount information to be applied to the vehicle eligible for the discount from among the discount information available to each group member.

[0280] When the "Confirm" button on the points usage information screen 108 is selected, the discount details (in this embodiment, the number of points to be applied) are determined (step 610), and the settlement information display screen 106 shown in Figure 24A is displayed. The points display unit 107 displays 3000P out of 3300P, and the remaining 800P displayed in the points details display unit 109 is displayed as the "total points carried over".

[0281] In this example, the 3300P for "XXXX" is split, and 3000P is used as applicable discount information. In this way, it is also possible to split the discount information that applies to each group member and use it as applicable discount information.

[0282] In this example, since the total parking fee is 3000 yen, 3000 points are automatically split from the 3300 points of "XXXX" and used as applicable discount information. However, this is not the only option; the discount information (points) for each group member may be split based on input from the person making the payment and used as applicable discount information.

[0283] Furthermore, selecting the "Settings" button on the settlement information display screen 106 allows you to configure various discount settings. For example, you could set it up so that you can directly input the points to be used based on the total discount information (points) for each group member displayed on the points details display section 109. Also, selecting the "Usage History" button displays the usage history from the past to the present.

[0284] When the "Pay" button on the payment information display screen 106 is selected, the payment confirmation screen 110 shown in Figure 24C is displayed. The payment confirmation screen 110 is provided with a fare display section 111, a vehicle subject to payment display section 112, and a registered card information display 113.

[0285] The fee display unit 111 shows the total parking time and total parking fee. The payment target vehicle display unit 112 shows the parking lot name and information of the payment target vehicle selected by the user 13. The registered card information display unit 113 shows the information of the registered credit card.

[0286] Also, on the payment confirmation screen 110, radio buttons are displayed that allow selection of payment using points and payment with a credit card. For example, if payment with a credit card is selected, points are not used and credit card payment is executed. It is also possible to pay the shortage amount with a credit card when there are insufficient points.

[0287] It is monitored whether the user 13 inputs execution of payment (step 611). In the present embodiment, when the "Execute Payment" button on the payment confirmation screen 110 is selected, step 611 becomes YES, and a payment instruction is sent from the user terminal 2 to the parking lot management device 3 (step 612).

[0288] The payment instruction includes the vehicle to be paid for and the discount details input via the GUI for parking lot users on the user terminal 2. The vehicle to be paid for and the discount details are output to the discount management unit 81 of the parking lot management device 3, and the discount management unit 81 determines the vehicle to be discounted and the applicable discount details. For the vehicle to be paid for, the "Payment Selection Flag" in the user vehicle information shown in FIG. 11 is set to 1.

[0289] Thus, in this parking lot management system 1, the discount management unit 81 can determine the vehicle to be discounted from the vehicles registered by the parking lot members who are group members of the user group. Also, the discount management unit 81 can determine a plurality of vehicles as the vehicles to be discounted.

[0290] Payment processing is executed by the payment processing unit 85 (step 613). In the present embodiment, 3000P of discount information is used, and the parking fee for a total of 10 hours is paid.

[0291] The results of the settlement process by the settlement processing unit 85 are reflected (step 614). In the parking management device 3, the "settlement completion flag" of the parked vehicle information shown in Figure 12 is set to 0. In addition, the discount information used is deleted or subtracted in the group user information used. This deletion and subtraction of discount information is also performed synchronously in the store user information of the store management device 4.

[0292] When the user terminal 2 receives the settlement processing result from the parking management device 3, the settlement completion screen 114 shown in Figure 24D is displayed. The settlement completion screen 114 is provided with a settlement result display unit 115 and a point balance display unit 116.

[0293] The settlement result display unit 115 displays the parking lot name and information about the vehicle for which the parking fee has been settled. The point balance display unit 116 displays the point balance. The point balance corresponds to the "total points carried over" displayed in the point display unit 107 of the settlement information display screen 106 in Figure 24A.

[0294] Thus, in this parking management system 1, parking members 13 can link their own vehicles with those of other parking members who are also co-users, and settle parking fees using discount information owned by each group member. This provides a high level of convenience.

[0295] (Adding vehicles belonging to parking lot members who are not members of the user group) The following explains step 605, adding / displaying vehicles subject to settlement, as shown in Figure 18. Figure 19 is a flowchart showing an example of adding vehicles subject to settlement.

[0296] The function to add vehicles to the settlement list allows for the temporary addition of vehicles belonging to parking members who are not members of a user group, and then settlement is performed accordingly. This function may be configured to be accessible only to the representative of the user group. Of course, the system may also be designed so that anyone, regardless of whether they are the representative or a co-user, can add vehicles to the settlement list.

[0297] In this embodiment, when the "Add" button on the vehicle selection screen 103 shown in Figure 23D is selected, the code image reading screen 117 shown in Figure 25A is displayed. The code image reading screen 117 displays a live camera image captured by the camera of the user terminal 2.

[0298] The user 13 of the vehicle to be added as a vehicle subject to settlement is asked to display the code image display screen 99 shown in Figure 23A. The requested user 13 displays the code image display screen 99 by selecting the "Display QR Code" button on the processing menu screen 90 shown in Figure 21B.

[0299] A user 13 who wants to add a vehicle to be included in the settlement process operates the user terminal 2 so that the code image 100 is included in the live camera image. This automatically captures the code image 100, and makes it possible to extract the membership number contained in the code image 100 (steps 701, 702).

[0300] The extracted member numbers are transmitted to the parking management device 3. Then, the parking user information management unit 79 extracts the vehicles to be added based on the member numbers (step 703). It is determined whether the "settlement target flag" of the extracted vehicles is 1 or not (step 704). In other words, it is determined whether the vehicles to be added have entered parking lot 10 or not.

[0301] If the "Payment Target Flag" is 0 instead of 1 (NO in step 704), the vehicle has not entered parking lot 10 and is not a vehicle subject to payment, so the process ends. Information to that effect may be sent to user terminal 2, and user terminal 2 may notify the user that it cannot be added to the payment target vehicles.

[0302] If the "Payment Target Flag" is 1 (YES in step 704), the vehicle has entered parking lot 10 and may be a vehicle subject to payment, so proceed to step 705.

[0303] In step 705, the "Payer Flag" of the vehicle to be added is set to 1. In other words, a flag is set for the vehicle to be added indicating that the payment is being made by user 13 who wants to add the vehicle (user 13 who is outside the user group from the perspective of the vehicle being added).

[0304] Thus, in this parking management system 1, when adding a vehicle belonging to user 13 who is not a member of a user group to the list of vehicles subject to payment, a proxy payment flag is set for the added vehicle. This restricts payment from being made by the vehicle's user or members of the user group to which it belonged. This prevents the payment process from becoming overly complex and improves convenience for user 13.

[0305] The setting of the "Payer Flag" in step 705 may also be performed when it is decided that the vehicle to be added will be added as a vehicle subject to payment. In this embodiment, if the "Payer Flag" is set in step 705 and the vehicle is not ultimately added as a vehicle subject to payment by user 13, the "Payer Flag" is reset to 0.

[0306] Once the "Payer Flag" setting in step 705 is complete, a message to that effect is sent to user terminal 2. Then, user terminal 2 displays the information of the vehicle to be added (step 706).

[0307] In this embodiment, the user terminal 2 displays the additional vehicle display screen 118 shown in Figure 25B. The additional vehicle display screen 118 is provided with an additional vehicle display unit 119. The additional vehicle display unit 119 displays information on vehicles belonging to parking lot members whose membership numbers have been read from the QR code and which are currently entered into parking lot 10, as vehicles to be added to the vehicles subject to payment.

[0308] Additionally, to the left of the vehicle's license plate number, an icon 120 will be displayed, representing one letter (for example, the initial) of the parking member "BBBB" who registered the vehicle. Instead of a letter of the user's name, a specific icon indicating that the vehicle is outside the user group may be displayed.

[0309] When user 13 selects the "Next" button on the additional vehicle display screen 118, the vehicle to be paid for is added (step 707). Then, the vehicle selection screen 103 shown in Figure 25C is displayed.

[0310] The vehicle selection screen 103 shown in Figure 25C is the same screen as the vehicle selection screen 103 shown in Figure 23D, but the vehicle selection section 104 displays newly added vehicles. By selecting the newly added vehicle, user 13 can settle parking fees for vehicles belonging to parking members who are not members of the user group.

[0311] The procedure for settlement is the same as when no additional vehicle is being added. That is, by appropriately operating the settlement information display screen 106 shown in Figure 24A, the point usage information screen 108 shown in Figure 24B, the settlement confirmation screen 110 shown in Figure 24C, and the settlement completion screen 114 shown in Figure 24D, it is possible to determine the discount details and settle the payment.

[0312] Once payment is completed for a newly added vehicle, the "Payer Flag" in the user vehicle information for that vehicle will be reset to 0 (temporary linking will be reset).

[0313] Thus, in this parking management system 1, the discount management unit 81 can determine that vehicles registered by parking members who are not members of a user group designated by a user group member are eligible for a discount.

[0314] By enabling payment for vehicles belonging to parking members who are not included in the user group, a high level of convenience can be achieved.

[0315] (Basic flow from entry to payment) Figure 20 is a flowchart showing the basic flow from vehicle entry to payment. Upon entry into parking lot 10, the parking control device 11 captures an image of the entering vehicle and transmits it to the parking management device 3 (step 801).

[0316] The parking management device 3 receives images of entering vehicles and extracts the vehicle license plates. The parked vehicle information shown in Figure 12 is generated (step 803), and the user vehicle information shown in Figure 11 is updated (step 804).

[0317] The user performs the payment operation using user terminal 2. Any user 13 who is a member of the user group can perform the payment operation (even if they are not a parking lot member).

[0318] The user terminal 2 sends an inquiry to the parking management device 3 regarding the group to be settled (step 805). The parking management device 3 transmits the group to be settled based on the member number, which is the login information from the user terminal 2 that made the inquiry (step 806). The group to be settled is the user group to which user 13, who is making the payment, belongs. The group to be settled is displayed on the user terminal 2 (step 807).

[0319] The user terminal 2 sends an inquiry to the parking management device 3 regarding vehicles subject to payment (step 808). The parking management device 3 searches for vehicles belonging to parking members of the user group that are parked in parking lot 10 and sends the information to the user terminal 2 (step 809). The vehicles subject to payment are displayed on the user terminal 2 (step 810).

[0320] A payment instruction is sent from the user terminal 2 to the parking management device 3 (step 811). The parking management device 3 executes the payment process (step 812), and the parked vehicle information and user vehicle information are updated (step 813).

[0321] In addition to this basic flow, this parking management system 1 can perform various processes, such as determining discount details as described above and settling payments for vehicles belonging to users 13 outside of the user group.

[0322] In this parking management system 1, the method and algorithm for determining which vehicles are subject to payment by the discount management unit 81 of the parking management system 1, and the method and algorithm for determining which discounts to apply, are not limited, and any method or algorithm may be adopted.

[0323] For example, instead of "points" that can be used to pay for parking fees, discount information might offer "free parking time." For instance, suppose a discount of "3 hours of free parking" is offered based on a group member "XXXX" using store 7. In such a case, it's possible to split the "3 hours of free parking" into three "1 hour of free parking" periods and apply them to three parked vehicles. This type of discount can also be implemented.

[0324] Any machine learning algorithm, such as DNN (Deep Neural Network), RNN (Recurrent Neural Network), or CNN (Convolutional Neural Network), may be used to determine which vehicles are eligible for payment and which discounts to apply. For example, using AI (Artificial Intelligence) that performs deep learning can enable highly flexible and accurate decisions.

[0325] Furthermore, the application of machine learning algorithms may be performed on any process described in this disclosure. In other words, machine learning-based processing may be performed on any process described in this disclosure.

[0326] (Transfer of discount information) In this parking management system 1, the discount management unit 81 makes it possible to change the owner of discount information generated for each group member. For example, it is possible to change the owner of discount information generated for a specific group member of a user group (e.g., "XXXX") to another group member of the user group (e.g., "YYYY").

[0327] Furthermore, in this parking management system 1, the discount management unit 81 can change the owner of the discount information generated for each group member to a facility user who is not a group member, as specified by the group member.

[0328] For example, referring to Figure 10, it is also possible to change the owner of the discount information generated for each group member ("XXXX", "YYYY", "ZZZZ") of the user group "0001 / Company" with "XXXX" as the representative to one of the group members ("CCCC", "BBBB") of the user group "0003 / School" with "CCCC" as the representative.

[0329] Furthermore, the discount management unit 81 can divide the discount information generated for a designated group member of a user group and assign it to other group members of the user group. Note that "assigning discount information" is equivalent to "changing the owner of the discount information."

[0330] Furthermore, the discount management unit 81 can divide the discount information generated for each group member and grant it to facility users who are not group members, as specified by the group members.

[0331] For example, the settlement completion screen 114 shown in Figure 24D displays a point balance of 800 yen for the [Company] group. Regarding this point balance of 800P, it is possible to change the owner of the discount information within the [Company] group, or to divide it and distribute it to other group members. It is also possible to change the owner of the discount information or divide the discount information and distribute it to a user 13 who is not a member of the [Company] group.

[0332] In this embodiment, selecting the "Point Transfer" button on the settlement completion screen 114 shown in Figure 24D displays the point transfer selection screen 121 shown in Figure 25D. Note that "Point Transfer" is one embodiment of changing the owner of discount information (points).

[0333] The transfer point selection screen 121 in Figure 25D is provided with a transfer point selection section 122. The transfer point selection section 122 displays the remaining discount information (points) for each group member of the user group.

[0334] User 13 can determine which points to transfer (points whose ownership will be changed) by selecting discount information (points) within the point transfer selection section 122. Of course, it is also possible to select multiple discount information (points).

[0335] Figure 26A shows another example of the transfer point selection screen 121. The transfer point selection screen 121 shown in Figure 26A has an input field where the number of points to transfer can be entered directly. The user 13 can select discount information (points) in the transfer point selection section 122 and directly enter the number of points they wish to transfer from among those points.

[0336] In other words, the transfer point selection screen 121 shown in Figure 26A makes it possible to divide the discount information (points) for each group member and transfer them to other group members. The discount information to be transferred can be specified not only by the number of points, but also by the number of points corresponding to parking time, or by a percentage.

[0337] When the "Confirm" button on the migration point selection screen 121 shown in Figures 25D and 26A is selected, the migration destination selection screen 124 shown in Figure 26B is displayed. The migration destination selection screen 124 is provided with a migration destination selection section 125. The migration destination selection section 125 displays group members other than the owner of the user group's migration point.

[0338] When the "Execute Migration" button on the migration destination selection screen 124 shown in Figure 26B is selected, the migration completion screen 126 shown in Figure 26C is displayed. The migration completion screen 126 displays the following information as point migration information. "Transfer Completion Date and Time"... The date and time when the points were transferred. "Source Point Information"... The group members and the number of points to be transferred from the source group. "Information about users at the destination"... User group name, members of the group at the destination, total points held by the members of the group at the destination.

[0339] When transferring points to change the owner of discount information (points) to user 13 who is not a member of the user group, for example, when the "Confirm" button on the point transfer selection screen 121 shown in Figures 25D and 26A is selected, a GUI is displayed to select whether to transfer points to a group member or to user 13 who is not a group member (illustration omitted).

[0340] When the GUI selects whether to transfer points to user 13 who is not a group member, the code image reading screen 127 shown in Figure 26D is displayed. On the code image reading screen 127, the code image displayed on user terminal 2 of user 13 to whom the points are to be transferred is read, and the membership number is extracted.

[0341] Once the information of user 13 is extracted from the extracted member number, the migration destination confirmation screen 128 shown in Figure 27A is displayed. The migration destination confirmation screen 128 displays the information of user 13 who will be the destination, including "member number," "member name," "currently held points," and "number of points to be transferred."

[0342] When the "Execute Migration" button on the migration destination confirmation screen 128 shown in Figure 27A is selected, the migration completion screen 129 shown in Figure 27B is displayed. The migration completion screen 129 displays the following information as point migration information. "Transfer Completion Date and Time"... The date and time when the points were transferred. "Point information from the source"... The number of users (13) from the source and the number of points transferred. "Information about users at the destination"...13 users at the destination, total points held by the users at the destination.

[0343] Once the transfer of discount information (change of owner / assignment of discount information) is complete, the results of that transfer will be reflected in the discount information of the group user information and the store user information.

[0344] Thus, with this parking management system 1, for example, surplus discount information can be passed on to the next user who will be paying. For example, when multiple people and multiple vehicles use a parking lot and the representative leaves first, the representative can pass on their discount information to the other users so that it can be applied to the payment of the vehicle that leaves later. This reduces the burden on the other users and provides high convenience.

[0345] Furthermore, this parking management system 1 allows for the sharing and transfer of discount information for a specified amount to other group members, offering a high level of convenience.

[0346] Furthermore, this parking management system 1 also allows discount information to be transferred to users 13 who are not members of the group. For example, it is possible to divide and transfer surplus discount information from the representative of a user group to users 13 who are not members of the group.

[0347] For example, if a representative and 13 users who are not joint users enter the parking lot 10 together in their respective vehicles and go shopping, the representative can pay and exit first, and then when the 13 users who are not joint users pay and exit later, they can use the representative's discount information to pay, thereby reducing the burden on the 13 users who are not joint users. As a result, a high level of convenience is achieved.

[0348] In the parking management system 1 according to this embodiment, user groups are registered, with parking users (parking members) and store users (store members) as group members. Discount information regarding parking fees incurred by group members using the store is then aggregated, and the vehicles eligible for discounts and the discounts to be applied are determined. This makes it possible to improve convenience for parking users.

[0349] The parking management system 1 according to this embodiment can also be called a parking fee settlement system for a paid parking lot adjacent to a store 7, etc. By applying the present invention, it becomes possible to apply parking discount information obtained by user 13 and multiple co-users linked to user 13 to the parking fees of vehicles subject to settlement by the same user 13 and multiple co-users linked to that user, and to perform settlement.

[0350] Furthermore, by applying the present invention, it becomes possible to settle payments for multiple parked vehicles and to carry over discount information obtained from shopping, etc., for use in the next payment. In addition, it becomes possible to appropriately settle payments for the vehicles that user 13 desires to be settled, by effectively utilizing parking discounts.

[0351] Furthermore, by applying this invention, it becomes easy to implement "bulk payment by a representative," where a representative of a user group settles the payment for all the parked vehicles in the user group at once. Furthermore, it becomes easy to transfer any surplus discount information to the next user of another user's payment system. Furthermore, it becomes easy to implement "discount information splitting," which allows designated discount information to be divided and passed on to other co-users. Furthermore, it becomes easy to implement "proxy payment," where a representative of a user group temporarily pays for vehicles belonging to users not associated with the representative.

[0352] Furthermore, as mentioned above, linking the store application and the parking application with the same membership number makes it easy to reflect discount information in parking payments, resulting in high convenience.

[0353] Furthermore, by applying the present invention, for example, when a group of users such as parents and children or relatives enter a restaurant in multiple vehicles for a meal at a memorial service, it becomes possible to use discount information to make various payments depending on the situation, resulting in extremely high convenience.

[0354] By applying this invention, it becomes possible to implement a simple and fair parking fee system for multiple users who enter with several vehicles. The number of vehicles, the number of users, and the total amount spent on purchases (discount information obtained from purchases) can be appropriately reflected in the parking fee discount. As a result, the convenience for users 13 is greatly improved.

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

[0356] In the above embodiment, becoming a parking lot member was predicated on being a store member, but this is not the only limitation. Even when parking lot member registration and store member registration are performed separately and independently, the present invention can be applied as long as parking lot user information and store user information are linked in any way.

[0357] In the above embodiment, reading a code image is performed as a method for obtaining information about other users 13. However, the method is not limited to this, and other methods may be employed.

[0358] When settling using the exit payment device 28 and the pre-payment device 26, settlement based on the user group may be performed, similar to settlement using the user terminal 2. That is, each GUI exemplified in Figures 21 to 27 may be displayed on the touch panel of the exit payment device 28 and the pre-payment device 26.

[0359] Figure 28 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 3, etc.

[0360] 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.

[0361] 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.

[0362] The parking management method and program execution according to the present invention by a computer system include both cases where group registration, aggregation of discount information, determination of vehicles eligible for discounts and discount details, acquisition of user information, generation of code images, generation of GUIs, settlement processing, etc., 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 part or all of the process executed by another computer 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.

[0363] The parking management system, user terminals, parking management devices, store management devices, parking control devices, exit payment devices, pre-payment devices, and other terminals and devices, the configuration of the user GUI, the operation by the user terminals, parking management devices, store management devices, parking control devices, exit payment devices, pre-payment devices, etc., and the processing flows such as the generation of various information, as described with reference to each drawing, are merely embodiments and can be arbitrarily modified without departing from the spirit of the present invention. In other words, any other configuration or algorithm for carrying out the present invention may be adopted.

[0364] 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.

[0365] 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.

[0366] 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.

[0367] 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]

[0368] As explained above, the technology of the present invention is a technology that can flexibly incorporate shopping discount services and the like at surrounding facilities in a ticketless parking lot. [Explanation of symbols]

[0369] 1…Parking management system 2…User terminal 3…Parking management system 4…Store management system 7 stores 8…Store terminals 10…Parking 11…Parking control system 12…Network 13…User 16… Code image reader 26… Pre-payment device 28...Exit payment device 34... Entering vehicles 35… Participating Vehicles 140… Computer

Claims

1. A group registration section for registering user groups whose group members include parking users who use the parking lot and facility users who use facilities affiliated with the said parking lot, A discount management unit collects discount information regarding parking fees incurred by the use of the facility by the group members of the user group, and determines the vehicles eligible for the discount and the details of the discount to be applied. A parking management system equipped with the following features.

2. A parking management system according to claim 1, The group registration unit registers the facility users who register their vehicles as parking lot users and registers the user group accordingly. Parking management system.

3. A parking management system according to claim 2, further, The system includes a user information acquisition unit that acquires facility user information, including identification information, relating to the facility users. The group registration unit registers the user group based on the identification information included in the acquired facility user information. Parking management system.

4. A parking management system according to claim 3, The user information acquisition unit acquires facility user information relating to facility users who register vehicles, and generates parking lot user information including vehicle information based on the identification information contained in the facility user information. Parking management system.

5. A parking management system according to claim 2, The discount management unit determines that multiple vehicles are eligible for the discount. Parking management system.

6. A parking management system according to claim 2, The discount management unit determines the vehicles eligible for the discount from among the vehicles registered by the parking lot users who are members of the user group. Parking management system.

7. A parking management system according to claim 6, The discount management unit determines that a vehicle registered by a parking lot user who is not a member of the user group, as designated by a member of the user group, is a vehicle eligible for the discount. Parking management system.

8. A parking management system according to claim 2, The discount management unit determines, from among the discount information generated for each of the group members, the applicable discount information to be applied to the vehicle subject to the discount. Parking management system.

9. A parking management system according to claim 8, The discount management unit divides the discount information generated for each of the group members and determines it as the applicable discount information. Parking management system.

10. A parking management system according to claim 2, The discount management unit changes the owner of the discount information generated for each of the group members. Parking management system.

11. A parking management system according to claim 10, The discount management unit changes the owner of the discount information generated for a predetermined group member of the user group to another group member of the user group. Parking management system.

12. A parking management system according to claim 10, The discount management unit changes the owner of the discount information generated for each of the group members to a facility user who is not a group member, as specified by the group member. Parking management system.

13. A parking management system according to claim 10, The discount management unit divides the discount information generated for a predetermined group member of the user group and assigns it to other group members of the user group. Parking management system.

14. A parking management system according to claim 10, The discount management unit divides the discount information generated for each of the group members and assigns it to facility users who are not group members, as specified by the group members. Parking management system.

15. A parking management system according to claim 3, further, The system includes a GUI generation unit that generates a GUI (Graphical User Interface) for parking lot users and transmits it to the user terminal of the parking lot user. Information processing system.

16. A parking management system according to claim 15, The discount management unit aggregates the discount information generated for each of the group members of the user group based on the identification information of each of the group members. The GUI generation unit displays the aggregated discount information on the parking lot user GUI in a manner that allows the owner of the discount information to be identified. Parking management system.

17. A parking management system according to claim 15, The GUI generation unit displays vehicles registered by parking lot users that belong to the user group, which includes the group member who has entered an input indicating that they will settle the parking fee, as vehicles subject to settlement in the parking lot user GUI. Parking management system.

18. A parking management system according to claim 3, The group registration unit registers the user group with the parking lot user who entered the intention to create the user group as the representative, and the facility users designated by the representative as co-users. Parking management system.

19. A parking management system according to claim 18, Each of the user terminals of the parking lot users and the user terminals of the facility users is capable of displaying a code image containing the identification information and extracting the identification information from the code image. The group registration unit registers the facility users identified by the identification information extracted from the code image by the user terminal of the representative as the user group of the joint users. Parking management system.

20. A parking management system according to claim 1, The discount management unit determines the vehicles eligible for the discount and the discount details based on the instructions of the group members of the user group. Parking management system.

21. A parking management system according to claim 3, further, The facility is equipped with a facility terminal that is located in the facility and extracts the identification information from a code image containing the identification information displayed on the user terminal of the facility user, associates it with the facility user's usage information regarding the facility, and transmits it as settlement information. Parking management system.

22. Register a user group whose members include parking lot users and facility users who use facilities affiliated with the aforementioned parking lot. The system collects discount information regarding parking fees incurred by the group members of the user group using the facility, and determines which vehicles are eligible for the discount and what discounts to apply. A parking management method performed by a computer system.

23. Register a user group whose members include parking lot users and facility users who use facilities affiliated with the aforementioned parking lot. The system collects discount information regarding parking fees incurred by the group members of the user group using the facility, and determines which vehicles are eligible for the discount and what discounts to apply. A program that causes a computer system to perform a task.

Images