Parking lot management system, parking lot management method, and program

Abstract

To provide a parking lot management system, a parking lot management method, and a program that enable the reduction of operational costs for remotely managing parking lots.SOLUTION: A parking lot management system manages a parking lot via a parking lot management device. A ticket issuing device issues to a user of the parking lot a parking ticket displaying a code image storing parking ticket information containing the entry date and time of a vehicle of the user and parking lot information used for managing the parking lot by the parking lot management device. When the code image displayed on the parking ticket is read by a settlement device, the parking fee is settled based on the entry date and time stored in the code image. Furthermore, the parking management system is configured such that when the code image is read by a portable terminal equipped with the function to read the code image of the user, the parking ticket information stored in the code image is transmitted from the portable terminal to the parking lot management device.SELECTED DRAWING: Figure 9

Description

[Technical Field]

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

[0002] In the parking lot payment system described in Patent Document 1, a two-dimensional code representing the attributes of the parking lot is displayed as an attribute sign on the ticket issuing machine and payment machine at the entrance and exit gates of the parking lot. When entering and exiting, users take a photo of the attribute sign using their smartphone. The photographed attribute information is sent to the server of a payment management company, which then controls the opening and closing of the gates and settles the parking fee when entering and exiting.

[0003] In the parking lot settlement system described in Patent Document 2, when settlement is performed at a settlement device located at the exit, a payment request is output from the settlement device to the user's mobile terminal (for example, a two-dimensional code is displayed or near-field wireless communication is performed). The user's mobile terminal, which has acquired the payment request, transmits the payment request to the settlement device via a communication line. The payment device, which has acquired the payment request, executes payment processing and transmits a payment completion notification to the user's mobile terminal via the communication line. The payment completion notification is output from the mobile terminal to the settlement device, and the exit gate opens. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2019-40502 [Patent Document 2] Japanese Patent Application Publication No. 2018-116338 Summary of the Invention [Problem to be solved by the invention]

[0005] There is a demand for technology that can reduce operating costs in systems that remotely manage parking lots.

[0006] In view of the above circumstances, an object of the present invention is to provide a parking lot management system, a parking lot management method, and a program that enable operational costs for remotely managing parking lots to be reduced. [Means for solving the problem]

[0007] In order to achieve the above object, a parking lot management system according to one embodiment of the present invention includes a parking lot management device, a ticket issuing device, and a payment settlement device. The parking lot management device manages a parking lot. The ticket issuing device issues a parking ticket to a user of the parking lot, displaying a code image that stores parking ticket information including the date and time of entry of the user's vehicle and parking lot information about the parking lot that is used for management of the parking lot by the parking lot management device. The settlement device has a function of reading the code image, and when the code image displayed on the parking ticket is read, the settlement device performs settlement of the parking fee based on the entry date and time stored in the code image. The parking lot management system is configured so that when the code image is read by a mobile terminal of the user that has the function of reading the code image, the parking ticket information stored in the code image is sent from the mobile terminal to the parking lot management device.

[0008] The parking lot information may include at least one of information regarding the issuance status of the parking ticket, information regarding the sales amount, information regarding change, information regarding pricing, information regarding the status of equipment located in the parking lot, and information regarding invalid parking tickets.

[0009] The parking lot management device may send a management side code image storing the parking ticket information with management information for managing the parking lot added to the mobile terminal that sent the parking ticket information stored in the code image to the parking lot management device.

[0010] When the settlement device reads the management side code image displayed by the mobile terminal, it may perform processing related to the management of the parking lot based on the management information stored in the management side code image.

[0011] The management information may include at least one of information regarding changes to pricing, information regarding changes to settings of devices located in the parking lot, information regarding update programs for devices located in the parking lot, and information regarding facilities affiliated with the parking lot.

[0012] The parking lot information may include information regarding a reading status of the management information stored in the management side code image by the settlement device.

[0013] The parking lot management device may transmit to the mobile terminal the management side code image storing the parking ticket information to which information regarding the payment status of the parking fee by the user has been added.

[0014] When the settlement device reads the management side code image displayed by the mobile terminal, it may perform settlement of the parking fee based on information regarding the settlement status stored in the management side code image.

[0015] The parking lot management device may perform settlement of the parking fee based on a settlement request input via the mobile terminal, and may send the management side code image to the mobile terminal, which stores the parking ticket information with information added that the settlement of the parking fee has been completed.

[0016] The parking lot management system may further include a store terminal having a function of reading the code image of a facility affiliated with the parking lot. In this case, when the store terminal reads the code image or the management-side code image, it may associate shopping information about the user's purchase with the parking ticket information stored in the code image or the management-side code image and transmit the associated shopping information to the parking lot management device. Furthermore, the parking lot management device may transmit the management-side code image storing the parking ticket information with the shopping information added to it to the mobile terminal.

[0017] When the settlement device reads the management side code image displayed by the mobile terminal, it may perform settlement of the parking fee based on the shopping information stored in the management side code image.

[0018] The ticket issuing device may divide the parking lot information into multiple divided parking lot information pieces, generate multiple code images each storing one of the multiple divided parking lot information pieces, and display them on each of the multiple parking tickets.

[0019] The settlement device may generate new parking lot information when the parking lot management device has completed receiving each of the plurality of divided parking lot information.

[0020] The parking lot management device may divide the management information into multiple divided management information, generate multiple management side code images storing each of the multiple divided management information, and transmit them to each of multiple mobile terminals.

[0021] The parking lot management device may generate new management information when the settlement device has completed reading each of the plurality of pieces of divided management information.

[0022] A parking lot management method according to one embodiment of the present invention includes a ticket issuing device issuing a parking ticket to a user of a parking lot, the parking ticket displaying a code image storing parking ticket information including the date and time of entry of the user's vehicle and parking lot information regarding the parking lot used for management of the parking lot by a parking lot management device that manages the parking lot. When the code image displayed on the parking ticket is read by a settlement device having the function of reading the code image, the parking fee is settled based on the entry date and time stored in the code image. When the code image is read by the user's mobile terminal having the function of reading the code image, the parking ticket information stored in the code image is sent to the parking lot management device.

[0023] A program according to one aspect of the present invention is a program that causes a management device that manages a parking lot, a ticket issuing device, a payment device, and a mobile terminal of a user of the parking lot to execute the parking lot management method. [Effects of the Invention]

[0024] As described above, according to the present invention, it is possible to reduce the operational costs for remotely managing a parking lot. [Brief explanation of the drawings]

[0025] [Figure 1] 1 is a schematic diagram showing an example of the configuration of a parking lot management system according to an embodiment of the present invention; [Figure 2] FIG. 1 is a schematic diagram showing a specific example of the configuration of a parking lot. [Figure 3] FIG. 2 is a block diagram showing an example of the hardware configuration of a ticket issuing device and a payment adjustment device. [Figure 4] FIG. 2 is a block diagram showing an example of the functional configuration of a ticket issuing device. [Figure 5] FIG. 2 is a block diagram showing an example of the functional configuration of the settlement device. [Figure 6] FIG. 2 is a block diagram showing an example of the hardware configuration of a mobile terminal of a parking lot user. [Figure 7]FIG. 2 is a block diagram showing an example of the functional configuration of a mobile terminal. [Figure 8] 2 is a block diagram showing an example of the functional configuration of the parking lot management device. FIG. [Figure 9] 1 is a schematic diagram showing the basic flow of a parking lot management method according to the present parking lot management system. [Figure 10] 10 is a flowchart showing an example of the operation of the ticket issuing device. [Figure 11] FIG. 2 is a schematic diagram showing an example of parking ticket information in the present embodiment. [Figure 12] 10 is a schematic diagram for explaining divided parking lot information and divided management information. FIG. [Figure 13] 2 is a schematic diagram showing an example of the structure of a parking ticket according to the present embodiment. FIG. [Figure 14] 10 is an example of a checkout page displayed on a user's mobile terminal. [Figure 15] 10 is a flowchart showing an example of the operation of the settlement device. [Figure 16] 10 is a flowchart showing an example of processing related to the handling of "parking lot information" and "management information" by the parking lot management device. [Figure 17] 1 is a block diagram showing an example of the hardware configuration of a computer 110 that can be used as a parking lot management device or the like. DETAILED DESCRIPTION OF THE INVENTION

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

[0027] [Parking lot management system] 1 is a schematic diagram showing an example of the configuration of a parking lot management system according to one embodiment of the present invention. The parking lot management system 1 includes a mobile terminal 2, a parking lot management device 3, a management institution terminal 4, a payment server device (not shown) owned by a payment institution 5, a store terminal 7 located in a store 6, and an owner terminal 8. The parking lot management system 1 also includes a ticket issuing device 10 and a payment settlement device 11 located in a parking lot 9.

[0028] 1, the mobile terminal 2, the parking lot management device 3, the management institution terminal 4, the payment server device of the payment institution 5, the store terminal 7, and the owner terminal 8 are interconnected via a network 12 so as to be able to communicate with each other. The network 12 is constructed, for example, by the Internet or a wide area communication network. Alternatively, any WAN (Wide Area Network) or LAN (Local Area Network) may be used, and the protocol for constructing the network 12 is not limited.

[0029] The ticket issuing device 10 and the settlement device 11 installed in the parking lot 9 are not equipped with a function for connecting to the network 12. Therefore, the ticket issuing device 10 and the settlement device 11 do not perform communication via the network 12.

[0030] The mobile terminal 2 is a terminal used by a user of the parking lot 9. A smartphone is typically used as the mobile terminal 2, but the mobile terminal 2 is not limited to this and various PDAs (Personal Digital Assistants) such as tablet terminals may also be used. The mobile terminal 2 has a function of reading a code image according to the present invention, which will be described later.

[0031] The owner terminal 8 is a terminal used by the owner of the parking lot 9. As the owner terminal 8, any computer such as a smartphone, a tablet terminal, or various types of PC (Personal Computer) may be used.

[0032] The parking lot management device 3 is a device that manages the parking lot 9, and is capable of providing the parking lot management service according to this embodiment as a Web service.

[0033] The parking lot management device 3 has hardware necessary for a computer, such as processors such as a CPU, GPU, and DSP, memories such as a ROM and RAM, and storage devices such as an HDD.

[0034] The parking lot management device 3 also has a communication unit for communicating with other terminals and devices via the network 12. The communication unit may be, for example, a wireless LAN module such as WiFi, or a communication device such as a modem or a router. The parking lot management device 3 may be, for example, any computer such as a PC.

[0035] As shown in Fig. 1, a database (DB) 13 is connected to the parking lot management device 3. DB 13 functions as a storage unit and stores various information related to the parking lot management service. For example, various DBs can be created in DB 13, such as a vehicle presence DB, parking lot DB, store usage DB, shopping information DB, discount DB, exit information DB, user DB, owner information DB, various history DBs, parking ticket information DB, parking lot information DB, and management information DB.

[0036] The various databases are comprehensively managed by the parking lot management device 3, and, for example, perform registration and cancellation of membership for users who use the parking lot management service, registration and storage of owner information for each parking lot 9, and recording and storage of operating income and expenditure information.

[0037] In this embodiment, a web page is generated by the parking lot management device 3. The generated web page is displayed on the screen by web browsers provided in the mobile terminal 2, the parking lot management device 3, the management institution terminal 4, the payment server device owned by the payment institution 5, the store terminal 7, and the owner terminal 8 via the network 12 shown in Fig. 1. For example, a user of the parking lot 9 or the owner of the parking lot 9 can view various web pages and use various web applications by operating the mobile terminal 2 or the owner terminal 8.

[0038] The management organization terminal 4 is used by an operator of a management organization that has been entrusted with the management of the parking lot 9 by the owner of the parking lot 9. As the management organization terminal 4, a PC, a tablet terminal, or the like is used.

[0039] In some cases, the owner of the parking lot 9 may manage the parking lot 9 himself. In this case, a terminal owned by the owner may function as the management agency terminal 4. It is also possible that the management agency entrusted with the management operations may own the parking lot management device 3 and provide the parking lot management service according to this embodiment.

[0040] The settlement institution 5 is, for example, a bank or a credit company, and executes payment (settlement) of parking fees by bank transfer, credit card payment, etc. The parking lot management device 3 executes instructions to settle parking fees to the settlement server device of the settlement institution 5, inquiries about settlement information such as whether the settlement has been completed, etc.

[0041] The store terminal 7 is installed in each store 6 that has a partnership with the parking lot 9 regarding discount services. For example, a partnership regarding discount services may be formed with a nearby commercial facility, but the present invention is not limited to this.

[0042] A POS register having a communication function, for example, is used as the store terminal 7. As shown in Fig. 1, a code image reader 14 is connected to the store terminal 7. The code image reader 14 is configured by an optical reading device with a built-in laser scanner, for example, and has a function of reading a code image according to the present invention, which will be described later.

[0043] Further, for example, the store terminal 7 and the parking lot management device 3 can indirectly (via a POS register server, etc.) share information about discounts on parking fees. The specific configurations and types of the store terminal 7 and the code image reader 14 are not limited.

[0044] In this embodiment, the store 6 affiliated with the parking lot 9 corresponds to one embodiment of a facility affiliated with the parking lot. The present technology can also be applied to any facility that may not be classified as a so-called store, such as a hospital or public facility. The store terminal 7 is a terminal of a facility affiliated with the parking lot.

[0045] Fig. 2 is a schematic diagram showing a specific configuration example of a parking lot 9. The parking lot 9 has an entrance 16 and an exit 17. As shown in Fig. 2, a central island 18 is installed between the entrance 16 and the exit 17. In addition, an entrance island 19 and an exit island 20 are installed on either side of the central island 18.

[0046] The area between the central island 18 and the entrance island 19 is the entrance lane 21 of the parking lot 9. The area between the central island 18 and the exit island 20 is the exit lane 22 of the parking lot 9.

[0047] As shown in Figure 2, the central island 18 has an entrance gate 23, an exit gate 24, a ticket issuing device 10, and a payment settlement device 11. The ticket issuing device 10 issues parking tickets to users of the parking lot 9. The payment settlement device 11 has a function of reading a code image according to the present invention, which will be described later, and is capable of settling parking fees.

[0048] The entrance gate 23, the exit gate 24, the ticket issuing device 10, and the settlement device 11 are connected by on-site wiring 26 installed within the premises 25 of the parking lot 9 (see FIGS. 1 and 3).

[0049] A first entrance loop coil 27 and a second entrance loop coil 28 are buried in the ground of the entrance lane 21. A first exit loop coil 29 and a second exit loop coil 30 are buried in the ground of the exit lane 22.

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

[0051] The interface 35 has an internal communication unit 36, a parking ticket printer 37, a card feeder 38, a display 39, and a speaker 40. The operation of each block is controlled by the CPU 32 which operates according to a program.

[0052] The on-premises communication unit 36 ​​has a communication circuit for communicating with the settlement device 11, and is communicatively connected to the on-premises communication unit 45 of the settlement device 11 via the on-premises wiring 26. The on-premises communication unit 36 ​​is also connected to the entrance gate 23 and the exit gate 24 via the on-premises wiring 26.

[0053] The parking ticket printer 37 prints necessary information on a parking ticket issued to a user who uses the parking lot 9. In this embodiment, the parking ticket printer 37 prints a code image according to the present invention, which will be described later.

[0054] The card feeder 38 issues a parking ticket to the user. The display 39 has an image display function. The speaker 40 has an audio output function. The specific configurations of the card feeder 38, the display 39, and the speaker 40 are not limited, and any configuration may be adopted.

[0055] The settlement device 11 has a CPU 41, a memory 42, and an interface 44 connected to these via a bus 43. The memory 42 is composed of, for example, ROM, RAM, flash memory, etc., and stores various programs, various parking data, etc. Of course, the settlement device 11 may also be equipped with a storage device such as an HDD.

[0056] The interface 44 has an internal communication unit 45, a code image reader 46, a bill and coin management unit 47, a receipt printer 48, a touch panel 49, and a speaker 50. The operation of each block is controlled by a CPU 41 that operates according to a program.

[0057] The on-premises communication unit 45 includes a communication circuit for communicating with the ticket issuing device 10, and is communicatively connected to the on-premises communication unit 36 ​​of the ticket issuing device 10 via the on-premises wiring 26. The on-premises communication unit 45 is also connected to the entrance gate 23 and the exit gate 24 via the on-premises wiring 26.

[0058] The code image reader 46 is configured by, for example, an optical reading device with a built-in laser scanner. The code image reader 46 can read a code image held over the reading port by scanning a laser beam from the reading port to the outside.

[0059] The bill and coin management unit 47 receives bills and coins inserted into the bill insertion slot and coin insertion slot, counts them, calculates the inserted amount, and also counts the change required for settlement and dispenses it into the coin / receipt outlet.

[0060] The receipt printer 48 prints the settlement amount, date and time, etc. on receipt paper and issues a receipt. The issued receipt can be collected from the coin / receipt outlet.

[0061] The touch panel 49 has an image display function and a function of accepting various touch operations from the user. The speaker 50 has an audio output function. The specific configurations of the touch panel 49 and the speaker 50 are not limited, and any configuration may be adopted.

[0062] The settlement device 11 can perform settlement processes including, for example, calculating parking fees, displaying on the touch panel 49 and outputting audio from the speaker 50, counting the coins and bills inserted, calculating whether or not change is due, and paying out change.

[0063] 4 is a block diagram showing an example of the functional configuration of the ticket issuing device 10. The ticket issuing device 10 has a vehicle detection unit 52, a gate control unit 53, an information management unit 54, and a code image generation unit 55. These blocks are configured by the CPU 32 executing a predetermined program, and processing for realizing the parking lot management method according to this embodiment is realized. Note that dedicated hardware such as an IC (integrated circuit) may be used as appropriate to configure each block.

[0064] The vehicle detection unit 52 detects the entry of a vehicle into the entrance lane 21 and the entrance of a vehicle into the premises 25 based on the signals output from the first and second entrance loop coils 27 and 28. Note that any other configuration may be adopted as the configuration for detecting a vehicle entering the entrance lane 21. For example, an optical sensor using infrared rays or the like may be used.

[0065] The gate control unit 53 controls the operation of the entrance gate 23. The information management unit 54 manages various types of information, such as sending information (data), receiving information, writing information to the memory 33 or a storage device, and reading information from the memory 33 or a storage device. The code image generation unit 55 generates a code image according to the present invention, which will be described later.

[0066] 5 is a block diagram showing an example of the functional configuration of the settlement device 11. The settlement device 11 has a vehicle detection unit 57, a gate control unit 58, an information extraction unit 59, a settlement unit 60, an information management unit 61, and an update processing unit 62. These blocks are configured by the CPU 41 executing a predetermined program, and processing for realizing the parking lot management method according to this embodiment is realized.

[0067] The vehicle detection unit 57 detects vehicles entering and exiting the exit lane 22 based on signals output from the first and second exit loop coils 29 and 30. The gate control unit 58 controls the operation of the exit gate 24.

[0068] The information extraction unit 59 controls the reading of the code image by the code image reader 46 and extracts information contained in the code image. The payment unit 60 executes payment of the parking fee.

[0069] The information management unit 61 manages various types of information, such as sending information (data), receiving information, writing information to the memory 42 or a storage device, and reading information from the memory 42 or a storage device.

[0070] In this embodiment, the information management unit 54 of the ticket issuing device 10 and the information management unit 61 of the settlement device 11 operate in conjunction with each other to manage various types of information. For example, only one of the information management unit 54 of the ticket issuing device 10 and the information management unit 61 of the settlement device 11 may be configured, and writing and reading of information to and from the memory 33 of the ticket issuing device 10 and the memory 42 of the settlement device 11 may be performed. Also, a storage device for storing various types of information may be configured in either the ticket issuing device 10 or the settlement device 11, and various types of information may be managed collectively.

[0071] The update processing unit 62 executes processing related to the management of the parking lot 9 based on the management information generated by the parking lot management device 3. The management information will be explained later.

[0072] 6 is a block diagram showing an example of the hardware configuration of the mobile terminal 2 of a user of the parking lot 9. The mobile terminal 2 has a CPU 64, a memory 65, and an interface 67 connected to these via a bus 66. The memory 65 is composed of, for example, a ROM, a RAM, a flash memory, etc., and stores various data.

[0073] Connected to the interface 67 are a touch panel 68, a camera 69, a speaker 70, a microphone 71, a communication unit 72, a short-range wireless communication unit 73, a GPS sensor 74, and an acceleration sensor 75. The operation of each block is controlled by the CPU 64, which operates according to a predetermined program.

[0074] The touch panel 68 has an image display function and a function of accepting various touch operations from the user. The specific configuration of the touch panel 68 is not limited, and any configuration may be adopted.

[0075] The camera 69 is, for example, a digital camera equipped with an image sensor such as a CMOS (Complementary Metal-Oxide Semiconductor) sensor or a CCD (Charge Coupled Device) sensor. Other types of cameras may also be used. In this embodiment, two types of cameras, a front camera and a rear camera, are installed.

[0076] The speaker 70 has a sound output function, and the microphone 71 has a sound collection function. The specific configurations of the speaker 70 and the microphone 71 are not limited, and any configuration may be adopted.

[0077] The communication unit 72 is a communication module for communicating with other terminals or devices such as the parking lot management device 3 via the network 12, and may be, for example, a wireless LAN module such as WiFi or a module compatible with mobile communication systems such as 4G or 5G.

[0078] The short-range wireless communication unit 73 is a module for performing short-range wireless communication with other devices. For example, the short-range wireless communication unit 73 may be provided with a Bluetooth (registered trademark) module, an NFC (Near Field Communication) module, or the like.

[0079] The GPS sensor 74 outputs position information of the main body of the portable terminal 2. The acceleration sensor 75 outputs changes in the angle, movement, and orientation of the main body of the portable terminal 2. The acceleration sensor 75 functions as a motion sensor, and is capable of detecting the state of the user using the portable terminal 2, including the posture, movement, etc. of the user.

[0080] 7 is a block diagram showing an example of the functional configuration of the mobile terminal 2. The mobile terminal 2 has an information extraction unit 77, an extracted information transmission unit 78, a payment request unit 79, and a code image reception unit 80. These blocks are configured by the CPU 64 executing a predetermined program, and processing for realizing the parking lot management method according to this embodiment is realized.

[0081] The information extraction unit 77 reads the code image captured by the camera 69 (mainly the rear camera) and extracts the information contained in the code image.

[0082] The extracted information transmitting unit 78 transmits the information extracted from the code image to the parking lot management device 3 via the network 12.

[0083] The settlement request unit 79 requests the parking lot management device 3 to settle the parking fee via the network 12. For example, the settlement request is transmitted to the parking lot management device 3 in response to an instruction from the user.

[0084] The code image receiving unit 80 receives the code image transmitted from the parking lot management device 3 via the network 12. In this embodiment, a web page including the code image is generated by the parking lot management device 3. The code image receiving unit 80 of the mobile terminal 2 receives the web page, thereby receiving the code image. Of course, the present invention is not limited to this configuration.

[0085] 8 is a block diagram showing an example of the functional configuration of the parking lot management device 3. The parking lot management device 3 has an information management unit 82, a code image generation unit 83, a code image transmission unit 84, and a payment acceptance unit 85. These blocks are configured by the processor of the parking lot management device 3 executing a predetermined program and cooperating with the hardware resources within the device, thereby realizing the processing for realizing the parking lot management method according to this embodiment. There are no limitations on the method for installing the program in the parking lot management device 3.

[0086] The information management unit 82 manages various types of information, such as sending information, receiving information, writing information to the DB 13 and the like, and reading information from the DB 13 and the like.

[0087] The code image generating unit 83 generates a code image (management-side code image) according to the present invention, which will be described later. The code image transmitting unit 84 transmits the code image generated by the code image generating unit 83 to the mobile terminal 2 via the network 12.

[0088] In this embodiment, a web page including the code image (management-side code image) generated by the code image generation unit 83 is generated. The code image transmission unit 84 transmits the web page. Of course, the present invention is not limited to this configuration.

[0089] The settlement reception unit 85 accepts the settlement request sent from the mobile terminal 2 and executes the settlement process for the parking fee. For example, an instruction to settle the parking fee is sent to the settlement institution 5 shown in FIG. 1. If the settlement request sent from the mobile terminal 2 requests settlement using points related to this parking lot management service, the point settlement process is executed based on the point balance in the user DB. There are no restrictions on the settlement method for the parking fee, and any settlement method may be adopted, such as a settlement method including a fee discount based on the purchase of a product, or payment by debit card or electronic money.

[0090] [Basic operation of parking lot management method] 9 is a schematic diagram showing the basic flow of the parking lot management method by the parking lot management system 1. First, a parking ticket 88 displaying a code image 87 is issued to a user who is driving a vehicle into the parking lot 9 (step 101).

[0091] When issuing a parking ticket 88, first, the information management unit 54 of the ticket issuing device 10 generates information (hereinafter referred to as parking ticket information) to be stored in the code image 87. In this embodiment, the parking ticket information generated includes a "parking ticket number," an "entry date and time," and "parking lot information."

[0092] The "parking ticket number" is a number for identifying the parking ticket 88. The "entry date and time" is information on the date and time when the user's vehicle entered the parking lot.

[0093] "Parking lot information" includes any information related to the parking lot 9 that is used for the management of the parking lot 9 by the parking lot management device 3. For example, "parking lot information" includes information related to the issuance status of the parking ticket 88, information related to the sales amount, information related to change, information related to fee setting, information related to the status of the devices installed in the parking lot 9, and information related to invalid parking tickets.

[0094] Information regarding the issuance status of parking tickets 88 includes, for example, information on the number of issued tickets, the number of unissued parking tickets 88 (remaining number of parking ticket papers), information that parking tickets 88 have run out, and information on the frequency of issuing parking tickets 88.

[0095] The sales amount information includes, for example, information on parking fees settled by the settlement device 11. For example, the sales amount may be tallied on a monthly, weekly, daily, or hourly basis. Information on the collection status of parking fees, etc., is also included in the sales amount information.

[0096] The information about change includes, for example, the amount of change (remaining coins and bills), the denomination of change, the degree of need for replenishment, and the like.

[0097] The information regarding pricing includes, for example, information such as parking fee per unit time, daytime fee, nighttime fee, maximum parking fee, and the time when the maximum parking fee applies.

[0098] In this embodiment, the information about the status of the devices arranged in the parking lot 9 includes any information about the status of the ticket issuing device 10, the settlement device 11, the entrance gate 23, and the exit gate 24. For example, the information about the status of the devices arranged in the parking lot 9 also includes the status (normal / failed) of the internal modules of these devices and the status of consumables used.

[0099] An invalid parking ticket is a parking ticket for which payment has been made and the vehicle has already left the parking lot 9. Information about the free parking ticket includes the parking ticket number of the invalid parking ticket, the number of times the code image of the invalid parking ticket was read, the date and time of reading, and other information.

[0100] All of these pieces of information may be generated as "parking lot information," or only one piece of information may be generated. Of course, information other than the above may also be generated as "parking lot information." Information regarding the status of consumables may also be managed, such as remaining parking ticket paper, remaining receipt paper, remaining change, remaining bills, etc.

[0101] Furthermore, the latest information is generated as the "parking lot information." That is, information corresponding to the latest state of the parking lot 9 is generated as the latest "parking lot information." The "parking lot information" may be generated with a version number or the like added to determine that it is the latest information.

[0102] The code image generation unit 55 of the ticket issuing device 10 generates a code image 87 that stores parking ticket information ("parking ticket number," "entry date and time," and "parking lot information"). The parking ticket printer 37 prints the code image 87 on a parking ticket 88. Then, the card feeder 38 operates to issue the parking ticket 88.

[0103] The code image 87 can have any configuration, such as a one-dimensional code, a stacked two-dimensional code, or a matrix two-dimensional code. On the other hand, a code image that can be widely read by the user's mobile terminal 2 is desirable, and for example, a QR code (registered trademark) or a barcode is suitable. Of course, as the reading function of the user's mobile terminal 2 improves, the configuration of the code image 87 suitable for the present invention is also expected to change. For example, a color code such as a Chameleon Code (registered trademark) is also likely to be usable.

[0104] 9, a user uses the portable terminal 2 to read the code image 87 displayed on the parking ticket 88 (step 102). The information extraction unit 77 of the portable terminal 2 extracts the parking ticket information ("parking ticket number," "entry date and time," and "parking lot information") stored in the code image 87. Then, the extracted information transmission unit 78 transmits the extracted parking ticket information ("parking ticket number," "entry date and time," and "parking lot information") to the parking lot management device 3 (step 103).

[0105] In this way, the parking lot management system 1 is configured so that when the code image 87 is read by a mobile terminal 2 having the function of reading the user's code image 87, the parking ticket information stored in the code image 87 is transmitted from the mobile terminal 2 to the parking lot management device 3.

[0106] The information management unit 82 of the parking lot management device 3 analyzes the "parking lot information" transmitted by the mobile terminal 2, and grasps the latest state and latest situation of the parking lot 9. Then, the parking lot management device 3 appropriately executes management processing for managing the parking lot 9.

[0107] For example, when malfunction information of a device (including an internal module) installed in the parking lot 9 is acquired, the information is shared from the parking lot management device 3 with the management institution terminal 4 and the owner terminal 8, and appropriate countermeasures are taken in cooperation with each other. It is also advisable to appropriately share information with the management institution terminal 4 etc. regarding the status of consumables, such as remaining parking ticket paper, remaining receipt paper, remaining change, remaining banknotes, etc.

[0108] In addition, in response to the portable terminal 2 reading the code image 87 printed on the parking ticket 88, the portable terminal 2 may be able to display the same code image 87 as that printed on the parking ticket 88.

[0109] For example, although not shown in Fig. 9, the code image generation unit 83 of the parking lot management device 3 generates a code image 87 that is the same as the one printed on the parking ticket 88 based on the parking ticket information ("parking ticket number," "entry date and time," and "parking lot information") transmitted from the mobile terminal 2. Then, the code image transmission unit 84 transmits the code image 87 that is the same as the one printed on the parking ticket 88 to the mobile terminal 2. This makes it possible to deal with, for example, loss of the parking ticket 88.

[0110] As shown in Figure 9, in this embodiment, the parking lot management device 3 can send a management side code image containing parking ticket information with added "management information" to the mobile terminal 2 that sent the parking ticket information stored in the code image 87 to the parking lot management device 3 (step 104).

[0111] The "management information" includes any information for managing the parking lot 9. For example, the "management information" includes information regarding changes to fee settings, information regarding changes to settings of devices installed in the parking lot 9, information regarding update programs for devices installed in the parking lot 9, and information regarding stores 6 (facilities) affiliated with the parking lot 9.

[0112] Information relating to changes in pricing includes, for example, information relating to changes in parking fees per unit time, daytime fees, nighttime fees, maximum parking fees, and the time periods when the maximum parking fees apply.

[0113] Information regarding setting changes of devices installed in the parking lot 9, in this embodiment, includes any information indicating setting changes of the ticket issuing device 10, the settlement device 11, the entrance gate 23, and the exit gate 24. Information regarding setting changes of the internal modules of these devices is also included.

[0114] In this embodiment, the information on the update programs for the devices installed in the parking lot 9 includes update program information for the ticket issuing device 10, the settlement device 11, the entrance gate 23, and the exit gate 24. Of course, update program information for the internal modules of these devices is also included.

[0115] Information about the store 6 (facility) that is affiliated with the parking lot 9 includes, for example, information about the newly affiliated store 6 and information about the details of the partnership (such as the discount amount and discount conditions).

[0116] The "management information" is generated by the information management unit 82 of the parking lot management device 3. All of the above information may be generated as the "management information", or one piece of information may be generated. Of course, information other than the above may also be generated as the "management information".

[0117] Furthermore, the latest information is generated as the "management information." That is, information for realizing the latest management processing for the parking lot 9 is generated as the latest "management information." The "management information" may be generated with a version number or the like added to determine that it is the latest information.

[0118] The information management unit 82 of the parking lot management device 3 adds the generated "management information" to the parking ticket information. At this time, the "parking lot information" may be deleted from the parking ticket information.

[0119] The code image generation unit 83 of the parking lot management device 3 generates a management-side code image that stores the parking ticket information to which "management information" has been added. Then, the code image transmission unit 84 transmits the management-side code image to the mobile terminal 2. The management-side code image stores at least the "parking ticket number," "entry date and time," and "management information."

[0120] The mobile terminal 2 can display the management-side code image 89. For example, in response to reception of the management-side code image 89 by the mobile terminal 2, the code image 87, which is the same as that printed on the parking ticket 88, is automatically updated to the management-side code image 89. At that time, the user may be notified that the code image has been updated to the management-side code image 89.

[0121] When the user leaves the parking lot 9, the user can perform payment operations using the mobile terminal 2 (step 105). The control-side code image 89 displayed on the mobile terminal 2 is held over the code image reader 46 of the payment device 11. The information extraction unit 59 of the payment device 11 extracts the parking ticket information stored in the control-side code image 89.

[0122] The settlement unit 60 of the settlement device 11 settles the parking fee based on the "entry date and time" included in the parking ticket information. In other words, when the settlement device 11 reads the management side code image 89 displayed on the mobile terminal 2, it can settle the parking fee based on the "entry date and time" stored in the management side code image 89.

[0123] The parking fee is displayed on the touch panel 49 of the settlement device 11, and the bill and coin management unit 47 and receipt printer 48 operate to accept the settlement operation by the user. Once the parking fee settlement is complete, the exit gate 24 opens, allowing the vehicle to exit the parking lot 9.

[0124] When the settlement operation using the mobile terminal 2 in step 105 is performed, the information extraction unit 59 extracts the "management information" stored in the management-side code image 89. The update processing unit 62 of the settlement device 11 executes processing related to the management of the parking lot 9 based on the "management information" stored in the management-side code image 89.

[0125] For example, the update processing unit 62 changes the fee setting based on information regarding the change in fee setting. The changed fee setting is stored in the memory 42 or the like and is used for calculating parking fees thereafter. Also, based on information regarding changes in the settings of devices installed in the parking lot 9, various setting changes are made to the ticket issuing device 10, the settlement device 11, the entrance gate 23, and the exit gate 24. Of course, setting changes are made to the internal modules of these devices.

[0126] Furthermore, based on the update programs for the devices installed in the parking lot 9, update processes are executed for the ticket issuing device 10, the settlement device 11, the entrance gate 23, and the exit gate 24. Typically, the software for these devices is updated. Of course, update processes are also executed for the internal modules of these devices. Furthermore, based on information about the stores 6 (facilities) affiliated with the parking lot 9, information about affiliated stores and the details of the partnership are updated.

[0127] In addition, various processes may be executed as processes related to the management of the parking lot 9 based on the "management information." Furthermore, the update processing unit that executes the processes is not limited to being configured in the settlement device 11, but may also be configured in the ticket issuing device 10, the entrance gate 23, the exit gate 24, etc. Then, the ticket issuing device 10, the settlement device 11, the entrance gate 23, and the exit gate 24 may each execute processes related to the management of the parking lot 9 independently or in conjunction with each other as appropriate.

[0128] The user can also perform payment using the parking ticket 88 (step 106). The code image 87 displayed on the parking ticket 88 is held over the code image reader 46 of the payment device 11. The information extraction unit 59 of the payment device 11 extracts the parking ticket information stored in the code image 87.

[0129] The settlement unit 60 of the settlement device 11 settles the parking fee based on the "entry date and time" included in the parking ticket information. In other words, when the settlement device 11 reads the code image 87 displayed on the parking ticket 88, it can settle the parking fee based on the "entry date and time" stored in the code image 87. Once the settlement of the parking fee is complete, the exit gate 24 opens, allowing the vehicle to exit the parking lot 9.

[0130] In this way, in this parking lot management system 1, it is possible to complete the settlement of parking fees using the parking ticket 88 through the ticket issuing device 10, the parking ticket 88, and the settlement device 11. This allows users who do not have a mobile terminal 2 that has the function of reading the code image 87 to use the parking lot 2 without any problems.

[0131] 9, in the present parking lot management system 1, a user can use a mobile terminal 2 to read a code image 87 printed on a parking ticket 88, thereby transmitting "parking lot information" to the parking lot management device 3. Also, every time a user uses the mobile terminal 2 to perform a settlement operation on the settlement device 11, the user can have the settlement device 11 read the "management information."

[0132] That is, in this parking lot management system 1, it is possible to transmit "parking lot information" reflecting the latest status of the parking lot 9 to the parking lot management device 3 via the user's mobile terminal 2. Also, it is possible to transmit the latest "management information" of the parking lot management device 3 to the settlement device 11 via the user's mobile terminal 2, and it is also possible to output (transfer) it to the ticket issuing device 10.

[0133] This allows the parking lot management device 3 to manage the parking lot 9 without building a communication system that enables communication between the ticket issuing device 10 and the settlement device 11 and the parking lot management device 3. As a result, even if the parking lot management device 3 is installed in a remote location away from the parking lot 9, it is possible to reduce the operating costs for managing the parking lot 9.

[0134] (Online payment using a mobile device) In this embodiment, it is also possible to perform online payment using the mobile terminal 2. The user inputs a predetermined online payment operation into the mobile terminal 2 that reads the code image 87 printed on the parking ticket 88.

[0135] The settlement request unit 79 of the mobile terminal 2 requests the parking lot management device 3 to settle the parking fee via the network 12. The settlement request sent from the mobile terminal 2 is accepted by the settlement acceptance unit 85 of the parking lot management device 3. Then, the parking fee is settled based on the "entry date and time" included in the parking ticket information sent from the mobile terminal 2.

[0136] When the payment of the parking fee is completed, the information management unit 82 of the parking lot management device 3 adds "information indicating that the payment of the parking fee has been completed (hereinafter referred to as payment completion information)" to the parking ticket information. Then, the code image generation unit 83 generates a management-side code image 89 that stores the parking ticket information to which the "payment completion information" has been added. The generated management-side code image 89 is transmitted to the mobile terminal 2.

[0137] When the vehicle is to leave the parking lot 9, the management side code image 89 displayed on the mobile terminal 2 is held over the code image reader 46 of the settlement device 11. The information extraction unit 59 of the settlement device 11 extracts the "payment completion information" stored in the management side code image 89.

[0138] The settlement unit 60 of the settlement device 11 settles the parking fee based on the "settlement completion information" included in the parking ticket information. For example, the touch panel 49 displays 0 yen as the parking fee. Alternatively, a notification is given that settlement has already been completed. Then, the exit gate 24 opens, allowing the vehicle to exit the parking lot 9.

[0139] Even in this case, by holding the management side code image 89 displayed by the mobile terminal 2 over the code image reader 46 of the settlement device 11, it becomes possible for the settlement device 11 to read the "management information" generated by the parking lot management device 3.

[0140] The information indicating that the parking fee settlement has been completed is included in the information regarding the status of the parking fee settlement by the user according to the present invention. Furthermore, the execution of the parking fee settlement by the settlement device 11 based on the "payment completion information" is one embodiment of the execution of the parking fee settlement based on the information regarding the payment status stored in the management side code image 89 when the management side code image 89 displayed by the mobile terminal 2 is read.

[0141] As information regarding the settlement status, not only "settlement completion information" but also any information such as regular payment information may be used.

[0142] (Use of discount services from affiliated stores) In this embodiment, it is possible to use discount services from stores 6 that are affiliated with the parking lot 9.

[0143] As described above, in this embodiment, a terminal having a function for reading the code image 87 and the management-side code image 89 is used as the store terminal 7 of the affiliated store 6 of the discount service. When a user pays for purchases at the store 6, the user holds the code image 87 or the management-side code image 89 over the code image reader 14 of the store terminal 7.

[0144] When the store terminal 7 reads the code image 87 or the management side code image 89, it associates the shopping information regarding the user's purchase with the parking ticket information stored in the code image 87 or the management side code image 89 and transmits it to the parking lot management device 3.

[0145] In this embodiment, "discount information (information on discount amount, free parking time, etc.)" is associated with parking ticket information as shopping information and transmitted to the parking lot management device 3. For example, "parking ticket number" and "shopping information (discount information)" are associated with each other and transmitted to the parking lot management device 3. Of course, payment information for merchandise, etc. may be transmitted to the parking lot management device 3 as shopping information, and discount information may be generated by the parking lot management device 3 based on the shopping information.

[0146] The information management unit 82 of the parking lot management device 3 adds "shopping information (discount information)" to the parking ticket information. Then, the code image generation unit 83 generates a management-side code image 89 that stores the parking ticket information to which the "shopping information (discount information)" has been added. The generated management-side code image 89 is transmitted to the mobile terminal 2.

[0147] When the vehicle is to exit the parking lot 9, the management side code image 89 displayed on the mobile terminal 2 is held over the code image reader 46 of the settlement device 11. The information extraction unit 59 of the settlement device 11 extracts the "shopping information (discount information)" stored in the management side code image 89.

[0148] The settlement unit 60 of the settlement device 11 settles the parking fee based on the "shopping information (discount information)." For example, the discounted parking fee is displayed on the touch panel 49. Once the parking fee settlement is complete, the exit gate 24 opens, allowing the vehicle to exit the parking lot 9.

[0149] Even in this case, by holding the management side code image 89 displayed by the mobile terminal 2 over the code image reader 46 of the settlement device 11, it becomes possible for the settlement device 11 to read the "management information" generated by the parking lot management device 3.

[0150] When online payment is made using the mobile terminal 2, the payment acceptance unit 85 of the parking lot management device 3 makes payment of the parking fee based on the "shopping information (discount information)."

[0151] (Latest parking information / Latest management information) In managing a parking lot by sending and receiving "parking lot information" and "management information" as shown in Fig. 9, it is important to receive the latest "parking lot information" from the settlement device 11. It is also important to send the latest "management information" to the settlement device 11.

[0152] It is also important that the settlement device 11 receives the "management information" without any omissions. In other words, it is desirable to avoid generating and transmitting new "management information" when the "management information" has not yet arrived at the settlement device 11.

[0153] In addition, in the present parking lot management system 1, parking ticket information including the same "parking lot information" may be transmitted from each of the portable terminals 2 of multiple users. Also, it may be the case that a management-side code image 89 storing the same "management information" is transmitted to each of the portable terminals 2 of multiple users.

[0154] To deal with such a situation, the parking lot management device 3 may determine whether the "parking lot information" included in the parking ticket information transmitted from the mobile terminal 2 is the latest. For example, it is possible to determine whether the "parking lot information" is the latest by referring to a version number or the like added to the "parking lot information."

[0155] Furthermore, the "parking lot information" generated by the ticket issuing device 10 may include information regarding the reading status of the "management information" stored in the management side code image 89 by the settlement device 11. For example, the "parking lot information" may include the version number of the "management information" that was successfully read.

[0156] This allows the parking lot management device 3 to grasp the "management information" that has arrived at the settlement device 11 based on information about the reading status of the "management information" included in the "parking lot information." For example, if the latest "management information" has arrived without any problems, it becomes possible to process the next "management information" as the latest "management information."

[0157] Furthermore, the "management information" generated by the parking lot management device 3 may include information regarding the reception status of the "parking lot information" transmitted from the mobile terminal 2. For example, the "management information" may include the version number of the properly received "parking lot information."

[0158] This allows the settlement device 11 to grasp the "parking lot information" that has arrived at the parking lot management device 3 based on information about the reception status of the "parking lot information" contained in the "management information." By sharing this information with the ticket issuing device 10, if the latest "parking lot information" has arrived without any problems, it becomes possible to process the next "parking lot information" as the latest "parking lot information."

[0159] [Example of specific parking lot management methods] A specific example of the operation of the parking lot management method by the parking lot management system 1 will now be described. Fig. 10 is a flowchart showing an example of the operation of the ticket issuing device 10.

[0160] The vehicle detection unit 52 of the ticket issuing device 10 monitors the detection of an entering vehicle (step 201). If an entering vehicle is detected (YES in step 201), the code image generation unit 55 generates a code image 87 (step 202).

[0161] Fig. 11 is a schematic diagram showing an example of parking ticket information in this embodiment, Fig. 12 is a schematic diagram for explaining divided parking lot information and divided management information.

[0162] In this embodiment, the information management unit 54 of the ticket issuing device 10 generates the following information as parking ticket information. "URL": The URL of the payment page for online payment of parking fees using the mobile terminal 2. "Parking ticket number": A number used to identify a parking ticket. "Serial number (parking ticket number serial number)"...Information regarding the type of code image 87 and management side code image 89. The code image 87 printed on the parking ticket 88 will be "1". The management side code image 89 in which "management information" is stored will be "2". Furthermore, the management side code image 89 in which "shopping information" is stored will be "3". Furthermore, the management side code image 89 in which "payment completion information" is stored will be "4".

[0163] "Entry date and time": The date and time the user's vehicle entered. "Shopping Information": Shopping information (discount information) at stores affiliated with discount services. When the parking ticket 88 is issued, this is set to "0 (yen)" or is blank. "Fee Information": Parking fee information. When parking ticket 88 is issued, this will be "0 (yen)" or blank. "Settlement information": Information on the amount paid. When parking ticket 88 is issued, this will be "0 (yen)" or blank. "Divided Parking Lot Information" "Serial number (parking lot information serial number)": A number used to identify divided parking lot information. "Division management information"..."0" or blank when parking ticket 88 is issued. "Serial number (management information serial number)": A number used to identify the divided management information.

[0164] As shown in Fig. 12A, in this embodiment, the information management unit 54 of the ticket issuing device 10 divides the parking lot information into multiple divided parking lot information 91. The value "1" of "parking lot information N1" shown in Fig. 12A is a number for identifying the parking lot information. By referring to this number, it is possible to determine whether the parking lot information is the latest information.

[0165] The values ​​after the hyphens in "N1-1" and "N1-2" of the divided parking lot information 91 shown in Figure 12A are numbers for identifying the divided parking lot information 91, and are values ​​that are stored in the parking ticket information as "serial numbers (parking lot information serial numbers)." In this embodiment, numbers (serial numbers) are added to the divided parking lot information 91 in order from the first half of the data.

[0166] 12A, the parking lot information is divided into two, but the number of divisions is not limited. Also, the method of adding the "serial number (parking lot information serial number)" is not limited.

[0167] In this embodiment, the ticket issuing device 10 generates a plurality of code images 87 each storing a plurality of divided parking lot information 91, and displays the code images 87 on a plurality of parking tickets 88. That is, one piece of divided parking lot information 91 is selected and stored in one code image 87. The code image 87 is printed on the parking ticket 88.

[0168] 12B, in this embodiment, the information management unit 82 of the parking lot management device 3 divides the management information into multiple pieces of divided management information 92. The value "1" of "management information M1" shown in FIG. 12B is a number for identifying the management information. By referring to this number, it is possible to determine whether the management information is the latest information.

[0169] 12B, the values ​​after the hyphens in "M1-1" to "M1-8" of the divided management information 92 are numbers for identifying the divided management information 92, and are values ​​stored as "additional numbers (management information additional numbers)." In this embodiment, numbers (additional numbers) are added to the divided management information 92 in order from the first half of the data.

[0170] 12B, the management information is divided into eight parts, but the number of parts is not limited.Furthermore, the method of adding the "additional number (management information additional number)" is not limited.

[0171] In this embodiment, the parking lot management device 3 generates a plurality of management-side code images 89 storing each of the plurality of divided management information 92, and transmits them to each of the plurality of mobile terminals 2. That is, one piece of divided management information 92 is selected and stored in one management-side code image 89. The management-side code image 89 is transmitted to the mobile terminal 2.

[0172] A code image 87 storing the above parking ticket information is generated and printed on a parking ticket 88 by the parking ticket printer 37. Then, the card feeder 38 operates to issue the parking ticket 88 (step 203).

[0173] Fig. 13 is a schematic diagram showing an example of the configuration of a parking ticket 88 according to this embodiment. In the example shown in Fig. 13, the following information is printed: "Name of parking lot," "Contact information," "Parking ticket number," "Entry date and time," code image 87 ("Code image 1"), "Comment on payment method," and "Comment on reading the 2D code using a mobile terminal." Of these, "Parking ticket number" and "Entry date and time" are information stored in code image 87 ("Code image 1").

[0174] In addition, the value of "1" in "Code Image 1" in the figure corresponds to the "Serial Number (Parking Ticket Number Serial Number)" shown in Figure 11, and indicates that it is the code image 87 printed on the parking ticket 88.

[0175] The removal of the parking ticket 88 is monitored (step 204). If the parking ticket 88 is removed (YES in step 204), the gate control unit 53 opens the entrance gate 23 (step 205).

[0176] The vehicle detection unit 52 monitors the entry of a vehicle into the premises 25 of the parking lot 9 (step 206). If entry into the premises 25 of the parking lot 9 is detected (YES in step 206), the gate control unit 53 closes the entrance gate 23 (step 207).

[0177] The parking information is updated by the information management unit 54 (step 208). The parking information includes the parking ticket number and status information indicating that the vehicle has entered normally, and is managed by the settlement device 11.

[0178] 14 is an example of a checkout page displayed on the user's mobile terminal 2. The checkout page 94 described below can also be called a code image display page that displays the code image 87 and the management side code image 89.

[0179] In this embodiment, when the mobile terminal 2 reads the code image 87 ("code image 1") displayed on the parking ticket 88, the parking ticket information stored in the code image 87 ("code image 1") is sent to the parking lot management device 3.

[0180] 14A is displayed on the mobile terminal 2 based on the "URL" included in the parking ticket information. That is, in this embodiment, the parking ticket information is transmitted to the parking lot management device 3 at the same time as accessing the payment page 94a, which is a web page.

[0181] As shown in FIG. 14A, the payment page 94a includes a URL display section 95, a parking lot name display section 96, an update button 97, a payment stage display section 98, a code image display section 99, and a payment button 100.

[0182] The URL display section 95 displays the URL of the payment page 94a. The parking lot name display section 96 displays text including the name of the parking lot. The update button 97 is used to update the payment page 94a to the latest version. The code image display section 99 displays the code image 87.

[0183] The payment stage display section 98 displays information that allows the user to grasp the progression of stages related to the payment of parking fees. In this embodiment, five stages are displayed: "Code Display," "Shopping Information," "Payment," "Confirmation," and "Complete." When the code image 87 printed on the parking ticket 88 is read, "Code Display" is highlighted. Then, the code image display section 99 displays the same code image 87 ("Code Image 1") as that printed on the parking ticket 88.

[0184] At a later timing, the parking lot management device 3 adds "management information" to the parking ticket information. In this case, in this embodiment, the "management information" is stored in the parking ticket information shown in FIG. 11, and "2" is stored in the "serial number (parking ticket number serial number)." A management-side code image 89 ("code image 2") storing the parking ticket information is sent from the parking lot management device 3 to the mobile terminal 2. Then, the management-side code image ("code image 2") is displayed in the code image display section 99 of the payment page 94a of the mobile terminal 2.

[0185] When a user of the parking lot 9 makes a purchase at the affiliated store 6 shown in FIG. 1 and pays, the user has the code image reader 14 of the store terminal 7 read "Code Image 1" (or "Code Image 2") on the payment page 94a shown in FIG. 14A. The store terminal 7 then associates "shopping information (discount information)" with the parking ticket information (e.g., "parking ticket number") stored in "Code Image 1" ("Code Image 2") and transmits it to the parking lot management device 3.

[0186] In the parking lot management device 3, "shopping information (discount information)" is added to the parking ticket information. In this embodiment, in the parking ticket information shown in FIG. 11, "shopping information (discount information)" is stored, and "3" is stored in "serial number (parking ticket number serial number)". A management-side code image 89 ("code image 3") in which the parking ticket information is stored is transmitted from the parking lot management device 3 to the mobile terminal 2.

[0187] 14B is displayed on the mobile terminal 2. On the checkout page 94b, "Code Display" and "Shopping Information" are highlighted in the checkout step display section 98 ("Code Display" may be displayed grayed out). The management side code image 89 ("Code Image 3") is then displayed in the code image display section 99. By checking the checkout step display section 98, the user can see that the discount for shopping at the affiliated store 6 has been applied and the code image has been updated.

[0188] If the user makes additional purchases at the affiliated store 6, the "shopping information (discount information)" data will be updated as needed. In accordance with the data update due to the additional purchases, the "serial number (parking ticket number serial number)" may be moved up to "3-1 (first purchase)" or "3-2 (second purchase)." Of course, the "shopping information (discount information)" may be updated while the "serial number (parking ticket number serial number)" remains at "3."

[0189] Furthermore, even if multiple users, such as passengers in the same vehicle, use the same code image 87 (management side code image 89) to make separate purchases, this can be handled by updating the "shopping information (discount information)" each time. In other words, the parking lot management system 1 can easily apply a shopping discount to a group when there are multiple occupants in one vehicle, for example.

[0190] When a user performs online payment using the mobile terminal 2, the payment button 100 is selected. This displays the payment page 94c shown in FIG. 14C. On the payment page 94c, "Code Display," "Shopping Information," and "Payment" are highlighted in the payment step display section 98 ("Code Display" and "Shopping Information" may be displayed in grayout). Then, the code image display section 99 displays payment content information instead of the code image 87 (management side code image 89).

[0191] In this embodiment, the payment details information displayed includes "parking ticket number," "entry date and time," "parking fee," "shopping discount," and "payment method." The text displayed on the payment button 100 is also changed from "payment" to "payment." This means that the payment button 100 has been changed to a payment execution button.

[0192] In Figure 14C, the "Payment Method" is set to credit card, and is surrounded by a dotted line. A link is embedded in the area surrounded by the dotted line, and when the user selects it, they are taken to a screen where they can input credit card information (credit card number, etc.). In addition, other payment methods such as code payment and point payment can be set and changed from the link.

[0193] It is even more preferable if this setting is stored inside the mobile terminal 2 as input information for the mobile terminal 2, and is automatically set the next time the screen is switched to (the next time the user enters the parking lot, or when the current time is exceeded, etc.) This setting information regarding payment is not transmitted to the parking lot management device 3 from the viewpoint of protecting personal information and security.

[0194] Although not shown in FIG. 14, when the settlement button 100 shown in FIG. 14C is selected, confirmation information for confirming the settlement details is displayed. At that time, "Code Display," "Shopping Information," "Settlement," and "Confirmation" are highlighted in the settlement stage display unit 98 ("Code Display," "Shopping Information," and "Settlement" may be displayed in gray). Then, when the settlement button 100 is selected again, a settlement request is sent from the settlement request unit 79 of the mobile terminal 2 to the parking lot management device 3. The settlement acceptance unit 85 of the parking lot management device 3 executes settlement of the parking fee.

[0195] When the parking fee payment is completed, the information management unit 82 of the parking lot management device 3 adds "payment completion information" to the parking ticket information as information regarding the payment status. In this embodiment, in the parking ticket information shown in FIG. 11, "fee information" and "payment information" are stored, and "4" is stored in "serial number (parking ticket number serial number)". A management-side code image 89 ("code image 4") storing the parking ticket information is sent from the parking lot management device 3 to the mobile terminal 2.

[0196] 14D is displayed on the mobile terminal 2. On the payment page 94d, "Code Display," "Shopping Information," "Payment," "Confirm," and "Complete" are highlighted in the payment step display section 98 (all but "Complete" may be grayed out). The management side code image ("Code Image 4") is then displayed in the code image display section 99. By checking the payment step display section 98, the user can see that the payment of the parking fee via online payment has been completed and the code image has been updated.

[0197] Furthermore, if you need to re-settle the parking fee, for example, if you want to extend the parking period after paying online, or if you forget to present the code image at the affiliated store 6 and want to receive a discount again, you can re-settle by selecting the re-settlement button 101.

[0198] 15 is a flowchart showing an example of the operation of the settlement device 11. The vehicle detection unit 57 of the settlement device 11 monitors the detection of an exiting vehicle (step 301). If an exiting vehicle is detected (YES in step 301), the code image 87 (management side code image 89) is read via the code image reader 46 (step 302). The information extraction unit 59 extracts the parking ticket information stored in the code image 87 (management side code image 89).

[0199] The information management unit 61 of the settlement device 11 determines whether online settlement using the mobile terminal 2 has been completed (step 303). This determination is made by referring to the "serial number (parking ticket number serial number)" of the parking ticket information extracted from the code image 87 (management side code image 89).

[0200] If the "serial number (parking ticket number serial number)" in the parking ticket information is a value other than "4," it is determined that online settlement has not been completed (NO in step 303), and the settlement unit 60 of the settlement device 11 settles the parking fee (step 304). For example, the parking fee is calculated based on the "entry date and time" included in the parking ticket information, and if "shopping information (discount information)" is extracted, the amount obtained by deducting the "shopping information (discount information)" from the parking fee is presented to the user.

[0201] When the parking fee has been paid, the exit gate 24 is opened by the gate control unit 58 (step 305).

[0202] If the "serial number (parking ticket number serial number)" in the parking ticket information is "4", it is determined that the parking fee has been settled online (YES in step 303), and the gate control unit 58 opens the exit gate 24 (step 305).

[0203] The vehicle detection unit 57 monitors the exit of the vehicle from the parking lot 9 (step 306). If the exit of the vehicle from the parking lot 9 is detected (YES in step 306), the gate control unit 58 closes the exit gate 24 (step 307).

[0204] The parking information is updated by the information management unit 61 (step 308). Specifically, status information indicating that the vehicle has exited normally is recorded in the parking information.

[0205] After the vehicle leaves the parking lot 9, the parking ticket 88 becomes an invalid parking ticket, and the "parking ticket number" is stored as an "invalid parking ticket number" in the settlement device 11. After that, the code image 87 and the management side code image 89 in which the "free parking ticket number" is stored become invalid, and settlement processing and the like are not executed.

[0206] This prevents, for example, if a user throws away the parking ticket 88 after exiting the vehicle, another user from picking up the parking ticket 88 and paying for it. It is also possible to prevent fraud such as another user taking a photo of the management side code image 89 in which the "payment completion information" is stored, that is, the management side code image 89 in which the "serial number (parking ticket number serial number)" of the parking ticket information is "4", with the mobile terminal 2 and misusing it to pay for their own parking fee.

[0207] In addition, in step 304, when the divided management information 92 is extracted from the management-side code image 89, the divided management information 92 is managed by the information management unit 61. For example, by referring to the "serial number (management information serial number)" included in the parking ticket information, it is determined whether or not reading of all the divided management information 92 has been completed.

[0208] When reading of all the divided management information 92 is completed, the management information is restored. Then, the update processing unit 62 of the settlement device 11 executes processing related to the management of the parking lot 9 based on the restored management information. Note that there may be cases where processing related to management can be executed based on the divided management information 92. In other words, processing may be executed without waiting for the restoration of the management information.

[0209] FIG. 16 is a flowchart showing an example of processing related to the handling of "parking lot information" and "management information" by the parking lot management device 3.

[0210] The parking ticket information transmitted from the mobile terminal 2 is received (step 401). The information management unit 82 determines whether the divided parking lot information 91 included in the parking ticket information is the latest "parking lot information" that has been divided (step 402). This determination is made by referring to the number ("1" of "N1" shown in FIG. 12A) in the divided parking lot information 91 that identifies the "parking lot information" that was the source of the division.

[0211] If the "parking lot information" from which the division is made is the latest (YES in step 402), it is determined whether the divided parking lot information 91 has already been received (step 403). For example, the divided parking lot information 91 may have already been received from another mobile terminal 2.

[0212] The determination in step 403 is made by referring to the "serial number (parking lot information serial number)" included in the parking ticket information. If the divided parking lot information 91 has not been received (NO in step 403), the divided parking lot information 91 is stored in DB 13 as new information (step 404).

[0213] If the "parking lot information" from which the information is divided is not the latest, or if the divided parking lot information 91 has already been received, the divided parking lot information 91 is not stored, or is temporarily stored in a memory or the like.

[0214] It is determined whether the settlement device 11 has read the latest "management information" (step 405).

[0215] In this embodiment, the "parking lot information" generated by the settlement device 11 includes information regarding the reading status of the "management information" stored in the management side code image 89 by the settlement device 11. Specifically, each piece of divided parking lot information 91 includes information on the divided management information 92 that has been read. In this embodiment, the parking ticket information includes a number for identifying the "management information" from which the division originated (the "1" in "M1" shown in FIG. 12B) and the serial number of the divided management information 92 (the value after the hyphen).

[0216] For example, each of the two divided parking lot information 91 shown in Figure 12A, "N1-1" and "N1-2", includes information on the divided management information 92 that has been read by the settlement device 11. Of course, any information may be used as long as it is possible to identify the divided management information 92 that has been read.

[0217] In step 405, the information of the division management information 92 that has been read by the settlement device 11 is extracted from the divided parking lot information 91 included in the received parking ticket information. For example, assume that the "management information" of the original division is the latest and all the serial numbers of the division management information 92 are complete. In this case, the settlement device 11 determines that reading of each of the multiple division management information 92 has been completed.

[0218] In this case, step 405 is answered as YES, and new "management information" is generated as the latest "management information" (step 406).

[0219] If the management information of the division source is not the latest, or if all the serial numbers of the divided management information 92 that has been read are not complete, step 405 becomes NO and the process ends.

[0220] 16 may be executed by the settlement device 11. For example, parking ticket information is extracted from the management-side code image 89. The information management unit 61 determines whether the divided management information 92 included in the parking ticket information is the latest "management information" that has been divided. This determination is made by referring to the number ("1" of "M1" shown in FIG. 12B) in the divided management information 92 for identifying the "management information" that was the source of the division.

[0221] If the "management information" of the original device is the latest, it is determined whether the divided management information 92 has already been received. For example, the divided management information 92 may have already been read from the management-side code image 89 displayed by another mobile terminal 2.

[0222] This determination is made by referring to the "serial number (management information serial number)" included in the parking ticket information. If the division management information 92 has not been received, the division management information 92 is stored as new information in the memory 42 or the like.

[0223] If the "management information" of the division source is not the latest, or if the division management information 92 has already been received, the division management information 92 is not stored, or is temporarily stored in the memory 42 or the like.

[0224] It is determined whether the parking lot management device 3 has received the latest "parking lot information."

[0225] In this embodiment, the "management information" generated by the parking lot management device 3 includes information regarding the reception status of the parking lot information included in the parking ticket information by the parking lot management device 3. Specifically, each piece of divided management information 92 includes information on the divided parking lot information 91 that has been received. In this embodiment, the parking ticket information includes a number for identifying the "parking lot information" from which the division originated (the "1" in "N1" shown in FIG. 12A) and the serial number of the divided parking lot information 91 (the value after the hyphen).

[0226] For example, each of the eight divided management information 92, "M1-1" to "M1-8", shown in Figure 12B includes information on the divided parking lot information 91 that has been completely received by the parking lot management device 3. Of course, any information may be used as long as it is possible to identify the divided parking lot information 91 that has been completely received.

[0227] Information on the divided parking lot information 91 that has been received by the parking lot management device 3 is extracted from the divided management information 92 included in the parking ticket information read from the management side code image 89. For example, assume that the original "parking lot information" is the latest and all the serial numbers of the divided parking lot information 91 are complete. In this case, the parking lot management device 3 determines that it has completed receiving each of the multiple divided parking lot information 91. In this case, new "parking lot information" is generated as the latest "parking lot information."

[0228] In this way, in this parking lot management system 1, each of the settlement device 11 and the parking lot management device 3 can determine whether the latest ``parking lot information'' and the latest ``management information'' have been received by the other device, thereby enabling efficient transmission and reception of information.

[0229] Furthermore, the parking lot management device 3 adds information about the divided parking lot information 91 that has not been completely received to the parking ticket information and generates a management-side code image 89. When the settlement device 11 reads out the management-side code image 89, it becomes possible to detect the divided parking lot information 91 that has not been received by the parking lot management device 3. Thereafter, when printing a code image 87 to issue a parking ticket 88, it is sufficient to generate a code image 87 that stores the divided parking lot information 91 that has not been received by the parking lot management device 3. This allows the parking lot management device 3 to efficiently receive the divided parking lot information 91 that has not been completely received.

[0230] Furthermore, the settlement device 11 adds the information of the division management information 92 that has not been completely read to the parking ticket information, generates a code image 87, and prints it on the parking ticket 88. When the code image 87 is read by the mobile terminal 2, the parking ticket information including the information of the division management information 92 that has not been completely read is transmitted to the parking lot management device 3.

[0231] The parking lot management device 3 can detect, from the received parking ticket information, any divided management information 92 that has not yet reached the settlement device 11. Thereafter, when generating a management-side code image 89, it is sufficient to generate a management-side code image 89 that stores the divided management information 92 that has not yet reached the settlement device 11. By reading the management-side code image 89, the settlement device 11 can efficiently read the divided management information 92 that has not yet been read.

[0232] 12, in this embodiment, the "parking lot information" is divided to generate a plurality of divided parking lot information 91. Also, the "management information" is divided to generate a plurality of divided management information 92. This makes it possible to reduce the amount of data encoded into a single code image 87 (management side code image 89). It also makes it possible to prevent a third party from easily analyzing the "parking lot information" and "management information" and using them fraudulently.

[0233] Of course, whether to divide the data may be determined appropriately based on the amount of data in the "parking lot information" and the "management information." Also, if there is no data to be transmitted as the "parking lot information" and the "management information," division may not be performed.

[0234] As described above, in the parking lot management system 1 according to this embodiment, the ticket issuing device 10 issues a parking ticket 88 displaying a code image 87 that stores parking ticket information including the "entry date and time" and "parking lot information." When the settlement device 11 reads the code image 87 displayed on the parking ticket 88, it settles the parking fee based on the "entry date and time" stored in the code image 87. Furthermore, when the code image 87 is read by a user's portable terminal 2 that has the function of reading the code image 87, the parking ticket information stored in the code image 87 is transmitted from the portable terminal 2 to the parking lot management device 3.

[0235] This allows the parking lot management device 3 to manage the parking lot 9 without building a communication system that enables communication between the ticket issuing device 10 and the settlement device 11 and the parking lot management device 3. As a result, even if the parking lot management device 3 is installed in a remote location away from the parking lot 9, it is possible to reduce the operating costs for managing the parking lot 9.

[0236] Recently, remote parking management systems have been developed that are constantly connected to the Internet and manage the status of paid parking lots using a remote management server, allowing the local parking lot and the remote management server to share and manage the parking lot's status.

[0237] However, relatively small, temporary parking lots, such as those rented for a fee, require users to sign up for a communication line in order to be connected to the Internet at all times, and incur considerable communication connection costs in order to maintain a constant connection to the Internet 24 hours a day, 365 days a year.

[0238] Furthermore, when using wireless internet connection services that are easy to install, there are cases where communication is interrupted due to poor connection caused by problems on the part of the telecommunications carrier. Even in such cases, it is necessary to be able to continue managing the parking lot properly, but in reality, in such cases, the parking lot management company often bears the loss or damage. In other words, if fees are settled online, a communication interruption may mean that fees cannot be collected.

[0239] With the technologies disclosed in Patent Documents 1 and 2, if parking lot users take time to activate and operate their smartphones, there is a high possibility of congestion occurring at the entrance, exit, or payment machine as people wait to operate the smartphone. If vehicles line up behind them at the exit, users who do not know how to operate their smartphones and are unable to pay the fare will be unable to back out, which could cause major disruption to the operation of the parking lot. Furthermore, no consideration is given at all to the convenience of users who do not have smartphones.

[0240] The parking lot management system according to the present invention does not require a network communication system, which simplifies the facilities of the parking lot 9. Furthermore, the ticket issuing device 10 and the settlement device 11 installed in the parking lot do not need to be connected to the network 12, so there are no expensive running costs for communication contract fees. Naturally, it is possible to sufficiently prevent the operation of the parking lot 9 from being affected by the state of the communication line, such as the inability to collect parking fees if the communication line is interrupted.

[0241] Even if the ticket issuing device 10 and the settlement device 11 are not directly connected to the network 12, they can exchange parking ticket information, including "parking lot information" and "management information," with the parking lot management device 3 located in a remote location, making it possible to remotely manage the parking lot 9. In addition, it becomes possible to easily change the functions and settings of the parking lot 9 remotely with minimal cost.

[0242] Furthermore, in this parking lot management system 1, even users who do not have a mobile terminal 2 that has the function of reading the code image 87 (management side code image 89) can settle the parking fee using the parking ticket 88. Therefore, convenience for users is not impaired, and many users can use the parking lot 9 comfortably.

[0243] Furthermore, users who own the mobile terminal 2 can receive discount services associated with online payment and shopping at affiliated stores 6, providing a high level of convenience.

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

[0245] Regarding the transmission of the divided parking lot information 91 and divided management information 92 illustrated in Figure 12, it is also possible to start transmission with data with a small serial number, and once the transmitting side detects confirmation of reception from the receiving side (reading by the settlement device 11 and reception by the parking lot management device 3), increment the serial number and transmit the next divided information.

[0246] Parking lot owners can access the parking lot management device 3 to change fee settings or understand revenue status. Alternatively, parking lot owners themselves may manage the parking lot management device 3.

[0247] For example, the ticket issuing device 10 and the settlement device 11 may be equipped with a short-range wireless communication unit such as a Bluetooth module or an NFC module. Instead of or in addition to a normal parking ticket 88, short-range wireless communication may be used between the ticket issuing device 10 and the settlement device 11 and the mobile terminal 2 to manage fixed-term subscribers and repeat user registrations.

[0248] In this case, it is possible to handle an increased amount of data compared to the "parking lot information" and "management information" stored in the code image printed on a normal parking ticket 88. For example, if the code image 87 printed on the parking ticket 88 is a QR code, the standard allows for a maximum of 4296 alphanumeric characters and a maximum of 2953 binary (8-bit) bytes to be stored, whereas when implementing the present invention, it is considered preferable to limit the amount of data to about half that, 2000 characters and 1500 bytes (although, of course, the amount is not limited to this range).

[0249] When using short-range wireless communication, even if the amount of data is several to several tens of times larger, the time required for communication is very short, and the standard communication speed for Bluetooth is a maximum of 24Mbps, so it is extremely effective, especially when the "management information" is something like updating a device's program, as it allows large programs to be sent and received in one communication.

[0250] As another example, when the ticket issuing device 10 and the settlement device 11 are connected to the network 12 and operated, the configuration of the present invention may be implemented as a backup means in the event of a communication failure. Also, when communication is unstable, the present invention can be implemented by including communication connection speed information, PING speed information, etc. in the "parking lot information."

[0251] In addition, as another embodiment, instead of updating and displaying the code image 87 printed on the parking ticket 88 by adding a serial number according to the status of settlement, shopping, etc., a separate update code image such as a settlement update code image or a shopping update code image, which is different from the code image 87, may be generated and displayed alongside the code image 87 on the mobile terminal 2, or an additional settlement update parking ticket or shopping update parking ticket may be issued by the settlement device 11, or a new update code image may be printed in the margin of the parking ticket 88.

[0252] FIG. 17 is a block diagram showing an example of the hardware configuration of a computer 110 that can be used as the parking lot management device 3 or the like.

[0253] The computer 110 includes a CPU 111, a ROM 112, a RAM 113, an input / output interface 115, and a bus 114 that interconnects these components. The input / output interface 115 is connected to a display unit 116, an input unit 117, a storage unit 118, a communication unit 119, a drive unit 110, and the like. Display unit 116 is a display device using, for example, a liquid crystal display, an electroluminescent display, etc. Input unit 117 is, for example, a keyboard, a pointing device, a touch panel, or other operating device. When input unit 117 includes a touch panel, the touch panel can be integrated with display unit 116. The storage unit 118 is a non-volatile storage device, such as a HDD, flash memory, or other solid-state memory. The drive unit 110 is a device capable of driving a removable storage medium 111, such as an optical storage medium or a magnetic recording tape. The communication unit 119 is a modem, router, or other communication device that can be connected to a LAN, WAN, or the like and is used to communicate with other devices. The communication unit 119 may communicate using either a wired or wireless method. The communication unit 119 is often used separately from the computer 110. Information processing by computer 110 having the above hardware configuration is realized by software stored in storage unit 118 or ROM 112, etc., working in cooperation with the hardware resources of computer 110. Specifically, the parking lot management method (information processing method) according to the present invention is realized by loading a program constituting the software, stored in ROM 112, etc., into RAM 113 and executing it. The program is installed in the computer 110 via, for example, a recording medium 111. Alternatively, the program may be installed in the computer 110 via a global network or the like. Alternatively, any other computer-readable non-transitory storage medium may be used.

[0254] The parking lot management method and program of the present invention may be executed by multiple computers connected to each other so as to be able to communicate via a network or the like, thereby constructing a parking lot management system or parking lot management device of the present invention. In other words, the parking lot management method and program according to the present invention can be executed not only in a computer system made up of a single computer, but also in a computer system in which multiple computers operate in conjunction with each other. In this disclosure, a system refers to a collection of multiple components (devices, modules (components), etc.), regardless of whether all the components are in the same housing. Therefore, multiple devices housed in separate housings and connected via a network, and a single device housed in a single housing with multiple modules, are both systems.

[0255] The execution of the parking lot management method and program according to the present invention by a computer system includes both cases where the generation of parking ticket information, the generation of parking lot information, the generation of code images, the generation of management information, the generation of divided parking lot information, the generation of divided management information, the reading of code images, the generation of payment pages, etc. are executed by a single computer, and cases where each process is executed by a different computer. Furthermore, the execution of each process by a specific computer includes having another computer execute part or all of the process and obtaining the results. In other words, the parking lot management method and program according to the present invention can also be applied to a cloud computing configuration in which a single function is shared and processed jointly by multiple devices via a network.

[0256] The parking lot management system, parking lot management device, ticket issuing device, settlement device, and other terminals and devices, various screens such as settlement pages, various GUI configurations, operations by the parking lot management device, ticket issuing device, settlement device, and other devices, and various processing flows such as the generation of various information, which have been described with reference to the drawings, are merely one embodiment and can be modified as desired without departing from the spirit of the present invention. In other words, any other configurations, algorithms, etc. for implementing the present invention may be adopted.

[0257] Furthermore, the technology of the present invention is not limited to the above-described embodiments, and may be variously modified, substituted, or altered within the scope of the spirit of the technical idea. Furthermore, if the technical idea can be realized in a different way due to technological advances or other derived technologies, it may be implemented using that method. Therefore, the claims cover all embodiments that may fall within the scope of the technical idea.

[0258] In this disclosure, to facilitate understanding of the explanation, words such as "approximately," "almost," and "roughly" may be used as appropriate. However, there is no clear difference between using and not using words such as "approximately," "almost," and "roughly." In other words, in the present disclosure, concepts that define shape, size, positional relationship, state, etc., such as "center," "middle," "uniform," and "equal" are concepts that include "substantially center," "substantially central," "substantially uniform," "substantially equal," etc. For example, this also includes a state where the value is within a predetermined range (for example, a range of ±10%) based on the criteria of "perfectly centered," "perfectly central," "perfectly uniform," "perfectly equal," etc. Therefore, even if the words "roughly," "almost," "approximately," etc. are not added, the concept expressed by adding "roughly," "almost," "approximately," etc. may be included. Conversely, a state expressed by adding "roughly," "almost," "approximately," etc. does not necessarily exclude a complete state.

[0259] In this disclosure, expressions using "more than," such as "greater than A" and "smaller than A," are expressions that comprehensively include both concepts that include equivalent to A and concepts that do not include equivalent to A. For example, "greater than A" is not limited to cases that do not include equivalent to A, but also includes "A or greater." Furthermore, "smaller than A" is not limited to "less than A," but also includes "A or less." When implementing the present technology, specific settings and the like may be appropriately adopted from the concepts included in "greater than A" and "smaller than A" so as to achieve the effects described above.

[0260] It is also possible to combine at least two of the features of the present invention described above. That is, the various features described in each embodiment may be combined in any way without distinguishing between the embodiments. Furthermore, the various effects described above are merely examples and are not limiting, and other effects may also be achieved. [Industrial Applicability]

[0261] As described above, the technology of the present invention is suitable for use in relatively small pay parking lots. [Explanation of symbols]

[0262] 1. Parking lot management system 2. Mobile devices 3...Parking lot management device 6. Store 7...Store terminal 9...Parking lot 10...Ticket issuing device 11…Payment device 12…Network 87...Code image 88...Parking ticket 89...Administrator code image 91...Divided parking lot information 92…Division management information 94...Checkout page

Claims

1. a parking lot management device that manages the parking lot; a ticket issuing device that issues a parking ticket to a user of the parking lot, the parking ticket displaying a code image that stores parking ticket information including the date and time of entry of the user's vehicle and parking lot information related to the parking lot that is used for management of the parking lot by the parking lot management device; a payment device that has a function of reading the code image and, when the code image displayed on the parking ticket is read, executes payment of the parking fee based on the entry date and time stored in the code image; Equipped with When the code image is read by a portable terminal of the user having a function of reading the code image, the parking ticket information stored in the code image is transmitted from the portable terminal to the parking lot management device. Parking management system.

2. The parking lot management system according to claim 1, The parking lot information includes at least one of information on the issuance status of the parking ticket, information on the sales amount, information on change, information on fee setting, information on the status of devices installed in the parking lot, and information on invalid parking tickets. Parking management system.

3. The parking lot management system according to claim 1 or 2, The parking lot management device transmits a management-side code image storing the parking ticket information to the mobile terminal that transmitted the parking ticket information stored in the code image to the parking lot management device, the management-side code image storing the parking ticket information to which management information for managing the parking lot has been added. Parking management system.

4. The parking lot management system according to claim 3, When the settlement device reads the management side code image displayed by the mobile terminal, the settlement device executes a process related to management of the parking lot based on the management information stored in the management side code image. Parking management system.

5. The parking lot management system according to claim 4, The management information includes at least one of information regarding changes in pricing, information regarding changes in settings of devices installed in the parking lot, information regarding update programs for devices installed in the parking lot, and information regarding facilities affiliated with the parking lot. Parking management system.

6. The parking lot management system according to claim 3, The parking lot information includes information on a reading status of the management information stored in the management-side code image by the settlement device. Parking management system.

7. The parking lot management system according to claim 3, The parking lot management device transmits to the mobile terminal the management side code image storing the parking ticket information to which information regarding the payment status of the parking fee by the user has been added. Parking management system.

8. The parking lot management system according to claim 7, When the payment device reads the management side code image displayed by the mobile terminal, the payment device executes payment of the parking fee based on information about the payment status stored in the management side code image. Parking management system.

9. The parking lot management system according to claim 7, The parking lot management device executes the settlement of the parking fee based on the settlement request input via the mobile terminal, and transmits the management side code image storing the parking ticket information to which information indicating that the settlement of the parking fee has been completed has been added to the mobile terminal. Parking management system.

10. The parking lot management system according to claim 3, further comprising: a store terminal having a function of reading the code image of a facility affiliated with the parking lot; When the store terminal reads the code image or the management-side code image, it associates shopping information about the user's purchase with the parking ticket information stored in the code image or the management-side code image and transmits the shopping information to the parking lot management device; The parking lot management device transmits the management side code image storing the parking ticket information to which the shopping information has been added to the mobile terminal. Parking management system.

11. The parking lot management system according to claim 10, When the settlement device reads the management side code image displayed by the mobile terminal, the settlement device executes settlement of the parking fee based on the shopping information stored in the management side code image. Parking management system.

12. The parking lot management system according to claim 1, The ticket issuing device divides the parking lot information into a plurality of divided parking lot information, generates a plurality of code images in which each of the plurality of divided parking lot information is stored, and displays the code images on each of a plurality of parking tickets. Parking management system.

13. The parking lot management system according to claim 12, The settlement device generates new parking lot information when the parking lot management device has completed receiving each of the plurality of divided parking lot information. Parking management system.

14. The parking lot management system according to claim 3, The parking lot management device divides the management information into a plurality of divided management information, generates a plurality of management-side code images in which each of the plurality of divided management information is stored, and transmits the generated code images to each of a plurality of mobile terminals. Parking management system.

15. The parking lot management system according to claim 14, The parking lot management device generates new management information when the settlement device has completed reading each of the plurality of divided management information. Parking management system.

16. a ticket issuing device issues a parking ticket to a user using the parking lot, the parking ticket displaying a code image storing parking ticket information including the date and time of entry of the user's vehicle and parking lot information related to the parking lot used for management of the parking lot by a parking lot management device that manages the parking lot; When a payment device having a function of reading the code image reads the code image displayed on the parking ticket, the payment device executes payment of the parking fee based on the entry date and time stored in the code image, When the user's portable terminal having a function for reading the code image reads the code image, the portable terminal transmits the parking ticket information stored in the code image to the parking lot management device. Parking lot management methods.

17. A program for causing a management device for managing a parking lot, a ticket issuing device, a payment device, and a mobile terminal of a user of the parking lot to execute a parking lot management method, The parking lot management method includes: the ticket issuing device issues to the user a parking ticket on which a code image is displayed that stores parking ticket information including the date and time of entry of the user's vehicle and parking lot information related to the parking lot used for management of the parking lot by the parking lot management device; When the settlement device having a function of reading the code image reads the code image displayed on the parking ticket, the settlement device executes settlement of the parking fee based on the entry date and time stored in the code image, When the portable terminal of the user having a function of reading the code image reads the code image, the portable terminal transmits the parking ticket information stored in the code image to the parking lot management device. program.

Images