JP7493981B2 - Electronic parking ticket management system, center server, parking lot management server, and electronic parking ticket management method - Google Patents

Description

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

When you use a parking lot at a supermarket, shopping mall, etc., you are charged a parking fee. However, there are well-known services that offer free parking for customers who shop at the store, for example for two hours, or discounts on parking fees depending on the amount of their purchases. To provide this type of service, a parking ticket is issued at the gate at the entrance to the parking lot, and payment is made at a payment machine before leaving.

JP 2016-157241 A

Parking tickets have numbers and other information magnetically recorded to identify the user. By reading this with a payment machine or the like, operators can identify the user and provide discount services. However, with the growing demand for cashless payments, there is a demand to be able to handle physical electronic parking tickets in place of paper parking tickets.

While electronic parking tickets are convenient, they require careful consideration of security and the confidentiality of personal information. For example, there is a need to link the entering vehicle with the user who is the target of the service reliably and without fail. Furthermore, with existing technology, a system for managing electronic parking tickets needs to be built for each service provider, which leaves room for consideration in terms of cost. Furthermore, there is a demand for a system that can provide a variety of services beyond just cashless payment.

The objective is to provide an electronic parking ticket management system, a server device, and a service providing system that can provide a variety of services.

According to an embodiment, the electronic parking ticket management system includes a roadside device installed in a parking lot , a center server communicably connected to the roadside device, a POS system that manages purchase information of users, and a service providing server that provides services to users. The roadside device includes a detection unit, an encryption unit, and a notification unit. The detection unit detects a vehicle ID that identifies 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 center server of the encrypted information. The center server includes a database in which the correspondence between the vehicle ID and the user ID that identifies the user is registered, a decryption unit, an identification unit, and a transmission unit. The decryption unit decrypts the notified encrypted information to restore the vehicle ID. The identification unit refers to the database to identify the user ID of the user corresponding to the restored vehicle ID. The transmission unit transmits electronic parking ticket information in which the vehicle ID is encoded to the user device of 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 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 a discount is applicable based on the vehicle ID and the purchase information for each user, calculates the discount amount if applicable, and notifies the exiting vehicle of the amount of the parking fee to be paid.

FIG. 1 is a system diagram showing an example of an electronic parking ticket management system according to an embodiment. FIG. 2 is a diagram for explaining cooperation between the electronic parking ticket management system shown in FIG. 1 and a store. FIG. 3 is a functional block diagram showing an example of an electronic parking ticket management system according to the first embodiment. FIG. 4 is a sequence diagram showing an example of a processing procedure in the system shown in FIG. FIG. 5 is a diagram for explaining the operation in the sequence diagram shown in FIG. FIG. 6 is a functional block diagram showing an example of an electronic parking ticket management system according to the second embodiment. FIG. 7 is a sequence diagram showing an example of a processing procedure in the system shown in FIG. FIG. 8 is a diagram for explaining the operation in the sequence diagram shown in FIG. FIG. 9 is a functional block diagram showing an example of an electronic parking ticket management system according to the third embodiment. FIG. 10 is a sequence diagram showing an example of a processing procedure in the system shown in FIG. FIG. 11 is a diagram for explaining the operation in the sequence diagram shown in FIG. FIG. 12 is a system diagram showing another example of an electronic parking ticket management system according to an embodiment. FIG. 13 is a diagram for explaining cooperation between the electronic parking ticket management system shown in FIG. 12 and a store. FIG. 14 is a functional block diagram showing an example of an electronic parking ticket management system according to the fourth embodiment. FIG. 15 is a sequence diagram showing an example of a processing procedure in the system shown in FIG. FIG. 16 is a diagram for explaining the operation in the sequence diagram shown in FIG. FIG. 17 is a functional block diagram showing an example of an electronic parking ticket management system according to the fifth embodiment. FIG. 18 is a sequence diagram showing an example of a processing procedure in the system shown in FIG. FIG. 19 is a diagram for explaining the operation in the sequence diagram shown in FIG. FIG. 20 is a diagram showing an example of a system in which a road-side device 40 and a parking lot management server 30 are directly connected to each other. FIG. 21 is a diagram showing an example of a case where a parking lot and a store are operated by different business entities.

In the embodiment, a system is described that provides services such as fee discounts to users who use paid parking lots, depending on their shopping history at related stores, etc. Use of parking lots is not limited to personal cars. In other words, so-called car sharing services, in which multiple people share a vehicle, have become known in recent years, and such forms are 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, two-wheeled motor vehicles, bicycles, public transportation, etc.) are collectively called mobility, whether privately owned or shared.

<First Configuration>
In the first configuration, a system in which a sales management system within a store and a center system independent of the store cooperate with each other will be described.

Figure 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 connected to the roadside unit 40 so that it can communicate with the roadside unit 40. The system in Figure 1 also includes a center server 200 connected to the roadside unit 40 so that it can communicate with the parking lot management server 30.

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 a mobile communication network 400. The center server 200 can communicate with a user device 10 carried by a user from the cloud 100, for example, via a base station 50 of the mobile communication network 400. Alternatively, the center server 200 can communicate with the user device 10 via an access point of a wireless LAN (Local Area Network) such as Wi-Fi (registered trademark). The access point can use existing infrastructure installed inside and outside the store.

The mobility 20 on which the user rides is equipped with an onboard device 21. The onboard device 21 pre-stores a unique onboard device ID (IDentification) for identifying the mobility 20. When the mobility 20 enters the parking lot through a gate, the roadside device 40 communicates with the onboard device 21, detects the onboard device ID, and reads its contents. Here, the roadside device 40 may be, for example, a device for electronic toll collection (ETC) equipped with a dedicated short-range communications (DSRC) function.

The vehicle-mounted device ID is, for example, a wireless call number (WCN) or a vehicle-mounted device management number. In the embodiment, the vehicle-mounted device ID is described as a vehicle ID for identifying the mobility 20. In addition, identification information such as the vehicle number written on the license plate or the vehicle registration number can also be used as the vehicle ID.

The roadside unit 40 encrypts the detected vehicle ID using key information and transmits it to the center server 200. The center server 200 also has key information corresponding to this key information, and decrypts the encrypted vehicle ID. This makes it possible to prevent the vehicle ID from being read by the parking lot management server 30 or on intermediate routes, and to prevent data from being stolen.

Figure 2 is a diagram for explaining the cooperation between the electronic parking ticket management system shown in Figure 1 and a store. The store is equipped with a parking lot management server 30, a service providing server 60, a POS server 70, and a POS terminal 75. These are connected to an in-store network 15 such as a LAN (Local Area Network). A 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.

In FIG. 2, a center server 200 is provided at the center of the cloud 100. When the mobility 20 approaches the roadside device 40, the vehicle ID is read from the vehicle-mounted 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.

A table in which the vehicle ID and the user ID of each user are associated with each other is registered in advance in a database 300 accessible from the center server 200. The user ID is, for example, an email address of the user device 10 (such as a mobile terminal such as a smartphone) owned by the user. In addition, information that can uniquely identify the user, such as a telephone 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, a tablet or a watch-type device can also be used as the user device 10. The center server 200 refers to the database 300 and acquires an email address corresponding to the vehicle ID. The center server 200 then 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, the mobility 20 and the user (user device 10) can be uniquely associated with each other by having the user device 10 read the electronic parking ticket, which can be useful for providing various services. Next, an embodiment based on the above configuration will be described.

[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 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 the service to the user. The parking lot management server 30 is connected to the roadside device 40 and the center server 200. Here, 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 device 40 are all computers equipped with a memory and a processor.

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

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

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

The center server 200 can access the database 300 and refer to the table 300a. The table 300a is a table that preregisters the correspondence between the vehicle ID and the email address (user ID) of the user associated with the vehicle. This email address is typically the email address of the user device 10.

The center server 200 includes a processor 201. The processor 201 includes an identification unit 201a, a decryption unit 201b, and a transmission unit 201c as processing functions related to the embodiment. These are understood to be processing functions implemented in a program pre-stored in a storage device of the center server 200.

First, the decryption unit 201b decrypts the encrypted information notified from the roadside device 40 to restore the vehicle ID.
The identification unit 201a identifies an email address (user ID) corresponding to the restored vehicle ID by referring to the table 300a of the database 300. 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".

The sending unit 201c sends the parking ticket information to the specified email address. This causes the parking ticket information to be delivered to the user device 10. In the first embodiment, the parking ticket information is the vehicle ID itself, or code information such as a barcode or QR code (registered trademark) that encodes the vehicle ID.

The POS server 70 includes a processor 71. The processor 71 includes a reading unit 71a as a processing function related to the embodiment. The reading unit 71a is understood as a processing function implemented in a program pre-stored in a storage device of the POS server 70. The reading unit 71a acquires purchase information when a user pays for purchases at a store. At that time, the reading unit 71a reads parking ticket information from the user device 10 using a code reader 76.

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

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

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

The center server 200 receives this encrypted information and decrypts it to restore the vehicle ID (step S2).
The center server 200 then generates a barcode or a QR code (registered trademark) from the vehicle ID, and transmits a message (code information) including image data of the code to the user device 10 in email format (step S3).

When a user shops at a store, the user presents a barcode (QR code (registered trademark)) displayed on the user device 10 each time he or she makes a purchase, and the barcode is read by the code reader 76. The code reader 76 reads the vehicle ID from the image of the barcode and notifies the POS server 70. The POS server 70 passes the user's purchasing information to the service providing server 60 together with the notified vehicle ID.

The service providing server 60 determines whether or not a discount is applied to the user based on the purchase information for each user acquired from the POS server 70 (step S4). If it is determined that a discount is applied, the service providing server 60 calculates and stores the discount amount based on the purchase amount and the parking time, etc. (step S5). Then , the service providing server 60 waits for the mobility to leave the garage.

When the user finishes shopping at the store and leaves the vehicle, the vehicle-mounted device 21 again accesses the roadside device 40. The roadside device 40 then obtains the vehicle ID, encrypts the 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.

The service providing server 60 calculates the settlement amount based on the discount service for the user with the identified user ID (step S6) , and notifies the vehicle-mounted device 21 via the parking lot management server 30 and the roadside device 40.
The vehicle-mounted device 21 pays the notified settlement amount by card payment or the like (step S7). The user may also be allowed to make payment at the settlement machine 90 (FIG. 2) at his/her discretion. When the payment is completed , the vehicle-mounted device 21 notifies the parking lot management server 30 of the payment amount via the roadside device 40. In this manner, the settlement is completed.
In response to this, the parking lot management server 30 transmits a message transmission request to the center server 200. Upon receiving this request, the center server 200 transmits a message such as "Thank you" to the user device 10, and notifies the user that the payment has been completed (step S8).

Figure 5 is a diagram for explaining the action in the sequence diagram shown in Figure 4. In the bottom part of the diagram, 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 to encrypt the information using a method such as using time as a seed so that the encrypted information does not become constant.

The center server 200 receives the encrypted vehicle ID, decrypts it, and uniquely identifies the entered vehicle and the user from the vehicle ID and user ID that are linked and managed in advance in the database 300. A table showing the correspondence between vehicle IDs and user IDs can be obtained, for example, as registration information from a web registration system, or from an interface that links with a car sharing operating company.

The center server 200 sends a barcode based on the vehicle ID to the user by email. At this time, to prevent the barcode from being misused, the barcode may be updated and redistributed at regular intervals.

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 along with the vehicle ID. The service providing server 60 performs discount determination and stores the results while updating them for each user.

When the user has finished shopping and leaves the parking lot, the roadside unit 40 reads the vehicle ID again. This vehicle ID is encrypted again and notified to the center server 200 via the parking lot management server 30. Again, it is preferable to prevent the encrypted information from becoming constant, for example by using a time seed. After decrypting the vehicle ID, the center server 200 transmits 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 amount charged. This information is passed to the vehicle-mounted unit 21 via the roadside unit 40, and payment is made wirelessly.

As described above, in the first embodiment, the roadside device 40 acquires the vehicle ID from the vehicle-mounted 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 acquired from the center server 200 in a code. Then, the entered vehicle and the user can be uniquely identified from the vehicle ID and user ID that are linked and managed in advance in the database 300. In other words, the purchase history and vehicle ID for each user can be associated and managed, and it is possible to correctly determine whether or not to provide a service when leaving the parking lot and calculate the service amount (discount amount).

In other words, when the vehicle ID is obtained from the vehicle-mounted device 21, a unique code is sent to the user device 10. By presenting the code each time a payment is made at a store, a purchase history is accumulated at the store. When the vehicle leaves the storehouse, the roadside unit 40 reads the vehicle ID again, and the corresponding settlement amount is notified to the vehicle-mounted device 21. Then, payment is carried out wirelessly between the roadside unit 40 and the vehicle-mounted device 21.

In this way, settlement is automatically performed when the vehicle leaves the parking lot, and the entire process can be made cashless unless the user wishes to pay in cash. Furthermore, no paper parking ticket is required throughout the process, and the fact that the user is using the parking lot is verified by a barcode or the like displayed on the user device 10. This makes it possible to realize a payment service using electronic parking tickets.

Moreover, the linking management between the vehicle ID and the user ID is performed by the center server 200. In other words, since the electronic parking ticket management function is implemented as SaaS (Software as a Service), it can be used as a service from the cloud from the store's perspective. This allows the functions for realizing the electronic parking ticket to be shared by multiple service providers and store operators, and can be used in an integrated manner. Moreover, since the vehicle ID is encrypted and exchanged between the roadside device 40 and the center server 200, there is no risk of data being stolen by other operators. Furthermore, since the correspondence between the vehicle ID and the user ID is managed centrally by the center server 200, the center server 200 can manage the user's store visit history and perform statistical analysis.

From these points, according to the first embodiment, it is possible to provide services to each user by cashless payment. 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, it is possible to optimize the system construction cost and operation cost from the viewpoint of the whole society. In other words, for store operators, it is not necessary to have a system that provides services by associating users with electronic parking tickets, so it is possible to reduce the cost for improving user services. For payment service operators, since they can receive system usage fees from store operators in a subscription format or the like, it brings regular profits. In other words, it is possible to build a system that is advantageous for both the operator who operates the store and the operator who provides the payment service. 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 a variety of services.

Second Embodiment
In the first embodiment, the purchasing history of the user is managed in association with the vehicle ID. In the second embodiment, instead of this, a parking ticket management number is issued as user identification information, and the purchasing history of the user is associated with the parking ticket management number.

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 decryption unit 201b. This management information is referred to as a parking ticket management number in the embodiment. The parking ticket management number is registered in table 300b of database 300 in association with the vehicle ID and the user ID. Furthermore, the transmission unit 201c transmits the parking ticket management number to the user device 10.

FIG. 7 is a sequence diagram showing an example of a processing procedure in the system shown in FIG.
7, first, when the mobility 20 enters the parking lot through the gate, the vehicle ID is passed from the vehicle-mounted device 21 to the roadside device 40. The roadside device 40 then 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 (FIG. 6) in association with the restored vehicle ID.
Next, the center server 200 encodes the parking ticket control number and transmits it to the user device 10 in the form of a barcode or the like (step S11).

When a user shops at a store, the user presents a barcode (QR code (registered trademark)) displayed on the user device 10 each time he or she makes a purchase, and the barcode is read by the code reader 76. The code reader 76 reads the parking ticket control 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 control number.
The service providing server 60 performs a discount determination (step S4) based on the parking ticket control number, and further performs a discount amount calculation (step S5) , and then waits for the mobility to leave the parking lot.

When the user finishes shopping at the store and leaves the vehicle , the vehicle-mounted device 21 again accesses the roadside device 40. The roadside device 40 then acquires the vehicle ID. The vehicle ID read by the roadside device 40 is encrypted in the roadside device 40 (step S9), and the encrypted information is again transmitted to the center server 200.
When the center server 200 receives the encrypted information, it decrypts it to restore the vehicle ID (step S12). The center server 200 then reads out the parking ticket control number corresponding to the restored vehicle ID from the table 300b (FIG. 6) (step S13) . The center server 200 then notifies the service providing server 60 of the parking ticket control number via the parking lot management server 30 .

The service providing server 60 calculates the settlement amount for the identified user (step S6) and notifies the vehicle-mounted device 21 via the parking lot management server 30 and the roadside device 40.
Thereafter, when the cashless payment is completed through the same procedure (step S7) as in the first embodiment , the payment amount is notified to the parking lot management server 30 via the roadside unit 40 .
The parking lot management server 30 then transmits a message transmission request to the center server 200. Upon receiving this request, the center server 200 transmits a message such as "Thank you" to the user device 10 to notify the user that the payment has been completed (step S8).

Figure 8 is a diagram for explaining the operation in the sequence diagram shown in Figure 7. In Figure 8, the center server 200 receives an encrypted vehicle ID, decrypts the vehicle ID, and identifies the corresponding user ID by referring to the database 300. Furthermore, the center server 200 generates a parking ticket management number and registers it in table 300b. The center server 200 sends a barcode based on the parking ticket management number to the user by email.

The barcode displayed on the user device 10 is read every time a purchase is made, and settlement information is sent to the POS server 70 and the service providing server 60 along with the parking ticket management number. The service providing server 60 performs a discount determination and stores the result while updating it for each user. When the mobility leaves the parking lot, 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 amount charged. After going through the above steps and making the payment via wireless payment, the payment including the service is completed.

In the second embodiment, a parking ticket control number, which is an electronic parking ticket, is newly issued instead of the vehicle ID itself. Then, payment within the store and the provision of services are performed in correspondence with the parking ticket control number. As a result, the second embodiment can achieve the same effects as the first embodiment. It is also possible to prevent the vehicle ID from being accidentally leaked and misused. Furthermore, since the correspondence between the vehicle ID and the parking lot control number is centrally managed by the center server 200, the user's store visit history can be managed by the center server 200 and statistically analyzed.

[Third embodiment]
In the third embodiment, a technology for issuing/managing a parking ticket control 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 generating unit 31a and a management information notifying unit 31b as processing functions according to the embodiment. These are understood as processing functions implemented in a program pre-stored in a storage device of the parking lot management server 30.

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

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

FIG. 10 is a sequence diagram showing an example of a processing procedure in the system shown in FIG.
10, first, when the mobility 20 enters the parking lot through the gate, the vehicle ID is passed from the in-vehicle device 21 to the roadside device 40. The roadside device 40 then encrypts the vehicle ID (step S1) and transmits it to the parking lot management server 30. The parking lot management server 30 generates a parking ticket control number using the encrypted vehicle ID transferred from the roadside device 40 (step S20), and transmits the encrypted information and the control number (parking ticket control number) to the center server 200.
The center server 200 decodes the vehicle ID (step S2) and registers the parking ticket control number in the database 300. The center server 200 then converts the parking ticket control number into a barcode and transmits it to the user device 10.
Thereafter, when the user shops at a store, the user presents the barcode (QR code (registered trademark)) displayed on the user device 10 each time he or she makes a purchase, following the same procedure as in the second embodiment, and has the barcode read by the code reader 76. The code reader 76 reads the parking ticket control 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 control number.
The service providing server 60 performs a discount determination (step S4) based on the parking ticket control number, and further performs a discount amount calculation (step S5), and then waits for the mobility to leave the parking lot.
Furthermore, when the user finishes shopping at the store and leaves the vehicle, the vehicle-mounted device 21 again accesses the roadside device 40 in the same manner as in the second embodiment. The roadside device 40 then acquires the vehicle ID. The vehicle ID read by the roadside device 40 is encrypted in the roadside device 40 (step S9), and the encrypted information is again transmitted to the center server 200.
When the center server 200 receives the encrypted information, it decrypts it to restore the vehicle ID (step S12). Furthermore, the center server 200 reads out the parking ticket control number corresponding to the restored vehicle ID from the table 300b (FIG. 6) (step S13). Then, the center server 200 notifies the service providing server 60 of the parking ticket control number via the parking lot management server 30.
The service providing server 60 calculates the settlement amount for the identified user (step S6) and notifies the vehicle-mounted device 21 via the parking lot management server 30 and the roadside device 40.
Thereafter, when the cashless payment (step S7) is completed in the same manner as in the first and second embodiments, the payment amount is notified to the parking lot management server 30 via the roadside device 40. Then, the parking lot management server 30 transmits a message transmission request to the center server 200. Upon receiving this request, the center server 200 transmits a completion message to the user device 10.

Figure 11 is a diagram for explaining the action in the sequence diagram shown in Figure 10. In Figure 11, the parking lot management server 30 receives 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 payment is made by wireless payment through the same procedure as in the second embodiment, the payment including the service is completed.

In the third embodiment, the parking ticket management number is generated by the store. This makes it possible to reduce the load on the center server 200. As a result, the third embodiment also makes it possible to provide services to each user with cashless payment. Ultimately, it becomes possible to provide a variety of services.

[supplementary explanation]
Here, a supplementary explanation will be given on the method of sending a request to the center server 200. For example, in Fig. 4, Fig. 7, and Fig. 10, it has been described that the settlement result (message) is sent to the user device 10 when the payment is completed. This is realized by the parking lot management server 30 requesting the sending of a settlement message. Technically, the parking lot management server 30 can request the center server 200 to send a settlement message in the form of, for example, an HTTP request using a Web API.

Similarly, the issuance of a parking ticket management number when a mobility vehicle enters, and the authentication and confirmation of a vehicle ID when the vehicle leaves the parking lot can be achieved by sending a request from the parking lot management server 30 to the center server 200. In addition, various services can be provided by the center server 200 by sending a predetermined request message from the parking lot management server 30.

<Second Configuration>
In the first configuration, the association between mobility and users is performed at a center separate from the store. In the second configuration, the system in which the association between mobility and users is performed at the store side will be described.

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

Figure 13 is a diagram for explaining the cooperation between the electronic parking ticket management system shown in Figure 12 and a store. A table in which vehicle IDs and individual user IDs of users are associated with each other is pre-registered in a database 80 accessible from the parking lot management server 30. The parking lot management server 30 refers to the database 80 and obtains an email address corresponding to the vehicle ID. The parking lot management server 30 then generates an electronic parking ticket such as a barcode or QR code (registered trademark) from the vehicle ID and issues it to the obtained email address. Next, an embodiment based on the above configuration will be described.

[Fourth embodiment]
Fig. 14 is a functional block diagram showing an example of an electronic parking ticket management system according to the fourth embodiment. In Fig. 14, the parking lot management server 30 stores in a database 80 a table 80 a in which vehicle IDs are associated with user IDs.
The processor 31 of the parking lot management server 30 includes an acquisition unit 31c, an identification unit 31d, and a transmission unit 31e.
The acquisition unit 31c acquires a vehicle ID via the roadside device 40. The identification unit 31d identifies a user ID corresponding to the acquired vehicle ID by referring to a table 80a in a database 80. The transmission unit 31e transmits the vehicle ID as parking ticket information to a user device 10 carried by a user having the identified user ID.

FIG. 15 is a sequence diagram showing an example of a processing procedure in the system shown in FIG.
15, first, when the mobility 20 enters the parking lot through the gate, the vehicle ID is passed from the in-vehicle device 21 to the roadside device 40. The roadside device 40 then 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 a user shops at a store, the user presents a barcode (QR code (registered trademark)) displayed on the user device 10 each time he or she makes a purchase, and the barcode is 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 vehicle ID acquired by the code reader 76 and the user's purchasing 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 garage.

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

Figure 16 is a diagram for explaining the action in the sequence diagram shown in Figure 15. In Figure 16, the parking lot management server 30 receives the vehicle ID, identifies the user ID from table 80a, and emails the barcode of the vehicle ID to the user.

The barcode displayed on the user device 10 is read every time a purchase is made, and payment information is sent to the POS server 70 and the service providing server 60 along with the vehicle ID. The service providing server 60 performs discount determination and stores the results while updating them for each user. When the mobility is taken out, the roadside unit 40 reads the vehicle ID again and notifies the parking lot management server 30. The parking lot management server 30 queries the service providing server 60 for discount information using the vehicle ID as a key.

The service providing server 60 notifies the roadside device 40 and the vehicle-mounted device 21 of the discount amount via the parking lot management server 30. Once the above steps are followed and payment is made wirelessly, payment including the service is completed.

In the fourth embodiment, processes such as matching vehicle IDs with user IDs, issuing electronic parking tickets (barcodes), and sales management are performed within the store without going through the center server 200. Because the vehicle ID is pre-matched to the user ID, the vehicle ID can be emailed to the user device 10 when the vehicle is parked, and the purchase history can be managed within the store. Therefore, the fourth embodiment also makes it possible to provide services to each user with cashless payment. Ultimately, it becomes possible to provide a variety of services.

[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 generating unit 31f. The generating unit 31f generates a parking ticket management number corresponding to the vehicle ID notified from the roadside device 40. The parking ticket management number is registered in a table 80b of a database 80 in association with the vehicle ID and the user ID. Furthermore, a transmitting unit 31e transmits the parking ticket management number to the user device 10.

FIG. 18 is a sequence diagram showing an example of a processing procedure in the system shown in FIG.
18, first, when the mobility 20 enters the parking lot through the gate, the vehicle ID is passed from the in-vehicle device 21 to the roadside device 40. The roadside device 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 as a barcode (QR code (registered trademark)) (step S3) .

When a user shops at a store, the user presents a barcode (QR code (registered trademark)) displayed on the user device 10 each time he or she makes a purchase, and the barcode is 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 user's purchase information together with the parking ticket control number obtained from the code reader 76 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 parking ticket management number, and waits for the mobility to leave the parking lot.

When the user finishes shopping at the store and leaves the mobility vehicle, the vehicle-mounted device 21 again accesses the roadside device 40. The roadside device 40 then acquires the vehicle ID. The vehicle ID read by the roadside device 40 is notified to the parking lot management server 30.
The parking lot management server 30 converts the vehicle ID into a parking ticket control number by referring to the table 80b (FIG. 17) (step S21). Then, the parking ticket control number is notified to the service providing server 60.
The service providing server 60 calculates the settlement amount for the user identified based on the parking ticket management number (step S6) and notifies the parking lot management server 200 and the vehicle-mounted device 21 via the roadside device 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 device 40. Then, a completion message is sent from the parking lot management server 30 to the user device 10.

Figure 19 is a diagram for explaining the action in the sequence diagram shown in Figure 18. In Figure 19, the parking lot management server 30 that receives the vehicle ID generates a parking ticket management number and registers it in table 80b. In addition, the parking lot management server 30 emails the barcode of the parking ticket management number to the user.

The barcode displayed on the user device 10 is read each time a purchase is made, and payment information is sent to the POS server 70 and the service providing server 60 along with the parking ticket management number. The service providing server 60 determines the discount and stores the result. When the mobility leaves the parking lot, the vehicle ID is notified to the parking lot management server 30, and the service providing server 60 is queried for the discount amount, the billing amount, etc., and the result is returned to the parking lot management server 30. After going through the above steps and making the payment via wireless payment, the payment including the service is completed.

In the fifth embodiment, a parking ticket control number based on the vehicle ID is issued. Then, payment within the store and the provision of services are carried out in association with the parking ticket control number. Moreover, the series of processes is completed within the store without going through the center server 200. For these reasons, the fifth embodiment can achieve the same effects as the fourth embodiment.

As described above, according to each of the above embodiments, it becomes possible to provide services to each user through cashless payment. Ultimately, it becomes possible to provide a wide variety of services.

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

The electronic parking ticket management system of the embodiment may use an ID such as an SNS (social networking service) instead of an email address. In this case, the electronic parking ticket management system of the embodiment may send a message using the SNS instead of an email. Furthermore, the electronic parking ticket may be notified in a push-type manner using a dedicated app. In this case, the user's preferences may be analyzed using a method such as collaborative filtering, and advertisements and coupon information based on the results may be notified along with the barcode information.

In the embodiment, a barcode or QR code (registered trademark) is generated from the vehicle ID and transmitted to the user device 10. Alternatively, a number or the like corresponding to the vehicle ID may be transmitted to the user device 10. In this case, a text reading function (OCR (Optical Character Recognition) is implemented in the code reader 76, and text-based authentication is performed. Alternatively, characters (letters and numbers) displayed on the user device 10 may be manually entered.

In the embodiment, the parking ticket management number generated from the vehicle ID is registered in table 300b. Alternatively, if the parking ticket management number can be uniquely generated from the vehicle ID using, for example, a hash function, it is not necessarily required to register it.

Furthermore, in each of the above embodiments, the description was given without distinguishing between parking lot operators and store operators. While there are configurations like this, there are also cases, for example in local shopping districts, where the parking lot operators and store operators are different. Of course, the present invention can also accommodate such configurations.

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

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 equipped with a POS server 70 that can communicate with the service providing server 60. The parking lot management server 30 communicates with the center server 200, and can provide services such as linking management between vehicle IDs and personal IDs, cashless payment, and preventing the theft of personal information. A system of this type can also provide a variety of services.

Each device in the above embodiment can be transferred to the administrator of the device, for example, with the program for executing the above process stored in ROM or an auxiliary storage device. However, the device may be transferred to the administrator without the program being stored in ROM or an auxiliary storage device. The device may also be transferred to the administrator with a program other than the program stored in ROM or an auxiliary storage device. The program may then be transferred separately to the administrator and written to the ROM or an auxiliary storage device under the operation of the administrator or a serviceman. The program can be transferred in this case by recording it on a removable storage medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by downloading it via the Internet or a LAN.

Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications 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 scope of the invention and its equivalents described in the claims.

10...user device, 15...in-store network, 20...mobility, 21...vehicle-mounted device, 24...number 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 device, 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...payment machine, 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 (9)

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 vehicle is applicable, and notifies the vehicle leaving the parking lot of a settlement amount for the parking fee ,
Electronic parking ticket management system. In the electronic parking ticket management system,
The center server includes:
A generating unit generates a parking ticket control number corresponding to the vehicle ID restored by the decoding unit, 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.
2. The electronic parking ticket management system according to claim 1. 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. 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 vehicle is applicable, and notifies the vehicle leaving the parking lot of a settlement amount for the parking fee ,
Electronic parking ticket management system. In the electronic parking ticket management system,
The parking lot management server includes:
a generating unit that generates a corresponding parking ticket management number from the vehicle ID notified from the roadside device, and registers the parking ticket management 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. 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 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;
A center server comprising: A generating unit generates a parking ticket control number corresponding to the vehicle ID restored by the decoding unit, 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.
The center server according to claim 6. A parking lot management server that is communicably connected to a roadside device and a center server installed in a parking lot,
a generating unit that generates a parking ticket management number corresponding to the vehicle ID from encrypted information of the vehicle ID notified from the roadside device;
a management information notifying unit that notifies a center server that is communicably connected to the roadside device of the parking ticket management number and the encrypted information;
A parking lot management server comprising: 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 communicably connected to the roadside device, a POS system that manages purchase information of users, and a service providing server that provides services to the users, comprising:
a step of detecting a vehicle ID that identifies a vehicle entering or leaving the parking lot by the roadside device;
a step of generating encrypted information by encrypting the detected vehicle ID by the roadside device;
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;
a step of 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 service providing server determining whether the vehicle is eligible for a discount based on the vehicle ID and the purchase information for each user, and if so, calculating the discount amount and notifying the leaving vehicle of the amount of the parking fee to be paid;
An electronic parking ticket management method comprising: