Information processing device, information processing method, and program

Abstract

This reduces the probability of the vehicle being unable to charge as scheduled, which could disrupt its operation. [Solution] The information processing device 1 includes a storage unit 12 that stores location data indicating the location of a charging facility that can charge the battery of the vehicle V, and drivable distance data indicating the relationship between the remaining power of the battery and the distance that the vehicle V can travel, an acquisition unit 131 that acquires power remaining data indicating the remaining power of the battery, and a planning unit 132 that, by referring to the drivable distance data, identifies the distance that the vehicle V can travel before being charged at the charging facility based on the remaining power data acquired by the acquisition unit 131, and creates a vehicle travel plan that includes information for identifying the charging facility to be charged by the vehicle V and the scheduled date and time of vehicle charging.

Description

Technical Field

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

Background Art

[0002] Conventionally, vehicles that run on power stored in a storage battery are known. Patent Document 1 discloses a technique for instructing a vehicle to move to the nearest charging point when the remaining amount of the storage battery becomes less than a predetermined value.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] When the remaining amount of the storage battery becomes less than a predetermined value and there are circumstances where the vehicle cannot head to a charging point, the storage battery of the vehicle cannot be charged. For example, when there are passengers in the vehicle or the place where the vehicle should go is determined, the vehicle cannot immediately head to the charging point. As a result, there has been a problem that the vehicle may become unable to run.

[0005] Therefore, the present invention has been made in view of these points, and an object thereof is to reduce the probability that a vehicle cannot be charged as scheduled and that travel is hindered.

Means for Solving the Problems

[0006] An information processing device according to a first aspect of the present invention includes: an acquisition unit that acquires power level data indicating the remaining power of a vehicle's battery; and a planning unit that determines the distance the vehicle can travel based on the power level data acquired by the acquisition unit and creates a driving plan for the vehicle that includes information for identifying the charging facility to be charged by the vehicle and the scheduled date and time for charging the vehicle. The planning unit sends a notification regarding charging to the vehicle when there is a predetermined time remaining until the scheduled date and time for charging. The notification is not output as sound if the vehicle is in operation, and the content of the notification is displayed inside the vehicle.

[0007] An information processing device in a second aspect of the present invention includes: an acquisition unit that acquires power level data indicating the remaining power of a vehicle's battery; and a planning unit that determines the distance the vehicle can travel based on the power level data acquired by the acquisition unit, and creates a driving plan for the vehicle that includes information for identifying the charging facility to be charged by the vehicle and the scheduled date and time for charging the vehicle. If the planning unit determines that the vehicle may not be able to reach the location of the charging facility by a predetermined buffer time before the scheduled date and time for charging, it sends a notification regarding charging to the vehicle at the time of the determination. The notification is not output as sound if the vehicle is in operation, and the content of the notification is displayed inside the vehicle.

[0008] A third aspect of the present invention is an information processing method which includes the steps of: obtaining power level data indicating the remaining power of a vehicle's battery, executed by a computer; determining the distance the vehicle can travel based on the power level data, creating a vehicle travel plan which includes information for identifying the charging facility to be charged by the vehicle and the scheduled date and time for charging the vehicle; and sending a notification regarding charging to the vehicle when a predetermined time has passed until the scheduled date and time for charging, wherein the notification is not output as sound when the vehicle is in operation, and the content of the notification is displayed inside the vehicle.

[0009] A fourth aspect of the present invention is an information processing method which includes the steps of: obtaining power level data indicating the remaining power of a vehicle's battery, executed by a computer; determining the distance the vehicle can travel based on the power level data, and creating a driving plan for the vehicle that includes information for identifying the charging equipment to be charged by the vehicle and the scheduled date and time for charging the vehicle; and, if it is determined that the vehicle may not be able to reach the location of the charging equipment by a predetermined buffer time before the scheduled date and time for charging, sending a notification regarding charging to the vehicle at the time the determination is made, wherein the notification is not output as sound when the vehicle is in operation, and the content of the notification is displayed inside the vehicle.

[0010] A fifth aspect of the present invention is a program that causes a computer to perform the following steps: acquire power level data indicating the remaining power of a vehicle's battery; determine the distance the vehicle can travel based on the power level data, create a driving plan for the vehicle including information for identifying the charging facility to be charged by the vehicle and the scheduled date and time for charging the vehicle; and send a notification regarding charging to the vehicle when there is a predetermined amount of time remaining until the scheduled date and time for charging, wherein the notification is not output as sound when the vehicle is in operation, and the content of the notification is displayed inside the vehicle.

[0011] A program according to a sixth aspect of the present invention is a program that causes a computer to perform the following steps: acquire power level data indicating the remaining power of a vehicle's battery; determine the distance the vehicle can travel based on the power level data, create a driving plan for the vehicle including information for identifying a charging facility to be charged by the vehicle and a scheduled date and time for charging the vehicle; and, if it is determined that the vehicle may not be able to reach the location of the charging facility by a predetermined buffer time before the scheduled date and time for charging, send a notification regarding charging to the vehicle at the time the determination is made, wherein the notification is not output as sound when the vehicle is in operation, and the content of the notification is displayed inside the vehicle. [Effects of the Invention]

[0012] According to the present invention, the probability of a vehicle being unable to charge as scheduled and causing problems with driving can be reduced. [Brief explanation of the drawing]

[0013] [Figure 1] This is a diagram illustrating the overview of the information processing system S. [Figure 2] This figure shows an example of a screen displaying the travel plan shown on vehicle terminal 2. [Figure 3] This is a diagram showing the configuration of the information processing device 1. [Figure 4] This figure shows an example of driving range data. [Figure 5] This diagram shows the screen used by the driver to reserve a charging station. [Figure 6] This is a diagram illustrating the operation of the dispatch management unit 134. [Figure 7] This figure shows an example of the screen displayed on the vehicle terminal 2 as the scheduled charging date approaches. [Figure 8] This flowchart shows the process flow when the information processing device 1 creates a travel plan. [Figure 9] This flowchart shows the processing flow when the information processing device 1 acquires dispatch request data. [Modes for carrying out the invention]

[0014] [Overview of Information Processing System S] Figure 1 is a diagram illustrating the overview of the information processing system S. The information processing system S is a system that enables the driver of a vehicle V, which runs using electricity stored in a battery, to know when it is time to recharge the battery of vehicle V. Vehicle V is an electric vehicle that carries passengers, such as a taxi or bus, but it may also be an electric vehicle that is used for the business operations of the operator itself. In the following explanation, we will focus on the case where vehicle V is a taxi.

[0015] The information processing system S includes an information processing device 1, a vehicle terminal 2, a user terminal 3, and a reservation server 4. The vehicle terminal 2 is a terminal provided in the vehicle V. The vehicle terminal 2 is a computer that the driver of the vehicle V can operate and view the displayed information, and is, for example, a tablet or a smartphone. The vehicle terminal 2 transmits and receives data to and from the information processing device 1 via the network N and the wireless communication line W. The network N is, for example, the Internet.

[0016] The user terminal 3 is a terminal used by a user who rides in the vehicle V, and is, for example, a tablet or a smartphone. The user terminal 3 transmits and receives data to and from the information processing device 1 via the network N and the wireless communication line W. When the user inputs the date and time, the scheduled boarding location, and the scheduled alighting location for which the user wants to ride in the vehicle V into the user terminal 3, the user terminal 3 transmits the vehicle allocation request data including the input information to the information processing device 1.

[0017] The information processing device 1 is a device for assisting in creating a driving plan for the vehicle V by an operator who manages the vehicle V, and is, for example, a computer managed by the operator or a server managed by another operator who provides services to the operator. The driving plan is created, for example, on a daily basis and includes the locations and times at which the vehicle V travels during a day.

[0018] When the information processing device 1 receives the vehicle allocation request data from the user terminal 3, it transmits vehicle allocation request data for confirming the availability of vehicle allocation to the vehicle terminals 2 of at least some of the plurality of pre-registered vehicles V. The vehicle terminal 2 displays that it has received the vehicle allocation request data, and when the driver performs an operation to receive the vehicle allocation request, the vehicle terminal 2 transmits vehicle allocation approval data indicating that vehicle allocation is possible to the information processing device 1. When the information processing device 1 receives the vehicle allocation approval data, it determines a vehicle allocation schedule indicating the date and time of vehicle allocation, the scheduled boarding location, and the scheduled alighting location in association with the vehicle V. The information processing device 1 creates, for example, a driving plan for the vehicle V based on the vehicle allocation schedule.

[0019] If vehicle V is an electric vehicle, it needs to be recharged when the remaining power in the battery installed in vehicle V (hereinafter referred to as "power level") becomes low. However, even if the driver realizes that the power level is low and needs to be recharged, they cannot immediately recharge if, for example, they have passengers on board or vehicle V has a destination to go to. Furthermore, it is conceivable that by the time it becomes possible to recharge, there may not be any charging facilities nearby. As a result, problems may arise such as being unable to dispatch a vehicle at the scheduled time, or running out of power and being unable to drive while carrying a user who has requested a ride.

[0020] Therefore, in order to prevent such problems from occurring, the information processing device 1 according to this embodiment is characterized by creating a driving plan that includes information for the driver to know the location of the charging facility where the vehicle V is scheduled to be charged (hereinafter sometimes referred to as the "scheduled charging location") and the scheduled date and time of charging, and providing this driving plan to the driver or manager of the vehicle V.

[0021] As shown in Figure 1, the information processing device 1 transmits and receives data to and from one or more vehicle terminals 2 installed in one or more vehicles V2 via the network N and wireless communication line W. The information processing device 1 creates a charging schedule based on the remaining power of each of the one or more vehicles V, and notifies one or more vehicle terminals 2 of the driving plan, which includes the vehicle dispatch plan and the charging schedule.

[0022] Vehicle terminal 2 displays the driving plan received via network N and wireless communication line W. By displaying the driving plan, including the charging schedule, vehicle terminal 2 enables the driver of vehicle V to realize that the time to charge is approaching, even if they are not aware of the timing of charging, and to move to a location with charging facilities (e.g., taxi office, commercial facility A, commercial facility B) to charge. Since the driving plan is created taking into account the dispatch schedule, the driver can move to the charging facility based on such a driving plan, thus avoiding situations where the vehicle V must be charged while carrying passengers.

[0023] The triangles (△) shown in Figure 1, representing the taxi office, commercial facility A, and commercial facility B, indicate charging facilities. Reservation information for these charging facilities is managed by the reservation server 4. The reservation information associates the identification information of the charging facility, the reservation date and time, and the identification information of the vehicle V to be charged (hereinafter referred to as the "reserved vehicle"). The information processing device 1 may reserve a charging facility by transmitting the reservation information to the reservation server 4 based on the created charging schedule.

[0024] The charging equipment is configured to charge the reserved vehicle at the reserved date and time. For example, the charging equipment obtains identification information of vehicle V when it is connected to the vehicle V with a charging cable, and starts charging vehicle V if the obtained identification information matches the identification information included in the reservation information. The charging equipment may perform such authentication by obtaining the identification information of vehicle V via short-range wireless communication, or by using the driver's IC card. If, as a result of authentication, the charging equipment determines that vehicle V is a vehicle that has a specific contract in place, it may charge the vehicle at a lower rate than the normal rate.

[0025] Figure 2 shows an example of a screen displaying a travel plan shown on the vehicle terminal 2. The screen shown in Figure 2 includes the schedule for actual travel with passengers and the schedule for charging. In the charging schedule, "rapid" indicates that rapid charging is planned, and "normal" indicates that normal charging, which takes longer than rapid charging, is planned. By having the information processing device 1 create such a travel plan and the vehicle terminal 2 display the travel plan, it is possible to prevent the vehicle V from running out of power at the time it should be traveling with passengers. In the following explanation, the reserved section of actual travel may be referred to as the reserved travel section.

[0026] Although the driving plan shown in Figure 2 also shows the actual vehicle schedule, the vehicle terminal 2 may display a screen showing only the charging schedule. The configuration and operation of the information processing device 1, and examples of screen transitions for the driving plan displayed by the vehicle terminal 2, will be described in detail below.

[0027] [Configuration of Information Processing Device 1] Figure 3 shows the configuration of the information processing device 1. The information processing device 1 includes a communication unit 11, a storage unit 12, and a control unit 13. The control unit 13 includes an acquisition unit 131, a plan creation unit 132, a reservation unit 133, and a dispatch management unit 134.

[0028] The communication unit 11 includes a communication interface for the information processing device 1 to send and receive data with the vehicle terminal 2 or the user terminal 3. The communication unit 11 inputs data indicating the remaining power level of the vehicle V, received from the vehicle V, into the acquisition unit 131. The communication unit 11 also transmits data indicating the driving plan created by the planning unit 132 to the vehicle terminal 2.

[0029] The communication unit 11 inputs the dispatch request data received from the user terminal 3 into the dispatch management unit 134, and transmits the dispatch request data received from the dispatch management unit 134 to the vehicle terminal 2. The communication unit 11 inputs the dispatch acceptance data received from the vehicle terminal 2 into the dispatch management unit 134 according to the dispatch request data. Furthermore, the communication unit 11 transmits the reservation data for charging equipment received from the reservation unit 133 to the reservation server 4 which manages the charging equipment.

[0030] The memory unit 12 has storage media such as ROM (Read Only Memory), RAM (Random Access Memory), and SSD (Solid State Drive). The memory unit 12 stores the programs executed by the control unit 13. The memory unit 12 stores the travel plan created by the planning unit 132, associating it with the identification information of the vehicle V. The memory unit 12 also stores various data used by the planning unit 132 to create the travel plan.

[0031] The memory unit 12 stores, for example, the locations of charging equipment that can charge the battery of vehicle V. Specifically, the memory unit 12 stores the name of the facility where the charging equipment is installed and the address or latitude and longitude of the facility. The memory unit 12 may further store the type and number of charging equipment installed at each facility.

[0032] Furthermore, the storage unit 12 stores drivable distance data that shows the relationship between the remaining power of the vehicle V's battery and the distance the vehicle V can travel. The storage unit 12 may store the drivable distance data in association with the identification information of the vehicle V, or it may store the drivable distance data in association with the type of vehicle V. The storage unit 12 may also store drivable distance data for each combination of the type of vehicle V and the specifications of the battery installed in the vehicle V.

[0033] Figure 4 shows an example of driving range data. In the driving range data shown in Figure 4, the horizontal axis shows the remaining power, and the vertical axis shows the driving range. The remaining power is shown as a percentage of the power when fully charged. In the example shown in Figure 4, it is assumed that vehicle V can travel 1 km with power equivalent to 1%.

[0034] The memory unit 12 may store the vehicle V's past driving history. The driving history associates the date and time with the vehicle V's driving route. The driving history may also include the date and time and location where passengers boarded the vehicle V, and the date and time and location where passengers alighted. The memory unit 12 may also store the vehicle V's past charging history. The charging history includes the date and time of charging and the type of charging (fast charging or normal charging).

[0035] The storage unit 12 may store at least one reserved travel section that vehicle V is to travel. Specifically, when the communication unit 11 receives dispatch request data from user terminal 3 and receives dispatch acceptance data from vehicle terminal 2 of vehicle V that has sent distribution request data, the storage unit 12 stores dispatch schedule data indicating the reserved travel section from the planned boarding location to the planned alighting location, associated with the date and time of dispatch indicated by the distribution request data.

[0036] The control unit 13 includes, for example, a CPU (Central Processing Unit). The control unit 13 functions as an acquisition unit 131, a planning unit 132, a reservation unit 133, and a dispatch management unit 134 by executing a program stored in the storage unit 12.

[0037] The acquisition unit 131 acquires power level data indicating the remaining power of the vehicle V's battery. The acquisition unit 131 may, for example, periodically acquire power level data from the vehicle V, but it may also acquire power level data from an external device that stores the power level data acquired from the vehicle V. The acquisition unit 131 may, for example, acquire power level data before the driver of the vehicle V starts their workday. The acquisition unit 131 notifies the planning unit 132 of the acquired power level data.

[0038] The acquisition unit 131 may acquire location data indicating the current position of vehicle V, data indicating the occupancy status, and travel history data indicating at least the mileage traveled. The data indicating the occupancy status is data indicating whether vehicle V is empty, occupied with passengers, or out of service. The acquisition unit 131 notifies the plan creation unit 132 of this data.

[0039] Furthermore, the acquisition unit 131 may acquire instructions for creating a driving plan from an external device. The external device may be, for example, a computer used by the vehicle V's administrator, but it may also be the vehicle terminal 2.

[0040] The planning unit 132 creates a driving plan for vehicle V. The planning unit 132 refers to the driving distance data stored in the storage unit 12 and identifies the distance that vehicle V can travel before charging, based on the remaining power data acquired by the acquisition unit 131. The planning unit 132 then creates a driving plan for vehicle V that includes information to identify the charging facility to which vehicle V will be charged and the scheduled date and time for vehicle V to be charged. The information to identify the charging facility includes at least one of the following: the name of the facility where the charging facility is installed, the address of the location where the charging facility is installed, and a number or text unique to the charging facility.

[0041] The planning unit 132 transmits the created travel plan to the vehicle terminal 2 via the communication unit 11, or displays it on a display or computer connected to the information processing device 1. In other words, the planning unit 132 allows the driver or manager of vehicle V to confirm the travel plan by viewing a screen like the one shown in Figure 2. The planning unit 132 may also notify the reservation unit 133 and the dispatch management unit 134 of the travel plan.

[0042] The planning unit 132 may create a travel plan based on the results of predicting the remaining power at each point in time by predicting the distance traveled by the vehicle V within a predetermined period. For example, the planning unit 132 predicts the distance that the vehicle V will travel within a predetermined period based on the dispatch schedule or past travel history, and predicts the remaining power at each point in time.

[0043] If the reserved travel sections for vehicle V are stored in the memory unit 12, the planning unit 132 creates a travel plan that includes the reserved travel sections stored in the memory unit 12. In the example shown in Figure 2, a travel plan is created that includes the reserved travel section from company J to company K starting at 10:30 and the reserved travel section from company L to company M starting at 13:30.

[0044] The planning unit 132 creates a driving plan that includes scheduled charging dates and times for periods other than when the vehicle is driving in the reserved driving section, so that the vehicle V can continue driving in the reserved driving section. Furthermore, if it is anticipated that the remaining power will be insufficient before driving in the reserved driving section, the planning unit 132 creates a driving plan that includes scheduled charging dates and times determined so that when driving in the reserved driving section begins, the battery will have enough power remaining to allow the vehicle to travel in the reserved driving section. For example, the planning unit 132 creates a driving plan in which the scheduled charging dates and times are set before driving in the reserved driving section begins.

[0045] The planning unit 132 first refers to the drivable distance data stored in the storage unit 12 to determine the distance that vehicle V can travel before charging at the charging facility, based on the remaining power status indicated by the remaining power data acquired by the acquisition unit 131, in order to create a driving plan that includes the scheduled charging date and time. The planning unit 132 then compares the determined drivable distance with the distance of the reserved driving section to determine whether vehicle V can travel the reserved driving section without charging before the start of driving in the reserved driving section.

[0046] If the specified drivable distance is shorter than the distance of the reserved driving section, the planning unit 132 determines that the vehicle V will not be able to travel in the reserved driving section unless it is charged before the start of travel in the reserved driving section, and sets a scheduled charging date and time in the time period before the start of travel in the reserved driving section. If the planning unit 132 determines that the specified drivable distance is greater than or equal to the distance of the reserved driving section, and that the vehicle V can travel in the reserved driving section without charging before the start of travel in the reserved driving section, it does not need to set a scheduled charging date and time in the time period before the start of travel in the reserved driving section.

[0047] However, even if the reserved driving section is completed, if the vehicle V cannot move from the point where the reserved driving section ends to a location with charging facilities, the vehicle V will become inoperable. Therefore, if the specified drivable distance is shorter than the sum of the distance of the reserved driving section and the distance from the point where the reserved driving section ends to a location with charging facilities, the planning unit 132 may set the scheduled charging date and time in the time period before the start of driving in the reserved driving section.

[0048] Furthermore, it is conceivable that before the scheduled start of the reserved travel section, vehicle V may move to the starting point of the reserved travel section, or travel through other sections before the scheduled start time. Even if the available travel distance is greater than the distance of the reserved travel section, if the power consumed by traveling through these other sections is large, there is a risk of insufficient power while traveling through the reserved travel section.

[0049] Therefore, the planning unit 132 may use the results of predicting the cumulative distance traveled during the time period before the start of travel in the reserved travel section, based on the travel history of the vehicle V for which the travel plan is to be created, to determine whether or not to set a scheduled charging date and time in the time period before the start of travel in the reserved travel section. In other words, the planning unit 132 may predict the cumulative distance traveled at each of several times on the target day for which the travel plan is to be created, based on the travel history, and create a travel plan that includes a scheduled charging date and time determined based on the predicted cumulative distance traveled and the remaining travel distance indicated by the remaining travel distance data. The planning unit 132 may also predict the cumulative distance traveled using statistical values ​​of the travel history of multiple vehicles V different from the vehicle V for which the travel plan is to be created.

[0050] Specifically, the planning unit 132 sets the scheduled charging date and time in the time period before the start of driving in the reserved driving section if the distance that can be traveled to reach the charging equipment is shorter than the sum of the predicted cumulative driving distance and the distance of the reserved driving section. The planning unit 132 may also set the scheduled charging date and time in the time period before the start of driving in the reserved driving section if the distance that can be traveled to reach the charging equipment is shorter than the sum of the predicted cumulative driving distance, the distance of the reserved driving section, and the distance from the end of the reserved driving section to the location of the charging equipment. In this way, by creating a driving plan in which the planning unit 132 sets the scheduled charging date and time while also considering the driving distance before and after the reserved driving section, it is possible to prevent situations in which the vehicle V cannot travel.

[0051] The planning unit 132 may send a charging notification to the vehicle terminal 2 of the vehicle V when a predetermined time has elapsed until the scheduled charging date and time. The predetermined time is, for example, 30 minutes. The charging notification indicates the location of the charging equipment and the time when charging should begin. When the vehicle terminal 2 receives the notification, it displays the contents of the notification on its display or outputs it as an audible signal. By being aware of such a notification, the driver can begin moving to arrive at the facility with the charging equipment where charging is scheduled to take place by the scheduled charging date and time. However, if the driver is actually in the vehicle, the audible notification may be disruptive to passengers. Therefore, if the vehicle terminal 2 is in the vehicle, it may not output the notification as an audible signal, but only display the contents of the notification.

[0052] Furthermore, if the planning unit 132 sends the notification too late, even if the driver understands the content of the notification and starts moving towards the charging equipment, they may not be able to arrive at the charging equipment by the scheduled charging date and time. Therefore, if the planning unit 132 determines, for example, that there is a possibility that vehicle V may not be able to arrive at the location of the charging equipment by a predetermined buffer time (e.g., 15 minutes) before the scheduled charging date and time, it may send a notification regarding charging at that time, even if it is before the predetermined time until the scheduled charging date and time.

[0053] Specifically, the planning unit 132 first calculates the time required for vehicle V to travel from its current location to a facility with charging equipment. If the planning unit 132 determines that the calculated time is longer than the time from the current time to 15 minutes before the scheduled charging date and time, it sends a charging notification to vehicle terminal 2 of vehicle V. By operating in this manner, the planning unit 132 can reduce the probability that vehicle V will not be able to reach the facility with charging equipment by the scheduled charging date and time.

[0054] Incidentally, it is conceivable that the distance traveled and location predicted by the planning unit 132 based on the vehicle V's past travel history when creating a travel plan may differ from the actual distance traveled and location of the vehicle V. Therefore, the planning unit 132 may update the travel plan based on the actual travel history of the vehicle V acquired via the acquisition unit 131. For example, the planning unit 132 updates the travel plan each time the vehicle switches between being occupied and empty. As an example, if the planning unit 132 determines that the vehicle V cannot arrive at the charging facility by the scheduled charging date and time, it updates the travel plan and notifies the vehicle terminal 2 of the updated travel plan. The planning unit 132 may also notify the reservation unit 133 and the dispatch management unit 134 of the updated travel plan.

[0055] If the planning unit 132 determines that the distance traveled by vehicle V, as indicated by its actual driving record, is greater than the predicted distance traveled, which was assumed when creating the driving plan, and that there is a possibility that the vehicle will not be able to travel the planned route, it may update the driving plan to bring forward the scheduled charging date and time. By operating in this manner, the planning unit 132 can reduce the risk of being unable to travel the planned route.

[0056] Conversely, if the planning unit 132 determines that the distance traveled by the vehicle V based on its driving record is less than the predicted distance traveled when creating the driving plan, and that the vehicle can travel the planned route without charging before starting the trip, it may delay the scheduled charging date and time or cancel the charging plan. The planning unit 132 may also cancel the reservation of the charging facility by notifying the reservation unit 133, which will be described later, that the plan has been canceled. By operating in this way, the planning unit 132 can prevent the loss of time caused by the vehicle V having to stop at a charging facility to charge.

[0057] The planning unit 132 may update the travel plan based on the data indicating the passenger status input from the acquisition unit 131, in response to a change in the passenger status from a state where there are passengers in vehicle V to a state where there are no passengers in vehicle V. By operating in this manner, the planning unit 132 can prevent a decrease in the driver's concentration due to the travel plan being updated during actual driving.

[0058] Incidentally, frequent rapid charging can easily degrade the battery. Therefore, in order to reduce the number of rapid charges as much as possible, the planning unit 132 may create a driving plan that includes a plan for normal charging if it determines that sufficient charging time can be secured based on past driving history. If the planning unit 132 determines, based on past charging history stored in the storage unit 12, that the degradation level of the vehicle V's battery is below a predetermined level, it may create a driving plan that uses a lower frequency of rapid charging than when the battery degradation level is above the predetermined level. By creating such a plan, the planning unit 132 can suppress battery degradation.

[0059] The planning unit 132 may determine the scheduled charging date and time based on the price of electricity. The price of electricity fluctuates depending on the balance of supply and demand. In addition, the amount of electricity generated by solar and wind power generation fluctuates depending on the weather. Based on these fluctuating factors, the planning unit 132 may prioritize determining the scheduled charging date and time to a time when the price of electricity is estimated to be below a threshold. If the market price of electricity is published every morning, the planning unit 132 may determine the scheduled charging date and time to a time when the market price is relatively low, in response to the publication of the market price of electricity. Specifically, the planning unit 132 may determine the scheduled charging date and time in response to the acquisition of the market price by the acquisition unit 131. By operating in this manner, the cost required for charging can be reduced.

[0060] The reservation unit 133 makes a reservation for vehicle V to charge at a charging facility where vehicle V is expected to charge at the scheduled charging date and time, based on the driving plan created by the planning unit 132. The reservation unit 133 reserves the charging facility by transmitting reservation information, including the vehicle V's identification information and the scheduled charging date and time, to the reservation server 4 via the communication unit 11. The reservation unit 133 may also make a reservation for vehicle V to charge at a charging facility if it receives a predetermined instruction from the driver of vehicle V who has viewed the driving plan.

[0061] Figure 5 shows the screen used by the driver to reserve a charging station. Figure 5(a) shows the screen displayed on vehicle terminal 2 at 11:50. In Figure 5(a), the rapid charging scheduled for 10:00 has finished and is indicated by a dashed line. In the charging plan shown in Figure 5(a), charging is scheduled to start at 12:30, but if vehicle V is likely to arrive at the charging station earlier than scheduled, the driver may want to start charging earlier.

[0062] When the driver presses the "Book Now" button, the screen transitions to Figure 5(b), and if the "Book Now" button is pressed again, the vehicle terminal 2 sends reservation request data to the information processing device 1.

[0063] When the reservation unit 133 receives reservation request data via the communication unit 11, it reserves a charging facility that is closest to the vehicle V's current location at the time the reservation request data was received and that is available for reservation. Once the reservation is complete, the reservation unit 133 sends reservation completion data to the vehicle terminal 2, including the name of the facility where the charging facility is installed and the reservation time. The reservation unit 133 may also calculate the time when the vehicle V is expected to arrive at the charging facility based on the distance from the vehicle V's current location to the charging facility, and use this calculated time as the reservation time.

[0064] When vehicle terminal 2 receives reservation completion data, it displays a screen indicating that the reservation has been made, as shown in Figure 5(c). If the "Go to charging location" button is pressed on the screen in Figure 5(c), vehicle terminal 2 may display the route from vehicle V's current location to the charging location.

[0065] The reservation unit 133 may change the reservation details if the vehicle is unable to arrive at the reserved charging facility at the reserved time due to an update in the driving plan. For example, if the reservation unit 133 had reserved the charging facility at the scheduled charging date and time indicated in the driving plan before the update, it will change the date and time of the reservation to the scheduled charging date and time indicated in the updated driving plan.

[0066] The dispatch management unit 134 determines which vehicle V to dispatch when it receives dispatch request data from the user terminal 3. Specifically, the dispatch management unit 134 sends a dispatch request to vehicle V based on a dispatch request from a user who wishes to ride in vehicle V (i.e., a user using the user terminal 3). More specifically, when the dispatch management unit 134 receives dispatch request data from the user terminal 3 via the communication unit 11, it sends dispatch request data to the vehicle terminal 2 of vehicle V that can pick up the user in the desired section of the journey, based on the desired date and time of ride indicated by the dispatch request data.

[0067] If the requested date and time for travel is close to or overlaps with the scheduled charging date and time for vehicle V, and vehicle V is dispatched at that time, vehicle V may not be able to charge as scheduled, which could cause problems with its operation. Therefore, the dispatch management unit 134 sends dispatch request data to vehicle V on the condition that the period of travel for the requested section of travel does not overlap with the scheduled charging date and time for vehicle V.

[0068] For example, the dispatch management unit 134 sends dispatch request data to vehicle V on the condition that the desired ride section indicated by the dispatch request data is between the current location of vehicle V and the charging facility where vehicle V is scheduled to charge, as indicated by the travel plan. The dispatch management unit 134 may also send dispatch request data to vehicle V on the condition that the direction from the boarding location to the alighting location matches the direction from the current location to the planned charging location.

[0069] Figure 6 is a diagram illustrating the operation of the dispatch management unit 134. Figure 6(a) shows a case where the desired ride section is between the vehicle V's current location and the planned charging location, and the direction from the pick-up location to the drop-off location matches the direction from the current location to the planned charging location. In such a case, even if vehicle V picks up a user in the desired ride section, it is considered that this will not significantly affect the time required to arrive at the planned charging location from the current location. Therefore, the dispatch management unit 134 transmits dispatch request data to vehicle V.

[0070] Figure 6(b) shows a case where the desired ride section lies between the vehicle V's current location and the planned charging location, but the direction from the pick-up location to the drop-off location does not match the direction from the current location to the planned charging location. In such a case, since vehicle V picking up a user in the desired ride section would significantly affect the time required to reach the planned charging location, the dispatch management unit 134 does not send a delivery request data to vehicle V. However, if the dispatch management unit 134 determines that vehicle V will arrive at the planned charging location by the planned charging date and time even if it picks up a user in such a desired ride section, it may send a dispatch request data to vehicle V.

[0071] Figure 6(c) shows a case where the desired ride section is not between the vehicle V's current location and the planned charging location. In such a case, if vehicle V were to pick up the user in the desired ride section, it would significantly affect the time required to arrive from the current location to the planned charging location. Therefore, the dispatch management unit 134 does not send dispatch request data to vehicle V.

[0072] Thus, even if the desired ride section indicated by the dispatch request lies between the current location of vehicle V and the charging facility where vehicle V is scheduled to charge as indicated by the travel plan, the dispatch management unit 134 may choose not to send the dispatch request data to vehicle V if the time required from the current location to the charging facility by vehicle V traveling along the desired ride section would exceed a predetermined time. The predetermined time is, for example, 10% of the time required from the current location to the charging facility.

[0073] The specified time may be the difference between the time when vehicle V is expected to arrive at the charging location and the scheduled charging date and time. In other words, if the dispatch management unit 134 anticipates that vehicle V will be delayed by more than a margin of error by picking up a user in the desired travel section, it will not send dispatch request data to vehicle V. By operating in this manner, the dispatch management unit 134 can prevent vehicle V from missing the scheduled charging date and time.

[0074] However, there are times when a driver may want to prioritize picking up passengers over arriving at the scheduled charging location by the scheduled charging date and time. In such cases, if the dispatch management unit 134 receives notification from the vehicle terminal 2 that the driver wishes to request a dispatch based on the driver's actions, it may send the dispatch request data to the vehicle terminal 2 even if the desired pick-up section indicated by the dispatch request data is not between the current location of vehicle V and the charging facility where vehicle V is scheduled to charge as indicated by the travel plan.

[0075] Figure 7 shows an example of the screen displayed on the vehicle terminal 2 as the scheduled charging date approaches. As shown in Figure 7(a), the vehicle terminal 2 displays a screen indicating that the scheduled charging date is approaching. On this screen, when the driver presses the "Proceed to charging location" button, as shown in Figure 7(b), the vehicle terminal 2 displays a map showing the route from the current location to the scheduled charging location. On this screen, the vehicle terminal 2 displays a "Resume dispatch request" button to set the vehicle dispatch request to resume. When the driver presses the "Resume dispatch request" button, the vehicle terminal 2 sends dispatch request notification data to the information processing device 1. When the dispatch management unit 134 receives the dispatch request notification data, it sends dispatch request data to the vehicle terminal 2, even if the scheduled charging date is approaching.

[0076] [Processing flow in information processing device 1] Figure 8 is a flowchart showing the process flow of the information processing device 1 creating a travel plan. The flowchart shown in Figure 8 starts from the point when the information processing device 1 receives an instruction from an external device to create a travel plan. The information processing device 1 may also start the process shown in the flowchart in Figure 8 from a predetermined time before the vehicle V starts traveling, regardless of the instruction from the external device. Furthermore, the information processing device 1 may repeat the process shown in the flowchart in Figure 8 after the vehicle V has started traveling.

[0077] The acquisition unit 131 selects the vehicle V for which a travel plan is to be created and acquires the remaining power data of the selected vehicle V (S11). Next, the plan creation unit 132 refers to the drivable distance data stored in the storage unit 12 and determines the distance that vehicle V can travel based on the remaining power data (S12). The plan creation unit 132 also refers to the dispatch schedule data stored in the storage unit 12 in association with vehicle V and determines the planned travel section and the time at which the vehicle should travel that section (S13).

[0078] Next, the planning unit 132 determines whether or not vehicle V needs to be charged before traveling the planned travel section, based on the drivable distance identified in S12 and the content of the planned travel section identified in S13 (S14). Specifically, the planning unit 132 calculates the distance that vehicle V is expected to travel in the time from when it starts driving until it starts traveling the planned travel section, based on, for example, the vehicle V's past driving history. The planning unit 132 determines whether or not vehicle V needs to be charged before traveling the planned travel section, based on whether or not the drivable distance after subtracting the calculated distance from the drivable distance identified in S12 is longer than the distance of the planned travel section.

[0079] If the planning unit 132 determines that the drivable distance is shorter than the distance of the planned driving section, or the distance of the planned driving section plus a predetermined margin, and that the vehicle V cannot complete the planned driving section, it sets the scheduled charging date and time before the planned driving section (S15). If the planning unit 132 determines that the drivable distance is greater than or equal to the distance of the planned driving section, or greater than or equal to the distance of the planned driving section plus a predetermined margin, and that the vehicle V can complete the planned driving section, it sets the scheduled charging date and time after the planned driving section (S16).

[0080] Next, the reservation unit 133 determines whether the probability of the driver charging at the scheduled charging date and time is higher than a threshold (S17). For example, the reservation unit 133 calculates a higher probability the shorter the drivable distance at the time the scheduled driving section begins. As an example, the reservation unit 133 sets the probability to 100% if the drivable distance at the time the scheduled driving section begins is zero, and sets the probability to 70% if the drivable distance at the time the scheduled driving section begins is the same as the distance of the scheduled driving section.

[0081] If the reservation unit 133 determines that the probability is above a threshold (for example, 70% or higher) (YES in S17), it reserves a charging facility within a predetermined range from the location where vehicle V is predicted to be before starting to travel the planned section (S18). If the reservation unit 133 determines that the probability is below the threshold (NO in S17), it does not reserve a charging facility.

[0082] The control unit 13 determines whether or not it is necessary to create a travel plan for another vehicle V (S19). If it is necessary to create a travel plan for another vehicle V (YES in S19), the control unit 13 repeats the processes from S11 to S19. If it is not necessary to create a travel plan for another vehicle V (NO in S19), the control unit 13 terminates the process of creating a travel plan.

[0083] Figure 9 is a flowchart showing the processing flow when the information processing device 1 acquires dispatch request data. When the dispatch management unit 134 acquires the dispatch request data (S21), it selects one vehicle V from a plurality of pre-registered vehicles V (S22). The dispatch management unit 134 refers to the travel plan stored in the storage unit 12 in association with the vehicle V and determines whether the vehicle V is scheduled to be charged within a first predetermined time before the desired boarding time indicated by the dispatch request data, and within a second predetermined time after the desired boarding time (S23).

[0084] The first predetermined time is the sum of the time required for charging and the time required to travel from the charging location to the desired pick-up location, for example, 60 minutes. The second predetermined time is the sum of the travel time from the desired pick-up location to the desired drop-off location and the time required to travel from the desired drop-off location to the charging facility.

[0085] If the dispatch management unit 134 determines that vehicle V is scheduled to be charged (YES in S23), it determines whether the desired ride section indicated by the dispatch request data is on the way to the charging facility for vehicle V (S24). If the ride section is on the way to the charging facility for vehicle V (YES in S24), the dispatch management unit 134 determines whether it can pick up passengers in the ride section and still make it in time for the charging facility's reservation (S25). If the dispatch management unit 134 determines that it can make it in time for the reservation, it sends the dispatch request data to vehicle V (S26). When the dispatch management unit 134 receives dispatch acceptance data from vehicle V (YES in S27), it terminates the dispatch process.

[0086] If the dispatch management unit 134 determines in S23 that there is no scheduled charging (NO in S23), it sends dispatch request data to vehicle V. If the dispatch management unit 134 determines NO in S24, S25, and S27, it returns to S22, selects another vehicle V, and repeats the process from S23 to S27.

[0087] [Effects of Information Processing Device 1] As described above, the information processing device 1 according to this embodiment refers to drivable distance data that shows the relationship between the remaining power of the battery installed in the vehicle V and the distance the vehicle V can travel, and identifies the distance the vehicle V can travel before being charged at a charging facility. Based on this, it creates a driving plan that includes the location of the charging facility where the vehicle V will be charged and the scheduled date and time for charging the vehicle V. By having the information processing device 1 create such a driving plan and the driver being aware of the driving plan, the driver can charge the vehicle V at the appropriate time. As a result, the probability of the vehicle V becoming unable to travel can be reduced.

[0088] Although the present invention has been described above using embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments, and various modifications and changes are possible within the scope of its gist. For example, all or part of the apparatus can be configured by functionally or physically distributing and integrating them in any unit. Specifically, the information processing device 1 may not have a reservation unit 133 and a dispatch management unit 134, while other devices may have a reservation unit 133 and a dispatch management unit 134, and the information processing device 1 may operate in cooperation with other devices. Furthermore, new embodiments resulting from any combination of multiple embodiments are also included in the embodiments of the present invention. The effects of the new embodiments resulting from the combinations will also have the effects of the original embodiments. [Explanation of Symbols]

[0089] 1. Information Processing Device 2 Vehicle terminals 3. User terminals 4. Reservation Server 11 Communications Department 12 Storage section 13 Control Unit 131 Acquisition Department 132 Planning Department 133 Reservation Department 134 Dispatch Management Department

Claims

1. An acquisition unit that acquires power level data indicating the remaining power level of the vehicle's battery, A planning unit identifies the distance the vehicle can travel based on the remaining power data acquired by the acquisition unit, and creates a driving plan for the vehicle that includes information for identifying the charging equipment to be used by the vehicle and the scheduled date and time for charging the vehicle. It has, The planning unit sends a notification regarding charging to the vehicle when a predetermined time has passed until the scheduled charging date and time. The aforementioned notification will not be output audibly if the vehicle is in use, and the content of the notification will be displayed inside the vehicle. Information processing device.

2. An acquisition unit that acquires power level data indicating the remaining power level of the vehicle's battery, A planning unit identifies the distance the vehicle can travel based on the remaining power data acquired by the acquisition unit, and creates a driving plan for the vehicle that includes information for identifying the charging equipment to be used by the vehicle and the scheduled date and time for charging the vehicle. It has, If the planning unit determines that there is a possibility that the vehicle may not be able to reach the location of the charging equipment by a predetermined buffer time before the scheduled charging date and time, it sends a notification regarding charging to the vehicle at the time the determination is made. The aforementioned notification will not be output audibly if the vehicle is in use, and the content of the notification will be displayed inside the vehicle. Information processing device.

3. A computer executes Steps include obtaining power level data that indicates the remaining power level of the vehicle's battery, The steps include: determining the distance the vehicle can travel based on the remaining power data, creating a driving plan for the vehicle that includes information for identifying the charging facility to be used by the vehicle and the scheduled date and time for charging the vehicle; The steps include sending a notification regarding charging to the vehicle when a predetermined time has passed until the scheduled charging date and time, It has, The aforementioned notification will not be output audibly if the vehicle is in use, and the content of the notification will be displayed inside the vehicle. Information processing methods.

4. A computer executes Steps include obtaining power level data that indicates the remaining power level of the vehicle's battery, The steps include: determining the distance the vehicle can travel based on the remaining power data, creating a driving plan for the vehicle that includes information for identifying the charging facility to be used by the vehicle and the scheduled date and time for charging the vehicle; If it is determined that the vehicle may not be able to reach the location of the charging equipment by a predetermined buffer time before the scheduled charging date and time, the step of sending a charging notification to the vehicle at the time the determination is made, It has, The aforementioned notification will not be output audibly if the vehicle is in use, and the content of the notification will be displayed inside the vehicle. Information processing methods.

5. On the computer, Steps include obtaining power level data that indicates the remaining power level of the vehicle's battery, The steps include: determining the distance the vehicle can travel based on the remaining power data, creating a driving plan for the vehicle that includes information for identifying the charging facility to be used by the vehicle and the scheduled date and time for charging the vehicle; The steps include sending a notification regarding charging to the vehicle when a predetermined time has passed until the scheduled charging date and time, A program to execute, The aforementioned notification will not be output audibly if the vehicle is in use, and the content of the notification will be displayed inside the vehicle. program.

6. On the computer, Steps include obtaining power level data that indicates the remaining power level of the vehicle's battery, The steps include: determining the distance the vehicle can travel based on the remaining power data, creating a driving plan for the vehicle that includes information for identifying the charging facility to be used by the vehicle and the scheduled date and time for charging the vehicle; If it is determined that the vehicle may not be able to reach the location of the charging equipment by a predetermined buffer time before the scheduled charging date and time, the step of sending a charging notification to the vehicle at the time the determination is made, A program to execute, The aforementioned notification will not be output audibly if the vehicle is in use, and the content of the notification will be displayed inside the vehicle. program.

Images