JP6909942B1 - Charging time management system and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To recognize charging more correctly even when a peculiar state such as a charge recording omission occurs. A charging time management system provides an acquisition means for acquiring information related to charging of a vehicle traveling by using a rechargeable battery, information on a charging location, and information on the time when information related to charging is obtained, and charging. It is provided with a charging time specifying means for specifying the charging time of the vehicle performed at the predetermined charging place by the information related to, the information about the charging place, and the information about the time. [Selection diagram] Fig. 3

Description

The present invention relates to a charging time management system and a program for managing the charging time of a vehicle.

Patent Document 1 describes an acquisition means for acquiring information related to vehicle charging and information related to vehicle movement history from a management server that manages a vehicle traveling using a rechargeable battery, and information related to vehicle charging. And, based on the information on the movement history of the vehicle, the charging degree specifying means for specifying the charging degree of the vehicle performed at the predetermined charging place, and the charging information on the charging place based on the specified charging degree. A charge management server including an output means for outputting is described.

Japanese Unexamined Patent Publication No. 2020-135412

One of the challenges in popularizing electric vehicles (EVs) is the delay in improving the charging environment in multiple dwellings. One of the factors behind the delay in the maintenance of the charging environment is that the electricity in the parking lot of the apartment house is the electricity in the common area, and when the EV owner charges it, the charge must be borne by the person who does not own the EV. There is a lack of fairness. There is a means to install a charging device that can measure the amount of charge and the charging time, but the installation of such a charging device costs a lot of money. If it is possible to determine how much the EV has been charged without using a special charging device, it is possible to introduce relatively inexpensive charging environment equipment into the housing complex while maintaining fairness.
According to the above-mentioned Patent Document 1, it is possible to solve this problem, but it is desired to recognize the charge more correctly even when a peculiar state such as a charge recording omission occurs.

The charging time management system to which the present invention is applied is an acquisition means for acquiring information on charging a vehicle traveling by using a rechargeable battery, information on a charging location, and information on the time when the information on charging is obtained. And the charging time specifying means for specifying the charging time of the vehicle performed at the predetermined charging place based on the information related to the charging, the information about the charging place, and the information about the time, and the said vehicle. Information on the charge amount of the rechargeable battery, information on the mileage of the vehicle, and information on the current flowing through the charging circuit of the vehicle are acquired, and the acquired information on the charge amount and the information on the mileage are used. It is a charging time management system including a charging time estimating means for specifying a charging period to be charged among the periods for which information on the current is not acquired and estimating the charging time in the specified charging period .
Also, information period of non-acquisition of the current may be a period in which the information of the current does not exist in a predetermined time length.
Further, the charging time estimating means may estimate the charging time based on the charging record information which is a record of the charging performed on the vehicle.
Further, the charging record information may be a record of charging of the vehicle when the increase in the charging amount of the rechargeable battery satisfies a predetermined condition.
The acquisition means, the charge time specifying means, and the charge time estimation means are provided in a charge management server that manages charging, and the acquisition means obtains information on the current from the vehicle management server that manages the vehicle. The charging time estimation means may acquire information on the charging amount and information on the mileage from the vehicle management server by acquiring information on the charging location and the information on the time.
From another point of view, in the program to which the present invention is applied, information on the current flowing through the rechargeable battery of a vehicle traveling by using the rechargeable battery, information on the charging location, and information on the current are obtained in the computer. A function of acquiring information about time, a function of specifying the charging time of the vehicle performed at a predetermined charging place by the information of the current, the information about the charging place, and the information about the time, and a function of specifying the charging time of the vehicle. The information on the charge amount of the rechargeable battery of the vehicle and the information on the mileage of the vehicle are acquired, and the information on the current is acquired by using the acquired information on the charge amount and the information on the mileage. It is a program that realizes a function of specifying a charging period to be charged among the periods not being charged and estimating the charging time in the specified charging period .

According to the present invention, even when a peculiar state such as a charge recording omission occurs, it is possible to recognize the charge more accurately.

It is a figure which shows the whole configuration example of the EV charge management system which concerns on this embodiment. It is a figure which shows the hardware configuration example of the vehicle management server, the charge management server, and the charge management server which concerns on this embodiment. It is a figure which shows the functional structure example of the charge management server which concerns on this embodiment. It is a flowchart when the charge time specifying part which concerns on this Embodiment detects the start time of charge of a rechargeable battery. It is a chart which showed the information acquired by the charge time specifying part at the time of detecting the start of charge in a rechargeable battery. It is a flowchart when the charging time specifying part which concerns on this Embodiment detects the end of charging of a rechargeable battery. (A) to (c) are charts showing an example of information acquired when the charging time specifying unit detects the start of charging of the rechargeable battery and then detects the end of charging of the rechargeable battery. (A) to (d) are diagrams showing information about EV used by a specific place determination unit. As an example of the classification of the data interruption period, it is a figure which showed the plurality of patterns used in this classification. (A) and (b) are charts showing an example of information used when the interruption period classification unit according to the present embodiment classifies the data interruption period and the charging time estimation unit estimates the charging time. (A) to (c) are specific examples when the charging time estimation unit according to the present embodiment creates a charging record storage array.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

<Overall configuration of EV charge management system>
FIG. 1 is a diagram showing an overall configuration example of the EV charge management system 1 according to the present embodiment. The EV charge management system 1 according to the present embodiment includes a vehicle management server 100, a charge management server 200, a charge management server 300, and an EV 500 which is an electric vehicle (EV). This EV500 is a vehicle that travels using a rechargeable battery.

The vehicle management server 100 is a server device that manages a plurality of EV500s. Examples of the vehicle management server 100 include a server device managed by an automobile company that manufactures or sells the EV500. The vehicle management server 100 is used to identify information (for example, the name and address of the user) of a user who uses the EV 500 (hereinafter, referred to as a "user") and information about the vehicle of the EV 500 (for example, the EV 500). Various information such as the vehicle ID assigned to each EV500 and the model of the EV500) is managed for each EV500. Further, the vehicle management server 100 acquires the position information of the EV500, the information related to the charging of the EV500, and the like from the EV500 at all times (for example, every 5 minutes) or as needed via a network such as the Internet.

In addition, the position information of the EV500 is information indicating the position where the EV500 exists. This information is acquired and recorded by the EV 500, and the vehicle management server 100 acquires the position information according to the passage of time. As a result, the movement history of the EV500 such as the movement route is grasped.

Here, as information related to charging the EV500, for example, information on the amount of charge such as SOC (State Of Charge) in the rechargeable battery of the EV500, for example, the amount of current flowing through the charging circuit or the rechargeable battery, or for example, the voltage applied to the rechargeable battery. Also, for example, the speed and mileage of the EV500, and the like.

The charge management server 200 is a server device that grasps and manages the time when the rechargeable battery of the EV 500 is charged. The charge management server 200 can be configured by, for example, a server device of an electric power company that provides electric power to the EV 500. The charge management server 200 acquires information related to charging such as the position information of the EV500 and the current information of the EV500 from the vehicle management server 100 via a network such as the Internet. Then, the charge management server 200 specifies and estimates the charging time performed by the EV 500 at a specific charging facility based on the information acquired from the vehicle management server 100.
In the present embodiment, the EV charge management system 1 functions as an example of the charge time management system, but the charge management server 200 can function alone as an example of the charge time management system.

The charge management server 300 is a server device that manages charging charges, which charges users. The charge management server 300 can be composed of, for example, a server device of a charging equipment management company that charges the EV 500, or a server device of a condominium management association in which the charging equipment is installed. The charge management server 300 acquires information indicating the charging time performed by the EV 500 at the charging facility from the charge management server 200 via a network such as the Internet. Then, the charge management server 300 calculates the charge to be charged to the user based on the acquired information.

The EV 500 includes a rechargeable battery 501, a charging circuit 502, and an on-board unit 503. Here, the EV500 is connected to a charging facility installed in an apartment house or the like via a charging plug or the like. Then, power is supplied from the charging equipment to the rechargeable battery 501 via the charging circuit 502. The rechargeable battery 501 is charged with the electric power supplied from the charging circuit 502, and the charged electric power is supplied to various parts of the EV 500. Further, the on-board unit 503 communicates with the vehicle management server 100, and outputs, for example, the position information of the EV500 acquired by GPS (Global Positioning System) and the information related to the charging of the EV500. The on-board unit 503 is not limited to the device attached at the time of manufacturing the EV500, and may be an external device attached after the manufacture of the EV500.

Further, the position information is not limited to the configuration acquired by GPS. For example, the on-board unit 503 of the EV500 may grasp the position of the EV500 by performing wireless communication with a device in the vicinity. Further, the surroundings may be photographed by the camera provided in the EV 500, and the photographed image may be transmitted to the vehicle management server 100. Further, it is conceivable that the charging equipment transmits the information of the EV 500 to the vehicle management server 100. For example, a camera is provided in the charging equipment, the EV500 is photographed by the camera, and the captured image is transmitted to the vehicle management server 100. By the vehicle management server 100 identifying the EV500, the EV500 is located at the location of the charging equipment. It is grasped that there is.

In the present embodiment, data is collected as a data collection period, for example, when the EV500 is running and when it is being charged. Further, for example, when the EV500 is stopped in a non-charged state, data is not collected as a non-data collection period. During this data collection period, the EV500 collects and stores data such as position information and battery current every second, for example.
Further, in the present embodiment, the data collection period is defined as the period during which the EV500 is turned on and the EV500 can run, and further, when the EV500 is charged even when the power is not turned on, the data is charged. It is a data collection period. The non-data collection period is a period other than the data collection period in which the EV 500 is not turned on and is not charged.

Further, in the above-mentioned example, the information of the user is stored in the vehicle management server 100, but it may be stored in the charge management server 200. In this case, in the charge management server 200, for example, the vehicle ID and the information of the user (that is, the information of the user who uses the EV 500 to which the vehicle ID is assigned) are associated with each other. On the other hand, in the vehicle management server 100, for example, for each EV500, the vehicle ID and other information (for example, the vehicle model of the EV500, the position information of the EV500, and the information related to the charging of the EV500) are associated with each other. Therefore, when the charge management server 200 acquires the EV500 information from the vehicle management server 100, the charge management server 200 can acquire the EV500 information used by the user by designating the vehicle ID associated with the user. Is possible.
In this case, the vehicle ID and the information of the user are linked, but the information that can identify the EV500 and the information of the user may be linked, and the configuration is not limited to the use of the vehicle ID.

<Hardware configuration of charge management server>
Next, the hardware configuration of each server according to the present embodiment will be described. FIG. 2 is a diagram showing a hardware configuration example of the vehicle management server 100, the charge management server 200, and the charge management server 300 according to the present embodiment.

As shown in the figure, the vehicle management server 100, the charge management server 200, and the charge management server 300 have a CPU (Central Processing Unit) 11 that controls the entire device through execution of a program including firmware, and a BIOS (Basic Input Output System). It includes a ROM (Read Only Memory) 12 for storing programs such as firmware and firmware, and a RAM (Random Access Memory) 13 used as an execution area for the program.

Further, the charge management server 200 includes an HDD (Hard Disk Drive) 14 which is a storage area for storing various programs such as an OS (Operating System) and an application, input data for various programs, output data from various programs, and the like. Then, the program stored in the ROM 12 or the HDD 14 or the like is read into the RAM 13 and executed by the CPU 11, so that the function of the charge management server 200 is realized.
Further, the charge management server 200 includes a communication interface 15 for communicating with the outside, a display mechanism 16 including a video memory, a display, and the like, and an input device 17 such as a keyboard, a mouse, and a touch panel.

<Functional configuration of charge management server 200>
Next, with reference to FIG. 3, the functional configuration of the charge management server 200 according to the present embodiment will be described. FIG. 3 is a diagram showing a functional configuration example of the charge management server 200 according to the present embodiment.
The charge management server 200 includes a data acquisition unit 210, a suspension period specifying unit 220, a charging time specifying unit 230, a specific location determination unit 240, a suspension period classification unit 250, a charging time estimation unit 260, and an output unit 270. And have.

The data acquisition unit 210 connects to the vehicle management server 100 via various networks, and acquires information related to charging the EV 500 and information related to the charging location. When the charge management server 200 specifies and estimates the charging time, the data acquisition unit 210 collectively acquires information related to charging of the EV 500 and information related to the charging location from the vehicle management server 100. Alternatively, information on the EV 500 may be periodically acquired from the vehicle management server 100 and stored in a storage device (HDD 14 or the like) of the charge management server 200. For example, if the electricity bill is charged on a monthly basis, the period for which the bill is calculated is one month from the end of the month when the previous electricity bill was charged. .. Then, the data acquisition unit 210 acquires the EV500 information about this target period.

Here, the information related to the charging of the EV 500 acquired by the data acquisition unit 210 includes the time when the data is measured, the amount of the battery current which is the amount of the current flowing through the rechargeable battery 501, and the balance of the charge amount of the rechargeable battery 501. Examples include the amount, the position information of the EV500, the vehicle speed of the EV500, and the mileage of the EV500.
The time for measuring the data indicates, for example, the time with the first second of the target period as a reference.
The amount of battery current is a measurement of the current flowing through the EV500 rechargeable battery 501. A state in which the battery current value of the EV 500 is negative is measured as a state in which the rechargeable battery 501 is discharged, and a state in which the battery current value is positive is measured as a state in which the rechargeable battery 501 is charged.
Further, the remaining charge amount of the rechargeable battery 501 can be obtained, for example, as a percentage in which the fully charged state of the rechargeable battery 501 is 100 and the state in which the charge amount is exhausted is 0. Hereinafter, the remaining charge amount expressed as a percentage may be referred to as SOC. This SOC is an example of charge amount information. Further, as the charge amount information, the remaining charge amount of the rechargeable battery 501 can be expressed by the electric power amount (kWh). The amount of electric power (kWh) spent for charging the rechargeable battery 501 can also be used as the information on the amount of charge.

The position information is, for example, information on whether or not the EV500 is in a specific place. Here, the specific place is a place having a charging facility such as a parking lot of an apartment house, and a predetermined user charges the EV500.
Whether or not the EV500 is in a specific place is determined by acquiring the latitude and longitude of the position of the EV500 by GPS or the like and determining whether or not the latitude and longitude of the EV500 and the latitude and longitude of the specific place are within a predetermined range. ..

As another method of determining whether or not the EV500 is in a specific location, for example, when specific information is transmitted from a wireless communication device in the specific location and the receiver loaded on the EV500 receives the specific information. In addition, there is also a method of determining that the EV500 is located at this specific location. Further, an image may be acquired by a camera installed at a specific place, the EV500 may be identified from the image information, and the position of the EV500 may be grasped.

The vehicle speed is the speed at which the EV500 is moving. The mileage is the distance traveled by the EV500. The mileage does not decrease and increases when the EV500 moves even during the non-data collection period.

The interruption period specifying unit 220 determines the period during which the temporal continuity of the acquired data related to the EV 500 is interrupted as the data interruption period. In the present embodiment, as described above, there is a data collection period and a non-data collection period, and this non-data collection period in which no data is acquired is one of the data interruption periods. In addition, the failure period, which is the period during which data could not be acquired due to some failure even though it was originally the data collection period, is also determined to be the data interruption period.

The charging time specifying unit 230 specifies the charging time, which is the time charged by the EV 500. The charging time specifying unit 230 detects the start time of charging and the end time of charging, and specifies the time between the start time of charging and the end time of charging as the charging time. As will be described in detail later, for example, the charging time specifying unit 230 detects the charging start time and the charging end time using the value of the battery current of the rechargeable battery 501 of the EV 500. Then, the charging time specifying unit 230 repeats the detection of the charging start time and the detection of the charging end time, and sets the time between the charging start time and the charging end time as the charging time. Identify.

The specific location determination unit 240 determines whether or not the EV 500 is in the specific location during the charging time specified by the charging time specific unit 230. Normally, it is determined from the acquired position information whether the EV500 is in a specific place. However, when it is difficult to receive radio waves from satellites, such as when the EV500 is located in an indoor parking lot, it may not be possible to acquire position information by GPS. When this position information cannot be acquired, the specific location determination unit 240 determines whether the EV500 is parked at a predetermined specific location.
Further, when the interruption period classification unit 250, which will be described later, classifies the data interruption period, the specific location determination unit 240 determines whether or not the EV 500 is in the specific location in the data interruption period classified as the billing target.

The interruption period classification unit 250 classifies the data interruption period specified by the interruption period identification unit 220 into a period subject to billing and a period not subject to billing. This classification is performed based on, for example, the remaining amount of SOC of the EV500 and the mileage of the data before and after the data interruption period.
The data interruption period specified by the above-mentioned interruption period specifying unit 220 includes a non-data collection period in which data is not acquired and a failure period in which data cannot be acquired due to a failure. Therefore, the interruption period classification unit 250 classifies the data interruption period in which it can be determined that the battery has been charged at the specific location as the billing target period, and the data interruption period in which it cannot be determined that the battery has been charged in the specific location is the period other than the charge target period.

The charging time estimation unit 260 estimates the charging time in the data interruption period determined by the interruption period classification unit 250 to be charged. Since no data has been acquired during this data interruption period, for example, the charging time performed during the data interruption period using SOC information before and after the data interruption period, records of past charging, and the like. To estimate.
The specific location determination unit 240, the interruption period classification unit 250, and the charge time estimation unit 260 function as an example of the charge time estimation means.

The output unit 270 transmits the charging time specified by the charging time specifying unit 230 and the charging time estimated by the charging time estimating unit 260 to the charge management server 300.

Hereinafter, the processing performed by the charge management server 200 will be described.
<Charging time specific processing>
First, the process of detecting the start time of charging by the charging time specifying unit 230 will be described with reference to the flowchart of FIG.
FIG. 4 is a flowchart when the charging time specifying unit 230 according to the present embodiment detects the charging start time of the rechargeable battery 501.

The charging time specifying unit 230 acquires the value of the battery current from the information of the battery current acquired by the data acquisition unit 210 by referring to the data in chronological order (step 1001). Next, the charging time specifying unit 230 determines whether or not the value of the battery current exceeds the threshold value (step 1002). This "threshold value" is determined in order to avoid grasping the time when the battery is fully charged as the charging time. Generally, the value of the battery current decreases as the battery approaches full charge, but the charging time is not grasped when the battery is fully charged. If the threshold value of the battery current is too small, the time when the battery is fully charged is recognized as the charging time, so a value that is not too small is set as the threshold value. In the present embodiment, for example, 1A (ampere) or the like is adopted as the threshold value.

If the battery current value does not exceed the threshold in step 1002 (NO in step 1002), the process returns to step 1001 and the battery current values are referred to in chronological order from the next battery current information (step 1001). .. When it is determined in step 1002 that the value of the battery current exceeds the threshold value (YES in step 1002), the charging time specifying unit 230 sets the time at which the battery current is measured as a candidate for the start time of charging, for example. Recording is performed on the HDD 14 (see FIG. 2) (step 1003).

Next, the charging time specifying unit 230 refers to the data from the time as a candidate for the charging start time to after a predetermined time (step 1004). In this step 1004, the charging time specifying unit 230 needs to grasp whether or not a current equal to or higher than the threshold value is stably flowing through the rechargeable battery 501 after the time as a candidate for the charging start time. Therefore, the charging time specifying unit 230 refers to the data at a predetermined time from the time as a candidate for the charging start time. By referring to the data of the predetermined time, for example, it is possible to grasp the temporary battery current generated during the regenerative operation and suppress the detection of the regenerative operation as the start time of charging. .. Here, the regenerative operation is a control for generating a current in the direction of charging the rechargeable battery 501 when the EV 500 is running downhill or when the brake is applied.
For example, 60 seconds can be adopted as a predetermined time from the candidate time.

In step 1004, the charging time specifying unit 230 referring to the data up to the predetermined time is such that the number of data referred to in step 1004 is equal to or greater than the predetermined ratio to the number of data to be acquired. (Step 1005). In this step 1005, for example, when there is an acceptable data loss of about several seconds, the charging start time is detected, and when there is an unacceptable amount of data loss, the start of the charging time is not detected. .. Here, the number of data to be acquired is, for example, 60 when the EV500 acquires data at 1-second intervals and the predetermined time is 60 seconds. For example, 90% or the like can be adopted as the predetermined ratio.

If it is determined in step 1005 that the number of referenced data is not greater than or equal to a predetermined ratio of the number of data to be acquired (NO in step 1005), the process returns to step 1001 and the charging time specifying unit 230 determines the next battery current. The battery current values are referred to in chronological order from the information in (Step 1001).
When it is determined in step 1005 that the number of referenced data is equal to or greater than a predetermined ratio of the number of data to be acquired (YES in step 1005), the charging time specifying unit 230 determines the values of all the referenced battery currents. Determines whether or not exceeds the threshold (step 1006). If at least one of the referenced battery current values is equal to or less than the threshold value (NO in step 1006), the process returns to step 1001 and the battery current values are referred to in chronological order from the next battery current information.
If it is determined in step 1006 that all the referenced battery current values exceed the threshold value (YES in step 1006), the charging time specifying unit 230 stores the time stored as a candidate for the charging start time. The charging start time is stored in the HDD 14 (step 1007), and the process ends.

Further, when the charging time specifying unit 230 can use the information for determining whether or not the EV500 is moving, as a condition for detecting the start of charging, when the EV500 is moving, the charging time is charged. You can add a condition that does not detect the start. By adding such a condition, it is possible to further suppress that the charging start time is set when the battery current generated in the regenerative operation is generated. Examples of the information for determining whether or not the EV500 is moving include the vehicle speed, the mileage, and the position information of the EV500. In addition, if the vehicle speed of the EV500 is higher than 0 km / h, or if the mileage or position information of the EV500 has changed, it can be determined that the vehicle is moving.

Next, the process of detecting the charging start time will be described with reference to FIG.
FIG. 5 is a chart showing information acquired by the charging time specifying unit 230 when detecting the start of charging in the rechargeable battery 501. In FIG. 5, the value (A) of the battery current flowing through the rechargeable battery 501, the mileage (m) of the EV500, and the vehicle speed (km / h) of the EV500 for each data acquisition time (second). It is shown.

When detecting the charging start time, the charging time specifying unit 230 refers to the data in chronological order from the oldest data. In the example of FIG. 5, first, the value of the battery current when the data acquisition time is 1 second is referred to, and −5A is acquired. Since the value of the battery current does not exceed the threshold value of 1 A, the charging time specifying unit 230 refers to the next data of 2 seconds in chronological order. Since the battery current at 2 seconds does not exceed the threshold value, refer to the following data. The data reference is repeated until the battery current value exceeds the threshold value. Since the value of the battery current for 10 seconds is 6A, which exceeds the threshold value, this 10 seconds is used as a candidate for the start time of charging. Then, referring to the data from the candidate time of 10 seconds to the predetermined time of 60 seconds later, the battery current value of the data from 11 seconds to 70 seconds is 6 A, so charging is performed. Detects that the start time of is 10 seconds.

Further, in the example of FIG. 5, since there is also data on the mileage and the vehicle speed, it is possible to determine whether the change in the mileage or the vehicle speed is 0 within 60 seconds after the value of the battery current exceeds the threshold value. , A more reliable start time of charging can be determined.

Next, the process of detecting the end time of charging will be described with reference to FIG.
FIG. 6 is a flowchart when the charging time specifying unit 230 according to the present embodiment detects the charging end time.
When the charging time specifying unit 230 detects the charging start time as described above, the charging time specifying unit 230 then performs a process of detecting the charging end time.
First, the charging time specifying unit 230 acquires the value of the battery current from the information of the battery current acquired by the data acquisition unit 210 by referring to the data in chronological order (step 2001). The charging time specifying unit 230 determines whether or not the referenced data and the next data in chronological order have an interval of a predetermined time or longer (step 2002). This step prevents the period during which data is not acquired from being specified as the charging time. As the predetermined time, for example, 60 seconds or the like can be adopted.

In step 2002, if it is determined that the referenced data and the next data in chronological order have an interval of a predetermined time or longer (YES in step 2002), the data can be acquired at this interval. Since the charging time cannot be specified, the charging time specifying unit 230 stores the time of the referenced data as the charging end time in, for example, the HDD 14 (see FIG. 2) (step 2003). .. Then, the process ends.

If it is determined in step 2002 that the referenced data and the next data in chronological order do not have an interval of more than a predetermined time (NO in step 2002), the charging time specifying unit 230 determines. It is determined whether or not the value of the battery current of the referenced data is smaller than the threshold value (step 2005). As the threshold value of the battery current value, for example, 1 A (ampere) or the like can be adopted.

If it is determined in step 2005 that the value of the battery current of the referenced data is larger than the threshold value (NO in step 2005), it is assumed that charging is continuing, and the process returns to step 2001, and the charging time specifying unit 230 , Refer to the battery current values in chronological order (step 2001).
When it is determined in step 2005 that the value of the battery current of the referenced data is equal to or less than the threshold value (YES in step 2005), the charging time specifying unit 230 ends charging for the time when the battery current is measured. As a candidate for the time of, for example, it is recorded in the HDD 14 (step 2006). Next, the charging time specifying unit 230 refers to the data from the candidate time of the charging end time to after a predetermined time (step 2007). It should be noted that this predetermined time is provided to exclude a decrease in current that is not related to the end of charging, and for example, 60 seconds or the like can be adopted.

Next, the charging time specifying unit 230 determines whether or not the value of the battery current is equal to or less than the threshold value in the data of a predetermined ratio or more with respect to the number of referenced data (step 2008). The sensitivity of detection of the end of charging can be changed by this predetermined ratio. The smaller the predetermined ratio, the higher the possibility that charging is completed when the value of a part of the battery current becomes low even during charging due to improper measurement or the like. The larger the predetermined ratio, the more likely it is that charging will be completed, and the end of charging will be determined. In other words, the larger the predetermined ratio, the higher the possibility of determining that charging has not been completed even when charging has been completed. As a predetermined ratio, for example, 90% or the like can be adopted.
In step 2008, when it is determined that the value of the battery current is not equal to or less than the threshold value in the data of a predetermined ratio or more with respect to the number of referenced data (NO in step 2008), the process returns to step 2001. , The charging time specifying unit 230 refers to the value of the battery current in chronological order.
In step 2008, when it is determined that the value of the battery current is equal to or less than the threshold value in the data of a predetermined ratio or more with respect to the number of referenced data (YES in step 2008), the charging time specifying unit The 230 stores the time stored as a candidate for the charging end time in the HDD 14 as the charging end time (step 2009), and the process ends.

Next, the process of detecting the end time of charging will be described with reference to FIG. 7.
7 (a) to 7 (c) are charts showing an example of information acquired when the charging time specifying unit 230 detects the start of charging of the rechargeable battery 501 and then detects the end of charging of the rechargeable battery 501. Is. FIG. 7A is a chart on which it is assumed that the battery is fully charged and charging is completed, and FIG. 7B is a chart on which it is assumed that scheduled charging is completed and charging is completed. Further, FIG. 7 (c) is a chart on which it is assumed that charging has been completed and the battery has been charged again. In each chart, the value (A) of the battery current flowing through the rechargeable battery 501, the mileage (m) of the EV500, and the vehicle speed (km / h) of the EV500 for each data acquisition time (seconds). It is shown.

In FIG. 7A, the battery current value of the data for 903 seconds is 1 A, and then the battery current value is 1 A or less, which is the threshold value, up to the data of 963 seconds. The value of the battery current is 1A or less. In this case, the charging time specifying unit 230 detects 903 seconds as the end time of charging. In FIG. 7A, the value of the battery current is gradually decreasing. It is considered that this change in the value of the battery current represents a movement in which the battery current gradually decreases as the state of the rechargeable battery approaches full charge due to charging. It is assumed that FIG. 7A shows the value of the battery current when the battery is fully charged and charging is completed after 903 seconds.

In FIG. 7B, since the battery current value of 3A, which is larger than the threshold value of 1A, is from 100 seconds to 106 seconds, it is considered that the battery is being charged during this period. On the other hand, there is no data between 106 seconds and 900 seconds. Therefore, since there is an interval of 60 seconds or more, which is a predetermined time, from the data of 106 seconds to the data of 900 seconds, which is the next data in chronological order, the charging time specifying unit 230 sets 106 seconds. Detect as the end time of charging.
In FIG. 7B, it is assumed that the EV500 is used after charging up to the time of 106 seconds by a timer or the like.

In FIG. 7 (c), there is no data between 106 seconds and 900 seconds. Therefore, since there is an interval of 60 seconds or more, which is a predetermined time, from the data of 106 seconds to the data of 900 seconds, which is the next data in chronological order, the charging time specifying unit 230 charges 106 seconds. Detect as the end time of. In FIG. 7C, it is assumed that the EV500 is charged for 106 seconds and then charged again for 900 seconds.

<Specific location detection method>
Next, the process performed by the specific location determination unit 240 will be described.
8 (a) to 8 (d) are diagrams showing information about the EV 500 used by the specific location determination unit 240. FIG. 8A is a chart of information acquired when the specific location determination unit 240 determines that the position of the EV 500 in the charging time is a specific location when the latest data of the charging time is running. .. Further, FIG. 8B is a chart of information acquired when the specific location determination unit 240 determines that the position of the EV 500 in the charging time is a specific location when the latest data of the charging time is being charged. Is. Further, FIG. 8C is a chart of information acquired when the specific location determination unit 240 determines that the position of the EV 500 in the charging time is not a specific location when the latest data of the charging time is running. Is. Furthermore, FIG. 8D shows information acquired when the specific location determination unit 240 determines that the position of the EV 500 in the charging time is not a specific location when the latest data of the charging time is charging. It is a chart. In the charts of FIGS. 8A to 8D, the value (A) of the battery current flowing through the rechargeable battery 501, the position of the EV500, and the vehicle speed (km / km) of the EV500 for each time (second) when the data was acquired. The values of h) and the mileage (m) of the EV500 are shown. The position of the EV500 is indicated by "1" when the EV500 is in a specific location, "0" when it is not, and "-" when the location is unknown such as when GPS position information cannot be obtained. There is. In FIGS. 8A to 8D, the home indicates a specific place, and the outing indicates a place other than the specific place.

As described above, the specific location determination unit 240 determines from the position information whether or not the charging at the charging time specified by the charging time specifying unit 230 is the charging performed at the specific location. When the position information at the specified charging time cannot be acquired, for example, the specific location determination unit 240 retroactively refers to the data acquired before the charging time even if the mileage during the charging time is the same data. .. Then, if there is position information in the referenced data, the specific location determination unit 240 determines that the position is the position information of the EV 500 during the charging time.
It should be noted that the same mileage means not only when the numerical values are exactly the same, but also when the difference in mileage is within a predetermined range, it can be determined that the mileage is the same. For example, when a specific indoor location exists at a position several meters away from a position where GPS radio waves can be received, the mileage can be treated as the same even if the mileage differs by several meters.

In FIG. 8A, the value of the battery current exceeds the threshold value of 1A from the data for 10 seconds. The value of the battery current is also the threshold value in the data of 60 seconds, which is a predetermined time for grasping whether the current exceeding the threshold value is stably flowing in the rechargeable battery 501, that is, 70 seconds in FIG. 8 (a). It exceeds 1A of. Therefore, the charging time specifying unit 230 can identify the charging time during which the EV 500 is charged for a period of 10 seconds or later. At this charging time, the position information is not recorded, and the specific location determination unit 240 performs a process of determining the position of the EV 500 during this charging time.

Here, the mileage is 10000 m in the charging time after 10 seconds. Then, if there is data that is the same as this mileage and the mileage acquired before the charging time is referred to, the mileage of 3 seconds can be referred to. The position information is 1 in these 3 seconds. Therefore, the specific location determination unit 240 determines that the position information of the EV 500 during this charging time is 1. As a result, it is determined that the charging for the charging time after 10 seconds was performed at a specific place.

FIG. 8B shows that the battery current value in the period of 10 seconds to 200 seconds is 6A, which exceeds the threshold value of 1A, and the battery current value is 6A in the period of 300 seconds to 360 seconds. ing. Therefore, the charging time specifying unit 230 identifies the period from 10 seconds to 200 seconds and the period after 300 seconds as the charging time.
Since the position information is not recorded in the charging time of 10 seconds to 200 seconds, the specific location determination unit 240 retroactively refers to the same data for the mileage of 10000 m in the charging time and acquires the position information. The specific location determination unit 240 acquires the position information 1 from the data of the last 5 seconds when the mileage is 10000 m. As a result, the specific location determination unit 240 determines the position information of the charging time of 10 to 200 seconds as 1.

Next, the specific location determination unit 240 determines the position of the charging time after 300 seconds. The mileage of the charging time for the period after 300 seconds is 10000 m. The position information of the data in which the mileage is 10000 m and is acquired before the charging time in the period after 300 seconds is referred to. Since there is no data position information from 200 seconds to 10 seconds, the position information 1 is acquired in the data of 5 seconds further back. As a result, the specific location determination unit 240 determines that the position information of the charging time in the period after 300 seconds is 1.

In FIG. 8 (c), similarly to FIG. 8 (a), the charging time specifying unit 230 specifies that the period after 10 seconds is the time when the EV 500 is charged. At this charging time, the position information is not recorded, and the specific location determination unit 240 performs a process of determining the position of the EV 500 during this charging time. Unlike FIG. 8A, it is determined that the position information before 3 seconds is 0 and the position information of the EV500 in the charging time after 10 seconds is 0. As a result, it is determined that the charging for the charging time after 10 seconds was performed at a place other than the specific place.

In FIG. 8 (d), similarly to FIG. 8 (b), the charging time specifying unit 230 identifies the period of 10 seconds to 200 seconds and the period after 300 seconds as the charging time.
Since the position information is not recorded in the charging time in the period of 10 seconds to 200 seconds, the specific location determination unit 240 traces back the same data in the mileage of 10000 m in this charging time as in FIG. 8 (b). With reference, the position information 0 is acquired from the data of 5 seconds in which the mileage is 10000 m. As a result, the specific location determination unit 240 determines that the position information of the charging time of 10 to 200 seconds is 0, and determines that the charging is performed at a place other than the specific location.

Further, the specific location determination unit 240 determines the position of the charging time after 300 seconds in the same manner as in FIG. 8B. As a result, the specific location determination unit 240 determines that the position information of the charging time in the period after 300 seconds is 0, and determines that the charging is performed at a place other than the specific location.

<Classification of data interruption period>
Next, the classification of the data interruption period by the interruption period classification unit 250 will be described with reference to FIG.
FIG. 9 is a diagram showing a plurality of patterns used in this classification as an example of the classification of the data interruption period.
FIG. 9 shows four classifications of CaseA to CaseD. The data interruption period in which the SOC and the mileage do not change is defined as CaseA, and the data interruption period in which the mileage does not change and the SOC changes is defined as CaseB. Further, the data interruption period in which the mileage changes and the SOC does not change is defined as Case C, and the data interruption period in which the mileage changes and the SOC also changes is defined as Case D.
Here, the data interruption period is classified into four according to whether or not there is a change in the mileage and a change in the SOC in the data before and after the data interruption period specified by the interruption period specifying unit 220.

First, it is considered that CaseA is not charged because the EV500 has not moved because the mileage has not changed before and after the data interruption period, and the SOC has not changed. The data interruption period of CaseA is the non-data collection period. Is assumed to be. Therefore, the data interruption period for CaseA is considered normal. Further, if the data interruption period is about several seconds, it is possible that the data is missing, but if the data is lost for about several seconds, the number of acquired data is predetermined in the detection of the start of charging and the detection of the end of charging. No measures will be taken to calculate the charge for charging performed at a specific location during this data interruption period because it corresponds to the case where the ratio is higher than the above.

In Case B, since the mileage does not change before and after the data interruption period, the EV500 does not move, and it is assumed that the EV500 is charged or discharged because the SOC changes. If the SOC decreases before and after the data interruption period, it is possible that the discharge record is leaked. For example, it is possible that the air conditioner is used while the vehicle is stopped.
The SOC increases before and after the data interruption period, and if it is assumed that the charge record is leaked and the position of the EV500 during the data interruption period is known to be a specific location because the mileage does not change, the SOC increases. It is possible to charge the electricity charge for the charged charge.

In Case C, it is assumed that the EV500 is moving during the data interruption period due to the change in the mileage, and the amount of electric power used for the movement is charged during the data interruption period because the SOC does not change. In this case, since the mileage changes, the position of the EV500 during the data interruption period cannot be grasped from the information before and after the data interruption period, and it cannot be determined whether or not the EV500 was in a specific place. .. Therefore, since it is not possible to determine whether or not the charging performed during the data interruption period was performed at a specific location, the charging performed during this data interruption period is not subject to electricity charges.
Further, when the mileage changes by about several hundred meters, it is not assumed that the vehicle is being charged because the recording is not recorded for several seconds during the traveling, so no countermeasure is required.

In Case D, it is assumed that the EV500 is moving during the data interruption period due to the change in the mileage, and is discharged or charged during the data interruption period because the SOC is changed.
In this case, it is possible to calculate the amount of increase in SOC by converting, for example, the power consumption rate (electricity cost) from the records of charging and running in the past, but was charging performed at a specific location? Since it is not possible to determine whether or not, charging performed during this data interruption period will not be subject to electricity charges.

Here, the process of classifying the data interruption period specified by the interruption period specifying unit 220 by the interruption period classification unit 250 will be described with reference to FIG.
10 (a) and 10 (b) are charts showing an example of information used when the interruption period classification unit 250 classifies the data interruption period and the charging time estimation unit 260 estimates the charging time. FIG. 10A shows a case where recording omission occurs during charging, and FIG. 10B shows a case where data loss occurs during charging. Here, the SOC (%) of the rechargeable battery 501, the position of the EV500, the vehicle speed (km / h), and the mileage (m) are shown for each time (second) when the data was acquired.

In FIG. 10A, the temporal continuity between 7 seconds and 907 seconds is interrupted, and the interruption period specifying unit 220 specifies that the period between 7 seconds and 907 seconds is a data interruption period. The data before and after this data interruption period are 7 seconds of data and 907 seconds of data. The suspension period classification unit 250 refers to these two data. The interruption period classification unit 250 determines that the mileage is unchanged at 10000 m and the SOC value is changed between 69.8 and 90.5 before and after this data interruption period, and this data interruption period is set to CaseB (CaseB). (See Fig. 9). In the example of this table, the SOC increases before and after the data interruption period, and the position information is 1, so it is assumed that charging is performed at a specific location. Therefore, charging during this data interruption period is subject to management billing.

In FIG. 10B, there is a data interruption period between 3 seconds and 10 seconds, and a data interruption period between 908 seconds and 3500 seconds. There is no change in the SOC value and the mileage value in the data of 3 seconds and 10 seconds, which is the data before and after the data interruption period between 3 seconds and 10 seconds. Therefore, the suspension period classification unit 250 classifies it into CaseA (see FIG. 9). This data interruption period is assumed to be a non-data collection period.

Further, since the data interruption period between 908 seconds and 3500 seconds has a change in SOC and no change in the mileage, the interruption period classification unit 250 classifies the data into Case B (see FIG. 9). Since the SOC increases before and after the data interruption period, it is assumed that the data interruption period is data loss during charging. Here, the specific location determination unit 240 determines the position of the EV 500 during the data interruption period. The position information of the data of 3 seconds can be referred to as data that is the same as the mileage before and after the data interruption period, and the specific location determination unit 240 determines that the position of this data interruption period is 1.
Therefore, charging during this data interruption period is subject to management billing.

<Explanation of charging time estimation method>
Next, a process of estimating the charging time in the data interruption period classified into the period subject to management billing will be described.
The charging time estimation unit 260 estimates the charging time from the difference in SOC and the actual charging record of the charging performed on the EV500. The estimation of the charging time is calculated from, for example, charging in which the SOC increases by 5% or more, or charging results of charging for, for example, 1 hour or more. After the start of charging, the time for the SOC to increase by, for example, 0.1% to 0.3% is stored as a result. The actual result may be the actual result at the time of estimating the charging time (current actual result), or the past actual result at the time of data measurement may be used.

11A to 11C are diagrams showing a process in which the charging time estimation unit 260 according to the present embodiment creates a charging record storage array C. The charge record storage array C is used to estimate the time it takes to increase the SOC per unit. FIG. 11A shows the actual charging results in chronological order. FIG. 11B shows a case where there is no charging record, and FIG. 11C shows a case where there is a charging record. 11 (b) and 11 (c) show the charge record storage array C. Each element of this charge record storage array C is the time actually taken to increase the percentage of SOC per unit (eg 0.1%).

In FIG. 11 (a), the SOC of the charging start time is 70.0%, and it is shown that it took 35 seconds to increase to 70.1%. Furthermore, it has been shown that it took 54 seconds for the SOC to increase from 70.1% to 70.2%. Then, the SOC increases from 70.2% to 70.3% in 55 seconds, the SOC increases from 70.3% to 70.4% in 57 seconds, and the SOC increases from 70.4% to 70. It has been shown that it took 56 seconds to increase to 5.5%.
The number of seconds required for these 0.1% increase, specifically 54 seconds, 55 seconds, and 57 seconds, is the value of the element of the charge record storage array C.
The time required for the initial increase of 0.1%, 35 seconds, is not adopted as an element of the charge record storage array C because the second decimal place value of the SOC value is unknown.

FIG. 11B first shows a state in which there is no element in the charge record storage array C. Therefore, 54 is first acquired, then 55 is acquired, and finally 57 is acquired as an element of the charge record storage array C.

In FIG. 11C, first, there are 18 elements as the elements of the charge record storage array C, and then further elements are acquired. Here, the upper limit of the number of elements is set, and the upper limit of the number of elements is 20. Here, if the upper limit of the number of elements of the charge record storage array C is not set, it is estimated using the old record, and the estimated value is likely to be different from the current value.
In the first example, there is a charge record storage array C having 18 elements, and then 54 seconds, 55 seconds, and 57 seconds are taken in as elements from the charge record of FIG. 11 (a). First, 54 seconds are taken into the charge record storage array C as elements, and the number of elements is 19. Further, 55 seconds are taken into the charge record storage array C as elements, and the number of elements is 20. Next, 57 seconds is taken into the charge record storage array C as an element, but since there is an upper limit on the number of elements, the oldest element among the charge record storage array C elements is deleted and the element of 57 seconds is taken in. ..

Using the charge record storage array C that incorporates the elements in this way, the time required to increase the percentage per unit (for example, 0.1%) is estimated, and at that time, the center of the charge record storage array C is estimated. Use the value. This median value is the value of the element located at the center when the elements of the charge record storage array C are arranged in order by the length of time. If the number of elements is even, the median is the average of the two centrally located elements.
Using the median value of the charge record storage array C thus obtained, the charge time in the charge record omission period is estimated. The charging time estimation unit 260 estimates the charging time performed during the data interruption period by applying the estimated charging time to the amount of increase in SOC during the data interruption period.

For example, when SOC increases by 20.7% before and after the data interruption period as shown in FIG. 10A, the time required for the estimated 0.1% increase is multiplied by 207 to interrupt the data. Estimated to be the time charged during the period.

The present disclosure is not limited to the above-described embodiment, and can be implemented in various forms without departing from the gist of the present disclosure.

1 ... EV charge management system, 100 ... vehicle management server, 200 ... charge management server, 210 ... data acquisition unit, 220 ... interruption period identification unit, 230 ... charge time identification unit, 240 ... specific location determination unit, 250 ... interruption period Classification unit, 260 ... Charging time estimation unit, 300 ... Charge management server, 500 ... EV

Claims (6)

An acquisition means for acquiring information related to charging of a vehicle traveling using a rechargeable battery, information on a charging location, and information on the time when the information related to the charging was obtained.
A charging time specifying means for specifying the charging time of the vehicle performed at a predetermined charging place based on the information related to the charging, the information on the charging place, and the information on the time.
Information on the charge amount of the rechargeable battery of the vehicle, information on the mileage of the vehicle, and information on the current flowing through the charging circuit of the vehicle are acquired, and the acquired information on the charge amount and the mileage are obtained. A charging time estimation means for specifying a charging period to be charged from the period during which the current information is not acquired and estimating the charging time in the specified charging period,
Charging time management system with. The charging time management system according to claim 1 , wherein the period in which the current information is not acquired is a period in which the current information does not exist for a predetermined time length. The charging time management system according to claim 1 , wherein the charging time estimating means estimates the charging time based on charging record information which is a record of charging performed on the vehicle. The charging time management system according to claim 3 , wherein the charging record information is a record of charging of the vehicle when an increase in the charging amount of the rechargeable battery satisfies a predetermined condition. The acquisition means, the charging time specifying means, and the charging time estimating means are provided in a charge management server that manages charging.
The acquisition means acquires the current information, the charging location information, and the time information from the vehicle management server that manages the vehicle.
The charging time management system according to claim 1 , wherein the charging time estimating means acquires information on the charging amount and information on the mileage from the vehicle management server. On the computer
A function to acquire information on the current flowing through the rechargeable battery of a vehicle traveling using the rechargeable battery, information on the charging location, and information on the time when the information on the current was obtained, and
A function of specifying the charging time of the vehicle performed at a predetermined charging location based on the current information, the charging location information, and the time information.
The information on the charge amount of the rechargeable battery of the vehicle and the information on the mileage of the vehicle are acquired, and the information on the current is acquired by using the acquired information on the charge amount and the information on the mileage. A function to specify the billing period to be billed out of the non-billing period and estimate the charging time in the specified billing period,
A program that realizes.

Images