Management System

Abstract

The present invention provides a management system that can prevent excessive communication load between the first and second servers. [Solution] The management system provides a charging plan to a vehicle that has a battery charged from an external power source. The first server sends multiple charging plans to the vehicle to the second server. The second server mediates the multiple charging plans. The second server stores the mediated charging plan. When the management system resends the mediated charging plan to the vehicle, the first server does not send the charging plan to the second server, but instead sends a retransmission request DR to resend the mediated charging plan, and a vehicle identifier ID indicating the vehicle to which the retransmission request is being sent, to the second server. When the second server receives the retransmission request DR, it sends the stored mediated charging plan to the vehicle identified by the vehicle identifier ID.

Description

Technical Field

[0001] The present invention relates to a management system.

Background Art

[0002] Patent Document 1 describes a vehicle management system that provides a charging plan for a vehicle having a battery charged from an external power source. The vehicle management system includes a first server and a second server.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the vehicle management system as described in Patent Document 1, the first server may transmit a plurality of charging plans to the second server for a vehicle. Further, when the second server mediates the plurality of charging plans, the second server transmits the charging plan of the mediation result to the vehicle.

[0005] In this case, when the vehicle management system retransmits the charging plan of the mediation result to the vehicle, if the first server transmits the target charging plan to the second server, the communication load between the first server and the second server becomes excessively high.

Means for Solving the Problems

[0006] A management system for solving the above problems is a management system that provides a charging plan to a vehicle having a battery that is charged from an external power source, and comprises a first server and a second server, wherein the first server transmits a plurality of charging plans to the vehicle to the second server, the second server mediates the plurality of charging plans, stores the mediated charging plan, transmits the mediated charging plan to the vehicle, and when the first server retransmits the mediated charging plan to the vehicle, the first server transmits to the second server a retransmission request to retransmit the mediated charging plan without transmitting the charging plan to the second server, and an identifier of the vehicle to which the retransmission request is transmitted, and when the second server receives the retransmission request, it transmits the stored mediated charging plan to the vehicle identified by the vehicle identifier. [Effects of the Invention]

[0007] According to the above configuration, when the vehicle management system resends the arbitration result of the charging plan to the vehicle, the first server does not send the charging plan to the second server. Therefore, the vehicle management system can prevent the communication load between the first server and the second server from becoming excessively high due to the first server sending the charging plan. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a schematic diagram showing a vehicle management system. [Figure 2] Figure 2 is an explanatory diagram showing the charging plan. [Figure 3] Figure 3 is a sequence chart showing the flow of information in the vehicle management system. [Figure 4] Figure 4 is a flowchart showing the series of processes performed by the first server. [Figure 5] Figure 5 is a flowchart showing the series of processes performed by the second server. [Modes for carrying out the invention]

[0009] <Overview of the management system> As shown in Figure 1, the vehicle management system 10 comprises a plurality of vehicles 20 and a management system 30.

[0010] <Vehicle Overview> Vehicle 20 is equipped with a charging port 21, a charging device 22, a battery 23, and a drive motor 24. Vehicle 20 is an electric vehicle.

[0011] The charging port 21 connects to an external charging connector on the vehicle 20. When the charging connector is connected to the charging port 21, the battery 23 is ready to be charged from an external power source on the vehicle 20.

[0012] The drive motor 24 is the power source for the vehicle 20. The drive motor 24 uses the power stored in the battery 23 to drive the vehicle 20. The battery 23 stores the power to operate the drive motor 24.

[0013] The charging device 22 includes a relay that switches between connecting and disconnecting the power path from the charging port 21 to the battery 23, and a power conversion circuit. The battery 23 is charged when the charging device 22 is controlled.

[0014] The vehicle 20 is equipped with an air conditioning unit 25, a communication device 26, and a control device 27. The air conditioning unit 25 performs heat exchange with the cooling water and blows air whose temperature has been adjusted by the heat exchange into the interior space of the vehicle 20. The air conditioning unit 25 adjusts the heat exchange and airflow to match the set temperature T, which is the target temperature of the interior space of the vehicle 20.

[0015] The communication device 26 can communicate with the management system 30 via a wireless communication network. The control device 27 controls the charging of the battery 23 and the operation of the air conditioning system 25 according to the charging plan PL received from the management system 30. Note that in Figure 1, only one of the multiple vehicles 20 is shown in detail, and detailed descriptions of the other vehicles 20 are omitted.

[0016] <Overview of the Management System> The management system 30 manages the charging plan PL of the vehicle 20. The management system 30 provides the charging plan PL for the vehicle 20 to the vehicle 20.

[0017] As shown in FIG. 2, the charging plan PL includes a vehicle identifier ID, charging control information CC, and air conditioning control information CA. The vehicle identifier ID is information for identifying the target vehicle 20.

[0018] The charging control information CC includes data indicating a charging start time ts for starting the charging of the battery 23, a charging end time te for ending the charging of the battery 23, a charging period CH for charging from the charging start time ts to the charging end time te, and a non-charging period NC for not charging.

[0019] In the example shown in FIG. 2, among the time from the charging start time ts to the charging end time te, the period from the charging start time ts to a time t1 after the charging start time ts is the charging period CH. The period from the time t1 to a time t2 after the time t1 is the non-charging period NC. The period from the time t2 to a time t3 after the time t2 is the charging period CH. The period from the time t3 to a time t4 after the time t3 is the non-charging period NC. The period from the time t4 to the charging end time te after the time t4 is the charging period CH. As a result, the charging control information CC is a plan such that the charging rate C at the charging start time ts is the first charging rate C1, while the charging rate C at the charging end time te is the second charging rate C2.

[0020] In addition, the charging control information CC is control information of the air conditioner 25 from the charging start time ts to the charging end time te. The charging control information CC includes a set temperature T that is setting information of the air conditioner 25 and an air conditioning start time ta for starting the operation of the air conditioner 25.

[0021] In the example shown in Figure 2, the air conditioning start time ta is time t4. Until the air conditioning start time ta, the air conditioning unit 25 is in an off state and not operating. From the air conditioning start time ta to time t5 (after ta), the set temperature T is the first temperature T1. From time t5 to the charging end time te (after t5), the set temperature T is the second temperature T2, which is higher than the first temperature T1. In the example shown in Figure 2, the air conditioning unit 25 operates in cooling mode.

[0022] As shown in Figure 1, the management system 30 comprises a first server 40 and a second server 50. The first server 40 transmits multiple charging plans PL for the vehicle 20 to the second server 50. The first server 40 includes a communication device 41 and a first information processing device 42. The communication device 41 is capable of communicating with the second server 50 via a wireless communication network.

[0023] The first information processing device 42 comprises a first execution device 43 and a first storage device 44. The first execution device 43 is a CPU. The first storage device 44 is memory. The first storage device 44 stores multiple application APs. An application AP is a program for creating a charging plan PL, which is executed by the first execution device 43. Multiple application APs create different charging plan PLs. The multiple application APs include the first application AP1 and the second application AP2.

[0024] The first application AP1 is an application AP that creates a charging plan PL based on the electricity cost of charging, for example. The second application AP2 is an application AP that creates a charging plan PL based on the load of the external power supply used for charging, for example.

[0025] The first execution device 43 executes each application AP, thereby creating multiple charging plan PLs. The first execution device 43 then transmits the created charging plan PLs to the second server 50 via the communication device 41.

[0026] Furthermore, the first storage device 44 stores various programs. The first execution device 43 executes the various programs stored in the first storage device 44. As a result, the first information processing device 42 performs a series of processes related to the charge plan PL. Specifically, the first storage device 44 stores the first retransmission program PR1. The first retransmission program PR1 is a program that causes the first execution device 43 to execute the processing when retransmitting the charge plan PL. The processing when the first retransmission program PR1 is executed will be described later.

[0027] The second server 50 mediates multiple charge plan PLs received from the first server 40. The second server 50 stores the resulting charge plan PLs. The second server 50 includes a communication device 51 and a second information processing device 52. The communication device 51 can communicate with the first server 40 via a wireless communication network. The communication device 51 can also communicate with the vehicle 20 via a wireless communication network.

[0028] The second information processing device 52 comprises a second execution device 53 and a second storage device 54. The second execution device 53 is a CPU. The second storage device 54 is memory. The second storage device 54 stores various programs. The second execution device 53 executes the various programs stored in the second storage device 54. As a result, the second information processing device 52 performs a series of processes related to the charge plan PL.

[0029] Specifically, the second memory device 54 stores the arbitration program PA and the second retransmission program PR2. The arbitration program PA is a program for arbitrating multiple charge plans PL by having the second execution device 53 execute it. The second execution device 53 arbitrates multiple charge plans PL by executing the arbitration program PA. The second execution device 53 arbitrates by selecting the charge plan PL with the earliest charge start time ts from among the acquired multiple charge plans PL.

[0030] The second retransmission program PR2 is a program that instructs the second execution device 53 to perform the processing required when retransmitting the charge plan PL. The processing that occurs when the second retransmission program PR2 is executed will be described later.

[0031] Furthermore, the second storage device 54 stores the arbitrated charging plan PL from among the multiple charging plan PLs received from the first server 40. When storing the charging plan PL, the second storage device 54 compresses and stores the arbitrated charging plan PL.

[0032] <Flow of charging planning in vehicle management systems> Next, we will explain the flow of the charging plan PL in the vehicle management system 10. As shown in Figure 3, first, in the first server 40, the first execution device 43 performs the process in step S11. In step S11, the first execution device 43 creates a charging plan PL by executing the first application AP1. After that, the first execution device 43 transmits the created charging plan PL to the second server 50 from the communication device 41.

[0033] Subsequently, the first execution device 43 performs the process in step S12. In step S12, the first execution device 43 creates a charging plan PL by executing the second application AP2. Then, the first execution device 43 transmits the created charging plan PL from the communication device 41 to the second server 50.

[0034] Subsequently, when the second server 50 obtains multiple charge plan PLs from the first server 40, the second execution device 53 performs the process in step S13. In step S13, the second execution device 53 mediates the multiple charge plan PLs. Specifically, the second execution device 53 mediates by selecting the charge plan PL with the earliest charge start time ts from among the multiple charge plan PLs obtained from the first server 40. After that, the second execution device 53 proceeds to step S14.

[0035] In step S14, the second execution device 53 compresses the charge plan PL, which is the arbitration result arbitrated in step S13, and stores it in the second storage device 54 for storage. On the other hand, the second execution device 53 does not store any charge plan PLs that are not arbitration results in the second storage device 54 for storage.

[0036] Subsequently, the second execution device 53 transmits the arbitration result charge plan PL to the target vehicle 20. After the vehicle 20 receives the arbitration result charge plan PL from the second server 50, the control device 27 performs the process in step S15.

[0037] In step S15, the control device 27 checks the charge plan PL of the mediation result. Specifically, the control device 27 checks whether there is any missing information in the acquired charge plan PL.

[0038] For example, the control device 27 determines that there is a gap if there is a period between the charging start time ts and the charging end time te that is neither a charging period CH nor a non-charging period NC. The control device 27 determines that the received result RR is successful if there is no gap.

[0039] On the other hand, the control device 27 determines that there are no missing data if the entire period from the charging start time ts to the charging end time te is either a charging period CH or a non-charging period NC. If there are missing data, the control device 27 determines that the received result RR is a failure.

[0040] The control device 27 then transmits the reception result RR to the second server 50 via the communication device 26. The reception result RR indicates whether the confirmation of the charging plan PL was successful or unsuccessful.

[0041] Subsequently, the second server 50 receives the reception result RR. The second server 50 forwards the received reception result RR to the first server 40. Then, the first server 40 and the second server 50 perform the processing that was done when they received the reception result RR, and the vehicle management system 10 completes this series of processes.

[0042] <Processing of the first server when resending the charging plan> When the first execution device 43 obtains the reception result RR from the second server 50, it starts executing the first retransmission program PR1.

[0043] As shown in Figure 4, when the first execution device 43 starts executing the first retransmission program PR1, the first execution device 43 first performs the process in step S21. In step S21, the first execution device 43 determines whether the acquired reception result RR is successful or not.

[0044] If the received result RR is successful (S21:YES), the first execution device 43 terminates this series of processes. On the other hand, if the received result RR is unsuccessful (S21:NO), the first execution device 43 proceeds to step S22.

[0045] In step S22, the first execution device 43 sends a retransmission request DR and a vehicle identifier ID indicating the vehicle 20 to be retransmitted to the second server 50. The retransmission request DR indicates a request to retransmit the arbitration result charge plan PL. After that, the first execution device 43 terminates this series of processes.

[0046] <Processing by the second server when resending the charging plan> When the second execution device 53 obtains the reception result RR from the vehicle 20, it starts executing the second retransmission program PR2.

[0047] As shown in Figure 5, when the second execution device 53 starts executing the second retransmission program PR2, the second execution device 53 first performs the process in step S31. In step S31, the second execution device 53 determines whether the acquired reception result RR is successful or not.

[0048] If the received result RR is successful (S31: YES), the second execution unit 53 proceeds to step S32. In step S32, the second execution unit 53 deletes the saved arbitration result charge plan PL. After that, the second execution unit 53 terminates this series of processes.

[0049] On the other hand, if the received result RR is a failure (S32: NO), the second execution device 53 proceeds to step S33. In step S33, the second execution device 53 determines whether or not it has received a retransmission request DR from the first server 40.

[0050] If the second execution device 53 has not received a retransmission request DR (S33: NO), the second execution device 53 repeats the process in step S33. On the other hand, if the second execution device 53 has received a retransmission request DR (S33: YES), the second execution device 53 proceeds to step S34.

[0051] In step S34, the second execution device 53 decompresses the compressed and stored data of the arbitration result charge plan PL. After that, the second execution device 53 proceeds to step S35.

[0052] In step S35, the second execution device 53 resends the decompressed arbitration result charge plan PL. Specifically, the second execution device 53 sends the decompressed arbitration result charge plan PL to the vehicle 20 indicated by the vehicle identifier ID obtained when the retransmission request DR was acquired. After that, the second execution device 53 terminates this series of processes.

[0053] <Operation of this embodiment> <Effects of this embodiment> (1) The management system 30 provides the vehicle 20 with a charging plan PL. The management system 30 comprises a first server 40 and a second server 50. The first server 40 sends multiple charging plan PLs to the vehicle 20 to the second server 50. The second server 50 mediates the multiple charging plan PLs. The second server 50 stores the mediated charging plan PL. When the management system 30 resends the mediated charging plan PL to the vehicle 20, the first server 40 does not send the charging plan PL to the second server 50. Instead, the first server 40 sends only a retransmission request DR and a vehicle identifier ID indicating the vehicle 20 that is sending the retransmission request DR to the second server 50. When the second server 50 receives the retransmission request DR, it sends the stored mediated charging plan PL to the vehicle 20 identified by the vehicle identifier ID.

[0054] According to the above configuration, when the management system 30 resends the arbitration result charging plan PL to the vehicle 20, the first server 40 does not send the charging plan PL to the second server 50. Therefore, the management system 30 can prevent the communication load between the first server 40 and the second server 50 from becoming excessively high due to the first server 40 sending the charging plan PL.

[0055] (2) When the second server 50 saves the arbitration result charging plan PL, it compresses the arbitration result charging plan PL before saving it. When the second server 50 sends the charging plan PL to the vehicle 20, it decompresses the saved arbitration result charging plan PL before sending it. With the above configuration, it is possible to prevent the storage capacity used by the second server 50 when saving the arbitration result charging plan PL from becoming excessively large.

[0056] (3) If the reception result RR received from the vehicle 20 indicates success, the second server 50 deletes the stored arbitration result charging plan PL. With the above configuration, the second server 50 can avoid wasting storage capacity by storing charging plan PLs that it no longer needs to store as arbitration results.

[0057] (4) The charging plan PL includes charging control information CC. The charging control information CC includes data indicating the charging start time ts when charging of the battery 23 begins, the charging end time te when charging of the battery 23 ends, and the charging period CH and non-charging period NC from the charging start time ts to the charging end time te. With the above configuration, the management system 30 can greatly benefit from the first server 40 not resending the charging plan PL to the second server 50 because the data capacity of the charging plan PL is considerably larger.

[0058] (5) The charging plan PL includes air conditioning control information CA. The air conditioning control information CA includes time-series data of the set temperature T, which is the setting information of the air conditioning unit 25, and the air conditioning start time ta, which is the start time when the air conditioning unit 25 starts operating. With the above configuration, the management system 30 can greatly benefit from the first server 40 not resending the charging plan PL to the second server 50 because the data capacity of the charging plan PL is considerably large.

[0059] <Example of changes> The above embodiment can be implemented with the following modifications. The above embodiment and the following modifications can be combined with each other to the extent that they do not contradict each other technically.

[0060] The control device 27 may be configured as a circuit including one or more processors that execute various processes according to a computer program (software). Alternatively, the control device 27 may be configured as a circuit including one or more dedicated hardware circuits, such as application-specific integrated circuits (ASICs), or a combination thereof, that execute at least some of the various processes. The processor includes a CPU and memory such as RAM and ROM. The memory stores program code or instructions configured to cause the CPU to execute processes. Memory, i.e., computer-readable media, includes any available media that can be accessed by a general-purpose or dedicated computer. The same applies to the first information processing device 42 and the second information processing device 52.

[0061] • Multiple charging plans PL created by the first information processing device 42 may be created by executing the same application AP. For example, even if the first information processing device 42 executes the same application AP, different execution times may result in different battery conditions for the vehicle 20, leading to the creation of different charging plans PL.

[0062] The contents of the charging plan PL are not limited to the examples of the above embodiment. The charging start time ts does not have to be a reserved time. For example, the charging start time ts may be immediate. Also, for example, the charging period CH may be data indicating power that changes with respect to time.

[0063] The charging plan PL does not necessarily have to include data indicating the charging start time ts, the charging end time te, and the charging period CH and non-charging period NC from the charging start time ts to the charging end time te. Also, for example, the charging plan PL does not necessarily have to include the air conditioning control information CA. That is, the charging plan PL does not necessarily have to include the setting information of the air conditioning unit 25 and the air conditioning start time ta.

[0064] The timing of mediation by the second server 50 may be, for example, when a second charging plan PL is received after the first charging plan PL has been received. Subsequently, the timing of mediation by the second server 50 again may be when a new charging plan PL is received while the mediation result charging plan PL is being saved. Alternatively, for example, the second server 50 may determine whether or not multiple charging plan PLs have been received within a predetermined period. In this case, if multiple charging plan PLs have been received within the predetermined period, the second server 50 may mediate the multiple charging plan PLs.

[0065] The method of arbitration by the second server 50 is not limited to the example of the above embodiment. For example, the second execution device 53 may arbitrate by selecting the charging plan PL with the earliest charging end time te. Alternatively, the second execution device 53 may arbitrate by selecting the charging plan PL with the highest second charging rate C2 at the charging end time te. Alternatively, the second execution device 53 may arbitrate by creating a charging plan PL that combines the contents of multiple charging plan PLs. Specifically, when adjusting two charging plan PLs, the second execution device 53 may use a charging plan PL that combines the charging control information CC of one charging plan PL and the air conditioning control information CA of the other charging plan PL as the arbitration result charging plan PL.

[0066] The second server 50 does not need to compress the arbitration result charging plan PL when saving the arbitration result charging plan PL. The second server 50 does not need to decompress the saved arbitration result charging plan PL before sending it to the vehicle 20.

[0067] If vehicle 20 successfully receives the arbitration result charging plan PL, the second server 50 does not need to delete the saved arbitration result charging plan PL. The method for determining the reception result is not limited to the example of the above embodiment. For example, when the second server 50 obtains a reception result RR indicating that it has received a charging plan PL from the vehicle 20, the second server 50 may perform the processing in step S32 by executing the second retransmission program PR2. On the other hand, when the second server 50 has not received a reception result RR indicating that it has received a charging plan PL from the vehicle 20 for a predetermined period of time, the second server 50 may perform the processing in step S33 by executing the second retransmission program PR2. In this case, when the first server 40 has not received a reception result RR from the second server 50 for a predetermined period of time, the first server 40 may perform the processing in step S22 by executing the first retransmission program PR1. [Explanation of Symbols]

[0068] 10…Vehicle Management System 20... Vehicles 23…Battery 25...Air conditioner 27...Control device 30…Management System 40… Server 1 50…Second Server CH…Charging period DR…Resend request NC…Non-charging period PL...Charging Plan ta…Air conditioning start time te... Charging completion time ts…Charging start time

Claims

1. A management system that provides a vehicle with a charging plan for a vehicle having a battery that is charged from an external power source, It consists of a first server and a second server. The first server transmits a plurality of charging plans for the vehicle to the second server. The second server mediates the multiple charging plans, saves the charging plan resulting from the mediation, and transmits the charging plan resulting from the mediation to the vehicle. When resending the charging plan of the mediation result to the vehicle, The first server does not send the charging plan to the second server, but instead sends to the second server a retransmission request to retransmit the charging plan of the arbitration result, and the identifier of the vehicle to which the retransmission request is to be sent. When the second server receives the retransmission request, it transmits the stored arbitration result charging plan to the vehicle identified by the vehicle identifier. Management system.

2. The second server is, When saving the charging plan of the mediation result, the charging plan of the mediation result is compressed and saved. When transmitting the aforementioned charging plan to the vehicle, the stored charging plan of the arbitration result is decompressed before transmission. The management system according to claim 1.

3. If the vehicle successfully receives the charging plan from the arbitration results, the second server deletes the charging plan from the arbitration results that it has stored. The management system according to claim 1.

4. The charging plan includes a charging start time when charging of the battery begins, a charging end time when charging of the battery ends, and data indicating the charging period and non-charging period from the charging start time to the charging end time. The management system according to claim 1.

5. The charging plan further includes setting information for the vehicle's air conditioning system and the air conditioning start time at which the air conditioning system begins to operate. The management system according to claim 4.

Images