JP5718871B2 - Charging system, charging amount management device, charging method and program - Google Patents

Description

  The present invention relates to a technique for providing charging power for an electric vehicle.

  2. Description of the Related Art In recent years, electric vehicles (hereinafter referred to as EV: electric vehicle) are becoming widespread due to technological progress such as improvement of storage battery performance. However, the EV travelable distance per charge is short, which is still less than that of an engine vehicle that uses gasoline or the like as fuel. In addition, the number of EV charging stations is less than that of gas stations.

  For this reason, the driver needs to perform frequent charging in order to avoid a shortage of battery power when going out (EV can be charged even with a 100V power source in a general household). There are many drivers who always maintain 100% charge, for example, every time they go home.

  As a technology related to this, for example, Patent Document 1 discloses an information acquisition unit that acquires the current position of a vehicle and the amount of power stored in a power storage device from the plurality of vehicles, and the current position and amount of power stored in each of the plurality of vehicles. A vehicle selection unit that selects one or more vehicles capable of supplying charging power to a charging target vehicle, which is a vehicle that requires charging of the power storage device, from among a plurality of vehicles, and a vehicle selection unit, An information providing apparatus including a notification unit that notifies a selected power-supplyable vehicle is described.

JP 2012-108870 A

  However, the driver does not always go out far away by driving the EV every time. Rather, most of them go out to the neighborhood, such as shopping and pick-up to the station. In this case, the amount of charge that is really needed is often less than the driver expects. As described above, most EVs have a surplus / excess amount of electric power (referred to as surplus power) on a daily basis compared to the actual required amount.

  Further, Patent Document 1 supplies (accommodates) charging power from a power supplyable vehicle to a charging target vehicle. Thereby, the charge object vehicle can charge electric power. However, on the other hand, a car that can supply power supplies charging power to the vehicle to be charged regardless of whether the supplied power is surplus or not.

  The present invention has been proposed in view of the above-described conventional problems, and an object of the present invention is to effectively utilize surplus power of the EV.

  In order to solve the above-described problems, in the present invention, an electric vehicle including an output device that outputs vehicle state information, a charge amount management device that manages the charge amount of the electric vehicle, and a charging facility for the electric vehicle are provided. A control system for controlling the charging system, wherein the control device controls the charging facility according to inquiry means for inquiring the charge amount management device about an excess charge amount of the electric vehicle, and a response to the inquiry. Control means for supplying electric power of the surplus charge amount from the electric vehicle, the charge amount management device receiving vehicle state information of the electric vehicle, and the vehicle state received by the reception means Storage means for storing a history of the vehicle state information by accumulating information, and estimating a required amount of battery charge required by the electric vehicle based on the history When the inquiry is received, the surplus charge amount of the battery is calculated based on the current charge amount of the battery included in the vehicle state information and the required charge amount of the battery estimated by the estimation means. And an inquiry response means for responding to the control device with the surplus charge amount calculated by the calculation means in response to the inquiry.

  According to the embodiment of the present invention, it is possible to effectively use surplus power of EV.

It is a figure which shows the structural example of a system. It is a figure which shows the software structural example of a system. FIG. 2 is a diagram illustrating a hardware configuration example of a management server 100, a control device 310, and a mobile terminal 400. It is a figure which shows an example of OBD data. It is a figure which shows an example of an OBD data history. It is a sequence diagram which shows the process example (process 1) of a system. It is a figure explaining the electric power supply of the surplus charge amount in the facility. It is a sequence diagram which shows the process example (process 2) of a system. It is a figure explaining surplus charge amount calculation.

  Hereinafter, preferred embodiments of the present invention will be described.

<Configuration>
(System configuration)
FIG. 1 is a diagram illustrating a configuration example of a system according to an embodiment of the present invention. The system according to the present embodiment includes a charge amount management server 100, an EV 200, a facility 300, a portable terminal 400, and a network 500.

  The charge amount management server 100 (hereinafter simply referred to as a management server) acquires EV200 OBD (On-board diagnostics) data via the portable terminal 400 of the driver, and associates the operating status and power storage status of the driver with the individual vehicle. It is a server to manage. Thereby, the surplus electric power part (overcharge part) of EV200 can be derived | led-out, and the surplus electric power can be utilized. Specific examples of utilization will be described later, but there are utilization methods such as providing to other EVs or facilities 300, for example.

  The EV 200 is an electric car including an OBD. Here, the EV 200 according to the present embodiment is a vehicle on which at least a driving battery is mounted, and includes vehicles such as a plug-in hybrid vehicle having a driving battery and a fuel system engine.

  Moreover, OBD is an abbreviation for On-board diagnostics and refers to an on-board failure diagnosis system, which acquires OBD data from various sensors in real time and manages the state of the vehicle. For example, when a certain part is diagnosed as having a failure, the OBD notifies the driver of the failure by lighting a lamp indicating the failure on the driver's seat panel or the like, and records OBD data representing the content of the failure. The mechanic can easily identify the failure location by reading the OBD data using a dedicated device.

  As shown in the figure, the EV 200 according to the present embodiment includes an ECU 210, an OBD reader 220, and a battery 230.

  ECU 210 is an abbreviation for engine control unit, and is a control computer for electronically controlling the entire vehicle and each on-vehicle device. Moreover, ECU210 has a function as the above-mentioned vehicle-mounted type failure diagnosis apparatus, and grasps | ascertains the state of each vehicle-mounted apparatus. Specifically, as OBD data, for example, engine speed, vehicle speed, driving time, travel distance, travel history (position information), SOC (State of Charge: battery charge state), throttle opening, advance angle, intake air temperature, Various vehicle state information such as voltage, fuel consumption information, CO2 emissions, brakes, doors, lamps, gears, lights (outside lights), courtesy (inside lights), turn signals, etc. are grasped. It also has a function of performing failure diagnosis according to the vehicle state information.

  The OBD reader 220 has a function of an interface between the ECU 210 and the outside. In the present embodiment, since the ECU 210 outputs and provides OBD data to the mobile terminal 400, the OBD reader 220 has a communication function (for example, WiFi) for communicating with the mobile terminal 400. In addition to communication, it is also possible to employ a connector for connecting directly to the portable terminal 400 with a cable.

  The battery 230 is a storage battery mounted on the EV 200. The ECU 210 manages charge information including the current charge amount and the like.

  The facility 300 is a facility such as a commercial facility or a public facility. In addition, the facility 300 is installed in a parking lot or the like as an example, and is used for an EV operated by a business whose main source of profit is buying and selling power, such as a specific scale power business (PPS), for example. Equipped with charging facilities. The charging facility is a facility that receives power from the EV and supplies power to other EVs or the facility 300. Therefore, in this embodiment, for example, the EV 200 can supply surplus power to other EVs and the facility 300 during parking, and can obtain various benefits in return for providing surplus power. This point will be described later.

  The portable terminal 400 is a portable terminal that a driver has. For example, it can be realized by a smartphone, a mobile phone, a PDA, or the like. While getting on the EV 200, the driver communicates with the ECU 210 via the OBD reader 220 to acquire OBD data indicating the vehicle state of the EV 200 one by one. In addition, the acquired OBD data is transmitted to the management server 100 during or after traveling.

  The network 500 is a communication network that connects the management server 100, the facility 300, and the mobile terminal 400 to each other. For example, the network 500 includes various networks such as 3G, the Internet, and a dedicated line.

(Software configuration)
FIG. 2 is a diagram illustrating a software configuration example of a system according to an embodiment of the present invention.

  First, the management server 100 includes a communication unit 110, a storage unit 120, a required charge amount estimation unit 130, a surplus charge amount calculation unit 140, and a surplus charge amount inquiry response unit 150 as functional units.

  The communication unit 110 has a function of transmitting / receiving data to / from an external device.

  The storage unit 120 has a function of accumulating and storing EV200 OBD data (OBD data history) received from the mobile terminal 400.

  The required charge amount estimation unit 130 estimates the required charge amount of the battery 230 required by the EV 200 based on the OBD data history accumulated in the storage unit 120. The required amount of charge of the battery required by the EV means, for example, the amount of charge required when the EV is used. For example, in the case of an EV that is charged every day, the charge amount of the battery used until the next charge time is the required charge amount. Since the required charge amount varies depending on the usage form of the EV, it is estimated based on the OBD data history of the EV.

The surplus charge amount calculation unit 140 acquires the current charge amount of the battery 230 (which can be said to be the remaining charge amount) of the EV 200 and the necessary charge amount estimated by the necessary charge amount estimation unit 130, and obtains the necessary charge from the current charge amount calculated surplus charge amount was subtracted the amount of (excess power amount). The current charge amount is the remaining charge amount that the EV 200 has at the present time, and the necessary charge amount is the charge amount of the battery used until the next charge. Therefore, it can be said that the difference between the present charge amount and the required charge amount is an excessive charge amount that is not used by the EV 200.

  The surplus charge amount inquiry response unit 150 responds with the surplus charge amount calculated by the surplus charge amount calculation unit 140.

  Next, the facility 300 includes a control device 310, a charging facility 320, and a service providing server 330.

  The control device 310 has a function of controlling the charging facility 320, and specifically includes a communication unit 311, a surplus charge amount query unit 312, and a control unit 313 as functional units.

  The communication unit 311 has a function of transmitting / receiving data to / from an external device.

  The surplus charge amount inquiry unit 312 has a function of inquiring the surplus charge amount of the EV 200 with respect to the management server 100 when, for example, an operation for accepting surplus power supply is performed or when the EV 200 is connected to the charging facility 320. Have.

  The control unit 313 has a function of controlling the charging facility 320. For example, the charging facility 320 is controlled, and supply control of the surplus charge amount from the EV 200 is performed.

  The charging facility 320 is a charging facility for EV. The charging facility 320 receives power from the EV and supplies power to other EVs or the facility 300 according to the control of the control device 310.

  When the EV 200 supplies (provides) surplus power to other EVs or the facility 300, the service providing server 330 provides various benefits and services in return for surplus power supply. Examples of benefits and services include commercial facility coupons, discount services, and parking fee services.

  The service providing server 330 is not necessarily installed in the facility 300, and may be installed in the data center, for example, together with the management server 100, or may be configured and installed as the same server as the management server 100. May be.

  Next, the mobile terminal 400 includes a communication unit 410 and a vehicle state information acquisition unit 420 as functional units.

  The communication unit 410 has a function of transmitting / receiving data to / from an external device.

  The vehicle state information acquisition unit 420 has a function of acquiring OBD data indicating the vehicle state of the EV 200 one by one from the ECU 210 via the OBD reader 220 while the driver gets on the EV 200. Also, the acquired OBD data is transmitted to the management server 100 via the communication unit 410 during or after traveling.

  Note that these functional units are realized by a computer program executed on hardware resources such as a CPU (Central Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory) of a computer constituting each device. Is. However, these functional units may be read as “means”, “module”, “unit”, or “circuit”.

  Further, these functional units do not have to be arranged on a single computer, and may be distributed as necessary.

  The storage unit 120 systematically holds predetermined data on a storage medium such as an HDD (Hard Disk Drive) in a computer constituting the management server 100. Of course, it does not need to be arranged in the management server 100, and may be arranged on another apparatus.

(Hardware configuration)
FIG. 3 is a diagram illustrating a hardware configuration example of the management server 100, the control device 310, and the portable terminal 400 according to an embodiment of the present invention. Specifically, these hardware configurations are the same as those of a general personal computer or workstation. As shown in the figure, the CPU 11, the ROM 12, the RAM 13, the input device 14, the output device 15, and the like. The communication device 16 and the HDD 17 are included.

  The CPU 11 executes various programs and performs arithmetic processing. The ROM 12 stores a program necessary for startup. RAM13 memorize | stores the process in CPU11 temporarily, or memorize | stores data. The input device 14 is a keyboard or a mouse. The output device 15 is a display. The communication device 16 communicates with other devices via the network 500. The HDD 16 stores various data and programs.

(Example of OBD data)
FIG. 4 is a diagram illustrating an example of OBD data according to the present embodiment. The OBD data includes items such as “OBD data item name” and “OBD data value”.

  “OBD data item name” indicates the name of the OBD data defined by the vehicle-mounted fault diagnosis system. “OBD data value” indicates a specific data value corresponding to “OBD data item name”.

  Specifically, the OBD data includes, for example, engine speed, vehicle speed, driving time, travel distance, travel history (position information), SOC (State of Charge: battery charge state), and the like.

  These pieces of information are provided by the function of the in-vehicle failure diagnosis system of the ECU 210. In the present embodiment, the driver outputs the information to the portable terminal 400 via the OBD reader 220 as described above at regular time intervals while the driver is in the vehicle. . Also, it is transmitted from the portable terminal 400 to the management server 100.

(Example of OBD data history)
FIG. 5 is a diagram showing an example of the OBD data history according to the present embodiment. The OBD data of the in-vehicle trouble diagnosis system that the ECU 210 has is transmitted to the management server 100 via the portable terminal 400 and is stored in the storage unit 120 as an OBD data history. Therefore, the OBD data history includes items such as “OBD data value” for each “year / month / day”, “time”, and “OBD data item name” as shown in the figure. “Date” and “time” indicate the date when the OBD data is acquired in the ECU 210.

  For example, referring to the OBD data history in FIG. 5, it can be seen that OBD data is received and stored with the start time of 2012/8/6 8:00. Thereafter, for example, OBD data is received every minute, and according to this OBD data history, the vehicle state of the EV 200 can be grasped in time series.

  Note that the OBD data history in FIG. 5 is the OBD data history of the user having the mobile terminal 400 (user ID: user001). In order to manage the OBD data history of a plurality of users, the management server 100 identifies the OBD data history for each user using, for example, a user ID. In addition, the portable terminal 400 performs login or the like using the user ID when communicating with the management server 100.

<Operation>
Next, the processing operation of the system according to the present embodiment will be described. Hereinafter, description will be made by dividing into two processes (Process 1) and (Process 2).

(Process 1)
FIG. 6 is a sequence diagram illustrating a processing example (processing 1) of the system according to the present embodiment.

  First, when the user gets on the EV 200 to start driving, the user accesses the management server 100 using the portable terminal 400 and executes user login (step S100). The portable terminal 400 has a dedicated application for accessing the management server 100 in advance, and can input a user ID and execute user login through the dedicated application. Alternatively, user login may be executed through a general-purpose browser or the like.

  When receiving the user login request, the management server 100 executes a login process based on the user ID (step S101). If the user ID is registered in advance, login is permitted.

  Next, the user uses the communication function (for example, WiFi) of the portable terminal 400 to execute an OBD data acquisition start request to the ECU 210 (including the in-vehicle failure diagnosis system) via the OBD reader 220 (step S102). ). As described above, the mobile terminal 400 can execute an OBD data acquisition start request through a dedicated application or a general-purpose tool for accessing the management server 100.

  Note that the operations of step S100 and step S102 may be performed simultaneously. That is, the OBD data acquisition start request may be executed at the same time as the user login using the portable terminal 400.

  The ECU 210 transmits OBD data to the mobile terminal 400 via the OBD reader 220 (step S103). A specific example of the OBD data is shown in FIG. 4, for example.

  When receiving the OBD data, the portable terminal 400 (vehicle state information acquisition unit 420) transmits the received OBD data to the management server 100 (step S104).

  Note that when the OBD reader 220 is in an environment where the OBD reader 220 can communicate with the network 500, the ECU 210 does not relay the portable terminal 400, but directly transmits the OBD data to the management server 100 via the OBD reader 220. You may send it.

  As described above, the mobile terminal 400 according to the present embodiment can be realized by, for example, a smartphone, a mobile phone, a PDA, or the like. For this reason, when the mobile terminal 400 has a car navigation function or a GPS sensor, the mobile terminal 400 uses destination information, travel history information, position information, and the like as supplementary information that supplements the OBD data history. Is also possible. In this case, the mobile terminal 400 may transmit destination information, travel history information, position information, and the like to the management server 100 in a form that complements the transmitted OBD data.

  When receiving the OBD data, the management server 100 stores the received OBD data in the storage unit 120 in association with each user ID (step S105). A specific example of this OBD data is shown in FIG. 5, for example.

  When the management server 100 receives supplementary information such as destination information, travel history information, and position information from the portable terminal 400 as described above, the management server 100 associates the supplementary information with the received OBD data for each user ID. (Not shown).

  Thereafter, steps S103 to S105 are repeated. That is, the ECU 210 continues to transmit the OBD data during the boarding (until the OBD data acquisition end request is received). In addition, since the mobile terminal 400 also continues to transmit the received OBD data to the management server 100, the storage unit 120 of the management server 100 continues to accumulate the OBD data one by one during boarding.

  Thereafter, when the user ends the operation of the EV 200, for example, immediately before getting off, the user uses the communication function (for example, WiFi) of the portable terminal 400 to the ECU 210 (including the on-vehicle failure diagnosis system) via the OBD reader 220. Then, an OBD data acquisition end request is executed (step S106). In response, ECU 210 ends the transmission of the OBD data.

  Instead of executing the OBD data acquisition end request, for example, the engine of the EV 200 may be stopped. Thereby, the ECU 210 is also stopped.

  Further, the user accesses the management server 100 using the portable terminal 400 and executes user logoff (step S107). In response to this, the management server 100 ends the reception and storage of the OBD data.

  Note that user logoff may be omitted. For example, if the management server 100 does not receive OBD data from the portable terminal 400 of the same user for a certain period of time, the management server 100 considers that the user has been logged off.

  As described above, the user transmits OBD data to the management server 100 through the portable terminal 400 every time the EV 200 is driven. Thereby, the OBD data history concerning the EV 200 of the same user is accumulated in the management server 100.

(Process 2)
FIG. 7 is a diagram for explaining the power supply of the surplus charge amount in the facility 300. In using the system according to the present embodiment, the user first parks the EV 200 in the parking lot of the facility 300. Next, the user connects the charging line 701 of the charging facility 320 to the charging port of the EV 200 in order to supply (provide) surplus power of the EV 200. Thereafter, the panel 702 of the charging facility 320 is operated, and an operation for supplying a user ID and surplus power is performed.

  FIG. 8 is a sequence diagram showing a processing example (processing 2) of the system according to the present embodiment. Based on FIG.

  Control device 310 accepts an application for power supply from the user (step S200). Specifically, the user operates the panel 702 of the charging facility 320 to perform an operation for inputting a user ID or the like and supplying a surplus charge amount.

  Note that the user may communicate with the charging facility 320 via the portable terminal 400 in place of the panel 702 operation of the charging facility 320, and may perform an operation for inputting a user ID or the like and supplying an excess charge amount.

  The control device 310 (surplus charge amount query unit 312) inquires of the management server 100 about the surplus charge amount of the EV 200 using the input user ID (step S201).

  When the management server 100 (necessary charge amount estimation unit 130) receives the inquiry from the control device 310, the management server 100 (necessary charge amount estimation unit 130) needs the battery 230 required by the EV 200 based on the OBD data history stored in the storage unit 120 and corresponding to the user ID. The amount of charge is estimated (step S202).

  Here, the required amount of charge refers to, for example, the amount of charge required from the present time until the next charge is performed when the EV is used. For example, in the case of an EV that is charged every day, the charge amount of the battery that is scheduled to be used until the next charge is the required charge amount. The required amount of charge depends on the life cycle of the user, but is estimated based on the OBD data history.

  Specifically, for example, the tendency of the charging cycle of the user is confirmed based on the OBD data history of “date”, “time”, and “SOC”. For example, if the user tends to charge the battery of the EV 200 every night, it is estimated that the next charging will be the night of the day.

  Next, based on the OBD data history of “Date”, “Time”, “Driving time”, “Driving distance”, and “Driving history (location information)”, the user's driving degree and lifestyle trends are confirmed. From this tendency, the amount of charge used for the EV 200 to travel is estimated.

  For example, a user often drives to a predetermined place (for example, shopping) in the morning during weekdays (Monday to Friday) every week, and tends to stay in the neighborhood of his home (a tendency not to go out). Suppose there is. In this case, the charge amount actually consumed on weekdays based on the “SOC” on weekdays is also taken into account, and the charge amount that would be required on weekdays is estimated to be within 20%, for example.

  In addition, for example, it is assumed that the user hardly drives on weekdays but tends to go out all day on holidays (Saturdays, Sundays, and holidays). In this case, the charge amount actually consumed on the holiday based on the holiday “SOC” is also taken into account, and the charge amount that would be required on the holiday is estimated to be within 90%, for example.

  As described above, the management server 100 (necessary charge amount estimation unit 130) estimates the necessary charge amount of the battery 230 that the EV 200 requires at the present time based on the OBD data history of the user.

  In addition, when the management server 100 receives supplementary information such as destination information, travel history information, and position information from the mobile terminal 400 as described above, the EV 200 is necessary while using the supplementary information. The required charge amount of the battery 230 to be used may be estimated. This is because the estimation accuracy of the required charge can be expected to be improved.

Excess Then, the management server 100 (surplus charge amount calculation unit 140) which acquires the current charge amount with the battery 230 having the EV200, the estimated been required charge amount was subtracted the necessary charge amount from the current charge amount A charge amount (surplus power amount) is calculated (step S203). Note that the current charge amount of the battery 230 included in the EV 200 may be acquired from “SOC” of the latest OBD data history.

FIG. 9 is a diagram for explaining the calculation of the surplus charge amount. As shown, the management server 100 (surplus charge amount calculation unit 140), a material obtained by subtract necessary charge amount from the current charge amount is calculated as the excess charge amount. As described above, since the required charge amount is the charge amount of the battery scheduled to be used until the next charge, if the required charge amount is secured for the EV 200, the surplus charge amount of power is supplied ( Provided), there is no problem in operation. Here, it is assumed that the current charge amount is 90%, the required charge amount is 20%, and the surplus charge amount is 70%.

The management server 100 (surplus charge amount calculation section 140), upon subtract necessary charge amount from the current charge amount, further a certain pre-charging amount (e.g., 5-10%) to those subtract, excess The charge amount may be calculated. Since the required charge amount is an estimated value based on the OBD data history, an estimation error can be absorbed thereby. In addition, it is possible to prepare for sudden operation of the EV 200.

  The management server 100 (excess charge amount inquiry response unit 150) responds to the calculated control device 310 (step S204). Here, it is assumed that the surplus charge amount is returned as 70%.

  The control device 310 controls the charging facility 320 in accordance with the inquiry response from the management server 100, and performs control to supply power for the excess charge amount from the EV 200 (step S205). Here, the electric power for the surplus charge amount (70%) is supplied from the battery 230 (charge amount 90%) of the EV 200 to the charging facility 320 side.

  When receiving the supply of power for the surplus charge amount, the control device 310 notifies the surplus charge amount provided to the service providing server 330 and the user ID (step S206).

  When the surplus charge amount and the user ID are notified, the service providing server 330 provides various services to the user as a return or compensation for surplus power supply according to the surplus charge amount (step S207).

(Service provision example)
As described above, when the EV 200 supplies (provides) surplus power, the service providing server 330 provides various benefits and services as a return or compensation for the surplus power supply.

  For example, when the user supplies surplus power from his / her EV 200 in the parking lot of the facility 300, the service providing server 330 uses a ticket machine provided in the charging facility 320, for example, a coupon ticket that can be used in the commercial facility, a discount Publish services. The user can make a purchase at a commercial facility using the issued coupon or discount service.

  For example, the user can receive a predetermined point service. In this case, the service providing server 330 requests the point system (not shown) to give points, thereby giving points to the user's point account. This point can be used for shopping at the commercial facility, partner facility, or Internet site.

  For example, the user can also receive a parking fee service. In this case, when paying the parking fee, the parking fee corresponding to the service is discounted.

  It should be noted that the degree of service, such as a coupon ticket, discount service, point service, and parking fee service discount amount, may be determined according to the surplus charge amount.

(Utilization of surplus power)
On the other hand, when the surplus power is supplied from the EV 200, the charging facility 320 of the facility 300 can charge other EVs that are parked so that the power can be interchanged between users. As a result, the facility 300 can be expected to improve customer service and attract customers. The customer can receive a charging service at the parking lot free of charge or for a fee depending on the shopping amount.

  Moreover, it is not limited to power interchange within one facility 300, and power may be interchanged between a plurality of facilities via a PPS and a transmission line. For example, by introducing a surplus power auction service mechanism, the facility secures the power to be provided to users (store customers) for its own facility, and the surplus power generated at other facilities is the most You can make a successful bid for cheap electricity.

<Summary>
As described above, according to the present embodiment, it is possible to effectively utilize the surplus power of the EV.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

  For example, in the above-described embodiment, when the OBD reader 220 has a means capable of directly communicating with the management server 100, the portable terminal 400 can be omitted. This is because even in this case, the management server 100 can acquire and manage the OBD data of the EV 200.

  In the above-described embodiment, OBD data is acquired as information indicating the vehicle state of the EV 200. However, the information indicating the vehicle state may be acquired from a separate system, and is not limited to the OBD data from the in-vehicle failure diagnosis system.

11 CPU
12 ROM
13 RAM
14 Input device 15 Output device 16 Communication device 17 HDD
DESCRIPTION OF SYMBOLS 100 Management server 110 Communication part 120 Storage part 130 Required charge amount estimation part 140 Surplus charge amount calculation part 150 Surplus charge amount inquiry response part 200 EV
210 ECU
220 OBD reader 230 battery 300 facility 310 control device 311 communication unit 312 surplus charge amount query unit 313 control unit 320 charging facility 330 service providing server 400 portable terminal 410 communication unit 420 vehicle state information acquisition unit 500 network

Claims (6)

An electric vehicle including an output device that outputs vehicle state information, a charge amount management device that manages the charge amount of the electric vehicle, and a control system that controls a charging facility of the electric vehicle,
The controller is
Inquiry means for inquiring the amount of surplus charge of the electric vehicle to the charge amount management device,
According to a response to the inquiry, and control means before Symbol electric vehicle to supply the power of the surplus charge amount to said charging facility,
The charge amount management device includes:
Supplemental information including at least one of vehicle state information of the electric vehicle and destination information acquired by the mobile terminal, travel history information, and position information is received from a portable terminal of a user driving the electric vehicle. Receiving means for
The vehicle state information and the supplementary information received by the receiving means, by storing in association with an identifier of the user, storage means for storing a history of said vehicle state information,
Estimating means for estimating the required amount of charge of the battery required by the electric vehicle based on the history;
When the inquiry is received, based on the current charge amount of the battery included in the vehicle state information and the required charge amount of the battery estimated by the estimation means, the surplus of the battery of the electric vehicle operated by the user A calculation means for calculating a charge amount;
In response to the inquiry, inquiry response means for responding to the control device the surplus charge amount calculated by the calculation means;
A charging system comprising: The charging system includes a service providing device,
The service providing apparatus acquires the surplus charge amount and provides a service to the user according to the surplus charge amount;
The charging system according to claim 1 . The estimating means estimates the next charging date and time indicating the date and time when the next charging is performed based on the history, and estimates the amount of charge required between the current date and the next charging date and time. , Estimating the estimated charge amount as the required charge amount,
The charging system according to claim 1 or 2 . An electric vehicle including an output device that outputs vehicle state information, a control device that controls a charging facility of the electric vehicle, and a charge amount management device that manages the charge amount of the electric vehicle, connected via a network,
Supplemental information including at least one of vehicle state information of the electric vehicle and destination information, travel history information, and position information acquired by the mobile terminal is received from a portable terminal of a user driving the electric vehicle. Receiving means;
The vehicle state information and the supplementary information received by the receiving means, by storing in association with the identifier of the user, storage means for storing a history of said vehicle state information,
Estimating means for estimating the required amount of charge of the battery required by the electric vehicle based on the history;
When receiving the inquiry of the excess amount of charge of the electric vehicle from the control device, wherein the current amount of charge of the battery included in the vehicle status information, based on the required amount of charge estimated by the battery by the estimation means, wherein A calculation means for calculating a surplus charge amount for supplying the battery from the electric vehicle to the charging facility and calculating a surplus charge amount of the battery of the electric vehicle operated by the user ;
In response to the inquiry, inquiry response means for responding to the control device the surplus charge amount calculated by the calculation means;
A charge amount management device comprising: A charging method in a charging system, comprising: an electric vehicle including an output device that outputs vehicle state information; a charge amount management device that manages a charge amount of the electric vehicle; and a control device that controls a charging facility of the electric vehicle. ,
The control device is
Inquiring the surplus charge amount of the electric vehicle to the charge amount management device,
The charge amount management device is
Supplemental information including at least one of vehicle state information of the electric vehicle and destination information, travel history information, and position information acquired by the mobile terminal is received from a portable terminal of a user driving the electric vehicle. Process,
The vehicle state information and the supplementary information received by said step of receiving, by storing in association with the identifier of the user, a step of storing a history of said vehicle state information,
Estimating the required amount of charge of the battery required by the electric vehicle based on the history; and
When the inquiry is received, based on the current charge amount of the battery included in the vehicle state information and the required charge amount of the battery estimated by the estimating step , the battery of the electric vehicle operated by the user is determined. Calculating a surplus charge amount;
A step of responding to the excess charge amount calculated by the step according to the calculated the control device to the inquiry,
The control device is
According to a response to the inquiry, the steps of the previous SL electric vehicle to supply the power of the surplus charge amount to said charging facility,
A charging method characterized by comprising: An electric vehicle equipped with an output device that outputs vehicle state information, a control device that controls a charging facility of the electric vehicle, and a charge amount management device that manages the charge amount of the electric vehicle connected to the network via a network,
Supplemental information including at least one of vehicle state information of the electric vehicle and destination information, travel history information, and position information acquired by the mobile terminal is received from a portable terminal of a user driving the electric vehicle. Receiving means;
The vehicle state information and the supplementary information received by the receiving means, by storing in association with the identifier of the user, storage means for storing a history of said vehicle state information,
Estimating means for estimating the required amount of charge of the battery required by the electric vehicle based on the history;
When receiving the inquiry of the excess amount of charge of the electric vehicle from the control device, wherein the current amount of charge of the battery included in the vehicle status information, based on the required amount of charge estimated by the battery by the estimation means, wherein A calculation means for calculating a surplus charge amount for supplying the battery from the electric vehicle to the charging facility and calculating a surplus charge amount of the battery of the electric vehicle operated by the user ;
A program for causing the control device to function as inquiry response means for responding to the surplus charge amount calculated by the calculation means in response to the inquiry.

Images