Parking discount management server and parking discount management method

Abstract

To provide a parking discount management sever that promotes use of a pay parking lot and provides the opportunity for attracting customers to affiliated stores.SOLUTION: A parking discount management server 11 comprises: a parking lot database that stores a parking lot ID of an affiliated parking lot and a store ID in association with each other; a purchase information storage unit 1124 that stores a plurality of pieces of purchase information including a user unique ID and the amount of commodities purchased by a user in a plurality of stores; and an adjustment control unit 1115 that receives an inquiry including the user unique ID and a parking lot unique ID of a pay parking lot in which the user parks a car, refers to the parking lot database 1121 to acquire a store ID corresponding to the parking lot unique ID included in the inquiry, refers to the purchase information storage unit 1124 to acquire purchase information corresponding to the user unique ID included in the inquiry, determines whether the user has purchased commodities in an affiliated store on the basis of the purchase information and the store ID, and calculates a parking fee compensation amount according to the purchase amount.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] An embodiment of the present invention relates to a parking discount management server and a parking discount management method. [Background technology]

[0002] Currently, when using parking lots for stores, including retail outlets (for example, coin parking lots), magnetic tickets or two-dimensional codes printed on paper are used to manage entry and exit from the parking lot. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-022285 A [Patent Document 2] Patent Publication No. 2021-163362 [Patent Document 3] JP 2023-089709 A Summary of the Invention [Problem to be solved by the invention]

[0004] To solve the problem that parking tickets for parking lots such as coin parking lots are magnetic or paper, or the tickets are paper, users must insert these media into a payment machine when paying the fee upon leaving the parking lot, which is inconvenient.

[0005] In addition, since stores that purchase tickets usually need to purchase tickets in units of several hundred, this places a heavy burden on the stores themselves, and since users who receive tickets also purchase tickets from stores that do not distribute tickets, there is a problem that there is little difference or advantage between stores that do not purchase tickets and stores that do not.

[0006] Furthermore, in the case of parking lots such as coin parking, there are fewer examples of parking ticket discount services being offered compared to parking lots attached to facilities. As a result, users do not perceive parking in coin parking lots as being advantageous, and this creates an opportunity loss for operators of such parking lots.

[0007] This invention was made in light of the above circumstances, and its purpose is to provide a technology that promotes the use of paid parking lots such as coin parking lots and gives affiliated stores an opportunity to attract customers. Another purpose of this invention is to provide a technology for offering discount services, such as those offered by large stores, to users of general stores. [Means for solving the problem]

[0008] In one embodiment, the parking discount management server comprises a parking database that stores the parking IDs and store IDs of affiliated parking lots with which a store is affiliated, in association with each other; a purchase information storage unit that stores multiple purchase information including the purchase amount and a user-specific ID when a user purchases a product at each of multiple stores; a receiving unit that receives an inquiry including the user-specific ID and the parking lot-specific ID of the paid parking lot where the user parks; an acquisition unit that refers to the parking lot database to acquire a store ID corresponding to the parking lot-specific ID included in the inquiry, and refers to the purchase information storage unit to acquire the purchase information corresponding to the user-specific ID included in the inquiry; a determination unit that determines whether the user made a purchase at the store based on the purchase information and the store ID; and a settlement control unit that calculates a compensation amount according to the purchase amount if it is determined that the user made the purchase. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an example of a schematic configuration of an electronic parking ticket usage system according to the present embodiment. [Diagram 2]FIG. 2 is a block diagram showing an example of a hardware configuration of the parking discount management server and a software configuration associated with the hardware configuration. [Diagram 3] FIG. 3 is a block diagram showing an example of a hardware configuration of the parking lot management server and a software configuration associated with the hardware configuration. [Figure 4] FIG. 4 is a block diagram showing an example of a hardware configuration of a roadside unit and a software configuration associated with the hardware configuration. [Diagram 5] FIG. 5 is a block diagram showing an example of a hardware configuration of the parking lot equipment and a software configuration associated with the hardware configuration. [Figure 6] FIG. 6 is a block diagram showing an example of a hardware configuration of a user device and a software configuration associated with the hardware configuration. [Figure 7] FIG. 7 is a block diagram showing an example of a hardware configuration of the vehicle-mounted device and a software configuration associated with the hardware configuration. [Figure 8] FIG. 8 is a block diagram showing an example of a hardware configuration of an electronic receipt management server and a software configuration associated with the hardware configuration. [Figure 9] FIG. 9 is a sequence diagram showing an example in which a user uses a paid parking lot to visit a store. [Figure 10] FIG. 10 is a flowchart illustrating an example of the process of step ST116 in more detail. [Figure 11] FIG. 11 is a block diagram showing an example of a hardware configuration of a parking lot management server and a software configuration associated with the hardware configuration. [Figure 12] FIG. 12 is a sequence diagram showing an example of a case where a user who uses a car share uses a paid parking lot to visit a store. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The parking discount management system, parking discount management server, and parking discount management method will be described in detail below with reference to the drawings. Note that in the following embodiments, parts with the same numbers perform the same operations, and will not be described again. For example, when there are multiple identical or similar elements, a common symbol may be used to describe each element without distinguishing between them, and a subnumber may be used in addition to the common symbol to describe each element with distinction between them.

[0011] [First embodiment] (composition) FIG. 1 is a diagram showing an example of a schematic configuration of an electronic parking ticket usage system according to the present embodiment. As shown in FIG. 1, the electronic parking ticket utilization system S according to the first embodiment includes a parking discount business operator 1, a parking lot business operator 2, a user 3, an electronic receipt service business operator 4, and a store 5.

[0012] The parking discount business operator 1 includes a parking discount management server 11. The parking lot business operator 2 includes a parking lot management server 21, a paid parking lot 22, and a roadside device 23 and parking lot equipment 24 arranged in the paid parking lot 22. The user 3 includes a user equipment 31 owned by the user 3, and an on-board device 33 arranged in a vehicle 32 used by the user 3. The electronic receipt service business operator 4 includes an electronic receipt management server 41.

[0013] The parking discount management server 11, the parking lot management server 21, the roadside device 23, the parking lot equipment 24, the user equipment 31, the in-vehicle device 33, and the electronic receipt management server 41 can communicate with each other through a network 100. Furthermore, the roadside device 23 can communicate with the in-vehicle device 33 and the parking lot equipment 24. Furthermore, although not shown, a POS (Point Of Sale) system installed in the store 5 can communicate with the electronic receipt management server 41. The roadside device 23 may be able to communicate with an external device such as a parking discount management server through the network 100.

[0014] The electronic parking ticket utilization system S may include components as necessary in addition to the components shown in FIG. 1, or specific components may be excluded from the electronic parking ticket utilization system S.

[0015] The parking discount management server 11 is a server installed at a predetermined location of a predetermined parking discount business operator 1, or at a predetermined location of a business operator that manages a cloud or the like. The parking discount management server 11 is capable of communicating with the user device 31, the parking lot device 24, the electronic receipt management server 41, the parking lot management server 21, etc., via a network 100, and transmits and receives various information. As described above, the parking discount management server 11 may be capable of communicating with the roadside device 23 via the network 100.

[0016] The parking lot management server 21 is a server managed by the parking lot operator 2. The parking lot management server 21 manages the entry and exit status of the vehicle 32 in the paid parking lot 22. Here, it is assumed that the parking lot operator 2 uses the electronic parking ticket service provided by the parking discount management server 11.

[0017] The paid parking lot 22 is a small parking lot such as a coin parking lot or a monthly parking lot. Alternatively, the paid parking lot 22 may be a parking lot attached to a large facility. In other words, the paid parking lot 22 may be a general parking lot as long as a parking fee is charged. The paid parking lot 22 is managed by the parking lot operator 2 of the paid parking lot 22 or the parking lot management server 21. Furthermore, in this embodiment, the paid parking lot 22 is an affiliated parking lot that is affiliated with the store 5. The paid parking lot 22 also includes a roadside unit 23 and parking lot equipment 24.

[0018] The roadside unit 23 is a device installed in the paid parking lot 22. The roadside unit 23 may be equipped with a device equipped with a dedicated short-range communications (DSRC) function, for example. If the entrance and exit locations of the parking lot are different, the roadside unit 23 is installed at both the entrance location and the exit location.

[0019] The parking lot equipment 24 is installed in the paid parking lot 22. The parking lot equipment 24 detects the vehicle 32 when the vehicle 32 enters or leaves the paid parking lot 22. The parking lot equipment 24 also uses a gate to control the entry and exit of the vehicle 32.

[0020] Here, the parking lot equipment 24 may not be required. For example, if the roadside device 23 can communicate with an external device such as the parking lot management server 21 and can detect the vehicle 32, it is possible to omit the parking lot equipment 24. In this case, for example, the paid parking lot 22 does not need to have a gate or the like for the vehicle 32 to enter and leave the parking lot.

[0021] The user device 31 is a terminal used by the user 3. The user device 31 may be a mobile terminal-type device such as a smartphone, a tablet terminal, or a wearable terminal.

[0022] The vehicle 32 is a vehicle 32 used by the user 3 and equipped with an on-board device 33. The vehicle 32 may be a general vehicle 32 that can use a parking lot affiliated with the store 5 described below. For example, the vehicle 32 may include a car sharing vehicle 32 in which multiple people share the vehicle 32, or may include a vehicle 32 whose owner has changed, such as a used car.

[0023] The vehicle-mounted device 33 is, for example, a device that allows the use of an ETC system by inserting an ETC card therein.

[0024] The electronic receipt management server 41 is a server installed at a predetermined location of the electronic receipt service provider 4. The electronic receipt management server 41 provides, for example, an electronic receipt application to the user 3. The user 3 can receive an electronic receipt when purchasing a product at a store 5 using an application in which the electronic receipt application is installed.

[0025] The store 5 is a small store 5 such as a retail store, or a store 5 in a large facility such as a supermarket or a shopping mall. As described above, the store 5 is affiliated with the paid parking lot 22. For example, when the user 3 purchases a product, the store 5 compensates the user 3 who parks the vehicle 32 in the affiliated paid parking lot 22 for a portion of the parking fee.

[0026] FIG. 2 is a block diagram showing an example of the hardware configuration of the parking discount management server 11 and the software configuration associated with the hardware configuration. First, the hardware configuration of the parking discount management server 11 will be described in detail. The parking discount management server 11 includes a control unit 111, a storage unit 112, a communication interface 113, an input / output interface 114, an input unit 115, and an output unit 116. The control unit 111, the storage unit 112, the communication interface 113, and the input / output interface 114 are communicatively connected to one another via a bus. The input / output interface 114 is also communicatively connected to the input unit 115 and the output unit 116.

[0027] The control unit 111 of the parking discount management server 11 controls the parking discount management server 11. The control unit 111 includes a hardware processor such as a central processing unit (CPU: Central Processing Unit).

[0028] The storage unit 112 is a storage medium. The storage unit 112 is configured by combining a non-volatile memory that can be written and read at any time, such as a hard disk drive (HDD) or a solid state drive (SSD), a non-volatile memory such as a read only memory (ROM), and a volatile memory such as a random access memory (RAM). The storage unit 112 has a program storage area and a data storage area in its storage area. The program storage area stores application programs required for executing various processes, in addition to an OS and middleware. The storage unit 112 also stores various information such as a membership number list of the electronic parking ticket application, information about members, the fee for the paid parking lot 22, discount conditions, etc. Here, the information about the member may include the name, address, telephone number, and credit card information of the user 3.

[0029] The communication interface 113 includes one or more wired or wireless communication modules. For example, the communication interface 113 includes a communication module that connects to the parking lot management server 21, the roadside device 23, the user device 31, and the electronic receipt management server 41 by wire or wirelessly through a network 100 including a LAN or the Internet. The communication interface 113 may be a general communication interface as long as it can communicate with the parking lot management server 21, the roadside device 23, the user device 31, and the electronic receipt management server 41 under the control of the control unit 111 and transmit and receive various information.

[0030] The input / output interface 114 is an interface that enables transmission and reception of information between the input unit 115 and the output unit 116. Here, the input / output interface 114 may be a part of the communication interface 113. In other words, the input / output interface 114 may include a communication module that is connected to the input unit 115 and the output unit 116 in a wired or wireless manner.

[0031] The input unit 115 is, for example, an input detection sheet that employs an electrostatic or pressure method and is arranged on the display screen of the display device, and outputs a signal corresponding to the touch position of the manager of the parking discount management server 11 to the control unit 111 via the input / output interface 114. For example, the input unit 115 and the output unit 116 may be a touch screen in which input and output are integrated. That is, the input unit 115 may receive input of necessary information by the manager of the parking discount management server 11 touching a button or the like displayed on the touch screen, and output a signal corresponding to the received information to the control unit 111. The input unit 115 may also include, for example, a keyboard, a pointing device, or the like, for the manager of the parking discount management server 11 to input instructions to the parking discount management server 11.

[0032] The output unit 116 is a display device using, for example, a liquid crystal, an organic electroluminescence (EL), or the like, and displays images and messages according to signals input from the input / output interface 114 .

[0033] Next, the software configuration of the parking discount management server 11 will be described in detail. The control unit 111 includes a communication control unit 1111 , a registration control unit 1112 , a ticket issuance control unit 1113 , an advertisement control unit 1114 , and a settlement control unit 1115 .

[0034] The communication control unit 1111 is a control unit that transmits and receives various information to and from the parking lot management server 21, the roadside device 23, the user device 31, the electronic receipt management server 41, etc., through the communication interface 113. For example, the communication control unit 1111 receives a ticket issuance request including a vehicle-specific ID and the like from the user device 31. The communication control unit 1111 also transmits an inquiry request to the parking lot management server 21 and receives the inquiry result.

[0035] The registration control unit 1112 is a control unit used when the store 5 registers a service contract or the like with the operator of the parking discount management server 11. Furthermore, the registration control unit 1112 is a control unit used when the user 3 registers user information when using the electronic parking ticket application.

[0036] The ticket issuance control unit 1113 is a control unit that controls the issuance of an electronic parking ticket when the user 3 uses the electronic parking ticket. For example, the ticket issuance control unit 1113 controls the issuance of an electronic parking ticket in response to an issuance request from the user device 31.

[0037] The advertisement control unit 1114 is a control unit used when advertising to users or registering coupons, etc., when the store 5 enters into a service contract with the operator of the parking discount management server 11. Furthermore, the advertisement control unit 1114 sets the delivery order and delivery frequency of advertisements or coupons, etc., after the vehicle 32 used by the user 3 enters the paid parking lot 22.

[0038] The settlement control unit 1115 is a control unit that determines the compensation amount, etc., to be paid by the store 5 out of the parking fee for the paid parking lot 22, according to the price of the product purchased by the user 3 at the store 5. The method of determining the compensation amount, etc., will be described in detail later.

[0039] The storage unit 112 includes a parking lot database 1121 , an advertisement database 1122 , a user information database 1123 , and a purchase information storage unit 1124 .

[0040] The parking lot database 1121 is a database for storing various information associated with each of the multiple paid parking lots 22. For example, the parking lot database 1121 is linked to the store unique ID of the store 5 and stores information including the parking lot unique IDs of the paid parking lots 22 affiliated with the store 5. Furthermore, the parking lot database 1121 stores information on the vehicles 32 parked in the paid parking lots 22.

[0041] The advertisement database 1122 is a database that stores information that the store 5 wants to advertise to the user 3. For example, the advertisement database 1122 stores a store-specific ID and an advertisement or coupon of the store 5 corresponding to the store-specific ID, in association with the parking lot-specific ID.

[0042] The user information database 1123 is a database that stores information related to the user 3, including the user unique ID of the user device 31. For example, the user information database 1123 stores the vehicle unique ID and the like in association with the user unique ID. Furthermore, the user information database 1123 may store the user unique ID in association with a membership number used in an electronic receipt.

[0043] FIG. 3 is a block diagram showing an example of the hardware configuration of the parking lot management server 21 and the software configuration associated with the hardware configuration. First, the hardware configuration of the parking lot management server 21 will be described in detail. The parking lot management server 21 includes a control unit 211, a storage unit 212, a communication interface 213, an input / output interface 214, an input unit 215, and an output unit 216. The control unit 211, the storage unit 212, the communication interface 213, and the input / output interface 214 are communicatively connected to each other via a bus. The input / output interface 214 is communicatively connected to the input unit 215 and the output unit 216.

[0044] The control unit 211 of the parking lot management server 21 controls the parking lot management server 21. The control unit 211 includes a hardware processor such as a CPU.

[0045] The storage unit 212 is a storage medium. The storage unit 212 is configured by combining a non-volatile memory such as an HDD or SSD that can be written and read at any time, a non-volatile memory such as a ROM, and a volatile memory such as a RAM. The storage unit 212 has a program storage area and a data storage area in its storage area. The program storage area stores application programs necessary for executing various processes in addition to the OS and middleware.

[0046] The communication interface 213 includes one or more wired or wireless communication modules. For example, the communication interface 213 includes a communication module that wirelessly connects to an external device such as the parking discount management server 11 through the network 100 including a LAN or the Internet. The communication interface 213 may be a general communication interface as long as it can communicate with the external device under the control of the control unit 211 and send and receive various information.

[0047] The input / output interface 214 is an interface that enables transmission and reception of information between the input unit 215 and the output unit 216. Here, the input / output interface 214 may be a part of the communication interface 213. In other words, the input / output interface 214 may include a communication module that is connected to the input unit 215 and the output unit 216 in a wired or wireless manner.

[0048] The input unit 215 is, for example, an input detection sheet that employs an electrostatic or pressure method and is arranged on the display screen of the display device, and outputs a signal corresponding to the touch position of the manager of the electronic receipt management server 41 to the control unit 211 via the input / output interface 214. For example, the input unit 215 and the output unit 216 may be a touch screen in which input and output are integrated. That is, the input unit 215 may receive input of necessary information by the manager of the parking lot management server 21 touching a button or the like displayed on the touch screen, and output a signal corresponding to the received information to the control unit 211. The input unit 215 may also include, for example, a keyboard, a pointing device, or the like for the manager of the parking lot management server 21 to input instructions to the parking lot management server 21.

[0049] The output unit 216 is a display device using, for example, a liquid crystal, an organic electroluminescence (EL), or the like, and displays images and messages according to signals input from the input / output interface 214 .

[0050] Next, the software configuration of the parking lot management server 21 will be described in detail. The control unit 211 includes a communication control unit 2111 , a parking status control unit 2112 , an inquiry control unit 2113 , and a parking fee control unit 2114 .

[0051] The communication control unit 2111 is a control unit for receiving various information between external devices. For example, the communication control unit 2111 receives entrance information and exit information from the roadside unit 23 installed in the paid parking lot 22. The entrance information includes at least a vehicle-specific ID, a parking lot-specific ID, an entrance time, etc. Furthermore, the exit information includes at least a vehicle-specific ID, a parking lot-specific ID, an exit time, etc. Furthermore, the communication control unit 2111 transmits an inquiry response generated in response to an inquiry request from the parking discount management server 11.

[0052] The entry / exit status control unit 2112 is a control unit that controls which paid parking lot 22 each vehicle 32 is entering. The entry / exit status control unit 2112 stores the received entry information or exit information in the entry / exit management database.

[0053] The inquiry control unit 2113 is a control unit that controls inquiries based on inquiry requests received from the parking discount management server 11. The inquiry method performed by the inquiry control unit 2113 will be described in detail later.

[0054] The parking fee control unit 2114 is a control unit that controls the parking fee for the vehicle 32 parked in each of the paid parking lots 22. The parking fee control unit 2114 calculates the parking fee based on the entry time included in the entry information and the exit time included in the exit information. The parking fee control unit 2114 is also used when billing the store 5 for parking fee compensation based on the parking fee compensation amount calculated by the parking discount management server 11.

[0055] The storage unit 212 includes an entry / exit management database 2121. The entry / exit management database 2121 is a database used to store entry information, exit information, etc. The entry / exit management database 2121 may further store parking fees by hour for each of the paid parking lots 22.

[0056] FIG. 4 is a block diagram showing an example of a hardware configuration of the roadside unit 23 and a software configuration associated with the hardware configuration. First, the hardware configuration of the roadside unit 23 will be described in detail. The roadside unit 23 includes a control unit 231, a storage unit 232, a communication interface 233, an input / output interface 234, an input unit 235, and an output unit 236. The control unit 231, the storage unit 232, the communication interface 233, and the input / output interface 234 are communicatively connected to each other via a bus. The input / output interface 234 is communicatively connected to the input unit 235 and the output unit 236.

[0057] The control unit 231 of the roadside unit 23 controls the roadside unit 23. The control unit 231 includes a hardware processor such as a CPU.

[0058] The storage unit 232 is a storage medium. The storage unit 232 is configured by combining a non-volatile memory that can be written and read at any time, such as an HDD or SSD, a non-volatile memory such as a ROM, and a volatile memory such as a RAM. The storage unit 232 has a program storage area and a data storage area in its storage area. The program storage area stores application programs required to execute various processes, in addition to an OS and middleware. The storage unit 232 stores various information such as a roadside device ID, roadside device position information, and key information for encrypting the roadside device information.

[0059] The communication interface 233 includes one or more wired or wireless communication modules. For example, the communication interface 233 includes a communication module that wirelessly connects to the in-vehicle device 33. The communication interface 233 further includes a communication module that wiredly or wirelessly connects to the parking lot equipment 24. The communication interface 233 may be a general communication interface as long as it can communicate between the in-vehicle device 33 and the parking lot equipment 24 under the control of the control unit 231 and transmit and receive various information.

[0060] The input / output interface 234 is an interface that enables transmission and reception of information between the input unit 235 and the output unit 236. Here, the input / output interface 234 may be a part of the communication interface 233. In other words, the input / output interface 234 may include a communication module that is connected to the input unit 235 and the output unit 236 in a wired or wireless manner.

[0061] The input unit 235 is, for example, an input detection sheet that employs an electrostatic or pressure method and is arranged on the display screen of the display device, and outputs a signal corresponding to a touch position of the manager of the roadside unit 23 to the control unit 231 via the input / output interface 234. For example, the input unit 235 and the output unit 236 may be a touch screen in which input and output are integrated. That is, the input unit 235 may receive input of necessary information by the manager of the roadside unit 23 touching a button or the like displayed on the touch screen, and output a signal corresponding to the received information to the control unit 231. The input unit 235 may also include, for example, a keyboard, a pointing device, or the like for the manager of the roadside unit 23 to input instructions to the roadside unit 23.

[0062] The output unit 236 is a display device using, for example, a liquid crystal, an organic electroluminescence (EL), or the like, and displays images and messages according to signals input from the input / output interface 234 .

[0063] Next, the software configuration of the roadside unit 23 will be described in detail. The control unit 231 includes a communication control unit 2311 and a signal control unit 2312 .

[0064] The communication control unit 2311 receives an acquisition instruction from the parking lot equipment 24, transmits an in-vehicle device information request to the in-vehicle device 33, and receives the in-vehicle device information from the in-vehicle device 33.

[0065] The signal control unit 2312 generates an in-vehicle unit information request based on the received acquisition instruction. The signal control unit 2312 generates roadside unit information including, in addition to the received roadside unit information, the identification information of the roadside unit stored in the storage unit 232, the roadside unit position information, and date and time information indicating the date and time when the vehicle 32 entered or left the paid parking lot 22. Here, the roadside unit position information may be information indicating the position of the roadside unit, or may be the roadside unit management number. The signal control unit 2312 may encrypt the roadside unit information using a general method.

[0066] FIG. 5 is a block diagram showing an example of the hardware configuration of the parking lot equipment 24 and the software configuration associated with the hardware configuration. First, the hardware configuration of the parking lot equipment 24 will be described in detail. The parking lot equipment 24 includes a control unit 241, a memory unit 242, a communication interface 243, an input / output interface 244, an input unit 245, an output unit 246, a vehicle detector 247, a gate 248, and a ticket issuing / payment unit 249. The control unit 241, the memory unit 242, the communication interface 243, and the input / output interface 244 are communicatively connected to one another via a bus. The input / output interface 244 is also communicatively connected to the input unit 245, the output unit 246, the vehicle detector 247, the gate 248, and the ticket issuing / payment unit 249.

[0067] The control unit 241 of the parking lot equipment 24 controls the parking lot equipment 24. The control unit 241 includes a hardware processor such as a central processing unit (CPU).

[0068] The storage unit 242 is a storage medium. The storage unit 242 is configured by combining a non-volatile memory that can be written and read at any time, such as an HDD or SSD, a non-volatile memory such as a ROM, and a volatile memory such as a RAM. The storage unit 242 has a program storage area and a data storage area in its storage area. The program storage area stores application programs required to execute various processes, in addition to an OS and middleware. The storage unit 242 also stores parking lot equipment identification information that identifies the parking lot equipment 24.

[0069] The communication interface 243 includes one or more wired or wireless communication modules. For example, the communication interface 243 includes a communication module that wirelessly connects to the parking discount management server 11 via the network 100, which includes a LAN or the Internet. The communication interface 243 further includes a communication module that connects to the roadside unit 23 via a wired or wireless connection. The communication interface 243 may be a general communication interface as long as it can communicate with the roadside unit 23 and the parking discount management server 11 under the control of the control unit 241 and send and receive various information.

[0070] The input / output interface 244 is an interface that enables transmission and reception of information between the input unit 245 and the output unit 246. Here, the input / output interface 244 may be a part of the communication interface 243. That is, the input / output interface 244 may include a communication module that is connected to the input unit 245, the output unit 246, the vehicle detector 247, the gate 248, and the ticket issuing / payment unit 249 by wire or wirelessly.

[0071] The input unit 245 is, for example, an input detection sheet that employs an electrostatic or pressure method and is arranged on the display screen of the display device, and outputs a signal corresponding to the touch position of the manager of the parking lot equipment 24 to the control unit 241 via the input / output interface 244. For example, the input unit 245 and the output unit 246 may be a touch screen in which input and output are integrated. That is, the input unit 245 may receive input of necessary information by the manager touching a button or the like displayed on the touch screen, and output a signal corresponding to the received information to the control unit 241. The input unit 245 may also include, for example, a keyboard, a pointing device, or the like for the manager of the parking lot equipment 24 to input instructions to the parking lot equipment 24.

[0072] The output unit 246 is a display device using, for example, a liquid crystal, an organic electroluminescence (EL), or the like, and displays images and messages according to signals input from the input / output interface 244. The output unit 246 may also include a speaker. The output unit 246 may output audio to the driver of the vehicle 32 (the user 3 of the user device 31) according to audio information received from the signal control unit 2413.

[0073] The vehicle detector 247 detects that the vehicle 32 is approaching the paid parking lot 22. For example, the vehicle detector 247 may detect the vehicle 32 by a laser-type or loop-type detection method. For example, the laser-type vehicle detector 247 irradiates a laser light under the control of the control unit 241 and detects the reflected light of the laser light reflected by an object such as the vehicle 32. Also, for example, the loop-type vehicle detector 247 includes a loop coil embedded in a road or the like before entering the entrance to the paid parking lot 22. The vehicle detector 247 detects the vehicle 32 based on a change in inductance when the vehicle 32 passes over the loop coil.

[0074] The gate 248 is installed at the entrance and exit of the paid parking lot 22. Under the control of the gate control unit 2414, the gate 248 is opened and closed to control the passage (entry or exit) of the vehicle 32 through the paid parking lot 22. For example, when it is necessary to stop the vehicle 32 or when the passage (entry or exit) of the vehicle 32 is prohibited, the gate 248 is closed under the control of the gate control unit 2414 to physically block the passage of the vehicle 32. When the passage (entry or exit) of the vehicle 32 is permitted, the gate 248 is opened under the control of the gate control unit 2414 to permit the passage of the vehicle 32.

[0075] The ticket issuing / payment unit 249 may issue a paper parking ticket with a two-dimensional code printed on it in response to an issuance instruction from the ticket issuing control unit 2415. The ticket issuing / payment unit 249 may also include a cash slot or a credit card slot for the user 3 to pay the parking fee. The ticket issuing / payment unit 249 may output a signal to the ticket issuing / payment unit 249 indicating that the user 3 has paid the parking fee.

[0076] When the paid parking lot 22 manages the entry and exit of vehicles using only electronic parking tickets, the parking lot equipment 24 does not need to include the gate 248, the ticket issuing and payment unit 249, etc. Although not shown in Fig. 5, the parking lot equipment 24 may also include a camera for acquiring the vehicle number of the vehicle 32 (i.e., the vehicle unique ID).

[0077] Next, the software configuration of the parking lot equipment 24 will be described in detail. The control unit 241 includes a communication control unit 2411 , a vehicle detection control unit 2412 , a signal control unit 2413 , a gate control unit 2414 , a ticket issuance control unit 2415 , and a payment control unit 2416 .

[0078] The communication control unit 2411 transmits an acquisition instruction to the roadside unit 23, and transfers the roadside unit information to the parking discount management server 11. The communication control unit 2411 may also cause the storage unit 242 to store the roadside unit information.

[0079] The vehicle detection control unit 2412 detects the vehicle 32 using the vehicle detector 247. Then, the vehicle detection control unit 2412 may output a detection signal indicating that a vehicle has been detected to the signal control unit 2413.

[0080] The signal control unit 2413 may generate an acquisition instruction for acquiring on-board device information from the on-board device 33 based on the detection signal, and output the acquisition instruction to the communication control unit 2411. Furthermore, the signal control unit 2413 may output audio information including the guidance instruction to a speaker included in the output unit 246 based on the guidance instruction.

[0081] The gate control unit 2414 controls the gate 248. For example, the gate control unit 2414 opens the gate 248 based on a gate opening instruction, and allows the vehicle 32 to pass.

[0082] The ticket issuance control unit 2415 is a control unit that controls the issuance of a parking ticket on paper to a user 3 who uses the paid parking lot 22. In this embodiment, the ticket issuance method may be a general method, and a detailed description thereof will be omitted here.

[0083] The payment control unit 2416 is a control unit used by the user 3 who has used the paid parking lot 22 when paying the parking fee for the paid parking lot 22 by paper medium. Note that the payment method may be any common method, and detailed explanation will be omitted here.

[0084] As described above, when the toll parking lot 22 manages the entry and exit of the vehicle 32 using only electronic parking tickets, the control unit 231 does not need to include the gate control unit 2414, the ticket issuing control unit 2415, the payment control unit 2416, and the like.

[0085] FIG. 6 is a block diagram showing an example of a hardware configuration of the user device 31 and a software configuration associated with the hardware configuration. First, the hardware configuration of the user device 31 will be described in detail. The user device 31 includes a control unit 311, a storage unit 312, a communication interface 313, an input / output interface 314, an input unit 315, and an output unit 316. The control unit 311, the storage unit 312, the communication interface 313, and the input / output interface 314 are communicatively connected to each other via a bus. The input / output interface 314 is communicatively connected to the input unit 315 and the output unit 316.

[0086] The control unit 311 of the user device 31 controls the user device 31. The control unit 311 includes a hardware processor such as a central processing unit (CPU).

[0087] The storage unit 312 is a storage medium. The storage unit 312 is configured by combining a non-volatile memory such as an HDD or SSD that can be written and read at any time, a non-volatile memory such as a ROM, and a volatile memory such as a RAM. The storage unit 312 has a program storage area and a data storage area in its storage area. The program storage area stores application programs required for executing various processes in addition to an OS (Operating System) and middleware. The storage unit 312 may also store a pre-registered vehicle-specific ID and a membership number of an electronic parking ticket application. The storage unit 312 may also store a pre-registered user-specific ID or a membership number for an electronic receipt.

[0088] The user unique ID may be any information that can identify the user 3, such as an email address, a name, a telephone number, or a terminal ID. The user unique ID further includes a membership number. The vehicle unique ID will be described in detail later.

[0089] The membership number is not limited to the membership number of the user 3, but may include family membership numbers used by the user's ten family members.

[0090] The communication interface 313 includes one or more wired or wireless communication modules. For example, the communication interface 313 includes a communication module that wirelessly connects to the parking discount management server 11 via the network 100, which includes a LAN or the Internet. The communication interface 313 may be a general communication interface as long as it can communicate with the parking discount management server 11 under the control of the control unit 311 and send and receive various information.

[0091] The input / output interface 314 is an interface that enables transmission and reception of information between the input unit 315 and the output unit 316. Here, the input / output interface 314 may be a part of the communication interface 313. In other words, the input / output interface 314 may include a communication module that is connected to the input unit 315 and the output unit 316 in a wired or wireless manner.

[0092] The input unit 315 is, for example, an input detection sheet that employs an electrostatic or pressure method and is arranged on the display screen of the display device, and outputs a signal corresponding to the touch position of the user 3 to the control unit 311 via the input / output interface 314. For example, the input unit 315 and the output unit 316 may be a touch screen in which input and output are integrated. That is, the input unit 315 may receive input of necessary information by the user 3 touching a button or the like displayed on the touch screen, and output a signal corresponding to the received information to the control unit 311. The input unit 315 may also include, for example, a keyboard, a pointing device, or the like for the user 3 of the user device 31 to input instructions to the user device 31.

[0093] The output unit 316 is a display device that uses, for example, liquid crystal, organic EL (Electro Luminescence), or the like, and displays images and messages according to signals input from the input / output interface 314 .

[0094] Next, the software configuration of the user device 31 will be described in detail. The control unit 311 includes a communication control unit 3111 , an electronic parking ticket application control unit 3112 , and an electronic receipt application control unit 3113 .

[0095] The communication control unit 3111 is a control unit that transmits and receives various information through the communication interface 313. For example, the communication control unit 3111 transmits a vehicle unique ID or a user unique ID, etc. to the parking discount management server 11, etc.

[0096] The electronic parking ticket application control unit 3112 is a control unit that controls an electronic parking ticket application used in the pay parking lot 22. For example, the electronic parking ticket application control unit 3112 controls the output unit 316 to display the electronic parking ticket application.

[0097] The electronic receipt application control unit 3113 is a control unit that controls an electronic receipt application used in the store 5 etc. For example, when the user 3 purchases a product at the store 5, the electronic receipt application control unit 3113 controls the output unit 316 to display code information (one-dimensional code or two-dimensional code) including a user unique ID or a membership number for an electronic receipt.

[0098] FIG. 7 is a block diagram showing an example of a hardware configuration of the vehicle-mounted device 33 and a software configuration associated with the hardware configuration. First, the hardware configuration of the vehicle-mounted device 33 will be described in detail. The in-vehicle device 33 includes a control unit 331, a storage unit 332, a communication interface 333, an input / output interface 334, an input unit 335, and an output unit 336. The control unit 331, the storage unit 332, the communication interface 333, and the input / output interface 334 are communicatively connected to each other via a bus. The input / output interface 334 is communicatively connected to the input unit 335 and the output unit 336.

[0099] The control unit 331 of the on-vehicle device 33 controls the on-vehicle device 33. The control unit 331 includes a hardware processor such as a CPU.

[0100] The storage unit 332 is a storage medium. The storage unit 332 is configured by combining a non-volatile memory such as an HDD or SSD that can be written and read at any time, a non-volatile memory such as a ROM, and a volatile memory such as a RAM. The storage unit 332 has a program storage area and a data storage area in its storage area. The program storage area stores application programs required to execute various processes in addition to an OS and middleware. The storage unit 332 may also store various information such as an on-board device ID, license plate information, vehicle type, vehicle weight, vehicle length, and vehicle height.

[0101] The communication interface 333 includes one or more wireless communication modules. For example, the communication interface 333 includes a communication module that wirelessly connects to the roadside unit 23. The communication interface 333 may be a general communication interface as long as it can communicate with the roadside unit 23 under the control of the control unit 331 and transmit and receive various information.

[0102] The input / output interface 334 is an interface that enables transmission and reception of information between the input unit 335 and the output unit 336. Here, the input / output interface 334 may be a part of the communication interface 333. In other words, the input / output interface 334 may include a communication module that is connected to the input unit 335 and the output unit 336 in a wired or wireless manner.

[0103] The input unit 335 is, for example, an input detection sheet that employs an electrostatic or pressure method and is arranged on the display screen of the display device, and outputs a signal corresponding to the touch position of the user 3 to the control unit 331 via the input / output interface 334. For example, the input unit 335 and the output unit 336 may include a touch screen in which input and output are integrated. For example, the input unit 335 may receive input of necessary information by the user 3 touching a button or the like displayed on the touch screen, and output a signal corresponding to the received information to the control unit 331. The input unit 335 also includes a card insertion unit into which a settlement card such as an ETC card can be inserted. When an ETC card is inserted into the card insertion unit, the control unit 331 can read various information such as an ETC card ID stored in the ETC card.

[0104] The output unit 336 is a display device using, for example, a liquid crystal, an organic electroluminescence (EL), or the like, and displays images and messages according to signals input from the input / output interface 334. The output unit 336 also has a speaker, etc. For example, when an ETC card is not inserted in the card insertion portion, when information cannot be read from the ETC card, or the like, the output unit 336 can inform the user 3 by voice.

[0105] Next, the software configuration of the vehicle-mounted device 33 will be described in detail. The control unit 331 includes a communication control unit 3311 and an in-vehicle information generating unit 3312 .

[0106] The communication control unit 3311 receives an on-board unit information request from the roadside unit 23 via the communication interface 333, and transmits on-board unit information to the roadside unit 23 in response to the on-board unit information request.

[0107] The vehicle-mounted device information generating unit 3312 generates the vehicle-mounted device information in response to the vehicle-mounted device information request. Here, the vehicle-mounted device information may include, for example, the vehicle-mounted device information stored in the storage unit 332 described later, the ETC card ID of the ETC card inserted into the vehicle-mounted device 33, the ETC card number, and the expiration date of the ETC card. The vehicle-mounted device information also includes at least a vehicle-specific ID. The vehicle-specific ID may be at least one of the vehicle-mounted device ID (for example, ASL-ID or WCN), the license plate information, and the ETC card ID. The vehicle-specific ID may be any information that can uniquely identify the vehicle 32.

[0108] FIG. 8 is a block diagram showing an example of a hardware configuration of the electronic receipt management server 41 and a software configuration associated with the hardware configuration. First, the hardware configuration of the electronic receipt management server 41 will be described in detail. The electronic receipt management server 41 includes a control unit 411, a storage unit 412, a communication interface 413, an input / output interface 414, an input unit 415, and an output unit 416. The control unit 411, the storage unit 412, the communication interface 413, and the input / output interface 414 are communicatively connected to each other via a bus. The input / output interface 414 is also communicatively connected to the input unit 415 and the output unit 416.

[0109] The control unit 411 of the electronic receipt management server 41 controls the electronic receipt management server 41. The control unit 411 includes a hardware processor such as a CPU.

[0110] The storage unit 412 is a storage medium. The storage unit 412 is configured by combining a nonvolatile memory such as an HDD or SSD that can be written and read at any time, a nonvolatile memory such as a ROM, and a volatile memory such as a RAM. The storage unit 412 has a program storage area and a data storage area in its storage area. The program storage area stores application programs required to execute various processes in addition to the OS and middleware.

[0111] The communication interface 413 includes one or more wired or wireless communication modules. For example, the communication interface 413 includes a communication module that wirelessly connects to an external device including the parking discount management server 11 and the like via the network 100 including a LAN or the Internet and the like. The communication interface 413 may be a general communication interface as long as it can communicate with the external device under the control of the control unit 411 and transmit and receive various information.

[0112] The input / output interface 414 is an interface that enables transmission and reception of information between the input unit 415 and the output unit 416. Here, the input / output interface 414 may be a part of the communication interface 413. In other words, the input / output interface 414 may include a communication module that is connected to the input unit 415 and the output unit 416 in a wired or wireless manner.

[0113] The input unit 415 is, for example, an input detection sheet that employs an electrostatic method or a pressure method and is arranged on the display screen of the display device, and outputs a signal corresponding to a touch position of the manager of the electronic receipt management server 41 to the control unit 411 via the input / output interface 414. For example, the input unit 415 and the output unit 416 may be a touch screen in which input and output are integrated. That is, the input unit 415 may receive input of necessary information by the manager of the electronic receipt management server 41 touching a button or the like displayed on the touch screen, and output a signal corresponding to the received information to the control unit 411. The input unit 415 may also include, for example, a keyboard, a pointing device, or the like for the manager of the electronic receipt management server 41 to input instructions to the electronic receipt management server 41.

[0114] The output unit 416 is a display device using, for example, a liquid crystal, an organic electroluminescence (EL), or the like, and displays images and messages according to signals input from the input / output interface 414 .

[0115] Next, the software configuration of the electronic receipt management server 41 will be described in detail. The control unit 411 includes a communication control unit 4111 and a purchase information control unit 4112 .

[0116] The communication control unit 4111 is an interface for receiving various information from an external device. For example, the communication control unit 4111 receives POS information from a POS (Point Of Sale) installed in each store 5. For example, the POS information includes a user-specific ID of the user 3 who uses the electronic receipt, a product purchased by the user, a store-specific ID, and the like. Furthermore, the communication control unit 4111 transmits purchase information to the parking discount management server 11. The purchase information includes at least the POS information.

[0117] The purchase information control unit 4112 is a control unit that generates purchase information based on POS information. For example, the purchase information control unit 4112 generates purchase information based on POS information received from the POS of each store 5. Furthermore, the purchase information control unit 4112 stores the generated purchase information in the purchase information storage unit 4121.

[0118] The storage unit 412 includes a purchase information storage unit 4121. The purchase information storage unit 4121 is a storage unit that stores purchase information generated by the purchase information control unit 4112. The purchase information storage unit 4121 may also store POS information.

[0119] In addition, when the store 5 (POS) outputs a receipt on paper, the user 3 can take a picture of the receipt using the camera of the user device 31 and transmit the purchase information based on the captured image to the parking discount management server 11. In such a case, the electronic receipt management server 41 may not be a required component.

[0120] (operation) First, it is assumed that a contract for a usage partnership has been concluded between the parking lot operator 2 and the store 5. Furthermore, it is assumed that the parking lot operator 2 uses an electronic parking ticket (using an electronic parking ticket application) provided by the parking discount management server 11. Furthermore, it is assumed that the electronic parking ticket application and the electronic receipt application have already been installed in the user device 31, and that the advance registration process has been completed. It is further assumed that the user 3 has consented to the linkage of the electronic parking ticket application and the electronic receipt application. As a result, it is assumed that the user information database 1123 of the parking discount management server 11 stores the vehicle unique ID and the membership number linked to the user unique ID.

[0121] FIG. 9 is a sequence diagram showing an example in which the user 3 uses the paid parking lot 22 to visit the store 5. In FIG. The operation of this sequence diagram is realized by the control unit 111 of the parking discount management server 11, the control unit 211 of the parking lot management server 21, the control unit 231 of the roadside unit 23, the control unit 311 of the user equipment 31, the control unit 311 of the in-vehicle unit 33, and the control unit 411 of the electronic receipt management server 41 reading and executing programs stored in the memory unit 112, memory unit 212, memory unit 232, memory unit 312, memory unit 332, and memory unit 412, respectively.

[0122] This sequence starts when the user 3 uses the vehicle 32 to enter the paid parking lot 22. It is assumed that the paid parking lot 22 is a parking lot with which the store 5 has an agreement.

[0123] In step ST101, the vehicle 32 equipped with the on-board device 33 enters the paid parking lot 22. For example, the vehicle detection control unit 2412 of the parking lot equipment 24 controls the vehicle detector 247 to detect the vehicle 32. Then, the communication control unit 2411 transmits an acquisition instruction to the roadside device 23.

[0124] In step ST102, the communication control unit 3311 transmits the on-board device information to the road-side device 23. First, the signal control unit 2312 generates an on-board device information request based on the received acquisition instruction. The communication control unit 2311 transmits the generated on-board device information request to the on-board device 33.

[0125] The vehicle-mounted device information generating unit 3312 that has received the vehicle-mounted device information request generates vehicle-mounted device information including the vehicle unique ID, the ETC card number, the expiration date of the ETC card, etc. Then, the communication control unit 3311 transmits the vehicle-mounted device information to the roadside device 23 via the communication interface 333.

[0126] In step ST103, the roadside unit 23 transmits the entry information to the parking lot management server 21. The signal control unit 2312 that has received the on-board unit information generates entry information including the on-board unit information, a parking lot unique ID that identifies the paid parking lot 22, the entry time of the vehicle 32, and the like. The communication control unit 2311 transmits the generated entry information to the parking lot management server 21 via the communication interface 233. The entry / exit status control unit 2112 of the parking lot management server 21 stores the received entry information in the entry / exit management database 2121.

[0127] Furthermore, the entry / exit status control unit 2112 may transmit a gate open instruction or the like to the parking lot equipment 24. The gate control unit 2414 opens the gate 248 in response to the instruction. This allows the user 3 to park the vehicle 32 in a parking space in the paid parking lot 22. At this time, the parking lot equipment 24 may launch an electronic parking ticket application and output a sound or video prompting the user to press an electronic parking ticket issuance request button.

[0128] In addition, in steps ST101 to ST103, the in-vehicle device 33 and the roadside device 23 are not required components. Instead of communication between the roadside device 23 and the in-vehicle device 33, a vehicle-specific ID (vehicle number) may be acquired by a camera provided in the parking lot equipment 24. In this case, the signal control unit 2413 of the parking lot equipment 24 may generate entry information, and the communication control unit 2411 may transmit the entry information to the parking discount management server 11.

[0129] In step ST104, the electronic parking ticket application control unit 3112 generates an electronic parking ticket issuance request. In response to the notification from the parking lot equipment 24, the user 3 launches the electronic parking ticket application and presses the electronic parking ticket issuance request button. The electronic parking ticket application control unit 3112 detects that the electronic parking ticket issuance request button has been pressed and generates an electronic parking ticket issuance request including a user unique ID and a vehicle unique ID. The electronic parking ticket issuance request may include location information of the user equipment 31 acquired by the control unit 111.

[0130] In step ST105, the communication control unit 3111 transmits an electronic parking ticket issuance request. The communication control unit 3111 transmits the electronic parking ticket issuance request generated by the electronic parking ticket application control unit 3112 to the parking discount management server 11 via the communication interface 313.

[0131] In step ST106, the ticket issuance control unit 1113 of the parking discount management server 11 and the inquiry control unit 2113 of the parking lot management server 21 perform a user inquiry. The ticket issuance control unit 1113 generates an inquiry request including the vehicle unique ID included in the received electronic parking ticket issuance request. The communication control unit 1111 transmits the generated inquiry request to the parking lot management server 21 through the communication interface 113.

[0132] The inquiry control unit 2113 inquires whether the vehicle unique ID included in the received inquiry request is stored in the entry / exit management database 2121. If the vehicle unique ID included in the inquiry request is stored in the entry / exit management database 2121, the inquiry control unit 2113 generates an inquiry result including the parking lot unique ID linked to the vehicle unique ID, the entry time, etc. On the other hand, if the vehicle unique ID is not stored in the entry / exit management database 2121, it generates an inquiry result indicating that the vehicle 32 corresponding to the relevant vehicle unique ID has not been entered into the paid parking lot 22. The communication control unit 2111 transmits the generated inquiry result to the parking discount management server 11 via the communication interface 213.

[0133] If the received inquiry result includes the parking lot unique ID and the entry time, etc., the ticket issuance control unit 1113 associates the parking lot unique ID and the entry time with the user unique ID and vehicle unique ID included in the ticket issuance request, and stores them in the parking lot database 1121. Note that before proceeding to step ST207, it may be possible to check whether the location information included in the electronic parking ticket issuance request matches the location information of the paid parking lot 22.

[0134] On the other hand, if it has not been stored, or if the inquiry result includes information that the vehicle 32 corresponding to the vehicle unique ID has not been parked in the paid parking lot 22, the ticket issuance control unit 1113 generates ticket issuance impossible information, and the communication control unit 1111 transmits the ticket issuance impossible information to the user device 31. In this case, the user 3 will respond according to the error situation.

[0135] In step ST107, the communication control unit 1111 transmits a ticket issuance permission. The ticket issuance control unit 1113 generates a ticket issuance permission including the parking lot unique ID and the entry time included in the inquiry result. The communication control unit 1111 transmits the ticket issuance permission to the user equipment 31 via the communication interface 113. Furthermore, the ticket issuance control unit 1113 outputs the ticket issuance permission to the advertisement control unit 1114.

[0136] The electronic parking ticket application control unit 3112 of the user device 31 may display on the output unit 316 that an electronic parking ticket has been issued, and may also display on the output unit 316 the entry time included in the ticket issuance permission, the name of the paid parking lot 22 corresponding to the parking lot's unique ID, etc.

[0137] In step ST108, the communication control unit 1111 transmits permission to issue a ticket to the parking lot management server 21. This process may be optional and may be skipped. In Fig. 9, this process is indicated by a dotted line.

[0138] Thereafter, the user 3 purchases a product at a store 5 that is affiliated with the paid parking lot 22. At this time, the user 3 wishes to receive the receipt as an electronic receipt.

[0139] Although not shown in FIG. 9, the communication control unit 1111 may transmit store information to the user equipment 31. For example, the advertisement control unit 1114 that has received the ticket issuance permission refers to the advertisement database 1122 and acquires advertisements and coupons for the store 5 that is affiliated with the paid parking lot 22 corresponding to the parking lot unique ID. Then, the advertisement control unit 1114 generates store information including the acquired advertisements and coupons. The communication control unit 1111 transmits the generated store information to the user equipment 31 via the communication interface 113. The communication control unit 1111 may transmit the store information at any timing while the user 3 is using the paid parking lot 22.

[0140] In step ST109, the user device 31 displays a code for obtaining an electronic receipt. The user 3 starts up an electronic receipt application of the user device 31. The electronic receipt application control unit 3113 causes the output unit 316 to display a one-dimensional code or a two-dimensional code including at least one of a user unique ID or a membership number.

[0141] Here, in step ST109, there may be cases where the user 3 does not purchase the product himself, but the user's family member purchases the product at the store 5. In this embodiment, it is assumed that the family member is registered as a family member using an electronic receipt application. In this case, a code is displayed on the user device 31 owned by the family member. The code includes a user unique ID or a family member number.

[0142] In step ST110, the communication control unit 4111 receives the POS information. For example, the POS system provided in the store 5 reads the user unique ID and the membership number from the code (one-dimensional code or two-dimensional code) displayed by the user device 31. Then, the POS system generates POS information including the product purchased by the user 3, the price, the store unique ID that identifies the store 5, and the user unique ID, and transmits the POS information to the electronic receipt management server 41.

[0143] It should be noted that, in step ST109, if the code includes a family member number, the POS information will include the family member number instead of the member number.

[0144] In step ST111, the communication control unit 4111 transmits the purchase information to the parking discount management server 11. The communication control unit 4111 receives the POS information through the communication interface 413. The purchase information control unit 4112 generates purchase information including the POS information, and stores the purchase information in the purchase information storage unit 4121. Then, the communication control unit 4111 transmits the purchase information to the parking discount management server 11 through the communication interface 413. Then, the settlement control unit 1115 stores the received purchase information in the purchase information storage unit 1124. The purchase information control unit 4112 may generate the purchase information every time it receives POS information, or may generate the purchase information at a fixed interval.

[0145] Here, if the POS information includes a family member number, the purchase information control unit 4112 may generate purchase information including the POS information. Furthermore, the purchase information control unit 4112 may store the POS information in the purchase information storage unit 4121 in association with the family member number.

[0146] Furthermore, steps ST109 to ST111 may be processes that are performed every time the user 3 or a family member of the user 3 makes a purchase at the store 5.

[0147] In steps ST109 to ST111, the parking discount management server 11 does not need to receive the purchase information via the electronic receipt management server 41. For example, the user 3 may take a picture of a receipt issued on paper using a camera provided in the user device 31. The control unit 311 may generate purchase information including the store ID, purchase amount, user unique ID (or membership number), etc., recognized from the captured image, and transmit it to the parking discount management server 11. In such a case, the electronic receipt management server 41 does not need to be installed.

[0148] In step ST112, the communication control unit 3111 transmits an inquiry. For example, assume that the user 3 wishes to see the current parking fee and presses the required button. In response to the pressing of the button, the electronic parking ticket application control unit 3112 creates an inquiry as to how much the current parking fee is. Here, the inquiry includes a user-specific ID, a vehicle-specific ID, a parking lot-specific ID, an entry time, etc. Alternatively, the electronic parking ticket application control unit 3112 may generate an inquiry at any period. The communication control unit 3111 transmits the inquiry to the parking discount management server 11 via the communication interface 313.

[0149] In step ST113, the communication control unit 1111 transmits a fee inquiry. The settlement control unit 1115 that receives the inquiry inquires about the current usage fee of the paid parking lot 22, and generates a fee inquiry. The fee inquiry includes at least the vehicle's unique ID, and may also include the parking lot's unique ID and the entry time. The communication control unit 1111 transmits the fee inquiry to the parking lot management server 21 via the communication interface 113.

[0150] In step ST114, the parking fee control unit 2114 calculates the parking fee. The parking fee control unit 2114 refers to the entry / exit management database 2121, acquires the parking lot unique ID and the entry time linked to the vehicle unique ID included in the fee inquiry, and calculates the parking fee at the current time.

[0151] In step ST115, the communication control unit 2111 transmits the fee response. The parking fee control unit 2114 generates a fee response including the calculated parking fee. The communication control unit 2111 transmits the fee response to the parking discount management server 11 via the communication interface 213.

[0152] In step ST116, the settlement control unit 1115 calculates the parking fee compensation amount based on the inquiry received in step ST112. FIG. 10 is a flowchart illustrating an example of the process of step ST116 in more detail. In step ST201, the payment control unit 1115 extracts an affiliated store from the parking lot unique ID. The payment control unit 1115 refers to the parking lot database 1121 and extracts the store 5 affiliated with the paid parking lot 22 corresponding to the parking lot unique ID included in the inquiry, i.e., the store unique ID.

[0153] In step ST202, the settlement control unit 1115 extracts the purchase information of the store 5. The settlement control unit 1115 refers to the purchase information database 524, and extracts the purchase information linked to the store-specific ID extracted in step ST201.

[0154] In step ST203, the settlement control unit 1115 judges whether the user 3 has made a purchase at the store 5. The settlement control unit 1115 judges whether the purchase information includes purchase information corresponding to the user unique ID. If there is no purchase information, the process proceeds to step ST207. On the other hand, if there is purchase information, the process proceeds to step ST204.

[0155] In step ST204, the settlement control unit 1115 determines whether x≧b. Here, x is the purchase amount at store 5, and may be the total amount of the fees purchased at store 5. b is the compensation application lower limit. For example, if the purchase amount x is less than the compensation application lower limit b, the parking fee will not be compensated. In this case, the process proceeds to step ST207. On the other hand, if the purchase amount x is equal to or greater than the compensation application lower limit b, the process proceeds to step ST205 to determine the amount to compensate the parking fee.

[0156] In step ST205, the settlement control unit 1115 determines the compensation amount according to the compensation application upper limit a. If the purchase amount x is greater than the compensation application upper limit a, the settlement control unit 1115 sets the purchase amount x to the compensation application upper limit a. On the other hand, if the purchase amount x is equal to or less than the compensation application upper limit, the settlement control unit 1115 leaves the purchase amount x as it is.

[0157] In step ST206, the settlement control unit 1115 calculates the compensation amount Y at the store 5. The settlement control unit 1115 calculates the compensation amount Y by purchasing amount x * compensation rate m. The compensation rate m may be a rate set for each store.

[0158] In step ST207, the settlement control unit 1115 determines whether or not there is a purchase at another store 5. If there are multiple stores 5 extracted in step ST201 and there is a store for which the compensation amount Y has not yet been calculated, the settlement control unit 1115 determines that there is a purchase at another store 5. In this case, the process returns to step ST202. On the other hand, if the compensation amount has been calculated for all stores, the process proceeds to step ST208.

[0159] In step ST208, the settlement control unit 1115 judges whether or not there is purchase information of a family member. The settlement control unit 1115 refers to the user information database 1123 to acquire the family member number linked to the user unique ID. Then, it judges whether or not there is purchase information linked to the family member number. If there is purchase information, the process proceeds to step ST209. On the other hand, if there is no purchase information, the process proceeds to step ST210.

[0160] In step ST209, the settlement control unit 1115 calculates the compensation amount for the purchase information linked to the family member number by the same processing as that explained in steps ST204 to ST206.

[0161] In step ST210, the settlement control unit 1115 calculates the parking fee compensation amount. The settlement control unit 1115 sets the total of the parking fees calculated in steps ST206 and ST209 as the parking fee compensation amount.

[0162] Returning to FIG. 9, in step ST117, the communication control unit 1111 transmits electronic parking ticket update information. The settlement control unit 1115 calculates the user parking fee to be paid by the user 3 by subtracting the parking fee compensation amount from the parking fee included in the fee response. Then, the ticket issuance control unit 1113 generates electronic parking ticket update information including the parking fee, the parking fee compensation amount, and the user parking fee. Then, the communication control unit 1111 transmits the electronic parking ticket update information to the user device 31 via the communication interface 113. The ticket issuance control unit 1113 may also include information on how much of the fee will be compensated if an additional amount of goods is purchased at the store 5 in the electronic parking ticket update information.

[0163] The processing of steps ST112 to ST117 may be performed every time the electronic parking ticket application control unit 3112 generates an inquiry.

[0164] In step ST118, the vehicle 32 equipped with the on-board device 33 leaves the paid parking lot 22. For example, the vehicle detection control unit 2412 of the parking lot equipment 24 controls the vehicle detector 247 to detect the vehicle 32. Then, the communication control unit 2411 transmits an acquisition instruction to the roadside device 23.

[0165] In step ST119, the communication control unit 3311 transmits the on-board device information to the road-side device 23. First, the signal control unit 2312 generates an on-board device information request based on the received acquisition instruction. The communication control unit 2311 transmits the generated on-board device information request to the on-board device 33.

[0166] The on-board device information generating unit 3312 that has received the on-board device information request generates the on-board device information. Then, the communication control unit 3311 transmits the on-board device information to the road-side device 23 via the communication interface 333.

[0167] In step ST120, the roadside unit 23 transmits the exit information to the parking lot management server 21. The signal control unit 2312 that has received the on-board unit information generates exit information including the on-board unit information, a parking lot unique ID that identifies the paid parking lot 22, the exit time of the vehicle 32, etc. The communication control unit 2311 transmits the generated exit information to the parking lot management server 21 via the communication interface 233. The entry / exit status control unit 2112 of the parking lot management server 21 stores the received exit information in the entry / exit management database 2121.

[0168] Furthermore, the entry / exit status control unit 2112 may transmit a gate open instruction or the like to the parking lot equipment 24. The gate control unit 2414 opens the gate in response to the instruction, thereby allowing the user 3 to exit the paid parking lot.

[0169] As in steps ST101 to ST103 described above, in steps ST118 to ST120, a vehicle number or the like, which is a vehicle-specific ID, may be acquired by a camera provided in the parking lot equipment 24. Then, the communication control unit 2411 may transmit the vehicle-specific ID to the parking lot management server 21 as entry information.

[0170] In step ST121, the communication control unit 2111 transmits the exit information to the parking discount management server 11. Upon receiving the exit information, the communication control unit 2111 transfers the exit information to the parking discount management server 11.

[0171] In step ST122, the settlement control unit 1115 calculates the total parking fee compensation amount. Having received the exit information, the settlement control unit 1115 refers to the parking lot database 1121 and the user information database 1123 to acquire the user unique ID and parking lot unique ID linked to the vehicle unique ID included in the exit information. Then, the total parking fee compensation amount is calculated in the same manner as in step ST116.

[0172] In step ST123, the communication control unit 1111 transmits the compensation details to the parking management server 21. The settlement control unit 1115 creates a compensation details including the total parking fee compensation amount. Then, the communication control unit 1111 transmits the created compensation details to the parking management server 21.

[0173] In step ST124, the communication control unit 2111 transmits the compensation claim to the electronic receipt management server 41. The parking fee control unit 2114 calculates the parking fee corresponding to the entry time to the exit time, and the user parking fee, which is the amount to be paid by the user 3, obtained by subtracting the compensation from the parking fee. Then, a compensation claim including the compensation to be paid by each store 5 according to the parking fee or compensation details is generated. Note that if the total amount of the compensation is more than the parking fee, the parking fee control unit 2114 may determine the compensation to be actually compensated according to the ratio of the parking fee and the compensation amount of each store 5 so that the total amount of the compensation is the parking fee. The communication control unit 2111 transmits the compensation claim to the electronic receipt management server 41 through the communication interface 213.

[0174] In step ST125, the communication control unit 4111 transmits the compensation to the parking lot management server 21. The control unit 211 receives the compensation from each store 5. Here, the method of receiving the compensation may be a general method. For example, the electronic receipt management server 41 may receive a predetermined amount of money from each store 5, pool it, and transfer the compensation from there to the parking lot management server 21.

[0175] In addition, in steps ST124 to ST125, the parking discount management server 11 may directly send a compensation claim to each store 5. In this case, each store 5 remits the compensation to the parking lot management server 21. When operating as described above, the electronic receipt management server 41 is no longer a required component, so it is not necessary to install the electronic receipt management server 41.

[0176] In step ST126, the parking fee control unit 2114 and the electronic parking ticket application control unit 3112 settle the user parking fee. For example, the communication control unit 2111 transmits the user parking fee to the user equipment 31. The user 3 instructs the user equipment 31 to settle the user parking fee, for example, by a predetermined electronic payment. As a result, the electronic parking ticket application control unit 3112 pays the user parking fee to the parking lot management server 21 by carrying out the predetermined payment. The payment method may be any general method or any arbitrary method.

[0177] Here, the processing of steps ST122 to ST126 may be performed immediately after the vehicle 32 leaves the garage, but may also be performed collectively for all users 3 at any interval, such as once a day.

[0178] (Effects of the first embodiment) According to the first embodiment described above, when a user 3 who parks in a paid parking lot 22 affiliated with a store 5 purchases a product at the store 5, the store 5 reimburses the usage fee for the paid parking lot 22 according to the purchase price of the product. This eliminates the need for the store 5 to cover the parking fee for a user 3 who does not use the store 5. Furthermore, the store 5 can avoid excessive burdens by determining an upper limit for the reimbursement amount and a lower limit for the purchase amount eligible for reimbursement.

[0179] Furthermore, by linking the electronic parking ticket and the electronic receipt, the user 3 can receive the same discount at a paid parking lot 22 such as a coin parking lot as at a paid parking lot 22 in a large facility.

[0180] [Second embodiment] In the second embodiment, the parking lot operator 2 may provide a car sharing service. In such a case, when the user 3 uses the car sharing vehicle 32, not only the parking fee but also the car sharing fee can be compensated. In the second embodiment, the user 3 uses the car sharing to use the paid parking lot 22.

[0181] (composition) In the second embodiment, the configurations of the parking discount management server 11, the roadside device 23, the parking lot equipment 24, the user equipment 31, the vehicle-mounted equipment 33, and the electronic receipt management server 41 may be the same as those in the first embodiment, so duplicated explanations will be omitted here.

[0182] FIG. 11 is a block diagram showing an example of the hardware configuration of the parking lot management server 21 and the software configuration associated with the hardware configuration. As shown in FIG. 11, the parking lot management server 21 differs from the first embodiment in that it includes a car share fee control unit 2115 and a car share management database 2122.

[0183] The car share fee control unit 2115 is a control unit for calculating a car share fee when the user 3 uses the car share. For example, the car share fee control unit 2115 calculates the car share fee based on the time from when the user 3 starts using the car share to when the user 3 ends using the car share.

[0184] The car sharing management database 2122 is a database that stores vehicles 32 available for car sharing, the vehicle unique ID of the vehicle 32, the user unique ID and car sharing membership number of the user 3 who uses car sharing, etc. Furthermore, when the user 3 uses car sharing, the car sharing management database 2122 may store the start date and time of use, the end date and time of use, etc., in association with the user unique ID or the car sharing membership number.

[0185] (operation) As in the first embodiment, a specific example of operations will be described when a user 3 having a user device 31 in which a parking ticket application and an electronic receipt application are linked uses a store 5. As described above, the user 3 uses a car share to use a paid parking lot 22.

[0186] FIG. 12 is a sequence diagram showing an example of a case where a user 3 using a car share uses a paid parking lot 22 and a store 5. In FIG. The operation of this sequence diagram is realized by the control unit 111 of the parking discount management server 11, the control unit 211 of the parking lot management server 21, the control unit 231 of the roadside unit 23, the control unit 311 of the user equipment 31, the control unit 311 of the in-vehicle unit 33, and the control unit 411 of the electronic receipt management server 41 reading and executing programs stored in the memory unit 112, memory unit 212, memory unit 232, memory unit 312, memory unit 332, and memory unit 412, respectively.

[0187] This sequence starts when the user 3 uses the vehicle 32 to enter the paid parking lot 22. It is assumed that the paid parking lot 22 is a parking lot with which the store 5 has an agreement.

[0188] Steps ST301 to ST305 are similar to the processes in steps ST101 to ST105 described with reference to FIG. 9, and therefore a duplicated description will be omitted here.

[0189] In step ST306, the ticket issuance control unit 1113 of the parking discount management server 11 and the inquiry control unit 2113 of the parking lot management server 21 perform a user inquiry. The ticket issuance control unit 1113 generates an inquiry request including the vehicle unique ID included in the received electronic parking ticket issuance request. The communication control unit 1111 transmits the generated inquiry request to the parking lot management server 21 through the communication interface 113.

[0190] The inquiry control unit 2113 inquires whether the vehicle unique ID included in the received inquiry request is stored in the entry / exit management database 2121 and the car share management database 2122. If the vehicle unique ID included in the inquiry request is stored in the entry / exit management database 2121 and the car share management database 2122, the inquiry control unit 2113 generates an inquiry result including the parking lot unique ID, entry time, car share member number, etc. linked to the vehicle unique ID. On the other hand, if the vehicle unique ID is not stored in the entry / exit management database 2121, it generates an inquiry result indicating that the vehicle 32 corresponding to the relevant vehicle unique ID has not been entered into the paid parking lot 22. The communication control unit 2111 transmits the generated inquiry result to the parking discount management server 11 via the communication interface 213.

[0191] If the received inquiry result includes the parking lot unique ID and the entry time, etc., the ticket issuance control unit 1113 associates the parking lot unique ID, the entry time, and the car share membership number with the user unique ID and the vehicle unique ID included in the ticket issuance request, and stores them in the parking lot database 1121. Note that before proceeding to step ST307, it may be possible to check whether the location information included in the electronic parking ticket issuance request matches the location information of the paid parking lot 22.

[0192] On the other hand, if it has not been stored, or if the inquiry result includes information that the vehicle 32 corresponding to the vehicle unique ID has not been parked in the paid parking lot 22, the ticket issuance control unit 1113 generates ticket issuance impossible information, and the communication control unit 1111 transmits the ticket issuance impossible information to the user device 31. In this case, the user 3 will respond according to the error situation.

[0193] Steps ST307 to ST322 are similar to steps ST107 to ST122 described with reference to FIG. 9, and therefore will not be described here.

[0194] Here, in steps ST316 and ST322, the fees to be compensated are the parking fee and the car sharing fee, so the amount of the compensation fee is simply calculated.

[0195] It is assumed that the user ends the use of the car share after step ST322. Therefore, the usage end date and time is stored in the car share management database 2122 of the parking lot management server 21. In addition, the car share fee control unit 2115 may calculate the car share usage fee based on the usage start date and time and usage end date and time stored in the car share management database 2122.

[0196] In step ST323, the communication control unit 3111 transmits a usage fee inquiry. For example, when it detects that the user 3 presses a predetermined button when he / she wishes to check the parking fee and the car share usage fee, or at an arbitrary period, the electronic parking ticket application control unit 3112 generates a usage fee inquiry to inquire about the usage fee. The usage fee inquiry includes the user's unique ID and the car share membership number, etc. The communication control unit 3111 transmits the generated fee inquiry to the parking management server 21 via the communication interface 313.

[0197] In step ST324, the communication control unit 2111 transmits a compensation amount determination inquiry. The parking fee control unit 2114 and the car share fee control unit 2115 that have received the usage fee inquiry refer to the entry / exit management database 2121 and the car share management database 2122, respectively, to obtain the parking fee and the car share fee corresponding to the user unique ID and the car share membership number. Furthermore, the parking fee control unit 2114 generates a compensation amount inquiry to inquire about the compensation amount. The communication control unit 2111 then transmits the generated compensation amount inquiry to the parking discount management server 11 via the communication interface 213.

[0198] In step ST325, the communication control unit 1111 transmits the compensation amount result. The settlement control unit 1115, which has received the compensation determination inquiry, refers to the purchase information storage unit 1124 and obtains the total fee compensation amount calculated in step ST322. The settlement control unit 1115 then generates a compensation amount result including the total fee compensation amount. The communication control unit 1111 transmits the generated compensation amount result via the communication interface 113.

[0199] In step ST326, the communication control unit 2111 transmits the usage fee response. The parking fee control unit 2114 or the car sharing fee control unit 2115 calculates the user payment fee to be paid by the user 3 by subtracting the total fee compensation amount from the total of the parking fee and the car sharing fee. Then, the parking fee control unit 2114 or the car sharing fee control unit 2115 generates a usage fee response including the parking fee, the car sharing fee, the fee compensation amount, and the user payment fee. The communication control unit 2111 transmits the user payment fee via the communication interface 213. The electronic parking ticket application control unit 3112 causes the output unit 316 to display the user payment fee. This allows the user 3 to know the details of the usage fee.

[0200] (Effects of the second embodiment) According to the second embodiment described above, when a user 3 who parks in a paid parking lot 22 affiliated with the store 5 and uses car sharing purchases a product at the store 5, the store 5 compensates the user for the car sharing fee in addition to the usage fee for the paid parking lot 22 according to the purchase price of the product. This motivates the user to purchase a more expensive product, which increases sales for the store 5.

[0201] [Other embodiments] It should be noted that the present invention is not limited to the above embodiment. For example, in the above embodiment, the roadside unit 23 and the parking lot equipment 24 are shown as separate devices, but the functions of the roadside unit 23 may be implemented by one parking lot equipment 24. In other words, the operation processed by the roadside unit 23 may be performed by the parking lot equipment 24.

[0202] Furthermore, although the parking discount management server 11 and the electronic receipt management server 41 are shown as separate servers, they may be integrated into one server.

[0203] In short, this invention is not limited to the above-mentioned embodiment, and various modifications can be made in the implementation stage without departing from the gist of the invention. Moreover, each embodiment may be implemented in combination as appropriate as possible, in which case the combined effect can be obtained. Furthermore, the above-mentioned embodiment includes inventions at various stages, and various inventions can be extracted by appropriate combinations of the disclosed constituent elements. [Explanation of symbols]

[0204] S…Parking discount management system 1. Parking discount business 11...Parking discount management server 111...Control unit 1111…Communication control unit 1112...Registration control unit 1113...Ticket issuing control unit 1114...Advertisement control unit 1115...Settlement control unit 112...Storage section 1121...Parking lot database 1122…Advertising database 1123...User information database 1124...Purchase information storage unit 113...Communication interface 114... Input / Output Interface 115...Input section 116...Output section 2. Parking lot operators 21...Parking lot management server 211...Control unit 2111…Communication control unit 2112…Inventory status control unit 2113... Reference control section 2114…Parking fee control unit 2115…Car sharing fee control unit 212...Storage section 2121...Inventory management database 2122…Car sharing management database 213…Communication interface 214... Input / Output interface 215...Input section 216...Output section 22... Paid parking lot 23…Roadside machine 231...Control unit 2311…Communication control section 2312: Signal control section 232...Storage section 233…Communication interface 234... Input / Output interface 235...Input section 236...Output section 24...Parking lot equipment 241...Control unit 2411…Communication control unit 2412…Vehicle detection control unit 2413…Signal control section 2414…Gate control section 2415...Ticket issuing control unit 2416...Payment control unit 242...Storage section 243…Communication interface 244... Input / Output interface 245…Input section 246…Output section 247…Vehicle detector 248…Gate 249…Ticketing and Payment Department 3. User 31...User equipment 311...Control unit 3111…Communication control section 3112...Electronic parking ticket application control unit 3113...Electronic receipt application control unit 312...Storage section 313…Communication Interface 314... Input / Output Interface 315...Input section 316...Output section 32…Vehicle 33…In-vehicle device 331...Control unit 3311…Communication control section 3312...In-vehicle equipment information generation section 332...Storage section 333…Communication Interface 334... Input / Output Interface 335...Input section 336...Output section 4. Electronic receipt service providers 41...Electronic receipt management server 411...Control unit 4111…Communication control section 4112...Purchase information control unit 412...Storage section 4121...Purchase information storage unit 413…Communication interface 414... Input / Output Interface 415...Input section 416...Output section 5. Store 100…Network

Claims

1. A parking lot database that stores the parking lot ID of the affiliated parking lot with the store in association with the store ID; a purchase information storage unit that stores a plurality of pieces of purchase information including a purchase price for a user purchasing a product at each of a plurality of stores and a user unique ID; a receiving unit that receives an inquiry including the user unique ID and a parking lot unique ID of a paid parking lot where the user is parked; an acquisition unit that refers to the parking lot database to acquire a store ID corresponding to a parking lot unique ID included in the inquiry, and refers to the purchase information storage unit to acquire the purchase information corresponding to a user unique ID included in the inquiry; a determination unit that determines whether the user made a purchase at the store based on the purchase information and the store ID; a settlement control unit that calculates a compensation amount according to the purchase amount when it is determined that the purchase has been made; A parking discount management server comprising:

2. The determination unit determines whether the purchase amount is below a compensation application lower limit, If the compensation application lower limit is exceeded, the settlement control unit does not calculate the compensation amount. The parking discount management server according to claim 1.

3. The determination unit determines whether the purchase amount exceeds a compensation application upper limit, If the compensation application upper limit is exceeded, the settlement control unit calculates the compensation amount using the purchase amount as the compensation application upper limit. The parking discount management server according to claim 1.

4. the user unique ID includes a family member number of an electronic receipt, and the acquisition unit further acquires purchase information of a family member corresponding to the family member number included in the user unique ID included in the inquiry; The determination unit determines whether a family member of the user made a purchase at the store based on the family member's purchase information and the store ID; When it is determined that the family member has made a purchase, the settlement control unit further calculates a compensation amount according to the purchase price of the family member. The parking discount management server according to claim 1.

5. The compensation amount is intended to compensate the user for the parking fee incurred by the user at the affiliated parking lot. The parking discount management server according to claim 1.

6. The compensation amount is for compensating for the parking fee as well as the car sharing fee for the vehicle used by the user.

6. The parking discount management server according to claim 5.

7. A parking discount management method implemented by a parking discount management server, comprising: A user information database of the parking discount management server stores a user unique ID that identifies a user and a vehicle unique ID that identifies a vehicle used by the user, the vehicle unique ID being associated with the user unique ID; A reception control unit of the parking discount management server receives a plurality of pieces of purchase information including a purchase amount of the user who purchased the product at each of a plurality of stores and the user unique ID; an acquisition unit of the parking discount management server acquires a vehicle unique ID stored in the user information database based on the user unique ID included in the purchase information; A determination unit of the parking discount management server determines whether the vehicle is parked in an affiliated parking lot with which the plurality of stores are affiliated, based on the vehicle unique ID; When a settlement control unit of the parking discount management server determines that the vehicle is parked in the affiliated parking lot, it calculates a compensation amount to be compensated by each of the plurality of stores according to the purchase amount, out of the parking fee incurred by parking in the affiliated parking lot; A parking discount management method comprising:

Images