Information processing apparatus and operation system

By generating an operation plan for electric vehicles, ensuring that the time schedule during the charging period is before or after the prohibited period, the problem of difficulty in ensuring driver rest time and reduced operation efficiency of electric vehicles in the prior art is solved, and the effect of effective operation within the prescribed period is achieved.

CN119809470APending Publication Date: 2025-04-11TOYOTA JIDOSHA KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202411035341.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-10-10
Filing Date
2024-07-31
Publication Date
2025-04-11

AI Technical Summary

Technical Problem

The prior art is difficult to ensure drivers' rest time while optimizing vehicle loading rates, and the charging demand of electric vehicles may lead to reduced operating efficiency.

Method used

The operation plan of the electric vehicle is generated by the information processing device, the routes containing multiple target locations and target charging places are searched, and run separately before and after the prohibited period, ensuring that the charging period begins before and after the prohibited period, and ends after or after.

Benefits of technology

It effectively suppresses the reduction in operating efficiency of electric vehicles and prohibits the operation of electric vehicles within the specified time period to ensure that the driver can reliably obtain rest time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119809470A_ABST
    Figure CN119809470A_ABST
Patent Text Reader

Abstract

The invention provides an information processing apparatus and an operation system. The information processing apparatus performs: a process of searching for a route including a plurality of target locations and a target charging location; and generating the operation plan such that the electric vehicle operates according to the route during a first operation period before the prohibition time period and during a second operation period after the prohibition time period. Operation of the electric vehicle is prohibited during the prohibition time period. For the operation plan, the information processing apparatus sets a charging period during which the electric vehicle is charged at the target charging site such that a start time of the charging period is before the prohibition period and an end time of the charging period is within the prohibition period or after the prohibition period.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to an information processing device and an operating system. Background Art

[0002] Japanese Patent Application Laid-Open No. 2004-131270 discloses a method of generating a delivery plan for each transportation company in a central device. Summary of the invention

[0003] In the method described in Japanese Patent Application Laid-Open No. 2004-131270, a delivery plan is generated in such a way as to improve the vehicle loading rate based on past operation performance. However, if only the vehicle loading rate is pursued, it may not be possible to fully ensure the driver's rest time. In addition, for example, in a system in which delivery is performed by an electric vehicle such as a battery electric vehicle, the electric vehicle may need to be charged during the delivery plan.

[0004] In order to ensure that the driver of an electric vehicle can reliably take a rest time, it is considered that the driver is obliged to take a rest in a specified time period (rest time period). However, if the driver arbitrarily determines the resting place and charging period, idle time (a period during which no work is actually performed) is likely to occur before the rest time period. The generation of such idle time leads to a decrease in operating efficiency.

[0005] The present disclosure has been made to solve the above-mentioned problems, and an object of the present disclosure is to suppress a decrease in the operating efficiency of an electric vehicle and prohibit the operation of the electric vehicle in a predetermined time period.

[0006] According to one aspect of the present disclosure, there is provided an information processing device that generates an operation plan for an electric vehicle. The electric vehicle is configured to be able to travel using electric power stored in the electric vehicle.

[0007] The information processing device is configured to perform the following processing: searching for a route including multiple target locations and target charging locations; and generating an operation plan in which the electric vehicle operates along the above route during a first operation period set before a prohibited time period and a second operation period set after the prohibited time period. The operation of the electric vehicle is prohibited during the prohibition time period. For the operation plan, the information processing device sets a charging period for charging the electric vehicle at the target charging site so that the start time of the charging period is before the prohibited time period and the end time of the charging period is within or after the prohibited time period.

[0008] According to the present disclosure, it is possible to suppress a decrease in the operating efficiency of an electric vehicle while prohibiting the electric vehicle from operating within a prescribed time period. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the accompanying drawings, in which like numerals represent like parts, and in which:

[0010] Figure 1 This is a diagram for explaining the configuration of the operating system involved in the first embodiment;

[0011] Figure 2 is a flowchart showing a method for generating an operation plan according to Embodiment 1;

[0012] Figure 3 is a diagram for explaining the operation plan generated in Implementation Method 1;

[0013] Figure 4 is a flowchart showing a method for generating an operation plan according to Embodiment 2;

[0014] Figure 5 is a flowchart showing display control in implementation mode 2;

[0015] Figure 6 This is a diagram showing a screen displayed in the display control according to the second embodiment. DETAILED DESCRIPTION

[0016] The embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and their description will not be repeated.

[0017] Implementation Method 1

[0018] Figure 1 1 is a diagram for explaining the configuration of an operation system according to this embodiment. Figure 1 The operating system includes a vehicle 10, electric vehicle supply equipment (EVSE) 20, and a server 30. The server 30 corresponds to an example of an “information processing device” in the present disclosure.

[0019] The vehicle 10 includes a power storage device 11, a battery management system (BMS) 11a, an inlet 12, a charger 13, a human machine interface (HMI) 14, an electronic control unit (ECU) 15, and a communication device 18. The vehicle 10 is, for example, a battery electric vehicle that can travel using the power of the power storage device 11.

[0020] The power storage device 11 includes a secondary battery (e.g., a lithium-ion secondary battery). A plurality of secondary batteries may form a battery pack. The power storage device 11 may also include an electric double layer capacitor instead of a secondary battery. The BMS 11a detects the state of the power storage device 11 (e.g., temperature, current, voltage, and SOC), and outputs the detection result to the ECU 15. The state of charge (SOC: state of charge) indicates the ratio of the current storage amount to the storage amount in the fully charged state.

[0021] The vehicle 10 is configured to perform external charging (charging based on power from outside the vehicle). Specifically, the vehicle 10 is configured to be able to charge the power storage device 11 using power supplied from the EVSE 20. The EVSE 20 includes a main body electrically connected to the power system PG and a charging cable 21 extending from the main body toward the outside. The power system PG is a power grid constructed by power transmission and distribution equipment. The socket 12 of the vehicle 10 is configured to be able to load and unload the connector 22 (front end) of the charging cable 21. When the connector 22 of the charging cable 21 is connected to the socket 12 of the vehicle 10 in the parked state (inserted state), the vehicle 10 receives power supply from the EVSE 20. On the other hand, when the socket 12 is not connected (unplugged state), the vehicle 10 does not receive power supply from the EVSE 20. The vehicle 10 also includes a connection detection circuit (not shown) that detects the state of the socket 12 (plugged state / unplugged state).

[0022] In external charging, power supplied from power system PG is input to socket 12 via EVSE 20 . Charger 13 generates charging power according to an instruction from ECU 15 using the power supplied from socket 12 , and inputs the generated charging power to power storage device 11 . Charger 13 is controlled by ECU 15 .

[0023] HMI14 includes an input device that outputs information input from the user to ECU15 and an output device (notification device) that outputs information to the user according to instructions from ECU15. As an example of the input device, in addition to buttons or keypads, an intelligent speaker that accepts voice input can also be cited. As an example of the output device, a display device and a speaker can be cited.

[0024] The ECU 15 includes a processor 151 and a storage device 152 . The communication device 18 includes a communication I / F (interface) for wireless communication. The ECU 15 is configured to communicate with the server 30 via the communication device 18 .

[0025] The server 30 includes a processor 31 and a storage device 32. The storage device 32 stores area information related to a plurality of areas registered in the server 30 and vehicle information related to a plurality of vehicles registered in the server 30. In this embodiment, electric vehicles used for delivery are registered in the server 30. Each vehicle may also have Figure 1 The vehicle 10 shown in the figure has the same structure. In addition, a delivery truck (electric vehicle) may be registered in the server 30.

[0026] The storage device 32 uses the vehicle identification information (vehicle ID) to distinguish and store the vehicle information of each vehicle. Regarding the corresponding vehicle, the vehicle information includes vehicle model information, specification information, location information, status information, information for identifying the driver, and information indicating the prohibited time period during which the operation of the vehicle is prohibited. The specification information includes the capacity and charging performance of the power storage device mounted on the vehicle and the power consumption of the vehicle. The status information is, for example, the stored power. The information used to identify the driver is, for example, the driver's name and contact information. In this embodiment, the prohibited time period is the statutory rest time period common to all vehicles registered with the server 30. The statutory rest time period is a time period during which the operation of the vehicle is prohibited in order to give the driver the rest time required by law. However, it is not limited to this, and different prohibited time periods can also be set for each vehicle (each driver).

[0027] The storage device 32 uses the identification information of the area (area ID) to distinguish and store area information divided by area. Regarding the corresponding area, the area information includes division information indicating the scope of the area, charging position information for determining the position of the charging point set for the area, and information indicating the specifications of the EVSE installed at the charging point. The information indicating the specifications of the EVSE is, for example, information indicating power supply performance such as rated power supply. The division information can also be cooperated with map information to show the area (area range) corresponding to the corresponding area on the map. The division information can also be registered in an application software with a geo-fencing function. In this embodiment, a charging point is pre-set in each area registered in the server 30. The charging point is located in the corresponding area (the area where the charging point is set). The EVSE installed at each charging point may also have Figure 1 Each EVSE may be an AC power supply device that outputs alternating current power or a DC power supply device that outputs direct current power.

[0028] When receiving a request for delivery to a place (delivery place) belonging to a registered area, the server 30 adds the delivery information related to the requested delivery to the storage device 32. The delivery information is distinguished for each delivery place and added to the area information of the area to which the delivery place belongs. That is, the added delivery information is associated with the area ID of the area to which the delivery place belongs. The delivery information includes, regarding the corresponding delivery place, delivery location information for identifying the delivery place, information related to the goods (delivery target) delivered to the delivery place (e.g., identification information of the goods), information related to the delivery date, and information related to the delivery entruster (e.g., the name and contact information of the delivery entruster).

[0029] Figure 2 This is a flowchart showing the method for generating a delivery plan according to the first embodiment. Figure 2 The processing flow shown is started by the server 30 when the specified plan generation timing is reached. The plan generation timing can also be a time that is a specified time (for example, 1 hour) back from the start time of the operation. For example, for an operation that starts at 8 am, the plan generation timing can also be set to 7 am. Each step in the flowchart is simply marked with "S". Figure 1 An example of a delivery plan for the vehicle 10 shown will be described.

[0030] refer to Figure 2 In S11, the server 30 obtains the position and state of the vehicle 10 (including the SOC of the power storage device 11) through wireless communication with the vehicle 10. In the next S12, the server 30 reads the vehicle information corresponding to the vehicle 10 from the storage device 32, and calculates the drivable distance of the vehicle 10 using the SOC (battery remaining capacity) of the power storage device 11 obtained in S11 and the specifications of the vehicle 10 (for example, power consumption). The power consumption indicates the drivable distance per unit of electricity.

[0031] In the next S13, the server 30 determines a plurality of delivery locations (hereinafter referred to as "target locations") to be delivered by the vehicle 10 today based on the delivery information stored in the storage device 32 and the position of the vehicle 10 obtained in S11. The target location belongs to any one of a plurality of areas registered in the server 30. Hereinafter, an area to which one or more target locations belong is referred to as a "target area". In this embodiment, the server 30 determines a plurality of target locations belonging to different target areas. Then, the server 30 generates a rough delivery plan for delivering to the determined plurality of target locations, and calculates the distance that the vehicle 10 travels when delivering according to the rough delivery plan (hereinafter referred to as "necessary driving distance"). Next, the server 30 determines in S14 whether the necessary driving distance (S13) is longer than the drivable distance (S12).

[0032] If the necessary driving distance is not longer than the possible driving distance (S14: No), the process ends. Figure 2 In this case, the server 30 generates a delivery plan that does not include the charging period through a process flow not shown, and transmits the delivery plan to the vehicle 10. On the other hand, when the required travel distance is longer than the drivable distance (S14: YES), the process proceeds to S15.

[0033] In S15, the server 30 calculates the amount of electricity (necessary charge amount) to be charged to the power storage device 11 of the vehicle 10 during the delivery plan using the vehicle information stored in the storage device 32. Specifically, the server 30 calculates the amount of electricity (necessary charge amount) required for the vehicle 10 to travel the required driving distance based on the average power consumption of the vehicle 10. Furthermore, the server 30 calculates the amount of electricity (retained electricity) retained by the vehicle 10 based on the capacity and SOC of the power storage device 11, and obtains the required charge amount by subtracting the retained electricity from the required electricity.

[0034] Next, in S16, the server 30 determines the order of operation for each of the multiple target areas (S13), and searches for a route in which the vehicle 10 can deliver to all the target locations. In detail, the server 30 searches for a route in which the vehicle 10 moves in the multiple target areas in the above order while completing the delivery in each target area, thereby delivering to all the target locations. In the operation according to such a route, the vehicle 10 moves to the next target area after completing the operation for all the target locations included in one target area. Multiple route plans are generated by the above search. Then, the server 30 extracts n (n: an integer greater than 2) route plans from the obtained multiple route plans. n can be set arbitrarily. The server 30 extracts n route plans in sequence, for example, starting from the side with the shorter time (operation time) to complete all the deliveries. The operation time is equivalent to the time from the start time of the operation to the end time of the operation. The start time of the operation can also be a specified time common to all route plans (for example, 8 o'clock in the morning). The end time of the operation varies according to the route.

[0035] In the next S17, the server 30 calculates the operation time (non-charging operation time) when the vehicle 10 is not charged for each route plan extracted as described above. The server 30 calculates the time (non-charging operation time) required to complete all deliveries according to each route plan, assuming that the vehicle 10 is not short of power.

[0036] In the next S18, the server 30 uses the vehicle information and area information stored in the storage device 32 to determine the charging start time and the target charging location for each route plan. Specifically, the server 30 determines the time when the specified time (hereinafter also referred to as "charging time before operation prohibition") is traced back from the start time of the prohibited time period of the vehicle 10 as the charging start time. The charging time before operation prohibition can be set arbitrarily, for example, more than 1 minute and less than 1 hour. Then, the server 30 refers to the area information and determines the charging point set in the target area where the vehicle 10 is located at the determined charging start time as the target charging location.

[0037] In the next S19, the server 30 corrects each route plan in a manner passing through the target charging place determined in S18, and calculates the operating time added by the correction (i.e., the moving time to the target charging place) for each route plan. In the next S20, the server 30 calculates the time (necessary charging time) taken to charge the vehicle 10 with the required charging amount at the target charging place at the start time of charging for each corrected route plan. Then, the server 30 determines the time when the necessary charging time has passed from the start time of charging as the charging end time. The charging end time is set for each route plan. In this embodiment, since the charging time before the operation is prohibited is short, the charging end time is set within the prohibited time period or after the prohibited time period. Thus, a delivery plan for each route plan is obtained. The delivery plan represents a route including multiple target locations and target charging places, an operation start time, an operation end time, a prohibited time period, and a charging period (charging start time and charging end time).

[0038] In the next S21, the server 30 calculates the working time of the driver of the vehicle 10 in the delivery plan of each route plan based on the operation start time, the operation end time and the prohibited time period. The working time is equivalent to the time obtained by subtracting the prohibited time period (rest time) from the time from the operation start time to the operation end time (working time). In the next S22, the server 30 selects the delivery plan with the shortest working time of the driver from the delivery plans generated for the n route plans as described above. In the case where there are multiple delivery plans with the shortest working time, the server 30 can also select a delivery plan based on the power consumed by the vehicle 10 for delivery (power consumption). The server 30 can also select the delivery plan with the least power consumption.

[0039] Then, the server 30 sends the delivery plan determined as described above to the vehicle 10. When the vehicle 10 receives the delivery plan, the ECU 15 causes the HMI 14 (notification device) to notify the delivery plan. More specifically, the ECU 15 controls the HMI 14 so that the HMI 14 notifies the driver of the vehicle 10 of the delivery plan. By the vehicle 10 performing delivery according to the delivery plan, it is possible to inhibit the operation of the vehicle 10 in the prohibited time period while suppressing the reduction in the operation efficiency of the vehicle 10. Figure 3 This effect will be further described.

[0040] Figure 3 It is used to illustrate the Figure 2 The process shown generates a diagram of the delivery plan. Figure 3 The areas A, B, C, D, E, F, and G shown correspond to the target areas, respectively. EVSE 20A, 20B, 20C, 20D, 20E, 20F, and 20G are installed at charging points set in areas A, B, C, D, E, F, and G, respectively. Figure 3 In the figure, time period T1 indicates the prohibited time period, time t11 indicates the start time of the prohibited time period, and time t12 indicates the end time of the prohibited time period. In addition, time ts indicates the charging start time, and time te indicates the charging end time. That is, the period from time ts to time te is equivalent to the charging period.

[0041] Delivery example Cex is a comparative example. In the comparative example, the driver of the vehicle 10 charges the vehicle 10 at an arbitrary timing and takes a rest at an arbitrary place regardless of the delivery plan. In the delivery plan involved in delivery example Cex, idle time (the period from time tw to time t11) occurs just before the arrival of time period T1. If the driver arbitrarily determines the resting place and charging period, idle time (a period during which substantially no work is performed) is likely to occur. The generation of idle time leads to a decrease in operating efficiency.

[0042] Route plans R1, R2, and R3 are respectively Figure 2 In this example, "n" in S16 is 3. Delivery plans Ex1, Ex2, and Ex3 are delivery plans corresponding to route plans R1, R2, and R3, respectively. Figure 2Then, through the processing of S15~S20 of the following S21 and S22, the delivery plan Ex2 (route plan R2) is selected from the delivery plans Ex1~Ex3 (route plans R1~R3). Specifically, the working hours of the drivers in the delivery plans Ex1, Ex2, and Ex3 are 500 minutes, 450 minutes, and 450 minutes, respectively. Therefore, the delivery plan Ex1 with a longer working time is excluded. In addition, the power consumption in the delivery plans Ex2 and Ex3 is 20kWh and 25kWh, respectively. Therefore, the delivery plan Ex2 with less power consumption is selected.

[0043] In route plan R2, delivery is performed in the order of areas A, B, D, C, E, F, and G. In more detail, after completing delivery to all target locations included in area A, vehicle 10 moves to area B, and after completing delivery to all target locations included in area B, it moves to area D, and so on, and delivery is performed in this way. That is, vehicle 10 operating according to route plan R2 performs delivery to all target locations included in areas A to G in the determined order of operation. In delivery plan Ex2, when vehicle 10 is located in area C, time ts arrives. Therefore, vehicle 10 uses EVSE 20C set at the charging point set in area C (target charging place in area C) to charge power storage device 11. The moment when delivery to all target locations included in areas A to G is completed is equivalent to the end time of operation.

[0044] In any of the delivery plans Ex1 to Ex3, the time ts is set before the time period T1, and the time te is set within the time period T1. Therefore, the first operation period set before the time period T1 becomes the period from the start time of the operation to the time ts. In addition, the second operation period set after the time period T1 becomes the period from the time t12 to the end time of the operation. That is, when the time ts is reached, the operation of the vehicle 10 is temporarily interrupted, and after the charging of the vehicle 10 is completed, when the time t12 is reached, the operation of the vehicle 10 is restarted. In addition, by Figure 2 The processing shown may generate a delivery plan in which the time te is set after the time period T1. In such a delivery plan, the timing of resuming the operation is the time te.

[0045] The server 30 (information processing device) according to the embodiment performs: searching for a route including a plurality of target locations and a target charging location; and generating an operation plan so that the electric vehicle operates along the route during the first operation period and the second operation period, respectively ( Figure 2S15-S20). The server 30 sets the charging period of the electric vehicle at the target charging location to a start time earlier than the prohibited time period and an end time later than or within the prohibited time period for the operation plan. Figure 2 S18, S20). According to the delivery plan generated in this way, when the vehicle 10 is parked at the target charging place (plugged in), the start time of the prohibited time period (rest start time) arrives. Therefore, it is possible to suppress the generation of idle time just before the prohibited time period. The driver of the vehicle 10 can rest at the target charging place. Generally speaking, the time required for charging an electric vehicle (especially a pure electric vehicle) is longer than the time required for refueling an internal combustion engine vehicle. Therefore, by allowing the driver to take the necessary rest during the charging of the vehicle 10, the decline in the operating efficiency of the vehicle 10 can be suppressed. By improving the operating efficiency, the benefits of delivery can be increased.

[0046] Implementation Method 2

[0047] Hereinafter, Embodiment 2 will be described with a focus on the differences from Embodiment 1. In this embodiment, HMI 14 includes a touch panel display (hereinafter referred to as "TPD") and a car navigation system (hereinafter referred to as "NAVI"). NAVI is equivalent to an example of the "notification device" of the present disclosure. ECU 15 is equivalent to an example of the "control device" of the present disclosure.

[0048] In this embodiment, the server 30 replaces Figure 2 The processing flow shown is executed Figure 4 The processing flow shown in the figure selects a vehicle to perform delivery and determines a delivery plan for the vehicle. In this embodiment, the content of delivery (a plurality of target locations belonging to different target areas) is predetermined, and the server 30 executes a process to select a vehicle to perform delivery from a plurality of registered vehicles (all of which are electric vehicles). Figure 4 The processing flow shown.

[0049] Figure 4 This is a flowchart showing a method for generating a delivery plan according to Embodiment 2. Figure 4 In S31, the server 30 obtains the position and status (including the remaining battery charge) of each vehicle through wireless communication with each registered vehicle. Furthermore, the server 30 calculates the drivable distance of each vehicle based on the sum of the power retained by the vehicle and the power charged to the vehicle when charging is continued during the prohibited time period. The calculated drivable distance is the drivable distance of the vehicle when charging is continued during the prohibited time period. The operation of the vehicle is prohibited during the prohibited time period, so the vehicle can be continuously charged during the prohibited time period.

[0050] In the next S32, the server 30 searches for a delivery plan that satisfies the first to eighth necessary conditions described below for each registered vehicle. The first necessary condition is that the route includes all target locations. The second necessary condition is that delivery is performed sequentially for each target area. According to the delivery plan that satisfies the second necessary condition, it is easy to grasp the delivery status and manage the delivery. The third necessary condition is that the prohibited time period is set in the prescribed time period T1 (legal rest time period). Time period T1 is the period from time t11 to time t12. The fourth necessary condition is that the operation start time is within the prescribed time period T2. Time period T2 is set before time t11. The fifth necessary condition is that the operation end time is within the prescribed time period T3. Time period T3 is set after time t12. According to the delivery plan that satisfies the third to fifth necessary conditions, it is easy to properly manage the driver's working hours. The sixth necessary condition is that the charging start time is within the prescribed time period T1a. Time period T1a is the period from time t13 to time t11. Time t13 is set between the end time of time period T2 and time t11. The seventh necessary condition is to set the charging point set in the target area where the vehicle is located at the time of charging start as the target charging place. The eighth necessary condition is that the charging end time is within the prohibited time period. According to the distribution plan that meets the eighth necessary condition, the second operation period often starts at time t12. By determining the start timing of the second operation period, the server 30 can easily manage the operation. The length of each time period can be set arbitrarily. The time periods T2 and T3 can also be one point (specified time) respectively. The time periods T1, T1a, T2, and T3 are stored in the storage device 32.

[0051] Through the above search, a delivery plan that meets the first to eighth necessary conditions is generated. In the next S33, the server 30 selects a vehicle that can deliver to all target locations from the multiple registered vehicles according to the delivery plan that meets the first to eighth necessary conditions. When multiple vehicles meet the requirements, one vehicle can be selected based on the location and specifications of the vehicle. In the next S34, the server 30 determines the delivery plan for the selected vehicle (the delivery plan that meets the first to eighth necessary conditions). In the case that there are multiple delivery plans that meet the first to eighth necessary conditions for the selected vehicle, the server 30 may also select the delivery plan with the least power consumption. Then, the server 30 sends the delivery plan to the selected vehicle. The following is a description of the selected vehicle. Figure 1 The example of the vehicle 10 is shown for description.

[0052] When the vehicle 10 receives the delivery plan from the server 30, the route indicated by the delivery plan is set in the NAVI of the HMI 14, and the NAVI guides the driver according to the route. Figure 5 The processing flow shown. Figure 5 : is a flowchart showing the display control of the vehicle 10 . Figure 6 The figures show the first to sixth screens displayed in the display control.

[0053] Reference Figure 5 In S51, ECU15 determines whether the start time (rest start time) of the prohibited time period indicated by the delivery plan has arrived. When the current time is before the rest start time (time t11) (S51: No), the process enters S52. In S52, ECU15 determines whether the vehicle 10 is being charged. In detail, ECU15 determines whether the aforementioned external charging is being performed. When the vehicle 10 is not being charged (S52: No), the process enters S53. In S53, ECU15 determines whether it is a time (hereinafter referred to as "charging preparation time") that is a specified time back from the charging start time indicated by the delivery plan. The charging preparation time is set slightly before the charging start time (for example, 10 minutes before).

[0054] After the operation starts, if all of S51 to S53 are judged as No, the process proceeds to S54. ECU15 performs display control in the first operation period in S54 to S56. Specifically, in S54, ECU15 judges whether the delivery to the current area (the target area where the vehicle 10 is located) is completed. ECU15 can recognize the delivery status of the vehicle 10 based on, for example, the position of the vehicle 10 on the route indicated by the delivery plan or the input (status report) from the driver to the HMI14.

[0055] If delivery to any destination point included in the current area has not been completed ( S54 : No), the process proceeds to S55 . In S55 , the ECU 15 causes the TPD display of the HMI 14 to Figure 6 The screen Sc1 (first screen) shown. More specifically, ECU15 controls TPD so that TPD displays screen Sc1. Screen Sc1 includes display units M11, M12A, M13A, M14, and M15. Display unit M11 displays the current time. Display unit M12A displays the current area, delivery status (in delivery), and delivery plan (the scheduled time for delivery completion for the current area). Display unit M13A displays the next area indicated by the delivery plan (the target area scheduled for delivery after the current area). Display unit M14 displays the prohibited time period (legal rest time period). Display unit M15 displays the target charging location and charging start time indicated by the delivery plan, and the number of target locations scheduled for delivery before charging starts.

[0056] When delivery to all destinations included in the current area is completed (S54: YES), the process proceeds to S56. In S56, the ECU 15 causes the TPD display of the HMI 14 to Figure 6 The screen Sc2 (second screen) shown in FIG. 1 includes display units M11, M12B, M13B, M14, and M15. The display unit M12B displays the current area and the delivery status (delivery completed). The display unit M13B displays the status of the vehicle 10 (moving to the next area) and the delivery plan (the scheduled time to start delivery in the next area). The display units M11, M14, and M15 of the screen Sc2 are the same as those of the screen Sc1.

[0057] When the processing of S55 or S56 is executed, the processing returns to S51. During the period when the charging preparation time has not arrived, the display control in the first operation period is executed (S54 to S56). Then, when the charging preparation time arrives (S53: Yes), the processing enters S57. In S57, the ECU 15 makes the TPD display of the HMI 14 Figure 6 The screen Sc3 (third screen) shown in FIG. Sc3 includes display units M21 and M22A. Display unit M21 displays the current time. Display unit M22A displays the current area and a message urging the driver to go to the target charging place. When the driver touches display unit M22A, TPD or NAVI can display the target charging place on the map.

[0058] When the process of S57 is executed, the process returns to S52. When the vehicle 10 arrives at the target charging location and the driver performs external charging of the power storage device 11, the determination in S52 is "yes", and the process proceeds to S58. In S58, the ECU 15 causes the Figure 6 The screen Sc4 (fourth screen) shown is displayed on the TPD of HMI14. The screen Sc4 includes display units M21, M22B, and M23. The display unit M21 displays the current time. The display unit M22B displays the current area, the status of the vehicle 10 (charging), and the remaining time until the rest start time (time t11). The display unit M23 displays the prohibited time period (legal rest time period).

[0059] Next, ECU15 determines in S59 whether the rest start time (time t11) has arrived. While the rest start time has not arrived (S59: No), S58 and S59 are repeated. Therefore, HMI14 continues to display screen Sc4 until the rest start time, and display unit M22B counts down the remaining time until the rest start. Then, when the rest start time arrives (S59: Yes), the process proceeds to S60. In S60, ECU15 Figure 6The screen Sc5 (fifth screen) shown is displayed on the TPD of the HMI 14. The screen Sc5 includes display units M21, M22C, and M23. The display unit M22C displays the current area, the status of the vehicle 10 (charging), a message urging the driver to take a rest, and a message notifying the driver that charging is completed during the rest. The display units M21 and M23 of the screen Sc5 are the same as those of the screen Sc4.

[0060] Next, the ECU 15 determines in S61 whether the end time (rest end time) of the prohibited time period indicated in the delivery plan has arrived. While the rest end time (time t12) has not arrived (S61: No), S60 and S61 are repeated. And, when the rest end time has arrived (S61: Yes), the process proceeds to S62. In S62, the ECU 15 Figure 6 The screen Sc6 (sixth screen) shown is displayed on the TPD of the HMI 14. The screen Sc6 includes display units M21, M22D and operation units M31, M32 (for example, buttons). The display unit M22D displays a message notifying the driver that the rest end time has arrived and instructions related to the operation units M31, M32. When the driver operates the operation unit M31, a first notification signal indicating that the driver has rested according to the statutory rest time period is sent from the vehicle 10 to the server 30. When the driver operates the operation unit M32, a second notification signal indicating that the driver has not rested according to the statutory rest time period is sent from the vehicle 10 to the server 30.

[0061] When the processing of S62 is executed, the processing returns to S51. Then, it is judged as "yes" in S51, and the processing enters S63. In S63, ECU15 determines whether the delivery to all target areas is completed. When the delivery to any target area is not completed (S63: No), ECU15 performs display control during the second operation period in S64~S66. In S64, S65, and S66, the processing based on S54, S55, and S56 is performed respectively. However, in S65, the seventh screen is displayed instead of screen Sc1. The seventh screen is a screen in which the display parts M14 and M15 are removed from the screen Sc1. In addition, in S66, the eighth screen is displayed instead of screen Sc2. The eighth screen is a screen in which the display parts M14 and M15 are removed from the screen Sc2. Thereafter, when the delivery to all target areas is completed (S63: Yes), the process ends. Figure 5 According to the above-mentioned display control, the driver can easily run the vehicle 10 as planned.

[0062] When receiving the second notification signal from the vehicle 10, the server 30 may change the delivery plan of the vehicle 10 so that the driver of the vehicle 10 can take a rest, and transmit the changed delivery plan to the vehicle 10. In addition, the server 30 may grasp the delivery status of the vehicle 10 based on the information (for example, location information) sequentially received from the vehicle 10. Furthermore, when the server 30 detects that the operation of the vehicle 10 is not carried out according to the plan (delivery plan), the server 30 may change the delivery plan of the vehicle 10 and transmit the changed delivery plan to the vehicle 10. The server 30 may also entrust other vehicles with the delivery that is excluded from the delivery plan of the vehicle 10 by changing the delivery plan.

[0063] Other Implementations

[0064] Above Figure 2 , Figure 4 , Figure 5 Each of the processes shown is performed by one or more processors executing a program stored in one or more memories. However, this is not limiting, and these processes may be performed only by hardware (electronic circuits) without using software. In addition, in Embodiment 1, Figure 5 Display controls shown.

[0065] The operation of electric vehicles is not limited to operation for delivery, but can also be operation for mobile sales (for example, mobile supermarkets) or operation for transportation of people. Electric vehicles can also be electric vehicles other than BEVs (for example, plug-in hybrid electric vehicles). Electric vehicles can also be operated by automatic driving. In order to allow the vehicle rather than the driver to rest, operation can also be prohibited during prohibited time periods. External charging is not limited to plug-in charging, but can also be contactless charging.

[0066] The embodiments disclosed this time should be considered in all respects as illustrative and non-restrictive. The scope of the present invention is indicated not by the description of the above embodiments but by the scope of claims, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

Claims

1. An information processing device for generating an operation plan for an electric vehicle, wherein: The electric vehicle is configured to be able to travel using electric power stored in the electric vehicle. The information processing device is configured to perform the following processing: Searching for a route including multiple destinations and destination charging locations; and The operation plan is generated in such a manner that the electric vehicle operates along the route during each of a first operation period and a second operation period, the first operation period being set before a prohibited time period during which operation of the electric vehicle is prohibited, and the second operation period being set after the prohibited time period, For the operation plan, the information processing device sets a charging period for charging the electric vehicle at the target charging location so that the start time of the charging period is before the prohibited time period and the end time of the charging period is within or after the prohibited time period.

2. The information processing device according to claim 1, wherein: The information processing device includes a processor and a storage device, wherein the storage device stores area information related to a plurality of areas. The area information indicates a charging point set in each of the plurality of areas. Each of the charging points in the area is located in the area where the charging point is set. The information processing device searches for the route passing through a plurality of target areas included in the plurality of areas, Each of the plurality of target areas includes more than one target location. The information processing device generates the operation plan so that the charging point set in the target area where the electric vehicle is located at a time that is a predetermined time back from the start time of the prohibited time period among the plurality of target areas becomes the target charging location.

3. The information processing device according to claim 2, wherein: The information processing device determines an operation order for each of the multiple target areas, and generates the operation plan in a manner that the electric vehicle moves to the next target area after completing the operation for all the target locations included in one target area, thereby performing the operation for the multiple target areas in sequence.

4. The information processing device according to claim 1, wherein: The operation of the electric vehicle is an operation for the electric vehicle to perform delivery to each of the plurality of destinations. The prohibited time period is a statutory rest time period for giving the driver of the electric vehicle a rest time prescribed by law, The operation plan also indicates the operation start time and the operation end time. The information processing device is configured to calculate the working time of the driver in the operation plan based on the operation start time, the operation end time and the prohibited time period, The information processing device is configured to acquire the operation plan for each of a plurality of route plans, and select the route used for the operation plan from the plurality of route plans based on the working time.

5. An operating system, comprising the information processing device according to any one of claims 1 to 4 and the electric vehicle, wherein: The information processing device is provided outside the electric vehicle and is configured to transmit the generated operation plan to the electric vehicle. The electric vehicle includes a notification device and a control device, wherein the notification device notifies the driver of the electric vehicle, and the control device controls the notification device. The control device is configured to control the notification device using the prohibited time period and the charging period indicated by the operation plan.

Citation Information

Patent Citations

  • Forming of delivery plan for improving load efficiency of regular service in plural operation companies

    JP2004131270A