Information processing method, program, and information processing apparatus

Abstract

To provide an information processing method and the like that allow automatic derivation of a required amount of power for a vehicle based on an electricity consumption.SOLUTION: An information processing method includes the processing of: obtaining both a travel route group from a departure place to a destination and a vehicle type; obtaining both a weather corresponding to each travel route and date information; determining an electricity consumption of each travel route based on the obtained vehicle type, the travel route, the weather, and the date information by referring to a storage unit that stores the electricity consumption in association with the vehicle type, the travel route, the weather, and the date information; and deriving a required amount of power in each travel route based on the determined electricity consumption.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an information processing method, a program, and an information processing apparatus.

Background Art

[0002] In recent years, development of technologies related to EV (Electric Vehicle) charging has been actively promoted. Patent Document 1 discloses an EV charging management method that determines whether charging is possible at the current position and current time of an automobile based on a charging schedule related to the amount of power to charge the automobile (vehicle) within the range of the amount of power that can be supplied in an area.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of Invention

Problems to be Solved by the Invention

[0004] However, the invention according to Patent Document 1 has a problem that it cannot automatically derive the required power amount for the vehicle based on power consumption efficiency.

[0005] In one aspect, an object is to provide an information processing method and the like capable of automatically deriving the required power amount for a vehicle based on power consumption efficiency.

Means for Solving the Problems

[0006] An information processing method according to one aspect relates to a route from a departure point to a destination Includes multiple routesThe system acquires a set of driving routes and vehicle types, obtains weather and date / time information corresponding to each driving route, and, by referring to a memory unit that stores the energy consumption associated with the vehicle type, driving route, weather, and date / time information, it identifies the energy consumption for each driving route based on the acquired vehicle type, driving route set, weather, and date / time information, and derives the required amount of power for each route based on the identified energy consumption. After the start of driving along the aforementioned route, the computer acquires the vehicle's location information, battery level, and driving distance corresponding to the driving route at predetermined time intervals. Based on the acquired location information, it determines whether predetermined update conditions have been met. If the predetermined update conditions are met, the computer derives the energy consumption of the driving route based on the acquired battery level and driving distance, and updates the energy consumption stored in the memory unit, which is associated with the vehicle type, driving route, weather, and date and time information, using the derived energy consumption. It is characterized by the following: [Effects of the Invention]

[0007] In one respect, it becomes possible to automatically derive the amount of electricity required by the vehicle based on its energy consumption. [Brief explanation of the drawing]

[0008] [Figure 1] This is an explanatory diagram showing an overview of the charging schedule system. [Figure 2] This is a block diagram showing an example server configuration. [Figure 3] This is an explanatory diagram showing an example of the record layout for the vehicle database and the seasonal database. [Figure 4] This is an explanatory diagram showing an example of the record layout for the weather database and power consumption database. [Figure 5] This is an explanatory diagram showing an example of the record layout for the vehicle status history database and the driving route database. [Figure 6] This is an explanatory diagram showing an example of a record layout for the fuel consumption database by driving route. [Figure 7] This is an explanatory diagram showing an example of a record layout in the operation plan database. [Figure 8] This is a block diagram showing an example configuration of an in-vehicle device and driver terminal. [Figure 9] This is an explanatory diagram illustrating the general process for creating operational plans for vehicles. [Figure 10] This is an explanatory diagram showing an example of a screen for creating a vehicle operation plan. [Figure 11] This is a flowchart showing the processing steps involved in creating a train schedule. [Figure 12]This is a flowchart showing the processing procedure of a subroutine for determining travel performance. [Figure 13] This is a flowchart showing the processing procedure of a subroutine for acquiring power consumption efficiency. [Figure 14] This is a flowchart showing the processing procedure of a subroutine for calculating the required electric energy. [Figure 15] This is a flowchart showing the processing procedure when updating the power consumption efficiency of a travel route. [Figure 16] This is a flowchart showing the processing procedure of a subroutine for processing to update power consumption efficiency. [Figure 17] This is an explanatory diagram showing an overview of a charging schedule system in Embodiment 3. [Figure 18] This is a block diagram showing a configuration example of a server in Embodiment 3. [Figure 19] This is an explanatory diagram showing an example of record layouts of the vehicle-charger correspondence DB and the charger installation location DB. [Figure 20] This is an explanatory diagram showing an example of a record layout of the charging schedule DB. [Figure 21] This is a block diagram showing a configuration example of a charger. [Figure 22] This is a flowchart showing the processing procedure when identifying a vehicle to be charged. [Figure 23] This is a flowchart showing the processing procedure when identifying a vehicle to be charged. [Figure 24] This is a flowchart showing the processing procedure of a subroutine for processing to identify a vehicle to be charged. [Figure 25] This is a flowchart showing the processing procedure when recreating a charging schedule. [Mode for Carrying Out the Invention]

[0009] Hereinafter, the present invention will be described in detail based on the drawings showing its embodiments.

[0010] (Embodiment 1) Embodiment 1 relates to a configuration for creating an operation plan for a vehicle. Figure 1 is an explanatory diagram showing an overview of the charging schedule system. The system of this embodiment includes an information processing device 1, a vehicle 2, an in-vehicle unit 3, and an information processing terminal 4. The information processing device 1 and the information processing terminal 4 transmit and receive information via a network N such as the Internet. The information processing device 1 and the in-vehicle unit 3 transmit and receive information via a network N such as the Internet, and a communication interface conforming to wireless communication standards such as 3G, 4G, 5G, or LTE (Long Term Evolution).

[0011] Information processing device 1 is an information processing device that processes, stores, and transmits various types of information. Information processing device 1 is, for example, a server device, a personal computer, etc. In this embodiment, information processing device 1 is assumed to be a server device, and for simplicity, it will be referred to as server 1 below.

[0012] Vehicle 2, also referred to as an electric vehicle (EV), includes private cars, commercial vehicles (such as light commercial vehicles, light four-wheeled commercial vehicles, or trucks), or passenger cars such as buses or taxis. Various businesses that own EVs may own multiple Vehicle 2 vehicles of the same model with the same battery characteristics. They may also own multiple Vehicle 2 vehicles of different models with different battery characteristics. Onboard unit 3 is a wireless device installed in Vehicle 2 that acquires and transmits status information of Vehicle 2. Status information will be described later.

[0013] Information processing terminal 4 is a terminal device that receives and transmits settings for each driving route included in the driving route group from the starting point to the destination. Information processing terminal 4 is an information processing device such as a smartphone, mobile phone, wearable device such as Apple Watch (registered trademark), tablet, or personal computer terminal. For simplicity, information processing terminal 4 will be read as driver terminal 4 below.

[0014] In this embodiment, Server 1 acquires a group of driving routes from the departure point to the destination and a vehicle identifier (vehicle ID). Server 1 acquires weather and date / time information corresponding to each driving route. Server 1 refers to a storage unit that stores the vehicle type and driver associated with the vehicle ID and acquires the vehicle type and driver. Server 1 refers to a storage unit that stores the power consumption associated with the vehicle type, driver, vehicle ID, driving route, weather, and date / time information and identifies the power consumption for each driving route based on the acquired vehicle type, driver, vehicle ID, driving route group, weather, and date / time information. Server 1 derives the required amount of power for each driving route based on the identified power consumption.

[0015] Figure 2 is a block diagram showing an example configuration of Server 1. Server 1 includes a control unit 11, a storage unit 12, a communication unit 13, a read unit 14, and a large-capacity storage unit 15. Each component is connected by a bus B or a LAN (Local Area Network), etc.

[0016] The control unit 11 includes an arithmetic processing unit such as a CPU (Central Processing Unit), MPU (Micro-Processing Unit), GPU (Graphics Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), or quantum processor. The control unit 11 reads and executes a control program 1P (program product) stored in the storage unit 12, thereby performing various information processing or control processing related to the server 1.

[0017] The control program 1P can be deployed on a single computer, at a single site, or distributed across multiple sites and interconnected by a communication network to run on multiple computers. While Figure 2 describes the control unit 11 as a single processor, it may also be a multi-processor system.

[0018] The storage unit 12 includes memory elements such as RAM (Random Access Memory) and ROM (Read Only Memory), and stores control programs 1P or data necessary for the control unit 11 to execute processing. The storage unit 12 also temporarily stores data necessary for the control unit 11 to execute arithmetic processing. The communication unit 13 is a communication module for performing communication-related processing, and transmits and receives information between the in-vehicle device 3 and the driver terminal 4, etc., via the network N.

[0019] The reading unit 14 reads a portable storage medium 1a, including a CD (Compact Disc)-ROM or DVD (Digital Versatile Disc)-ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 14 and store it in the large-capacity storage unit 15. Alternatively, the control unit 11 may download the control program 1P from another computer via a network N or the like and store it in the large-capacity storage unit 15. Furthermore, the control unit 11 may also read the control program 1P from the semiconductor memory 1b.

[0020] The large-capacity storage unit 15 includes a recording medium such as an HDD (Hard disk drive) or an SSD (Solid State Drive). The large-capacity storage unit 15 includes a vehicle database 151, a seasonal database 152, a weather database 153, a power consumption database 154, a vehicle status history database 155, a driving route database 156, a driving route-specific energy consumption database 157, and a driving plan database 158.

[0021] Vehicle DB151 stores information about the vehicle. Season DB152 stores information such as initial values ​​for electricity consumption according to the season. Weather DB153 stores temperature levels and precipitation levels. Power consumption DB154 stores the power consumption of each electrical device, including air conditioning, lights, or wipers, for each vehicle type.

[0022] Vehicle Status History DB155 stores vehicle status information. Driving Route DB156 stores information about the group of driving routes from the starting point to the destination, and information about each driving route included in the group. Driving Route-Specific Energy Consumption DB157 stores energy consumption for each driving route. Operation Plan DB158 stores the operation plan, including the required energy for each driving route.

[0023] In this embodiment, the storage unit 12 and the large-capacity storage unit 15 may be configured as a single storage device. Furthermore, the large-capacity storage unit 15 may be composed of multiple storage devices. Moreover, the large-capacity storage unit 15 may be an external storage device connected to the server 1.

[0024] Server 1 may perform various information processing and control processes as a single computer, or it may be performed in a distributed manner across multiple computers. Furthermore, Server 1 may be implemented using multiple virtual machines located within a single server, or it may be implemented using a cloud server.

[0025] Figure 3 is an explanatory diagram showing an example of the record layout for the vehicle database 151 and the seasonal database 152. Vehicle DB151 includes columns for Vehicle ID, Vehicle Number, Vehicle Type, Driver ID, Driver Email Address, and Update Date / Time. The Vehicle ID column stores the uniquely identified ID of each vehicle 2 to identify each vehicle 2. The Vehicle Number column stores, for example, the number written on the license plate (vehicle registration number, etc.).

[0026] The Vehicle Type column stores the vehicle type of Vehicle 2. The vehicle type includes, for example, the type of Vehicle 2 (e.g., light four-wheeled passenger car, light commercial vehicle, or light four-wheeled commercial vehicle), brand, and model number. For example, if the type, brand, and model number of Vehicle 2 are the same (i.e., the battery characteristics are the same), they may be determined to be the same vehicle type. The Driver ID column stores a uniquely identifiable driver ID to identify each driver. The Driver Email Address column stores the driver's email address. The Update Date and Time column stores the date and time information regarding the vehicle was updated.

[0027] The seasonal DB152 includes columns for season name, start date, end date, initial energy consumption, air conditioning ON, small lights, headlights, wiper ON, precipitation probability, and rear defogger ON. While Figure 3 illustrates examples of air conditioning, small lights, headlights, wipers, and rear defogger, the data is not limited to these electrical devices. All electrical devices consuming power within vehicle 2 are included.

[0028] The Season Name column stores the names of the seasons (spring, summer, autumn, and winter). The Season Name column may also store the name of the month (e.g., January), or both the season name and the month name. The Start Date column stores the start date of the season. The End Date column stores the end date of the season. The Initial Energy Consumption column stores the initial energy consumption value for the season. The Air Conditioning ON column includes the Outdoor Temperature column and the Precipitation Probability column. The Outdoor Temperature column stores the outdoor temperature when the air conditioning is operating (Air Conditioning ON). The Precipitation Probability column stores the probability of precipitation when the air conditioning is operating.

[0029] The small light column includes an ON time column and an OFF time column. The ON time column stores the time when the small lights are turned on. The OFF time column stores the time when the small lights are turned off. The headlight column also includes an ON time column and an OFF time column. The ON time column stores the time when the headlights are turned on. The OFF time column stores the time when the headlights are turned off.

[0030] The "Wiper ON Precipitation Probability" column stores the probability of precipitation when the wipers are activated. The "Rear Defogger ON" column stores the outside temperature (e.g., less than 5°C) at which the driver activates the rear defogger. Note that the outside temperature at which the air conditioning is ON, the probability of precipitation when the air conditioning is ON, the ON / OFF times for the parking lights, the ON / OFF times for the headlights, the probability of precipitation when the wipers are ON, and the outside temperature at which the rear defogger is ON are all stored for each season.

[0031] Figure 4 is an explanatory diagram showing an example of the record layout for weather DB153 and power consumption DB154. Weather DB153 stores multiple temperature levels based on reference temperature and multiple precipitation levels based on reference precipitation probability. Temperature levels indicate temperature thresholds that affect the operation of each electrical device. Precipitation levels indicate precipitation probability thresholds that affect the operation of each electrical device. For example, temperature levels include high temperature (28°C or higher), moderate temperature (10°C or higher and below 28°C), low temperature (3°C or higher and below 10°C), and very low temperature (below 3°C). Precipitation levels include heavy rain (greater than 50% and 100% or less), moderate rain (greater than 20% and 50% or less), light rain (greater than 0% and 20% or less), and sunny (0%).

[0032] Weather DB153 includes columns for type, name, minimum, and maximum. The type column stores the type of weather, including temperature and probability of precipitation. The name column stores the name of the temperature level or the name of the precipitation level. The minimum column stores the minimum value of temperature or probability of precipitation. The maximum column stores the maximum value of temperature or probability of precipitation.

[0033] The power consumption DB154 includes a vehicle type column, an electrical equipment name column, and a power consumption column. The vehicle type column stores the vehicle type of vehicle 2. The electrical equipment name column stores the names of the electrical equipment. Electrical equipment includes headlights, parking lights, air conditioning, rear defogger, or wipers, etc. The power consumption column stores the power consumption corresponding to each electrical equipment.

[0034] Figure 5 is an explanatory diagram showing an example of the record layout for the vehicle status history DB155 and the driving route DB156. The vehicle status history DB155 includes columns for vehicle ID, transmission date and time, longitude and latitude, battery level, cumulative mileage, air conditioning status, air conditioning airflow, rear defogger, wiper, small lamp, headlight, and creation date and time.

[0035] The Vehicle ID column stores the vehicle ID that identifies Vehicle 2. The Transmission Date and Time column stores the date and time when the status information of Vehicle 2 was transmitted. The Longitude and Latitude column stores the longitude and latitude that indicate the location information of Vehicle 2. The Battery Level column stores the battery level of Vehicle 2. The Cumulative Mileage column stores the cumulative mileage of Vehicle 2.

[0036] The Air Conditioning Status column stores information indicating whether the air conditioner is operating or not. For example, if the air conditioner is operating, "ON" is stored in the Air Conditioning Status column. Conversely, if the air conditioner has stopped operating, "OFF" is stored in the Air Conditioning Status column. The Air Conditioning Airflow column stores the airflow of the air conditioner.

[0037] The rear defogger column stores information indicating whether the rear defogger is operating or not. For example, if the rear defogger is operating, "ON" is stored in the rear defogger column. Conversely, if the rear defogger has stopped operating, "OFF" is stored in the rear defogger column.

[0038] The wiper row stores information indicating whether the wipers are activated or not. For example, if the wipers are activated, "ON" is stored in the wiper row. Conversely, if the wipers are not activated, "OFF" is stored in the wiper row.

[0039] The small lamp column stores information indicating whether the small lamps are turned on or off. For example, if the small lamps are turned on, "ON" is stored in the small lamp column. Conversely, if the small lamps are not turned on, "OFF" is stored in the small lamp column.

[0040] The headlight column stores information indicating whether the headlights are turned on or off. For example, if the headlights are turned on, "ON" is stored in the headlight column. Conversely, if the headlights are not turned on, "OFF" is stored in the headlight column. The creation date and time column stores information about the date and time the status history of vehicle 2 was created.

[0041] The route database DB156 includes columns for parent route ID, child route ID, departure point, and destination. The parent route ID column stores the ID of a group of routes that includes multiple routes. The child route ID column stores the ID of each route included in the group of routes. For example, route group A_B includes routes A_1 and 1_B. Route A_1 is the route from Toyosu to the Tokyo / Saitama weather zone boundary, and route 1_B is the route from the Tokyo / Saitama weather zone boundary to Hasuda. Because the usage status of electrical equipment changes as the weather conditions change at the weather zone boundary, the weather zone boundary becomes the destination or waypoint. Weather zone boundaries will be explained later.

[0042] The departure point column stores the starting point for each travel route. The destination column stores the destination or intermediate points for each travel route. Note that intermediate points, such as weather zone boundaries, may be included in the destination.

[0043] Figure 6 is an explanatory diagram showing an example of the record layout of the Route-Specific Fuel Consumption DB157. Based on the daily driving performance data of Vehicle 2, the fuel consumption calculated from the vehicle type, driver ID, driving route, weather, and date and time information can be stored (stored) in the Route-Specific Fuel Consumption DB157. The Route-Specific Fuel Consumption DB157 includes columns for child route ID, vehicle type, driver ID, vehicle ID, weather category, season name, departure date and time, temperature level, precipitation level, and fuel consumption.

[0044] The Child Route ID column stores the Child Route ID that identifies each driving route. The Vehicle Type column stores the vehicle type. The Driver ID column stores the Driver ID that identifies the driver. The Vehicle ID column stores the Vehicle ID that identifies Vehicle 2. The Weather Category column stores the name of the region (e.g., Tokyo or Osaka) established based on the weather forecast category. The weather forecast category is a subdivision unit into which each prefecture is divided, for example, by the Japan Meteorological Agency.

[0045] The Season Name column stores the season corresponding to each route. The Departure Date and Time column stores the time period of the departure date and time corresponding to each route. The time period may be determined by a predetermined time interval (for example, 30 minutes or 60 minutes). For example, if the departure date and time is 11:15, it falls within the time period from 11:00 to 11:30, and 11:00 is stored in the Departure Date and Time column. The Temperature Level column stores the temperature level corresponding to each route. The Precipitation Level column stores the precipitation level corresponding to each route. The Fuel Consumption column stores the fuel consumption for each route.

[0046] Figure 7 is an explanatory diagram showing an example of the record layout of the operation plan DB158. The operation plan DB158 includes columns for plan ID, child route ID, vehicle ID, driver ID, scheduled departure date and time, scheduled arrival date and time, distance, required energy, total required energy, weather category, temperature, probability of precipitation, headlights, small lamps, air conditioning, rear defogger, and wipers.

[0047] The Plan ID column stores the ID of the operation plan data, which is used to uniquely identify the data for each operation plan. The Child Route ID column stores the Child Route ID, which identifies each route. The Vehicle ID column stores the Vehicle ID, which identifies the vehicle. The Driver ID column stores the Driver ID, which identifies the driver. The Departure Date and Time column stores the departure date and time corresponding to each route. The Arrival Date and Time column stores the arrival date and time corresponding to each route.

[0048] The distance column stores the distance from the starting point to the destination. The energy consumption column stores the energy consumption required for each route. The total energy consumption column stores the sum of the energy consumption required for each route. The weather classification column stores the names of the regions based on weather forecast classifications. The temperature column stores the temperature corresponding to each route. The precipitation probability column stores the probability of precipitation corresponding to each route.

[0049] The headlight row stores the power consumption of the headlights. The parking lamp row stores the power consumption of the parking lamps. The air conditioning row stores the power consumption of the air conditioning. The rear defogger row stores the power consumption of the rear defogger. The wiper row stores the power consumption of the wipers. The power consumption stored in each of the headlight, parking lamp, air conditioning, rear defogger, and wiper rows is used to calculate the required power consumption in cases where there is no driving history. The calculation process for the required power consumption in cases where there is no driving history will be described later.

[0050] Note that different types of vehicle 2 may be equipped with different electrical devices (headlights, parking lights, air conditioning, rear defogger or wipers, etc.). Figure 7 illustrates an example where various types of vehicle 2 are equipped with common electrical devices, but this is not the only example. For example, if vehicle 2 is equipped with both common electrical devices and other electrical devices, the sum of the power consumption of the common electrical devices and the power consumption of the other electrical devices may be used. Note that for each type of vehicle 2, the electrical devices installed in vehicle 2 and the power consumption of each electrical device may be stored in the operation plan DB158.

[0051] The storage configurations described above for each database are merely examples; other storage configurations are also acceptable as long as the relationships between the data are maintained.

[0052] Figure 8 is a block diagram showing an example configuration of the in-vehicle unit 3 and the driver terminal 4. The in-vehicle unit 3 includes an in-vehicle control unit 31, a memory unit 32, a communication unit 33, and a clock unit 34.

[0053] The in-vehicle control unit 31 performs various information processing and control processing related to the in-vehicle device 3. The storage unit 32 includes memory elements such as RAM or ROM and stores control programs 3P or data necessary for the in-vehicle control unit 31 to execute processing. The storage unit 32 also temporarily stores data necessary for the in-vehicle control unit 31 to execute calculation processing. The communication unit 33 is a communication module for performing communication-related processing and sends and receives information with the server 1, etc.

[0054] The clock unit 34 measures the time or elapsed time, and is a circuit that provides the measurement result to the on-board control unit 31 upon request from the on-board control unit 31. The clock unit 34 also provides a timer function. The timer function notifies the on-board control unit 31 when a preset time has elapsed since the start command was given. Alternatively, the timer function responds to an inquiry from the on-board control unit 31 regarding whether or not a preset time has elapsed since the start command was given.

[0055] The driver terminal 4 includes a control unit 41, a storage unit 42, a communication unit 43, an input unit 44, and a display unit 45. Each component is connected via bus B or LAN, etc.

[0056] The control unit 41 includes a processing unit such as a CPU or MPU, and performs various information processing and control processing related to the driver terminal 4 by reading and executing the control program 4P (program product) stored in the storage unit 42. In Figure 8, the control unit 41 is described as a single processor, but it may be a multi-processor system.

[0057] The storage unit 42 includes memory elements such as RAM or ROM, and stores control programs 4P or data necessary for the control unit 41 to execute processing. The storage unit 42 also temporarily stores data necessary for the control unit 41 to execute arithmetic processing.

[0058] The communication unit 43 is a communication module for performing communication-related processing and sends and receives information with the server 1, etc., via the network N. The input unit 44 may be a keyboard, mouse, or a touch panel integrated with the display unit 45. The display unit 45 is a liquid crystal display or an organic EL (electroluminescence) display, etc., and displays various information according to the instructions of the control unit 41.

[0059] Figure 9 is an explanatory diagram illustrating the outline of the process for creating a route plan for vehicle 2. The route plan may be for a relatively near future period, such as the next day or the day after. First, we will explain the process of deriving the required amount of power for each route included in the group of routes.

[0060] Server 1 acquires a set of driving routes from the departure point to the destination. Specifically, the driver terminal 4 receives the departure date and time, departure point, and destination setting (input or selection) for each driving route included in the set of driving routes from the departure point to the destination in Vehicle 2. The driver terminal 4 sends the departure date and time, departure point, and destination for each received driving route to Server 1, associated with the vehicle ID.

[0061] Server 1 receives the vehicle ID, departure date and time, departure point, and destination for each driving route transmitted from the driver terminal 4. Based on the received departure point and destination, Server 1 calculates the travel time from the departure point to the destination for each driving route. The travel time from the departure point to the destination may be calculated, for example, through an external server where map data is stored. Based on the received departure date and time and the calculated travel time, Server 1 calculates the estimated arrival date and time at the destination.

[0062] Server 1 retrieves the driver ID and vehicle type of vehicle 2 from the vehicle database 151 based on the received vehicle ID. Server 1 also retrieves weather and date / time information corresponding to each driving route. The weather information includes temperature and probability of precipitation. The date / time information includes the season and departure date and time for each driving route.

[0063] Specifically, Server 1 acquires one of several routes. Based on the starting point of the acquired route, Server 1 acquires the temperature and probability of precipitation announced by the Japan Meteorological Agency from, for example, an external weather forecast server or site. Based on the acquired temperature, Server 1 identifies the corresponding temperature level from Weather DB 153. Based on the acquired probability of precipitation, Server 1 identifies the corresponding precipitation level from Weather DB 153.

[0064] Server 1 retrieves the season from the season DB 152 based on the departure date and time of the travel route. Server 1 retrieves the weather category (e.g., Tokyo), which is a region established based on weather forecast categories, from an external weather forecast server or site based on the longitude and latitude of the departure point of the travel route. The weather category may be stored in advance in the storage unit 12 or the large-capacity storage unit 15 of Server 1.

[0065] Server 1 determines whether or not there is a record of driving on the given route. Specifically, Server 1 determines whether or not the route data corresponding to the acquired child route ID, vehicle type, driver ID, vehicle ID, weather category, weather conditions (temperature level and precipitation level), and date and time information (season and departure date and time) has been stored in the route-specific fuel consumption DB157.

[0066] For example, Server 1 determines whether the acquired child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date / time information matches the child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date / time information stored in the Route-Specific Fuel Consumption DB 157. The process for determining the consistency of the departure date and time included in the date / time information may use the time period (e.g., 11:00 to 11:30) corresponding to the departure date and time (e.g., 11:00). For example, if the departure date and time stored in the Route-Specific Fuel Consumption DB 157 is 11:00, then the acquired departure date and time (e.g., 11:15) falls within the time period from 11:00 to 11:30, and the departure date and time are determined to match.

[0067] Server 1 determines that there is a record of travel on a given route if the travel route data is stored in the travel route-specific energy consumption DB157. Server 1 determines that there is no record of travel on a given route if the travel route data is not stored in the travel route-specific energy consumption DB157.

[0068] If Server 1 determines that there is a record of driving on the relevant route, it identifies (obtains) the electricity consumption of the driving route corresponding to the acquired child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date and time information from the Driving Route Electricity Consumption DB157.

[0069] Server 1 derives the required power consumption for the driving route based on the identified power consumption. The required power consumption is expressed by the following equation (1). Required electricity amount (kWh) = distance (km) / electricity cost (km / kWh) …(1) Server 1 calculates the distance from the starting point to the destination along the specified driving route. The distance from the starting point to the destination may be calculated, for example, through an external server where map data is stored. Based on the calculated distance and the energy consumption of the specified driving route, Server 1 uses the above-described formula (1) to derive (calculate) the amount of electricity required for the driving route, taking into account the driver's driving habits, season, weather, time of day, and the influence of terrain on energy consumption.

[0070] If Server 1 determines that there is no record of driving on the given route, it derives (calculates) the amount of power required for that route based on the standard energy consumption and the power consumption of each electrical device.

[0071] First, Server 1 derives the base energy consumption. Specifically, Server 1 identifies the season from Season DB 152 based on the departure date and time included in the date and time information corresponding to the travel route. Server 1 obtains the initial energy consumption value corresponding to the identified season from Season DB 152 as the base energy consumption. Server 1 calculates the distance from the departure point to the destination on the travel route. Based on the obtained base energy consumption and the calculated distance, Server 1 derives (calculates) the base energy consumption using the above-mentioned formula (1).

[0072] Next, Server 1 derives the power consumption of each electrical device based on the weather and date / time information corresponding to the driving route. Electrical devices include air conditioning, lights (small lights and headlights), and wipers, etc. Specifically, Server 1 identifies the electrical devices whose power consumption should be added from Season DB152 based on the temperature and probability of precipitation corresponding to the driving route, as well as the season and departure date / time.

[0073] For example, if the outside temperature is 30°C when the air conditioning is operating (air conditioning ON), or if the probability of precipitation is 75% when the air conditioning is operating, Server 1 identifies the electrical equipment that is "air conditioning" from the power consumption DB154. Alternatively, if the departure date and time fall within the time period when the small lights are on, Server 1 identifies the electrical equipment that is "small lamps" from the power consumption DB154. Based on the vehicle type, Server 1 retrieves the power consumption of each identified electrical equipment from the power consumption DB154.

[0074] Server 1 calculates a value by multiplying the power consumption (kW) of each identified electrical device by the time (h) required for the driving route. Server 1 then calculates the total value for all electrical devices from the calculated values ​​for each device. The total value for all electrical devices represents the total amount of power required for all electrical devices on the driving route.

[0075] Server 1 then uses equation (2), described later, to calculate the total power consumption of the calculated standard power consumption and the acquired power consumption of all electrical equipment as the required power consumption in the case of no driving history. The required power consumption in the case of no driving history is expressed by the following equation (2). Required power consumption (kWh) when there is no driving history = Standard power consumption (kWh) + Total power consumption of each electrical device (kWh) ... (2)

[0076] Server 1 obtains the weather category, season name, temperature level, and precipitation level. The process for obtaining the weather category, season name, temperature level, and precipitation level is the same as the process described above, so the explanation is omitted. Server 1 assigns a child route ID to the relevant route. Server 1 temporarily stores the weather category, season name, departure date and time, temperature level, precipitation level, and calculated required power amount in the storage unit 12, associating them with the assigned child route ID, so that they can be stored as a single record in the operation plan DB 158 described later.

[0077] This allows for the appropriate determination of the required power consumption based on date and time information, driving route, driving time, and the power consumption of electrical equipment (air conditioning, lights, or wipers, etc.), even in cases where there is no past driving record, such as a new driving route.

[0078] In this way, Server 1 can derive the amount of power required for each route by performing the power derivation process described above for each route included in the route group.

[0079] Next, we will explain the process of creating a travel plan based on the required power consumption for each derived travel route. If there is travel history, Server 1 retrieves the vehicle ID and driver ID, the temperature and probability of precipitation corresponding to each travel route, the season and departure date and time, arrival date and time, distance, and required power consumption (actual power consumption × distance) from the storage unit 12. Alternatively, if there is no travel history, Server 1 retrieves the vehicle ID and driver ID, the temperature and probability of precipitation corresponding to each travel route, the season and departure date and time, arrival date and time, distance, required power consumption (reference power consumption), and the power consumption of each electrical device from the storage unit 12.

[0080] Server 1 calculates the total power consumption required for each route as the total power consumption required for the route group. Server 1 assigns a plan ID to each route group to identify the operation plan. Server 1 stores the operation plan in the operation plan DB 158, associating it with the assigned plan ID.

[0081] Specifically, if there is a record of travel, Server 1 stores in the Operation Plan DB158 the following information to identify each travel route: child route ID, vehicle ID, driver ID, scheduled departure date and time, scheduled arrival date and time, distance, required power for each travel route, required power for the group of travel routes (sum of required power for each travel route), weather category, temperature, and probability of precipitation.

[0082] Alternatively, if there is no record of driving, Server 1 stores in the operation plan DB158 the following information to identify each driving route: child route ID, vehicle ID, driver ID, scheduled departure date and time, scheduled arrival date and time, distance, required power consumption for each driving route, required power consumption corresponding to the group of driving routes, weather category, temperature, probability of precipitation, power consumption of headlights, power consumption of small lamps, power consumption of air conditioner, power consumption of rear defogger, and power consumption of wipers.

[0083] The process for updating the electricity consumption of the driving route shown in Figure 9 will be explained in Embodiment 2.

[0084] Figure 10 is an explanatory diagram showing an example of the operation plan creation screen for vehicle 2. The creation screen includes a route setting field 11a and a map display field 11b. The route setting field 11a is a field for accepting settings for each route included in the route group. The map display field 11b is a display field for displaying map data corresponding to the route group.

[0085] When the driver terminal 4 receives a setting operation in the route setting field 11a, it accepts the settings for each route included in the route group from the departure point to the destination in the vehicle 2. As shown in the figure, the driver terminal 4 accepts the departure date and time, departure point, and destination for each route.

[0086] The driver terminal 4 transmits the departure date and time, departure point, and destination for each accepted driving route to the server 1, associated with the vehicle ID. The server 1 receives the vehicle ID, departure date and time, departure point, and destination for each driving route transmitted from the driver terminal 4. Based on the received departure point and destination, the server 1 calculates the estimated time required from the departure point to the destination for each driving route. Based on the received departure date and time and the calculated time required, the server 1 calculates the estimated arrival date and time at the destination.

[0087] Server 1 acquires map data corresponding to a group of driving routes, including each individual driving route, from an external server where map data is stored, for example. Server 1 transmits the calculated estimated arrival date and time for each driving route, along with the acquired map data, to the driver terminal 4. The driver terminal 4 receives the estimated arrival date and time and map data for each driving route transmitted from Server 1. The driver terminal 4 displays the received estimated arrival date and time for each driving route in the driving route setting field 11a, and displays the received map data in the map display field 11b.

[0088] In Figure 10, the estimated arrival time for each route is calculated on the server 1 side, but this is not the only way. For example, the driver terminal 4 may accept input of the estimated arrival time for each route from the driver. Alternatively, the driver terminal 4 may calculate the estimated arrival time for each route through an external server where map data is stored.

[0089] Figure 11 is a flowchart showing the processing procedure when creating a route plan. The control unit 41 of the driver terminal 4 receives the departure date and time, departure point, and destination setting for each route included in the route group via the input unit 44 (step S401). The control unit 41 transmits the departure date and time, departure point, and destination for each received route to the server 1 via the communication unit 43, associating them with the vehicle ID (step S402).

[0090] The control unit 11 of server 1 receives the vehicle ID, departure date and time, departure point and destination for each driving route transmitted from the driver terminal 4 via the communication unit 13 (step S101). The control unit 11 acquires one driving route from among multiple driving routes (step S102). The control unit 11 executes a subroutine to determine whether or not the acquired driving route has been driven before (step S103). The subroutine for determining whether or not the driving record exists will be described later.

[0091] The control unit 11 determines whether or not there is a record of travel on the said travel route based on the determination result obtained by the travel record determination subroutine (step S104). If the control unit 11 determines that there is no record of travel on the said travel route (NO in step S104), it executes a subroutine for calculating the required amount of power (step S110). The subroutine for calculating the required amount of power will be described later.

[0092] The control unit 11 temporarily stores the calculated required power amount in the storage unit 12 (step S111). The control unit 11 then proceeds to the process in step S107, which will be described later. Specifically, the control unit 11 assigns a child route ID to the driving route. The control unit 11 then temporarily stores the vehicle type, driver ID, vehicle ID, weather category, season name, departure date and time, temperature level, precipitation level, standard power consumption, and power consumption of each electrical device as a single record in the storage unit 12, in association with the assigned child route ID, so that it can be stored in the operation plan DB 158.

[0093] Regarding departure dates and times, the time indicating the time period to which the departure date and time belongs is stored in the route-specific fuel consumption DB157. For example, if the departure date and time is 2023 / 1 / 20 11:15, the time period to which the departure date and time belongs is 11:00 to 11:30. The control unit 11 stores the time (11:00) indicating this time period in the departure date and time column.

[0094] If the control unit 11 determines that there is a record of driving on the said driving route (YES in step S104), it executes a subroutine for acquiring the energy consumption (step S105). The subroutine for acquiring the energy consumption will be described later.

[0095] The control unit 11 derives the amount of power required for the driving route (step S106). Specifically, the control unit 11 obtains the child route ID of the driving route from the driving route DB 156 of the large capacity storage unit 15 based on the starting point and destination of the driving route, or the weather category boundary. The control unit 11 calculates the distance from the starting point to the destination of the driving route. Based on the power consumption of the driving route and the calculated distance of the driving route, the control unit 11 derives the amount of power required for the driving route (power consumption × distance) using the above-described formula (1).

[0096] The control unit 11 determines whether the route is the last route (step S107). If the control unit 11 determines that the route is not the last route (NO in step S107), it returns to the process in step S102.

[0097] If the control unit 11 determines that the travel route is the last travel route (YES in step S107), it calculates the total amount of power required for each of the calculated travel routes as the amount of power required for the travel route group (step S108). For example, the travel route group includes travel route A_1, travel route 1_B, travel route B_2, travel route 2_3, and travel route 3_3T. For example, A_1, 1_B, B_2, and 2_3 are travel routes that have been traveled before, and 3_3T is a travel route that has not been traveled before.

[0098] The required power for A_1, 1_B, B_2, and 2_3 is derived based on the energy consumption obtained by the energy consumption acquisition subroutine (step S105). The required power for 3_3T is the required power (base energy consumption + total energy consumption of each electrical device) calculated by the required power calculation subroutine (step S110). For example, the required power for A_1, 1_B, B_2, 2_3, and 3_3T are "2kWh, 4kWh, 1.3kWh, 4kWh, and 4.7kWh". The required power (16kWh) corresponding to the driving route group is the sum of the required power for A_1, 1_B, B_2, 2_3, and 3_3T (2kWh + 4kWh + 1.3kWh + 4kWh + 4.7kWh).

[0099] The control unit 11 stores the operation plan in the operation plan DB 158 of the large-capacity storage unit 15, associating it with the child route ID, vehicle ID, and driver ID (step S109), and then terminates the process. Specifically, the control unit 11 assigns a plan ID to identify the operation plan. If there is a record of travel, the control unit 11 stores in the operation plan DB 158, associating it with the assigned plan ID, the child route ID that identifies each travel route, the vehicle ID, the driver ID, the scheduled departure date and time, the scheduled arrival date and time, the distance, the amount of power required for each travel route, the amount of power required for the travel route group (the sum of the amount of power required for each travel route), the weather category, the temperature, and the probability of precipitation.

[0100] Alternatively, if there is no record of driving, the control unit 11 stores in the operation plan DB 158 the following information, associated with the assigned plan ID: sub-route ID that identifies each driving route, vehicle ID, driver ID, scheduled departure date and time, scheduled arrival date and time, distance, required power consumption for each driving route, required power consumption corresponding to the driving route group, weather category, temperature, probability of precipitation, power consumption of headlights, power consumption of small lamps, power consumption of air conditioner, power consumption of rear defogger, and power consumption of wipers.

[0101] Figure 12 is a flowchart showing the processing procedure of the subroutine for determining driving performance. The control unit 11 of server 1 obtains the driver ID and vehicle type of the vehicle 2 from the vehicle DB 151 of the large-capacity storage unit 15 based on the vehicle ID (step S01). The control unit 11 obtains the weather classification from an external weather forecast server or site based on the longitude and latitude of the starting point of the driving route via the communication unit 13 (step S02).

[0102] The control unit 11, via the communication unit 13, obtains temperature and precipitation probability announced by the Japan Meteorological Agency, etc., from an external weather forecast server or site based on the starting point of the travel route (step S03). Based on the obtained temperature, the control unit 11 identifies the corresponding temperature level from the weather DB 153 of the large-capacity storage unit 15 (step S04). Based on the obtained precipitation probability, the control unit 11 identifies the corresponding precipitation level from the weather DB 153 of the large-capacity storage unit 15 (step S05). Based on the departure date included in the date and time information corresponding to the travel route, the control unit 11 identifies the season from the season DB 152 of the large-capacity storage unit 15 (step S06).

[0103] The control unit 11 determines whether the driving route data has been stored in the driving route-specific energy consumption DB 157 of the large-capacity storage unit 15 (step S07). Specifically, the control unit 11 obtains the child route ID of the driving route from the driving route DB 156 of the large-capacity storage unit 15 based on the departure point and destination of the driving route, or the weather category boundary. The control unit 11 determines whether the driving route data has been stored in the driving route-specific energy consumption DB 157 by determining whether the acquired child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date and time information (season and departure date and time) matches the child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date and time information stored in the driving route-specific energy consumption DB 157 of the large-capacity storage unit 15.

[0104] If the travel route data is stored in the travel route-specific energy consumption DB157 (YES in step S07), the control unit 11 determines that there is a record of travel on that travel route (step S08). The control unit 11 terminates the subroutine for determining travel record and returns. If the travel route data is not stored in the travel route-specific energy consumption DB157 (NO in step S07), the control unit 11 determines that there is no record of travel on that travel route (step S09). The control unit 11 terminates the subroutine for determining travel record and returns.

[0105] Figure 13 is a flowchart showing the processing procedure of the subroutine for acquiring the electricity consumption. The control unit 11 of server 1 executes the processes in steps S11 to S16. Note that the processes in steps S11 to S16 are the same as the processes in steps S01 to S06, so the explanation is omitted.

[0106] The control unit 11 retrieves the child route ID and fuel consumption stored in the fuel consumption DB 157 of the large-capacity storage unit 15 (step S17). Specifically, the control unit 11 retrieves the child route ID of the driving route from the driving route DB 156 of the large-capacity storage unit 15 based on the departure point and destination of the driving route, or the weather category boundary. Based on the retrieved child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date and time information, the control unit 11 retrieves the fuel consumption of the driving route from the fuel consumption DB 157 of the large-capacity storage unit 15 for driving routes that match the child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date and time information stored in the driving route fuel consumption DB 157. The control unit 11 finishes the fuel consumption acquisition subroutine and returns.

[0107] Figure 14 is a flowchart showing the processing procedure of the subroutine for calculating the required amount of power. The control unit 11 of server 1 identifies the season from the season DB 152 of the large-capacity storage unit 15 based on the departure date included in the date and time information corresponding to the travel route (step S21). The control unit 11 obtains the initial power consumption value corresponding to the identified season from the season DB 152 of the large-capacity storage unit 15 as the reference power consumption (step S22).

[0108] The control unit 11 calculates the distance from the starting point to the destination along the driving route (step S23). Based on the acquired standard energy consumption and the calculated distance, the control unit 11 derives the standard required energy amount using the above-described formula (1) (step S24). The control unit 11 obtains the temperature and probability of precipitation corresponding to the driving route from an external weather forecast server or site via the communication unit 13 (step S25).

[0109] The control unit 11 identifies the electrical equipment to which the required power consumption will be added from the seasonal DB 152 of the large-capacity storage unit 15, based on the temperature and probability of precipitation corresponding to the driving route, as well as the season and departure date and time (step S26). Based on the vehicle type, the control unit 11 obtains the power consumption of each identified electrical equipment from the power consumption DB 154 of the large-capacity storage unit 15 (step S27).

[0110] The control unit 11 calculates the power consumption of each electrical device (step S28). Specifically, the control unit 11 obtains the travel time by calculating the difference between the arrival time and departure time of the travel route. Based on the power consumption of each electrical device and the travel time, the control unit 11 calculates the power consumption of each electrical device using equation (3) described later. The power consumption of each electrical device is expressed by the following equation (3). The required power consumption of electrical equipment (kWh) = Power consumption of electrical equipment (kW) × Time required for driving (h) ... (3) The control unit 11 terminates the subroutine for calculating the required power consumption and returns.

[0111] According to this embodiment, if there is a record of driving history, the accuracy of the energy consumption can be improved by calculating the required amount of power for each driving route based on driver, vehicle type, driving route group, weather, and date and time information.

[0112] According to this embodiment, if there is a record of driving, it is possible to derive the amount of electricity required for each driving route based on the electricity consumption obtained from the driving record.

[0113] According to this embodiment, it is possible to create an operation plan that includes the amount of electricity required for each route.

[0114] According to this embodiment, even in cases where there is no past driving record, such as a new driving route, it is possible to appropriately calculate the required amount of power based on date and time information, weather, driving route, and power consumption of electrical equipment.

[0115] (Embodiment 2) Embodiment 2 relates to a configuration in which the energy consumption of a driving route is updated after the start of driving along that route, based on the location information of the vehicle 2, the remaining battery level, and the distance traveled. Note that explanations of content that overlaps with Embodiment 1 will be omitted.

[0116] Returning to Figure 9, the process of updating the energy consumption of the driving route will be explained. The onboard unit 3 installed in vehicle 2 acquires the power supply status (supplying / supplying off) of the motor of vehicle 2 after the start of driving on the driving route corresponding to vehicle 2. The onboard unit 3 determines whether a predetermined time interval (for example, 1 minute) has elapsed since the last time the status information of vehicle 2 was sent to server 1.

[0117] The in-vehicle unit 3 acquires status information of vehicle 2 when a predetermined time interval has elapsed or when the power supply status is stopped (arrival at destination). The status information of vehicle 2 includes longitude and latitude, battery level, cumulative mileage, air conditioning status (ON / OFF), air conditioning airflow, rear defogger status (ON / OFF), wiper status (ON / OFF), small lamp status (on / off) or headlight status (on / off), etc.

[0118] The in-vehicle unit 3 associates the vehicle ID of vehicle 2 with the acquired status information of vehicle 2 and transmits it to the server 1. The server 1 receives the vehicle ID and status information transmitted from the in-vehicle unit 3. The server 1 stores the status information of vehicle 2 in the vehicle status history DB 155, associating it with the received vehicle ID.

[0119] Server 1 determines whether predetermined update conditions have been met based on the longitude and latitude of Vehicle 2. While various update conditions are possible, the following are examples: Server 1 determines that the update conditions have been met if Vehicle 2's current location is at the boundary of either the destination or a weather zone. Server 1 determines that the update conditions have not been met if Vehicle 2's current location is neither at the destination nor a weather zone boundary.

[0120] Specifically, Server 1 determines whether Vehicle 2's current location is the destination based on the longitude and latitude of Vehicle 2's current location and the longitude and latitude of the destination. Server 1 also obtains a weather zone (e.g., Tokyo) from an external weather forecast server or site based on Vehicle 2's longitude and latitude. Server 1 then determines whether Vehicle 2 is at the boundary of the weather zone based on the obtained longitude and latitude of Vehicle 2's current location and the longitude and latitude of the region indicated in the obtained weather zone.

[0121] Server 1, upon determining that the predetermined update conditions have been met, derives the energy consumption for the route based on the remaining battery level and distance traveled. Server 1 obtains the corresponding sub-route ID from the route DB 156 based on the starting point and current location of the route. Server 1 obtains the vehicle type and driver ID from the vehicle DB 151 based on the vehicle ID. Server 1 updates the energy consumption stored in the route-specific energy consumption DB 157 using the obtained sub-route ID, vehicle type, driver ID, vehicle ID, weather category, season, departure date and time, weather, and the derived energy consumption.

[0122] Specifically, Server 1 retrieves the previous cumulative mileage used in the previous energy consumption calculation and the previous battery level used in the previous energy consumption calculation for Vehicle 2 from the Vehicle Status History DB 155 based on the Vehicle ID. Note that the data (records) used in the previous energy consumption calculation may be identified using an energy consumption calculation flag or the like. Based on the current cumulative mileage transmitted from the in-vehicle device 3 and the retrieved previous cumulative mileage, Server 1 calculates the current mileage (current cumulative mileage - previous cumulative mileage).

[0123] Server 1 calculates the current power consumption (previous battery level - current battery level) based on the current battery level transmitted from the in-vehicle unit 3 and the previously acquired battery level. Based on the calculated current driving distance and current power consumption, Server 1 derives the energy consumption for the driving route using equation (4) described below. The energy consumption for the driving route is expressed by the following equation (4). Electricity cost (km / kWh) = distance (km) / power consumption (kWh)…(4)

[0124] Server 1 retrieves the driver ID and vehicle type of vehicle 2 from the vehicle database 151 based on the vehicle ID. Server 1 retrieves the temperature and probability of precipitation announced by the Japan Meteorological Agency from an external weather forecast server or site based on the starting point of the driving route. Server 1 identifies the corresponding temperature level from the weather database 153 based on the retrieved temperature.

[0125] Server 1 identifies the corresponding precipitation level from the weather DB 153 based on the acquired probability of precipitation. Server 1 acquires the season from the season DB 152 based on the departure date of the travel route. Server 1 acquires the weather classification from an external weather forecast server or site based on the longitude and latitude indicating the departure point of vehicle 2. Server 1 acquires the corresponding child route ID from the travel route DB 156 based on the departure point and current location of the travel route.

[0126] Server 1 determines the consistency between the acquired child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date / time information and the child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date / time information stored in the route-specific energy consumption DB 157 of the large-capacity storage unit 15. Based on this, it identifies the energy consumption corresponding to the child route ID, vehicle type, driver ID, vehicle ID, weather category, weather (temperature level and precipitation level), and date / time information (season and departure date / time) from the route-specific energy consumption DB 157.

[0127] Server 1 updates the energy consumption identified from the route-specific energy consumption DB 157 using the derived energy consumption. For example, Server 1 calculates a weighted average value based on the derived energy consumption and the identified energy consumption. Server 1 updates the energy consumption identified from the route-specific energy consumption DB 157 using the weighted average value of the calculated energy consumption. Alternatively, Server 1 may directly update the energy consumption identified from the route-specific energy consumption DB 157 using the derived energy consumption.

[0128] This makes it possible to improve the accuracy of the energy consumption for each route by using the actual driving data of vehicle 2 to update the energy consumption for each route stored in the route-specific energy consumption DB157.

[0129] Figure 15 is a flowchart showing the processing procedure when updating the energy consumption of a driving route. The onboard control unit 31 of the onboard device 3 installed in vehicle 2 acquires the power supply status (supplying / supply stopped) of the motor of vehicle 2 (step S321). The onboard control unit 31 determines, via the clock unit 34, whether a predetermined time interval (e.g., 1 minute) has elapsed since the last transmission of vehicle 2 status information to server 1, or whether the power supply status is supply stopped (step S322).

[0130] The on-board control unit 31 waits if neither of the following conditions is met: a predetermined time interval has elapsed, or the power supply is not supplied (NO in step S322). If either of the above conditions is met: a predetermined time interval has elapsed, or the power supply is not supplied (YES in step S322), the on-board control unit 31 acquires status information for the vehicle 2 (step S323).

[0131] Status information includes longitude and latitude, battery level, cumulative mileage, air conditioning status, air conditioning airflow, rear defogger status, wiper status, small lamp status or headlight status, etc. The on-board control unit 31 associates the acquired status information with the vehicle ID of vehicle 2 and transmits it to the server 1 via the communication unit 33 (step S324). The control unit 11 of the server 1 receives the vehicle ID and status information transmitted from the on-board unit 3 via the communication unit 13 (step S121).

[0132] The control unit 11 stores the status information of the vehicle 2 in the vehicle status history DB 155 of the large-capacity storage unit 15, associating it with the received vehicle ID (step S122). Specifically, the control unit 11 stores the transmission date and time, longitude and latitude, battery level, cumulative mileage, air conditioning status (ON / OFF), air conditioning airflow (maximum airflow, airflow level 3, airflow level 2 or airflow level 1, etc.), rear defogger status (ON / OFF), wiper status (ON / OFF), small lamp status (on / off), headlight status (on / off), and creation date and time as a single record in the vehicle status history DB 155, as associated with the vehicle ID.

[0133] The control unit 11 determines whether the current location of vehicle 2 is the destination or the boundary of a weather zone, based on the vehicle's latitude and longitude (step S123). Specifically, the control unit 11 determines whether the vehicle's current location is the destination, based on the latitude and longitude of the vehicle's current location and the latitude and longitude of the destination. The control unit 11 also obtains the weather zone from an external weather forecast server or site via the communication unit 13, based on the latitude and longitude of the vehicle's departure point. If the departure point is the boundary of a weather zone, the control unit 11 obtains the new weather zone from two options: the old zone and the new zone. The control unit 11 determines whether the vehicle 2 is the boundary of a weather zone, based on the latitude and longitude of the vehicle's current location and the latitude and longitude of the region indicated in the obtained weather zone.

[0134] If the current position of vehicle 2 is not either the destination or the boundary of the weather category (NO in step S123), the control unit 11 returns to the process in step S121. If the current position of vehicle 2 is either the destination or the boundary of the weather category (YES in step S123), the control unit 11 executes a subroutine for updating the fuel consumption (step S124). The subroutine for updating the fuel consumption will be described later. The control unit 11 then terminates the process.

[0135] Figure 16 is a flowchart showing the processing procedure of the subroutine for updating the energy consumption. The control unit 11 of server 1 obtains the previous cumulative mileage used in the previous energy consumption calculation and the previous battery level used in the previous energy consumption calculation from the vehicle status history DB 155 of the large capacity storage unit 15 based on the vehicle ID (step S31). The control unit 11 calculates the current mileage (current cumulative mileage - previous cumulative mileage) based on the current cumulative mileage transmitted from the in-vehicle device 3 and the obtained previous cumulative mileage (step S32).

[0136] The control unit 11 calculates the current power consumption (previous battery level - current battery level) based on the current battery level transmitted from the in-vehicle unit 3 and the previously acquired battery level (step S33). Based on the calculated current driving distance and current power consumption, the control unit 11 derives the energy consumption for the driving route using the above-described formula (4) (step S34).

[0137] The control unit 11 executes the processes in steps S35 to S40. Note that the processes in steps S35 to S40 are the same as those in steps S01 to S06, so their explanation will be omitted.

[0138] The control unit 11 identifies the energy consumption stored in the energy consumption DB 157 for each driving route in the large-capacity storage unit 15 (step S41). Specifically, the control unit 11 obtains the child route ID of the driving route from the driving route DB 156 of the large-capacity storage unit 15 based on the departure point and destination of the driving route, or the weather category boundary. The control unit 11 determines the consistency between the obtained child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date / time information and the child route ID, vehicle type, driver ID, vehicle ID, weather category, weather, and date / time information stored in the energy consumption DB 157 for each driving route in the large-capacity storage unit 15, thereby identifying the energy consumption from the energy consumption DB 157 for each driving route.

[0139] The control unit 11 calculates a weighted average of the energy consumption based on the derived energy consumption and the identified energy consumption (step S42). Specifically, the control unit 11 weights the number of times the energy consumption calculated from past performance has been stored (updated), and also weights the number of times the energy consumption derived this time has been stored, and then calculates a weighted average. The weight is calculated as number of times / total number of times (number of past storages + number of current storages).

[0140] For example, if the number of times the past weighted average values ​​have been stored is 9, the weight of the past energy consumption (specified energy consumption) is 9 / 10 (0.9). Since the number of times the energy consumption was derived this time is 1, the weight of the derived energy consumption is 1 / 10 (0.1). Then, the control unit 11 calculates the weighted average value of the energy consumption based on the specified energy consumption (e.g., 5.9 km / kWh) and its weight (0.9), and the derived energy consumption (e.g., 6.7 km / kWh) and its weight (0.1). For example, the calculated weighted average value of the energy consumption is 5.98 kWh (6.7 × 0.1 + 5.9 × 0.9).

[0141] Furthermore, the energy consumption is not limited to the weighted average mentioned above; it may also be a simple average (or median), arithmetic mean, geometric mean, harmonic mean, the value derived in this study, or any other statistical measure.

[0142] The control unit 11 updates the energy consumption identified from the route-specific energy consumption DB 157 using the weighted average value of the calculated energy consumption (step S43). The control unit 11 finishes the energy consumption update subroutine and returns.

[0143] According to this embodiment, after starting to travel along a route, it becomes possible to update the energy consumption of that route based on the location information of the vehicle 2 corresponding to the route, the remaining battery level, and the distance traveled.

[0144] (Embodiment 3) Embodiment 3 relates to a method for creating a charging schedule for vehicle 2. Note that explanations of content that overlaps with Embodiments 1 and 2 will be omitted.

[0145] In this embodiment, Server 1 acquires date and time information, required power, and battery level of a vehicle 2 corresponding to a group of driving routes from a departure point to a destination. Server 1 stores the acquired date and time information, required power, and battery level in association with a vehicle ID that identifies the vehicle 2. Server 1 calculates the charge rate per unit time from the acquired date and time information, required power, and battery level.

[0146] Server 1 obtains the total contracted power amount and the maximum charging capacity per charger. Based on the obtained total contracted power amount and maximum charging capacity, Server 1 determines the number of chargers that can charge simultaneously. Based on the determined number of chargers and the calculated charging rate per unit time, Server 1 identifies the vehicle to be charged.

[0147] Figure 17 is an explanatory diagram showing an overview of the charging schedule system in Embodiment 3. Note that components that overlap with those in Figures 1 and 2 are denoted by the same reference numerals and their descriptions are omitted. The charging schedule system in this embodiment includes a charger 5. The charger 5 is connected to the vehicle 2's charging device via a charging plug and charging cable, etc.

[0148] Figure 18 is a block diagram showing an example configuration of server 1 in Embodiment 3. Note that components that overlap with those in Figure 2 are denoted by the same reference numerals and their descriptions are omitted. The large-capacity storage unit 15 includes a vehicle charger-compatible DB 159, a charger installation location DB 160, and a charging schedule DB 161. The vehicle charger-compatible DB 159 stores correspondence information between a vehicle 2 and a charger 5 connected to that vehicle 2. The charger installation location DB 160 stores the location where the charger 5 is installed. The charging schedule DB 161 stores the charging schedule for vehicle 2.

[0149] Figure 19 is an explanatory diagram showing an example of the record layout for the vehicle charger compatibility DB159 and the charger installation location DB160. The DB159 for vehicle chargers includes columns for vehicle ID, charger number, charging status, charging start date and time, and charging completion date and time. The vehicle ID column stores the vehicle ID that identifies vehicle 2. The charger number column stores the ID of charger 5, which is uniquely identified to identify each charger 5.

[0150] The Charging Status column stores the charging status of charger 5. The charging status includes not charging, charging, or charging complete. The Charging Start Date and Time column stores the charging start date and time for vehicle 2. The Charging Completion Date and Time column stores the charging completion date and time for vehicle 2.

[0151] The charger location database DB160 includes a charger number column and an installation location column. The charger number column stores the charger number that identifies charger 5. The installation location column stores the location (e.g., longitude and latitude) where charger 5 is installed.

[0152] Figure 20 is an explanatory diagram showing an example of the record layout of the charging schedule DB161. The charging schedule DB161 includes columns for Management ID, Vehicle ID, Required Power, Season Name, Departure Date and Time, Battery Level, Charge Amount, Available Charging Time, and Charge Amount per Unit Time.

[0153] The Management ID column stores the Management ID of the charging schedule data, which is uniquely identified to identify the data for each charging schedule. The Vehicle ID column stores the Vehicle ID that identifies Vehicle 2. The Required Energy column stores the total amount of energy required for each driving route, which was determined in step S108. The Season Name column stores the name of the season.

[0154] The Departure Date and Time column stores the departure date and time corresponding to the route group. The Battery Level column stores the battery level of vehicle 2. The Charge Amount column stores the amount of energy remaining after subtracting the battery level from the required energy. The Rechargeable Time column stores the time calculated based on the departure date and time and the current date and time (Departure Date and Time - Current Date and Time). The Charge Amount per Unit Time column stores the amount of energy charged per unit time in vehicle 2. The battery level, charge amount, rechargeable time, and charge amount per unit time are updated periodically (for example, every 10 minutes).

[0155] Figure 21 is a block diagram showing an example configuration of the charger 5. The charger 5 includes a charging control unit 51, a connection detection unit 52, and a communication unit 53. The charging control unit 51 controls the charging ON or OFF of the charger 5 according to a power command value (specifying the output power of the charger 5) provided by the server 1. The connection detection unit 52 detects the connection between the charger 5 and the vehicle 2. The communication unit 53 is a communication module for performing communication-related processing and sends and receives information with the server 1, etc.

[0156] Next, the process of creating a charging schedule for vehicle 2 will be explained. Server 1 determines whether or not a next-day operation plan exists in the operation plan DB 158 for each vehicle 2. In this embodiment, an example of a next-day operation plan is described, but it is not limited to this. For example, it can be similarly applied to operation plans for a relatively near future period, such as the day after next.

[0157] Server 1 extracts vehicles 2 whose operation plan for the following day exists in the operation plan DB158. Based on the vehicle ID of the extracted vehicles 2, Server 1 obtains the charging status of each vehicle 2. Based on the obtained charging status of vehicles 2, Server 1 identifies vehicles 2 that are not charged. Server 1 obtains the date and time information (season and departure date and time), required power, and battery level of the identified vehicles 2.

[0158] Specifically, Server 1 retrieves the departure date and time and required power amount for the identified vehicle 2 from the operation plan DB 158 based on the vehicle ID of the identified vehicle 2. Based on the retrieved departure date and time, Server 1 identifies the season from the season DB 152. Based on the identified vehicle ID of the identified vehicle 2, Server 1 retrieves the latest battery level of the identified vehicle 2 from the vehicle status history DB 155.

[0159] Server 1 calculates the charge rate per unit time. The charge rate per unit time is expressed by the following formula (5). Charge amount per unit time = (Required power - Battery level) / (Departure date and time - Current date and time) ... (5) Server 1 calculates the amount of charge per unit time for each vehicle 2 using the above-described formula (5), based on the acquired date and time information, required power, and remaining battery level.

[0160] Server 1 stores the acquired date and time information, required power, and battery level in the schedule DB 161, associating them with the vehicle ID of the identified vehicle 2. Specifically, Server 1 assigns a management ID for managing the schedule data. Server 1 stores the required power, season name, departure date and time, battery level, charge amount (required power - battery level), chargeable time (departure date and time - current date and time), and charge amount per unit time for vehicle 2 as a single record in the charge schedule DB 161, associating them with the assigned management ID and vehicle ID.

[0161] Note that the season included in the date and time information is not mandatory and does not need to be stored in the charging schedule DB161.

[0162] Next, the process for identifying vehicle 2 to be charged will be explained. Server 1 sorts the calculated charge amount per unit time in descending order, for example, the date and time information, required power amount, and battery level of vehicle 2. Server 1 outputs the sorted date and time information, required power amount, and battery level, associating them with the vehicle ID of each vehicle. Server 1 may also update the charging schedule DB 161 by associating the sorted date and time information, required power amount, and battery level with the vehicle ID of each vehicle.

[0163] Server 1 obtains the total contracted power amount from an external power management system, for example. For example, the total contracted power amount may be 20kW. Server 1 obtains the maximum charging capacity per charger 5, which is previously stored in the storage unit 12 or the large-capacity storage unit 15, for example. For example, the maximum charging capacity per charger 5 may be 6kW.

[0164] Server 1 determines the number of chargers 5 that can be charged simultaneously. The number of chargers 5 that can be charged simultaneously is expressed by the following equation (6). Number of chargers 5 = Total contracted power amount / Maximum charging capacity per charger 5 ... (6)

[0165] Server 1 determines the number of chargers 5 that can be charged simultaneously using equation (6) described above, based on the acquired total contracted power amount and the maximum charging capacity per charger 5. For example, the determined number of chargers 5 that can be charged simultaneously is 3.

[0166] Server 1 identifies the vehicles 2 to be charged based on the determined number of chargers 5 and the amount of charge per unit time after sorting. Specifically, Server 1 identifies the vehicles 2 to be charged in descending order of the amount of charge per unit time, based on the determined number of chargers 5.

[0167] The following describes the process of identifying vehicle 2 to be charged as an example. Server 1 obtains the required power for the next day, departure date and time, and battery level for each vehicle ID of multiple vehicles 2 that have returned to the business premises. For example, if the obtained required power, departure date and time, and battery level are... Vehicle ID: LF001, Required energy: 40kWh, Departure time: 14:00, Battery level: 8kWh Vehicle ID: LF002, Required power: 30kWh, Departure time: 09:00, Battery level: 12kWh Vehicle ID: LF003, Required power: 40kWh, Departure time: 09:00, Battery level: 5kWh Vehicle ID: LF004, Required power: 40kWh, Departure time: 10:00, Battery level: 4kWh Vehicle ID: LF005, Required power: 20kWh, Departure time: 12:00, Battery level: 6kWh.

[0168] Server 1 calculates the charge amount (required power amount - battery level) and the charging time (departure date and time - current date and time) based on the acquired date and time information, required power amount, and battery level. Based on the acquired date and time information and the calculated required power amount and battery level, Server 1 calculates the charge amount per unit time for each vehicle 2 using the above formula (5).

[0169] The calculated charge amount per unit time Vehicle ID: LF001, Required energy: 40kWh, Departure time: 14:00, Battery level: 8kWh, Charge amount: 32kWh, Charging time: 20h, Charge rate per unit time: 1.6kWh / h Vehicle ID: LF002, Required energy: 30kWh, Departure time: 09:00, Battery level: 12kWh, Charge amount: 18kWh, Charging time: 15h, Charge rate per unit time: 1.2kWh / h Vehicle ID: LF003, Required energy: 40kWh, Departure time: 09:00, Battery level: 5kWh, Charge amount: 35kWh, Charging time: 15h, Charge rate per unit time: 2.3kWh / h Vehicle ID: LF004, Required energy: 40kWh, Departure time: 10:00, Battery level: 4kWh, Charge amount: 36kWh, Charging time: 16h, Charge rate per unit time: 2.25kWh / h Vehicle ID: LF005, Required energy: 20kWh, Departure time: 12:00, Battery level: 6kWh, Charge amount: 14kWh, Charging time: 18h, Charge rate per unit time: 0.78kWh / h.

[0170] Server 1 sorts the calculated charge amount per unit time in descending order. The sorted vehicle ID, date and time information, required power, and battery level are Vehicle ID: LF003, Required energy: 40kWh, Departure time: 09:00, Battery level: 5kWh, Charge amount: 35kWh, Charging time: 15h, Charge rate per unit time: 2.3kWh / h Vehicle ID: LF004, Required energy: 40kWh, Departure time: 10:00, Battery level: 4kWh, Charge amount: 36kWh, Charging time: 16h, Charge rate per unit time: 2.25kWh / h Vehicle ID: LF001, Required energy: 40kWh, Departure time: 14:00, Battery level: 8kWh, Charge amount: 32kWh, Charging time: 20h, Charge rate per unit time: 1.6kWh / h Vehicle ID: LF002, Required energy: 30kWh, Departure time: 09:00, Battery level: 12kWh, Charge amount: 18kWh, Charging time: 15h, Charge rate per unit time: 1.2kWh / h Vehicle ID: LF005, Required energy: 20kWh, Departure time: 12:00, Battery level: 6kWh, Charge amount: 14kWh, Charging time: 18h, Charge rate per unit time: 0.78kWh / h.

[0171] Server 1 determines the number of chargers 5 that can be charged simultaneously (3 units) using the above formula (6), based on the total contracted power amount (e.g., 20kW) and the maximum charging capacity per charger 5 (e.g., 6kW).

[0172] Based on the determined number of chargers 5 that can be charged simultaneously, Server 1 identifies the vehicles 2 with vehicle IDs "LF003", "LF004", and "LF001" as vehicles 2 to be charged, sorted from the highest amount of charge per unit time among the multiple vehicles 2.

[0173] The server 1 then sends a connection instruction between the vehicle 2 and the charger 5 to the driver's terminal 4 of the driver operating each identified vehicle 2. The server 1 may also send the connection instruction to the corresponding driver's email address. The driver's terminal 4 receives the connection instruction sent from the server 1 and displays it on the screen. This makes it possible to achieve charging according to the operation plan even if the number of installed chargers is less than the number of vehicles.

[0174] After the driver connects the vehicle 2 and the charger 5, the driver terminal 4 accepts the vehicle ID of vehicle 2 and the charger number of charger 5 from the driver. The driver terminal 4 transmits the received vehicle ID and charger number to the server 1. The server 1 receives the vehicle ID and charger number transmitted from the driver terminal 4.

[0175] Server 1 determines the consistency between the location information of vehicle 2 and the location information of charger 5 based on the received vehicle ID and charger number. Specifically, Server 1 obtains the latest longitude and latitude of vehicle 2 from the vehicle status history DB 155 based on the vehicle ID. Server 1 obtains the location information of the place where charger 5 is installed from the charger installation location DB 160 based on the charger number.

[0176] Server 1 determines whether the acquired location information of vehicle 2 matches the location information of the charger. If the two do not match, Server 1 sends an alert (first alert) to the driver terminal 4 indicating that the location information does not match. The driver terminal 4 receives the first alert sent from Server 1 and displays the received first alert on its screen.

[0177] Server 1 determines the accuracy of the relationship between the charging completion date and time and the departure date and time if both match. Specifically, Server 1 obtains the current date and time as the charging start date and time for Vehicle 2. Based on the required power and remaining battery level of Vehicle 2, Server 1 calculates the amount of charge (required power - remaining battery level) for Vehicle 2.

[0178] Server 1 calculates the charging completion date and time for vehicle 2 based on the acquired charging start date and time and the calculated charging amount. The charging completion date and time is expressed by the following formula (7). Charging completion time = Charging start time + Charge amount / Maximum charging capacity per unit of charger 5 …(7) Server 1 obtains, for example, the maximum charging capacity per charger 5 that has been previously stored in the storage unit 12 or the large-capacity storage unit 15. Based on the charging start date and time, the amount of charge, and the obtained maximum charging capacity per charger 5, Server 1 calculates the charging completion date and time for the vehicle 2 using the formula (7) described above.

[0179] If the calculated charging completion date and time is not before the departure date and time of the vehicle 2, Server 1 sends an alert (second alert) to the driver terminal 4, including a note that charging will not be completed in time. The driver terminal 4 receives the second alert sent from Server 1 and displays the received second alert on its screen. The second alert may also include a recommendation to use a charger that can rapidly charge the vehicle 2's battery using DC current in a relatively short time.

[0180] If the calculated charging completion date and time is earlier than the departure date and time of the vehicle 2, Server 1 outputs a charging instruction to the charger 5 connected to the vehicle 2. The charger 5 receives the charging instruction sent from Server 1. The charger 5 charges the vehicle 2 connected to the charger 5 according to the received charging instruction.

[0181] Server 1 associates the vehicle ID of vehicle 2 with the charger number of charger 5, and stores the charging status ("charging"), charging start date and time, and charging completion date and time as a single record in the vehicle charger-compatible DB159.

[0182] Furthermore, the order in which the above-mentioned determination of the consistency of location information and the accuracy of the relationship between the charging completion date and time and the departure date and time are determined is not limited; either can be determined first.

[0183] In this embodiment, the determination of the consistency of location information, which is longitude and latitude, was performed, but this is not the only method. For example, the consistency of location information may be determined by the connection status between vehicle 2 and charger 5 using wireless connection means such as WiFi, Bluetooth®, Zigbee®, or RFID provided on vehicle 2 and charger 5. For example, if a connection is established between vehicle 2 and charger 5, server 1 determines that the location information matches. If a connection is not established between vehicle 2 and charger 5, server 1 determines that the location information does not match.

[0184] It should be noted that the process is not limited to determining the consistency of location information as described above. For example, it may also perform a process to determine the consistency of license plates. Specifically, Server 1 acquires an image of the license plate of Vehicle 2 taken by an imaging device installed near Charger 5. Server 1 uses known image recognition technology to analyze the acquired image of the license plate and recognize the number written on it. Based on the recognized number and the license plate number of Vehicle 2 stored in Vehicle DB 151, Server 1 determines the consistency of the license plates.

[0185] Figures 22 and 23 are flowcharts showing the processing procedure for identifying the vehicle 2 to be charged. The control unit 11 of the server 1 extracts the vehicle ID of the vehicle 2 corresponding to the operation plan for the next day from the operation plan DB 158 of the large-capacity storage unit 15 (step S131). Based on the extracted vehicle ID of each vehicle 2, the control unit 11 obtains the charging status of each vehicle 2 from the vehicle charger corresponding DB 159 of the large-capacity storage unit 15 (step S132). Based on the obtained charging status of each vehicle 2, the control unit 11 extracts the vehicle 2 whose charging status is not charged (step S133).

[0186] The control unit 11 acquires date and time information (season and departure date and time) and required power for the extracted vehicle 2 (step S134). Specifically, based on the vehicle ID of the extracted vehicle 2, the control unit 11 acquires the departure date and time corresponding to the group of travel routes and the required power for each travel route from the operation plan DB 158 of the large capacity storage unit 15. The control unit 11 calculates the total power for each acquired required power for each travel route. Based on the acquired departure date and time, the control unit 11 acquires the season from the season DB 152.

[0187] Based on the vehicle ID of the extracted vehicle 2, the control unit 11 obtains the latest battery level of the vehicle 2 from the vehicle status history DB 155 in the large capacity storage unit 15 (step S135). Based on the obtained date and time information, required power, and battery level, the control unit 11 calculates the charge amount per unit time using the above-described formula (5) (step S136).

[0188] The control unit 11 stores the acquired date and time information, required power (total power), and battery level in the charging schedule DB 161 of the large-capacity storage unit 15, associating them with the vehicle ID of the identified vehicle 2 (step S137). Specifically, the control unit 11 assigns a management ID for managing the schedule data. The control unit 11 stores the required power, season name, departure date and time, battery level, charge amount (required power - battery level), chargeable time (departure date and time - current date and time), and charge amount per unit time as a single record in the charging schedule DB 161, associating them with the assigned management ID and vehicle ID.

[0189] The control unit 11 executes a subroutine for identifying the vehicle 2 to be charged (step S138). The subroutine for identifying the vehicle to be charged will be described later. The control unit 11 transmits a connection instruction between the vehicle 2 and the charger 5 to the driver terminal 4 of the driver operating each identified vehicle 2 via the communication unit 13 (step S139).

[0190] The control unit 41 of the driver terminal 4 receives a connection instruction transmitted from the server 1 via the communication unit 43 (step S431). The control unit 41 displays the received connection instruction via the display unit 45 (step S432). The control unit 41 receives input from the driver of the vehicle ID of vehicle 2 and the charger number of charger 5 via the input unit 44 (step S433). The control unit 41 transmits the received vehicle ID and charger number to the server 1 via the communication unit 43 (step S434).

[0191] The control unit 11 of server 1 receives the vehicle ID and charger number transmitted from the driver terminal 4 via the communication unit 13 (step S140). Based on the received vehicle ID, the control unit 11 obtains the latest longitude and latitude of the vehicle 2 from the vehicle status history DB 155 in the large capacity storage unit 15 (step S141).

[0192] The control unit 11 obtains location information of the location where the charger 5 is installed from the charger location DB 160 in the large-capacity storage unit 15 based on the charger number (step S142). The control unit 11 determines whether the obtained location information of the vehicle 2 matches the location information of the charger (step S143).

[0193] If the two do not match (NO in step S143), the control unit 11 sends a first alert to the driver terminal 4 via the communication unit 13, indicating that the location information does not match (step S150). The control unit 41 of the driver terminal 4 receives the first alert sent from the server 1 via the communication unit 43 (step S435). The control unit 41 displays the received first alert via the display unit 45 (step S436).

[0194] If both conditions match (YES in step S143), the control unit 11 obtains the current date and time as the charging start date and time for vehicle 2 (step S144). Based on the required power and remaining battery level of vehicle 2, the control unit 11 calculates the amount of charge (required power - remaining battery level) for vehicle 2 (step S145).

[0195] The control unit 11 calculates the date and time when charging is complete for the vehicle 2 (step S146). Specifically, the control unit 11 obtains the maximum charging capacity per charger 5 that has been previously stored in the storage unit 12 or the large-capacity storage unit 15. Based on the charging start date and time, the amount of charge, and the obtained maximum charging capacity per charger 5, the control unit 11 calculates the date and time when charging is complete for the vehicle 2 using the above-described formula (7).

[0196] The control unit 11 determines whether the calculated charging completion date and time is earlier than the departure date and time of the vehicle 2 (step S147). If the calculated charging completion date and time is earlier than the departure date and time of the vehicle 2 (YES in step S147), the control unit 11 sends a charging instruction to the charger 5 connected to the vehicle 2 via the communication unit 13 (step S148).

[0197] The control unit 11 associates the vehicle ID of vehicle 2 with the charger number of charger 5, stores the charging status ("charging"), the charging start date and time, and the charging completion date and time as a single record in the vehicle charger-compatible DB 159 of the large-capacity storage unit 15 (step S149). The control unit 11 then terminates the process.

[0198] If the calculated charging completion date and time is not earlier than the departure date and time of the vehicle 2 (NO in step S147), the control unit 11 sends a second alert to the driver terminal 4 via the communication unit 13 (step S151). The second alert may include, for example, a message to the driver stating that charging will not be completed in time and recommending the use of a fast-charging charger.

[0199] The control unit 41 of the driver terminal 4 receives the second alert transmitted from the server 1 via the communication unit 43 (step S437). The control unit 41 displays the received second alert via the display unit 45 (step S438).

[0200] Figure 24 is a flowchart showing the processing procedure of a subroutine for identifying the vehicle to be charged. The control unit 11 of server 1 sorts the calculated charge amount per unit time in descending order, for example, the date and time information, required power amount, and battery level of vehicle 2 (step S51). The control unit 11 outputs the sorted date and time information, required power amount, and battery level, associating them with the vehicle ID (step S52).

[0201] The control unit 11 obtains the total contracted power amount from an external power management system, for example, via the communication unit 13 (step S53). The control unit 11 obtains the maximum charging capacity per charger 5 that has been previously stored in the storage unit 12 or the large-capacity storage unit 15 (step S54). Based on the obtained total contracted power amount and the maximum charging capacity per charger 5, the control unit 11 determines the number of chargers 5 that can be charged simultaneously using the above-described equation (6) (step S55).

[0202] The control unit 11 determines the number of chargers 5 as the number of vehicles 2 to be identified, and identifies the vehicles 2 to be charged from among multiple charge amounts per unit time, in descending order of charge amount per unit time (step S56). The control unit 11 finishes the subroutine for identifying the vehicles to be charged and returns.

[0203] According to this embodiment, it is possible to create an appropriate charging schedule for vehicle 2 by utilizing the required amount of power calculated based on the power consumption identified by the driver, driving route group, weather, and date and time information.

[0204] According to this embodiment, if the location information of the vehicle 2 and the location information of the location where the charger 5 connected to the vehicle 2 is installed do not match, it is possible to output a first alert.

[0205] According to this embodiment, a second alert can be output if the charging completion date and time in vehicle 2 is not earlier than the departure date and time.

[0206] <Modification 1 in Embodiment 3> This section explains the process of recreating the charging schedule. For example, if a second vehicle (vehicle 2), different from vehicle 2 (vehicle 1), returns to the business premises, the charging schedule for this second vehicle (vehicle 2) and for multiple vehicles 1 (vehicle 2) whose charging status is either uncharged or charging will need to be readjusted based on the required power, departure date and time, and remaining battery level.

[0207] Specifically, Server 1 acquires the date and time information, required power, and battery level of multiple first vehicles 2 whose charging status is either uncharged or charging. From the acquired date and time information, required power, and battery level of each first vehicle 2, Server 1 calculates the charge rate per unit time for each first vehicle 2. Server 1 acquires the date and time information, required power, and battery level of a second vehicle 2. From the acquired date and time information, required power, and battery level of the second vehicle 2, Server 1 calculates the charge rate per unit time for that second vehicle 2.

[0208] Server 1 re-sorts the data by the amount of charge per unit time calculated for the first vehicle 2 and the second vehicle 2. Server 1 then outputs the date and time information, required power, and remaining battery level, associating them with the vehicle ID of each vehicle 2.

[0209] Then, Server 1 acquires the total contracted power amount and the maximum charging capacity per charger 5, similar to the processing in Embodiment 3. Based on the acquired total contracted power amount and maximum charging capacity, Server 1 determines the number of chargers that can be used for simultaneous charging. Based on the determined number of chargers and the calculated charging amount per unit time, Server 1 identifies the vehicle 2 to be charged.

[0210] Figure 25 is a flowchart showing the processing procedure when recreating the charging schedule. The control unit 11 of the server 1 extracts the vehicle IDs of the first vehicle 2 whose charging status is either not charged or charging from the car charger-compatible DB 159 of the large-capacity storage unit 15 (step S161). Based on the extracted vehicle IDs of each first vehicle 2, the control unit 11 obtains the departure date and time, required power amount, and battery level for each first vehicle 2 (step S162). Note that the process for obtaining date and time information, required power amount, and battery level is the same as in steps S134 to S135, so a detailed explanation is omitted.

[0211] The control unit 11 calculates the amount of charge per unit time in the first vehicle 2 using the above-described formula (5) based on the acquired date and time information, required power, and remaining battery level (step S163). The control unit 11 acquires the vehicle ID of the second vehicle 2 (step S164). For example, the control unit 41 of the driver terminal 4 receives the input of the vehicle ID of the second vehicle 2 from the driver via the input unit 44. The control unit 41 may also transmit the received vehicle ID to the server 1 via the communication unit 43.

[0212] The control unit 11 acquires the date and time information, required power amount, and battery level of the second vehicle 2 based on the acquired vehicle ID (step S165). Since the processing in step S165 is the same as the processing in step S162, a detailed explanation is omitted. Based on the acquired date and time information, required power amount, and battery level, the control unit 11 calculates the amount of charge per unit time for the second vehicle 2 using the above-described formula (5) (step S166). The control unit 11 executes the processing in step S137. The subsequent processing is the same as the processing in Figures 22 and 23 in Embodiment 3, so the same reference numerals are used for overlapping components and their explanation is omitted.

[0213] According to this modified version, it becomes possible to ensure charging for multiple vehicles 2, including the second vehicle 2 that has returned to the business premises, by adjusting the charging schedule as needed.

[0214] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the claims, not in the sense described above, and all modifications are intended to be in the sense and scope equivalent to the claims.

[0215] The matters described in each embodiment can be combined with each other. Furthermore, the independent and dependent claims described in the claims can be combined with each other in any combination, regardless of the form of reference. In addition, the claims use a form in which claims referencing two or more other claims (multi-claim form), but are not limited to this. A form in which multi-claims referencing at least one multi-claim (multi-multi-claim) may also be used. [Explanation of Symbols]

[0216] 1. Information processing device (server) 11 Control Unit 12 Storage section 13 Communications Department 14 Reading section 15 Mass storage 151 Vehicle Database 152 Seasonal DB 153 Weather DB 154 Power consumption DB 155 Vehicle Condition History Database 156 Driving Route Database 157 Electricity consumption by route 158 Operation Plan Database 159 Car Charger Compatible DB 160 Charger installation location DB 161 Charging Schedule DB 1a Portable storage medium 1b Semiconductor memory 1P Control Program 2 vehicles 3 Onboard equipment 31. On-board control unit 32 Storage section 33 Communications Department 34 Clock Department 3P control program 4. Information processing terminal (driver's terminal) 41 Control Unit 42 Storage section 43 Communications Department 44 Input section 45 Display section 4P control program 5 charger 51 Charging Control Unit 52 Connection detection unit 53 Communications Department

Claims

1. The system acquires a set of driving routes, including multiple routes from the starting point to the destination, and the vehicle type. Obtain weather and date / time information corresponding to each driving route. By referring to a memory unit that stores electricity consumption associated with vehicle type, driving route, weather, and date / time information, the electricity consumption for each driving route is identified based on the acquired vehicle type, driving route group, weather, and date / time information. Based on the identified energy consumption, the required amount of electricity for each driving route is derived. After the start of travel along the aforementioned route, the vehicle's location information, battery level, and distance traveled corresponding to the aforementioned route are acquired at predetermined time intervals. Based on the acquired location information, it is determined whether or not the predetermined update conditions have been met. When the specified update conditions are met, the energy consumption of the aforementioned route is calculated based on the acquired battery level and distance traveled. The calculated energy consumption is used to update the energy consumption in the storage unit, which is stored in association with the vehicle type, driving route, weather, and date and time information. An information processing method in which a computer performs the processing.

2. The aforementioned weather includes information on temperature and probability of precipitation, The aforementioned date and time information includes the season and departure date and time for each route. The information processing method according to claim 1.

3. Multiple temperature levels based on reference temperature and multiple precipitation levels based on reference precipitation probability are provided. Based on the aforementioned temperature, identify the temperature level, Based on the aforementioned probability of precipitation, the precipitation level is determined, By referring to the storage unit that stores the electricity consumption associated with the vehicle type, driving route, temperature level, precipitation level, and date and time information, the electricity consumption for each driving route is determined based on the identified temperature level and precipitation level, the vehicle type, the group of driving routes, and the date and time information. The information processing method according to claim 2, wherein the processing is performed by a computer.

4. If the aforementioned driving route is not stored in the memory unit, the standard energy consumption is determined based on the date and time information. Based on the identified standard energy consumption and the aforementioned driving route, the standard power consumption is derived. Based on the aforementioned weather and date / time information, the power consumption of electrical equipment including air conditioning, lights, and wipers is derived. The total power consumption, calculated from the derived reference power consumption and the power consumption of the electrical equipment, and the energy consumption are determined based on the aforementioned driving route. The information processing method according to claim 1 or 2, wherein the processing is performed by a computer.

5. The system acquires a set of driving routes, including multiple routes from the starting point to the destination, and the vehicle type. Obtain weather and date / time information corresponding to each driving route. By referring to a memory unit that stores electricity consumption associated with vehicle type, driving route, weather, and date / time information, the electricity consumption for each driving route is identified based on the acquired vehicle type, driving route group, weather, and date / time information. Based on the identified energy consumption, the required amount of electricity for each driving route is derived. After the start of travel along the aforementioned route, the vehicle's location information, battery level, and distance traveled corresponding to the aforementioned route are acquired at predetermined time intervals. Based on the acquired location information, it is determined whether or not the predetermined update conditions have been met. When the specified update conditions are met, the energy consumption of the aforementioned route is calculated based on the acquired battery level and distance traveled. The calculated energy consumption is used to update the energy consumption in the storage unit, which is stored in association with the vehicle type, driving route, weather, and date and time information. A program that instructs a computer to perform a process.

6. An information processing device comprising a control unit, The control unit, The system acquires a set of driving routes, including multiple routes from the starting point to the destination, and the vehicle type. Obtain weather and date / time information corresponding to each driving route. By referring to a memory unit that stores electricity consumption associated with vehicle type, driving route, weather, and date / time information, the electricity consumption for each driving route is identified based on the acquired vehicle type, driving route group, weather, and date / time information. Based on the identified energy consumption, the required amount of electricity for each driving route is derived. After the start of travel along the aforementioned route, the vehicle's location information, battery level, and distance traveled corresponding to the aforementioned route are acquired at predetermined time intervals. Based on the acquired location information, it is determined whether or not the predetermined update conditions have been met. When the specified update conditions are met, the energy consumption of the aforementioned route is calculated based on the acquired battery level and distance traveled. The calculated energy consumption is used to update the energy consumption in the storage unit, which is stored in association with the vehicle type, driving route, weather, and date and time information. Information processing device.

7. The system acquires a set of driving routes, including multiple routes from the starting point to the destination, and the vehicle type. Obtain weather and date / time information corresponding to each driving route. By referring to a memory unit that stores electricity consumption associated with vehicle type, driving route, weather, and date / time information, the electricity consumption for each driving route is identified based on the acquired vehicle type, driving route group, weather, and date / time information. If none of the aforementioned driving routes are stored in the memory unit, the standard energy consumption is determined based on the date and time information. Based on the identified standard energy consumption and each of the aforementioned driving routes, the standard power consumption is derived. Based on the aforementioned weather and date / time information, the power consumption of electrical equipment including air conditioning, lights, and wipers is derived. The total power consumption of the derived standard power consumption and the power consumption of the electrical equipment, and the energy consumption based on each of the aforementioned driving routes, are used to determine the energy consumption. Based on the identified energy consumption, the required amount of electricity for each driving route is derived. An information processing method in which a computer performs the processing.

Images