Charge processing system, central management device, charge processing method, charge processing program

Abstract

To allow cashless settlement and touchless settlement to be performed for payment of a parking fee.SOLUTION: A fee processing system according to an embodiment includes a parking lot apparatus installed in a parking lot and an information processing device connected to the parking lot apparatus. The parking lot apparatus transmits exit information received from an in-vehicle device and including a first vehicle identifier that identifies a vehicle, to the information processing device. The information processing device stores a second vehicle identifier that identifies the vehicle, and if the first vehicle identifier and the second vehicle identifier are the same, transmits, to the parking lot apparatus, a first instruction for allowing the vehicle to enter the parking lot, and if the first vehicle identifier and the second vehicle identifier included in the exit information received from the parking lot apparatus are the same, transmits, to the parking lot apparatus, a second instruction for allowing the vehicle to exit the parking lot, and outputs information including a parking fee for the vehicle determined from an entry date and time and an exit date and time.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a fee processing system, a central management device, a fee processing method, and a fee processing program. [Background technology]

[0002] Parking fees are charged when using parking lots at facilities such as supermarkets and shopping malls. When a user uses the parking lot, they issue a parking ticket at the gate at the entrance to the parking lot and pay at the payment machine before leaving. There is also a method of using the parking lot that allows users to enter, exit, and make payment using a card associated with the user without issuing a parking ticket. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2017-037671 Summary of the Invention [Problem to be solved by the invention]

[0004] In response to the diversification of payment methods for parking fees, cashless measures have been promoted. For example, cashless payment methods such as credit card payment, QR code (registered trademark) payment, and electronic money e-payment have been introduced. However, with the spread of COVID-19, there is a growing demand for touchless payment in addition to cashless payment in order to prevent the spread of viruses and other infections.

[0005] There is also a demand for cashless and touchless payment of parking fees and other charges without the use of special cards. [Means for solving the problem]

[0006] According to an embodiment, a fee processing system for processing parking fees for vehicles that use a parking lot comprises parking lot equipment installed in the parking lot and an information processing device connected to the parking lot equipment. When the parking lot equipment detects that the vehicle is entering or exiting the parking lot, it receives a first vehicle identifier that identifies the vehicle from an onboard device of the vehicle and controls the vehicle's entry into or exit from the parking lot in accordance with instructions from the information processing device. The parking lot equipment transmits entry information including an entry date and time indicating the date and time the vehicle entered the parking lot and the first vehicle identifier, and exit information including an exit date and time indicating the date and time the vehicle exited the parking lot and the first vehicle identifier to the information processing device. The information processing device stores a second vehicle identifier that identifies the vehicle, and if the first vehicle identifier and the second vehicle identifier are the same, transmits a first instruction to the parking lot equipment to allow the vehicle to enter the parking lot, and if the first vehicle identifier and the second vehicle identifier are the same, transmits a second instruction to the parking lot equipment to allow the vehicle to exit the parking lot, and outputs information including the parking fee for the vehicle determined from the entry date and time and the exit date and time. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing an example of a schematic configuration of a fee processing system according to the first embodiment. [Figure 2] FIG. 2 is a block diagram showing an example of the hardware configuration of the user device. [Figure 3] FIG. 3 is a block diagram showing an example of a hardware configuration of the vehicle-mounted device. [Figure 4] FIG. 4 is a block diagram showing an example of the hardware configuration of the parking lot equipment. [Figure 5] FIG. 5 is a block diagram showing an example of the hardware configuration of the central server. [Figure 6] FIG. 6 is a block diagram showing an example of the hardware configuration of the key management server. [Figure 7] FIG. 7 is a sequence diagram illustrating an example of a processing procedure in the fee processing system of the first embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a schematic configuration of a fee processing system according to the second embodiment. [Figure 9] FIG. 9 is a block diagram showing an example of the hardware configuration of the user management server 43. As shown in FIG. [Figure 10] FIG. 10 is a sequence diagram illustrating an example of a processing procedure in the fee processing system according to the second embodiment. [Figure 11] FIG. 11 is a sequence diagram illustrating an example of a processing procedure in a fee processing system according to a modification of the second embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of a schematic configuration of a fee processing system according to the third embodiment. [Figure 13] FIG. 13 is a block diagram illustrating an example of the hardware configuration of the shared car management server. [Figure 14] FIG. 14 is a sequence diagram illustrating an example of a processing procedure in the fee processing system of the third embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of a schematic configuration of a fee processing system according to the fourth embodiment. [Figure 16] FIG. 16 is a block diagram illustrating an example of a hardware configuration of the in-store device. [Figure 17] FIG. 17 is a sequence diagram illustrating an example of a processing procedure in the fee processing system according to the fourth embodiment. [Figure 18] FIG. 18 is a sequence diagram showing an example of a processing procedure in a fee processing system according to a modification of the fourth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] The fee processing system, the central management device, the fee processing method, and the fee processing program will be described in detail below with reference to the drawings. Note that in the following embodiments, parts with the same numbers perform similar operations, and redundant explanations will be omitted.

[0009] [First embodiment] (composition) Fig. 1 is a diagram showing an example of the schematic configuration of a fee processing system according to the first embodiment. As shown in Fig. 1, the fee processing system according to the first embodiment includes a user device 1, a vehicle 2, a parking lot device 3, and a central management device 4. The central management device 4 is connected to the user device 1 and the parking lot device 3 via a network 5. The vehicle 2 includes an on-board device 21. The on-board device 21 recognizes the parking lot device 3 and is capable of communicating with the parking lot device 3.

[0010] The fee processing system may include other components as needed in addition to the components shown in FIG. 1, or specific components may be excluded from the fee processing system.

[0011] The user device 1 is a terminal used by a user. The user device 1 may be a mobile terminal device such as a smartphone, or a stationary device such as a personal computer.

[0012] Vehicle 2 may be any ordinary vehicle that can use a parking lot. For example, vehicle 2 may include a car sharing vehicle in which multiple people share a vehicle.

[0013] The vehicle-mounted device 21 can use an ETC (electronic toll collection) system by inserting an ETC card, for example.

[0014] The parking lot equipment 3 is installed in a parking lot that can be used when a user of the user equipment 1 or the like visits a facility such as a supermarket or shopping mall in the vehicle 2. The parking lot equipment 3 may be equipped with, for example, an ETC device equipped with a DSRC (dedicated short-range communications) function. This device enables the parking lot equipment 3 to communicate with the in-vehicle device 21. It goes without saying that the parking lot equipment 3 is not limited to a parking lot that can be used when a user uses a facility, and may be installed in a general parking lot such as a pay parking lot. The parking lot equipment 3 is equipped with, for example, a control unit 31 and a departure control bar 32. The parking lot equipment 3 may open and close the departure control bar 32 under the control of the control unit 31, and control the entry and exit of the vehicle 2 into and from the parking lot. Note that if the entry and exit locations for the parking lot are different, the parking lot equipment may be installed separately.

[0015] The central management device 4 is an information processing device including a central server 41 and a key management server 42. The central management device 4 is installed at a management company or the like that manages the fee processing system. The central server 41 and the key management server 42 may be installed in the same location or in different locations. The central server 41 and the key management server 42 are connected to each other and can communicate various data with each other. This communication is secure, using wired or wireless connections. In FIG. 1, the central server 41 and the key management server 42 are shown as separate servers, but it goes without saying that their functions may be integrated into a single server.

[0016] FIG. 2 is a block diagram showing an example of the hardware configuration of the user device 1. As shown in FIG. The user device 1 has a processor 101 such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). A memory 102, a communication unit 103, and an input / output interface 104 are connected to the processor 101 via a bus 105. In FIG. 2, the "input / output interface" is written as "input / output IF."

[0017] The memory 102 can be a storage medium that can be used in combination with a nonvolatile memory that can be written to and read from at any time, such as an EPROM (Erasable Programmable Read Only Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive), and a nonvolatile memory such as a ROM (Read Only Memory). The memory 102 stores programs required for the processor 101 to execute various processes.

[0018] Furthermore, the memory 102 includes a storage medium that combines a nonvolatile memory that can be written to and read from at any time, such as an HDD or a memory card, with a volatile memory such as a RAM (Random Access Memory). The memory 102 can store data acquired and generated in the process of the processor 101 executing programs and performing various processes.

[0019] The communication unit 103 is a communication interface including a wired or wireless communication module. For example, the communication unit 103 includes a communication module that wirelessly connects to the central server 41 via the network 5. The communication unit 103 may be a general communication unit as long as it can communicate with devices such as the central server 41 under the control of the processor 101 and send and receive various information.

[0020] An input unit and a display unit (not shown), for example, are connected to the input / output interface 104. The input unit is, for example, a device that receives voice data such as a microphone, a device that recognizes character data input by a user using an input detection sheet that employs an electrostatic or pressure method, and a device that receives image data such as a camera. The display unit is, for example, a display device that uses liquid crystal, organic EL (Electro Luminescence), or the like, and displays voice, characters, images, etc. in accordance with signals input from the input / output interface 104.

[0021] Next, a description will be given of functions realized by the processor 101 of the user device 1. The functions realized by the processor 101 are realized by the processor 101 executing a program stored in the internal memory, the memory 102, or the like.

[0022] The processor 101 has a function of transmitting registration information to the central server 41 via the communication unit 103 . The registration information includes the vehicle ID (Identification) of the vehicle 2, personal identification information, payment method information, etc. The vehicle ID is any ID that can identify the vehicle 2, such as the vehicle number printed on the license plate attached to the vehicle 2, the automobile registration number, or an ID unique to the in-vehicle device 21. The personal identification information is information for identifying the user of the user device 1, such as the user's name, address, telephone number, email address, etc. The payment method information is information that indicates how various fees such as parking fees will be paid, and includes, for example, a bank account number if payment is made by direct debit from a bank account, or a credit card number if payment is made by credit card, etc. Furthermore, the user of the user device 1 may use the input / output interface 104 to input the registration information on a predetermined secure web screen, or may input the registration information on a secure input screen of a predetermined application.

[0023] The processor 101 has a function of receiving usage detail information from the central server 41 via the communication unit 103. The usage detail information includes, for example, information about the parking fee for the vehicle 2 that used the parking lot, i.e., the fee charged to the user. Alternatively, the usage detail information may include not only the parking fee but also detailed information such as the date and time the parking lot was used. In other words, the usage detail information may include only the fee charged to the user, including the parking fee, or may include detailed information in addition to the fee charged to the user. The processor 101 may receive the usage statement information via the email address entered in the registration information, or may receive the usage statement information using a predetermined application. The user of the user device 1 can check the parking fee included in the usage statement information through the input / output interface 104.

[0024] FIG. 3 is a block diagram showing an example of the hardware configuration of the vehicle-mounted device 21. As shown in FIG. The vehicle-mounted device 21 has a processor 211 such as a CPU or an MPU. A memory 212, a communication unit 213, a card processing unit 214, and an input / output interface 215 are connected to the processor 211 via a bus 216. In FIG. 3, the "input / output interface" is written as "input / output IF."

[0025] The memory 212 can be a storage medium that can be used by combining, for example, a nonvolatile memory that can be written to and read from at any time, such as an EPROM, HDD, or SSD, with a nonvolatile memory such as a ROM. The memory 212 stores programs required for the processor 211 to execute various processes.

[0026] Furthermore, the memory 212 can be a storage medium that can be used by combining, for example, a nonvolatile memory that can be written to and read from at any time, such as an HDD or a memory card, with a volatile memory, such as a RAM. The memory 102 can store data acquired and generated in the process of the processor 211 executing programs and performing various processes. For example, the memory 212 stores in advance a vehicle ID that identifies the vehicle 2.

[0027] The communication unit 213 is a communication interface including one or more wireless communication modules. For example, the communication unit 213 includes a communication module that wirelessly connects to the parking lot equipment 3. The communication unit 213 may be a general unit as long as it can communicate with the parking lot equipment 3 under the control of the processor 211 and send and receive various information.

[0028] The card processing unit 214 processes payment cards such as ETC cards. The card processing unit 214 has a structure that allows a payment card to be inserted. The card processing unit 214 acquires a card ID and the like from the payment card under control of the processor 211. The card processing unit 214 may also store various data on the payment card under control of the processor 211.

[0029] The input / output interface 215 is connected to, for example, an input unit and a display unit (not shown). The input unit is, for example, a device for receiving voice data such as a microphone, a device for recognizing data input by a user using an input detection sheet that employs an electrostatic or pressure method, and a device for receiving image data such as a camera. The display unit is, for example, a display device that uses a liquid crystal display, an organic electroluminescence display, or the like, and displays voice, text, images, etc. in response to signals input from the input / output interface 215. For example, when entering or exiting the parking lot equipment 3, the input / output interface 215 may convey various information to the user by voice or the like.

[0030] Next, a description will be given of functions realized by the processor 211 of the vehicle-mounted device 21. The functions realized by the processor 211 are realized by the processor 211 executing a program stored in the internal memory, the memory 212, or the like.

[0031] The processor 211 has a function of detecting the parking lot equipment 3 when approaching the parking lot equipment 3. Furthermore, the processor 211 has a function of communicating with the detected parking lot equipment 3 through the communication unit 213 and transmitting various information such as vehicle information including the vehicle ID to the parking lot equipment 3. Note that when communicating with the parking lot equipment 3, it is not necessary for an ETC card to be inserted in the on-board device 21. The processor 211 also has a function to transmit various information such as vehicle information including a vehicle ID when the information is requested by the parking lot equipment 3. That is, the processor 211 has a function to actively or passively transmit various information such as vehicle information including a vehicle ID.

[0032] FIG. 4 is a block diagram showing an example of the hardware configuration of the parking lot equipment 3. As shown in FIG. The parking lot equipment 3 has a processor 301 such as a CPU or MPU. A memory 302, a departure control unit 303, a communication unit 304, a vehicle communication unit 305, an encryption / decryption unit 306, and an input / output interface 307 are connected to this processor 301 via a bus 308. The control unit 31 also has the processor 301, the memory 302, the departure control unit 303, the communication unit 304, the vehicle communication unit 305, the encryption / decryption unit 306, and an input / output IF. In FIG. 4, the "input / output interface" is written as "input / output IF."

[0033] The memory 302 can be a storage medium that can be used by combining a nonvolatile memory that can be written to and read from at any time, such as an EPROM, HDD, or SSD, with a nonvolatile memory such as a ROM. The memory 302 stores programs required for the processor 301 to execute various processes.

[0034] Furthermore, the memory 302 may be a storage medium that combines a nonvolatile memory, such as a HDD or a memory card, that can be written to and read from as needed, with a volatile memory, such as a RAM. The memory 302 can store data acquired and generated in the process of the processor 301 executing programs and performing various processes. For example, the memory 302 can store key information for encrypting the vehicle ID received from the in-vehicle device 21.

[0035] The start control unit 303 controls the entry and exit of the vehicle 2 in the parking lot. For example, the start control unit 303 controls the opening and closing of the start control bar 32 under the control of the processor 301 in response to instructions received from the central server 41. For example, when the start control unit 303 is to temporarily stop the vehicle 2 or when the start control unit 303 is to prohibit the passage (entry) of the vehicle 2, it closes the start control bar 32 to prevent the passage of the vehicle 2. On the other hand, when the start control unit 303 is to permit the passage (entry) of the vehicle 2, it opens the start control bar 32 to allow the passage of the vehicle 2.

[0036] The communication unit 304 is a communication interface including one or more wired or wireless communication modules. For example, the communication unit 304 includes a communication module that wirelessly connects to the central server 41 via the network 5. The communication unit 304 may be a general unit as long as it can communicate with devices such as the central server 41 under the control of the processor 301 and send and receive various information.

[0037] The vehicle communication unit 305 is a communication interface including one or more wireless communication modules. For example, the vehicle communication unit 305 includes a communication module that wirelessly connects to the vehicle-mounted device 21. The vehicle communication unit 305 may be a general unit used in ETC systems as long as it can communicate with the vehicle-mounted device 21 under the control of the processor 301 and send and receive various information.

[0038] The encryption / decryption unit 306 encrypts or decrypts any data using, for example, key information stored in the memory 302. The any data may be, for example, a vehicle ID received from the vehicle-mounted device 21. The encryption and decryption method may be any general encryption / decryption method, and a description thereof will be omitted here.

[0039] The input / output interface 307 is connected to, for example, an input unit and a display unit (not shown). The input unit is, for example, a device for receiving audio data such as a microphone, and a device for receiving image data such as a camera. The display unit is, for example, a display device using a liquid crystal display, an organic electroluminescence display, or the like, and displays audio, text, images, and the like according to signals input from the input / output interface 307. For example, if the start control bar 32 is closed to prevent the vehicle 2 from passing, the input / output interface 307 may display necessary announcements, etc., in audio and / or text, to prompt the user of the vehicle 2 to take necessary measures.

[0040] Next, a description will be given of the functions realized by the processor 301 of the parking lot equipment 3. The functions realized by the processor 301 are realized by the processor 301 executing a program stored in the internal memory, the memory 302, or the like.

[0041] The processor 301 has a function of receiving vehicle information including the vehicle ID from the in-vehicle device 21 when the vehicle 2 enters the parking lot via the vehicle communication unit 305. The processor 301 also has a function of controlling the encryption / decryption unit 306 to encrypt the received vehicle ID using key information stored in the memory 302. The processor 301 then has a function of transmitting entry information including information on the date and time when the vehicle 2 entered the parking lot in addition to the encrypted vehicle ID to the central server 41 via the communication unit 304. Note that the date and time here includes information on only either the date or the time. For example, the date and time when vehicle 2 entered the parking lot may be the date and time when vehicle information including the vehicle ID was received from the in-vehicle device 21. Similarly, when vehicle 2 leaves the parking lot, the processor 301 has a function to transmit exit information including information on the date and time when vehicle 2 left the parking lot, in addition to the encrypted vehicle ID, to the central server 41 via the communication unit 304. For example, the date and time when vehicle 2 left the parking lot may be the date and time when the vehicle ID including the vehicle ID was received from the in-vehicle device 21. Note that the processor 301 may not only encrypt the vehicle ID, but may also encrypt information about the date and time when the vehicle 2 entered or exited the parking lot in addition to the vehicle ID. That is, the processor 301 may encrypt the entry information and exit information and transmit the encrypted entry information and exit information to the central server 41. Furthermore, transmitting the encrypted vehicle ID to the central server 41 can prevent the vehicle ID from being read or altered by a malicious third party on the network 5.

[0042] The processor 301 further receives registered information from the central server 41 through the communication unit 304. In response to receiving the registered information, the processor 301 has a function of transmitting passage information including a vehicle ID (for example, information indicating that the vehicle has used a parking lot and has passed a start control bar) to the central server 41 through the communication unit 304. The registered information will be described later.

[0043] The processor 301 may have a function to determine a parking fee based on the date and time when the vehicle 2 enters the parking lot and the date and time when the vehicle 2 exits the parking lot. In this case, the memory 302 may store information about parking fees according to time. The processor 301 may also have a function to transmit passage information including the determined parking fee to the central server 41. Parking fees include a fee that is accumulated over time to form a total amount, and a flat rate for a specified time.

[0044] FIG. 5 is a block diagram showing an example of the hardware configuration of the central server 41. As shown in FIG. The central server 41 has a processor 411 such as a CPU or an MPU. A memory 412, a communication unit 413, and an input / output interface 414 are connected to the processor 411 via a bus 415. In FIG. 5, the "input / output interface" is written as "input / output IF."

[0045] The memory 412 can be a storage medium that combines a nonvolatile memory that can be written to and read from at any time, such as an EPROM, HDD, or SSD, with a nonvolatile memory such as a ROM. The memory 412 stores programs required for the processor 411 to execute various processes.

[0046] Furthermore, the memory 412 includes a storage medium that combines a nonvolatile memory that can be written to and read from at any time, such as a HDD or a memory card, with a volatile memory, such as a RAM. The memory 412 can store data acquired and generated in the process of the processor 411 executing programs and performing various processes. For example, the memory 412 stores information about parking fees.

[0047] The communication unit 413 is a communication interface including one or more wired or wireless communication modules. For example, the communication unit 413 includes a communication module that wirelessly connects to the user device 1 and the parking lot device 3 via the network 5. The communication unit 413 also includes a communication module that connects to the key management server 42 via a wired or wireless connection. The communication unit 413 may be a general unit that can communicate with the user device 1, the parking lot device 3, and the key management server 42 under the control of the processor 411 and send and receive various information.

[0048] The input / output interface 414 is connected to, for example, an input unit and a display unit (not shown). The input unit is, for example, a device that receives voice data such as a microphone, a device that recognizes text data entered by an administrator who manages the central server 41 using an input detection sheet that employs an electrostatic or pressure method, and a device that receives image data such as a camera. The display unit is a display device that uses, for example, a liquid crystal display, an organic electroluminescence display, or the like, and displays voice, text, images, and the like in response to signals input from the input / output interface 414. For example, when changing the parking fee, the administrator who manages the central server 41 changes it via the input / output interface 414.

[0049] Next, a description will be given of the functions realized by the processor 411 of the central server 41. The functions realized by the processor 411 are realized by the processor 411 executing a program stored in the internal memory, the memory 412, or the like.

[0050] The processor 411 has a function of registering registration information received from the user device 1 via the communication unit 413. The processor 411 has a function of receiving entry information including an encrypted vehicle ID and the date and time when the vehicle 2 entered the parking lot, and exit information including an encrypted vehicle ID and the date and time when the vehicle 2 exited the parking lot, transmitted from the parking lot device 3. The processor 411 has a function of transmitting the encrypted vehicle ID as encrypted vehicle identification information to the key management server 42. Furthermore, the processor 411 has a function of receiving, via the communication unit 413, the vehicle identification information including the vehicle ID decrypted by the key management server 42.

[0051] The processor 411 has a function of comparing the decrypted vehicle ID with the vehicle ID registered in the memory 412. The processor 411 also has a function of transmitting, via the communication unit 413, to the parking lot equipment 3, registered information including a registered flag indicating whether the decrypted vehicle ID matches or does not match the registered vehicle ID.

[0052] Here, the processor 301 of the parking lot equipment 3 has a function of controlling the start control unit 303 in accordance with the instruction indicated by the registered flag to control the start control bar 32. For example, when the registered flag indicates that the decrypted vehicle ID matches the registered vehicle ID, the processor 301 has a function of controlling the start control unit 303 to open the start control bar 32 and allow the vehicle 2 to pass. On the other hand, if the registered flag indicates that the decrypted vehicle ID does not match the registered vehicle ID, the processor 301 has a function of controlling the start control unit 303 to close the start control bar 32. Furthermore, when the start control bar 32 is closed, the processor 301 may have a function of issuing a parking ticket to the user of the vehicle 2. The start control unit 303 and the start control bar 32 can be omitted. That is, if the processor 301 can control the entry and exit of the vehicle 2 by voice and / or text in accordance with the instruction indicated by the registered flag, these can be omitted.

[0053] The processor 411 has the function of sending a fee notification to the user equipment 1 via the communication unit 413 when a predetermined time has passed since the vehicle 2 entered the parking lot equipment 3 or when the parking fee reaches a predetermined fee (predetermined time, fee conditions). The fee notification is a notification sent when a predetermined time has elapsed after the vehicle 2 has entered, or when the parking fee exceeds a predetermined amount. The fee notification includes information for informing the user equipment 1 of the parking fee up to the current stage ((the fee output by the processor 411 at the predetermined time and fee condition)). Furthermore, the transmission of the fee notification may or may not be executed by the processor 411. For example, the user device 1 may receive an input from the user of the user device 1 as to whether or not to send a fee notification, and the processor 411 of the central server 41 may receive that information and set the fee notification, or the processor 411 may set the fee notification automatically. The processor 411 also has a function of determining the time that the vehicle 2 has been in the parking lot from the received entry date and time and exit date and time of the vehicle 2, and determining the parking fee based on that time. The processor 411 has a function of outputting usage statement information including information about the determined parking fee via the communication unit 413. For example, the processor 411 transmits the output usage statement information to the user device 1. Alternatively, the processor 411 may transmit update information indicating that the usage statement has been output and updated to the user device 1. In this case, the user of the user device 1 may check the usage statement information using a predetermined website or a predetermined application based on the update information. The processor 411 has a function of carrying out payment processing based on the payment method information included in the registration information from the user device 1. The processor 411 also has a function to share information about parking fees with a web server or application server (not shown) so that parking fees can be used on a specific website or application. Alternatively, the central server 41 may be equipped with an application server.

[0054] In addition, the calculation of parking fees requires only the date and time information of vehicle 2's entry and exit, and the departure control unit 303 and departure control bar 32 that control vehicle 2's entry and exit can be omitted, and it can also be omitted to issue instructions from processor 411 to parking equipment 3 to control entry and exit.

[0055] FIG. 6 is a block diagram showing an example of the hardware configuration of the key management server 42. As shown in FIG. The key management server 42 has a processor 421 such as a CPU or an MPU. A memory 422, a communication unit 423, an encryption / decryption unit 424, and an input / output interface 425 are connected to the processor 421 via a bus 426. In Fig. 6, the "input / output interface" is written as "input / output IF."

[0056] The memory 422 can be a storage medium that can be used by combining a nonvolatile memory that can be written to and read from at any time, such as an EPROM, HDD, or SSD, with a nonvolatile memory such as a ROM. The memory 422 stores programs required for the processor 421 to execute various processes.

[0057] Furthermore, the memory 422 includes a storage medium that combines a nonvolatile memory that can be written to and read from at any time, such as an HDD or a memory card, with a volatile memory such as a RAM. The memory 422 can store data acquired and generated in the process of the processor 421 executing programs and performing various processes. The memory 422 stores key information corresponding to the key information used by the parking lot device 3 to encrypt the vehicle ID.

[0058] The communication unit 423 is a communication interface including one or more wired or wireless communication modules. For example, the communication unit 423 includes a communication module that connects to the central server 41 via a wired or wireless connection. The communication unit 423 may be a general unit as long as it can securely communicate with the central server 41 under the control of the processor 421 and send and receive various information.

[0059] The encryption / decryption unit 424 decrypts various encrypted information received from the central server 41 under the control of the processor 421. Note that the encryption / decryption unit 424 can also encrypt various information received from the key management server 42.

[0060] An input unit and a display unit (not shown), for example, are connected to the input / output interface 425. The input unit is, for example, a device for receiving audio data such as a microphone, a device for recognizing character data input by an administrator who manages the key management server 42 using an input detection sheet that employs an electrostatic or pressure method, and a device for receiving image data such as a camera. The display unit is, for example, a display device using a liquid crystal display, an organic electroluminescence display, or the like, and displays audio, characters, images, and the like in response to signals input from the input / output interface 425.

[0061] Next, a description will be given of functions realized by the processor 421 of the key management server 42. The functions realized by the processor 421 are realized by the processor 421 executing a program stored in the internal memory, the memory 422, or the like.

[0062] The processor 421 has a function of receiving encrypted identification information through the communication unit 423. The processor 421 has a function of controlling the encryption / decryption unit 424 to decrypt the encrypted vehicle identification information using corresponding key information stored in the memory 422. Furthermore, the processor 421 has a function of transmitting the decrypted encrypted vehicle identification information through the communication unit 423 as vehicle identification information.

[0063] (operation) 7 is a sequence diagram showing an example of the processing procedure in the fee processing system of the first embodiment. The operation of this sequence diagram is realized by the processor 101 of the user device 1, the processor 211 of the vehicle-mounted device 21, the processor 301 of the parking lot device 3, the processor 411 of the central server 41, and the processor 421 of the key management server 42 reading and executing programs stored in the memory 102, the memory 212, the memory 302, the memory 412, and the memory 422, respectively.

[0064] First, the processor 101 of the user equipment 1 transmits registration information including the vehicle ID of the vehicle 2, personal identification information, payment method information, etc. to the central server 41 via the communication unit 103 and the network 5 (ST11). Note that the registration information may also include information regarding whether to issue a fee notification after a predetermined time has elapsed since the date and time the vehicle 2 entered the parking lot or when the parking fee reaches a predetermined fee.

[0065] The processor 411 of the central server 41 registers the received registration information in the memory 412 (ST12). The processor 411 registers the registration information in the memory 102.

[0066] After registration is complete, the vehicle 2 used by the user of the user device 1 enters a parking lot to use a predetermined facility such as a shopping mall. Here, the parking lot is a facility for the user to use. When the vehicle enters the parking lot, the processor 211 of the in-vehicle device 21 detects the parking lot equipment 3 and connects to the parking lot equipment 3. The processor 211 then transmits vehicle information including the vehicle ID via the communication unit 213 (ST13). The method by which the processor 211 detects the parking lot equipment 3 may be a general method similar to the method for detecting a toll gate in an ETC system.

[0067] The processor 301 of the parking lot equipment 3 controls the encryption / decryption unit 306 and encrypts the vehicle ID using the key information stored in the memory 302. Then, the processor 301 transmits the encrypted vehicle ID and entry information including information about the date and time when the vehicle 2 entered the parking lot (for example, the date and time when the launch control bar 32, described later, opened, the vehicle entered, and the bar closed) via the communication unit 304 and the network 5 (ST14). Note that the processor 301 may encrypt the entry information instead of encrypting only the vehicle ID. In other words, the processor 301 may encrypt information about the date and time when the vehicle 2 entered the parking lot in addition to the vehicle ID.

[0068] The processor 411 of the central server 41 transmits the encrypted vehicle identification information, including the encrypted vehicle ID, contained in the received entry information to the key management server 42 via the communication unit 413 (ST15). If the entry information is encrypted, the processor 411 transmits the encrypted vehicle identification information, including the encrypted entry information, to the key management server 42.

[0069] The processor 421 of the key management server 42 controls the encryption / decryption unit 424 to decrypt the vehicle ID included in the encrypted vehicle identification information using key information (second key information) corresponding to the predetermined encryption key (first key information) used by the encryption / decryption unit 306 of the parking lot device 3. The processor 421 transmits the vehicle identification information including the decrypted vehicle ID to the central server 41 via the communication unit 423 (ST16). If the encrypted vehicle identification information includes encrypted entry information, the processor 421 decrypts the entry information and transmits the vehicle identification information including the decrypted entry information to the central server 41. If the central server 41 and the key management server 42 are integrated into one server, the processor of the server simply decrypts the vehicle ID or entry information.

[0070] The processor 411 compares the registered vehicle ID with the vehicle ID included in the received vehicle identification information. Then, the processor 411 transmits the registration information including a registration flag according to the comparison result to the parking lot equipment 3 via the communication unit 413 and the network 5 (ST17). Here, the registration flag may be a bit value of 1 bit. For example, if the registered flag is "1," this indicates that the registered vehicle ID and the vehicle ID included in the vehicle identification information are the same, i.e., the vehicle ID included in the vehicle information has been registered. Therefore, the registered flag being "1" indicates an instruction to allow vehicle 2 to enter the parking lot. On the other hand, if the registered flag is, for example, "0," this indicates that the registered vehicle ID and the vehicle ID included in the vehicle identification information are different, i.e., the vehicle ID included in the vehicle information is unregistered. Therefore, a registered flag of "0" indicates an instruction not to allow vehicle 2 to enter the parking lot. The registered flag is not limited to a one-bit value, and may be any information indicating whether the vehicle ID included in the vehicle information is registered or not.

[0071] If the registration flag indicates that the vehicle ID included in the vehicle information has been registered, that is, if the instruction is to allow vehicle 2 to enter the parking lot, processor 301 controls start control unit 303 to open start control bar 32 and allow vehicle 2 to pass. Then, processor 301 transmits, via communication unit 304 and network 5, passage information including the encrypted vehicle ID and information indicating that vehicle 2 has passed through start control bar 32 (ST18).

[0072] Although not shown in FIG. 7 , if the registered flag indicates that the vehicle ID included in the vehicle information is unregistered, that is, if the registration flag instructs not to allow vehicle 2 to enter the parking lot, processor 301 controls start control unit 303 to close start control bar 32. Then, processor 301 may notify the user of vehicle 2 that there is no registration information by voice, text, or the like via input / output interface 307, and issue a parking ticket. After issuing the parking ticket, processor 301 opens start control bar 32 to allow vehicle 2 to pass. In this case, when vehicle 2 exits, a conventional method of settling the fare using the parking ticket received by the user may be employed, and a description thereof will be omitted here.

[0073] When the processor 411 receives the passing information, it starts charging the vehicle 2 (ST19). As in steps ST15 and ST16, it may also start charging the parking fee after decoding the vehicle ID included in the passing information and confirming that it is the same as the registered vehicle ID.

[0074] The processor 411 transmits a fee notification to the user equipment 1 via the communication unit 413 and the network 5 to notify the user equipment 1 of the current parking fee (ST20). The processor 411 starts charging the parking fee, i.e., transmits the fee notification after a predetermined time has elapsed since the vehicle 2 entered the parking lot or when the parking fee reaches a predetermined amount. Alternatively, the processor 411 may send a notification indicating that there has been a change in the parking fee to the user device 1. In this case, the user of the user device 1 may check the parking fee using a predetermined website or a predetermined application based on the notification. It should be noted that the processor 411 does not have to transmit the fee notification to the user equipment 1. For example, if the received registration information contains information indicating that a fee notification is desired, the processor 411 transmits the fee notification to the user equipment 1, and if the received registration information contains information indicating that a fee notification is not desired, the processor 411 does not transmit the fee notification to the user equipment 1.

[0075] After that, the user finishes using a facility such as a shopping mall and gets into vehicle 2 to exit the parking lot. As in step ST13, processor 211 detects parking lot equipment 3 and connects to parking lot equipment 3. Then, processor 211 transmits vehicle information including the vehicle ID via communication unit 213 (ST21).

[0076] The processor 301 controls the encryption / decryption unit 306 to encrypt the received vehicle ID using the key information stored in the memory 302. Then, the processor 301 transmits the encrypted vehicle ID and exit information including the date and time when the vehicle 2 exited the parking lot via the communication unit 304 and the network 5 (ST22). Note that, like the entry information, the processor 301 may encrypt the exit information instead of encrypting only the vehicle ID. That is, the processor 301 may encrypt information such as the date and time when the vehicle 2 exited the parking lot in addition to the vehicle ID.

[0077] The processor 411 transmits the encrypted vehicle identification information, including the encrypted vehicle ID, contained in the received exit information to the key management server 42 via the communication unit 413 (ST23). If the entry information is encrypted, the processor 411 transmits the encrypted vehicle identification information, including the encrypted exit information, to the key management server 42.

[0078] The processor 421 controls the encryption / decryption unit 424 to decrypt the vehicle ID using key information (second key information) corresponding to the predetermined key information (first key information) used by the encryption / decryption unit 306 of the processor 301 of the parking lot equipment 3. The processor 421 transmits the vehicle identification information including the decrypted vehicle ID to the central server 41 via the communication unit 423 (ST24). Note that if the encrypted vehicle identification information includes encrypted exit information, the processor 421 decrypts the exit information and transmits the vehicle identification information including the decrypted output information to the central server 41.

[0079] The processor 411 compares the registered vehicle ID with the vehicle ID included in the received vehicle identification information, and then transmits the registration information including a registration flag according to the comparison result to the parking lot equipment 3 via the communication unit 413 and the network 5 (ST25).

[0080] If the registered flag indicates that the vehicle ID included in the vehicle identification information is registered, the processor 301 uses the start control unit 303 to open the start control bar 32 and allow the vehicle 2 to pass. Then, the processor 301 transmits, via the communication unit 304 and the network 5, passage information including the encrypted vehicle ID and information indicating that the vehicle 2 has passed the start control bar 32 (ST26). Here, the processor 301 may determine the parking fee based on the date and time when the vehicle 2 enters the parking lot and the date and time when the vehicle 2 exits the parking lot. In this case, in step ST25, the processor 411 transmits the entry information and exit information to the parking lot equipment 3 in addition to the registered information. Processor 301 extracts the date and time when vehicle 2 entered the parking lot and the date and time when vehicle 2 exited the parking lot from the received entry information and exit information and uses these to determine the parking fee. Alternatively, processor 301 may store the date and time when vehicle 2 entered the parking lot in step ST14 and the date and time when vehicle 2 exited the parking lot in step S22 in memory 302 and use these dates and times to determine the parking fee. Then, the processor 301 may transmit the passage information including the determined parking fee to the central server 41. The processor 301 may encrypt the passage information instead of encrypting only the vehicle ID. In other words, the processor 301 may encrypt all information included in the passage information in addition to the vehicle ID.

[0081] 7, if the registered flag indicates that the vehicle ID included in the vehicle information is unregistered, the processor 301 may transmit information requesting the in-vehicle device 21 to transmit the vehicle ID. In this case, the process returns to step ST21.

[0082] The processor 411 transmits the encrypted vehicle identification information including the encrypted vehicle ID contained in the received passage information to the key management server 42 via the communication unit 413 (ST27). If the passage information is encrypted, the processor 411 transmits the encrypted vehicle identification information including the encrypted passage information to the key management server 42.

[0083] The processor 421 controls the encryption / decryption unit 424 to decrypt the vehicle ID using key information corresponding to the predetermined key information used by the processor 301 of the parking lot equipment 3. The processor 421 transmits the vehicle identification information including the decrypted vehicle ID to the central server 41 via the communication unit 423 (ST28). Note that if the encrypted vehicle identification information includes encrypted passage information, the processor 421 decrypts the passage information and transmits the vehicle identification information including the decrypted passage information to the central server 41.

[0084] The processor 411 determines the time that the vehicle 2 stayed in the parking lot from the entry date and time included in the entry information and the exit date and time included in the exit information, and calculates the parking fee based on the determined time (ST29). This calculation of the parking fee may also be performed after the processor 411 determines that the vehicle ID included in the vehicle identification information received in step ST28 matches the registered vehicle ID. By making this determination, the parking fee can be calculated after confirming that there is no error in the exit of the vehicle 2. Furthermore, this parking fee may be calculated after vehicle 2 leaves the parking lot. In other words, vehicle 2 can pass even if the parking fee has not been determined when vehicle 2 leaves the parking lot, and vehicle 2 can leave the parking lot without having to consider delays in determining the parking fee. If the passage information includes the parking fee determined by the processor 301 of the parking lot device 3, step ST29 is omitted.

[0085] The processor 411 transmits usage statement information including information about the parking fee to the user device 1 via the communication unit 413 and the network 5 (ST30). The usage statement information may also include breakdown information of the parking fee. Here, the breakdown information includes, for example, information such as the date and time when the vehicle 2 entered and left the parking lot, and the amount charged per unit time. The user of the user device 1 can check the parking fee included in the usage statement information via the input / output interface 104. Alternatively, the processor 411 may send update information indicating that the usage details have been updated to the user device 1. In this case, the user of the user device 1 may check the usage details information using a predetermined website or a predetermined application based on the update information. The processor 411 also has a function to share the usage detail information with a web server or application server (not shown) in order to use the usage detail information on a specific website or application. Alternatively, the central server 41 may be equipped with an application server.

[0086] In the first embodiment, an example was shown in which the vehicle ID, entry information, exit information, or passage information was encrypted, but each processor does not have to encrypt these. That is, the processor 301 of the parking lot device 3 can transmit the vehicle ID, etc. to the central server 41 without encryption. In this case, the key management server 42 may not be required. In this case, steps ST15, ST16, ST23, ST24, ST27, and ST28 in FIG. 7 are omitted.

[0087] (Operation and effect of the first embodiment) According to the embodiment described above, when the vehicle 2 uses a parking lot, it can do so without using a parking ticket. Furthermore, since the payment of the parking fee is made based on the payment method information included in the registration information, it can be made touchlessly. In other words, there is no need to pay by touching the payment machine with cash or the like using a parking ticket, and payment can be made automatically and contactlessly.

[0088] [Second embodiment] (composition) Fig. 8 is a diagram showing an example of the schematic configuration of a fee processing system according to the second embodiment. As shown in Fig. 8, the fee processing system according to the second embodiment includes a user device 1, a vehicle 2, a parking lot device 3, and a central management device 4. The central management device 4 is connected to the user device 1 and the parking lot device 3 via a network 5. The vehicle 2 includes an on-board device 21. The on-board device 21 recognizes the parking lot device 3 and is capable of communicating with them.

[0089] The central management device 4 includes a central server 41, a key management server 42, and a user management server 43.

[0090] The fee processing system may include other components as needed in addition to the components shown in FIG. 8, or specific components may be excluded from the fee processing system.

[0091] Referring to FIG. 8, the difference from the first embodiment is that the central management device 4 includes a user management server 43.

[0092] The user management server 43 may be installed in a management company that manages the fee processing system. The user management server 43 may be installed in the same location as the central server 41 and the key management server 42 or in a different location. The user management server 43 is also connected to the central server 41 and is capable of communicating various data. For example, the user management server 43 may be a server owned by a business that bills users for usage fees for the user device 1, or a server owned by a business that bills users for usage fees for electricity, water, gas, etc. In other words, the user management server 43 is a server that has already received and stored information regarding personal identification information and payment method information from users in advance in order to receive payment of various fees from the users.

[0093] Furthermore, the central server 41 and the user management server 43 may be managed by different businesses. Therefore, although Fig. 8 shows an example in which the central server 41 and the user management server 43 are directly connected, it goes without saying that the central server 41 and the user management server 43 may be connected via the network 5.

[0094] FIG. 9 is a block diagram showing an example of the hardware configuration of the user management server 43. As shown in FIG. The user management server 43 has a processor 431 such as a CPU or MPU. A memory 432, a communication unit 433, and an input / output interface 434 are connected to this processor 431 via a bus 435. In FIG. 9, the "input / output interface" is written as "input / output IF."

[0095] The memory 432 can be a storage medium that can be used by combining a nonvolatile memory that can be written to and read from at any time, such as an EPROM, HDD, or SSD, with a nonvolatile memory such as a ROM. The memory 432 stores programs required for the processor 431 to execute various processes.

[0096] Furthermore, the memory 432 includes a storage medium that combines a nonvolatile memory, such as a HDD or memory card, that can be written to and read from as needed, with a volatile memory, such as a RAM. The memory 432 can store data acquired and generated in the process of the processor 431 executing programs and performing various processes. For example, the memory 432 stores personal identification information, such as the name, address, telephone number, and email address of the user of the user device 1, as well as payment method information.

[0097] The communication unit 433 is a communication interface including one or more wired or wireless communication modules. For example, the communication unit 433 includes a communication module that wirelessly connects to the user device 1 via the network 5. The communication unit 433 also includes a communication module that connects to the central server 41 by wire or wirelessly. The communication unit 433 may be a general unit as long as it can communicate between the user device 1 and the central server 41 and send and receive various information under the control of the processor 431.

[0098] An input unit and a display unit (not shown), for example, are connected to the input / output interface 434. The input unit is, for example, a device for receiving voice data such as a microphone, a device for recognizing character data input by an administrator who manages the user management server 43 using an input detection sheet that employs an electrostatic or pressure method, and a device for receiving image data such as a camera. The display unit is, for example, a display device using a liquid crystal display, an organic electroluminescence display, or the like, and displays voice, characters, images, etc. in response to signals input from the input / output interface 414.

[0099] Next, a description will be given of functions realized by the processor 431 of the user management server 43. The functions realized by the processor 431 are realized by the processor 431 executing a program stored in the internal memory, the memory 432, or the like.

[0100] The user registers lump-sum payment billing information (lump-sum payment registration information) via the interface of the user device 1, requesting that charges to be billed, such as a usage fee for the user device 1, and parking fees be billed together.

[0101] The processor 431 has a function of registering lump-sum payment registration information received from the user device 1 via the communication unit 433. The lump-sum payment registration information may include a vehicle ID. The processor 431 has a function of transmitting determination information including the vehicle ID to the central server 41 via the communication unit 433. The processor 431 may transmit the determination information periodically, for example, once a day, via the communication unit 433, or may transmit the determination information to the central server 41 upon receiving the lump-sum payment registration information. The processor 411 of the central server 41 also has a function to receive determination information. The processor 411 also has a function to register the vehicle ID included in the received determination information in the memory 412. The processor 411 also has a function to transmit billing information to the user management server 43 via the communication unit 413. The billing information includes various information such as the parking fee for the parking lot, breakdown information of the parking fee, and the vehicle ID.

[0102] The processor 431 has a function of receiving billing information from the central server 41 via the communication unit 433. The processor 431 has a function of outputting usage detail information including information on the determined parking fee and fees to be billed, such as a usage fee for the user device 1, via the communication unit 433. For example, the processor 431 transmits the usage detail information to the user device 1. The processor 431 also has a function of performing payment processing based on the payment method included in the lump-sum payment registration information registered by the user device 1.

[0103] In the second embodiment, the processor 101 of the user equipment 1 has a function of transmitting lump-sum payment registration information instead of registration information, and other configurations are the same as those in the first embodiment, so a description thereof will be omitted here.

[0104] (operation) 10 is a sequence diagram showing an example of the processing procedure in the fee processing system of the second embodiment. The operation of this sequence diagram is realized by the processor 101 of the user device 1, the processor 211 of the vehicle-mounted device 21, the processor 301 of the parking lot device 3, the processor 411 of the central server 41, the processor 421 of the key management server 42, and the processor 431 of the user management server 43 reading and executing programs stored in the memory 102, the memory 212, the memory 302, the memory 412, the memory 422, and the memory 432, respectively.

[0105] First, the processor 101 of the user device 1 transmits lump-sum payment registration information, including the vehicle ID of the vehicle 2, to the user management server 43 via the communication unit 103 and the network 5 (ST41). The lump-sum payment registration information may also include information as to whether or not to send a fee notification after a predetermined time has elapsed since the vehicle 2 entered the parking lot or when the parking fee reaches a predetermined fee.

[0106] The processor 431 of the user management server 43 stores the received lump-sum payment registration information in the memory 432. Furthermore, the processor 431 transmits determination information including the vehicle ID stored in the memory 432 and information on whether to notify the fee to the central server 41 via the communication unit 433 (ST42). The processor 431 may transmit the determination information periodically, for example, once a day, or may transmit the determination information upon receiving the lump-sum payment registration information.

[0107] The processor 411 of the central server 41 registers the received vehicle ID and information on whether to notify the fee in the memory 412 (ST43).

[0108] Steps ST44 to ST60 are the same processes as steps ST13 to ST29 described with reference to FIG. 7 in the first embodiment, and therefore will not be described again here.

[0109] The processor 411 of the central server 41 transmits the billing information including the breakdown information and the vehicle ID to the user management server 43 via the communication unit 413 (ST61). The breakdown information may include, for example, information such as the date and time of entry and exit of the vehicle 2, and the amount charged per unit time.

[0110] The processor 431 of the user management server 43 searches for the same vehicle ID stored in the memory 432 as the received vehicle ID, and identifies the user device 1. The processor 431 compiles the parking fee together with the fee to be charged to the identified user device 1, including the usage fee of the user device 1, and stores them in the memory 432. When compiling, the processor 431 may also associate each item of information and store it in the memory 432. The processor 431 periodically transmits, for example, once a month, usage detail information including the fee to be charged to the user (the total amount of the fee to be charged and the parking fee) and detail information associated with the fee to be paid by the user (ST62). The user of the user device 1 can check the parking fee and its detail information included in the usage detail information via the input / output interface 104. The usage detail information may also include only the fee to be paid by the user, or only the parking fee.

[0111] (Operation and effect of the second embodiment) According to the embodiment described above, when vehicle 2 uses a parking lot, it can be used without using a parking ticket. Furthermore, payment at the parking fee machine is also made based on the payment method information in the registration information, so it can be done without touching. Furthermore, the central server 41 does not need to perform payment processing for the charged fee, which reduces the burden on the central server 41.

[0112] [Modification of the second embodiment] (composition) The modified example of the second embodiment has the same schematic configuration as the fee processing system of the second embodiment shown in Fig. 8. In the modified example of the second embodiment, the central server 41 does not register the vehicle ID, but only the memory 432 of the user management server 43 has the function of registering the vehicle ID. Then, every time entry information including the vehicle ID is received from the vehicle-mounted device 21, the processor 411 of the central server 41 has the function of sending a registration confirmation including the vehicle ID to the user management server 43. The processor 431 of the user management server 43 then has the function of comparing the received vehicle ID with the vehicle ID stored in the memory 432, and transmitting a registration response including a registration flag according to the comparison result via the communication unit 433. The processor 411 has the function of receiving the registration response via the communication unit 413. That is, in the modified example of the second embodiment, every time the processor 411 of the central server 41 receives a vehicle ID from the vehicle-mounted device 21, it sends a registration confirmation query to the user management server 43. Then, the processor 411 of the central server 41 receives a registration response including a registered flag indicating whether the received vehicle ID is a vehicle ID registered in the user management server 43.

[0113] The other configurations are the same as those described in the second embodiment, and therefore will not be described here.

[0114] (operation) 11 is a sequence diagram showing an example of the processing procedure in the fee processing system of a modified example of the second embodiment. The operation of this sequence diagram is realized by the processor 101 of the user device 1, the processor 211 of the vehicle-mounted device 21, the processor 301 of the parking lot device 3, the processor 411 of the central server 41, the processor 421 of the key management server 42, and the processor 431 of the user management server 43 reading and executing programs stored in the memory 102, the memory 212, the memory 302, the memory 412, the memory 422, and the memory 432, respectively.

[0115] First, the processor 101 of the user device 1 transmits lump-sum payment registration information, including the vehicle ID of the vehicle 2, to the user management server 43 via the communication unit 103 and the network 5 (ST71). The lump-sum payment registration information may also include information as to whether or not to send a fee notification after a predetermined time has elapsed since the vehicle 2 entered the parking lot or when the parking fee reaches a predetermined fee.

[0116] The processor 431 of the user management server 43 registers the received lump-sum payment registration information in the memory 412 (ST72).

[0117] After the registration is completed, the vehicle 2 driven by the user of the user device 1 enters a parking lot to use a predetermined facility such as a shopping mall. When the vehicle enters the parking lot, the processor 211 of the in-vehicle device 21 detects the parking lot device 3 and connects to the parking lot device 3. The processor 211 then transmits vehicle information including the vehicle ID via the communication unit 213 (ST73).

[0118] The processor 301 of the parking lot equipment 3 controls the encryption / decryption unit 306 and encrypts the vehicle ID using the key information stored in the memory 302. Then, the processor 301 transmits the encrypted vehicle ID and entry information including information on the date and time when the vehicle 2 entered via the communication unit 304 and the network 5 (ST74).

[0119] The processor 411 of the central server 41 transmits the encrypted vehicle identification information, including the encrypted vehicle ID included in the received entry information, to the key management server 42 via the communication unit 413 (ST75).

[0120] The processor 421 of the key management server 42 controls the encryption / decryption unit 424 to decrypt the vehicle ID included in the encrypted vehicle identification information using a key corresponding to the predetermined encryption key used by the encryption / decryption unit 306 of the parking lot device 3. The processor 421 transmits the vehicle identification information including the decrypted vehicle ID to the central server 41 via the communication unit 423 (ST76).

[0121] The processor 411 transmits a registration confirmation including the vehicle ID included in the vehicle identification information received from the key management server 42 to the user management server 43 via the communication unit 413 (ST77).

[0122] The processor 431 compares the registered vehicle ID with the vehicle ID included in the received registration confirmation, and then transmits a registration response including a registered flag according to the comparison result to the parking lot device 3 via the communication unit 433 (ST78). The registration response may also include information as to whether or not to notify the driver of the fee when a predetermined time has elapsed since the vehicle 2 entered the parking lot or when the parking fee reaches a predetermined amount. Here, the registered flag may be the same as the registered flag described in the first embodiment, and therefore a description thereof will be omitted here.

[0123] The processor 411 transmits the registered information including the received registered flag to the parking lot equipment 3 (ST79).

[0124] Furthermore, steps ST80 to ST93 are the same as steps ST49 to ST62 described in the second embodiment, and therefore a description thereof will be omitted here.

[0125] (Operation and effect of the modified example of the second embodiment) According to the embodiment described above, when vehicle 2 uses a parking lot, it can be used without using a parking ticket. Furthermore, payment at the parking machine can be made touchlessly because it is made based on the payment method information in the registration information. Furthermore, the central server 41 does not need to process the payment of the charged fee, thereby reducing the burden on the central server 41. Furthermore, by inquiring of the user management server 43 as to whether the received vehicle ID is registered each time the central server 41 receives a vehicle ID from the in-vehicle device 21, it becomes possible to confirm that the vehicle ID is a registered vehicle ID even if the user changes the vehicle ID immediately before using the vehicle 2.

[0126] [Third embodiment] (composition) Fig. 12 is a diagram showing an example of the schematic configuration of a fee processing system according to the third embodiment. As shown in Fig. 12, the fee processing system according to the third embodiment includes a user device 1, a vehicle 2, a parking lot device 3, and a central management device 4. The central management device 4 is connected to the user device 1, an on-board device 21, and the parking lot device 3 via a network 5. The vehicle 2 includes the on-board device 21. Furthermore, the on-board device 21 recognizes the parking lot device 3 and is capable of communicating with it.

[0127] The central management device 4 includes a central server 41, a key management server 42, and a shared car management server 44.

[0128] The fee processing system may include other components as required in addition to the components shown in FIG. 12, or specific components may be excluded from the fee processing system.

[0129] Referring to FIG. 12, the difference from the first embodiment is that the central management device 4 includes a shared car management server 44.

[0130] 12 shows only one on-board unit 21, the vehicle 2 may have two or more on-board units. For example, one on-board unit 21 is an ETC on-board unit for using an ETC system, and the other is a shared car on-board unit used to use the shared car vehicle 2. The ETC on-board unit may have the same configuration as the on-board unit 21 shown in FIG. 3. On the other hand, the shared car on-board unit may have the same configuration as the on-board unit 21 shown in FIG. 3, but the card processing unit 214 may be equipped with a contactless IC (integrated circuit) card reader. The user of the user device 1 may start using the vehicle 2 by holding a predetermined IC card over the IC card reader.

[0131] The shared car management server 44 may be installed in a management company that manages the fee processing system. The shared car management server 44 may be installed in the same location as the central server 41 and the key management server 42 or in a different location. The shared car management server 44 is also connected to the central server 41 and is capable of communicating various data. For example, the shared car management server 44 may be a server owned by a business operator that provides a car sharing service. In other words, the central server 41 and the shared car management server 44 may be managed by different businesses. Therefore, although FIG. 12 shows an example in which the central server 41 and the shared car management server 44 are directly connected, it goes without saying that they may also be connected via the network 5.

[0132] In addition, the shared car management server 44 has received information about personal identification information and payment method information about the user of the user device 1 who uses car sharing in advance from the user. Furthermore, since the vehicle 2 is owned by the business operator that manages the shared car management server 44, the shared car management server 44 is a server that already stores the vehicle ID of the vehicle 2.

[0133] FIG. 13 is a block diagram showing an example of the hardware configuration of the shared car management server 44. The shared car management server 44 has a processor 441 such as a CPU or MPU. A memory 442, a communication unit 443, and an input / output interface 444 are connected to this processor 441 via a bus 445. In FIG. 13, the "input / output interface" is written as "input / output IF."

[0134] The memory 442 can be a storage medium that can be used by combining a nonvolatile memory that can be written to and read from at any time, such as an EPROM, HDD, or SSD, with a nonvolatile memory such as a ROM. The memory 442 stores programs required for the processor 431 to execute various processes.

[0135] Furthermore, the memory 442 includes a storage medium that combines a nonvolatile memory, such as a hard disk drive (HDD) or memory card, that can be written to and read from as needed, with a volatile memory, such as RAM. The memory 442 can store data acquired and generated in the process of the processor 441 executing programs and performing various processes. For example, the memory 442 stores personal identification information, such as the name, address, telephone number, and email address of the user using the user device 1, payment method information, and vehicle ID. The memory 442 also stores member identification information that indicates that the user using the user device 1 is eligible to use the car sharing service, i.e., is a member eligible to use the car sharing service.

[0136] The communication unit 443 is a communication interface including one or more wired or wireless communication modules. For example, the communication unit 443 includes a communication module that wirelessly connects to the user device 1 and the in-vehicle device 21 via the network 5. The communication unit 433 also includes a communication module that connects to the central server 41 by wire or wirelessly. The communication unit 443 may be a general unit as long as it can communicate with the user device 1, the in-vehicle device 21, and the central server 41 under the control of the processor 441 and transmit and receive various information.

[0137] For example, an input unit and a display unit (not shown) are connected to the input / output interface 444. The input unit is, for example, a device for receiving voice data such as a microphone, a device for recognizing character data input by an administrator who manages the shared car management server 44 using an input detection sheet that employs an electrostatic or pressure method, and a device for receiving image data such as a camera. The display unit is a display device that uses, for example, a liquid crystal display, an organic electroluminescence display, or the like, and displays voice, text, images, and the like according to signals input from the input / output interface 414 .

[0138] Next, a description will be given of the functions realized by the processor 441 of the shared car management server 44. The functions realized by the processor 441 are realized by the processor 441 executing a program stored in the internal memory, the memory 442, or the like.

[0139] The processor 441 has a function of receiving member identification information and usage start information from the user device 1 or the vehicle-mounted device 21 via the communication unit 443. The usage start information is information indicating that the user of the user device 1 has started to use the vehicle 2. For example, the user of the user device 1 who wants to use the vehicle 2 holds an IC card over the IC card reader of the in-vehicle device 21. By reading the information from the IC card, the processor 211 of the in-vehicle device 21 detects that the user of the user device 1 will use the vehicle 2. Then, the processor 211 transmits the usage start information to the shared car management server 44 via the communication unit 213. The processor 441 has a function of transmitting determination information including the vehicle ID to the central server 41 via the communication unit 443. The processor 441 may transmit the determination information periodically, for example, once a day, via the communication unit 443, or may transmit the determination information to the central server 41 upon receiving usage start information. The processor 411 of the central server 41 also has a function to receive determination information. The processor 411 also has a function to register the vehicle ID included in the received determination information in the memory 412. The processor 411 also has a function to transmit billing information to the user management server 43 via the communication unit 413. The billing information includes various information such as the parking fee for the parking lot, breakdown information of the parking fee, and the vehicle ID.

[0140] The processor 441 has a function of receiving billing information from the central server 41 through the communication unit 443. Furthermore, the processor 441 has a function of receiving termination information from the user device 1 or the vehicle-mounted device 21 through the communication unit 443. The end information is information indicating that the user of the user device 1 has ended use of the vehicle 2. For example, the user of the user device 1 who is using the vehicle 2 holds an IC card over the IC card reader of the in-vehicle device 21. By reading the information from the IC card, the processor 211 of the in-vehicle device 21 detects that the user of the user device 1 has ended use of the vehicle 2. Then, the processor 211 transmits the termination information to the shared car management server 44 via the communication unit 213. Upon receiving the termination information, the processor 441 transmits a deletion request including the vehicle ID to the central server 41 via the communication unit 443. The deletion request includes a request to delete the vehicle ID registered in the memory 412 of the central server 41. This is because the user has finished using the vehicle 2, and there is no longer any need to register the vehicle ID of the vehicle 2 in the central server 41. In addition, when a user of user device 1 has finished using vehicle 2 and another user uses vehicle 2, the vehicle ID can be re-registered to prevent erroneous parking fees from being charged to the user of user device 1 who is not using the vehicle.

[0141] The processor 441 has a function of outputting usage detail information including information on the determined parking fee and various fee information such as the usage fee for the vehicle 2, via the communication unit 443. For example, the processor 441 transmits the usage detail information to the user device 1. The processor 441 also has a function of performing payment processing based on payment method information included in the registration information from the user device 1.

[0142] In the third embodiment, in addition to the configuration of the shared car management server 44 described above, the processor 101 of the user device 1 or the processor 211 of the vehicle-mounted device 21 transmits usage start information to the shared car management server 44, and the processor 411 of the central server 41 has the function of receiving determination information including the vehicle ID and registering the vehicle ID in the memory 412, and therefore the explanation here is omitted, as it is the same as the first embodiment.

[0143] (operation) 14 is a sequence diagram showing an example of the processing procedure in the fee processing system of the third embodiment. The operation of this sequence diagram is realized by the processor 101 of the user device 1, the processor 211 of the in-vehicle device 21, the processor 301 of the parking lot device 3, the processor 411 of the central server 41, the processor 421 of the key management server 42, and the processor 441 of the shared car management server 44 reading and executing programs stored in the memory 102, the memory 212, the memory 302, the memory 412, the memory 422, and the memory 442, respectively.

[0144] First, the processor 101 of the user device 1 receives, via the input / output interface 104, an input indicating that the user has started using the vehicle 2. Then, the processor 101 transmits, via the communication unit 103 and the network 5, usage start information indicating that the user has started using the vehicle 2 to the shared car management server 44 (ST101). Note that, although Figure 14 shows an example in which the processor 101 of the user device 1 transmits the usage start information to the shared car management server 44, the processor 211 of the vehicle-mounted device 21 may transmit the usage start information to the shared car management server 44. When a user who uses vehicle 2 goes through the predetermined procedures for using vehicle 2 and unlocks vehicle 2 or starts the engine of vehicle 2, the processor 211 of the in-vehicle device 21 transmits usage start information to the shared car management server 44. Alternatively, the user of user device 1 who uses vehicle 2 holds an IC card over the IC card reader of the in-vehicle device 21. By reading the information from the IC card, the processor 211 of the in-vehicle device 21 detects that the user of user device 1 will use vehicle 2. Then, the processor 211 transmits the usage start information to the shared car management server 44 via the communication unit 213. In addition, the usage start information may include information as to whether or not to notify the fee after a predetermined time has elapsed since vehicle 2 was parked in the parking lot or when a predetermined fee has been reached, and this information may be included in the information registered when vehicle 2 is used.

[0145] After receiving the usage start information, the processor 441 of the shared car management server 44 transmits to the central server 41 determination information including the vehicle ID of the vehicle 2 registered in the memory 442 and information on whether to notify the fee (ST102).

[0146] The processor 411 of the central server 41 registers the received vehicle ID and information on whether to notify the fee in the memory 412 (ST103).

[0147] Steps ST104 to ST121 are the same processes as steps ST44 to ST61 described with reference to FIG. 10 in the second embodiment, and therefore will not be described again here.

[0148] The processor 101 of the user device 1 receives, via the input / output interface 104, an input indicating that the user has finished using the vehicle 2. Thereafter, the processor 101 transmits, via the communication unit 103 and the network 5, end information indicating that the user has finished using the vehicle 2 to the shared car management server 44 (ST122). 14 shows an example in which the processor 101 of the user device 1 transmits the termination information to the shared car management server 44, but the processor 211 of the in-vehicle device 21 may transmit the termination information. For example, the processor 211 of the in-vehicle device 21 transmits the termination information to the shared car management server 44 in various ways, such as when the user of the vehicle 2 goes through a predetermined procedure to terminate use of the vehicle 2, locks the vehicle 2, or turns off the engine of the vehicle 2.

[0149] When receiving the termination information, the processor 441 of the shared car management server 44 transmits a deletion request including the vehicle ID registered in the memory 442 to the central server 41 (ST123).

[0150] Upon receiving the deletion request, processor 411 deletes from memory 412 information relating to the same vehicle ID as the vehicle ID included in the deletion request (ST124).

[0151] The processor 441 calculates the amount to be charged, including the parking fee, the fee for using the vehicle 2, etc. (ST125). The processor 441 can also store in the memory 442 the breakdown information of the fee to be charged and the parking fee, as well as the breakdown information of the fee for using the vehicle 2, etc.

[0152] The processor 441 transmits usage detail information including the billed fee to the user device 1 via the communication unit 443 (ST126). The usage detail information may also include information such as a breakdown of the usage fee for the vehicle 2 stored in the memory 442. The user of the user device 1 can check the parking fee, breakdown information of the parking fee, the usage fee for the vehicle 2, and the breakdown of the usage fee included in the usage detail information via the input / output interface 104.

[0153] Furthermore, in the third embodiment, an example was shown in which the vehicle ID is stored in the central server 41, but as in the modified example of the second embodiment, the vehicle ID may not be stored in the central server 41, and only the shared car management server 44 may store the vehicle ID. That is, in the third embodiment as well, every time the processor 411 of the central server 41 receives a vehicle ID from the in-vehicle device 21, it sends a registration confirmation query to the shared car management server 44. Then, the processor 411 of the central server 41 may receive a registration response that includes a registered flag indicating whether the received vehicle ID is a vehicle ID registered in the shared car management server 44.

[0154] (Operation and effect of the third embodiment) According to the embodiment described above, vehicle 2 can use the parking lot without using a parking ticket. Furthermore, payment at the parking machine is made based on the payment method information in the registration information, so it can be done touchlessly. Furthermore, the central server 41 does not need to process the payment of the charged fee, which reduces the burden on the central server 41. Furthermore, by registering the vehicle ID of vehicle 2 in the central server 41 every time a user starts using vehicle 2 and deleting the vehicle ID of vehicle 2 from the central server 41 every time the user finishes using the parking lot, the parking fee can be charged to the user who used the parking lot.

[0155] [Fourth embodiment] (composition) FIG. 15 is a diagram illustrating an example of the schematic configuration of a fee processing system according to a fourth embodiment. As illustrated in FIG. 15, the fee processing system according to the fourth embodiment includes a user device 1, a vehicle 2, a parking lot device 3, a central management device 4, and a store device 6. The store device 6 is installed in a facility such as a shop to register products to be paid for and to settle payments for the registered products, and is operated by a store clerk or the like. The store device 6 typically includes a Point of Sale (POS) server included in a POS system and a POS terminal connected to the POS server. The store device 6 may also include an electronic cash register that is not included in a POS system. The store device 6 may also be a general-purpose device such as a PC.

[0156] The central management device 4 is also connected to the user device 1, parking lot devices 3, and store devices 6 via a network 5. The vehicle 2 is equipped with an on-board device 21. The on-board device 21 recognizes the parking lot devices 3 and is capable of communicating with them. The store device 6 is capable of communicating with the user device 1 and parking lot devices 3.

[0157] The fee processing system may include other components as required in addition to the components shown in FIG. 8, or specific components may be excluded from the fee processing system.

[0158] Referring to FIG. 15, the second embodiment differs from the first embodiment in that the fee processing system includes an in-store device 6.

[0159] The in-store device 6 may be installed in a predetermined facility such as a shopping mall. For example, the in-store device 6 can communicate with parking lot devices 3 in a parking lot that uses the facility such as a shopping mall, and the in-store device 6 can also communicate with user devices 1. Although only one in-store device 6 is shown in FIG. 15, there may be multiple in-store devices 6. In other words, the in-store device 6 may of course be divided into multiple devices having similar functions.

[0160] FIG. 16 is a block diagram showing an example of the hardware configuration of the in-store device 6. As shown in FIG. The in-store device 6 has a processor 601 such as a CPU or MPU. A memory 602, a communication unit 603, and an input / output interface 604 are connected to the processor 601 via a bus 605. In FIG. 16, the "input / output interface" is written as "input / output IF."

[0161] The memory 602 can be a storage medium that can be used by combining a nonvolatile memory that can be written to and read from at any time, such as an EPROM, HDD, or SSD, with a nonvolatile memory such as a ROM. The memory 602 stores programs required for the processor 601 to execute various processes.

[0162] Furthermore, the memory 602 includes a storage medium that combines a nonvolatile memory, such as a HDD or memory card, that can be written to and read from as needed, with a volatile memory, such as a RAM. The memory 602 can store data acquired and generated in the process of the processor 601 executing programs and performing various processes. For example, the memory 602 stores a discount amount for parking fees according to the fee for using a facility such as a shopping mall.

[0163] The communication unit 603 is a communication interface including one or more wired or wireless communication modules. For example, the communication unit 603 includes a communication module that wirelessly connects to the central server 41 via the network 5. The communication unit 603 also includes a communication module that wirelessly connects to the user device 1, and further includes a communication module that wiredly or wirelessly connects to the parking lot device 3. The communication unit 603 may be a general unit as long as it can communicate with the user device 1, the parking lot device 3, and the central server 41 under the control of the processor 601 and send and receive various information.

[0164] For example, an input unit and a display unit (not shown) are connected to the input / output interface 604. The input unit is a device that recognizes character data entered by a manager who manages the in-store device 6, for example, by an input detection sheet that employs an electrostatic or pressure method. Furthermore, the input unit functions as a POS terminal equipped with a code reader that reads the barcode displayed by the user device 1 and acquires parking ticket information. The display unit is a display device that uses, for example, a liquid crystal display, an organic electroluminescence display, or the like, and displays voice, text, images, and the like in response to signals input from the input / output interface 604. The POS terminal serving as the input unit may be located in a different location from the store device 6, as long as it is connected to the store device 6. Alternatively, the POS terminal serving as the input unit may be located in a designated facility such as a shopping mall, and the store device 6 may be located in a different location from the facility.

[0165] First, the processor 411 of the central server 41 has a function of receiving the passing information and transmitting the parking ticket information to the user device 1 via the communication unit 413 when charging is initiated. The processor 411 may also send a notification that the parking ticket information has been issued to the user device 1. In this case, the user of the user device 1 may, if necessary, use a specific website or application to display the parking ticket information on the user device 1. Here, the parking ticket information is the vehicle ID itself, or a coded version of the vehicle ID, such as a barcode or QR code (registered trademark). The parking ticket information may also include information such as the date and time of entry into the parking lot. The processor 101 of the user device 1 has a function of receiving the parking ticket information from the central server 41 via the communication unit 103. The processor 101 has a function of transmitting or presenting the parking ticket information to the store device 6 via the communication unit 103. The processor 301 of the parking lot device 3 also has a function of sending a discount amount inquiry to the store device 6 via the communication unit 304. For example, the discount amount inquiry includes information for inquiring whether there is a discount on the parking fee and the vehicle ID. The processor 411 also has a function to share the parking ticket information with a web server or application server (not shown) in order to use the parking ticket information on a specific website or application. Alternatively, the central server 41 may be equipped with an application server.

[0166] Next, a description will be given of functions realized by the processor 601 of the in-store device 6. The functions realized by the processor 601 are realized by the processor 601 executing a program stored in the internal memory, the memory 602, or the like.

[0167] The processor 601 has a function of receiving parking ticket information from the user device 1 via the communication unit 603. For example, the user device 1 can cause the store device 6 to read the parking ticket information when a user pays for shopping or using a facility in a facility such as a shopping mall. The processor 601 may also read the entry date and time from the parking ticket information. The processor 601 has a function of storing in the memory 602 the total amount of the payment for the user's purchases or facility use, the payment date and time, and the entry date and time. Furthermore, the processor 601 has a function of storing in the memory 602 the date and time when the user's vehicle entered the store, the store where the user made a purchase, and the items that the user purchased. The processor 601 has a function to determine the discount amount based on at least one of the total amount of the payment amount paid by the user, the payment date and time, the entry date and time, information about the store used by the user, and the item purchased by the user. In other words, the processor 601 may determine the discount amount based on various information, not limited to the payment amount. The processor 601 also has a function to associate the parking ticket information with the discount amount and store them in the memory 602.

[0168] The processor 601 has a function of receiving a discount amount inquiry from the parking lot equipment 3 through the communication unit 603. The processor 601 further has a function of searching for parking ticket information stored in the memory 602 that matches the vehicle ID, and transmitting discount information including the discount amount and vehicle ID associated with the searched parking ticket information to the parking lot equipment 3.

[0169] The processor 301 of the parking lot equipment 3 has a function of transmitting passage information including discount information. The processor 301 may also have a function of determining a parking fee based on the date and time when the vehicle 2 entered the parking lot, the date and time when the vehicle 2 exited the parking lot, and the discount information. In this case, the memory 302 may store information about parking fees according to time. The processor 301 may also have a function of transmitting the passage information including the determined parking fee to the central server 41.

[0170] The processor 411 of the central server 41 has the function of determining the parking fee based further on the discount information included in the received passage information.

[0171] The other configurations are the same as those in the first embodiment, and therefore will not be described here.

[0172] (operation) 17 is a sequence diagram showing an example of the processing procedure in the fee processing system of the fourth embodiment. The operation of this sequence diagram is realized by the processor 101 of the user device 1, the processor 211 of the vehicle-mounted device 21, the processor 301 of the parking lot device 3, the processor 411 of the central server 41, the processor 421 of the key management server 42, and the processor 601 of the store device 6 reading and executing programs stored in the memory 102, the memory 212, the memory 302, the memory 412, the memory 422, and the memory 602, respectively.

[0173] First, steps ST131 to ST139 are the same processes as steps ST11 to ST19 described with reference to FIG. 7 in the first embodiment, and therefore will not be described again here.

[0174] The processor 411 of the central server 41 transmits the parking ticket information to the user device 1 via the communication unit 413 and the network 5 (ST140). The parking ticket information may include information about the vehicle ID, the entry time, the date and time when the vehicle 2 entered the parking lot, and a discount code for a store or the like according to the specified date and time. The processor 101 of the user device 1 stores the received parking ticket information in the memory 102. The processor 411 may also send a notification that the parking ticket information has been issued to the user device 1. In this case, the user of the user device 1 may, if necessary, use a specific website or application to display the parking ticket information on the user device 1.

[0175] Step ST141 is the same process as step ST20 described with reference to FIG. 7 in the first embodiment, and therefore will not be described again here.

[0176] When the user of the user device 1 settles the payment for shopping or the fee for using the facility at a predetermined facility, the processor 101 of the user device 1 transmits the parking ticket information to the store device 6 (ST142). For example, the user of the user device 1 settles the payment for shopping or the fee for using the facility at a predetermined facility using the store device 6. When settling the fee, the processor 101 of the user device 1 may present the parking ticket information stored in the memory 102 via the input / output interface 104 and have the store device 6 read it from the input unit (POS terminal), or may transmit the parking fee information to the store device 6. In other words, as long as the processor 601 of the store device 6 can receive the parking ticket information, the processor 101 may use a general method.

[0177] The processor 601 of the store device 6 determines the discount amount based on at least one of the total amount of the payment made by the user, the payment date and time, the entry date and time, information about the store used by the user, and the items purchased by the user (ST143). The processor 601 associates the parking ticket information with the determined discount amount and stores them in the memory 602. For example, the processor 601 may determine that parking will be free for a predetermined period of time depending on the amount to be paid. The processor 601 may also transmit information about the discount amount to the central server 41 via the communication unit 603. The processor 411 of the central server 41 may calculate the current parking fee based on the received discount amount and include information about the calculated parking fee in the fee notification. The processor 411 may also transmit, as a fee notification, information indicating that the parking fee has changed due to a parking fee discount. In this case, the user of the user device 1 may check the parking fee using a predetermined website or a predetermined application based on the information.

[0178] Furthermore, steps ST144 to ST148 are the same processes as steps ST21 to ST25 described with reference to FIG. 7 in the first embodiment, and therefore will not be described again here.

[0179] If the registered flag indicates that the vehicle ID included in the vehicle identification information is registered, the processor 301 uses the start control unit 303 to open the start control bar 32 and allow the vehicle 2 to pass. The processor 301 also transmits a discount amount inquiry to the store device 6 to inquire whether there is a discount on the parking fee at the parking lot (ST149). For example, the discount amount inquiry includes the vehicle ID and information for inquiring whether there is a discount on the parking fee. The processor 601 of the store device 6 compares the parking ticket information stored in the memory 602 with the vehicle ID and determines whether there is a discount amount associated with the retrieved parking ticket information. Then, based on the determination, the processor 601 transmits the discount information, including the information on the discount amount read out and the vehicle ID, to the parking lot device 3 (ST150). For example, as described above, the processor 601 transmits discount information indicating that parking is free for a predetermined period of time to the central server 41. Here, the processor 601 may determine the parking fee based on the date and time when the vehicle 2 entered the parking lot, the date and time when the vehicle 2 exited the parking lot, and the discount amount. Then, the processor 301 may transmit passage information including the determined parking fee to the central server 41. In this case, in step ST148, the processor 411 transmits the entry information and exit information to the parking lot equipment 3 in addition to the registered information. The processor 301 extracts the date and time when the vehicle entered the parking lot and the date and time when the vehicle exited the parking lot from the received entry information and exit information, and uses these to determine the parking fee. Alternatively, the processor 301 may store the date and time when the vehicle 2 entered the parking lot in step ST134 and the date and time when the vehicle 2 exited the parking lot in step ST145 in the memory 302, and use these dates and times to determine the parking fee.

[0180] The processor 301 transmits, via the communication unit 304 and the network 5, passage information including the encrypted vehicle ID, discount information, and information indicating that the vehicle 2 has passed through the launch control bar 32 (ST151).

[0181] Processor 411 transmits the encrypted vehicle identification information, including the encrypted vehicle ID, contained in the received passage information to key management server 42 via communication unit 413 (ST152).

[0182] The processor 421 controls the encryption / decryption unit 424 to decrypt the vehicle ID using key information corresponding to the predetermined key information used by the processor 301 of the parking lot equipment 3. The processor 421 transmits the vehicle identification information including the decrypted vehicle ID to the central server 41 via the communication unit 423 (ST153).

[0183] Processor 411 determines the time that vehicle 2 stayed in the parking lot from the entry date and time included in the entry information and the exit date and time included in the exit information, and calculates the parking fee based on the determined time and discount information (ST154). For example, processor 411 determines whether the determined time is within the free time included in the discount information, and if it is within the free time, determines that the parking fee is free. The calculation of the parking fee may be performed after the processor 411 determines that the vehicle ID included in the vehicle identification information received in step ST153 matches the registered vehicle ID. If the passing information includes the parking fee determined by the processor 301 of the parking lot device 3, step ST154 is omitted.

[0184] The processor 411 transmits usage detail information including information about the parking fee and breakdown information of the parking fee to the user device 1 via the communication unit 413 and the network 5 (ST155). The user of the user device 1 can check the parking fee included in the usage detail information via the input / output interface 104.

[0185] (Operation and effect of the fourth embodiment) According to the fourth embodiment described above, when the vehicle 2 uses a parking lot, it can be used without using a parking ticket. Furthermore, payment at the parking fee machine can be made touchlessly because it is made based on the payment method information in the registration information. Furthermore, it is possible for users of facilities such as shopping malls to receive discounts on parking fees according to the fees they pay at the facility.

[0186] [Modification of the fourth embodiment] (composition) The modified fourth embodiment has the same schematic configuration as the fee processing system of the fourth embodiment shown in Fig. 15. In the modified fourth embodiment, the in-store device 6 including the POS server does not determine the discount amount, but the in-store device 6 transmits information for determining the discount amount to the central server 41. The central server 41 then determines the discount amount based on the received information.

[0187] For example, when parking ticket information is received from the user device 1, the processor 601 of the store device 6 has a function of transmitting the parking ticket discount information to the central server 41 via the communication unit 603. The parking ticket discount information includes, for example, the total amount of the payment for the purchases or use of a specified facility made by the user of the user device 1, the date and time of payment, information on which store the user made the purchase at, information on which item the user purchased, and the parking ticket information. The processor 411 of the central server 41 has a function of receiving parking ticket discount information through the communication unit 413. The processor 411 also has a function of identifying a vehicle ID from the parking ticket information included in the parking ticket discount information, and managing the discount amount based on the parking ticket discount information of the identified vehicle ID. For example, the processor 411 stores the discount amount in the memory 412 in association with the vehicle ID. Furthermore, the processor 411 may determine the current parking fee based on the discount amount, and notify the determined parking fee when notifying the fee. Furthermore, the processor 411 has a function of calculating the parking fee based on the discount amount stored in the memory 412, the entry date and time included in the entry information, and the exit date and time included in the exit information, based on the length of time the vehicle 2 has stayed in the parking lot. For example, the parking fee is determined by deducting the discount amount from the parking fee incurred according to the length of time the vehicle 2 has been parked in the parking lot.

[0188] Also, similar to the fourth embodiment, in the modification of the fourth embodiment, the parking lot equipment 3 can determine the parking fee. In this case, the processor 601 has a function of transmitting registered information including information about the discount amount to the parking lot equipment 3. The processor 301 of the parking lot equipment 3 then has a function of calculating the parking fee based on the entry / exit information of the vehicle 2 and the discount amount. Furthermore, the processor 301 has a function of transmitting passage information including information about the calculated parking fee to the central server 41.

[0189] The other configurations are the same as those described in the second embodiment, and therefore will not be described here.

[0190] (operation) 18 is a sequence diagram showing an example of the processing procedure in a fee processing system according to a modification of the fourth embodiment. The operation of this sequence diagram is realized by the processor 101 of the user device 1, the processor 211 of the vehicle-mounted device 21, the processor 301 of the parking lot device 3, the processor 411 of the central server 41, the processor 421 of the key management server 42, and the processor 601 of the store device 6 reading and executing programs stored in the memory 102, the memory 212, the memory 302, the memory 412, the memory 422, and the memory 602, respectively.

[0191] First, steps ST161 to ST172 are the same processes as steps ST131 to ST142 described with reference to FIG. 17 in the fourth embodiment, and therefore will not be described again here.

[0192] When the processor 601 of the in-store device 6 receives the parking ticket information via the communication unit 603 and the network 5, it transmits parking ticket discount information including the parking ticket information, the settlement fee, etc. to the central server 41 (ST173).

[0193] The processor 411 of the central server 41 that has received the parking ticket information determines a discount amount based on at least one of the total amount of the payment amount settled by the user, the payment date and time, the entry date and time, information on the store used by the user, and the item purchased by the user. The processor 411 then manages the determined discount amount (ST174). For example, the processor 411 identifies a vehicle ID from the parking ticket information, and stores the determined discount amount in association with the identified vehicle ID in the memory 412.

[0194] Next, steps ST175 to ST182 are the same processes as steps ST21 to ST28 described with reference to FIG. 7 in the first embodiment, and therefore will not be described again here.

[0195] Processor 411 determines the length of time vehicle 2 has stayed in the parking lot from the entry date and time included in the entry information and the exit date and time included in the exit information, and calculates the parking fee based on the determined length of time and the discount information stored in memory 412 (ST183). For example, processor 411 determines the parking fee by deducting the discount amount associated with the vehicle ID stored in memory 412 from the parking fee according to the length of stay. The calculation of the parking fee may be performed after the processor 411 determines that the vehicle ID included in the vehicle identification information received in step S182 matches the registered vehicle ID. As in the first embodiment, if the passing information includes the parking fee determined by the processor 301 of the parking lot device 3, step ST29 is omitted.

[0196] The processor 411 transmits usage detail information including information about the parking fee and breakdown information of the parking fee to the user device 1 via the communication unit 413 and the network 5 (ST184). The user of the user device 1 can check the parking fee included in the usage detail information via the input / output interface 104.

[0197] (Operation and effect of the modification of the fourth embodiment) According to the fourth embodiment described above, when the vehicle 2 uses a parking lot, it can be used without using a parking ticket. Furthermore, since the payment of the parking fee is made based on the payment method information in the registration information, it can be made without touching. Furthermore, it becomes possible for users who use facilities such as shopping malls to receive a discount on the parking fee according to the amount used at the facility.

[0198] [Other embodiments] It should be noted that the present invention is not limited to the above-described embodiments. For example, the first to fourth embodiments can be combined. For example, when the fourth embodiment is combined with the second embodiment, the fee processing system can include a user management server 43 and a store device 6 in addition to the configuration of the first embodiment. It is also possible to combine the second embodiment and the fourth embodiment.

[0199] In short, this invention is not limited to the above-described embodiments, and various modifications can be made in the implementation stage without departing from the spirit of the invention. Furthermore, the embodiments may be implemented in combination as appropriate as possible, and in such cases, the combined effects can be obtained. Furthermore, the above-described embodiments include inventions at various stages, and various inventions can be extracted by appropriately combining the disclosed multiple constituent elements. [Explanation of symbols]

[0200] 1...User equipment 101...Processor 102...Memory 103…Communications Department 104...Input / output interface 105...Bus 2...Vehicle 21...Onboard equipment 211...processor 212...Memory 213…Communications Department 214...Card processing unit 215...Input / output interface 216...Bus 3. Parking lot equipment 31...Control unit 32...Launch control bar 301...Processor 302...Memory 303...Start control unit 304…Communications Department 305...Vehicle communication unit 306...Encryption and decryption unit 307... Input / output interface 308...bus 4…Central management device 41...Central server 411...Processor 412...Memory 413…Communications Department 414...input / output interface 415...Bus 42...Key management server 421...Processor 422...Memory 423…Communications Department 424...Encryption and decryption unit 425...input / output interface 426...Bus 43...User management server 431...Processor 432...Memory 433…Communications Department 434... Input / output interface 435...Bus 44...Shared car management server 441...Processor 442...Memory 443…Communications Department 444...input / output interface 445...Bus 5. Network 6...Store equipment 601...processor 602...Memory 603…Communications Department 604... Input / output interface 605...Bus

Claims

1. A fee processing system for processing parking fees for vehicles using a parking lot, Parking lot equipment installed in the parking lot; a central control unit connected to the parking equipment; Equipped with The parking lot equipment includes: When detecting that the vehicle is entering or leaving the parking lot, a first vehicle identifier that identifies the vehicle is received from an on-board device of the vehicle; Controlling the entry of the vehicle into or exit from the parking lot in response to an instruction from the central management device; Transmitting entry information including the entry date and time indicating the date and time when the vehicle entered the parking lot and the first vehicle identifier, and exit information including the exit date and time indicating the date and time when the vehicle exited the parking lot and the first vehicle identifier to the central management device; The central management device A central server and a user management server are provided, The user management server receiving registration information from a user equipment, the registration information including a second vehicle identifier identifying the vehicle and a payment; storing the registration information; transmitting the second vehicle identifier to the central server; The central server receiving the second vehicle identifier; storing the second vehicle identifier; If the first vehicle identifier and the second vehicle identifier are the same, sending an entry instruction to the parking lot equipment to allow the vehicle to enter the parking lot; If the first vehicle identifier and the second vehicle identifier are the same, sending an exit instruction to the parking lot equipment to cause the vehicle to exit the parking lot; After the vehicle leaves the parking lot, a parking fee for the vehicle is determined based on the entry date and time and the exit date and time; Transmitting the parking fee to the user management server; The user management server Calculating a charge payable by the user of the user equipment, including the determined parking fee, based on the registration information; outputting information including the billed amount; Fee processing system.

2. the fee processing system further includes a key management server connected to the central management device and storing second key information corresponding to the first key information; the central management device is a device that transmits the first vehicle identifier, which is encrypted using the first key information included in the entry information and the exit information, to the key management server in the encrypted state; the key management server is a device that decrypts the encrypted first vehicle identifier using the corresponding second key information and transmits the decrypted first vehicle identifier to the central management device; The fee processing system according to claim 1 .

3. the central server receives the entry information from the parking lot device, and transmits the first vehicle identifier included in the entry information to the user management server; the user management server transmits the entry instruction to the central server when the first vehicle identifier and the second vehicle identifier are the same; the central server transmits the entry instruction to the parking lot device, receives the exit information, transmits the exit instruction, and transmits the determined parking fee to the user management server; 3. A fee processing system according to claim 1 or 2.

4. The central management device further includes a shared car management server that stores information for sharing and using the vehicle among multiple users, The shared car management server stores the second vehicle identifier, receives use start information indicating the start of use of the vehicle from the user device or the in-vehicle device, and transmits the second vehicle identifier to the central server in response to receiving the use start information; The central server receives the second vehicle identifier from the shared car management server, stores the second vehicle identifier, sends the entry instruction, sends the exit instruction, receives the exit information, and sends the determined parking fee to the shared car management server; The shared car management server receives termination information from the user device or the in-vehicle device indicating that use of the vehicle is to be terminated, and transmits a deletion request to the central server in response to the termination information, requesting that the second vehicle identifier be deleted from the central server; calculates a charge to be paid by the user of the user device, including the determined parking fee; and outputs information including the charge; the central server receives the deletion request from the shared car management server, and deletes the second vehicle identifier in response to receiving the deletion request.

3. A fee processing system according to claim 1 or 2.

5. the parking lot is a parking lot for a user of the vehicle to use a predetermined facility, and the fee processing system further includes a store device used in the predetermined facility; After receiving the entry information from the parking lot equipment, the central management device transmits to the user equipment parking ticket information capable of identifying the second vehicle identifier or information indicating that the parking ticket information has been issued; the store device, when the user settles the cost of shopping at the facility or the cost incurred by using the facility, receives the parking ticket information and determines a discount amount based on at least one of the total amount of the settlement cost settled by the user, the settlement date and time, the entry date and time, store information within the facility used by the user, and the item purchased by the user; the central management device receives the discount amount from the store device and determines the parking fee based on the discount amount; 5. A fee processing system according to claim 1.

6. the parking lot is a parking lot for a user of the vehicle to use a predetermined facility, and the fee processing system further includes a store device used in the predetermined facility; After receiving the entry information from the parking lot equipment, the central management device transmits to the user equipment parking ticket information capable of identifying the second vehicle identifier or information indicating that the parking ticket information has been issued; the store device receives the parking ticket information when the user settles the shopping fee at the facility or the fee incurred by using the facility, and transmits parking ticket discount information including the fee to be settled and the parking ticket information to the central management device; the central management device determines a discount amount based on at least one of the total amount of the settled fees, the settlement date and time, the entry date and time, store information within the facility used by the user, and the items purchased by the user, and determines the parking fee based on the discount amount; 5. A fee processing system according to claim 1.

7. the central management device, after transmitting the entry instruction to the parking lot equipment, receives from the parking lot equipment passage information indicating that the vehicle has entered the parking lot, and after receiving the passage information, starts charging a parking fee.

7. A fee processing system according to claim 1.

8. When a predetermined time has elapsed since the date and time included in the entry information or when the parking fee exceeds a predetermined amount, the central management device notifies the user equipment of the current parking fee or sends a notification including information indicating that the parking fee has changed. The fee processing system according to claim 7.

9. The fee processing system according to claim 1 , wherein either the central management device or a parking lot device determines a parking fee for the vehicle based on the entry date and time and the exit date and time.

10. A central management device for processing parking fees for vehicles using parking fees, comprising: a memory for storing registration information including a second vehicle identifier identifying the vehicle and a payment; a processor connected to the memory; Equipped with The processor: receiving the second vehicle identifier and the registration information from a user equipment; storing the second vehicle identifier and the registration information in the memory; receiving entry information from a parking lot device located in the parking lot, the entry information including a first vehicle identifier and an entry date and time when the vehicle entered; If the first vehicle identifier and the second vehicle identifier are the same, sending an entry instruction to the parking lot device to allow the vehicle to enter the parking lot; receiving exit information from the parking lot device, the exit information including the first vehicle identifier and an exit date and time when the vehicle exited; If the first vehicle identifier and the second vehicle identifier are the same, sending an exit instruction to the parking lot device to cause the vehicle to exit the parking lot; After the vehicle leaves the parking lot, determining a parking fee for the vehicle based on the entry date and time and the exit date and time; calculating a charge payable by the user of the user equipment, including the determined parking fee, based on the registration information; outputting information including the billed amount; A central management device that performs the above.

11. the memory further stores second key information corresponding to the first key information; The processor: decrypting the first vehicle identifier encrypted with the first key information by using the corresponding second key information; The central control unit according to claim 10.

12. The processor: calculating a charge payable by the user of the user equipment, the charge including the determined parking fee, and transmitting information including the charge to the user equipment; The central control unit according to claim 10 or 11.

13. the memory further stores information for sharing the vehicle among a plurality of users; The processor: receiving, from the user device or the vehicle-mounted device of the vehicle, use start information indicating that use of the vehicle is to be started; receiving end information indicating that use of the vehicle will be terminated from the user device or the in-vehicle device; deleting the second vehicle identifier in response to the termination information; calculating a charge payable by the user of the user equipment, the charge including the determined parking fee; transmitting information including the billing amount to the user equipment; The central control unit according to claim 10 or 11.

14. the parking lot is a parking lot where a user of the vehicle can use a predetermined facility, the predetermined facility having a store device; The processor: After receiving the entry information from the parking lot device, transmit to the user device parking ticket information capable of identifying the second vehicle identifier or information indicating that the parking ticket information has been issued; receiving a discount amount from the store device; determining the parking fee based on the discount amount; The central control unit according to any one of claims 10 to 13.

15. The processor: after transmitting the entry instruction to the parking lot device, receiving passage information from the parking lot device indicating that the vehicle has entered the parking lot, and after receiving the passage information, starting to charge a parking fee. The central control unit according to any one of claims 10 to 14.

16. The processor: When a predetermined time has elapsed since the date and time included in the entry information or when the parking fee exceeds a predetermined amount, the system notifies the user device of the current parking fee or transmits a notification including information indicating that the parking fee has changed. The central control unit according to claim 15.

17. A fee processing method executed by a central management device for processing parking fees for vehicles using a parking lot, comprising: receiving registration information from a user equipment, the registration information including a second vehicle identifier identifying the vehicle and a payment; storing the second vehicle identifier and the registration information; receiving entry information from a parking lot device located in the parking lot, the entry information including a first vehicle identifier and an entry date and time when the vehicle entered; If the first vehicle identifier and the second vehicle identifier are the same, sending an entry instruction to the parking lot device to allow the vehicle to enter the parking lot; receiving exit information from the parking lot device, the exit information including the first vehicle identifier and an exit date and time when the vehicle exited; If the first vehicle identifier and the second vehicle identifier are the same, sending an exit instruction to the parking lot device to cause the vehicle to exit the parking lot; After the vehicle leaves the parking lot, determining a parking fee for the vehicle based on the entry date and time and the exit date and time; calculating a charge payable by the user of the user equipment, including the determined parking fee, based on the registration information; outputting information including the billed amount; A fee processing method is provided.

18. A fee processing program comprising instructions to be executed by a processor of a central control device for processing parking fees for vehicles using a parking lot, the instructions comprising: receiving registration information from a user equipment, the registration information including a second vehicle identifier identifying the vehicle and a payment; storing the second vehicle identifier and the registration information; receiving entry information from a parking lot device located in the parking lot, the entry information including a first vehicle identifier and an entry date and time when the vehicle entered; If the first vehicle identifier and the second vehicle identifier are the same, sending an entry instruction to the parking lot device to allow the vehicle to enter the parking lot; receiving exit information from the parking lot device, the exit information including the first vehicle identifier and an exit date and time when the vehicle exited; If the first vehicle identifier and the second vehicle identifier are the same, sending an exit instruction to the parking lot device to cause the vehicle to exit the parking lot; After the vehicle leaves the parking lot, determining a parking fee for the vehicle based on the entry date and time and the exit date and time; calculating a charge payable by the user of the user equipment, including the determined parking fee, based on the registration information; outputting information including the billed amount; A fee processing program is provided.

Images