Control method, program, and control device

Abstract

To provide a control method, a program, and a control device capable of improving the technology related to payment or receipt of money by a user of a vehicle.SOLUTION: A control method is executed by an in-vehicle system mounted on a vehicle. The control method includes: acquiring, from a communication terminal of a user, first wallet information indicating a first wallet associated with authentication information acquired from the communication terminal after the authentication information is determined to be valid, in the in-vehicle system or a computer communicable with the in-vehicle system; linking vehicle wallet information indicating a vehicle wallet managed by the vehicle to the first wallet information; and storing link information indicating that the vehicle wallet information has been linked to the first wallet information, in a memory in the in-vehicle system.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a control method, a program, and a control device. [Background technology]

[0002] Patent document 1 discloses a technology that adjusts the advertising fee presented to a user being taken to a destination by vehicle along with a suggestion to stop by a location other than the destination, depending on the route indicated in route data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-193524 Summary of the Invention [Problem to be solved by the invention]

[0004] Further improvements are needed in the technology relating to the payment or receipt of money by vehicle users. [Means for solving the problem]

[0005] A control method according to one embodiment of the present disclosure is a control method executed by an in-vehicle system mounted on a vehicle, in which, after authentication information obtained from a user's communications terminal is determined to be valid in the in-vehicle system or a computer capable of communicating with the in-vehicle system, first wallet information indicating a first wallet associated with the authentication information is obtained from the communications terminal, vehicle wallet information indicating a vehicle wallet managed in the vehicle is linked to the first wallet information, and link information indicating that the vehicle wallet information and the first wallet information are linked is stored in a memory in the in-vehicle system. Effect of the Invention

[0006] A control method according to one aspect of the present disclosure allows for further improvements in technology relating to payment or receipt of money by vehicle users. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing an example of the overall configuration of a vehicle payment system according to the present embodiment. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of the vehicle payment system according to the present embodiment. [Diagram 3] FIG. 3 shows the screen transitions on the information terminal when starting or ending use of a vehicle as a sharing car. [Figure 4] FIG. 4 shows the screen transitions on the information terminal when starting or ending use of a vehicle as a sharing car. [Figure 5A] FIG. 5A is a block diagram showing an example of a functional configuration of the vehicle payment system according to the present embodiment. [Figure 5B] FIG. 5B is a sequence diagram showing an example of the flow of transaction processing from the start of use of a vehicle to the end of use in the vehicle payment system according to this embodiment. [Figure 6] FIG. 6 is a flowchart showing an example of the flow of a payment process among an external device, a vehicle, and a user in the vehicle payment system according to this embodiment. [Figure 7] FIG. 7 is a flowchart showing an example of the flow of a payment process among an external device, a vehicle, and a user in the vehicle payment system according to this embodiment. [Figure 8] FIG. 8 is a flowchart showing an example of the flow of an electronic key selection process in the vehicle payment system according to the present embodiment. [Figure 9] FIG. 9 is a diagram for explaining an example of a process for notifying a user of a transaction between a vehicle and an external device in the vehicle payment system according to the present embodiment. [Figure 10]FIG. 10 is a diagram for explaining an example of a process for notifying a user of a transaction between a vehicle and an external device in the vehicle payment system according to the present embodiment. [Figure 11] FIG. 11 is a diagram for explaining an example of a pattern of a transaction of monetary value between an external device, a vehicle, and a user in the vehicle payment system according to this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of a vehicle payment system to which a control method, a program, and a control device according to the present disclosure are applied will be described with reference to the drawings.

[0009] (Background to this disclosure) The environment surrounding our daily lives is becoming increasingly digitalized. For example, many people own smartphones, which are personal information terminals, and install and use a variety of applications on their smartphones, such as applications for managing the user's health (hereafter, applications are called apps), and social communication apps for communicating with others.

[0010] This disclosure discloses technology to assist users in living healthy, happy, comfortable, convenient, secure, safe, enjoyable, economical, and rational lives by linking a smartphone, which is an information terminal with diverse information processing capabilities, apps that run on the smartphone, and an information processing server that manages and provides diverse information (hereinafter, the information processing server will be referred to as the cloud).

[0011] The present disclosure can also be realized as a program that causes a computer to execute each characteristic configuration included in the control method used herein, or as a system operated by this program. It goes without saying that such a computer program can be distributed on a computer-readable non-transitory recording medium such as an SD card or via a communication network such as the Internet.

[0012] Note that each of the embodiments described below shows a specific example of the present disclosure. The numerical values, shapes, components, steps, and order of steps shown in the following embodiments are merely examples and do not limit the present disclosure. Furthermore, among the components in the following embodiments, components that are not described in an independent claim showing a top concept are described as optional components. Furthermore, in all of the embodiments, the respective contents can be combined.

[0013] (First form) It is expected that the Internet will continue to become more widespread in our society, and various sensors will become more ubiquitous. As a result, it is expected that information on the internal state and activities of individuals, as well as information on entire cities, including buildings and transportation networks, will be digitized and made available on computer systems. Digitized data on individuals (personal information) will be securely managed as big data on cloud servers such as information banks via communication networks, and will be used for various purposes for the benefit of individuals and society.

[0014] In Japan, this kind of advanced information society is known as Society 5.0. It is a society that is expected to achieve economic development and resolve social issues through an information infrastructure (cyber-physical system) that highly integrates the real space (physical space), the material world that surrounds individuals, with the virtual space (cyberspace), where computers work together to perform various processes related to the physical space.

[0015] In such an advanced information society, by analyzing the communication (including the acquisition, provision and expression of information) and behavior of individuals in various daily situations, and analyzing big data including accumulated personal information, it will be possible to provide necessary information and services to individuals in the most optimal communication method for each situation.In addition, blockchain has been developed in the advanced information society, and vehicles have become an asset managed by blockchain.

[0016] In what follows, we will explain the specific ways in which various users will share and use vehicles in their own ways in an advanced information society where such cyber-physical systems are operating.

[0017] FIG. 1 is a diagram showing an example of the overall configuration of a vehicle payment system according to the present embodiment. Here, a vehicle 1 will be described as a sharing car used by an unspecified number of users. The vehicle 1 can connect to the Internet, which is a wide area communication network 3, by using wireless communication such as cellular communication 2 called 4G or 5G, and access various information. In addition, the vehicle 1 can perform short-distance wireless communication 4 with a short-distance device by using Bluetooth (registered trademark) or UWB (Ultra Wide Band), which is an ultra-wideband wireless communication standard. Furthermore, the vehicle 1 can obtain and update an electronic key that can be used for the vehicle 1 from a vehicle management cloud 5 via the Internet.

[0018] In addition, a vehicle ID, which is identification information of the vehicle, or a QR code (registered trademark) indicating the vehicle ID is printed on the vehicle 1. Here, the electronic payment means recorded in the memory of the vehicle 1 is called a vehicle wallet. The vehicle wallet may be a wallet (identified by a unique wallet address) that can handle crypto assets used in blockchain. Alternatively, the vehicle wallet may be in any form as long as it can trade digital monetary value (points, currency, crypto assets (including digitized currency), tokens, etc.) with other payment means, such as a bank account set in the vehicle 1, credit card information, smartphone QR payment, or an electronic money account issued by a transportation facility.

[0019] In this embodiment, a cloud (a computer system consisting of one or more computers connected to a computer network) used by the vehicle management company to operate and manage the vehicle 1 is referred to as the vehicle management cloud 5. The vehicle management cloud 5 acquires information about the vehicle 1 via the network and controls the vehicle 1 remotely (vehicle control).

[0020] The external device 20 is a general term for devices such as gasoline pumps, EV chargers, ETC gates, and traffic sensors installed on roads that can trade some information or service with vehicles in exchange for monetary value via wired or wireless communication. The external device 20 works in conjunction with an external device management cloud 60 that monitors the operating status of the external device 20 and controls the external device 20 remotely.

[0021] An information terminal (smartphone or the like) 6 owned by a user records and manages the user's digital driver's license, a personal electronic key selected by the user when using the vehicle 1 for personal use, a company electronic key selected by the user when using the vehicle 1 for company business, and a personal wallet and a company wallet (which may be address information or link information for each wallet) linked to each electronic key as payment means. The information terminal 6 may be configured to link and manage the user's digital driver's license with the personal wallet and / or company wallet. In this embodiment, if the electronic key that unlocks the shared car or the electronic key designated by the user to use the vehicle 1 is a personal electronic key, the personal wallet is automatically selected and used as the payment means, and if the electronic key is a company electronic key, the company wallet is automatically selected and used as the payment means.

[0022] In this embodiment, the vehicle 1 is used as a shared car for explanation, but the present invention is not limited to this. It is considered that the present embodiment can be similarly applied to vehicles used temporarily by unspecified users, in which monetary value is traded with an external device 20. Specifically, the present embodiment may be applied to vehicles used by unspecified users, such as robotaxis (autonomous taxis), shared bikes, shared bicycles, shared kick scooters, and shared vertical take-off and landing aircraft (flying taxis).

[0023] Also, without using the vehicle 1, information and functions equivalent to the vehicle wallet (herein referred to as an intermediary wallet) may be stored in the user's information terminal 6. In this case, the user directly conducts transactions between his / her own information terminal 6 and the external device 20, but the transactions with the external device 20 are conducted via an intermediary wallet that is not related to the user's personal information or payment means, thereby making it possible to conceal the user's personal information and payment means from the external device 20. This type of usage may be applied to the payment of fares when boarding an airplane, ship, train, bus, taxi, etc., the payment of shopping charges at a retail store, etc.

[0024] The personal cloud 30 is a cloud that manages personal information including a user's personal electronic key and personal wallet, and payment methods. For example, the personal cloud 30 stores the usage history of the user's personal electronic key and the transaction history of the personal wallet. Similarly, the company cloud 40 stores the usage history of the user's company electronic key and company wallet. The company cloud 40 may also have a function to determine permission to use the company electronic key when the user starts using the company electronic key.

[0025] 2 is a block diagram showing an example of the configuration of the vehicle payment system according to the present embodiment. The information terminal 6 includes a sensor unit 601 for acquiring video information, audio information, and / or physical quantities of the surrounding environment, a video / audio output unit 602 for outputting video and audio, an operation unit 603 for accepting button presses and touch operations from the user, a calculation unit 604 for performing various calculations and information processing such as information drawing performed within the information terminal 6, a memory 605 for storing data and files used by the calculation unit 604, and a communication unit 606 for communicating with other computers on a communication network.

[0026] When an application for managing keys is installed in the information terminal 6, the program and necessary data are recorded in the memory 605 of the information terminal 6, and the program is executed by the calculation unit 604.

[0027] The information terminal 6 will be described as a smartphone, but is not limited to this. It may be in the form of a wristwatch-type smart watch, eyeglass-type smart glasses, a finger ring-type smart ring, a voice-operated smart speaker, or a robot with movable parts.

[0028] The vehicle management cloud 5 comprises a communication unit 501 for communicating with other computers on the communication network, a memory 502 which records information about the vehicle 1 and the user and its management program, and a calculation unit 503 which performs various types of data processing.

[0029] Like the vehicle management cloud 5, the external device management cloud 60, the personal cloud 30, and the company cloud 40 each include a communication unit 501 for communicating with other computers on the communication network, a memory 502 that records information about vehicles and users and management programs for the same, and a calculation unit 503 that performs various types of data processing.

[0030] The vehicle 1 includes a movable unit 101 for moving the vehicle 1 and for moving devices (seats, etc.) in the vehicle cabin space, a lighting unit 102 for illuminating the area around the vehicle 1, a sensor unit 103 for detecting the positions and states of people and cars around the vehicle 1 and people and objects inside the vehicle cabin, an information input / output unit 104 for providing various video and audio information to passengers and accepting inputs such as touch operations and voice operations from passengers, a key control unit 105 for authenticating the key to be unlocked and controlling the locking / unlocking of the doors of the vehicle 1, a calculation unit 106 (an example of a control device) for executing various processes related to the vehicle core system and vehicle functions, a memory 107 for recording various data including programs for the vehicle core system and a database for key management, a communication unit 108 for wirelessly communicating with an external device 20, a communication unit 109 for wirelessly communicating with an external device 20, and a communication unit 110 for setting the air conditioning for the driver's seat and / or the air conditioning for the entire vehicle cabin. The vehicle 1 includes a vehicle interior space control unit 109 that sets the version of the (Single-Side Bus) standard, a battery management unit 110 that controls charging and discharging of the battery of the vehicle 1, and the like.

[0031] The vehicle management cloud 5, the external device management cloud 60, the personal cloud 30, the company cloud 40, the vehicle 1, and the information terminal 6 may communicate with each other through a communication means other than the Internet of the wide area communication network 3. For example, the unlocking process performed between the vehicle 1 and the information terminal 6 may use short-range wireless communication 4.

[0032] 3 and 4 are diagrams showing the screen transitions on the information terminal 6 when starting or ending use of the vehicle 1 as a sharing car. FIG. 3 shows the screen transitions when starting use. First, the user launches the "Sharing Car App" app for using a sharing car that is installed on the information terminal 6. The launched screen is the first (leftmost) screen, and displays a "Use Now" button to start use immediately, a "Reserve" button to make a reservation for a sharing car, a "History" button to check past usage history, and a "Settings" button to check and set the user's personal information and electronic key setting information.

[0033] When the user selects the "Use now" button via the operation unit 603 by touch operation or the like, the screen transitions to a screen for reading the two-dimensional code affixed to vehicle 1 in order to identify vehicle 1 to be used. The car sharing app can identify vehicle 1 (vehicle ID) by placing the two-dimensional code of vehicle 1 within the dashed square on the screen.

[0034] Once vehicle 1 is identified, the screen transitions to one where the user can select the key to use vehicle 1. Three keys are shown as an example here. The first key is displayed to be selected when vehicle 1 is to be used for business purposes in the XX department of XX company, the second key is displayed to be selected when vehicle 1 is to be used for business purposes in the □□ department of the same XX company where the user also has a concurrent position, and the third key is displayed to be selected when vehicle 1 is to be used for personal purposes. In Figure 3, user C selects the second key depending on the purpose of vehicle use. In other words, the user is planning to use vehicle 1 for business purposes in the □□ department where the user also has a concurrent position.

[0035] When the key is selected, the calculation unit 503 of the vehicle management cloud 5 determines whether the vehicle 1 can be used, and if use is permitted, a message is displayed indicating that boarding is permitted. In this example, after boarding, the information input / output unit 104 (for example, a monitor placed in the cockpit) equipped in the vehicle 1 notifies the user that guidance such as how to start the vehicle 1 and how to end use will be presented.

[0036] Also, if no boarding action is detected within a predetermined time (for example, if none of the doors or trunk of the vehicle 1 are unlocked), the use may be automatically terminated. This automatic cancellation function and its indication are intended to prevent the usage fee for the person who made the reservation from increasing above a predetermined amount, particularly in cases where the start of use of the reserved vehicle 1 is not detected even after a predetermined time has passed since the start time of use, and to lend the vehicle 1 to another person who wishes to use it.

[0037] FIG. 4 shows the screen transitions when usage is terminated. When a user wishes to terminate usage from the information terminal 6, they can end usage by starting up the car sharing app and selecting the "return now" button. For ease of understanding, the screen may display information indicating the key whose usage is to be terminated. When the "return now" button is selected, the screen transitions to a confirmation screen for termination of usage. On the confirmation screen, vehicle information for which usage is to be terminated (exterior image of vehicle 1, vehicle 1 license plate number, etc.) and key information (key owner information, etc.) are displayed on the information terminal 6.

[0038] When the intention to end use is confirmed on the confirmation screen, usage history information including the user who used the service, the key used, the vehicle used, the start / end date and time of use, the start / end location of use, the usage fee, etc. is displayed on the video / audio output unit 602 of the information terminal 6.

[0039] 5A is a block diagram showing an example of a functional configuration of a vehicle according to the present embodiment. In the present embodiment, the vehicle 1 realizes an acquisition unit 106a, a link unit 106b, a trading unit 106c, a provision unit 106d, and the like by the calculation unit 106 executing a program stored in the memory 107. In the present embodiment, the acquisition unit 106a, the link unit 106b, the trading unit 106c, the provision unit 106d, and the like are realized in the vehicle 1, but they may be realized in cooperation with the user's information terminal 6 or the vehicle management cloud 5.

[0040] After the acquisition unit 106a determines that the authentication information (e.g., vehicle ID, user electronic key, and user wallet information indicating the user wallet that is the user's wallet) acquired from the user's information terminal 6 (an example of a communication terminal) is valid in the in-vehicle system or a computer capable of communicating with the in-vehicle system (e.g., the calculation unit 503 of the vehicle management cloud 5), the acquisition unit 106a acquires user wallet information (an example of the first wallet information) indicating the user wallet (an example of the first wallet) associated with the authentication information from the information terminal 6 (or the vehicle management cloud 5). Here, the in-vehicle system is a system mounted on the vehicle 1, and may be an in-vehicle device including the calculation unit 106, the memory 107, and the like. In this embodiment, the determination as to whether the authentication information acquired from the information terminal 6 is valid is performed in the vehicle management cloud 5, but this is not limited thereto, and may be performed in the vehicle 1.

[0041] The link unit 106b links the vehicle wallet information, which indicates the vehicle wallet managed in the vehicle 1, to the user wallet information. Furthermore, the link unit 106b stores link information, which indicates that the vehicle wallet information and the user wallet information are linked, in the memory 107 in the in-vehicle system. In this way, when the vehicle 1 has a wallet (payment means), a transaction is performed between the external device 20 and the vehicle 1, and a transaction is performed between the vehicle 1 and the user wallet (payment means) of the user (information terminal 6), thereby preventing user information from leaking to the external device 20 during a transaction. In other words, by connecting the user wallet, the vehicle wallet, and the external device wallet in series, the user wallet automatically linked to the electronic key to be used can be concealed from the external device 20.

[0042] Here, the information terminal 6 may manage (store) a plurality of electronic keys (e.g., a personal electronic key, a company electronic key) available to the user and a plurality of pieces of wallet information indicating a plurality of wallets owned by the user in association with each other. Furthermore, the authentication information may include an electronic key (an example of a first electronic key) selected by the user from among the plurality of electronic keys. In this case, after it is determined that the authentication information is valid, the acquiring unit 106a may acquire, from the information terminal 6, wallet information associated with the first electronic key from among the plurality of pieces of wallet information managed by the information terminal 6, as user wallet information.

[0043] Here, the plurality of pieces of wallet information may be information related to a plurality of payment services available to the user. In this case, the first electronic key may be selected based on one of the plurality of payment services selected by the user via the GUI of the information terminal 6.

[0044] The multiple electronic keys may include a company electronic key (an example of a company key) associated with the company to which the user belongs, and the user's personal electronic key (an example of a personal key). In this case, when the selected first electronic key is a company electronic key, the link unit 106b links company wallet information indicating a company wallet managed by the company to the vehicle wallet information as user wallet information. Also, when the selected first electronic key is a personal electronic key, the link unit 106b links personal wallet information indicating the user's personal wallet to the vehicle wallet information as user wallet information.

[0045] The transaction unit 106c executes a payment process for paying money from the user wallet to the external device wallet (one example of an external wallet) of the external device 20 via the vehicle wallet in response to a request from the external device 20 outside the vehicle 1 or the in-vehicle system. Here, the payment process includes paying money from the vehicle wallet to the external device wallet based on the vehicle wallet information, and transferring the paid money from the user wallet to the vehicle wallet based on the vehicle wallet information and the user wallet information. Note that while the explanation has been given here of the transfer of money, the money is not limited to cash and also includes points having economic value, crypto assets, tokens expressing some kind of right, and the like.

[0046] The same applies when the user wallet receives money from the external device 20. In that case, the transaction unit 106c executes a payment process to pay money from the external device wallet of the external device 20 to the user wallet via the vehicle wallet in response to a request from the external device 20 outside the vehicle 1 or the in-vehicle system. Here, the payment process includes paying money from the external device wallet to the vehicle wallet based on the vehicle wallet information and the external device wallet, and transferring the paid money from the vehicle wallet to the user wallet based on the vehicle wallet information and the user wallet information. In addition, the payment of money from the vehicle wallet to the external device wallet is executed without transmitting an ID (such as a user ID, an application ID, or an information terminal 6 ID) for identifying the user or the information terminal 6 and user wallet information to the external device 20.

[0047] Furthermore, the vehicle wallet information includes a vehicle wallet address indicating the address of the vehicle wallet. Furthermore, the user wallet information includes a user wallet address indicating the address of the user wallet. In this case, a payment from the vehicle wallet to the external device wallet may be executed by recording a first payment transaction using the external device wallet address acquired from the external device 20 and the vehicle wallet address on the blockchain. Furthermore, a payment from the user wallet to the vehicle wallet may be executed by recording a second payment transaction using the user wallet address and the vehicle wallet on the blockchain.

[0048] Furthermore, the payment from the vehicle wallet to the external device wallet may be executed at a first timing when a payment request occurs between the external device 20 and the vehicle 1. The payment from the user wallet to the vehicle wallet may be executed at a second timing that is later than the first timing. Here, the second timing may be the timing when the user suspends or terminates the use of the vehicle 1, or the timing when a preset period ends.

[0049] Furthermore, in a payment from the vehicle wallet to the external device wallet, a payment of a first amount requested by the external device 20 may be executed. In addition, in a payment from the user wallet to the vehicle wallet, a payment of a second amount different from the first amount may be executed.

[0050] Furthermore, the transaction unit 106c may obtain permission information in advance from the information terminal 6 after linking the vehicle wallet information to the user wallet information. Here, the permission information may indicate that the in-vehicle system has a temporary or other conditional authority to request and execute a transfer of money from the user wallet to the vehicle wallet. In this case, receipt of payment from the user wallet to the vehicle wallet is executed based on the permission information before or after payment from the vehicle wallet to the external device wallet.

[0051] The payment from the user wallet to the vehicle wallet may be executed in advance by transferring a predetermined amount from the user wallet to the vehicle wallet after linking the vehicle wallet information to the user wallet information (prepaid type). In this case, the payment from the vehicle wallet to the external device wallet may be executed within a predetermined amount when a payment request occurs between the external device 20 and the vehicle 1.

[0052] The process of transferring money from the vehicle wallet to the external device wallet may be performed by recording a payment transaction using the vehicle wallet address and the external device wallet address on a blockchain, and the corresponding process of transferring money between the user wallet and the vehicle wallet may be performed by a settlement method that does not involve recording on the blockchain in order to avoid tracking by a third party.

[0053] Furthermore, the payment process may be performed via an intermediary wallet different from the vehicle wallet in addition to the vehicle wallet. In this case, receipt of money from the user wallet in the payment process includes a payment from the user wallet to the intermediary wallet and a payment from the intermediary wallet to the vehicle wallet. Furthermore, the payment from the vehicle wallet to the external device wallet, the payment from the intermediary wallet to the vehicle wallet, and the payment from the user wallet to the intermediary wallet are performed by recording each payment transaction on the blockchain. Furthermore, the timing at which at least two of the respective payment transactions are recorded may be separated by a predetermined time or more.

[0054] After the payment process, the transaction unit 106c may transmit a payment report indicating that the payment process has been completed to the information terminal 6. Here, the payment report may include payee information for identifying the external device 20 or the external device wallet, and information on the payment amount.

[0055] Furthermore, after the payment process, the transaction unit 106c may display a payment report indicating that the payment process has been completed on the information input / output unit 104 (an example of a display) mounted on the vehicle 1. The display content of the payment report may include a display object for identifying the external device 20.

[0056] Furthermore, if the external device is a charger for charging the battery of the vehicle 1, the payment report may include information on the amount of charge that has been applied to the battery.

[0057] Furthermore, if the selected electronic key is a company electronic key, the transaction unit 106c may transmit a payment report indicating that the payment process using the company wallet has been completed to the company cloud 40 (an example of a company server) associated with the company to which the user belongs after the payment process, if the selected electronic key is a personal electronic key, after the payment process, the transaction unit 106c may transmit a payment report indicating that the payment process using the user wallet has been completed to the information terminal 6 or the personal cloud 30 (an example of a personal server) used by the user.

[0058] The transaction unit 106c executes a receiving process for receiving money paid from the external device wallet of the external device 20 to the user wallet via the vehicle wallet in response to a request from the external device 20 outside the vehicle 1 or the vehicle 1. Here, the receiving process may include receiving money paid from the external device wallet to the vehicle wallet based on the vehicle wallet information, and transferring money from the vehicle wallet to the user wallet based on the vehicle wallet information and the user wallet information. Receiving money paid from the external device wallet to the vehicle wallet may be executed without transmitting an ID for identifying the user or the information terminal 6 and the user wallet information to the external device 20.

[0059] The process of transferring money from the external device wallet to the vehicle wallet may be performed by recording a payment transaction using the wallet address indicated by the vehicle wallet information on a blockchain. Also, the corresponding process of transferring money between the vehicle wallet and the user wallet may be performed by a settlement method that does not involve recording on the blockchain in order to avoid tracking by a third party.

[0060] In this embodiment, the transaction unit 106c transfers money between the vehicle wallet and the external device wallet in the payment processing and receipt processing with the external device 2, but it can also transfer money with the external device management cloud 60. Furthermore, when the transaction unit 106c is realized in the vehicle management cloud 5, it can also transfer money between the vehicle wallet and the external device wallet in the payment processing and receipt processing between the vehicle management cloud 5 and the external device 20 (or the external device management cloud 60).

[0061] The providing unit 106d may provide sensing data (an example of detection data) obtained by the vehicle 1 detecting its running state or the situation around the vehicle 1 to a traffic infrastructure system related to the road on which the vehicle 1 runs. In this case, the external device 20 may be at least a part of the traffic infrastructure system. The payment from the external device wallet may be a payment for providing the sensing data to the traffic infrastructure system. For example, the acquiring unit 106a acquires the position information of the vehicle 1 at predetermined time intervals, and the communication unit 108 transmits the movement history information, which is a compilation of the position information within a past predetermined time, to the external device 20 installed along the road together with the vehicle ID (and / or the user ID, the vehicle wallet, and the ID of the ETC on-board device), and the external device 20 may pay a price to the vehicle for providing the movement history information.

[0062] FIG. 5B is a sequence diagram showing an example of the flow of transaction processing from the start of use of a vehicle to the end of use in the vehicle payment system according to this embodiment. When a user starts using a vehicle 1, the user first obtains the vehicle ID of the vehicle 1 to be shared using the information terminal 6 (the car sharing app of the information terminal 6) and selects an electronic key (step S500). For example, the information terminal 6 reads a QR code printed near the driver's door of the vehicle 1 using the car sharing app to obtain the vehicle ID and start the transaction processing. Then, the information terminal 6 transmits a key authentication request to the vehicle management cloud 5 (step S501).

[0063] At that time, the information terminal 6 also transmits to the vehicle management cloud 5 authentication information including the target vehicle ID (information based on the QR code), the electronic key designated (selected) by the user at the time of use, and user wallet information indicating the user wallet, which is the payment method corresponding to the electronic key. The vehicle management cloud 5 authenticates the electronic key (step S502) and returns the result (key authentication result) (step S503). If the key authentication fails, the transaction process ends. If it is successful, the vehicle management cloud 5 continues by transmitting an instruction to unlock the door, the electronic key designated by the user, and user wallet information to the vehicle 1 or an application (hereinafter, the vehicle 1 or this application is referred to as the vehicle 1) running on the computer system (including the calculation unit 106, the memory 107, the communication unit 108, and the information input / output unit 104) mounted on the vehicle 1 (step S504).

[0064] The acquisition unit 106a of the vehicle 1 acquires an unlocking instruction, an electronic key, and user wallet information from the vehicle management cloud 5. The vehicle 1 receives this, unlocks the doors, and starts the vehicle 1 (step S505). The link unit 106b of the vehicle 1 also links the vehicle wallet information with the user wallet information (step S506). In other words, the user wallet information is recorded in the memory 107 so that the total amount of transactions between the external device 20 and the vehicle wallet during the period in which the user uses the vehicle 1 can be charged or paid to the user wallet successively or later in a lump sum.

[0065] While the user is using the vehicle 1, a request for a transaction of monetary value with the external device 20 occurs each time. This includes both requests for payment for travelling on toll roads, charging the battery, filling up with gasoline, etc., and requests for transfer of compensation for sharing vehicle sensor data, information on the vehicle 1, or passengers. When the external device 20 transmits a transaction request to the vehicle 1 (step S507), the vehicle 1 determines whether the transaction request is necessary (step S508). If it is determined that the transaction is not necessary, the transaction process ends here, and if it is determined that the transaction is necessary, the process continues to the following process.

[0066] The transaction unit 106c of the vehicle 1 performs a transaction (transfer of monetary value) between the vehicle wallet and the external device wallet (or payment means) in accordance with the transaction request (step S509). Then, a notification that the transaction has been completed is returned to the external device 20 (step S510). If this transaction is recorded on a blockchain, both the external device 20 and the vehicle 1 can refer to and confirm the transaction record. After that, the vehicle 1 manages in the memory 107 a record of all transactions between the external device 20 and the vehicle 1 that occurred while the user was using the vehicle 1 (step S511). This transaction history record may be managed in the memory 107 of the vehicle 1, or may be sent to and managed in the vehicle management cloud 5, or if it is recorded on a blockchain, it may be referred to.

[0067] When the user ends use of the vehicle 1, the user selects end of use via the information input / output unit 104 of the vehicle 1 and instructs the vehicle 1 to start a use end process (step S512). The transaction unit 106c of the vehicle 1 executes a transaction to request the user wallet to pay a monetary value including the cumulative amount of transactions between the external device 20 and the vehicle 1 while the user is using the vehicle 1 and the usage fee for the vehicle 1 to the vehicle wallet (step S513). If the payment is negative, the transaction unit 106c executes a transaction to pay the monetary value from the vehicle wallet to the user wallet. In addition, when use ends, the vehicle 1 deletes the electronic key and user wallet information used by the user from the memory 107 (step S514).

[0068] In the present disclosure, the above embodiment has been described as an example, but the same effect and purpose may be realized in a different form. It is sufficient that the vehicle 1 temporarily becomes the transaction partner and processes transactions of monetary value with the external device 20 that occur while the user is using the vehicle 1. The vehicle 1 transacts the amount of transactions with the external device 20 or the cumulative amount of transactions with the user wallet each time a transaction with the external device 20 occurs (i.e., sequentially) or in a lump sum at the end of the user's use, etc. In this way, by preventing direct transactions between the external device 20 and the user via the vehicle 1 (vehicle wallet), it is expected that the user of the vehicle 1 (user's personal information, electronic key, user wallet information, etc.) can be concealed and cannot be identified from the external device 20 or third parties participating in the blockchain network. This leads to protecting the privacy of users of the vehicle 1, such as sharing cars.

[0069] Fig. 6 is a flowchart showing an example of the flow of payment processing among an external device, a vehicle, and a user in the vehicle payment system according to this embodiment. Here, an example of the flow of processing is described in which the external device 20 bills the vehicle 1, and then the vehicle 1 bills the user. Also, here, the processing start timing is described as the point in time when payment to the external device 20 is required based on the user's use of the vehicle 1, such as when gasoline is filled up, when battery charging is completed, when passing through a toll road gate, etc., and the monetary value of the payment (billing amount) is determined.

[0070] Note that before this payment occurs, for example, when the user starts using the vehicle 1, the user agrees in advance to the terms of payment with the vehicle management company, and this agreement is recorded on the blockchain. In addition, in the following explanation, it is assumed that, based on the terms of the agreement, when a request is made from the vehicle wallet to the user's wallet, payment will be made automatically in response to the request, as long as it is within the user's usage period, as written in the smart contract, the information terminal 6 (app), the vehicle 1, or the vehicle management cloud 5 (or the app for the vehicle management cloud 5).

[0071] First, when the external device 20 determines the billing amount (money to be billed) for the vehicle 1 (step 601), it notifies the vehicle 1 of a billing request ID and bills the vehicle 1 for the billing amount (step S602). Note that the billing request ID that identifies the transaction between the external device 20 and the vehicle 1 and the billing request ID that identifies the transaction between the vehicle 1 and the user are information used by the billing party to identify the transaction. Therefore, it does not matter whether the same information is used or not.

[0072] When the transaction unit 106c of the vehicle 1 receives a billing request (billing request ID) from the external device 20 (step S603), it judges whether the billing request is based on the user's use of the vehicle 1 (step S604). If the billing request is not based on the user's use of the vehicle 1 (step S604: No), the transaction unit 106c of the vehicle 1 ends the payment process. On the other hand, if the billing request is based on the user's use of the vehicle 1 (step S604: Yes), the transaction unit 106c of the vehicle 1 executes the payment process from the vehicle wallet to the external device wallet (step S605). Next, the transaction unit 106c of the vehicle 1 notifies the external device 20 of the execution of the payment process (step S606). At that time, the transaction unit 106c of the vehicle 1 attaches the billing request ID. The external device 20 confirms the execution of the payment process notified from the vehicle 1 (step S607). The transaction unit 106c of the vehicle 1 also charges the payment amount from the vehicle wallet to the user wallet, which is the wallet of the user (step S608). At that time, the transaction unit 106c of the vehicle 1 also gives a charge request ID.

[0073] The information terminal 6 on which an application for managing transactions of the user wallet is running, or the smart contract registered on the blockchain in which the user has written the terms of agreement with the vehicle management company, receives or detects a billing request for the payment amount from the vehicle 1 (step S609). Next, the information terminal 6 or the smart contract determines whether the received billing request is a billing based on the user's use of the vehicle 1 (step S610). If the received billing request is not a billing based on the user's use of the vehicle 1 (step S610: No), the information terminal 6 or the smart contract ends the payment process. On the other hand, if the received billing request is a billing based on the user's use of the vehicle 1 (step S610: Yes), the information terminal 6 or the smart contract makes a payment from the user wallet to the vehicle wallet (step S611). Next, the information terminal 6 or the smart contract notifies the vehicle 1 of the payment (step S612). At that time, the information terminal 6 or the smart contract notifies the payment by adding a billing request ID. The transaction unit 106c of the vehicle 1 confirms the payment from the user wallet to the vehicle wallet (step S613).

[0074] 7 is a flowchart showing an example of the flow of a payment process among an external device, a vehicle, and a user in the vehicle payment system according to this embodiment. Here, an example of the flow of a process in which the vehicle 1 charges the external device 20 for uploading the sensing data of the vehicle 1 and notifies the user of the amount paid to the wallet of the user is described.

[0075] In addition, the processing start timing is described here as the point in time when a transfer is made from the external device 20 based on the user's use of the vehicle 1, such as when sensing data sensed by the sensor unit 103 of the vehicle 1 is transmitted to the external device 20, when information regarding the vehicle 1 or the user is transmitted to the external device 20, or when the vehicle 1 or the user transmits a response to an inquiry or question from the external device 20, and the monetary value of the transfer (e.g., the payment amount) is determined.

[0076] Note that before this transfer occurs, for example, when the user starts using the vehicle 1, the user agrees in advance with the vehicle management company on the conditions of the transfer, and this agreement is recorded on the blockchain. In addition, in the following explanation, it is assumed that, based on the terms of the agreement, when a transfer request is made from the vehicle wallet to the user wallet, the transfer will be made automatically in response to the request as long as it is within the user's usage period, as set forth in the smart contract, the information terminal 6 (app), the vehicle 1, or the vehicle management cloud 5 (app for the vehicle management cloud 5).

[0077] When permission or an instruction to provide the sensing data acquired by the vehicle 1 to the external device 20 is received from the user (step S701), the providing unit 106e of the vehicle 1 transmits the sensing data of the vehicle 1 to the external device 20 (step S702). At that time, the providing unit 106d of the vehicle 1 notifies the external device 20 of a request request ID.

[0078] When the external device 20 receives the sensing data from the vehicle 1 (step S703), it determines the payment amount to the vehicle 1, and pays the determined payment amount from the external device wallet to the vehicle wallet (step S704). Next, the external device 20 notifies the vehicle 1 of the determined payment amount (step S705). At that time, the external device 20 notifies the vehicle 1 by adding the received billing request ID.

[0079] When the payment amount is received from the external device 20 (step S706), the transaction unit 106c of the vehicle 1 pays the received payment amount from the vehicle wallet to the user wallet (step S707). Next, the transaction unit 106c of the vehicle 1 displays the payment amount to the user on the information input / output unit 104 to notify the user (step S708).

[0080] When notifying the user of the payment amount, the user is notified using the information input / output unit 104 of the vehicle 1. As a result, the user of the information terminal 6 checks the payment amount from the vehicle 1 (step S709). Furthermore, it is possible to notify the user using the IVI (In-Vehicle Infotainment) or HUD (Head Up Display) of the vehicle 1. Specifically, it is possible to notify the user of the transaction between the vehicle 1 and the external device 20 in an easy-to-understand manner, as shown in Figs. 9 and 10 described later. Note that, in Figs. 6 and 7, it has been described that a transaction is executed between the vehicle 1 and the user wallet to compensate for each transaction between the external device 20 and the vehicle 1, but the present disclosure is not limited to this. For multiple transactions between the external device 20 and the vehicle 1, the user wallet may be transacted with the vehicle wallet in one transaction (via an intermediary wallet if necessary).

[0081] Fig. 8 is a flowchart showing an example of the flow of an electronic key selection process in the vehicle payment system according to the present embodiment. Fig. 8 is a flowchart explaining how a user's wallet is selected and notified to the vehicle 1 according to the electronic key selected by the user when the user starts using the vehicle 1.

[0082] After the user inputs the vehicle ID into the information terminal 6, the user selects one of the multiple electronic keys owned by the user depending on the intended use of the vehicle 1. If the electronic key is a personal electronic key indicating personal use, the information terminal 6 (or the application of the information terminal 6) notifies the vehicle 1 of wallet information indicating the personal wallet or payment method corresponding to the personal electronic key as user wallet information.

[0083] In addition, the vehicle insurance details corresponding to the personal electronic key, such as the insurance contract number and the contact information of the insurance company, are notified to the vehicle 1. The vehicle insurance applied to each electronic key is set in advance in the information terminal 6 (or the application of the information terminal 6), and by temporarily sharing the vehicle insurance information with the vehicle 1 until the end of use, in the unlikely event of an accident, it becomes possible to confirm the safety of the user and grasp the accident situation via the information input / output unit of the vehicle 1. The same is true for the company electronic key. The company wallet may be a wallet on a blockchain like the personal wallet, or a payment method such as a credit card, but is characterized in that it is linked to the budget code for each department of the company. Note that, although the flowchart has been described as notifying the vehicle 1, as described above, it may be notified to the vehicle management cloud 5 instead of the vehicle 1.

[0084] First, the user selects an electronic key according to the intended use of the vehicle 1 (step S801), and the information terminal 6 determines whether the selected electronic key is a personal electronic key or a company electronic key (step S802). If the electronic key selected by the user is a personal electronic key (step S802: personal electronic key), the information terminal 6 notifies the vehicle 1 of the personal wallet (or payment method) corresponding to the selected personal electronic key (step S803). The information terminal 6 also notifies the vehicle 1 of the vehicle insurance details (contract number, contact information, etc.) corresponding to the selected personal electronic key (step S804).

[0085] If the electronic key selected by the user is a company electronic key (step S802: company electronic key), the information terminal 6 notifies the vehicle 1 of the company wallet (or payment method) corresponding to the selected company electronic key (step S805). The information terminal 6 also notifies the vehicle 1 of the vehicle insurance details (contract number, contact information, etc.) corresponding to the selected company electronic key (step S806). In this way, not only is the wallet that serves as the payment method selected according to the electronic key selected by the user according to the purpose of vehicle use, but the vehicle insurance details linked to the electronic key are notified to the vehicle 1 (or the vehicle management cloud 5), so that when a problem including an accident occurs in the vehicle 1, the situation can be quickly shared with the insurance company. Furthermore, when a problem such as an accident occurs or when abnormal vibration is detected when the vehicle is broken into while parked, the vehicle 1 can automatically sound an alarm or share the sensing data acquired by the sensor unit 103 with the insurance company. In cases where a user of a shared car parks and leaves the vehicle, the vehicle is damaged, this may be objective circumstantial evidence.

[0086] 9 and 10 are diagrams for explaining an example of a process for notifying a user of a transaction between a vehicle and an external device in the vehicle payment system according to the present embodiment. In this figure, the lighting of the vehicle 1 is directed to illuminate the sidewalk in the area of ​​the dashed rectangular area on the right side. This can increase the safety of people on the sidewalk and help reduce the amount of light (electricity usage) of street lights when there is sufficient brightness. For example, the vehicle 1 (providing unit 106d) can broadcast that it is illuminating the sidewalk, and the lighting or sensor that receives the wireless communication signal can return 10 points to the vehicle 1. In such a case, the transaction unit 106c can display "sidewalk lighting (X city) +10p" on the screen of the information input / output unit 104 (IVI) of the vehicle 1, and can notify the user, together with a voice, that 10 points have been acquired from the local government (X city) due to the lighting of the sidewalk.

[0087] The trading unit 106c can also use the HUD to notify the user that 10 points have been acquired through the lighting of the sidewalk in a more understandable and natural way. For example, the trading unit 106c can easily understand that 10 points have been acquired through the lighting of the sidewalk by displaying visual information indicating that points have been acquired, such as "+10p", in or near the area of ​​the dashed rectangular area where the lighting of the sidewalk is being irradiated. The view through the windshield in FIG. 9 shows this, and "Traffic volume +5p" and "Sidewalk lighting +10p" displayed at the bottom of the windshield in FIG. 10 (in the direction of the point generation by the installed HUD) are also examples of visual information indicating the acquisition of points. In addition, at this time, the trading unit 106c can also notify the user of the direction in an easy-to-understand manner using stereophonic sound, so that the notification sound of the point acquisition is sounded from the direction of the dashed rectangular area where the lighting is irradiated.

[0088] Here, the trading unit 106c may add spatial position information to the point information, which indicates the point on the three-dimensional spatial coordinates at which the subject that returned the points (e.g., a light) returned the points. This allows the IVI or HUD to display visual information of the point return at the spatial position of the point return. Note that the musical note mark in the dashed rectangular area indicates that the virtual sound source position is at that position, and may or may not be actually displayed as visual information on the IVI or HUD.

[0089] Although the vehicle 1 (provider 106d) broadcasts information that the sidewalk is illuminated, the vehicle 1 may transmit information about the sidewalk lighting to the external device 20 such as a street lamp after mutual authentication with the external device 20 such as a street lamp. The mutual authentication may include at least one of the vehicle ID, the vehicle wallet, information from the vehicle 1 about the location, illuminance, and lighting time of the sidewalk lighting, the user ID, the electronic key being used, the user wallet, the external device ID of the information receiver, information about the operator of the external device 20, information about the compensation for providing information or service, and information about the reward message.

[0090] Similarly, the vehicle 1 (providing unit 106d) may broadcast information regarding traffic volume, and a traffic light at an intersection that receives the wireless communication signal may rebate 5 points to the vehicle 1. In this case as well, the trading unit 106c may notify the user in an easy-to-understand manner via visual information from the IVI, HUD, or information terminal 6, or via audio information.

[0091] Although the vehicle 1 (provider 106d) broadcasts information regarding traffic volume, the information regarding traffic volume may be transmitted to a traffic light after mutual authentication with the traffic light etc. The mutual authentication may include at least one of the vehicle ID, the vehicle wallet, the type of sensing data regarding traffic volume from the vehicle 1, the measurement date and time, the measurement location, information regarding measurement accuracy, the user ID, the electronic key being used, the user wallet, the external device ID of the information receiving side, the operator information of the external device 20, information regarding the compensation for the provision of information or service, and the reward message information.

[0092] When vehicle 1 exchanges information with an unspecified number of communication devices in its vicinity via wireless communication, it is conceivable that a large number of transactions and value exchanges will take place like this. In such cases, if transactions can be conducted without the need for the payment means of the user of vehicle 1 (including temporary users) to exchange with these communication devices, privacy concerns will be reduced, and it is expected that the number of users wishing to provide information will increase. In addition, parties who transact with the user (gas stations, charging stations, ETC gates, local governments, road management companies, etc.) will not have to handle personal information in each transaction, which has the advantage of avoiding the management burden of handling personal information and the risk of leaking the user's personal information.

[0093] FIG. 11 is a diagram for explaining an example of a transaction pattern of monetary value (including not only cash as described above, but also points issued by companies and local governments, and tokens traded on a blockchain) between an external device, a vehicle, and a user in the vehicle payment system according to this embodiment.

[0094] First, an example (upper part) of a basic pattern of transactions between the external device 20, the vehicle 1, and the user will be described. If the payment methods of the external device 20, the vehicle 1, and the user are all wallets recorded and managed in the blockchain, there is a possibility that all transaction histories (indicated by solid arrows) on the blockchain may be viewed by a third party. For this reason, it is possible to change the timing and amount of the two transactions. For example, the transaction unit 106c may perform transactions between the external device 20 (external device wallet) and the vehicle 1 (vehicle wallet) every time a transaction occurs, and between the vehicle 1 (vehicle wallet) and the user (user wallet), in addition to the transaction amount accumulated at the end of use, etc., the vehicle usage fee, and other expenses unrelated to the external device 20 may be added and processed collectively. By doing so, even if the transaction history on the blockchain can be tracked by a third party, the monetary value (transaction amount) and transaction date and time of the two transactions are significantly different, making it difficult for the external device 20 and a third party to identify the relationship between the external device 20 and the user.

[0095] Next, an example of a pattern (middle) in which a transaction between the vehicle 1 and the user is performed using a payment means that is not disclosed will be described. In the case of a transaction using a wallet recorded in the blockchain, there is a possibility that all transaction history (indicated by the solid arrow) may be viewed by a third party on the blockchain. For this reason, it is possible to take a means (indicated by the dashed arrow) for a transaction between the vehicle 1 and the user that is not recorded on the blockchain. For example, it is possible for the transaction unit 106c to exchange transactions between the external device 20 and the vehicle 1 on the blockchain between their respective wallets, and to carry out a transaction between the vehicle 1 and the user using a means that is not recorded on the blockchain, such as a credit card. Of course, a means other than a credit card may be used, such as a bank account or an electronic money account.

[0096] In this case, a billing request is issued from the vehicle wallet to the user's payment means (user wallet) at least once. It is considered that it would be troublesome to ask the user for confirmation via the information terminal 6 or the like every time. Therefore, the user may import the address of the vehicle wallet into the information terminal 6 (application of the information terminal 6) and give permission to the company providing the payment means to automatically make payments for bills from the vehicle wallet without asking the user for confirmation each time, during the vehicle usage period (during the period of notification of start and end from the information terminal 6 (application of the information terminal 6)), as long as the amount is below a certain amount or certain conditions are met. This permission may be given via the information input / output unit 104 of the information terminal 6 (application of the information terminal 6) or the IVI of the vehicle 1. In this way, it is possible to make it difficult for a third party to identify the relationship between the vehicle 1 and the user. Naturally, the relationship between the external device 20 and the user is even more difficult to identify.

[0097] Next, an example of a pattern (lower part) using a settlement means that mediates transactions between the external device 20, the vehicle 1, and the user will be described. If the user's settlement means is a personal or corporate wallet used by the user on the blockchain, a transaction record will remain on the blockchain, which may be viewed by a third party. In this case, the transaction unit 106c may perform the transaction via an intermediary wallet for intermediation, rather than directly between the vehicle wallet and the user wallet. If the same amount is traded each time a transaction occurs, it is easy for a third party to track the transaction, and there is a possibility that the relationship between the external device 20 and the user may be unraveled. For this reason, for example, it is conceivable to change the transaction timing and / or transaction amount using this intermediary wallet.

[0098] In the case of a shared car, it is considered that a transaction between the external device 20 and the vehicle 1 that occurs during use is performed each time it occurs. The vehicle wallet may be configured to transact with the intermediary wallet each time a transaction of the same amount occurs during use, or may be configured to transact with the intermediary wallet all at once after use ends. On the other hand, the intermediary wallet may be configured to transact with the user wallet at a timing and amount different from the transaction timing and transaction amount each time or all at once with the vehicle 1.

[0099] For example, the external device wallet and the vehicle wallet trade the amount at the time of occurrence of a transaction. The vehicle wallet and one of the intermediary wallets owned by the vehicle management company of the vehicle conduct a transaction to ensure that the balance of the vehicle wallet is at a certain level or more at a timing and amount different from the timing of the transaction with the external device, such as when the balance of the vehicle wallet falls below a certain amount. The same or another intermediary wallet owned by the vehicle management company and the user's wallet trade the usage fee for the use of the vehicle 1, including the total transaction amount between the external device 20 and the vehicle 1, at a timing according to the user's vehicle usage period, more specifically, for example, the transaction unit 106c trades the usage fee for the use of the vehicle 1, including the total transaction amount between the external device 20 and the vehicle 1, at the end of the use of the vehicle 1, etc. By doing this, even if all transactions are visualized on the blockchain, it is possible to make it difficult for a third party to track individual transactions because the transaction amount and transaction date and time are significantly different. By doing this, it is possible to make it difficult for a third party to identify the relationship between the vehicle 1 and the user. Naturally, the relationship between the external device 20 and the user is even more difficult to identify.

[0100] Thus, according to the vehicle payment system of this embodiment, when the vehicle 1 has a wallet (payment means), a transaction is performed between the external device 20 and the vehicle 1, and a transaction is performed between the vehicle 1 and the user's (information terminal 6) user wallet (payment means), thereby preventing user information (in particular, the user ID, the ID of the information terminal 6, email address, telephone number, personal wallet address information owned by the user, etc.) from leaking to the external device 20 during a transaction.

[0101] The programs executed by the vehicle 1 of this embodiment are provided by being pre-installed in a ROM (Read Only Memory) or the like. The programs executed by the vehicle 1 of this embodiment may be provided by being recorded in a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), or an SD card in the form of an installable or executable file.

[0102] Furthermore, the program executed by the vehicle 1 of the present embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the program executed by the vehicle 1 of the present embodiment may be provided or distributed via a network such as the Internet.

[0103] In addition, in this embodiment, in the in-vehicle system, an example of a processor (calculation unit 106) such as a CPU (Central Processing Unit) uses a RAM (Random Access Memory) or the like as a working area and executes various programs stored in a ROM (memory 107) or the RAM, etc., thereby realizing an acquisition unit 106a, a link unit 106b, a trading unit 106c, and a provision unit 106d.

[0104] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope of the invention and its equivalents described in the claims, as well as in the scope and spirit of the invention. [Explanation of symbols]

[0105] 1 vehicle 5. Cloud vehicle management 6 Information terminal 20 External equipment 60 External device management cloud 106 Arithmetic section 106a Acquisition Department 106b Link section 106c Trading Department 106d Providing Department 107 Memory

Claims

1. A control method executed by an in-vehicle system installed in a vehicle, comprising: In the in-vehicle system or a computer capable of communicating with the in-vehicle system, after it is determined that authentication information acquired from a user's communication terminal is valid, first wallet information indicating a first wallet associated with the authentication information is acquired from the communication terminal; linking vehicle wallet information indicating a vehicle wallet managed in the vehicle to the first wallet information; storing link information indicating that the vehicle wallet information and the first wallet information are linked in a memory in the vehicle-mounted system; Control methods.

2. In the communication terminal, a plurality of electronic keys available to the user and a plurality of pieces of wallet information indicating a plurality of wallets held by the user are managed in association with each other; the authentication information includes a first electronic key selected by the user from among the plurality of electronic keys; The control method described in claim 1, further comprising: obtaining, from the communication terminal, the first wallet information associated with the first electronic key from the multiple wallet information managed in the communication terminal after it is determined that the authentication information is valid.

3. The plurality of pieces of wallet information are information related to a plurality of payment services available to the user, The control method according to claim 2 , wherein the first electronic key is selected based on one of the plurality of payment services selected by the user via a GUI of the communication terminal.

4. the plurality of electronic keys include a company key associated with a company to which the user belongs and a personal key of the user; If the selected first electronic key is the company key, company wallet information indicating a company wallet managed by the company is linked to the vehicle wallet information as the first wallet information; The control method according to claim 2 , further comprising the step of: linking personal wallet information indicating a wallet of the user as the first wallet information to the vehicle wallet information when the selected first electronic key is the personal key.

5. Furthermore, in response to a request from an external device outside the vehicle or the in-vehicle system, a payment process is executed to pay money from the first wallet to an external wallet of the external device via the vehicle wallet; 3. The control method of claim 2, wherein the payment processing includes paying money from the vehicle wallet to the external wallet based on the vehicle wallet information, and receiving money paid from the first wallet to the vehicle wallet based on the vehicle wallet information and the first wallet information.

6. The control method described in claim 5, wherein payment of money from the vehicle wallet to the external wallet is executed without transmitting an ID for identifying the user or the communication terminal and the first wallet information to the external device.

7. the vehicle wallet information includes a vehicle wallet address indicating an address of the vehicle wallet; The first wallet information includes a first wallet address indicating an address of the first wallet, The payment from the vehicle wallet to the external wallet is performed by recording a first payment transaction using the address of the external wallet obtained from the external device and the vehicle wallet address on a blockchain; 6. The method of claim 5, wherein the payment from the first wallet to the vehicle wallet is performed by recording a second payment transaction using the first wallet address and the vehicle wallet on the blockchain.

8. The payment from the vehicle wallet to the external wallet is executed at a first timing when a request for payment occurs between the external device and the vehicle; The control method of claim 7 , wherein the payment from the first wallet to the vehicle wallet is executed at a second timing that is later than the first timing.

9. The control method according to claim 8 , wherein the second timing is a timing when the user stops or ends use of the vehicle, or a timing when a preset period ends.

10. A payment from the vehicle wallet to the external wallet is made in a first amount requested by the external device; 8. The method of claim 7, wherein a payment from the first wallet to the vehicle wallet comprises a payment of a second amount different from the first amount.

11. Furthermore, after linking the vehicle wallet information to the first wallet information, permission information is acquired in advance from the communication terminal; the authorization information indicates that the in-vehicle system has temporary authority to request and execute a transfer of money from the first wallet to the vehicle wallet; receiving a payment from the first wallet to the vehicle wallet, before or after a payment from the vehicle wallet to the external wallet, by the in-vehicle system based on the authorization information; The control method according to claim 5.

12. a payment from the first wallet to the vehicle wallet is pre-performed by transferring a predetermined amount from the first wallet to the vehicle wallet after linking the vehicle wallet information to the first wallet information; The control method according to claim 7 , wherein payment from the vehicle wallet to the external wallet is executed within the range of the predetermined amount at the time when a request for payment occurs between the external device and the vehicle.

13. the vehicle wallet information includes a vehicle wallet address indicating an address of the vehicle wallet; a payment from the vehicle wallet to the external wallet is performed by recording a payment transaction using the vehicle wallet address on a blockchain; The control method according to claim 5 , wherein the receipt of money paid from the first wallet to the vehicle wallet is performed by a settlement method that does not involve recording on the blockchain.

14. the payment processing is performed through an intermediary wallet, separate from the vehicle wallet, in addition to the vehicle wallet; receiving money from the first wallet in the payment transaction includes making a payment from the first wallet to the intermediary wallet and making a payment from the intermediary wallet to the vehicle wallet; 6. The method of claim 5, wherein payments from the vehicle wallet to the external wallet, payments from the intermediary wallet to the vehicle wallet, and payments from the first wallet to the intermediary wallet are performed by recording each payment transaction on a blockchain.

15. 15. The method of claim 14, wherein at least two of the respective payment transactions are recorded at different times.

16. After the payment process, sending a payment report to the communication terminal indicating that the payment process has been completed; The control method according to claim 5 , wherein the payment report includes payee information for identifying the external device or the external wallet, and information on a payment amount.

17. After the payment process, display a payment report on a display mounted on the vehicle indicating that the payment process has been completed; The control method according to claim 5 , wherein the display content of the payment report includes a display object for identifying the external device.

18. the external device is a charger for charging a battery of the vehicle, The control method according to claim 16 or 17, wherein the payment report includes information on the amount of charge charged in the battery.

19. the plurality of electronic keys includes a company key associated with a company to which the user belongs and a personal key of the user; If the selected first electronic key is the company key, company wallet information indicating a company wallet managed by the company is linked to the vehicle wallet information as the first wallet information; After the payment process, a payment report indicating that the payment process using the company wallet has been completed is sent to a company server associated with the company to which the user belongs; If the selected first electronic key is the personal key, linking personal wallet information indicating the wallet of the user to the vehicle wallet information as the first wallet information; The control method according to claim 5 , further comprising the step of: after the payment processing, sending a payment report indicating that the payment processing using the user's wallet has been completed to the communication terminal or a personal server used by the user.

20. Furthermore, in response to a request from an external device outside the vehicle or the vehicle, a receiving process is executed to receive money paid to the first wallet from an external wallet of the external device via the vehicle wallet; The receiving process includes: receiving money paid from the external wallet to the vehicle wallet based on the vehicle wallet information; 2. The method of claim 1, further comprising: transferring money from the vehicle wallet to the first wallet based on the vehicle wallet information and the first wallet information.

21. The control method described in claim 20, wherein receipt of money paid from the external wallet to the vehicle wallet is performed without transmitting an ID for identifying the user or the communication terminal and the first wallet information to the external device.

22. the vehicle wallet information includes a wallet address indicating an address of the vehicle wallet; Receiving money paid from the external wallet to the vehicle wallet is performed by recording a payment transaction using the wallet address on a blockchain; The control method of claim 20, wherein the transfer from the vehicle wallet to the first wallet is performed by a settlement method that does not involve recording on the blockchain.

23. Furthermore, the vehicle provides detection data obtained by detecting the running state of the vehicle or the surrounding conditions of the vehicle to a traffic infrastructure system related to a road on which the vehicle is traveling; the external device is at least a part of the transportation infrastructure system; The control method according to claim 20 , wherein the payment from the external wallet is a payment for providing the detection data to the transportation infrastructure system.

24. In an in-vehicle system mounted in a vehicle or a computer capable of communicating with the in-vehicle system, After determining that authentication information obtained from a user's communication terminal is valid, obtain first wallet information from the communication terminal, the first wallet information indicating a first wallet associated with the authentication information; linking vehicle wallet information indicating a vehicle wallet managed in the vehicle to the first wallet information; storing link information indicating that the vehicle wallet information and the first wallet information are linked in a memory in the vehicle-mounted system; A program that causes a processor to execute a process.

25. A control device in an in-vehicle system mounted in a vehicle or a computer capable of communicating with the in-vehicle system, A processor; a memory in which a program for causing the processor to execute a predetermined process is stored; The processor, based on the program, after determining that authentication information obtained from a user's communication terminal is valid, obtaining first wallet information from the communication terminal, the first wallet information indicating a first wallet associated with the authentication information; linking vehicle wallet information indicating a vehicle wallet managed in the vehicle to the first wallet information; storing link information indicating that the vehicle wallet information and the first wallet information are linked in a memory in the vehicle-mounted system; Control device.

Images