Facility management system, facility management device, facility management method, and program

Abstract

To provide a facility management system, a facility management method, and a program that enable improved convenience for users of facilities such as parking lots. [Solution] This facility management system is a facility management system for managing facilities that can be used by users using their vehicles, and comprises an acquisition unit, a management unit, a code image generation unit, and a GUI generation unit. The acquisition unit acquires user-related information concerning at least one of the user and the vehicle from a facility-side wireless device that performs wireless communication with a vehicle-side wireless device installed in the vehicle when the vehicle enters the facility. The management unit manages history information regarding the user's use of the facility based on the user-related information. The code image generation unit generates a first code image that includes user identification information to identify the user. The GUI generation unit generates a user GUI for displaying the history information and the first code image, and transmits it to the user's terminal.

Description

Technical Field

[0005]

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

Background Art

[0002] Conventionally, in a paid parking lot, a facility usage fee management system has been realized that manages vehicles equipped with ETC on-vehicle units from entry to exit and automatically settles the usage fees of the parking lot by ETC settlement.

[0003] In addition, in a paid parking lot for ETC vehicles provided adjacent to a commercial facility these days, a facility usage fee management system has also been realized that reflects a fee discount according to the shopping amount in the commercial facility for the parking fee.

[0004] Patent Document 1 discloses a parking lot server that can perform cashless settlement of a parking fee with discount information reflected by an ETC system. In this parking lot server, ETC information is received from an entry ETC roadside unit provided at the entrance of the parking lot. The parking lot server also receives, from a store terminal related to a store, the code information of the ETC information and the discount information corresponding to the code information. The parking lot server can generate a request information for a parking fee with discount information reflected based on the received information, and cashless settlement is executed based on the generated request information.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] Thus, in facilities such as parking lots, technologies capable of improving the convenience of users are required.

[0007] In view of the above circumstances, the object of the present invention is to provide a facility management system, a facility management method, and a program that can improve the convenience of users of facilities such as parking lots. [Means for solving the problem]

[0008] To achieve the above objective, a facility management system according to one embodiment of the present invention is a facility management system for managing facilities that can be used by users with a vehicle, and comprises an acquisition unit, a management unit, a code image generation unit, and a GUI (Graphical User Interface) generation unit. The acquisition unit acquires user-related information concerning at least one of the user and the vehicle from a facility-side wireless device that communicates wirelessly with a vehicle-side wireless device installed in the vehicle when the vehicle enters the facility. The management unit manages historical information regarding the user's use of the facility based on the user-related information. The code image generation unit generates a first code image that includes user identification information to identify the user. The GUI generation unit generates a user GUI for displaying the history information and the first code image, and transmits it to the user's terminal.

[0009] The facility management system may further include a settlement processing unit that performs settlement processing for the user's use of the facility.

[0010] The facility management system may further include a facility terminal located in another facility available to the user, which reads the user identification information from the first code image, associates the read user identification information with the user's usage information for the other facility, and transmits it as settlement information.

[0011] The facility terminal may transmit the settlement information to the settlement processing unit. In this case, the settlement processing unit may calculate the usage fee for the user's use of the facility based on the date and time of entry into the facility and the settlement information.

[0012] The facility management system may further include a pre-payment device that accepts pre-payment operations from the user. In this case, the pre-payment device may read the user identification information from the first code image and transmit the read user identification information to the payment processing unit. The payment processing unit may also calculate the usage fee for the user's use of the facility based on the user identification information and transmit it to the pre-payment device.

[0013] The facility management system may further include an output terminal located in the other facility available to the user, which outputs a second code image containing usage information relating to the user's use of the other facility. In this case, the settlement processing unit may calculate the usage fee for the user's use of the facility based on the usage information read from the second code image by the user terminal.

[0014] The aforementioned history information may include settlement fees corresponding to the use of the aforementioned facilities.

[0015] The aforementioned history information may include information regarding the current use of the facility, corresponding to the case when the vehicle is entering the facility.

[0016] The GUI generation unit may display the first code image on the user GUI when predetermined conditions relating to the user are met.

[0017] The facility management system may further include a storage unit that stores information indicating that the vehicle is entering the facility. In this case, the GUI generation unit may display the first code image on the user GUI when the vehicle is entering the facility.

[0018] The GUI generation unit may display, on the user GUI, the number of times the vehicle can enter the facility without incurring a fee.

[0019] The facility management system may further include the facility-side wireless device.

[0020] The vehicle-side wireless device may be an ETC (Electronic Toll Collection) in-vehicle unit. In this case, the facility-side wireless device may be an ETC roadside unit.

[0021] A facility management device according to an aspect of the present invention is a facility management device for managing a facility that can be used by a user using a vehicle, and includes the acquisition unit, the management unit, the code image generation unit, and the GUI generation unit.

[0022] A facility management method according to an aspect of the present invention is a facility management method executed by a computer system for managing a facility that can be used by a user using a vehicle, and includes obtaining user-related information regarding at least one of the user and the vehicle from a facility-side wireless device that performs wireless communication with a vehicle-side wireless device mounted on the vehicle when the vehicle enters the facility. Based on the user-related information, history information regarding the user's use of the facility is managed. A first code image including user identification information for identifying the user is generated. A user GUI for displaying the history information and the first code image is generated and transmitted to the user's user terminal.

[0023] A program according to an aspect of the present invention is a program for causing a computer system to execute the facility management method.

Advantages of the Invention

[0024] As described above, according to the present invention, it becomes possible to improve the convenience of users who use facilities such as parking lots.

Brief Description of Drawings

[0025] [Figure 1] It is a schematic diagram showing a configuration example of a parking lot management system according to an embodiment of the present invention. [Figure 2] It is a schematic diagram showing a configuration example of a parking lot. [Figure 3] It is a block diagram showing a hardware configuration example of a ticket issuing device. [Figure 4] It is a block diagram showing a hardware configuration example of an exit settlement device. [Figure 5] It is a block diagram showing a hardware configuration example of a pre-settlement device. [Figure 6] It is a block diagram showing a functional configuration example of a parking lot management device. [Figure 7] It is a diagram showing an example of information stored in each of a user information DB, a member's parked car DB, a discount information DB, and a usage history DB constructed in a DB. [Figure 8] It is a flowchart showing an operation example of the parking lot management system when a vehicle enters the parking lot. [Figure 9] It is a flowchart showing an operation example of the parking lot management system when a vehicle exits the parking lot. [Figure 10] It is a schematic diagram showing an example of a user GUI. [Figure 11] It is a schematic diagram showing an example of a user GUI. [Figure 12] It is a diagram showing an example of a discount code ticket. [Figure 13] It is a schematic diagram for explaining an example of using a code image. [Figure 14] It is a diagram showing an example of a variation of a user GUI. [Figure 15] It is a block diagram showing a hardware configuration example of a computer that can be used as a parking lot management device or the like.

Modes for Carrying Out the Invention

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

[0027] [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. Figure 2 is a schematic diagram showing an example configuration of a parking lot.

[0028] The parking management system 1 corresponds to one embodiment of the facility management system according to the present invention for managing facilities that can be used by a user 2 using a vehicle 3. The parking lot 4 also corresponds to one embodiment of a facility that can be used by a user 2 using a vehicle 3.

[0029] The parking lot 4 according to this embodiment can be used by both vehicles equipped with an ETC device (ETC vehicles) and vehicles not equipped with an ETC device (non-ETC vehicles).

[0030] As shown in Figure 1, the parking management system 1 includes a mobile terminal 5, a parking management device 6, a management agency terminal 7, a payment server device (not shown) owned by the payment agency 8, a store terminal 10 located at the store 9, and an owner terminal 11.

[0031] The parking management system 1 also includes a ticket issuing device 13, a pre-payment device 14, an exit payment device 15, an entrance roadside device 16, and an exit roadside device 17, all located in the parking lot 4. Of these, the ticket issuing device 13 and the exit payment device 15 are primarily operated by users 2 of vehicles not equipped with ETC.

[0032] The mobile terminal 5, parking management device 6, management agency terminal 7, payment server device of the payment agency 8, store terminal 10, owner terminal 11, and pre-payment device 14 are all connected to each other via a network 18 so that they can communicate with one another. The network 18 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 the network 18 is not limited.

[0033] The mobile terminal 5 is a terminal used by user 2 who uses the parking lot 4, and functions as one embodiment of the user terminal according to the present invention. Typically, a smartphone is used as the mobile terminal 5, but it is not limited to this, and various PDAs (Personal Digital Assistants) such as tablet terminals may be used. The mobile terminal 5 has the function of reading the second code image according to the present invention, which will be described later.

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

[0035] The parking management device 6 is a device that manages the parking lot 4, and can provide the parking management service according to this embodiment as a web service. The parking management device 6 functions as one embodiment of the facility management device according to the present invention.

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

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

[0038] As shown in Figure 1, a database (DB) 19 is connected to the parking management device 6. DB 19 functions as a storage unit and stores various information related to this parking management service. For example, it is possible to construct various databases within DB 19, such as a user information DB (see Figure 7A), a member vehicle presence DB (see Figure 7B), a non-member vehicle presence DB, a discount information DB (see Figure 7C), a usage history DB (see Figure 7D), a parking information DB, a store usage DB, an owner information DB, various history DBs, a parking ticket information DB, and a management information DB.

[0039] Various databases are comprehensively managed by the parking management device 6, which performs tasks such as registering and canceling memberships of users 2 who use the parking management service, managing the usage status of each parking lot 4, registering and storing owner information for each parking lot 4, and recording and storing operational revenue and expenditure information.

[0040] In this embodiment, a web page is generated by the parking management device 6. The generated web page is displayed on the screens of the mobile terminal 5, the parking management device 6, the management agency terminal 7, the payment server device of the payment agency 8, the store terminal 10, and the owner terminal 11 via the network 18 shown in Figure 1, using web browsers installed in each.

[0041] For example, users 2 who use parking lot 4, and the owner of parking lot 4, can access various web pages and use various web applications by operating their mobile device 5 or owner's device 11.

[0042] The management agency terminal 7 is used by an operator of the management agency that has been entrusted with the management of parking lot 4 by the owner of parking lot 4. A PC or tablet device may be used as the management agency terminal 7.

[0043] In some cases, the owner of parking lot 4 may also manage the parking lot 4 themselves. In this case, the owner's terminal can function as the management agency terminal 7. Alternatively, a management agency entrusted with management duties may own the parking lot management device 6 and provide the parking lot management service according to this embodiment.

[0044] The payment institution 8 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 6 issues instructions to the payment server device of the payment institution 8 for the settlement of parking fees, and queries for settlement information such as whether the settlement has been completed. The payment institution 8 may also include institutions that provide various code payment services.

[0045] The store terminals 10 are placed in each store 9 that has a partnership with the parking lot 4 for discount services. For example, this could include partnerships with nearby commercial facilities for discount services, but it is not limited to this.

[0046] For example, in a commercial facility adjacent to parking lot 4, if user 2 of parking lot 4 makes purchases or other purchases within the commercial facility, a discount service is provided where the parking fee is discounted or waived depending on the amount spent. For example, each store in the commercial facility has at least one cash register, and a cash register management device is installed to integrate these. The cash register management device may also be a POS server. Note that the cash register management device is not necessarily installed within the commercial facility. The parking lot management device 6 manages the parking lot in association with the affiliated commercial facility.

[0047] In the example shown in Figure 1, a POS register with communication capabilities is used as the store terminal 10. A code image reader 20 and a discount code ticket issuing device 21 are connected to the store terminal 10 of store 9A. The code image reader 20 is composed of, for example, an optical reading device with a built-in laser scanner and has the function of reading the first code image according to the present invention, which will be described later. The discount code ticket issuing device 21 issues a discount code ticket including the second code image according to the present invention.

[0048] On the other hand, in store 9b, only the discount code issuing device 21 is connected to the store terminal 10, and the code image reader 20 is not connected. The present invention is also applicable to such a store 9b.

[0049] In this embodiment, each store 9 corresponds to an embodiment of another facility available to users according to the present invention. Furthermore, the store terminal 10 equipped with a code image reader 20 functions as an embodiment of a facility terminal according to the present invention. Furthermore, the store terminal 10 equipped with a discount code ticket issuing device 21 functions as an embodiment of an output terminal according to the present invention. In other words, in store 9a, the store terminal 10 realizes both a facility terminal and an output terminal according to the present invention. Of course, the invention is not limited to this, and the facility terminal and the output terminal may be configured separately.

[0050] Furthermore, for example, the store terminal 10 and the parking management device 6 can indirectly share information regarding parking fee discounts (discount rates, discount times, etc.) via a POS server or the like. The specific configuration and types of the store terminal 10, the code image reader 20, and the discount code ticket issuing device 21 are not limited.

[0051] As shown in Figure 2, parking lot 4 is equipped with a ticket issuing device 13, a pre-payment device 14, an exit payment device 15, an entrance roadside device 16, and an exit roadside device 17. Parking lot 4 is also equipped with an entrance gate 23 and an exit gate 24.

[0052] The ticket issuing device 13, entrance gate 23, and entrance roadside device 16 are located near the entrance lane 25 for allowing vehicles 3 to enter the parking lot 4. An entrance loop coil 26 for detecting the presence and passage of vehicles 3 is also embedded in the entrance lane 25.

[0053] The pre-payment device 14 is located within the parking lot 4 and accepts pre-payment operations from users 2. In this embodiment, the pre-payment device 14 also functions as a master unit that relays communication between each device located in the parking lot 4 and devices located outside.

[0054] The exit payment device 15, exit gate 24, and exit roadside device 17 are located near the exit lane 27 for allowing vehicles 3 to exit the parking lot 4. An exit loop coil 28 is also embedded in the exit lane 27.

[0055] Furthermore, the ticketing device 13, the pre-payment device 14, the exit payment device 15, the entrance roadside device 16, the exit roadside device 17, the entrance gate 23, and the exit gate 24 are connected by internal wiring 29 installed within the parking lot 4. Instead of internal wiring 29, a local network using wireless communication may be constructed.

[0056] Figure 3 is a block diagram showing an example of the hardware configuration of the ticket issuing device 13. The ticket issuing device 13 has a CPU 31, a memory 32, and an interface 34 connected to these via a bus 33. The memory 32 is composed of, for example, ROM, RAM, flash memory, etc., and stores various programs and various parking data. Of course, the ticket issuing device 13 may also be equipped with a storage device such as an HDD.

[0057] Interface 34 is connected to the on-premises communication unit 35, parking ticket printer 36, card feeder 37, display 38, and speaker 39. The operation of each block is controlled by a CPU 31 that operates according to a program.

[0058] The premises communication unit 35 is equipped with a communication circuit for communicating with other devices within the premises and is connected to other devices via premises wiring 29 in a communicative manner.

[0059] The parking ticket printer 36 prints the necessary information on the parking ticket issued to user 2 who will be using parking lot 4.

[0060] The card feeder 37 supplies blank parking tickets stocked in the device to the parking ticket printer 36, prints them, and then issues them to the user 2. The display 38 has an image display function. The speaker 39 has an audio output function. For example, the display 38 and speaker 39 can display operation guidance and output audio. The specific configuration of the card feeder 37, display 38, and speaker 39 is not limited, and any configuration may be adopted.

[0061] The entrance gate 23 shown in Figure 2 is positioned further forward in the direction of travel than the ticket issuing device 13 of the entrance lane 25. The specific configuration of the entrance gate 23 is not limited, and any configuration may be adopted.

[0062] The entrance roadside device 16 is positioned further forward in the direction of travel than the entrance gate 23 of the entrance lane 25. However, it is not limited to this, and the entrance roadside device 16 may be positioned before the entrance gate 23 in the direction of travel.

[0063] The entrance roadside device 16 is a device for realizing ETC communication and consists of, for example, a DSRC (Dedicated Short Range Communications) antenna and a roadside unit. The entrance roadside device 16 is capable of wireless communication with the ETC onboard unit (not shown) installed in the vehicle 3.

[0064] To briefly explain ETC, each ETC onboard unit has a unique ID called a Wireless Call Number (WCN). After installing it in a vehicle, the unit is set up. Onboard unit setup is the process of registering vehicle information necessary to use ETC services (especially ETC2.0) and to prevent billing errors when using toll roads with different toll systems depending on the vehicle type, and to enable the ETC onboard unit to be used. Specifically, the vehicle information listed on the vehicle registration certificate is registered in the ETC onboard unit. Typically, all information on the license plate (4-digit serial number, name of the land transport bureau, classification number (3 digits), usage number (in kana)), as well as the vehicle identification number, manufacturer name, weight, dimensions, etc., are registered.

[0065] The entrance roadside device 16 receives ETC information from the ETC onboard unit. The ETC information includes, for example, vehicle information such as the onboard unit management number, WCN, and vehicle number registered in the ETC onboard unit, as well as ETC card information stored on the ETC card inserted into the ETC onboard unit, such as the ETC card number and user information. The ETC information is encrypted during transmission to protect against malicious unauthorized access.

[0066] The ETC information received by the entrance roadside device 16 is transmitted to the parking management device 6 via the prepayment device 14.

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

[0068] Interface 44 is connected to the local communications unit 45, receipt printer 46, banknote and coin management unit 47, touch panel 48, and speaker 49. The operation of each block is controlled by the CPU 41, which operates according to a program.

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

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

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

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

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

[0074] The exit gate 24 shown in Figure 2 is positioned further forward in the direction of travel than the exit payment device 15 of the exit lane 27. The specific configuration of the exit gate 24 is not limited, and any configuration may be adopted.

[0075] The exit roadside device 17 is positioned ahead of the exit gate 24 in the direction of travel of the exit lane 27. However, it is not limited to this, and the exit roadside device 17 may be positioned before the exit gate 24 in the direction of travel.

[0076] The exit roadside device 17 is a device for realizing ETC communication and has the same configuration as the entrance roadside device 16. The exit roadside device 17 is capable of wireless communication with the ETC onboard unit (not shown) installed in the vehicle 3 and receives ETC information from the ETC onboard unit.

[0077] The ETC information received by the exit roadside device 17 is transmitted to the parking management device 6 via the prepayment device 14.

[0078] Figure 5 is a block diagram showing an example of the hardware configuration of the pre-payment device 14. The pre-payment device 14 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 14 may also be equipped with a storage device such as an HDD.

[0079] Interface 54 is connected to an external communication unit 55, a code image reader 56, an internal communication unit 57, a card reader 58, a banknote / 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.

[0080] The external communication unit 55 is configured to communicate with each device shown in Figure 1 via the network 18. Examples of external communication units 55 include wireless LAN modules such as WiFi, and communication devices such as modems and routers. Alternatively, the external communication unit 55 may also include communication modules such as Bluetooth®, or mobile communication modules such as 5G or LTE.

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

[0082] 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 the first code image and the second code image according to the present invention.

[0083] 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 15.

[0084] 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 15. Of course, other configurations may also be used.

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

[0086] Figure 6 is a block diagram showing an example of the functional configuration of the parking management device 6. Figure 7 is a diagram showing an example of the information stored in each of the user information database, member vehicle occupancy database, discount information database, and usage history database built within DB19.

[0087] As shown in Figure 6, the parking management device 6 includes a user information management unit 65, an ETC information receiving unit 66, a vehicle occupancy information management unit 67, a discount information management unit 68, a usage history management unit 69, a code image generation unit 70, a GUI generation unit 71, and a settlement processing unit 72.

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

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

[0090] The user information management unit 65 manages information about users 2 of the parking lot 4 who have registered with the parking lot management service (hereinafter sometimes referred to as members). In this embodiment, the user information management unit 65 generates and manages user information 74 as shown in Figure 7A. User information 74 can also be called member information.

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

[0092] "Membership Number"... A number assigned to each member. "Name"... The member's name. "ETC Information"... ETC information associated with the member. For example, it stores the on-board unit management number and WCN of the ETC on-board unit installed in the member's vehicle 3, vehicle information registered in the ETC on-board unit, and ETC card information of the ETC card used by the member.

[0093] In this embodiment, the entrance roadside device 16 and the exit roadside device 17 receive ETC information from the ETC onboard unit so that it includes at least the information stored as "ETC information" in the user information 74.

[0094] "Payment Method 1," "Payment Method 2"... These are the payment methods for each member's parking fees. For example, credit card payment using an ETC card with credit functionality can be registered. Of course, it is possible to register multiple payment methods, such as credit card payments using other credit cards or QR code payments. "Email address"...an email address. In this embodiment, an email address that can be received and viewed by the mobile device 5 is registered. "Password"...Login password. In addition, personal information of User 2 (member) may be registered as appropriate. For example, individual contract information (regular use, conditions for multiple uses per day, etc.) may be recorded and managed.

[0095] The ETC information receiving unit 66 receives and manages ETC information transmitted from the entrance roadside device 16 and the exit roadside device 17 of the parking lot 4.

[0096] The vehicle occupancy information management unit 67 manages information on vehicles 3 parked in the parking lot 4. In this embodiment, the vehicle occupancy information management unit 67 generates and manages member-only vehicle occupancy information 75 shown in Figure 7B.

[0097] As shown in Figure 7B, in this embodiment, the following information (data) is stored as member vehicle information 75.

[0098] "Membership Number"... A number assigned to each member. "Entry Date and Time"... The date and time when the member's vehicle 3 enters the parking lot 4. For example, the date and time when the entrance gate 23 is opened, or the date and time when vehicle 3 enters the premises of the parking lot 4 as detected via the entrance loop coil 26, can be used as the "Entry Date and Time".

[0099] "ETC information"...ETC information transmitted from the entrance roadside device 16 and received by the ETC information receiving unit 66. "Settlement Date and Time"... The date and time when the payment for parking lot 4 was settled. "Discount Information"... Information regarding discounts that are incurred based on the use of store 9. In this embodiment, a link to discount information 76 shown in Figure 7C is stored. "Settlement fee"...the fee that has been settled.

[0100] Note that "Settlement Date and Time" and "Settlement Fee" will remain blank until the payment for parking lot 4 is settled. "Discount Information" will be stored with a link generated when the discount information 76 shown in Figure 7C is generated. Other information may be stored as member-only vehicle occupancy information 75.

[0101] The discount information management unit 68 manages information regarding discounts that are generated in accordance with the use of store 9. In this embodiment, the discount information management unit 68 generates and manages the discount information 76 shown in Figure 7C.

[0102] As shown in Figure 7C, in this embodiment, the following information (data) is stored as discount information 76.

[0103] "Membership Number"... A number assigned to each member. "Store Number"... A number assigned to each of the 9 stores that are affiliated with Parking Lot 4. "Shopping Date and Time"... The date and time the member made a purchase. "Discount amount"... The amount of the discount applied to the purchase. Each time a member makes a purchase at store 9 and a discount is applied, the "store number," "purchase date and time," and "discount amount" are stored in discount information 76. In addition, various other information, such as conditions indicating the relationship between the purchase amount and the discount amount, may be stored.

[0104] The usage history management unit 69 manages historical information regarding each member's use of the parking lot 4, from the past to the present. In this embodiment, the usage history management unit 69 generates and manages the history information 77 shown in Figure 7D.

[0105] As shown in Figure 7D, in this embodiment, the following information (data) is stored as history information 77.

[0106] "Membership Number"... A number assigned to each member. "Entry Date and Time"... The date and time when the member's vehicle 3 entered parking lot 4. "Discount Information"... Information regarding discounts that are incurred based on the use of store 9. In this embodiment, a link to discount information 76 shown in Figure 7C is stored. "Settlement fee"... Settlement fee corresponding to the use of Parking Lot 4 (facility). "Departure Date and Time"... The date and time when the member's vehicle 3 leaves the parking lot 4. For example, the date and time when the exit gate 24 is opened, or the date and time when vehicle 3 leaves the premises of the parking lot 4 as detected via the exit loop coil 28, can be used as the "Departure Date and Time". In addition, any information related to the use of parking lot 4, such as "settlement date and time," may be stored as history information 77. For example, various information such as entry and exit history with ETC vehicle information from the past to the present, and toll collection history may be recorded and managed.

[0107] The code image generation unit 70 generates a first code image containing user identification information that can identify user 2, who is registered as a member. In this embodiment, the first code image is generated in which the "member number" is stored as the user identification information.

[0108] The GUI generation unit 71 generates a user GUI for displaying the history information 77 and the first code image, and sends it to the user 2's mobile terminal 5.

[0109] The settlement processing unit 72 performs the settlement process for user 2's use of parking lot 4. For example, the settlement processing unit 72 calculates the usage fee for each user 2 (including members and non-members) and performs the settlement process. At this time, if a discount is applied due to the use of store 9, the usage fee reflecting the discount is calculated and the settlement process is performed.

[0110] In this embodiment, the settlement processing unit 72 performs ETC automatic payment. Note that ETC automatic payment can be performed not only by member user 2, but also by non-member user 2. In addition, various other settlement processes, such as point settlement, debit card payment, and electronic money payment, may be performed.

[0111] In this embodiment, the settlement processing unit 72 determines whether ETC automatic payment is possible when an ETC vehicle enters or exits the vehicle, including whether or not prepayment is required and whether or not there are any shopping discounts. The settlement processing unit 72 also selects a payment institution based on the user information 74 and sends and receives payment information.

[0112] Furthermore, the settlement processing unit 72 can calculate the usage fee for each user 2 based on requests from the pre-payment device 14 or the mobile terminal 5, and notify the pre-payment device 14 or the mobile terminal 5. Of course, if a discount is applied as a result of using the store 9, it is possible to calculate the usage fee reflecting the discount and notify the pre-payment device 14 or the mobile terminal 5.

[0113] In this embodiment, the ETC information receiving unit 66 functions as one embodiment of an acquisition unit that acquires user-related information concerning at least one of the user and the vehicle from a facility-side wireless device that performs wireless communication with a vehicle-side wireless device mounted on the vehicle when the vehicle enters the facility, according to the present invention.

[0114] Furthermore, parking lot 4 corresponds to one embodiment of the facility, and the ETC onboard unit corresponds to one embodiment of a vehicle-side wireless device installed in a vehicle. In addition, the entrance roadside device 16 and the exit roadside device 17 correspond to one implementation form of the facility-side wireless device.

[0115] Furthermore, ETC information corresponds to one embodiment of user-related information relating to at least one of the user and the vehicle. For example, ETC card information such as the ETC card number is included in the user information. Also, the on-board unit management number, WCN (Wireless Call Number), and vehicle information registered in the ETC on-board unit are included in the vehicle information.

[0116] Furthermore, the ETC information receiving unit 66 and the usage history management unit 69 function as one embodiment of a management unit that manages historical information regarding a user's use of the facility based on user-related information according to the present invention. In this embodiment, by referring to the user information 74 shown in Figure 7A, the ETC information receiving unit 66 extracts the "member number," which is user identification information. Then, for each extracted "member number," the history information 77 shown in Figure 7D is generated and managed.

[0117] Furthermore, the code image generation unit 70 functions as one embodiment of the code image generation unit according to the present invention, which generates a first code image including user identification information that identifies a user. In this embodiment, "member number" is used as one embodiment of the user identification information, but any information that can identify user 2 may be used. For example, an ETC card number may be used.

[0118] Furthermore, the GUI generation unit 71 functions as one embodiment of a GUI generation unit that generates a user GUI for displaying history information and the first code image, and transmits it to the user's terminal.

[0119] Furthermore, the settlement processing unit 72 functions as one embodiment of a settlement processing unit that performs settlement processing for the user's use of the facility.

[0120] Figure 8 is a flowchart showing an example of the operation of the parking management system 1 when vehicle 3 enters parking lot 4. The entrance loop coil 26 monitors whether or not vehicle 3 has been detected (step 101). If vehicle 3 is detected (YES in step 101), the entrance roadside device 16 is activated (step 102). The entrance roadside device 16 determines whether or not ETC information has been received (step 103). In this embodiment, it is assumed that the ETC information includes ETC card information.

[0121] If wireless communication is performed between the ETC onboard unit installed in vehicle 3 and the ETC information is received (YES in step 103), the ETC information is transmitted to the ETC information receiving unit 66 of the parking management device 6. The ETC information receiving unit 66 then determines, based on the ETC card information, whether or not the ETC card is a usable card (step 104).

[0122] There are several types of ETC cards, such as ETC cards issued by various credit card companies, ETC Corporate Cards, and ETC Personal Cards. Step 104 determines whether the ETC card is a type of ETC card that can be used with this parking management system 1. Of course, it is also possible to build this parking management system 1 to support all ETC cards. In that case, step 104 is omitted.

[0123] If the ETC card is a valid card (YES in step 104), the ETC normal flag is set and stored in DB19 (step 105). Note that the ETC normal flag is set in step 105 not only for member user 2 but also for non-member user 2 if a valid ETC card is inserted.

[0124] When the ETC normal flag is set, entrance gate 23 opens (step 106).

[0125] If the ETC card is not a valid card (NO in step 104), the ETC error flag is set and stored in DB19 (step 107).

[0126] If ETC information cannot be received in step 103 (NO), or if the ETC abnormality flag is set in step 106, the ticket issuing device 13 is activated and a parking ticket is issued (step 108). Then, the entrance gate 23 is opened (step 106).

[0127] The entrance loop coil 26 monitors whether or not vehicle 3 has passed through the entrance gate 23 (step 109). When vehicle 3 passes through the entrance gate 23 (YES in step 109), vehicle occupancy information is generated (step 110).

[0128] If user 2 is a member, member-only vehicle presence information 75 shown in Figure 7B is generated. For user 2 who is not a member but can use an ETC card, non-member-only vehicle presence information is generated, which includes information that the ETC card can be used. This vehicle presence information also stores the information necessary for ETC card payment.

[0129] For user 2, who has been issued a parking ticket, non-member vehicle occupancy information is generated, which includes information indicating that a parking ticket has been issued. This vehicle occupancy information also stores information necessary for payment at the pre-payment device 14 and the exit payment device 15.

[0130] The entrance roadside device 16 and the ticket issuing device 13 stop operating (turn OFF), and the entrance gate 23 is closed (step 111).

[0131] Figure 9 is a flowchart showing an example of the operation of the parking management system 1 when vehicle 3 exits parking lot 4. The exit loop coil 28 monitors whether or not vehicle 3 has been detected (step 201). If vehicle 3 is detected (YES in step 201), the exit roadside device 17 is activated (step 202). The exit roadside device 17 determines whether or not ETC information has been received (step 203).

[0132] If wireless communication is performed between the ETC onboard unit installed in vehicle 3 and the ETC information is received (YES in step 203), the ETC information is transmitted to the ETC information receiving unit 66 of the parking management device 6. The ETC information receiving unit 66 then determines whether or not the ETC card is a usable card (step 204). This determination is performed by referring to the ETC normal flag / ETC abnormal flag. Of course, this determination may also be performed based on the ETC card information.

[0133] If the ETC card is a usable card (YES in step 204), the settlement processing unit 72 determines whether or not the payment for parking lot 4 has been settled (step 205).

[0134] If user 2 is a member, the member-only vehicle information 75 shown in Figure 7B is referenced, and if the "settlement date and time" and "settlement amount" are stored, it is determined that payment has been made (YES). For example, if user 2, who is a member, makes a prepayment using the prepayment device 14, the "settlement date and time" and "settlement amount" are stored in the member-only vehicle information 75, and it is determined that payment has been made.

[0135] If the "Payment Date and Time" and "Payment Amount" are not stored in the member's vehicle information 75, it is determined that payment has not been made (NO). A flag or similar indicator to show whether payment has been made may be set as appropriate.

[0136] In this embodiment, for user 2, who is not a member but has an ETC card, payment other than ETC automatic payment is not possible (only ETC automatic payment is possible), so it is determined that payment has not been made (NO).

[0137] If payment for parking lot 4 has been made (YES in step 205), exit gate 24 will open (step 209). If payment for parking lot 4 has not been made (NO in step 205), ETC automatic payment will be performed (step 206). Then, exit gate 24 will open (step 209).

[0138] In this parking management system 1, for example, for member users 2 who have made advance payments, member users 2 who have not made advance payments, and non-member users 2 who can use an ETC card, the exit gate 24 is automatically opened when vehicle 3 moves to exit lane 27. If a predetermined amount of time elapses before vehicle 3 exits and a charge is incurred again, the additional charge will be automatically settled by ETC and the exit gate 24 will be opened.

[0139] If ETC information cannot be received (NO in step 203), or if the ETC card is not a usable card (NO in step 204), the exit payment device 15 is activated (step 207).

[0140] The exit payment device 15 queries the parking management device 6 to inquire whether or not payment for parking lot 4 has been made. The parking management device 6 determines whether or not payment has been made by referring to the occupancy information for non-members, which includes information that a parking ticket has been issued (step 208). For example, if user 2, who was issued a parking ticket, has made a prepayment using the prepayment device 14, the payment will be considered made.

[0141] If user 2, who has been issued a parking ticket, has not made a prepayment, they will be prompted to make a payment via the exit payment device 15 (for example, by outputting an audio guidance), and the payment will be marked as completed once user 2 has made the payment.

[0142] Once user 2, who has been issued a parking ticket, has paid (YES in step 208), exit gate 24 opens (step 209).

[0143] The exit loop coil 28 monitors whether or not vehicle 3 has passed through the exit gate 24 (step 210). When vehicle 3 passes through the exit gate 24 (YES in step 210), the vehicle occupancy information is deleted and history information is generated / updated (step 212).

[0144] If user 2 is a member, the member-only vehicle information 75 is deleted from the member-only vehicle database shown in Figure 7B. Then, the history information 77 shown in Figure 7D is generated / updated. If no history information 77 exists for user 2, new history information 77 is generated. If history information 77 has been generated in the past, information regarding the use of parking lot 4 in the current instance is added to that history information 77.

[0145] For non-member users 2 (users 2 who can use an ETC card and users 2 who have been issued a parking ticket), the non-member vehicle presence information is deleted. Then, non-member history information is generated and stored in DB19.

[0146] The exit roadside device 17 and the exit payment device 15 stop operating (turn OFF), and the exit gate 24 is closed (step 213).

[0147] [User GUI] In this parking management system 1, the GUI generation unit 71 provides a user GUI to the user 2 who becomes a member. The user GUI is displayed on the screen via the web browser of the mobile terminal 5.

[0148] User 2 accesses the website providing this parking management service by, for example, entering a designated URL into the browser of their mobile device 5 (or scanning a designated QR code (registered trademark)). This allows them to operate the user GUI described below on the web application.

[0149] Of course, this is not the only option, and the parking management service may also be provided via a native application. In this case, the application program for the parking management service is downloaded to user 2's mobile device 5. By launching the application, user 2 can operate the user GUI. Various other forms of operation for the user GUI may also be employed.

[0150] Figures 10 and 11 are schematic diagrams showing an example of a user GUI. Figure 10A shows the new registration / login screen 79 as displayed as the user GUI.

[0151] In the new registration / login screen 79 shown in Figure 10A, the name "Usage History Inquiry Service" is used, focusing on the usage history display function, which is one of the functions of this parking management service. Focusing on this function, it is also possible to call this parking management system 1 the "Usage History Inquiry System." In this case, it is also possible to call the parking management device 6 the "Usage History Inquiry Management Device."

[0152] Furthermore, focusing on the function of managing the usage fees for parking lot 4, this parking management system 1 can also be called a facility usage fee management system. In this case, the parking management device 6 can also be called a facility usage fee management device.

[0153] As shown in Figure 10A, the new registration / login screen 79 has a new registration button 80, account input fields 81a and 81b, and a login button 82. When user 2 uses this user inquiry service for the first time, they select the new registration button 80 and perform the member registration operation. For example, a GUI for member registration is displayed, and user information 74 as shown in Figure 7A is entered.

[0154] For user 2, who is already a member, login information is entered into account input fields 81a and 81b, and login is performed. Specifically, the ID (member number in this embodiment) is entered into account input field 81a, and the password is entered into account input field 81b. After entering the login information, if the login button 82 is selected, login is performed. If the checkbox for automatic login next time is checked, login will be performed automatically from the next time onward.

[0155] Figure 10B shows the usage history display screen 83, which is displayed as a user GUI. The usage history display screen 83 consists of a menu switching unit 84 and a usage history display unit 85.

[0156] The menu switching section 84 is located in the header of the usage history display screen 83 and allows switching between the displays of "Usage History," "My Page," and "Digital Tickets." User 2 can switch between the displays by selecting the respective text for "Usage History," "My Page," and "Digital Tickets."

[0157] The usage history display screen 83 is the screen displayed when "Usage History" is selected, and the usage history display section 85 is displayed below the menu switching section 84. A mail icon and a logout button are displayed above the menu switching section 84. The mail icon is displayed when an email is received at the email address registered in the user information 74. The logout button is selected when user 2 logs out.

[0158] The usage history display unit 85 displays the usage period selection unit 86 and the history information display units 87a to 87c. The usage period selection unit 86 is used to specify the period of history information to be displayed in the usage history display unit 85. For example, it is possible to specify periods such as "All," "March," or "June to October."

[0159] Each of the history information display units 87a to 87c displays history information of when user 2 has used parking lot 4 in the past. In the example shown in Figure 10B, information regarding the use of parking lot 4, for which payment was made on "2024 / 07 / 15" at "08:24", is displayed in the history information display unit 87a. Information regarding the use of parking lot 4, for which payment was made on "2024 / 07 / 12" at "12:34", is displayed in the history information display unit 87b.

[0160] Furthermore, information regarding the use of parking lot 4, when a settlement was made once at 21:48 on 2024 / 07 / 08, and then the cancellation process was executed at 10:20 on 2024 / 07 / 10, resulting in a refund of 1500 yen, is displayed on the history information display unit 87c.

[0161] User 2 can view more detailed history information by selecting each of the history information display units 87a to 87c. The information displayed in the history information display units 87a to 87c, and the detailed information displayed when the history information display units 87a to 87c are selected, are obtained based on the history information 77 shown in Figure 7D.

[0162] For example, the information stored in the history information 77, such as "settlement fee," may be displayed as is, or various information stored in other databases linked to the information stored in the history information 77 may be displayed as usage history. This makes it possible to display various information about when user 2 has used parking lot 4 in the past.

[0163] For example, the entry and exit history of vehicle 3, which has used ETC automatic payment, and the history of other services are displayed for each date. User 2 can view all the information from the past to the present for the period selected in the usage period selection section 86, one by one, by scrolling the screen.

[0164] For example, while cashless ETC automatic payment improves convenience for user 2, there may be concerns about users losing track of usage fees and developing a poor sense of money. By presenting a usage history display screen 83, as illustrated in Figure 10B, user 2 can check their usage history at any time, which is extremely useful.

[0165] Furthermore, user 2 can manage each piece of history information together by selecting the appropriate checkboxes displayed in each of the history information display sections 87a to 87c. For example, it is possible to display the selected history information again in a list, create receipts all at once, or print them all at once. In addition, "Select All" and "Deselect All" buttons are provided for inputting the checkboxes. This improves the usability for user 2.

[0166] Figure 10C shows the current usage information screen 89, which is displayed as a user GUI. As shown in Figure 10B, it is also possible to configure the current usage information display unit 90 at the bottom of the menu switching unit 84 when "Usage History" is selected in the menu switching unit 84. Any operation may be used to display the current usage information display unit 90, such as selecting a predetermined button.

[0167] The current usage information display unit 90 displays usage information for the current parking lot 4 (facility), corresponding to the case where vehicle 3 is entering the parking lot 4 (facility). In this embodiment, the following are displayed: "Parking lot name," "Entry date and time," "Parking time," "Parking fee," "Discount fee," and "Usage fee."

[0168] User 2 can check their current usage information and understand when they should exit the parking lot by, how much more they need to spend to qualify for a discount, and so on. Of course, information such as "You need to spend X more yen" to make the parking fee free could also be displayed. By visualizing information about current usage fees and discounts in this way, it is possible to improve the convenience for User 2.

[0169] Although not shown in the diagram, when "My Page" is selected in the menu switching section 84, a user information screen is displayed at the bottom of the menu switching section 84, showing a GUI that allows users to view and change already registered user information and payment methods.

[0170] Figure 10D shows the digital ticket display screen 91, which is displayed as a user GUI. The digital ticket display screen 91 is the screen displayed when "Digital Ticket" is selected in the menu switching unit 84, and the digital ticket display unit 92 is displayed at the bottom of the menu switching unit 84.

[0171] The digital ticket display unit 92 displays a digital ticket 93 and a discount code ticket reading button 94. The digital ticket 93 can also be called a digital parking ticket, and in this embodiment, it displays information such as "entry time," "entry gate," "vehicle number," "vehicle type," "vehicle name," and "ETC normal."

[0172] The digital ticket 93 also displays a first code image 95 generated by the code image generation unit 70. The first code image 95 stores the user identification information, which is the "membership number".

[0173] In this embodiment, a QR code that can be read relatively widely by store terminals 10, pre-payment devices 14, etc., is used as the first code image 95. Of course, the configuration of the first code image 95 is not limited in the application of the present invention. Any configuration can be used as the first code image 95, such as a one-dimensional code, a stacked two-dimensional code, a matrix two-dimensional code, etc.

[0174] Of course, if the reading functions of the store terminal 10 and the pre-payment device 14 are improved, the configuration of the first code image 95, which is suitable for the present invention, will also change. For example, color codes such as Chameleon Code (registered trademark) are also considered to be fully usable.

[0175] In this embodiment, the digital ticket display unit 92 displays text indicating that prepayment is possible by holding the first code image 95 over the prepayment device 14. The digital ticket display unit 92 also displays text prompting the user to read the discount code ticket.

[0176] Figure 12 shows an example of a discount code voucher. The discount code voucher 97 is issued by a discount code voucher issuing device 21 connected to the store terminal 10. In this embodiment, the discount code voucher 97 displays "contact information (telephone number)", "discount code voucher number", "purchase date and time", "total purchase amount", and "discount amount".

[0177] Furthermore, a second code image 98 is displayed on the discount code voucher 97. The second code image 98 stores usage information related to the user 2's use of store 9 (another facility). In this embodiment, the discount information that arises from the use of store 9, i.e., the discount information 76 shown in Figure 7C, is stored in the second code image 98 as usage information.

[0178] In this embodiment, the second code image 98 is a QR code, similar to the first code image 95. Of course, other types of code images may be used.

[0179] When user 2 reads the second code image 98 of the discount code voucher 97, they select the discount code voucher reading button 94 displayed on the digital voucher display screen 91 in Figure 10D. This activates the code image reading function (camera) of the mobile terminal 5, and the code image reading screen is displayed.

[0180] Figure 11 shows the code image reading screen 100, which is displayed as a user GUI. The code image reading screen 100 displays a live camera image 101 captured by the camera of the mobile device 5. The code image reading screen 100 also displays text prompting the user to read the second code image 98 of the discount code voucher 97, text indicating that it can be used in conjunction with digital vouchers, and a link to instructions on how to use it.

[0181] User 2 operates the mobile terminal 5 so that the second code image 98 is included in the live camera image 101. As a result, the second code image 98 is automatically captured, and the usage information contained in the second code image 98 can be read. When User 2 selects the back button 102, the screen returns to the digital ticket display screen 91 shown in Figure 10D.

[0182] [Examples of using code images] Figure 13 is a schematic diagram illustrating an example of code image usage. As shown in Figure 13A, user 2, a member, makes a purchase at store 9, which is affiliated with parking lot 4. For example, when settling the usage fee at store 9, user 2 displays the digital ticket display screen 91 shown in Figure 10D. Then, the code image reader 20 connected to the store terminal 10 reads the first code image 95 on the digital ticket display screen 91.

[0183] The store terminal 10 reads the "membership number," which is user identification information, from the first code image 95. The store terminal 10 then associates the read "membership number" with the usage information regarding user 2's use of store 9 (another facility) and transmits it to the parking management device 6 as payment information.

[0184] In this embodiment, the read "member number" is associated with the discount information that arises from the use of store 9, i.e., the discount information 76 shown in Figure 7C, and transmitted to the parking management device 6 as payment information. The transmitted discount information 76 is stored in the discount information DB and also transmitted to the payment processing unit 72 as appropriate (including cases where the payment processing unit 72 reads it as appropriate).

[0185] The settlement processing unit 72 calculates the usage fee for user 2's use of parking lot 4 (facility) based on the date and time of entry of vehicle 3 into parking lot 4 (facility) and the settlement information. This makes it possible to calculate a usage fee for user 2, who is a member, that reflects the discount information 76 included in the settlement information.

[0186] As shown in Figure 1, in store 9b, there may be cases where a member user 2 makes a purchase at store 9b where only the discount code issuing device 21 is installed. In that case, after the purchase is settled, the discount code voucher 97 issued by the discount code issuing device 21 is read, as shown in Figure 13B.

[0187] User 2 displays the code image reading screen 100 shown in Figure 11 and reads the second code image 98 displayed on the discount code ticket 97. The mobile terminal 5 transmits the usage information read from the second code image 98, i.e., the discount information 76 shown in Figure 7C, along with user 2's information (e.g., "membership number") to the parking management device 6. The transmitted discount information 76 is stored in the discount information DB and also transmitted to the settlement processing unit 72 as appropriate (including cases where the settlement processing unit 72 reads it as appropriate).

[0188] The settlement processing unit 72 calculates the usage fee for user 2's use of the parking lot 4 (facility) based on the usage information (discount information 76) read from the second code image 98 by the mobile terminal 5. This makes it possible to calculate the usage fee that reflects the discount information 76.

[0189] In addition, in stores 9A, as shown in Figure 1, where both a code image reader 20 and a discount code issuing device 21 are installed, it is possible to freely choose between reading the first code image 95 with the code image reader 20 and reading the second code image 98 displayed on the discount code ticket 97. In other words, this parking management system 1 makes it possible to read both code images simultaneously.

[0190] Thus, with this parking management system 1, even a store terminal 10 that is not equipped with a code image reader 20 can issue a discount code ticket 97, making it possible to calculate the parking fee for the parking lot 4 while reflecting the discount according to the user's purchases. For example, even a store 9 that only has a store terminal 10 that is not connected to the network 18 can calculate the usage fee that reflects the discount by installing a discount code issuing device 21.

[0191] As shown in Figure 13C, user 2, who will become a member, can make a prepayment using the first code image 95. User 2 displays the digital ticket display screen 91 shown in Figure 10D and has the code image reader 56 of the prepayment device 14 read the first code image 95.

[0192] The pre-payment device 14 performs an inquiry regarding the usage fee for parking lot 4. Specifically, the pre-payment device 14 reads the user identification information, the "member number," from the first code image 95 and transmits the read "member number" to the payment processing unit 72 of the parking management device 6.

[0193] The settlement processing unit 72 calculates the usage fee for user 2's use of parking lot 4 (facility) based on the received "membership number" and transmits it to the pre-payment device 14. If a discount is available at the affiliated store 9 based on the purchase, the usage fee reflecting the discount is calculated and transmitted to the pre-payment device 14. The pre-payment device 14 displays the usage fee for parking lot 4 to user 2, and user 2 makes the pre-payment.

[0194] Furthermore, during prepayment, it is also possible to have the prepayment device 14 read the second code image 98 of the discount code ticket 97. The prepayment device 14 then transmits the usage information (discount information 76) stored in the second code image 98 to the parking management device 6. The payment processing unit 72 of the parking management device 6 calculates the parking fee based on the received discount information 76.

[0195] By adopting this configuration, it is possible to calculate the usage fee that reflects the discount even if user 2 does not use the mobile device 5. Furthermore, even for non-member user 2 who has been issued a parking ticket, it is possible to calculate the usage fee that reflects the discount by having the pre-payment device 14 read the second code image 98 of the discount code ticket 97 during the pre-payment process.

[0196] [Examples of variations in the user GUI] Figure 14 shows examples of variations in the user GUI. In the example shown in Figure 14A, the selection of "digital ticket" is restricted in the menu switching unit 84. That is, user 2 cannot display the digital ticket display screen 91 shown in Figure 10D.

[0197] Thus, in this parking management system 1, it is possible to set conditions for displaying the first code image 95 in the user GUI. When the conditions are met, the first code image 95 is displayed. In other words, the GUI generation unit 71 can be configured to display the first code image 95 in the user GUI when certain conditions relating to user 2 are met.

[0198] For example, it is possible to set the fact that vehicle 3 is entering parking lot 4 as a predetermined condition for user 2. In this case, DB 19 is stored with information indicating that vehicle 3 is entering parking lot 4 (facility). For example, member vehicle information 75 stored in the member vehicle database shown in Figure 7B can be used as information indicating that vehicle 3 is entering parking lot 4 (facility).

[0199] The GUI generation unit 71 accesses the member vehicle database shown in Figure 7B and displays the first code image 95 on the user GUI when vehicle 3 is entering parking lot 4. This prevents members who are not using parking lot 4 from intentionally or negligently (e.g., out of habit) presenting and having the first code image 95 scanned when shopping at store 9.

[0200] The conditions for displaying the first code image 95 on the user GUI are not limited, and any conditions can be set. For example, it is possible to set a condition that the first code image 95 will not be displayed if the location information of the mobile device 5 deviates from the area where the discount-eligible facility or related facilities / stores are located.

[0201] Furthermore, if the application of a discount varies depending on the day of the week (weekday or holiday, etc.) or time of day, it is possible to set conditions such as displaying the first code image 95 only on the days and times when the discount applies.

[0202] Thus, this parking management system 1 makes it possible to visualize whether the first code image 95, which reflects discount information, is available or unavailable, thereby preventing the misuse of the first code image 95 and the acquisition of inappropriate discount information. Furthermore, for users 2, it becomes very easy and intuitive to understand when the first code image 95 can be used and when it cannot, resulting in high convenience.

[0203] Figure 14B shows examples of other variations of the user GUI. This parking management system 1 can accommodate multiple uses of parking lot 4 (facility). Multiple uses of parking lot 4 means that if payment is made at the time of the first use (from entry to exit), it is possible to use parking lot 4 a predetermined number of times within a predetermined period without incurring a predetermined usage fee.

[0204] For example, in a configuration where multiple uses are permitted per day, as long as it is within the same day (from 0:00 to 24:00, or within the operating hours of the same day), after the initial payment, the vehicle 3 can enter and exit parking lot 4 a predetermined number of times without incurring additional usage fees.

[0205] In the example shown in Figure 14B, the multiple usage information display unit 104 is displayed below the menu switching unit 84. The multiple usage information display unit 104 displays information related to multiple uses. In this embodiment, the "parking lot name," "(first) payment date and time," and "remaining number of available uses" are displayed.

[0206] In this embodiment, the GUI generation unit 71 displays the number of times a vehicle 3 can enter the parking lot 4 (facility) without incurring any charges on the user GUI.

[0207] By checking the multiple usage information display unit 104, user 2 can easily and intuitively understand how many more times they can use parking lot 4, thus providing high convenience. In the example shown in Figure 14B, it is displayed that parking lot 4 can be used 2 more times, in which case a shopping discount is not required, and therefore the "digital ticket" option is unavailable (the display of the first code image 95 is restricted).

[0208] The multiple-use information display unit 104 may display information about a predetermined period during which multiple uses are permitted. For example, one form of multiple use could be that parking lot 4 can be used any number of times within a predetermined period. In this case, the multiple-use information display unit 104 may display information such as the date and time remaining until the predetermined period ends (e.g., 1 day remaining, 1 hour 30 minutes remaining).

[0209] Multiple uses of parking lot 4 can be achieved by user 2 through an application, for example, via the user GUI. If user 2's application for multiple uses is accepted, information regarding the multiple use will be displayed on user 2's user GUI, as shown in Figure 14B. Of course, the methods for applying for multiple uses are not limited.

[0210] Furthermore, the configurations of the user GUI screens shown in Figures 10, 11, and 14 are merely examples, and various other configurations can be adopted. For example, any GUI can be generated and displayed that allows registered user 2 to check various information such as parking lot 4 usage, discount services, other services, and service application conditions. This can improve the convenience for user 2.

[0211] In the parking management system 1 according to this embodiment, user history information 77 is managed based on ETC information acquired from roadside devices (entrance roadside device 16, exit roadside device 17) that communicate wirelessly with the ETC onboard unit. A first code image 95 including the "member number" is also generated. Then, a user GUI for displaying the history information 77 and the first code image 95 is generated and transmitted to user 2's mobile terminal 5. This makes it possible to improve the convenience of user 2 using the parking lot 4.

[0212] For example, in the parking fee management system described in Patent Document 1, user 2 is required to select their vehicle 3. In this case, if the wrong vehicle 3 is selected, it is difficult to notice the mistake after the discounted fee has been applied, and it cannot be easily resolved, potentially leading to disputes among users.

[0213] In contrast, the present parking management system 1 eliminates the need for vehicle selection operations, thus preventing the problems described above. By applying this invention, it is possible to improve the convenience of users 2 while allowing cashless payment of usage fees, which reflect discount information according to the usage status of the parking lot 4 (facility), via the ETC system.

[0214] One of the advantages of the present invention, as already mentioned, is that if ETC information such as the ETC card number is successfully obtained from the ETC onboard unit installed in the user's vehicle 3, the vehicle 3 can be exited hands-free via ETC automatic payment.

[0215] In this case, it is possible to reduce the usage fee by reflecting shopping discounts at partner stores 9. One way to do this is to display the digital voucher 93 on the user's mobile device 5 and have the first code image 95 read by the code image reader 20 of the store terminal 10.

[0216] In addition to this method, a discount code voucher 97 is issued from the discount code issuing device 21, and the user 2 has their mobile terminal 5 read the second code image 98. This method also makes it possible to reduce the usage fee by reflecting shopping discounts at affiliated stores 9.

[0217] For example, individual shops and small facilities may find it difficult to prepare store terminals 10 connected to the network 18 or code image readers 20. On the other hand, large commercial facilities, especially those with large-scale POS systems, may promote the use of digital tickets 93 and often not support discount code tickets 97.

[0218] In this parking management system 1, for individual shops and small facilities where the use of digital tickets 93 is difficult, a discount code issuing device 21 that issues discount code tickets 97 can be installed to easily apply shopping discounts. Furthermore, for large commercial facilities that do not support discount code tickets 97, shopping discounts can be easily applied by using digital tickets 93.

[0219] Thus, this parking management system 1 can flexibly adapt to the form of stores 9, and can be built as an extremely versatile and useful system.

[0220] Furthermore, with this parking management system 1, even if the acquisition of ETC information from the ETC onboard unit is successful, it is possible to select a payment method other than automatic ETC payment. For example, by using the pre-payment device 14 to pay in cash, or by combining point payment processing, debit card payment, or electronic money payment, it is possible to exit parking lot 4 with payment already made without automatic ETC payment.

[0221] For example, it's possible to implement flexible measures that allow user 2 to enjoy various benefits, such as accumulating points based on the number of uses, or not automatically paying for ETC during cashback campaigns for code payments.

[0222] Since ETC onboard units can be installed and removed independently, it is possible to receive an ETC onboard unit from another vehicle (Vehicle 3) and install it in your own vehicle (Vehicle 3). Also, when you replace your vehicle (Vehicle 3), you will almost always replace the ETC onboard unit as well.

[0223] Therefore, when entering and exiting parking lots 4 etc. with an ETC vehicle, if only the WCN of the ETC onboard unit is used, if the ETC onboard unit is changed, it will be necessary to re-register the ETC information (WCN) in user information 74 shown in Figure 7A, which may make the procedure complicated.

[0224] To address this point, in the above embodiment, the ETC card number is used as the ETC information to be registered as user information 74. This eliminates the need to re-register ETC information even if the ETC onboard unit is changed, and makes it possible to use the parking management service based on the same ETC card number. Of course, the application of the present invention does not exclude the form in which only the WCN is used as ETC information.

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

[0226] The first code image 95 displayed on the digital ticket 93 may store not only user identification information but also other information (data). For example, the first code image 95 may store information indicating that vehicle 3 is entering parking lot 4 (facility). For example, information regarding the date and time when vehicle 3 entered parking lot 4 (facility) can be used. This makes it possible to prevent, for example, taking a picture (capture) of a past first code image 95 and using that captured image of the first code image 95 in the present.

[0227] Furthermore, the first code image 95 may be updated if there is a change in the payment status at parking lot 4 (facility) or the shopping status at store 9 (other facility). For example, if the initial first code image 95 stores unpaid information, and user 2 makes a prepayment, a new first code image 95 storing paid information may be generated and sent to the mobile terminal 5.

[0228] Alternatively, if user 2 makes a new purchase and a new discount becomes available, a new first code image 95 containing information about the new discount may be generated and transmitted to the mobile terminal 5.

[0229] In the usage history display screen 83 shown in Figure 10B, not only the usage history for parking lot 4 may be displayed, but also the usage history of other parking lots 4 where ETC payment is made, and the shopping history at affiliated stores 9. For example, when user 2 selects the parking lots 4 and stores 9 for which the usage history is to be displayed, the usage history for the selected parking lots 4 and stores 9 will be displayed. Of course, it may also be possible to display the usage history of multiple parking lots 4 together, or to display the usage history of parking lots 4 and stores 9 together.

[0230] All or part of the information stored in DB19 shown in Figure 1 may be stored in the storage unit (memory, HDD, etc.) of the prepayment device 14 and synchronized with each other. This allows for backup in the event that the network 18 becomes inoperable. For example, by storing ETC information, vehicle presence information, prepayment information, etc., in the storage unit of the prepayment device 14, it becomes possible to handle vehicle entry and exit within the parking lot 4 even if the network 18 becomes inoperable.

[0231] In the current usage information screen 89 shown in Figure 10C, etc., information such as whether a shopping discount is applicable, whether the shopping discount amount has reached its limit, whether a shopping discount is not needed for the current parking fee, and whether multiple usage is applied may be displayed in a way that is easily identifiable to User 2. For example, the display may be made easy to understand for User 2 by using bold text or other highlighting, graying out, or an X mark as appropriate. This makes it possible to easily understand, for example, that there is no need to make a purchase or that parking is available for XX minutes, thereby providing a high level of convenience.

[0232] In addition to services that offer discounts on admission fees for purchases, there should also be a service that allows free re-entry within a certain time frame after exiting using a purchase discount. For example, this would be an effective service for bringing in products for repair or picking up items from dry cleaners.

[0233] The facilities that user 2 can use with vehicle 3 are not limited to parking lot 4, and the present invention can be applied to a variety of other facilities. For example, the present invention can be applied to various facilities where an ETC automatic payment system can be installed, such as facilities that have introduced a drive-through format (e.g., fast food restaurants), gas stations, car washes, roadside rest areas, etc. Of course, the term "facility" is a concept that includes any facility that may not be distinguished from so-called stores, such as hospitals and public facilities.

[0234] Furthermore, in this disclosure, the term "vehicle" is not limited to automobiles, but also includes bicycles, motorcycles, tricycles, electric scooters, and the like.

[0235] By applying this invention, it becomes possible to comprehensively manage payment methods for facility usage fees and the reflection of shopping discounts at other facilities partnered with the facility. Furthermore, it becomes possible to improve the convenience of user 2.

[0236] Figure 15 is a block diagram showing an example of the hardware configuration of a computer 110 that can be used as a parking management device 6, etc.

[0237] The computer 110 includes a CPU 111, ROM 112, RAM 113, an input / output interface 115, and a bus 114 connecting these to each other. The input / output interface 115 is connected to a display unit 116, an input unit 117, a storage unit 118, a communication unit 119, and a drive unit 120, among others. The display unit 116 is a display device using, for example, liquid crystal, EL, etc. The input unit 117 is, for example, a keyboard, pointing device, touch panel, or other operating device. If the input unit 117 includes a touch panel, the touch panel may be integrated with the display unit 116. The storage unit 118 is a non-volatile storage device, such as an HDD, flash memory, or other solid-state memory. The drive unit 120 is a device capable of driving a removable recording medium 121, such as an optical recording medium or magnetic recording tape. The communication unit 119 is a modem, router, or other communication device that can connect to a LAN, WAN, etc., and communicates with other devices. The communication unit 119 may use either wired or wireless communication. The communication unit 119 is often used separately from the computer 110. Information processing by the computer 110 having the hardware configuration described above is realized through the cooperation of software stored in the memory unit 118 or ROM 112, etc., and the hardware resources of the computer 110. Specifically, the facility 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 112, etc., into the RAM 113, and then having the CPU 111 control and execute them. The program is installed on the computer 110, for example, via a recording medium 121. Alternatively, the program may be installed on the computer 110 via a global network or the like. In addition, any non-transient storage medium that is readable by a computer may be used.

[0238] Multiple computers connected to each other via a network or the like can collaborate to execute the facility 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 facility management method and program according to the present invention can be executed not only in a computer system composed 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.

[0239] The execution of the facility management method and program according to the present invention by a computer system includes both cases in which, for example, the acquisition of user-related information, the management of historical information, the generation of first and second code images, the generation of a user GUI, and settlement processing are performed by a single computer, and cases in which 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.

[0240] The various terminals and devices such as the parking management system, parking management device, ticketing device, exit payment device, pre-payment device, entrance roadside device, exit roadside device, etc., the configuration of the user GUI, the operation by the parking management device, ticketing device, exit payment device, pre-payment device, entrance roadside device, exit roadside device, etc., and the various 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.

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

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

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

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

[0245] As described above, the technology of the present invention is a technology that can easily incorporate shopping discount services from surrounding facilities in a parking lot where ETC vehicles can enter, exit, and pay nonstop and hands-free. [Explanation of Symbols]

[0246] 1…Parking management system 2…User 3…Vehicles 4…Parking 5… Mobile devices 6…Parking management system 8…Payment institutions 9 stores 10…Store terminal 13…Ticket issuing device 14… Pre-payment device 15...Exit payment device 16…Entrance roadside equipment 17…Exit roadside device 18…Network 20… Code image reader 21…Discount code issuing device 23…Entrance Gate 24…Exit Gate 74…User information 75…Vehicle information for members 76…Discount Information 77…History information 79... Login screen 83...Usage history display screen 87a~87c...History information display section 89…Current usage information screen 91... Digital ticket display screen 93…Digital ticket 95...First code image 97…Discount code coupon 98...Second code image 100... Code image reading screen 104…Multiple User Information Display Section 110... Computer

Claims

1. A facility management system for managing facilities that users can access using their vehicles, An acquisition unit that acquires user-related information concerning at least one of the user and the vehicle from a facility-side wireless device that performs wireless communication with a vehicle-side wireless device installed on the vehicle when the vehicle enters the facility, A management unit manages historical information regarding the user's use of the facility based on the user-related information, A code image generation unit generates a first code image that includes user identification information to identify the user, A GUI generation unit generates a user GUI (Graphical User Interface) for displaying the history information and the first code image, and transmits it to the user's terminal. A facility management system equipped with the following features.

2. A facility management system according to claim 1, further, The system includes a settlement processing unit that performs settlement processing for the user's use of the facility. Facility management system.

3. A facility management system according to claim 2, further, The facility terminal is located in another facility accessible to the user, reads the user identification information from the first code image, associates the read user identification information with the user's usage information for the other facility, and transmits it as settlement information. Facility management system.

4. A facility management system according to claim 3, The facility terminal transmits the settlement information to the settlement processing unit. The settlement processing unit calculates the usage fee for the user's use of the facility based on the date and time of entry into the facility and the settlement information. Facility management system.

5. A facility management system according to claim 2, further, The system is equipped with a prepayment device that accepts prepayment operations from the user, The pre-payment device reads the user identification information from the first code image and transmits the read user identification information to the payment processing unit. The settlement processing unit calculates the usage fee for the user's use of the facility based on the user identification information and transmits it to the pre-payment device. Facility management system.

6. A facility management system according to claim 2, further, The system includes an output terminal located in another facility accessible to the user, which outputs a second code image containing usage information regarding the user's use of the other facility, The settlement processing unit calculates the usage fee for the user's use of the facility based on the usage information read from the second code image by the user terminal. Facility management system.

7. A facility management system according to claim 1, The aforementioned history information includes settlement fees corresponding to the use of the aforementioned facilities. Facility management system.

8. A facility management system according to claim 1, The aforementioned history information includes information regarding the current use of the facility, corresponding to the case when the vehicle is entering the facility. Facility management system.

9. A facility management system according to claim 1, The GUI generation unit will display the first code image on the user GUI when predetermined conditions relating to the user are met. Facility management system.

10. A facility management system according to claim 9, further, The vehicle is equipped with a storage unit that stores information indicating that the vehicle is entering the facility. The GUI generation unit causes the first code image to be displayed on the user GUI when the vehicle is entering the facility. Facility management system.

11. A facility management system according to claim 1, The GUI generation unit displays on the user GUI the number of times the vehicle can enter the facility without incurring any charges. Facility management system.

12. A facility management system according to claim 1, further, The facility is equipped with the aforementioned wireless device. Facility management system.

13. A facility management system according to claim 1, The aforementioned vehicle-side wireless device is an ETC (Electronic Toll Collection) on-board unit. The aforementioned facility-side wireless device is an ETC roadside device. Facility management system.

14. There is a facility management device for managing facilities that users can use with their vehicles, An acquisition unit that acquires user-related information concerning at least one of the user and the vehicle from a facility-side wireless device that performs wireless communication with a vehicle-side wireless device installed on the vehicle when the vehicle enters the facility, A management unit manages historical information regarding the user's use of the facility based on the user-related information, A code image generation unit generates a first code image that includes user identification information to identify the user, A GUI generation unit generates a user GUI (Graphical User Interface) for displaying the history information and the first code image, and transmits it to the user's terminal. A facility management device equipped with the following features.

15. A facility management method performed by a computer system to manage facilities that can be used by users with vehicles, When the vehicle enters the facility, the facility-side wireless device, which communicates wirelessly with the vehicle-side wireless device installed in the vehicle, acquires user-related information concerning at least one of the user and the vehicle. Based on the user-related information, the system manages the user's history information regarding their use of the facility. A first code image is generated that includes user identification information to identify the user. A user GUI (Graphical User Interface) for displaying the history information and the first code image is generated and transmitted to the user's terminal. Facility management methods.

16. A program that causes a computer system to execute a facility management method for managing facilities that users can use with their vehicles, The aforementioned facility management method is, When the vehicle enters the facility, the facility-side wireless device, which communicates wirelessly with the vehicle-side wireless device installed in the vehicle, acquires user-related information concerning at least one of the user and the vehicle. Based on the user-related information, the system manages the user's history information regarding their use of the facility. A first code image is generated that includes user identification information to identify the user. A user GUI (Graphical User Interface) for displaying the history information and the first code image is generated and transmitted to the user's terminal. program.

Images