Electronic parking ticket management system, central server, parking lot management server, and electronic parking ticket management method

Abstract

To be able to provide a wide variety of services.SOLUTION: According to the embodiment, a server apparatus is communicatively connected to a roadside unit installed at the gate of a parking lot. The roadside unit includes a detection unit for detecting a mobility identifier that identifies a mobility entering through the gate, from the mobility. The server apparatus includes a database, an identifying unit, and a transmitting unit. The database is a database in which the correspondence between the mobility identifiers and user identifiers is registered in advance. The identifying unit refers to the database to identify the user identifier corresponding to the mobility identifier notified from the roadside unit. The transmitting unit transmits parking ticket information to a user device possessed by a user having the identified user identifier.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] Embodiments of the present invention relate to an electronic parking ticket management system, a server device, and a service providing system.

Background Art

[0002] When using a parking lot at a supermarket, shopping mall, etc., a parking fee is charged. However, for customers who have shopped at a store, services such as making the parking fee free for, for example, a limited time of 2 hours or discounting the parking fee according to the shopping amount are well known. In providing this type of service, a parking ticket is issued at the gate at the entrance of the parking lot and settlement is performed by a settlement machine before leaving the store.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] On a parking ticket, a number or the like as user identification information is magnetically recorded. By reading this with a settlement machine or the like, the operator can identify the user (customer) and provide a discount service. However, as the demand for cashless settlement increases, it is required to be able to handle an electronic parking ticket without a physical entity instead of a paper-based parking ticket.

[0005] While electronic parking tickets are convenient, attention must be paid to security and the confidentiality of personal information. For example, it is required to reliably and unambiguously associate the incoming vehicle with the user targeted for the service. Also, in existing technologies, since it is necessary to construct a system for managing electronic parking tickets for each service provider, there is room for consideration in terms of cost. Furthermore, a system that can provide various services beyond cashless settlement is required.

[0006] Therefore, an object is to provide an electronic parking ticket management system, a server device, and a service providing system that can provide various services.

Means for Solving the Problem

[0007] According to an embodiment, the electronic parking ticket management system includes a roadside unit installed in a parking lot, a center server communicably connected to the roadside unit, a POS system for managing purchase information of a user, and a service providing server for providing services to the user. The roadside unit includes a detection unit, an encryption unit, and a notification unit. The detection unit detects a vehicle ID for identifying a vehicle entering or leaving the parking lot. The encryption unit encrypts the detected vehicle ID to generate encrypted information. The notification unit notifies the encrypted information to the center server. The center server includes a database registering the correspondence between the vehicle ID and the user ID for identifying the user, a decryption unit, a specifying unit, and a transmission unit. The decryption unit decrypts the notified encrypted information to restore the vehicle ID. The specifying unit specifies the user ID of the user corresponding to the restored vehicle ID by referring to the database. The transmission unit transmits electronic parking ticket information obtained by encoding the vehicle ID to the user device of the user ID specified by the specifying unit. The POS system includes a reading unit for reading electronic parking ticket information from the user device when acquiring purchase information. The service providing server includes a record management unit and a service providing unit. The record management unit manages purchase information for each user based on the electronic parking ticket information and purchase information read by the POS system. The service providing unit determines whether it is a discount target from the vehicle ID and the purchase information for each user, and if it is a discount target, the discount amount Calculate the parking feeNotify the actuarial amount.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

DETAILED DESCRIPTION OF THE INVENTION

[0009] In the embodiment, a system that provides services such as a fee discount to a user who uses a paid parking lot according to the history of shopping in related stores or the like will be described. The use of the parking lot is not limited to private cars. That is, in recent years, a so-called car-sharing service in which a plurality of people share a vehicle has become known, and such a form is also assumed in the embodiment. This type of service is called MaaS (Mobility as a Service), and various means of transportation including vehicles (four-wheeled vehicles, motorcycles, bicycles, or public transportation) are collectively referred to as mobility regardless of whether they are privately owned or shared.

[0010] <The First Configuration> In the first configuration, a system in which the sales management system in the store and the center system independent of the store cooperate will be described.

[0011] FIG. 1 is a system diagram showing an example of an electronic parking ticket management system according to an embodiment. This system includes a roadside unit 40 installed at the gate of a parking lot and a parking lot management server 30 communicably connected to the roadside unit 40. Further, the system in FIG. 1 includes a center server 200 communicably connected to the roadside unit 40 via the parking lot management server 30.

[0012] The center server 200 is a physical or virtual server formed in the cloud 100 and can access the database 300. The cloud 100 is connected to the mobile communication network 400. The center server 200 can communicate with a user device 10 possessed by a user, for example, via a base station 50 of the mobile communication network 400 from the cloud 100. Alternatively, the center server 200 can also communicate with the user device 10 via an access point of a wireless LAN (Local Area Network) represented by Wi-Fi (registered trademark). The access point can utilize the existing infrastructure installed inside and outside the store.

[0013] The mobility 20 in which the user rides includes an in-vehicle unit 21. The in-vehicle unit 21 stores in advance a unique in-vehicle unit ID (Identification: identifier) for identifying the mobility 20. When the mobility 20 enters the parking lot through the gate, the roadside unit 40 communicates with the in-vehicle unit 21, detects the in-vehicle unit ID, and reads its content. Here, the roadside unit 40 may be, for example, a device for ETC (electronic toll collection) equipped with a DSRC (dedicated short-range communications) function.

[0014] The in-vehicle device ID is, for example, a WCN (wireless call number) or an in-vehicle device management number. In the embodiment, the in-vehicle device ID will be described by referring to it as the vehicle ID for identifying the mobility 20. In addition, identification information such as the vehicle number described on the license plate or the vehicle registration number can also be used as the vehicle ID.

[0015] The roadside unit 40 encrypts the detected vehicle ID using the key information and transmits it to the center server 200. The center server 200 also has key information corresponding to this key information, and the center server 200 decrypts the encrypted vehicle ID. This can prevent the vehicle ID from being read or the data being intercepted on the parking lot management server 30 or on the intermediate route.

[0016] FIG. 2 is a diagram for explaining the cooperation with a store of the electronic parking ticket management system shown in FIG. 1. The store includes a parking lot management server 30, a service providing server 60, a POS server 70, and a POS terminal 75. These are connected to the in-store network 15 such as a LAN (Local Area Network). The roadside unit 40 can also be connected to the in-store network 15, and the parking lot management server 30 can communicate with the roadside unit 40 via the in-store network 15.

[0017] In FIG. 2, a center server 200 is provided at the center of the cloud 100. When the mobility 20 approaches the roadside unit 40, the vehicle ID is read from the in-vehicle device 21. This vehicle ID is passed to the center server 200 via the in-store network 15 and the parking lot management server 30.

[0018] In a database 300 accessible from a center server 200, a table in which a vehicle ID and a user ID of an individual user are associated in advance is registered in advance. The user ID is, for example, the email address of a user device 10 (such as a mobile terminal typified by a smartphone) possessed by the user. In addition, information that can uniquely identify the user, such as a phone number, an SNS account, an account of an electronic money application, and an account ID of an individual application, can be used as the user ID. Furthermore, tablets, watch-type devices, etc. can also be used as the user device 10. The center server 200 refers to the database 300 and acquires the email address corresponding to the vehicle ID. Then, the center server 200 generates an electronic parking ticket from the vehicle ID and issues the electronic parking ticket to the acquired email address. The electronic parking ticket can be in the form of, for example, a barcode or a QR code (registered trademark). When purchasing at a store, by having the user device 10 read this electronic parking ticket, the mobility 20 and the user (user device 10) can be uniquely associated with each other and used to provide various services. Next, an embodiment based on the above configuration will be described.

[0019] [First Embodiment] FIG. 3 is a functional block diagram showing an example of an electronic parking ticket management system according to the first embodiment. In FIG. 3, a POS server 70 and a POS terminal 75 together form a POS system that acquires user purchase information. The POS terminal 75 includes a code reader 76 that reads the barcode of the user device 10 and acquires the vehicle ID. The service providing server 60 is installed, for example, for each service provider and provides services to users. The parking lot management server 30 is connected to the roadside unit 40 and the center server 200. Here, each of the POS server 70, the POS terminal 75, the user device 10, the service providing server 60, the parking lot management server 30, and the roadside unit 40 is a computer equipped with a memory and a processor.

[0020] The roadside unit 40 includes a processor 41 in addition to a non-volatile memory such as a ROM, a volatile memory such as a RAM, an auxiliary storage device such as an EPROM (Programmable Read-Only Memory), an erasable EPROM, an HDD (hard disk drive), a flash memory, and various interfaces. The processor 41 is an arithmetic chip represented by a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).

[0021] The processor 41 includes a detection unit 41a, an encryption unit 41b, and a notification unit 41c as processing functions according to the embodiment. These are understood as processing functions implemented in a program pre-stored in the storage device of the roadside unit 40.

[0022] The detection unit 41a communicates with the mobility 20 entering from the gate of the parking lot and detects the vehicle ID that identifies the mobility. The encryption unit 41b encrypts the detected vehicle ID with key information (private key) to generate encrypted information. The notification unit 41c notifies the encrypted information to the center server 200. Here, the center server 200 has a decryption key or a public key that pairs with the above key information, and can restore the vehicle ID from the encrypted information.

[0023] The center server 200 can access the database 300 and refer to the table 300a. The table 300a is a table in which the correspondence between the vehicle ID and the email address (user ID) of the user associated with the vehicle is registered in advance. This email address is typically the email address of the user device 10.

[0024] The center server 200 includes a processor 201. The processor 201 includes a specifying unit 201a, a decrypting unit 201b, and a transmitting unit 201c as processing functions according to the embodiment. These are understood as processing functions implemented in a program pre-stored in the storage device of the center server 200.

[0025] First, the decoding unit 201b decodes the encrypted information notified from the roadside unit 40 and restores the vehicle ID. The specifying unit 201a refers to the table 300a of the database 300 to specify the email address (user ID) corresponding to the restored vehicle ID. For example, if the restored vehicle ID is "Vehicle 1", the email address corresponding to the user of this Vehicle 1 is "aaa@aaa.jp".

[0026] The transmission unit 201c transmits the parking ticket information to the specified email address. As a result, the parking ticket information is delivered to the user device 10. In the first embodiment, the vehicle ID itself, or code information such as a barcode or QR code (registered trademark) encoding the vehicle ID is taken as the parking ticket information.

[0027] The POS server 70 includes a processor 71. The processor 71 includes a reading unit 71a as a processing function according to the embodiment. The reading unit 71a is understood as a processing function implemented in a program pre-stored in the storage device of the POS server 70. The reading unit 71a acquires purchase information when the user settles the shopping in the store. At that time, the reading unit 71a reads the parking ticket information from the user device 10 by the code reader 76.

[0028] The service providing server 60 includes a processor 61. The processor 61 includes a recording management unit 61a and a service providing unit 61b as processing functions according to the embodiment. These are understood as processing functions implemented in a program pre-stored in the storage device of the service providing server 60.

[0029] The recording management unit 61a acquires the purchase information for each user from the POS server 70 and manages the purchase records of each user based on this purchase information. The service providing unit 61b provides a parking fee discount service according to the purchase record of the user to the user who presents the parking ticket information (code information of the vehicle ID) transmitted from the center server 200 at the time of settlement. Next, the operation in the above configuration will be described.

[0030] Figure 4 is a sequence diagram showing an example of the processing procedure in the system shown in Figure 3. First, when the mobility 20 enters the parking lot from the gate, the vehicle ID is passed from the in-vehicle device 21 to the roadside unit 40. Then, the roadside unit 40 encrypts the vehicle ID (step S1) and sends the encrypted information to the center server 200 (via the parking lot management server 30).

[0031] The center server 200 receives this encrypted information, decrypts it, and restores the vehicle ID (step S2). Then, the center server 200 generates a barcode or QR code (registered trademark) from the vehicle ID and sends a message (code information) including the image data of the code to the user device 10 in the form of an email (step S3).

[0032] When the user shops at the store, the user presents the barcode (QR code (registered trademark)) displayed on the user device 10 each time they make a purchase and has it read by the code reader 76. The code reader 76 reads the vehicle ID from the barcode image and notifies the POS server 70. The POS server 70 passes the user's purchase information together with the notified vehicle ID to the service providing server 60.

[0033] The service providing server 60 determines whether to apply a discount to the user based on the purchase information for each user obtained from the POS server 70 (step S4). When it is determined that there is a discount, the service providing server 60 calculates and stores the discount amount based on the purchase amount, parking time, etc. (step S5). Then, it waits for the mobility to leave the warehouse.

[0034] When the user's shopping in the store is completed and the user's mobility exits the warehouse, the in-vehicle device 21 accesses the roadside unit 40 again. Then, the roadside unit 40 acquires the vehicle ID, encrypts this vehicle ID (step S9), and sends the obtained encrypted information to the center server 200 again. When the center server 200 receives this encrypted information, it decrypts it to restore the vehicle ID (step S12). Then, the center server 200 notifies the service providing server 60 of this vehicle ID via the parking lot management server 30.

[0035] The service providing server 60 calculates the settlement amount based on the discount service for the user with the specified user ID (step S6). Then, it notifies the in-vehicle device 21 via the parking lot management server 30 and the roadside unit 40. The in-vehicle device 21 makes a payment for the notified settlement amount by card payment or the like (step S7). Note that the user may optionally be able to make a payment with the payment machine 90 (Figure 2). When the payment is completed, the payment amount is notified from the in-vehicle device 21 to the parking lot management server 30 via the roadside unit 40. In this way, the settlement is completed. In response to this, the parking lot management server 30 sends a message transmission request to the center server 200. The center server 200 that has received this request sends a message such as "Thank you" to the user device 10 to notify the user that the settlement has been completed (step S8).

[0036] Figure 5 is a diagram for explaining the operation in the sequence diagram shown in Figure 4. In the lowermost part of the figure, the vehicle ID read from the mobility is encrypted and notified to the center server 200 via the parking lot management server 30. It is preferable that the encryption uses a method such as using time as a seed so that the encrypted information does not become fixed.

[0037] Upon receiving the encrypted vehicle ID, the central server 200 decrypts the vehicle ID and uniquely identifies the parked vehicle and the user from the vehicle ID and user ID that are linked and managed in the database 300 in advance. A table showing the correspondence between the vehicle ID and the user ID can be obtained, for example, as registration information from a web registration system or from an interface that cooperates with a car-sharing operation company.

[0038] The central server 200 sends the barcode based on the vehicle ID to the user by email. At this time, in order to prevent the barcode from being misused, the barcode may be updated and redelivered at regular intervals.

[0039] The barcode displayed on the user device 10 is read every time a purchase is made, and the settlement information is sent to the POS server 70 and the service providing server 60 together with the vehicle ID. The service providing server 60 performs a discount determination and stores the result while updating it for each user.

[0040] When the user who has finished shopping exits, the roadside unit 40 reads the vehicle ID again. This vehicle ID is encrypted again and notified to the central server 200 via the parking lot management server 30. Here too, it is preferable to prevent the encrypted information from being fixed, for example, by using time as a seed. The central server 200 that has decrypted the vehicle ID sends the vehicle ID to the service providing server 60 via the parking lot management server 30. The service providing server 60 notifies the parking lot management server 30 of the discount amount or the billing amount. This information is passed to the in-vehicle unit 21 via the roadside unit 40, and payment is made by wireless payment.

[0041] As described above, in the first embodiment, the roadside unit 40 acquires the vehicle ID from the in-vehicle device 21, encrypts it, and transmits it to the parking lot management server 30. The parking lot management server 30 transmits the encrypted vehicle ID to the center server 200 and inquires about the discount amount from the service providing server that manages the user's purchase history. The center server 200 transmits the decrypted vehicle ID to the parking lot management server 30 and the user device 10. The user device 10 displays the vehicle ID obtained from the center server 200 in code. Then, the vehicle and the user that have entered the warehouse can be uniquely identified from the vehicle ID and the user ID that are linked and managed in the database 300 in advance. That is, the purchase history for each user can be associated with the vehicle ID and managed, and it is possible to accurately perform the determination of whether to provide the service at the time of leaving the warehouse and the calculation of the service amount (discount amount).

[0042] That is, when the vehicle ID is acquired from the in-vehicle device 21, a code unique to the user device 10 is sent. By presenting the code each time a payment is made at the store, a history of purchase records is accumulated at the store. When leaving the warehouse, the vehicle ID is read again by the roadside unit 40, and the corresponding settlement amount is notified to the in-vehicle device 21. Then, a wireless payment is executed between the roadside unit 40 and the in-vehicle device 21.

[0043] In this way, the settlement is automatically performed when leaving the warehouse, and all processes can be made cashless as long as the user does not desire to pay in cash. Also, in the series of processes, a parking ticket in paper medium is not required, and the fact that the user is using the parking lot is proven by a barcode or the like displayed on the user device 10. Thereby, a payment service using an electronic parking ticket can be realized.

[0044] Moreover, the association management between the vehicle ID and the user ID is carried out on the center server 200 side. That is, since the electronic parking ticket management function is SaaS (Software as a Service) - enabled, from the perspective of the store side, it can be used as a service from the cloud. As a result, the functions for realizing the electronic parking ticket are shared among multiple service providers and store operators, and can be intensively utilized. Moreover, since the vehicle ID is encrypted and exchanged between the roadside unit 40 and the center server 200, there is no risk of data extraction by other operators. Furthermore, since the correspondence between the vehicle ID and the user ID is centrally managed in the center server 200, the user's store visit history can be managed on the center server 200 side and statistically analyzed.

[0045] From these aspects, according to the first embodiment, it becomes possible to provide services for each user with cashless settlement. Moreover, since the vehicle ID is encrypted, security can be ensured. Furthermore, since the electronic parking ticket management function can be realized in the form of a cloud service, from the perspective of the whole society, it is possible to optimize the system construction cost and operation cost. That is, for the store operator, it is not necessary to have its own system for associating users with electronic parking tickets to provide services, so the cost for improving user services can be reduced. For the payment service provider, since it can receive system usage fees from the store operator in a subscription form or the like, it can bring regular profits. That is, a system that is advantageous for both the operator on the store - operating side and the operator on the payment - service - providing side can be constructed. From the above, according to the first embodiment, it is possible to provide an electronic parking ticket management system, a server device, and a service - providing system that can provide various services.

[0046] [Second Embodiment] In the first embodiment, the purchase record of the user was managed in association with the vehicle ID. In the second embodiment, instead of this, a parking ticket management number as user - specific information is issued, and a technique for associating the user's purchase record with the parking ticket management number will be described.

[0047] Figure 6 is a functional block diagram showing an example of an electronic parking ticket management system according to the second embodiment. The processor 201 of the center server 200 includes a generation unit 201d. The generation unit 201d generates management information corresponding to the vehicle ID restored by the decoding unit 201b. In this embodiment, this management information is referred to as a parking ticket management number. The parking ticket management number is registered in the table 300b of the database 300 in association with the vehicle ID and the user ID. Further, the transmission unit 201c transmits the parking ticket management number to the user device 10.

[0048] Figure 7 is a sequence diagram showing an example of a processing procedure in the system shown in Figure 6. In Figure 7, first, when the mobility 20 enters the parking lot from the gate, the vehicle ID is passed from the in-vehicle device 21 to the roadside unit 40. Then, the roadside unit 40 encrypts the vehicle ID (step S1) and transmits the encrypted vehicle ID to the center server 200. The center server 200 decrypts the vehicle ID (step S2) and generates a parking ticket management number corresponding to the restored vehicle ID (step S10). The generated parking ticket management number is registered in the table 300b (Figure 6) in association with the restored vehicle ID. Next, the center server 200 encodes this parking ticket management number and transmits it to the user device 10 in a form such as a barcode (step S11).

[0049] When the user shops at the store, the user presents the barcode (QR code (registered trademark)) displayed on the user device 10 each time they shop and has it read by the code reader 76. The code reader 76 reads the parking ticket management number from the user device 10 and notifies the POS server 70. The POS server 70 passes the user's purchase information together with the notified parking ticket management number to the service providing server 60. The service providing server 60 performs a discount determination (step S4) based on the parking ticket management number and further performs a discount amount calculation (step S5). Then, it waits for the mobility to leave the warehouse.

[0050] When the user's shopping in the store is completed and when the in-vehicle device 21 exits the user's mobility, the in-vehicle device 21 accesses the roadside unit 40 again. Then, the roadside unit 40 acquires the vehicle ID. The vehicle ID read by the roadside unit 40 is encrypted at the roadside unit 40 (step S9), and the encrypted information is transmitted to the center server 200 again. When the center server 200 receives this encrypted information, it decrypts it to restore the vehicle ID (step S12). Further, the center server 200 reads out the parking ticket management number corresponding to the restored vehicle ID from the table 300b (Fig. 6) (step S13). Then, this parking ticket management number is notified to the service providing server 60 via the parking lot management server 30.

[0051] The service providing server 60 calculates the settlement amount for the specified user (step S6), and notifies the in-vehicle device 21 via the parking lot management server 30 and the roadside unit 40. After that, when the cashless settlement is completed by the same procedure as in the first embodiment (step S7), the payment amount is notified to the parking lot management server 30 via the roadside unit 40. Then, the parking lot management server 30 transmits a message transmission request to the center server 200. The center server 200 that has received this request transmits a message such as "Thank you" to the user device 10, and notifies the user that the settlement has been completed (step S8).

[0052] Fig. 8 is a diagram for explaining the operation in the sequence diagram shown in Fig. 7. In Fig. 8, the center server 200 that has received the encrypted vehicle ID decrypts the vehicle ID, and refers to the database 300 to specify the corresponding user ID. Further, the center server 200 generates a parking ticket management number and registers it in the table 300b. The center server 200 transmits a barcode based on the parking ticket management number to the user by mail.

[0053] The barcode displayed on the user device 10 is read each time shopping is done, and the settlement information, together with the parking ticket management number, is sent to the POS server 70 and the service providing server 60. The service providing server 60 performs a discount determination and stores the result while updating it for each user. When mobility is shipped out, the roadside unit 40 reads the vehicle ID again, encrypts it, and notifies the center server 200. The center server 200 transmits the parking lot management number to the service providing server 60 via the parking lot management server 30. The service providing server 60 notifies the parking lot management server 30 of the discount amount or the billing amount. Through the above procedures, when payment is made by wireless settlement, the settlement including the service is completed.

[0054] In the second embodiment, instead of the vehicle ID itself, a parking ticket management number, which is an electronic parking ticket, is newly issued. Then, the settlement and service provision in the store are carried out in association with the parking ticket management number. From these, the second embodiment can also obtain the same effects as the first embodiment. In addition, it is possible to prevent the vehicle ID from being inadvertently leaked and misused. Furthermore, since the correspondence between the vehicle ID and the parking lot management number is centrally managed by the center server 200, the center server 200 can manage the user's store visit history and perform statistical analysis.

[0055] [Third Embodiment] In the third embodiment, a technique for issuing / managing the parking ticket management number on the store side will be described. FIG. 9 is a functional block diagram showing an example of an electronic parking ticket management system according to the third embodiment. In FIG. 9, the parking lot management server 30 includes a processor 31. The processor 31 includes a generation unit 31a and a management information notification unit 31b as processing functions according to the embodiment. These are understood as processing functions implemented in a program pre-stored in the storage device of the parking lot management server 30.

[0056] The generation unit 31a generates a parking ticket management number corresponding to the vehicle ID passed from the roadside unit 40. The management information notification unit 31b notifies the center server 200 of the parking ticket management number and the encrypted vehicle ID.

[0057] The center server 200 registers the parking ticket management number notified from the parking lot management server 30 in the table 300b in association with the vehicle ID and the user ID. Further, the transmission unit 201c of the center server 200 transmits the parking ticket management number to the user device 10.

[0058] FIG. 10 is a sequence diagram showing an example of a processing procedure in the system shown in FIG. 9. In FIG. 10, first, when the mobility 20 enters the parking lot from the gate, the vehicle ID is passed from the in-vehicle device 21 to the roadside unit 40. Then, the roadside unit 40 encrypts the vehicle ID (step S1) and transmits it to the parking lot management server 30. The parking lot management server 30 generates a ticket management number based on the encrypted vehicle ID transferred from the roadside unit 40 (step S20), and sends the encrypted information and the management number (parking ticket management number) to the center server 200. The center server 200 decrypts the vehicle ID (step S2) and registers the parking ticket management number in the database 300. Then, the center server 200 converts the parking ticket management number into a barcode and transmits it to the user device 10. After that, when the user shops at the store, in the same procedure as in the second embodiment, the user presents the barcode (QR code (registered trademark)) displayed on the user device 10 each time they shop and has it read by the code reader 76. The code reader 76 reads the parking ticket management number from the user device 10 and notifies the POS server 70. The POS server 70 passes the user's purchase information to the service providing server 60 together with the notified parking ticket management number. The service providing server 60 performs a discount determination (step S4) based on the parking ticket management number and further performs a discount amount calculation (step S5). Then, it waits for the mobility to leave the warehouse. Furthermore, when the user's shopping in the store is completed and the user's mobility is about to leave the store, in the same procedure as in the second embodiment, the in-vehicle device 21 accesses the roadside unit 40 again. Then, the roadside unit 40 acquires the vehicle ID. The vehicle ID read by the roadside unit 40 is encrypted at the roadside unit 40 (step S9), and the encrypted information is transmitted to the center server 200 again. When the center server 200 receives the encrypted information, it decrypts it to restore the vehicle ID (step S12). Further, the center server 200 reads out the parking ticket management number corresponding to the restored vehicle ID from the table 300b (Fig. 6) (step S13). Then, the center server 200 notifies this parking ticket management number to the service providing server 60 via the parking lot management server 30. The service providing server 60 calculates the settlement amount for the specified user (step S6) and notifies the in-vehicle device 21 via the parking lot management server 30 and the roadside unit 40. Thereafter, when the cashless payment (step S7) is completed in the same procedure as in the first embodiment and the second embodiment, the payment amount is notified to the parking lot management server 30 via the roadside unit 40. Then, the parking lot management server 30 transmits a message transmission request to the center server 200. The center server 200 that has received this request transmits a completion message to the user device 10.

[0059] Fig. 11 is a diagram for explaining the operation in the sequence diagram shown in Fig. 10. In Fig. 11, the parking lot management server 30 that has received the encrypted vehicle ID generates a parking ticket management number and sends it to the center server 200 together with the vehicle ID. The center server 200 sends a barcode based on the parking ticket management number to the user by email. After that, when the payment by wireless payment is made through the same procedure as in the second embodiment, the payment including the service is completed.

[0060] In the third embodiment, the parking ticket management number is generated on the store side. This makes it possible to reduce the load on the center server 200. From these facts, the third embodiment also enables the provision of services for each user in cashless settlement. As a result, it becomes possible to provide a variety of services.

[0061] [Supplementary Explanation] Here, the method of sending a request to the center server 200 will be supplemented. For example, in FIGS. 4, 7, and 10, it was described that the settlement result (message) is sent to the user device 10 at the time of settlement completion. This is realized by requesting the parking lot management server 30 to send the settlement message. Technically, for example, in the form of an HTTP request using a Web API, the parking lot management server 30 can request the center server 200 to send the settlement message.

[0062] Similarly, the issuance of the parking ticket management number at the time of entry of the mobility, the authentication and confirmation of the vehicle ID at the time of exit, etc. can also be realized by sending a request from the parking lot management server 30 to the center server 200. In addition, by sending a predetermined request message and sending it from the parking lot management server 30, various services can be received from the center server 200.

[0063] <Second Configuration> In the first configuration, the configuration in which the association between the mobility and the user is implemented at a center separate from the store was described. In the second configuration, a system in which the association between the mobility and the user is implemented on the store side will be described.

[0064] FIG. 12 is a system diagram showing another example of the electronic parking ticket management system according to the embodiment. This system includes a roadside unit 40 installed at the gate of the parking lot and a parking lot management server 30 communicably connected to the roadside unit 40. In FIG. 12, the parking lot management server 30 is connected to the mobile communication network 400 and can communicate with the user device 10 via the base station 50. The parking lot management server 30 is communicably connected to a database 80. Further, the roadside unit 40 transmits the detected vehicle ID to the parking lot management server 30 as plain text.

[0065] FIG. 13 is a diagram for explaining the cooperation with the store of the electronic parking ticket management system shown in FIG. 12. A table in which the vehicle ID and the user ID of the individual user are associated in advance is registered in advance in the database 80 accessible from the parking lot management server 30. The parking lot management server 30 refers to the database 80 and acquires the email address corresponding to the vehicle ID. Then, the parking lot management server 30 generates an electronic parking ticket such as a barcode or a QR code (registered trademark) from the vehicle ID and issues it to the acquired email address. Next, an embodiment based on the above configuration will be described.

[0066] [Fourth Embodiment] FIG. 14 is a functional block diagram showing an example of the electronic parking ticket management system according to the fourth embodiment. In FIG. 14, the parking lot management server 30 stores a table 80a associating the vehicle ID and the user ID in the database 80. The processor 31 of the parking lot management server 30 includes an acquisition unit 31c, a specifying unit 31d, and a transmission unit 31e. The acquisition unit 31c acquires the vehicle ID via the roadside unit 40. The specifying unit 31d specifies by referring to the user ID corresponding to the acquired vehicle ID and the table 80a of the database 80. The transmission unit 31e transmits the vehicle ID as parking ticket information to the user device 10 possessed by the user of the specified user ID.

[0067] FIG. 15 is a sequence diagram showing an example of a processing procedure in the system shown in FIG. 14. In FIG. 15, first, when the mobility 20 enters the parking lot from the gate, the vehicle ID is passed from the in-vehicle device 21 to the roadside unit 40. Then, the roadside unit 40 transmits the vehicle ID to the parking lot management server 30. The parking lot management server 30 identifies the user ID from the vehicle ID and transmits the encoded vehicle ID to the user device 10 (step S3). When the user shops at the store, the user presents the barcode (QR code (registered trademark)) displayed on the user device 10 each time they make a purchase and has it read by the barcode reader 76. The barcode reader 76 reads the vehicle ID from the user device 10 and notifies the POS server 70. The POS server 70 passes the vehicle ID acquired by the barcode reader 76 and the user's purchase information to the service providing server 60. The service providing server 60 performs a discount determination (step S4) and a discount amount calculation (step S5) based on the vehicle ID and waits for the mobility to leave the warehouse.

[0068] When the user's shopping at the store is completed and the user's mobility leaves the warehouse, the in-vehicle device 21 accesses the roadside unit 40 again. Then, the roadside unit 40 acquires the vehicle ID. The vehicle ID read by the roadside unit 40 is notified to the service providing server 60 via the parking lot management server 30. The service providing server 60 calculates the settlement amount for the user (step S6) and notifies the in-vehicle device 21 via the parking lot management server 30 and the roadside unit 40. After that, when the cashless payment (step S7) is completed by the same procedure as in the first embodiment, the payment amount is notified to the parking lot management server 30 via the roadside unit 40. Then, the parking lot management server 30 transmits a completion message to the user device 10.

[0069] FIG. 16 is a diagram for explaining the operation in the sequence diagram shown in FIG. 15. In FIG. 16, the parking lot management server 30 that has received the vehicle ID identifies the user ID from the table 80a and sends the barcode of the vehicle ID to the user by email.

[0070] The barcode displayed on the user device 10 is read each time shopping is done, and the settlement information, together with the vehicle ID, is sent to the POS server 70 and the service providing server 60. The service providing server 60 performs discount determination and stores the result while updating it for each user. When the vehicle departs from the mobility, the roadside unit 40 reads the vehicle ID again and notifies the parking lot management server 30. The parking lot management server 30 inquires of the service providing server 60 about the discount information using the vehicle ID as a key.

[0071] The service providing server 60 notifies the roadside unit 40 and the in-vehicle device 21 of the discount amount via the parking lot management server 30. Through the above procedures, when payment is made by wireless settlement, the settlement including the service is completed.

[0072] In the fourth embodiment, processes such as the association between the vehicle ID and the user ID, the issuance of the electronic parking ticket (barcode), and the sales management are executed in the store without passing through the center server 200. Since the vehicle ID is pre-associated with the user ID, the vehicle ID can be mailed to the user device 10 upon arrival, and the purchase history can be managed in the store. Therefore, also according to the fourth embodiment, it becomes possible to provide services for each user by cashless settlement. Consequently, it becomes possible to provide various services.

[0073] [Fifth Embodiment] FIG. 17 is a functional block diagram showing an example of an electronic parking ticket management system according to the fifth embodiment. In FIG. 17, the processor 31 of the parking lot management server 30 includes a generation unit 31f. The generation unit 31f generates a parking ticket management number corresponding to the vehicle ID notified from the roadside unit 40. The parking ticket management number is registered in the table 80b of the database 80 in association with the vehicle ID and the user ID. Further, the transmission unit 31e transmits the parking ticket management number to the user device 10.

[0074] FIG. 18 is a sequence diagram showing an example of a processing procedure in the system shown in FIG. 17. In FIG. 18, first, when the mobility 20 enters the parking lot from the gate, the vehicle ID is passed from the in-vehicle device 21 to the roadside unit 40. The roadside unit 40 transmits the vehicle ID to the parking lot management server 30. The parking lot management server 30 generates a parking ticket management number from the notified vehicle ID (step S20), registers it in the table 80b, and transmits it to the user device 10 in the form of a barcode (QR code (registered trademark)) (step S3).

[0075] When the user shops at the store, the user presents the barcode (QR code (registered trademark)) displayed on the user device 10 each time they make a purchase and has it read by the code reader 76. The code reader 76 reads the vehicle ID from the user device 10 and notifies the POS server 70. The POS server 70 passes the purchase information of the user to the service providing server 60 together with the parking ticket management number obtained from the code reader 76. The service providing server 60 performs discount determination (step S4) and discount amount calculation (step S5) based on the parking ticket management number, and waits for the mobility to leave the warehouse.

[0076] When the user finishes shopping at the store and the user's mobility leaves the warehouse, the in-vehicle device 21 accesses the roadside unit 40 again. Then the roadside unit 40 acquires the vehicle ID. The vehicle ID read by the roadside unit 40 is notified to the parking lot management server 30. The parking lot management server 30 refers to the table 80b (FIG. 17) and converts this vehicle ID into a parking ticket management number (step S21). Then, this parking ticket management number is notified to the service providing server 60. The service providing server 60 calculates the settlement amount for the user specified based on the parking ticket management number (step S6), and notifies the in-vehicle device 21 via the parking lot management server 200 and the roadside unit 40. After that, when the cashless payment (step S7) is completed, the payment amount is notified to the parking lot management server 30 via the roadside unit 40. Then, a completion message is transmitted from the parking lot management server 30 to the user device 10.

[0077] FIG. 19 is a diagram for explaining the operation in the sequence diagram shown in FIG. 18. In FIG. 19, the parking lot management server 30 that has received the vehicle ID generates a parking ticket management number and registers it in the table 80b. Further, the parking lot management server 30 emails the barcode of the parking ticket management number to the user.

[0078] The barcode displayed on the user device 10 is read every time shopping is done, and the settlement information is sent to the POS server 70 and the service providing server 60 together with the parking ticket management number. The service providing server 60 performs a discount determination and stores the result. When the mobility is shipped out, the vehicle ID is notified to the parking lot management server 30, and the discount amount, the billing amount, etc. are queried to the service providing server 60, and the result is responded to the parking lot management server 30. Through the above procedures, when payment is made by wireless payment, the settlement including the service is completed.

[0079] In the fifth embodiment, a parking ticket management number based on the vehicle ID is issued. And the settlement in the store and the provision of the service are carried out in association with the parking ticket management number. Moreover, a series of processes are completed in the store without going through the center server 200. From these, the fifth embodiment can also obtain the same effect as the fourth embodiment.

[0080] As described above, according to each of the above embodiments, it is possible to provide services for each user by cashless settlement. As a result, it is possible to provide various services.

[0081] Note that the present invention is not limited to the above embodiments. For example, as shown in FIG. 20, the roadside unit 40 and the parking lot management server 30 may be directly connected. Further, the roadside unit 40 may be a camera that reads the vehicle number etc. from the license plate 24 installed on the mobility 20. Also, the service providing server 60 and the POS server 70 may be configured by the same server.

[0082] In the electronic parking ticket management system of the embodiment, instead of an email address, an ID such as that of an SNS (social networking service) may be used. In this case, the electronic parking ticket management system of the embodiment may send a message using the SNS or the like instead of an email. Furthermore, a dedicated application may be used to notify the electronic parking ticket in a push type. At that time, the user's preferences may be analyzed by a method such as collaborative filtering, and advertisements and coupon information according to the result may be notified together with the barcode information.

[0083] Also, in the embodiment, a barcode or a QR code (registered trademark) was generated from the vehicle ID and sent to the user device 10. Instead of this, a number or the like corresponding to the vehicle ID may be sent to the user device 10. In this case, a text reading function (OCR (Optical Character Recognition)) is implemented in the code reader 76, and authentication based on text is performed. Alternatively, the characters (letters and numerical values) displayed on the user device 10 may be manually input.

[0084] Also, in the embodiment, the registration of the parking ticket management number generated from the vehicle ID in the table 300b was described. Instead of this, for example, if a parking ticket management number can be uniquely generated from the vehicle ID using a hash function or the like, it is not necessarily required to register it.

[0085] Furthermore, in each of the above embodiments, the description was made without distinguishing between the parking lot operator and the store operator. While there is such a form, for example, in a local shopping street, there may be a case where the parking lot operator and the store operator are different. Of course, the present invention can also cope with such a form.

[0086] FIG. 21 is a diagram showing an example of a case where a parking lot and a store are operated by different business entities. FIG. 21 shows a case where this type of service operation form is applied to the system described in the second embodiment. Of course, in the systems of the first, third to fifth embodiments, cases where a parking lot and a store are operated by different business entities can also be applied.

[0087] In FIG. 21, the parking lot management server 30 and the service providing server 60 belong to the parking lot operator. The store operator is provided with a POS server 70 that can communicate with the service providing server 60. Then, the parking lot management server 30 can communicate with the center server 200 to provide services such as linked management of vehicle IDs and personal IDs, cashless settlement, and prevention of leakage of personal information. Such a system configuration can also provide various services.

[0088] Each device in the above-described embodiment can be transferred to the administrator of each device, etc. with a program for executing the above-described processing stored in a ROM or an auxiliary storage device, etc. However, the device may be transferred to the administrator, etc. in a state where the program is not stored in a ROM or an auxiliary storage device, etc. Also, the device may be transferred to the administrator, etc. in a state where a program different from the program is stored in a ROM or an auxiliary storage device, etc. And the program may be separately transferred to the administrator, etc. and written into a ROM or an auxiliary storage device, etc. under the operation of the administrator or a service technician, etc. The transfer of the program at this time can be realized by recording it on a removable storage medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by downloading via the Internet or a LAN.

[0089] Although some embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalent scope thereof.

Explanation of Reference Numerals

[0090] 10… User device, 15… In-store network, 20… Mobility, 21… On-vehicle device, 24… License plate, 30… Parking lot management server, 31… Processor, 31a… Generation unit, 31b… Management information notification unit, 31c… Acquisition unit, 31d… Identification unit, 31e… Transmission unit, 31f… Generation unit, 40… Roadside unit, 41… Processor, 41a… Detection unit, 41b… Encryption unit, 41c… Notification unit, 50… Base station, 60… Service providing server, 61… Processor, 61a… Record management unit, 61b… Service providing unit, 70… POS server, 71… Processor, 71a… Reading unit, 75… POS terminal, 76… Code reader, 80… Database, 80a… Table, 80b… Table, 90… Cash register, 100… Cloud, 200… Center server, 201… Processor, 201a… Identification unit, 201b… Decryption unit, 201c… Transmission unit, 201d… Generation unit, 300… Database, 300a… Table, 300b… Table, 400… Mobile communication network.

Claims

1. A roadside unit installed in a parking lot; A center server communicably connected to the roadside device; A POS system that manages user purchasing information; a service providing server that provides a service to the user; The roadside unit includes: A detection unit that detects a vehicle ID that identifies a vehicle entering or leaving the parking lot; an encryption unit that encrypts the detected vehicle ID to generate encrypted information; a notification unit that notifies the center server of the encrypted information, The center server includes: a database in which the vehicle ID and a user ID for identifying a user are registered; a decryption unit that decrypts the notified encrypted information to restore the vehicle ID; an identification unit that identifies a user ID of a user corresponding to the restored vehicle ID by referring to the database; a transmission unit that transmits electronic parking ticket information in which the vehicle ID is encoded to a user device having the user ID identified by the identification unit, The POS system includes: a reading unit that reads the electronic parking ticket information from the user device when acquiring the purchase information, The service providing server includes: a record management unit that manages purchase information for each user based on the electronic parking ticket information and the purchase information read by the POS system; a service providing unit that determines whether a discount is applicable based on the vehicle ID and the purchase information for each user, calculates a discount amount if the user is eligible for the discount, and notifies the user of a parking fee settlement amount. Electronic parking ticket management system.

2. In the electronic parking ticket management system, The center server includes: The parking ticket information storing unit stores the parking ticket information in a storage device that stores the parking ticket information and the parking ticket management number ...

2. The electronic parking ticket management system according to claim 1.

3. The electronic parking ticket management system further includes a parking lot management server communicably connected to the roadside device, The notification unit of the roadside device notifying the parking lot management server of the encrypted information encrypted by the encryption unit; The parking lot management server includes: a generation unit that generates a corresponding parking ticket control number from the encrypted information notified from the roadside device; a management information notifying unit that notifies the center server of the parking ticket management number and the encrypted information, The transmission unit of the center server transmitting electronic parking ticket information in which the parking ticket management number is encoded to a user device possessed by the user having the specified user ID; 2. The electronic parking ticket management system according to claim 1.

4. A roadside unit installed in a parking lot; A parking lot management server connected to the roadside device so as to be able to communicate with the roadside device; A POS system that acquires user purchasing information; a service providing server that provides a service to the user; The roadside unit includes: A detection unit that detects a vehicle ID that identifies a vehicle entering or leaving the parking lot; a notification unit that notifies the center server of the encrypted information; The parking lot management server includes: A database in which the correspondence between vehicle IDs and user IDs is registered in advance; an acquisition unit that acquires the vehicle ID from the roadside device; an identification unit that identifies a user ID corresponding to the acquired vehicle ID by referring to the database; a transmission unit that transmits electronic parking ticket information to a user device of the user having the specified user ID; The POS system includes: a reading unit that reads the electronic parking ticket information from the user device when acquiring the purchase information, The service providing server includes: a record management unit that manages the purchase information for each user based on the electronic parking ticket information read by the POS system and the purchase information; a service providing unit that determines whether a discount is applicable based on the vehicle ID and the purchase information for each user, calculates a discount amount if the user is eligible for the discount, and notifies the user of a parking fee settlement amount. Electronic parking ticket management system.

5. In the electronic parking ticket management system, The parking lot management server includes: a generating unit that generates a corresponding parking ticket control number from the vehicle ID notified from the roadside device, and registers the parking ticket control number in association with the vehicle ID and the user ID; The transmission unit transmits electronic parking ticket information in which the parking ticket management number is encoded to a user device possessed by a user having a user ID identified by the identification unit.

5. The electronic parking ticket management system according to claim 4.

6. A center server that is communicably connected to a roadside device installed in a parking lot, A database in which a correspondence between a vehicle ID and a user ID for identifying a user is registered; a decryption unit that decrypts the encrypted information notified from the roadside device to restore the vehicle ID; an identification unit that identifies a user ID of a user corresponding to the restored vehicle ID by referring to the database; a generation unit that generates a parking ticket control number corresponding to the vehicle ID restored by the decryption unit, and registers the parking ticket control number in association with the vehicle ID and the user ID; a transmission unit that transmits electronic parking ticket information obtained by encoding the parking ticket management number and the vehicle ID to a user device possessed by a user having a user ID identified by the identification unit; A center server comprising:

7. An electronic parking ticket management method for an electronic parking ticket management system including a roadside device installed in a parking lot, a center server communicatively connected to the roadside device, a POS system for managing user purchasing information, and a service providing server for providing services to the user, comprising: a step of detecting a vehicle ID that identifies a vehicle entering or leaving the parking lot by the roadside device; the roadside device encrypting the detected vehicle ID to generate encrypted information; a step of the roadside device notifying the center server of the encrypted information; a step of registering, in a database, a correspondence between the vehicle ID and a user ID that identifies a user, by the center server; the center server decrypting the notified encrypted information to restore the vehicle ID; a step of the center server referring to the database to identify a user ID of a user corresponding to the restored vehicle ID; a step of the center server transmitting electronic parking ticket information in which the vehicle ID is encoded to the user device of the specified user ID; a step of the POS system reading the electronic parking ticket information from the user device when acquiring the purchase information; the service providing server managing purchase information for each user based on the electronic parking ticket information and the purchase information read by the POS system; The electronic parking ticket management method includes a process in which the service providing server determines whether the vehicle is eligible for a discount based on the vehicle ID and the purchasing information for each user, and if so, calculates the discount amount and notifies the user of the amount of the parking fee to be paid.

Images