JP7361638B2 - vehicle charging device - Google Patents

Description

The present invention relates to a vehicle charging device.

Patent Document 1 describes a charging control device for performing timer charging for charging a power storage device mounted on a vehicle using a power source external to the vehicle according to a charging plan that is set. In the charging control device, the learning device learns vehicle usage status collected for each user for each user, and the control device creates a charging plan for the vehicle used by the user corresponding to the user who uses the vehicle. The settings are made according to the learning results of the learning device.

JP2017-93088A

With the technology described in Patent Document 1, it is not possible to grasp the user's behavior from the time the vehicle is used until the next time the vehicle is used, so it may not be possible to set an appropriate charging plan according to the user's behavior. be.

The present invention has been made in consideration of the above facts, and is a vehicle charging system that can appropriately charge the batteries of shared cars used by multiple residents in accordance with the residents' actions during periods when the shared cars are not in use. The purpose is to obtain equipment.

The vehicle charging device according to the invention described in claim 1 includes a behavior detection unit that detects the behavior of a plurality of residents who each use a shared car in their respective housing units, and the usage timing and mileage of the shared car for each resident. , a usage status storage unit that stores usage status of the shared car; and at least a usage timing of the shared car based on the behavior detected by the behavior detection unit and the usage status stored in the usage status storage unit. and an estimation unit that estimates the mileage for each resident, and a charging control unit that charges the battery of the shared car by at least the mileage estimated by the estimation unit by the usage timing estimated by the estimation unit. , contains.

In the invention according to claim 1, the behavior of a plurality of residents who use shared cars in their respective housing units is detected, and based on the detected behavior and usage status of the shared car, at least the usage timing and mileage of the shared car are determined. is estimated for each resident. Then, the battery of the shared car is charged by at least the estimated travel distance of the shared car by the estimated usage timing of the shared car. Thereby, the batteries of the shared cars used by a plurality of residents can be appropriately charged according to the residents' actions during the period when the shared cars are not used.

The invention according to claim 2 is the invention according to claim 1, wherein the estimation section is an extraction section that extracts the usual behavior pattern of each resident based on the history of the behavior detected by the behavior detection section. a determination unit that determines whether the behavior detected by the behavior detection unit matches the usual behavior pattern extracted by the extraction unit; and an input requesting section that performs a process of requesting residents who are determined not to be using the shared car to input timing of use and mileage of the shared car.

In the invention as set forth in claim 2, when a shared car is suddenly used at a timing different from the usual behavior pattern, behavior that does not match the usual behavior pattern is detected as a sign of this. Residents whose behavior is determined not to match their usual behavior pattern are asked to enter the timing and mileage of their shared car use, so even if a shared car is suddenly used, It becomes possible to charge the shared car appropriately.

The present invention has the effect that the batteries of shared cars used by a plurality of residents can be appropriately charged according to the residents' actions during periods when the shared cars are not in use.

FIG. 1 is a block diagram showing a schematic configuration of a shared car management system according to an embodiment. It is a functional block diagram of a shared car management server. It is a chart showing an example of the contents of resident behavior history DB. It is a chart showing an example of the contents of a shared car usage status DB. It is a flow chart which shows an example of charge control processing. It is an image diagram showing an example of a shared car usage reservation form.

Hereinafter, an example of an embodiment of the present invention will be described in detail with reference to the drawings. The shared car management system 10 shown in FIG. , a charging device 22 , and a shared car management server 24 . The resident behavior detection sensor 14, the mobile terminal 16, the shared car usage detection sensor 20, the charging device 22, and the shared car management server 24 are connected to each other via a network 42 so as to be able to communicate with each other.

The resident behavior detection sensor 14 is composed of, for example, a camera, and is provided in each of the housing units 12 of a plurality of residents using the shared car 18, and detects the behavior of the residents in each housing unit 12. The resident behavior detection sensor 14 detects the resident's current position within the housing unit 12, the resident's behavior at the current position, the type of clothing the resident is wearing, etc., and detects the resident's behavior within the housing unit 12, such as "getting up" and "cooking." , ``meal,'' ``laundry,'' ``cleaning,'' ``dressing,'' ``bathing,'' ``sleeping,'' and so on. Note that the dwelling unit 12 provided with the resident behavior detection sensor 14 may be a detached house or an apartment complex. Further, the resident behavior detection sensor 14 may be a wearable sensor, a human sensor, etc., or may be configured to detect the resident's behavior by also detecting the use of electrical equipment such as a television or gas appliances such as a gas stove. There may be.

Each resident behavior detection sensor 14 transmits the detection result of resident behavior to the shared car management server 24 via the network 42. The shared car management server 24 stores the resident behavior detection results received from the resident behavior detection sensor 14 in a resident behavior history DB (DataBase) 36 for each resident, as shown in FIG. 3 as an example. Although FIG. 3 shows a state in which the detection results of the actions of a total of five residents, residents A to E, are stored in the resident action history DB 36, the number of residents using the shared car 18 is five. Anything other than that is fine. Furthermore, the resident behavior detection sensor 14 is an example of a behavior detection section.

The mobile terminal 16 is composed of a smartphone, a tablet terminal, or the like, and is operated by the resident when the resident owning the mobile terminal 16 makes a reservation for use of the shared car 18. Reservations for the use of the shared car 18 are managed by the shared car management server 24.

The shared car usage detection sensor 20 is installed in each shared car 18, and detects the usage status of the shared car 18 by a resident, for example, by communicating with a control device (not shown) installed in the shared car 18. Specifically, the usage status of the shared car 18 detected by the shared car usage detection sensor 20 includes the usage timing (usage date and time) of the shared car 18 for each resident using the shared car 18, usage time, actual mileage, This includes the remaining capacity of the battery installed in the shared car 18, etc. Note that, although an EV (Electric Vehicle) is suitable for the shared car 18 in this embodiment, it may also be a PHEV (Plug-in Hybrid Electric Vehicle).

Each of the shared car usage detection sensors 20 transmits the detection result of the usage status of the shared car 18 to the shared car management server 24 via the network 42 . The shared car management server 24 divides the detection results of the usage status of the shared car 18 received from the shared car usage detection sensor 20 for each shared car 18 as shown in FIG. 4, and stores them in the shared car usage status DB 38. Make me remember. Note that although FIG. 4 shows a state in which the detection results of the usage status of a total of three shared cars 18, vehicle (1) to vehicle (3), are stored in the shared car usage status DB 38, The number may be other than three.

The charging device 22 is installed in a predetermined parking lot where the shared car 18 is parked, and charges the battery of the shared car 18 parked in the predetermined parking lot according to instructions from the shared car management server 24. The charging device 22 preferably has a configuration in which, for example, a self-propelled power supply unit approaches the vehicle and charges the vehicle (for example, as disclosed in Japanese Unexamined Patent Publication No. 2011-254593), but other configurations may be used.

The shared car management server 24 includes a CPU (Central Processing Unit) 26, a memory 28 such as a ROM (Read Only Memory) and a RAM (Random Access Memory), and a memory such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). It includes a nonvolatile storage section 30 and a communication control section 32. The CPU 26, memory 28, storage section 30, and communication control section 32 are connected to each other via an internal bus 34 so as to be able to communicate with each other.

The storage unit 30 of the shared car management server 24 stores a resident behavior history DB 36, a shared car usage status DB 38, and a charging control program 40. The shared car management server 24 reads out the charging control program 40 from the storage unit 30 and expands it into the memory 28, and executes the charging control program 40 expanded into the memory 28 by the CPU 26, thereby allowing the shared car management server 24 to perform the sharing shown in FIG. It functions as a car usage estimation section 50 and a charging control section 60, and also performs charging control processing to be described later. Note that the storage unit 30 that stores the shared car usage status DB 38 is an example of a usage status storage unit.

The shared car usage estimating unit 50 estimates the shared car 18 based on the behavior of a plurality of residents in the dwelling unit 12 detected by the resident behavior detection sensor 14 and the usage status of the shared car 18 stored in the shared car usage status DB 38. Estimate the usage timing, usage time, and mileage for each resident. Note that the shared car usage estimation unit 50 is an example of an estimation unit.

The charging control unit 60 causes the charging device 22 to charge the battery of the shared car 18 by at least the mileage estimated by the shared car usage estimation unit 50 by the usage timing estimated by the shared car usage estimation unit 50.

Further, the shared car usage estimation unit 50 includes a resident behavior pattern extraction unit 52, a resident behavior determination unit 54, a shared car usage pattern extraction unit 56, and an input request unit 58.

The resident behavior pattern extraction unit 52 extracts the usual behavior pattern of each resident based on the behavior history of a plurality of residents in the dwelling unit 12 detected by the resident behavior detection sensor 14 and stored in the resident behavior history DB 36. The resident's usual behavior pattern is extracted by, for example, calculating the average value of behavior start times for each type of resident's behavior. Note that the resident behavior pattern extraction unit 52 may extract the usual behavior patterns separately for each day of the week. The resident behavior pattern extraction unit 52 is an example of an extraction unit.

The resident behavior determination unit 54 compares the behavior of the plurality of residents in the dwelling unit 12 detected by the resident behavior detection sensor 14 with the usual behavior pattern extracted by the resident behavior pattern extraction unit 52, and determines whether the resident behavior is normal. Determine whether the behavior matches the behavior pattern. For example, if the wake-up time t detected by the resident behavior detection sensor 14 for a certain resident is less than a predetermined time from the wake-up time T in the usual behavior pattern, the wake-up time t of the resident is determined to match the resident's usual behavior pattern. Further, if the time t differs from the time T by a predetermined time or more, it is determined that the time t of the resident's wake-up does not match the resident's usual behavior pattern. The resident behavior determination unit 54 is an example of a determination unit.

The shared car usage pattern extraction unit 56 extracts the usual usage pattern of the shared car 18 for each resident based on the usage history of the shared car 18 stored in the shared car usage status DB 38 for each shared car 18. do. The usage pattern of the shared car 18 extracted by the shared car usage pattern extraction unit 56 includes usage timing, usage time, and mileage of the shared car 18. Regarding the extraction of the usual usage pattern of the shared car 18, in the same way as the extraction of the resident's usual behavior pattern described above, the average value of each parameter of the usage timing, usage time, and mileage of the shared car 18 is calculated. done by doing.

The input request unit 58 provides information on the timing and duration of use of the shared car to residents whose behavior detected by the resident behavior detection sensor 14 has been determined by the resident behavior determination unit 54 to not match the usual behavior pattern. Performs processing to request input of travel distance.

Next, as an operation of this embodiment, a charging control process performed by the shared car management server 24 will be described with reference to FIG. Note that the charging control process shown in FIG. 5 is periodically executed for each resident using the shared car 18.

In step 100 of the charging control process, the shared car usage estimation unit 50 makes a reservation for the use of the shared car 18 via the mobile terminal 16 by a resident (hereinafter simply referred to as "resident") who is the subject of this charging control process. Determine whether you performed the operation yourself. To reserve the use of the shared car 18 by a resident, the resident accesses a predetermined web page for reserving the use of the shared car 18 via the mobile terminal 16, and displays the date and time of use of the shared car 18, the time of use, and the driving distance of the shared car 18 on the web page. This is done by inputting the distance (scheduled date), etc. If the resident performs an operation to reserve the use of the shared car 18, the determination in step 100 is affirmative and the process moves to step 110. In this case, the shared car use estimating unit 50 acquires the date and time of use, time of use, mileage, etc. of the shared car 18 input by the resident.

On the other hand, if the resident has not performed an operation to reserve the use of the shared car 18, the determination in step 100 is negative and the process moves to step 102. In step 102, the shared car use estimation unit 50 determines whether the resident has returned home to the dwelling unit 12 or not. If the resident is out, the determination in step 102 is negative, and the charging control process ends. Further, if the resident has returned home to the dwelling unit 12, the determination in step 102 is affirmed and the process moves to step 104.

In step 104, the resident behavior determination unit 54 of the shared car usage estimation unit 50 compares the current behavior of the resident in the dwelling unit 12 detected by the resident behavior detection sensor 14 with the resident behavior in the resident unit 12 extracted by the resident behavior pattern extraction unit 52. Compare with a person's normal behavior pattern. Then, the resident behavior determination unit 54 determines whether the resident's current behavior matches the resident's usual behavior pattern (is the resident's usual behavior) based on the result of the above verification.

If the resident's current behavior is the resident's usual behavior, the determination in step 104 is affirmative and the process moves to step 106. In step 106, the shared car usage estimation unit 50 acquires the resident's usual shared car usage pattern from the shared car usage pattern extraction unit 56. As a result, the shared car usage estimating unit 50 obtains (estimates) the usage date and time, usage time, mileage (scheduled), etc. of the shared car 18 that corresponds to the resident's usual shared car usage pattern. When the process of step 106 is completed, the process moves to step 110.

Further, if the resident's current behavior does not match the resident's usual behavior pattern, the determination in step 104 is negative and the process moves to step 108. For example, in Figure 3, Resident D wakes up and gets dressed around 5 o'clock, and this time is the same time as Resident D's usual waking up and getting dressed time (shown in parentheses in Figure 3). 8 o'clock) for a predetermined period of time or more. In such a case, it is determined that resident D's current behavior does not match the usual behavior pattern. Further, for example, in FIG. 3, resident E goes to bed around 3 o'clock, and this time differs from resident E's usual "bedtime" time by more than a predetermined amount of time. In such a case, it is determined that the resident E's current behavior does not match the usual behavior pattern.

If the resident's behavior does not match the usual behavior pattern, there is a possibility that the resident suddenly uses the shared car 18 at a timing different from the usual behavior pattern. Therefore, in step 108, the input request unit 58 sends a push notification of a shared car usage reservation form 64 as shown in FIG. 6 as an example to the mobile terminal 16 owned by the resident. The shared car usage reservation form 64 is displayed on the department. This allows the residents to confirm whether they plan to use the shared car 18 or not.

In addition, the shared car usage reservation form 64 is provided with input columns for the date and time of use of the shared car 18, the usage time, and the travel distance (scheduled). Note that each input field of the shared car usage reservation form 64 may display usage date and time, usage time, mileage (scheduled), etc. that correspond to the resident's usual shared car usage pattern. By displaying this shared car usage reservation form 64 on the display section of the mobile terminal 16, when a resident is planning to use the shared car 18 unexpectedly, the date and time of use, usage time and mileage of the shared car 18 can be displayed. etc. (modify the usage date and time, usage time, mileage, etc. according to the resident's usual shared car usage pattern). When a resident plans to suddenly use the shared car 18, the date and time of use, usage time, mileage, etc. of the shared car 18 entered (corrected) by the resident are acquired (estimated) by the shared car usage estimation unit 50. Ru.

In step 110, the charging control unit 60 acquires the usage date and time, usage time, mileage, etc. of the shared car 18 from the shared car usage estimation unit 50. Then, based on the information acquired from the shared car usage estimation unit 50, the charging control unit 60 selects a shared car 18 to be processed that matches the acquired usage schedule of the shared car 18 (a shared car 18 that can travel more than △km after ○ hours) ) is selected from a plurality of shared cars 18.

In step 112, the charging control unit 60 determines whether the shared car 18 to be processed selected in step 110 is returning to a predetermined parking lot. If the shared car 18 to be processed is leaving the garage, the determination in step 112 is negative, and step 112 is repeated until the shared car 18 to be processed selected in step 110 returns to the predetermined parking lot.

Further, if the determination in step 112 is affirmative, the process moves to step 114. In step 114, the charging control unit 60 determines whether or not it is the charging period during which the shared car 18 to be processed is to be charged. Note that the charging period for the shared car 18 is set such that charging for at least the distance traveled by the shared car 18 by the resident is completed by the date and time when the shared car 18 is used by the resident.

If the determination in step 114 is affirmative, the process moves to step 116. In step 116, the charging control unit 60 instructs the charging device 22 to charge the battery of the shared car 18 to be processed. Thereby, the charging device 22 charges the shared car 18 to be processed. After the process of step 116 is performed, the process moves to step 118. If the determination at step 114 is negative, step 116 is skipped and the process proceeds to step 118.

In step 118, the shared car usage estimation unit 50 transmits the shared car reservation completion screen to the mobile terminal 16 by push notification to notify that the reservation of the shared car 18 has been completed. 16 display section. Thereby, the resident recognizes that the reservation for the shared car 18 has been completed.

As described above, in this embodiment, the resident behavior detection sensor 14 detects the behavior of a plurality of residents who each use the shared car 18 in their respective housing units. In addition, the shared car usage status DB 38 of the storage unit 30 stores usage status of the shared car 18 including usage timing and travel distance of the shared car 18 for each resident. Further, the shared car usage estimating unit 50 calculates at least the usage timing and travel of the shared car 18 based on the behavior detected by the resident behavior detection sensor 14 and the usage status of the shared car 18 stored in the shared car usage status DB 38. Estimate the distance for each resident. Then, the charging control unit 60 charges the battery of the shared car 18 by at least the mileage estimated by the shared car usage estimation unit 50 by the usage timing estimated by the shared car usage estimation unit 50. Thereby, the batteries of the shared cars 18 used by a plurality of residents can be appropriately charged according to the residents' actions during the period when the shared cars 18 are not used.

Further, in this embodiment, the shared car use estimation section 50 includes a resident behavior pattern extraction section 52, a resident behavior determination section 54, and an input request section 58. The resident behavior pattern extraction unit 52 extracts the usual behavior pattern of each resident based on the behavior history detected by the resident behavior detection sensor 14. Furthermore, the resident behavior determination unit 54 determines whether the behavior detected by the resident behavior detection sensor 14 matches the usual behavior pattern extracted by the resident behavior pattern extraction unit 52. Then, the input requesting section 58 performs a process of requesting input of the usage timing and mileage of the shared car 18 from the resident who is determined by the resident behavior determining section 54 to not match the usual behavior pattern. This makes it possible to appropriately charge the shared car 18 even when the shared car 18 is suddenly used.

In addition, although the mode in which the shared car usage estimating unit 50 estimates (obtains) the usage time of the shared car 18 in addition to the usage timing (usage date and time) and travel distance of the shared car 18 has been described above, the present invention is not limited to this. Therefore, estimating (obtaining) the usage time of the shared car 18 may be omitted.

Further, although the above describes a mode in which the usual usage pattern of the shared car 18 is extracted and the usage timing, usage time, and mileage of the shared car 18 are obtained (estimated) from the pattern, the present invention is not limited to this. It's not something you can do. For example, when the shared car 18 was used by the resident in the past, the resident's behavior detected by the resident behavior detection sensor 14, the usage timing, usage time, and mileage of the shared car 18 (an example of a teacher signal), Generate training data that is associated with . In addition, by using the generated learning data to learn a model for outputting the usage timing, usage time, and travel distance of the shared car 18 from the resident behavior detected by the resident behavior detection sensor 14, the neural Generate trained models such as networks. Note that deep learning can be used as an example of the learning algorithm. Then, by performing signal processing in a multilayer neural network based on the resident behavior detected by the resident behavior detection sensor 14 and the generated trained model, the usage timing, usage time, and mileage of the shared car 18 can be determined. It may also be acquired (estimated).

10 Shared car management system 12 Residential unit 14 Resident behavior detection sensor 16 Mobile terminal 18 Shared car 20 Shared car usage detection sensor 22 Charging device 24 Shared car management server 38 Shared car usage status DB
50 Shared car usage estimation unit 52 Resident behavior pattern extraction unit 54 Resident behavior determination unit 56 Shared car usage pattern extraction unit 58 Input request unit 60 Charging control unit

Claims (2)

a behavior detection unit that detects the behavior of a plurality of residents who each use a shared car in their respective housing units;
a usage status storage unit that stores the usage status of the shared car, including usage timing and mileage of the shared car for each resident;
an estimation unit that estimates at least the usage timing and travel distance of the shared car for each resident based on the behavior detected by the behavior detection unit and the usage status stored in the usage status storage unit;
a charging control unit that charges the battery of the shared car by at least the mileage estimated by the estimation unit by the usage timing estimated by the estimation unit;
vehicle charging equipment including; The estimation section is
an extraction unit that extracts the usual behavior pattern of each resident based on the behavior history detected by the behavior detection unit;
a determination unit that determines whether the behavior detected by the behavior detection unit matches the usual behavior pattern extracted by the extraction unit;
an input requesting unit that performs a process of requesting input of the usage timing and mileage of the shared car from a resident who is determined by the determination unit to not match the usual behavior pattern;
The vehicle charging device according to claim 1, comprising: