Notification method, vehicle management system

Abstract

To notify a user of a vehicle possessing power of a facility requesting such power when the facility requests power generated by a specific scheme.SOLUTION: A notifying method includes: determining a destination candidate of a vehicle from multiple facilities by using first information on the vehicle and second information on the multiple facilities requesting power (S16 and S17); and transmitting the determined destination candidate to a user terminal of the vehicle (S18). The first information includes a power generation type of power stored in a battery device of the vehicle. The second information includes a power generation type of power requested by each of the multiple facilities.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present disclosure relates to a notification method and a vehicle management system.

Background Art

[0002] Facilities with EVSE (Electric Vehicle Supply Equipment) installed on the premises are known. EVSE is power supply equipment for vehicles and supplies power to vehicles equipped with a power storage device. For example, Japanese Patent Application Laid-Open No. 2015-231324 (Patent Document 1) discloses a technique for scheduling the power supplied to a vehicle at each EVSE using reservation information from facility users.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In recent years, the development of V2H (Vehicle to Home) technology has been promoted. V2H technology is a technology for discharging power from a vehicle equipped with a power storage device to a house, and is also applicable to buildings other than houses (for example, facilities). By using such V2H technology, a system that allows a vehicle to carry power to a facility and supply power from the vehicle to the facility can be realized.

[0005] In recent years, electric power has been classified according to the power generation method, and there is a tendency to evaluate that the power generated by a method with a lower environmental load has a higher environmental value. For this reason, depending on the facility, it may require power generated by a specific method. Specifically, facilities that require renewable energy, such as facilities participating in RE100 (Renewable Energy 100%), are assumed.

[0006] If the information on the facility that is seeking the power held by the vehicle can be notified to the user of the vehicle, the user can drive the vehicle to transport the power to the facility and deliver the power to the facility by means of V2H technology. However, an effective technology for notifying the above-mentioned user of the vehicle of the above-mentioned facility has not yet been proposed.

[0007] The present disclosure has been made to solve the above problems, and an object thereof is to notify the user of a vehicle having the power that the facility seeking the power generated by a specific method is seeking the power.

Means for Solving the Problems

[0008] According to an aspect according to the first aspect of the present disclosure, the following notification method is provided.

[0009] (Item 1) The notification method includes determining a candidate destination of the vehicle from among a plurality of facilities using first information regarding the vehicle and second information regarding the plurality of facilities that request power, and transmitting the determined candidate destination to a user terminal of the vehicle. The first information includes the type of power generation of the power stored in the power storage device provided in the vehicle. The second information includes the type of power generation of the power requested by each of the plurality of facilities.

[0010] In the above method, a candidate destination of the vehicle is transmitted to the user terminal. At this time, a candidate destination of the vehicle is determined using first information indicating the type of power generation of the power stored in the power storage device provided in the vehicle and second information indicating the type of power generation of the power requested by each of the plurality of facilities. Therefore, according to the above method, when the facility is seeking the power generated by a specific method, it is possible to notify the user of the vehicle having the power that the facility seeking the power is a candidate destination of the vehicle.

[0011] The notification method described in the above Item 1 may have the configuration described in any one of Items 2 to 4 shown below.

[0012] (2) The notification method according to item (1) further has the following characteristics. The first information further includes the amount of power that can be discharged from the power storage device and the position of the vehicle. The second information further includes the amount of power required by each of the plurality of facilities and the position of each of the plurality of facilities.

[0013] According to the above method, the vehicle and the facility are matched from the viewpoints of position and power amount, and it becomes easier to notify the user of the vehicle of the facility suitable for the position and state (for example, remaining charge amount) of the vehicle as a candidate for the destination of the vehicle.

[0014] (3) The notification method according to item (1) or (2) further has the following characteristics. Determining the candidate for the destination includes excluding a facility that is more than a predetermined distance away from the position of the vehicle from the candidates for the destination, and excluding a facility that requires power of a power generation type not stored in the power storage device from the candidates for the destination.

[0015] According to the above method, a facility suitable for the position and stored power of the vehicle is notified to the user of the vehicle as a candidate for the destination of the vehicle. Therefore, it becomes easier for the vehicle to supply the power required by the facility to that facility.

[0016] (4) The notification method according to any one of items (1) to (3) further has the following characteristics. The notification method further includes lowering the upper limit value of the incentive that the facility gives to the vehicle when the vehicle supplies the power required by the facility as the number of users of the facility that requires power decreases.

[0017] The facility selected as the destination of the vehicle can not only receive power supply from the vehicle, but also has a higher possibility of being used by the vehicle user who visits the facility. In the above method, as the number of users of the facility decreases, the upper limit value of the incentive (the upper limit value of the incentive per vehicle) that the facility gives to one vehicle is lowered. By paying a small incentive to many vehicles, it becomes possible to attract many vehicles to the facility without increasing the total amount of incentives.

[0018] According to one form, a program is provided that causes a computer to execute the notification method according to any one of claims 1 to 4. In another form, a computer device that distributes the program is provided.

[0019] According to the form related to the second aspect of the present disclosure, a vehicle management system shown below is provided.

[0020] (Claim 5) The vehicle management system includes a computer device including a processor and a storage device that stores a program that causes the processor to execute the notification method according to any one of claims 1 to 4, a vehicle, and a user terminal. The vehicle is configured to record the power generation type of the charged power when the power storage device is charged. The user terminal is configured to display a candidate destination including a plurality of facilities received from the computer device, request the user to select one facility from the plurality of displayed facilities, and transmit identification information of the facility selected by the user to the computer device.

[0021] According to the vehicle management system, by the computer device executing the notification method according to any one of claims 1 to 4, when a facility is requesting power generated by a specific method, the user of the vehicle having that power can be notified of the facility requesting that power as a candidate destination of the vehicle.

[0022] Note that the vehicle may be an electric vehicle (xEV) that uses power as all or part of the power source. xEVs include BEV (battery electric vehicle), PHEV (plug-in hybrid vehicle), FCEV (fuel cell vehicle), etc.

Advantages of the Invention

[0023] According to the present disclosure, when a facility is requesting power generated by a specific method, it becomes possible to notify the user of the vehicle having that power of the facility requesting that power.

Brief Description of the Drawings

[0024]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Embodiments for Carrying Out the Invention

[0025] Embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals and their descriptions are not repeated.

[0026] FIG. 1 is a diagram for explaining the outline of a vehicle management system according to an embodiment of the present disclosure. Referring to FIG. 1, the vehicle management system according to this embodiment includes a server 100, a plurality of vehicles (for example, vehicles 10A and 10B), a plurality of facilities (for example, facilities 30A to 30C), a plurality of retail electricity providers (for example, retail electricity providers 411 and 412), and a plurality of power generation facilities (for example, power generation facilities 421 and 422). Also, nodes corresponding individually to the vehicles, facilities, retail electricity providers, and power generation facilities, and a blockchain connecting each node are implemented on a cloud 500. The server 100 is also connected to the blockchain and functions as one node of the blockchain. The server 100 may function as a super node. A platform for managing vehicles and facilities is constructed on the cloud 500 by blockchain technology.

[0027] Each node of the blockchain shares a ledger (blockchain ledger) based on distributed ledger technology. By having multiple nodes with common data, high availability (the property of being difficult to go down) can be achieved. In the blockchain, data tampering prevention is achieved by updating the ledger based on a predetermined consensus algorithm (for example, PoW, PoS, DPoS, PoI, PoC, or Ordering Service). Also, the reliability of data can be ensured by means such as electronic signatures. P2P (Peer to Peer) power trading may be conducted on the blockchain using smart contracts.

[0028] The blockchain ledger records who generated how much power, where, and by what method, and where the generated power was supplied or stored. For example, the retail ID or generation ID described later indicates who generated the power. Also, for example, in the form of the power coloring information shown in FIG. 1, how much power was generated and by what method is recorded in the ledger. The flow (circulation process) and location (storage location) of the generated power are indicated, for example, by the power tracking information described later. When power delivery occurs, the power tracking information is updated at both nodes. With distributed ledger technology, the flow of power can be tracked in real time.

[0029] Retail electricity provider 411 procures power generated by, for example, renewable energy (such as solar, wind, hydro, geothermal, etc.) and sells the procured power via the power grid. Retail electricity provider 412 sells the power generated by its own power supply equipment (hereinafter also referred to as "Power G") via the power grid. The power generation type of Power G includes thermal power. The power generation type of Power G may further include at least one of nuclear power, pumped storage, and renewable energy (RE) in addition to thermal power.

[0030] Nodes corresponding to each retail electricity provider (hereinafter referred to as "retail nodes") manage the electricity handled by the corresponding retail electricity provider. Each retail node records information on the electricity procured by the corresponding retail electricity provider (hereinafter also referred to as "retail information") in the blockchain ledger. The retail information includes the identification information of the retail electricity provider (retail ID), the electricity storage location (e.g., the identification information of the energy storage device), the power generation type, the power generation amount (Wh), and the power tracking information.

[0031] The classification method of the power generation type can be arbitrarily set. In this embodiment, the power generation type is classified as RE, solar power, wind power, non-RE, etc. The power generation type of the electricity sold by the retail electricity provider 411 is classified as "RE". Since the power generation type of the power source G includes other than RE, the power generation type of the electricity sold by the retail electricity provider 412 is classified as "non-RE".

[0032] The power tracking information included in the retail information indicates the flow of the electricity procured by the retail electricity provider. If the retail electricity provider retains the procured electricity, the retail node records in the blockchain ledger the power tracking information indicating that the procured electricity is at the electricity storage location. When the retail electricity provider sells the procured electricity, the retail node cooperates with the node corresponding to the destination (purchaser) of the electricity to record the electricity distribution process in the blockchain ledger. The retail node may update the blockchain ledger in cooperation with the facilities and terminals held by the retail electricity provider.

[0033] Note that in FIG. 1, only two retail electricity providers 411 and 412 are shown, but the number of retail electricity providers participating in the platform (blockchain) is arbitrary, and may be, for example, 3 or more and less than 20, or 20 or more. Also, the power generation type of the electricity sold by the retail electricity provider is not limited to the above, and other power generation methods may be used.

[0034] The power generation facility 421 is, for example, a solar power generation facility. The power generation facility 421 may be a large-scale solar power system (megasolar). Alternatively, the power generation facility 421 may be a solar panel installed on the roof of a house. The power generation facility 422 is, for example, a wind power generation facility. The power generation facility 422 may be an onshore wind farm or an offshore wind farm.

[0035] The node corresponding to each power generation facility (hereinafter referred to as "power generation node") manages the power generated by the corresponding power generation facility. Each power generation node records information regarding the power generated by the corresponding power generation facility (hereinafter also referred to as "power generation information") in the blockchain ledger. The power generation information includes the identification information (power generation ID) of the power generation facility, the type of power generation (e.g., solar or wind), the amount of power generation (Wh), and power tracking information. The power tracking information included in the power generation information indicates the flow of the power generated by the power generation facility. Each power generation node records the power distribution process in the blockchain ledger in cooperation with the node corresponding to the destination of the power generated by the corresponding power generation facility.

[0036] Note that although only two power generation facilities 421 and 422 are shown in FIG. 1, the number of power generation facilities participating in the platform (blockchain) is arbitrary and may be, for example, 3 or more and less than 20, or 20 or more. Also, the type of power generation of the power generated by the power generation facility is not limited to solar and wind power, and may be other power generation methods (e.g., thermal power, hydraulic power, geothermal power, or biomass).

[0037] Each vehicle included in the vehicle management system is an xEV (electric vehicle) equipped with a power storage device and participates in a platform (blockchain). For example, vehicles 10A and 10B are BEVs (battery electric vehicles) equipped with batteries 11A and 11B respectively. Each vehicle is configured to be able to perform external charging (charging the above power storage device with power from outside the vehicle) and external power supply (supplying power outside the vehicle with the power discharged from the above power storage device). The vehicle may perform external charging or external power supply while connected to an EVSE (Electric Vehicle Supply Equipment) (plug-in state). The vehicle may perform external charging using an EVSE (home charger) installed at the user's home. The vehicle may perform external charging using a public EVSE. Also, the vehicle may perform power supply (external power supply) to a building such as a home or a facility by V2H (Vehicle to Home) technology. Each vehicle communicates with the corresponding node and updates the blockchain ledger every time external charging or external power supply is performed.

[0038] The node corresponding to each vehicle (hereinafter referred to as "vehicle node") manages the power held by the corresponding vehicle. Each vehicle node records information about the corresponding vehicle (hereinafter also referred to as "vehicle information") in the blockchain ledger. The vehicle information includes a vehicle ID (identification information of the vehicle), the specifications of the vehicle regarding charge and discharge capabilities (for example, full charge capacity, rated charging power, and rated discharge power), position information indicating the position where external charging or external discharge was last performed, power coloring information, and power tracking information. The power coloring information indicates the amount of power for each power generation type stored in the power storage device of the vehicle. For example, the power coloring information shown in FIG. 1 indicates that battery 11A holds P1 (kWh) of power generated by a power source configuration including other than RE (renewable energy), P2 (kWh) of power generated by sunlight, and P3 (kWh) of power generated by RE (renewable energy).

[0039] The power tracking information included in the vehicle information indicates the flow of power stored in the vehicle's power storage device. When external charging or external power supply is executed, the location information, power coloring information, and power tracking information are updated. When external charging is executed, the vehicle node cooperates with the node corresponding to the power supply source to record the power distribution process in the blockchain ledger. When external power supply is executed, the vehicle node cooperates with the node corresponding to the destination of the power to record the power distribution process in the blockchain ledger.

[0040] The vehicle node records the power generation type of the power clearly generated by sunlight among the REs as "sunlight" (individual RE), and records the power generation type of the power that is clearly generated by RE but the RE by which it is generated is unknown as "RE" (RE in general). For example, when the user purchases power from the retail electricity provider 411 and charges the vehicle's power storage device, the vehicle node records the power generation type of the power as "RE". Also, when the power generated by the power generation facility 421 is charged to the vehicle's power storage device, the vehicle node records the power generation type of the power as "sunlight". Also, when the user purchases power from the retail electricity provider 412 and charges the vehicle's power storage device, the vehicle node records the power generation type of the power as "non-RE".

[0041] When the vehicle is in the plug-in state, information indicating the state of the vehicle (such as SOC) is uploaded to the vehicle node, and the vehicle node updates the power coloring information. If the current SOC value of the power storage device at the current (this update) is lower than the SOC value at the previous update, the vehicle node assumes that the power corresponding to the difference was consumed during the vehicle's travel. At this time, the vehicle node assumes that the power stored in the power storage device at the previous update was consumed in order from the power with a low environmental value. The higher the environmental value of the power generated by a method with a low environmental load. That is, RE has a higher environmental value than non-RE. The vehicle node may assume that the power with an equal environmental value was consumed evenly. SOC (State Of Charge) indicates the remaining charge, and for example, represents the ratio of the current charge amount to the fully charged state charge amount as 0 to 100%.

[0042] Note that although only two vehicles 10A and 10B are shown in FIG. 1, the number of vehicles participating in the platform can be arbitrary. For example, it may be 3 or more and less than 100, or 100 or more. The vehicles are not limited to BEVs without internal combustion engines, and may be PHEVs with internal combustion engines, or other vehicle types (e.g., FCEVs).

[0043] Each facility included in the vehicle management system is equipped with a power storage device and an EVSE within the site and participates in the platform (blockchain). Each facility monitors the power supply and demand balance. When the power is insufficient, it requests power from the server 100, and when there is surplus power, it stores the surplus power in the power storage device. The EVSE of the facility functions as a V2H charger (power conditioner between the vehicle and the facility). Specifically, the EVSE has both the function of converting the power discharged from the vehicle into power that can be used in the facility and the function of converting the power supplied by the facility into power that can be used by the vehicle. Each facility may supply power to the vehicle through the EVSE. Also, each facility may receive power supply from the vehicle through the EVSE.

[0044] The node corresponding to each facility (hereinafter referred to as the "facility node") manages the power handled by the corresponding facility. Each facility node records information about the corresponding facility (hereinafter also referred to as "facility information") in the blockchain ledger. The facility information includes a facility ID (identification information of the facility), a classification according to the business type, a location (e.g., latitude and longitude), information indicating the relationship between the facility and the power grid (on-grid / off-grid), the power generation type of the power handled by the facility, the stored power amount, and power tracking information. The facility information may further include information other than the above (e.g., the name of the facility).

[0045] Each facility is classified into one of the categories according to its business type. For example, Facility 30A is a restaurant and belongs to Category A. Facility 30B is a convenience store and belongs to Category B. Facility 30C is a fitness gym and belongs to Category C. Note that the number of categories is not limited to three and can be arbitrary. Examples of business types other than the above include cafeterias, hotels, department stores, supermarkets, shopping malls, etc. Figure 1 shows only three facilities 30A to 30C, but the number of facilities participating in the platform can be arbitrary. For example, it may be 4 or more and less than 100, or 100 or more.

[0046] Off-grid facilities are independent of the power grid and do not receive power supply from the power grid. In contrast, on-grid facilities are connected to the power grid and can receive power supply from the power grid. The types of power generation for the power handled by the facilities are two types: "RE100 (Renewable Energy 100%)" and others (non-RE). In RE100 facilities, only power generated from renewable energy is handled. RE100 on-grid facilities may purchase power from retail electricity provider 411, but do not purchase power from retail electricity provider 412. RE100 off-grid facilities basically ensure the required amount of power by on-site variable power sources (e.g., power generation equipment such as solar panels). However, when demand exceeds supply and power is insufficient, they request power generated from renewable energy from server 100. In contrast, facilities that receive power supply generated from non-renewable energy are classified as "non-RE". Server 100 is a computer belonging to the aggregator, and in the following, server 100 may be referred to as the "aggregator server". The configuration of server 100 will be described later (see Figure 2).

[0047] The stored electric energy indicates the amount of electric energy (Wh) stored in the energy storage device within the facility site. All the electric power stored in the energy storage device of the RE100 facility is treated as electric power of the power generation type "RE". Also, all the electric power stored in the energy storage device of the non-RE facility is treated as electric power of the power generation type "non-RE". The power tracking information included in the facility information indicates the flow of electric power handled by the facility. When the facility supplies electric power to a vehicle through an EVSE, the facility node cooperates with the node corresponding to the destination of the electric power (vehicle node) to record the process of electric power circulation in the blockchain ledger. For example, when the electric power supplied by the RE100 facility is charged to the energy storage device of the vehicle, the vehicle node records the power generation type of that electric power as "RE". Also, when the electric power supplied by the non-RE facility is charged to the energy storage device of the vehicle, the vehicle node records the power generation type of that electric power as "non-RE". The facility node may update the blockchain ledger at a predetermined cycle in cooperation with the server provided within the facility.

[0048] Figure 2 is a diagram for explaining external power supply from a vehicle to a facility. Each vehicle and each facility included in the vehicle management system have, for example, the configuration (common configuration) shown in Figure 2. Hereinafter, when not distinguishing those vehicles, they are referred to as "Vehicle 10", and when not distinguishing those facilities, they are referred to as "Facility 30". In the example shown in Figure 2, Vehicle 10 is parked within the site of Facility 30. The user of Vehicle 10 holds a mobile terminal 20. The mobile terminal 20 functions as a user terminal of Vehicle 10.

[0049] The server 100 includes a processor 110, a RAM (Random Access Memory) 120, and a storage device 130. As the processor 110, for example, a CPU (Central Processing Unit) can be adopted. The storage device 130 is configured to be able to store the stored information. By the processor 110 executing the program stored in the storage device 130, various processes (for example, a series of processes shown in Figure 4 described later) are executed. However, these various processes are not limited to being executed by software, and can also be executed by dedicated hardware (electronic circuit).

[0050] Facility 30 includes a server 310, an EVSE 320, a camera 330, and a power supply device 350. The server 310 is a computer configured to be able to utilize a platform on the cloud 500 via a communication network NW. The server 100 and the server 310 communicate with each other via the communication network NW. The communication network NW is a wide area network constructed by, for example, the Internet and a wireless base station. The EVSE 320 is installed outdoors at the facility 30 (for example, in a parking lot within the site of the facility 30). The camera 330 includes a camera for monitoring the interior of the facility 30 and a camera for monitoring the exterior of the facility 30. The camera 330 outputs the acquired video to the server 310. The server 310 sequentially acquires the number of users of the facility 30 based on the video of the camera 330.

[0051] The power supply device 350 includes, for example, a distribution board that supplies power to various devices installed within the site of the facility 30. In the form where the facility 30 is on-grid, the power supply device 350 is electrically connected to the power grid. In the form where the facility 30 is off-grid, the power supply device 350 is not connected to the power grid. The power supply device 350 may be electrically connected to a power generation facility (for example, a solar power generation facility) installed within the site of the facility 30. The power supply device 350 may further include a power storage device that stores the generated power.

[0052] The vehicle 10 includes a battery 11, an inlet 12, an HMI (Human Machine Interface) 13, a communication device 14, and an electronic control unit (hereinafter referred to as "ECU (Electronic Control Unit)") 15.

[0053] As the battery 11, a known vehicle power storage device (for example, a liquid secondary battery, a all-solid-state secondary battery, or a battery pack) can be adopted. Examples of vehicle secondary batteries include lithium-ion batteries and nickel-metal hydride batteries.

[0054] ECU 15 is a computer including, for example, a processor and a storage device. HMI 13 includes an input device and a display device. HMI 13 may include a touch panel display. In this embodiment, HMI 13 includes a navigation system. HMI 13 may further include at least one of a meter panel and a head-up display. HMI 13 may further include a smart speaker that receives voice input.

[0055] ECU 15 communicates with a device outside the vehicle through communication device 14. Communication device 14 includes a TCU (Telematics Control Unit) and / or a DCM (Data Communication Module) that perform wireless communication. ECU 15 communicates with server 100 while the vehicle 10 is running. ECU 15 is configured to be able to utilize a platform on cloud 500 via communication network NW. Also, communication device 14 includes a communication I / F for directly communicating with a mobile terminal 20 existing within the vehicle or in the vicinity of the vehicle. Vehicle 10 (ECU 15) and mobile terminal 20 may perform short-range communication such as wireless LAN (Local Area Network), NFC (Near Field Communication), or Bluetooth (registered trademark).

[0056] In this embodiment, a smartphone having a touch panel display is adopted as mobile terminal 20. The smartphone incorporates a computer including a processor and a storage device. By the processor executing a program stored in the storage device, various processes (for example, a series of processes shown in FIG. 5 described later) are executed. Also, mobile terminal 20 accesses communication network NW by wireless communication and communicates with server 100 via communication network NW. However, it is not limited to this, and any mobile terminal can be adopted as mobile terminal 20. For example, a laptop, a tablet terminal, a portable game machine, a wearable device (such as a smartwatch, smart glasses, smart gloves, etc.), an electronic key, etc. can also be adopted as mobile terminal 20.

[0057] The main body of the EVSE320 incorporates a control unit 321 and a circuit unit 322. The EVSE320 further includes a touch panel display (hereinafter referred to as "TPD") 323 and a charging cable 324. The control unit 321 includes a processor and a storage device, and controls the circuit unit 322 according to a command from the server 310. The circuit unit 322 includes a circuit for supplying power to the vehicle 10 (charging the battery 11) and a circuit for supplying power to the power supply equipment 350 of the facility 30. The charging cable 324 has a connector 325 (plug) at its tip.

[0058] The connector 325 is configured to be detachable from the inlet 12 of the vehicle 10. The inlet 12 corresponds to a charging / discharging port that functions as both a charging port and a discharging port. When the connector 325 of the charging cable 324 connected to the main body of the EVSE320 is connected to the inlet 12 of the parked vehicle 10, the vehicle 10 is in an electrically connected state (plugged-in state) with the EVSE320. On the other hand, for example, during the running of the vehicle 10, the vehicle 10 is in a state where it is not electrically connected to the EVSE320 (plugged-out state).

[0059] The EVSE320 is provided with a connection detection circuit (not shown) that detects the state of the connector 325 (plugged-in state / plugged-out state). The connection detection circuit outputs the state of the connector 325 to the control unit 321. The control unit 321 acquires information indicating the operating status of the EVSE320 (for example, the charging power from the power supply equipment 350 to the vehicle 10 and the discharging power from the vehicle 10 to the power supply equipment 350) from a sensor (not shown) included in the circuit unit 322. In this embodiment, only the vehicle 10 participating in the platform (blockchain) is permitted to use the EVSE320. The server 310 identifies the vehicle 10 using the EVSE320 based on the vehicle ID received from the vehicle 10 and permits the use of the EVSE320. During the period when the EVSE320 is being used, information regarding the EVSE320 and information regarding the vehicle 10 using the EVSE320 (for example, SOC and power coloring information) are sequentially transmitted from the EVSE320 to the server 310.

[0060] When the power of facility 30 is insufficient and the vehicle 10 and the EVSE 320 are in a plugged-in state, when the server 310 determines, based on the blockchain ledger (for example, the power coloring information of the vehicle 10), how much power the vehicle 10 has that meets the power requirements of the facility 30. For example, if the power generation type of the power handled by the facility 30 is "RE100", the facility 30 requests power generated by renewable energy (RE). Hereinafter, the amount of power that the vehicle 10 holds that meets the power requirements of the facility 30 is referred to as the "target remaining power". For example, in the power coloring information shown in FIG. 1, the amount of power (power generated by RE) required by the RE100 facility 30 is "P2 + P3" (kWh), which corresponds to the target remaining power.

[0061] The server 310 obtains the target remaining power of the vehicle 10 as described above. After that, the TPD 323 displays, for example, the screen Sc1. The screen Sc1 displays a message requesting the vehicle 10 to discharge, together with the target remaining power of the vehicle 10, the current SOC of the battery 11, and information regarding incentives (for example, the incentive unit price). Further, the screen Sc1 displays an operation unit M11 for accepting an input of approval and an operation unit M12 for accepting an input of rejection.

[0062] When the operation unit M11 is operated by the user of the vehicle 10, the server 310 executes the discharge control of the battery 11 while communicating with the control unit 321 of the EVSE 320. When the power shortage of the facility 30 is eliminated by the discharge of the battery 11, or when the target remaining power amount of the vehicle 10 runs out, the server 310 terminates the discharge of the battery 11. Also, the server 310 terminates the discharge of the battery 11 even when it receives a discharge stop request from the vehicle 10 or the EVSE 320. When the discharge of the battery 11 ends, the TPD 323 displays, for example, the screen Sc2. The screen Sc2 displays information indicating the incentive obtained by the user of the vehicle 10 by this discharge, together with a message notifying the end of the discharge. Further, the server 310 may send a discharge end notification to the mobile terminal 20. When the operation unit M12 is operated on the screen Sc1, the process by the EVSE 320 ends without the discharge of the battery 11 being executed.

[0063] In this embodiment, an incentive point system is adopted. That is, the incentive acquisition amount is counted in points (pt). A high number of points means a high value. The points may be treated like virtual currency or may be exchangeable for money. Also, the points may be convertible into goods or rights (for example, the right to receive services corresponding to the number of points). In this embodiment, as the incentive unit price, the number of points per unit discharge amount (pt / Wh) is adopted. However, it is not limited to this, and the incentive unit price may be the unit price for the number of discharges or the unit price for the discharge time. The incentive mechanism is not limited to the above incentive point system and can be arbitrarily determined by contract.

[0064] FIG. 3 is a diagram for explaining information received by the server 100 (aggregator server) from each vehicle and each facility. The facility group shown in FIG. 3 is included in the vehicle management system shown in FIG. 1. In FIG. 3, facilities belonging to section A are denoted as "A-1", "A-2", ···, facilities belonging to section B are denoted as "B-1", "B-2", ···, and facilities belonging to section C are denoted as "C-1", "C-2", ···.

[0065] Referring to FIG. 3, each vehicle (vehicles 10A, 10B, ···) included in the vehicle management system shown in FIG. 1 sequentially transmits its real-time position and SOC to the server 100 together with the vehicle ID. These pieces of information are stored in the storage device 130 (FIG. 2). The storage device 130 manages the current position and current SOC of each vehicle, distinguishing them by vehicle ID.

[0066] Predetermined application software (hereinafter referred to as "mobile app") is installed on the user terminal (mobile terminals 20A, 20B, ···) of each vehicle. Each user terminal can exchange information with the server 100 through the mobile app. The user of vehicle 10 can specify the type of facility (for example, any of sections A to C) that the user wants to use by operating the mobile terminal 20 (the user terminal of vehicle 10) shown in FIG. 2. Further, the user can request the server 100 to extract one or more facilities belonging to the specified type (section) and matching the current situation (for example, position and state) of the current vehicle 10 from the facility group shown in FIG. 3, and notify the extracted facilities to the mobile terminal 20. The mobile terminal 20 transmits a signal (hereinafter referred to as "facility search request") for requesting the above extraction and notification to the server 100 in response to the user operation.

[0067] The facility search request includes the vehicle ID, the type (category) of the facility, and the lower SOC value. The server 100 uses the vehicle ID included in the facility search request to obtain information on the vehicle 10 that sent the facility search request from the blockchain ledger. The type of the facility is specified by the user as described above. However, the ECU 15 or the mobile terminal 20 may specify the type of the facility on behalf of the user. The ECU 15 or the mobile terminal 20 may estimate the facility that the user wants to use from the history data regarding the movement of the vehicle 10. The lower SOC value is the lower limit value of the SOC indicating the discharge limit of the vehicle, and is preset for each vehicle. In the vehicle 10 shown in FIG. 2, discharging is prohibited when the SOC of the battery 11 falls below the lower SOC value, and when the SOC of the battery 11 reaches the lower SOC value, the ECU 15 forcibly terminates the discharging of the battery 11. The lower SOC value may be a fixed value. An arbitrary value may be set as the lower SOC value by the vehicle user. Further, the ECU 15 or the mobile terminal 20 may set the lower SOC value based on the history data of the vehicle 10.

[0068] Each server 310 (FIG. 2) included in the facility group shown in FIG. 3 monitors the power supply-demand balance of the facility, and when the power is insufficient, transmits a signal for requesting power (hereinafter referred to as "power request") to the server 100. The power request includes the facility ID, the power generation type of the requested power (hereinafter referred to as "request type"), the amount of the requested power (hereinafter referred to as "requested Wh"), the current number of facility users, and the incentive standard unit price. In this embodiment, the request type of the RE100 facility is "RE", and the request type of the non-RE facility is "unspecified (RE and non-RE)". The incentive standard unit price is a parameter used in the process shown in FIG. 4 described later, and is preset for each facility. The incentive standard unit price may be a fixed value. An arbitrary value may be set as the incentive standard unit price by the facility administrator. Further, the server 310 may set the incentive standard unit price based on the power price.

[0069] FIG. 4 is a flowchart showing the processing procedure of the notification method according to this embodiment. The processing shown in this flowchart is executed by the server 100 when the server 100 receives the above facility search request. The server 100 executes a series of processes shown in FIG. 4 described below for the vehicle (hereinafter referred to as the "target vehicle") that sent the above facility search request. Hereinafter, each step in the flowchart is simply denoted as "S".

[0070] Referring to FIG. 4, in S11, the server 100 acquires information regarding the target vehicle based on the vehicle ID. Specifically, the server 100 confirms the content of the facility search request received from the target vehicle and acquires the vehicle information of the target vehicle from the blockchain ledger. Also, the server 100 acquires the current position and the current SOC of the target vehicle from the storage device 130. Further, the server 100 obtains the amount of power that can be discharged (hereinafter denoted as "ΔP" A ") for each power generation type from the power storage device (battery 11) of the target vehicle. The server 100 may obtain ΔP A for each power generation type based on the power color-coding information, the current SOC, and the lower SOC value of the target vehicle.

[0071] In the subsequent S12, the server 100 grasps the status of each vehicle other than the target vehicle (hereinafter referred to as "other vehicles") based on the vehicle ID. Specifically, the server 100 acquires the vehicle information of the other vehicles from the blockchain ledger. The server 100 acquires the current position and the current SOC of the other vehicles from the storage device 130. Also, the server 100 obtains the amount of power that can be discharged (hereinafter denoted as "ΔP" B ") for each power generation type from the power storage device (battery 11) of the other vehicles based on the power color-coding information and the current SOC of the other vehicles. Further, the server 100 confirms whether the other vehicles have performed a destination notification (S24 in FIG. 5) described later.

[0072] In the subsequent S13, the server 100 acquires information regarding each facility that requests power (i.e., each facility that transmitted the aforementioned power request) based on the facility ID. Specifically, the server 100 checks the content of the power request received from each facility and acquires the facility information of each facility that requests power from the blockchain ledger.

[0073] In the subsequent S14, the server 100 determines the incentive unit price for each facility that requests power. The server 100 determines the incentive unit price for the facility based on the incentive reference unit price (Figure 3) received from the facility.

[0074] Specifically, the server 100 predicts whether the required Wh (Figure 3) of the facility is satisfied based on the information acquired in S11 to S13. The server 100 calculates ΔP for each power generation type of each vehicle (target vehicle and other vehicles) existing around the facility (for example, within a range set based on the location of the facility). A , ΔP B (S11, S12) may be used for the above prediction. Also, the server 100 may correct ΔP B and the required Wh for each power generation type using the destination notification (S24 in Figure 5) described later. The server 100 may assume that power exchange (power supply from the vehicle to the facility) has occurred between the vehicles and facilities indicated by the destination notification. If the server 100 predicts that the required Wh of the facility will be satisfied even with the incentive reference unit price remaining as it is, the server 100 sets the incentive reference unit price as the incentive unit price for the facility as it is. If the server 100 predicts that the required Wh of the facility will not be satisfied with the incentive reference unit price remaining as it is, the server 100 performs an addition operation on the incentive reference unit price to make the incentive unit price for the facility higher than the incentive reference unit price. As described above, the incentive unit price according to the prediction result is determined for each facility.

[0075] In the subsequent S15, the server 100 determines the upper limit value of the incentive that each facility requesting power grants to one vehicle (the incentive upper limit value per vehicle). The server 100 determines the incentive upper limit value per vehicle of the facility based on the number of users of the facility (Fig. 3). Specifically, the server 100 lowers the incentive upper limit value per vehicle of the facility as the number of users of the facility decreases. In this way, the incentive upper limit value per vehicle corresponding to the number of facility users is determined for each facility. By lowering the incentive upper limit value per vehicle, the facility can pay incentives to more vehicles. And by paying a small amount of incentives to many vehicles, it becomes possible to attract many vehicles to the facility without increasing the total amount of incentives. The user of the target vehicle arriving at the facility is likely to become a facility user. Note that the incentive upper limit value per vehicle of the facility corresponds to the upper limit value of the incentive that the facility grants to the target vehicle when the target vehicle supplies the facility with the power of the requested type (the requested power). The incentive granted from the facility to the target vehicle may include coupons available at the facility.

[0076] In the subsequent S16, the server 100 performs matching between the target vehicle and the facilities. The server 100 extracts facilities belonging to the type of facility specified by the user (Fig. 3) from among the facilities participating in the platform. Hereinafter, the extracted facilities are referred to as "first candidates". Subsequently, the server 100 excludes facilities that are located at a distance of more than a predetermined distance from the current position of the target vehicle from the first candidates. Hereinafter, the facilities remaining at this stage are referred to as "second candidates". Subsequently, the server 100 excludes facilities that request power of a power generation type not stored in the power storage device (battery 11) of the target vehicle from the second candidates. Hereinafter, the facilities remaining at this stage are referred to as "third candidates". When the number of facilities included in the third candidates exceeds a predetermined number, the server 100 performs the exclusion process described below.

[0077] The server 100 calculates ΔP for each power generation type of the target vehicle ABased on (S11), the required type (S13), required Wh (S13), incentive unit price (S14), and incentive upper limit per vehicle (S15) of each facility included in the third candidate, determine the maximum incentive that can be obtained by the target vehicle for each facility included in the third candidate.

[0078] For example, the total ΔP of RE in general and individual RE (such as solar power and wind power) A For a target vehicle with a total of 5 kWh of RE (including general RE and individual RE like solar and wind), the maximum incentive that can be obtained at a facility with a required type of "RE", a required Wh of "20 kWh", an incentive unit price of "1 pt / Wh", and an incentive upper limit per vehicle of "10,000 pt" is 5,000 points. In another scenario, if the required Wh of the above facility becomes "3 kWh", the maximum incentive for the target vehicle becomes 3,000 points. Also, if the incentive upper limit per vehicle of the facility becomes "2,000 points", the maximum incentive for the target vehicle becomes 2,000 points.

[0079] The server 100 excludes the facilities included in the third candidate in ascending order of the maximum incentive for the target vehicle, and narrows down the candidates to the above-mentioned predetermined number of facilities. Hereinafter, the remaining predetermined number of facilities is referred to as the "fourth candidate".

[0080] In the subsequent S17, the server 100 determines the candidate destination of the target vehicle. When the number of facilities included in the third candidate in S16 exceeds the predetermined number, the server 100 determines the fourth candidate as the candidate destination of the target vehicle. When the number of facilities included in the third candidate in S16 does not exceed the above-mentioned predetermined number, the server 100 determines the third candidate as the candidate destination of the target vehicle. However, when the number of facilities included in the third candidate in S16 is "0", the server 100 determines the second candidate as the candidate destination of the target vehicle. Also, when the number of facilities included in the second candidate in S16 is "0", the server 100 determines the first candidate as the candidate destination of the target vehicle.

[0081] In subsequent S18, the server 100 transmits the destination candidates determined in S17 to the user terminal (mobile terminal 20) of the target vehicle. Specifically, the server 100 transmits a signal (hereinafter referred to as a "candidate notification") including the destination candidates of the target vehicle and the information of each facility included in the candidates (for example, the information displayed in S21 of FIG. 5 described later) to the user terminal of the target vehicle.

[0082] FIG. 5 is a flowchart showing an example of the process executed by the user terminal that has received the above candidate notification (notification of the destination candidates of the target vehicle). The process shown in this flowchart is executed by the user terminal (mobile terminal 20) of the target vehicle when the user terminal receives the above candidate notification.

[0083] Referring to FIG. 5, in S21, the user terminal displays the destination candidates of the target vehicle. Then, while displaying the destination candidates of the target vehicle, the user terminal accepts an input from the user of the target vehicle. In subsequent S22, the user terminal determines whether the destination has been determined by the user.

[0084] Specifically, in S21, the mobile terminal 20 displays, for example, the screen Sc3. The screen Sc3 shows, for each facility indicated by the above candidate notification as a candidate destination of the target vehicle, a classification (common to all facilities), the name of the facility, the distance between the target vehicle and the facility, the maximum incentive, the discharge amount for obtaining the maximum incentive, the SOC value of the target vehicle after discharging for obtaining the maximum incentive, the required type (RE / unspecified), the relationship between the facility and the power grid (on-grid / off-grid), and the power generation type of the power handled by the facility (RE100 / non-RE). Further, the screen Sc3 displays an operation unit M31 (for example, a checkbox) for receiving an input to select one facility from the candidate destinations, an operation unit M32 for receiving an input for determination, an operation unit M33 for receiving an input for sorting (rearranging), and an operation unit M34 for receiving an input for cancellation. When a plurality of facilities are included in the candidate destinations of the target vehicle, by displaying the operation units M31 and M32 on the screen Sc3, the mobile terminal 20 requests the user to select one facility from among the plurality of facilities.

[0085] When the operation unit M33 is operated by the user on the screen Sc4, the mobile terminal 20 displays the screen Sc4. The screen Sc4 includes operation units M41, M42,... for receiving an input of a sorting rule. When the operation unit M41 is operated by the user, the mobile terminal 20 sorts the candidate destinations (a plurality of facilities) of the target vehicle in order from the facility closest to the target vehicle and displays the sorted screen Sc3. On the other hand, when the operation unit M42 is operated by the user, the mobile terminal 20 sorts the candidate destinations (a plurality of facilities) of the target vehicle in order from the facility with the highest maximum incentive and displays the sorted screen Sc3. In this way, the user can rearrange the candidate destinations of the target vehicle displayed on the screen Sc3 according to a desired rule.

[0086] On screen Sc3, when the operation unit M32 is operated by the user while one facility (destination) is selected by the operation unit M31, it is determined as YES in S22, and the process proceeds to S23. In S23, the user terminal sets the facility (destination) selected by the user in the navigation system (HMI13) of the target vehicle. The navigation system refers to the map information and performs a route search to find the optimal route (for example, the shortest route) from the current position of the target vehicle to the destination (destination), and displays the found route on the map. Then, in S24, the user terminal transmits a signal (hereinafter referred to as "destination notification") including the identification information (facility ID) of the facility (destination of the target vehicle) selected by the user and the vehicle ID of the target vehicle to the server 100.

[0087] On the other hand, on screen Sc3, when the operation unit M34 is operated by the user, it is determined as NO in S22, and the process proceeds to S24 without performing the process of S23. In this case, in S24, instead of the above destination notification, a signal indicating that the user has not determined the destination is transmitted from the user terminal to the server 100. When the process of S24 is executed, the series of processes shown in FIG. 5 ends.

[0088] As described above, the notification method according to this embodiment includes a series of processes shown in FIG. 4. Specifically, the notification method uses first information regarding a target vehicle and second information regarding a plurality of facilities that request power to determine candidates for the destination of the target vehicle from among the plurality of facilities (S16 and S17), and includes transmitting the determined destination candidates to the user terminal of the target vehicle (S18). The first information includes power color-coding information (FIG. 1) indicating the power generation type of the power stored in the power storage device provided in the target vehicle. The second information includes the power generation type (RE / specified) of the power requested by each of the plurality of facilities. According to such a method, when a facility requests power generated by a specific method (for example, renewable energy), it becomes possible to notify the user of the target vehicle that holds the power of the facility that requests the power as a candidate for the destination of the target vehicle. In addition, by the target vehicle transporting power to the facility, it becomes possible to supply power not only to on-grid facilities but also to off-grid facilities. Further, since it is not necessary to use power grid for forwarding, the forwarding cost can be reduced.

[0089] The vehicle management system according to this embodiment includes a server 100, a vehicle 10, and a mobile terminal 20 (user terminal) (see FIG. 2). The server 100 is a computer device including a processor 110 and a storage device 130 that stores a program for causing the processor 110 to execute the above notification method. The vehicle 10 communicates with the corresponding node and updates the blockchain ledger every time external charging or external power supply is performed. That is, when the battery 11 (power storage device) of the vehicle 10 is charged, the vehicle 10 records the power generation type of the charged power. When the mobile terminal 20 receives candidates for destinations including a plurality of facilities from the server 100, the mobile terminal 20 is configured to display the candidates for the destinations (S21 in FIG. 5), request the user to select one facility from among the plurality of displayed facilities (S21 in FIG. 5), and transmit the identification information of the facility selected by the user to the server 100 (S24 in FIG. 5). According to such a vehicle management system, when the server 100 (computer device) executes the above notification method, when a facility is requesting power generated by a specific method, the user of the vehicle having that power can be notified of the facility requesting that power as a candidate for the destination of the vehicle.

[0090] Note that the display content of the screen Sc3 shown in FIG. 5 can be changed as appropriate. Some items (for example, the name of the facility) displayed on the screen Sc3 may be omitted.

[0091] In the above embodiment, nodes other than the server 100 are implemented on the cloud. However, it is not limited to this, and the form of the platform (blockchain) can be changed as appropriate. For example, all nodes of the blockchain (retail nodes, power generation nodes, vehicle nodes, facility nodes, etc.) may be realized by on-premises servers. Also, in the above embodiment, the mobile terminal 20 is adopted as the user terminal of the vehicle. However, it is not limited to this, and any terminal belonging to the user of the vehicle can be adopted as the user terminal. For example, the user terminal may be an in-vehicle terminal (for example, HMI13).

[0092] The power system may be a large-scale AC grid, a microgrid, or a DC (direct current) grid. The vehicle is not limited to a four-wheel passenger car, and may be a bus or a truck, or a three-wheel BEV. The vehicle may be equipped with a solar panel. The vehicle may be configured to be wirelessly chargeable. A vehicle that performs wireless charging may be regarded as being in a state equivalent to the aforementioned "plug-in state" when the alignment between the power transmission unit (e.g., a power transmission coil) on the power supply facility side and the power reception unit (e.g., a power reception coil) on the vehicle side is completed. The vehicle may be configured to be capable of autonomous driving or equipped with a flight function. The vehicle may be a vehicle capable of traveling without a driver (e.g., a robot taxi, an automated guided vehicle (AGV), or an agricultural machine).

[0093] The embodiments disclosed herein should be considered as illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims rather than the description of the above embodiments, and is intended to include all modifications within the meaning and scope equivalent to the claims.

Explanation of Reference Numerals

[0094] 10, 10A, 10B vehicle, 11, 11A, 11B battery, 12 inlet, 13 HMI, 14 communication device, 15 ECU, 20, 20A, 20B mobile terminal, 30, 30A, 30B, 30C facility, 100 server, 110 processor, 120 RAM, 130 storage device, 310 server, 320 EVSE, 350 power supply facility, 500 cloud.

Claims

1. A computer device determines candidates for the destination of the vehicle from among the plurality of facilities using first information regarding the vehicle and second information regarding a plurality of facilities that require power, and the computer device transmits the determined candidates for the destination to a user terminal of the vehicle, comprising: the first information includes the type of power generation of the power stored in the power storage device provided in the vehicle, the second information includes the type of power generation of the power required by each of the plurality of facilities, a notification method.

2. the first information further includes the amount of power that can be discharged from the power storage device and the position of the vehicle, the second information further includes the amount of power required by each of the plurality of facilities and the position of each of the plurality of facilities, the notification method according to claim 1.

3. determining the candidates for the destination includes: the computer device excludes facilities that are separated from the position of the vehicle by a predetermined distance or more from the candidates for the destination, the computer device excludes facilities that require power of a type of power generation not stored in the power storage device from the candidates for the destination, the notification method according to claim 1.

4. The computer device lowers the upper limit value of the incentive that the facility gives to the vehicle when the vehicle supplies the power required by the facility as the number of users of the facility that requires power is smaller, further comprising the notification method according to claim 1.

5. A vehicle management system comprising a computer device including a processor and a storage device, a vehicle, and a user terminal of the vehicle, wherein the storage device stores a program that causes the processor to determine candidates for the destination of the vehicle from among the plurality of facilities using first information regarding the vehicle and second information regarding a plurality of facilities that require power, transmit the determined candidates for the destination to the user terminal, the first information includes the type of power generation of the power stored in the power storage device provided in the vehicle, the second information includes the type of power generation of the power required by each of the plurality of facilities, the vehicle is configured to record the type of power generation of the power charged when the power storage device is charged, the user terminal displays the candidates for the destination when receiving the candidates for the destination including a plurality of facilities from the computer device, ​ requesting the user to select one facility from the plurality of facilities shown; transmitting the identification information of the facility selected by the user to the computer device; A vehicle management system configured to execute.

Images