Charging management system and charging management method
The charging management system addresses security risks in mobile object charging by assessing and rewarding high security levels with preferential treatment, enhancing the security and efficiency of charging operations.
Patent Information
- Application Number
- PCT/JP2024/006658
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-31
- Filing Date
- 2024-02-22
- Publication Date
- 2024-12-05
AI Technical Summary
The increasing use of chargeable mobile objects and charging stations poses security risks due to potential vulnerabilities in wireless communication, particularly in ensuring the confidentiality, integrity, and availability of information, as well as defense against external cyber attacks and malicious operations.
A charging management system that includes a reception and processing unit to assess and manage the security level of mobile objects, providing preferential treatment such as priority access, discounted charging fees, and enhanced charging speeds based on their security levels, encouraging users to maintain high security standards by updating software and enabling security monitoring services.
The system effectively enhances the security of mobile objects by incentivizing users to improve their security measures, ensuring the confidentiality and integrity of information while maintaining efficient charging operations.
Smart Images

Figure JP2024006658_05122024_PF_FP_ABST
Abstract
Description
Charging management system and charging management method
[0001] The present disclosure relates to a charge management system and a charge management method.
[0002] 2. Description of the Related Art As rechargeable mobile objects become more common, charging stations including a plurality of charging devices are also becoming more common.
[0003] JP 2010-237924 A, International Publication No. 2013 / 057879, JP 2012-147651 A, JP 2013-62918 A, International Publication No. 2022 / 163619, JP 2019-200506 A
[0004] A mobile object that can be charged may be able to communicate with the outside world via a wireless communication line. When a mobile object can communicate with the outside world via a wireless communication line, the convenience of the mobile object is improved. For example, a charging management system can be constructed that collects and manages management information related to the security of the mobile object in a server via a wireless communication line, and the charging management system can manage charging of the mobile object using a charging device.
[0005] On the other hand, if a mobile object is capable of communicating with the outside world via a wireless communication line, there is a possibility that a security problem may arise with respect to communication access from the outside world to the mobile object.
[0006] The present disclosure provides a charge management system and a charge management method that can ensure the security of a mobile object.
[0007] A charging management system according to the present disclosure includes a reception unit and a processing unit. The reception unit receives a request for a mobile object to use a charging device. The mobile object is capable of charging. The processing unit performs processing for the mobile object to use the charging device in accordance with the request and a security level of the mobile object.
[0008] 1 is a diagram showing the configuration of a charging management system according to an embodiment. FIG. 1 is a diagram showing the configuration of a vehicle according to an embodiment. FIG. 2 is a diagram showing the configuration of a central ECU according to an embodiment. FIG. 2 is a diagram showing the data structure of vehicle status information according to an embodiment. FIG. 3 is a diagram showing the data structure of security anomaly information according to an embodiment. FIG. 4 is a diagram showing the data structure of vehicle configuration information according to an embodiment. FIG. 5 is a diagram showing the configuration of an ECU according to an embodiment. FIG. 6 is a diagram showing the data structure of version information according to an embodiment. FIG. 7 is a diagram showing the configuration of a vehicle management server according to an embodiment. FIG. 8 is a diagram showing the data structure of server access information according to an embodiment. FIG. 9 is a diagram showing the data structure of vehicle information according to an embodiment. FIG. 10 is a diagram showing the configuration of a station management server according to an embodiment. FIG. 11 is a diagram showing a reservation schedule notified to a vehicle according to an embodiment. FIG. 12 is a diagram showing the data structure of station information according to an embodiment. FIG. 13 is a diagram showing the data structure of electricity price information according to an embodiment. FIG. 14 is a diagram showing the configuration of a charging station according to an embodiment. FIG. 15 is a diagram showing the configuration of a charging management system according to a first modified example of an embodiment. FIG. 16 is a diagram showing station information notified to a vehicle according to the first modified example of an embodiment. A sequence diagram showing the operation of a charging management system according to a second modified example of an embodiment. A flowchart showing a security level determination process according to a second modified example of an embodiment. A flowchart showing a station search process according to a second modified example of an embodiment. A flowchart showing a billing amount estimation process according to a second modified example of an embodiment. 10. A sequence diagram showing the operation of a charge management system according to a third modified example of an embodiment. A diagram showing the configuration of a charge management system according to a fourth modified example of an embodiment. A diagram showing the data structure of vehicle information in the fourth modified example of an embodiment. A flowchart showing the process of schedule allocation in a fifth modified example of an embodiment. A flowchart showing the process of charge output adjustment in a sixth modified example of an embodiment. A diagram showing the configuration of a charge management system according to a seventh modified example of an embodiment. A diagram showing the configuration of a charge management system according to an eighth modified example of an embodiment. A diagram showing the configuration of a charge management system according to a ninth modified example of an embodiment.
[0009] Hereinafter, embodiments of a charge management system according to the present disclosure will be described with reference to the drawings.
[0010] (Embodiment) The charging management system according to the embodiment is a system for managing charging of a mobile body that can be charged using a charging device, and the mobile body can communicate with the outside world via a wireless communication line, and accordingly, measures are taken to ensure the security of the mobile body.
[0011] In this specification, the security of a mobile body means ensuring the confidentiality, integrity, and availability of information of the mobile body. The security level of a mobile body means the level of ability to ensure the confidentiality, integrity, and availability of information of the mobile body. The security level of a mobile body may also include the level of defense capability against external cyber attacks and the level of internal defense capability against unauthorized operation of malware. In the following, a vehicle is used as an example of a mobile body.
[0012] The charging management system 1 is a system for managing a charging infrastructure for a vehicle 10, and may be configured as shown in Fig. 1. Fig. 1 is a diagram showing the configuration of the charging management system 1. The charging management system 1 includes a vehicle 10, a vehicle management server 20, a charging station 30, a station management server 40, and a power distribution network 50. The charging station 30 includes a plurality of charging devices 601a to 601c. Hereinafter, when the charging devices 601a to 601c are not to be distinguished from one another, they may be simply referred to as charging devices 601.
[0013] In the charge management system 1, the vehicle 10 and the vehicle management server 20 are communicatively connected via a wireless communication line. The vehicle management server 20 and the station management server 40 are communicatively connected via a wireless communication line and / or a wired communication line. The station management server 40 and the charging station 30 are communicatively connected via a wireless communication line. The charging station 30 and the power distribution network 50 are connected via a power cable so that power can be supplied.
[0014] The wireless communication line includes a communication line using radio access technology (RAT: Radio Access Technology), such as LTE (Long Term Evolution), NR (New Radio), Wi-Fi, Bluetooth (registered trademark), etc. The wired communication line includes the Internet, a telephone switching network, etc.
[0015] In the charging management system 1, the vehicle management server 20 is managed by, for example, a vehicle manufacturer. The vehicle management server 20 manages the security status of the vehicle 10. The station management server 40 is managed by a charging service provider or a charging owner. The station management server 40 monitors the status of the charging station 30 and issues control instructions. Furthermore, the station management server 40 determines preferential treatment depending on the status of the vehicle 10. The charging station 30 is connected to a power distribution network 50.
[0016] The vehicle 10 can transmit the management information to the vehicle management server 20. When the vehicle management server 20 receives the management information related to the security of the vehicle 10, it determines the security level of the vehicle 10 according to the management information. The vehicle management server 20 notifies the station management server 40 of the security level of the vehicle 10. The station management server 40 determines parameters related to charging of the vehicle 10 according to the security level of the vehicle 10. The station management server 40 may determine parameters such that the higher the security level of the vehicle 10, the more advantageous the conditions under which the vehicle 10 can charge. The station management server 40 notifies the charging station 30 of the parameters. The charging station 30 performs processing related to the vehicle's use of the charging device 601 according to the parameters.
[0017] As a result, the charge management system 1 can provide preferential treatment to vehicles 10 with a high security level regarding the use of the charging device 601, and can provide incentives to users of the vehicles 10 to improve security and encourage them to ensure security. As a result, the security of the vehicle 10 can be ensured by the user of the vehicle 10 taking security measures such as updating the software used in the vehicle 10.
[0018] The security level of the vehicle 10 may be determined using any information related to the vehicle 10's ability to ensure confidentiality, integrity, and availability of information.
[0019] For example, the charge management system 1 may determine the security level of the vehicle 10 based on the latest version of software installed in the vehicle 10 .
[0020] The charge management system 1 may determine the security level of the vehicle 10 based on whether security software is installed in the vehicle 10 or whether a security monitoring service is enabled. The security monitoring service may be a security monitoring service that detects signs of intrusion into the in-vehicle system. The security monitoring service includes, for example, a network intrusion detection system that protects the in-vehicle network and a host-based intrusion detection system that protects the in-vehicle ECU.
[0021] The charge management system 1 may determine the security level of the vehicle 10 based on information about a breach history (i.e., security breach history) of at least one of an external cyber-attack on the vehicle 10 and an internal unauthorized operation by malware within the vehicle 10. The information about the security breach history may include whether or not there is a security breach history, the number of security breaches, the recency of the security breach history (whether or not it has occurred recently), and the like.
[0022] The charge management system 1 may determine the security level of the vehicle 10 based on the number of security errors that occur, determined by monitoring information received by the vehicle 10 or information communicated within the vehicle 10 .
[0023] Furthermore, the preferential treatment to be given to the vehicle 10 according to the security level of the vehicle 10 may be any treatment that provides an incentive for security measures.
[0024] For example, the charging management system 1 may make it easier for the vehicle 10 to find a charging environment depending on the security level of the vehicle 10. The charging management system 1 may allow the reservation application software to make a reservation for a charging station 30 for a later date depending on the security level of the vehicle 10. The charging management system 1 may cause the reservation application software to place the vehicles 10 in the usage reservation queue in descending order of security level.
[0025] The charging management system 1 may provide a discount on the charging fee depending on the security level of the vehicle 10. The charging management system 1 may reduce the estimated usage fee for the charging device 601 depending on the security level of the vehicle 10. The charging management system 1 may reduce the charged usage fee for the charging device 601 depending on the security level of the vehicle 10.
[0026] The charge management system 1 may be configured to save time by increasing the charging speed (or output) of the charging device 601 according to the security level of the vehicle 10. The charge management system 1 may be configured to preferentially allocate the amount of charge by the charging device 601 when power is tight according to the security level of the vehicle 10.
[0027] In the charge management system 1, the vehicle 10 is a mobile body that can be charged and has wheels. The vehicle 10 may be, for example, an EV (Electric Vehicle) type mobile body or a PHV (Plug-in Hybrid Vehicle) type mobile body. The vehicle 10 may be a two-wheeled vehicle, a three-wheeled vehicle, a four-wheeled vehicle, or a mobile body having five or more wheels. The following description will mainly focus on the case where the vehicle 10 is an EV four-wheeled vehicle.
[0028] The vehicle 10 may be configured as shown in Fig. 2. Fig. 2 is a diagram showing the configuration of the vehicle 10, and illustrates the network within the vehicle 10.
[0029] The vehicle 10 includes a battery 300, a display 400, a central ECU (Electronic Control Unit) 100, ECUs 200a to 200d, and a vehicle network 500. The battery 300, the display 400, the central ECU 100, and the ECUs 200a to 200d are connected to each other so as to be able to communicate with each other via the vehicle network 500. The vehicle network 500 may be, for example, a Controller Area Network (CAN), Ethernet (registered trademark), a Local Interconnect Network (LIN), or FlexRay (registered trademark).
[0030] At least one piece of software is installed in each of the central ECU 100 and the ECUs 200a to 200d. Installing software means that the software is stored and ready to run. As a result, multiple functions to be implemented in the vehicle 10 are distributed and implemented in the central ECU 100 and the ECUs 200a to 200d.
[0031] Software 1001 is set in the central ECU 100. Software other than the software 1001 may also be set in the central ECU 100. The central ECU 100 starts the software 1001 in response to startup of the vehicle 10, etc. The central ECU 100 functions as a communication interface to the outside of the vehicle 10 in accordance with the software 1001. The central ECU 100 may further have a function as a firewall to the outside of the vehicle 10. The central ECU 100 may have a function to generate information to be displayed on the display 400.
[0032] Software 200a1 is set in ECU 200a. Software other than software 200a1 may also be set in ECU 200a. ECU 200a activates software 200a1 in response to, for example, connection of charging station 30 to battery 300. ECU 200a can manage battery 300 in accordance with software 200a1. ECU 200a has a function of managing battery 300.
[0033] For example, the ECU 200a can grasp the state of the battery 300 (e.g., the remaining charge of the battery) and notify the central ECU 100 of information related to the state of the battery 300. The ECU 200a may request the charging device 601 to start charging when the charging device 601 is connected to the battery 300. The ECU 200a may request the charging device 601 to stop charging when the amount of charge of the battery 300 reaches a predetermined amount.
[0034] Software 200b1 is set in ECU 200b. Software other than software 200b1 may be set in ECU 200b. ECU 200b starts software 200b1 in response to startup of vehicle 10, etc. ECU 200b is capable of executing a first process in accordance with software 200b1. ECU 200b has a first function for executing the first process. The first function may be a function other than the function of central ECU 100 and the function of ECU 200a.
[0035] Software 200c1 is set in ECU 200c. Software other than software 200c1 may be set in ECU 200c. ECU 200c starts software 200c1 in response to startup of vehicle 10, etc. ECU 200c is capable of executing a second process in accordance with software 200c1. ECU 200b has a second function of executing the second process. The second function may be a function other than the function of central ECU 100, the function of ECU 200a, and the first function.
[0036] Software 200d1 is set in ECU 200d. Software other than software 200d1 may be set in ECU 200d. ECU 200d starts software 200d1 in response to startup of vehicle 10, etc. ECU 200d is capable of executing a third process in accordance with software 200d1. ECU 200d has a third function for executing the third process. The third function may be a function other than the function of central ECU 100, the function of ECU 200a, the first function, and the second function.
[0037] The number of ECUs other than the central ECU 100 and the ECU 200a is not limited to three (ECUs 200b to 200d) as illustrated in FIG. 2, but may be two or less, or four or more.
[0038] The battery 300 is capable of storing electric power to be used by the vehicle 10. The battery 300 is connected to a motor (not shown) via a power conversion device (not shown), and is capable of supplying the stored electric power to the motor via the power conversion device.
[0039] The battery 300 includes a charging interface 301 , a charging circuit 302 , and a power storage unit 303 .
[0040] The charging interface 301 functions as an interface for the charging device 601. The charging interface 301 has an inlet. The inlet corresponds to an outlet of the charging device 601. When the charging device 601 has an outlet that complies with a predetermined charging standard (e.g., CHAdeMO standard, GB / T standard, CCS standard, etc.), the charging interface 301 has an inlet that complies with the predetermined charging standard.
[0041] For the sake of simplicity, it is assumed that the outlet of the charging device 601 and the inlet of the charging interface 301 are for rapid charging or primarily operate for rapid charging.
[0042] The charging circuit 302 is connected between the charging interface 301 and the power storage unit 303, and performs predetermined power conversion on the power received by the charging interface 301 and supplies the power to the power storage unit 303. The charging circuit 302 has an AC / DC converter that converts the AC power from the charging interface 301 into DC power, a DC / DC converter that converts the voltage level, and various switches that turn on and off the power supply to the power storage unit 303.
[0043] The power storage unit 303 stores the supplied power. The power storage unit 303 may be a power storage component such as an electric double layer capacitor or an electrolytic capacitor, or may be a secondary battery such as a lead storage battery, a lithium ion battery, a nickel-metal hydride battery, a nickel-cadmium battery, or an all-solid-state battery.
[0044] The display 400 can display predetermined information on a display screen. The display 400 may be disposed in a position in the vehicle cabin where it can be viewed by a user (for example, a driver or a passenger).
[0045] When central ECU 10 receives the information about charging device 601, it generates corresponding display information and supplies it to display 400. Display 400 may display the information about charging device 601 on the display screen in accordance with the display information. The information about charging device 601 includes, for example, information about the location of charging station 30 that includes charging device 601 and information about reservations for use of charging device 601.
[0046] Display 400 may further be capable of receiving input from a user. Display 400 may have buttons for receiving input arranged around the periphery of the display screen, or a touch sensor for detecting input may be stacked on the display screen.
[0047] When the display 400 receives an input from the user, it supplies the input information to the central ECU 10. The central ECU 10 may transmit the input information to the vehicle management server 20 via a wireless communication line.
[0048] The central ECU 100 may be configured as shown in Fig. 3. Fig. 3 is a diagram showing the configuration of the central ECU 100.
[0049] The central ECU 100 includes a server communication unit 101 , a security anomaly management unit 102 , a user terminal communication unit 103 , a vehicle network communication unit 104 , a vehicle state storage unit 105 , a security anomaly storage unit 106 , and a vehicle configuration storage unit 107 .
[0050] Each unit in the central ECU 100 may be realized in software as a module configured within the central ECU 100 by executing software 1001 (see FIG. 2 ). For example, the central ECU 100 may be a system including a processor, a nonvolatile memory, and a volatile memory. The nonvolatile memory stores a program. The processor may read and start the program from the nonvolatile memory when triggered by, for example, power-on of the vehicle 10, and may load modules corresponding to each unit into the volatile memory either collectively at the time of compilation or sequentially as processing progresses. In this way, the processor may operate according to the program. Alternatively, each unit in the central ECU 100 may be realized in hardware as a circuit configured within the central ECU 100. Alternatively, some of the units in the central ECU 100 may be realized in software and the rest may be realized in hardware.
[0051] The server communication unit 101 functions as a communication interface via a wireless communication line. The server communication unit 101 can communicate with the vehicle management server 20 via the wireless communication line. For example, the server communication unit 101 may transmit predetermined information (e.g., management information related to the security of the vehicle 10) to the vehicle management server 20 via the wireless communication line. The server communication unit 101 may receive predetermined information from the vehicle management server 20 via the wireless communication line.
[0052] The server communication unit 101 may further have a function as a firewall against communication access from outside. The server communication unit 101 may have a function of pre-setting authentication information in which sender IDs and passwords are associated with multiple sender IDs, and performing authentication against communication access from outside using the authentication information. The server communication unit 101 may have a function of pre-setting a blacklist including one or more sender IDs to be rejected, or a whitelist including one or more sender IDs to be approved, and performing filtering against communication access from outside using the blacklist or whitelist.
[0053] The security anomaly management unit 102 manages security anomalies in the vehicle 10. Security anomalies in the vehicle 10 may be detected comprehensively by the security anomaly management unit 102, or may be detected by the security anomaly management unit 102 and the other ECUs 200a to 200d, respectively, or may be detected by the vehicle management server 20.
[0054] The security anomaly management unit 102 may manage the presence or absence, number, or recency of a security intrusion history. The security anomaly management unit 102 may manage the number of security errors determined by monitoring information received by the vehicle 10 or information communicated within the vehicle 10.
[0055] For example, the security anomaly management unit 102 may have a function to detect an external cyber-attack on the vehicle 10 and / or an intrusion due to unauthorized operation of malware within the vehicle 10. Alternatively, if each ECU (central ECU 100, ECUs 200a to 200d) has a function to detect an intrusion due to a cyber-attack and / or unauthorized operation of malware, the security anomaly management unit 102 may have a function to integrate the intrusion detection results of each ECU. Alternatively, if the vehicle management server 20 has a function to detect an intrusion due to a cyber-attack and / or unauthorized operation of malware, the security anomaly management unit 102 may have a function to acquire the intrusion detection results of the vehicle management server 20 via a wireless communication line and the server communication unit 101.
[0056] The user terminal communication unit 103 functions as a communication interface via a wireless communication line. The user terminal communication unit 103 can communicate with a user terminal via the wireless communication line. The wireless communication line may be a Bluetooth (registered trademark) line, a Wi-Fi line, or the like. The user terminal may be a smartphone (not shown). For example, when notifying a user (e.g., a driver or a passenger) of predetermined information instead of or together with the display 400, the user terminal communication unit 103 may transmit the predetermined information (e.g., information related to the charging device 601) to the user terminal via the wireless communication line. As a result, if the predetermined information received by the user terminal is displayed on its screen, the predetermined information can be notified to the user.
[0057] The vehicle network communication unit 104 functions as an interface for communication via the vehicle network 500. The vehicle network communication unit 104 is capable of communicating with each unit in the vehicle 10 (see FIG. 2 ) via the vehicle network 500.
[0058] The vehicle state storage unit 105 stores vehicle state information 1051. The vehicle state information 1051 is information relating to the current state of the vehicle 10. The vehicle state information 1051 is information in which items relating to the vehicle state and their contents are associated with each other for a plurality of items. The vehicle state information 1051 may have a data structure as shown in FIG. 4. FIG. 4 is a diagram showing the data structure of the vehicle state information 1051.
[0059] The vehicle state information 1051 includes an item column 1051a and a content column 1051b. The item column 1051a records items related to the current vehicle state. The content column 1051b records content related to the current vehicle state. By referring to the vehicle state information 1051, it is possible to understand the items related to the current vehicle state and the corresponding content.
[0060] 4, the item column 1051a records "battery remaining capacity," "location," and "driving status," and the content column 1051b records "50%, "XXX, YYY," and "driving." By referring to the vehicle status information 1051, it can be determined that the current "battery remaining capacity" is "50%, the current "location" is "XXX, YYY," and the current "driving status" is "driving."
[0061] 3 can access the vehicle state storage unit 105 and update the vehicle state information 1051. The central ECU 100 may communicate with each unit in the vehicle 10 via the vehicle network communication unit 104, collect information about the current vehicle state, and update the vehicle state information 1051 in accordance with the collected information.
[0062] The central ECU 100 may update the vehicle state information 1051 at predetermined intervals.
[0063] The central ECU 100 may monitor the current vehicle state and update the vehicle state information 1051 every time a change in the current vehicle state is detected.
[0064] Alternatively, each ECU (central ECU 100, ECUs 200a to 200d) may monitor the current vehicle state corresponding to the function assigned to it, and may notify the central ECU 100 whenever it detects a change in the current vehicle state. When the central ECU 100 receives a notification of a change in the current vehicle state, it may update the vehicle state information 1051 in accordance with the notification.
[0065] The server communication unit 101 may refer to the vehicle state storage unit 105, acquire vehicle state information 1051 from the vehicle state storage unit 105, and transmit the vehicle state information 1051 to the vehicle management server 20 via a wireless communication line. This allows the vehicle management server 20 to manage the current state of the vehicle 10.
[0066] The security anomaly storage unit 106 stores security anomaly information 1061. The security anomaly information 1061 is information relating to the history (log) of security anomalies in the vehicle 10. The security anomaly information 1061 is information in which a log identifier, the time of occurrence of a security anomaly, the type of security anomaly, and details of the security anomaly are associated with each other for a plurality of logs. The security anomaly information 1061 may have a data structure as shown in FIG. 5. FIG. 5 is a diagram showing the data structure of the security anomaly information 1061.
[0067] The security anomaly information 1061 includes an identifier column 1061a, an occurrence time column 1061b, a security anomaly type column 1061c, and a details column 1061d. The identifier column 1061a records the log identifier (e.g., log number). The occurrence time column 1061b records the time when the security anomaly occurred. The security anomaly type column 1061c records the type of security anomaly. The details column 1061d records details of the security anomaly. By referring to the security anomaly information 1061, it is possible to know the time when the security anomaly occurred, its type, and details for each log.
[0068] In the case of FIG. 5 , “1,” “2,” and “3” are recorded in the identifier column 1061a. “15:30,” “15:45,” and “15:47” are recorded in the occurrence time column 1061b. “Security access anomaly,” “ECU operation anomaly detection,” and “network anomaly detection” are recorded in the security anomaly type column 1061c. “Unauthorized access from XXX,” “Abnormal app behavior at YYY,” and “ZZZ message anomaly” are recorded in the details column 1061d. By referring to log “1” in the security anomaly information 1061, it is possible to know that “unauthorized access from XXX” occurred as a “security access anomaly” at “15:30.” By referring to log “2,” it is possible to know that “Abnormal app behavior at YYY” occurred as an “ECU operation anomaly detection” at “15:45.” By referring to log “3,” it is possible to know that “ZZZ message anomaly” occurred as a “network anomaly detection” at “15:47.”
[0069] 3 can access the security anomaly storage unit 106 and update the security anomaly information 1061. The security anomaly management unit 102 may collect information related to security anomalies in the vehicle 10 and update the security anomaly information 1061 in accordance with the collected information.
[0070] The security anomaly management unit 102 may update the security anomaly information 1061 at predetermined intervals.
[0071] The security anomaly management unit 102 may monitor the current security status of the vehicle 10 and update the security anomaly information 1061 every time a security anomaly of the vehicle 10 is detected.
[0072] Alternatively, each ECU (central ECU 100, ECUs 200a to 200d) may monitor the current security status of vehicle 10 corresponding to the function assigned to it, and notify central ECU 100 whenever a security abnormality is detected. When notified of a security abnormality, central ECU 100 may update security abnormality information 1061 in response to the notification.
[0073] The server communication unit 101 may refer to the security anomaly storage unit 106, acquire security anomaly information 1061 from the security anomaly storage unit 106, and transmit the security anomaly information 1061 to the vehicle management server 20 via a wireless communication line. This allows the vehicle management server 20 to manage security anomalies in the vehicle 10.
[0074] The vehicle configuration storage unit 107 stores vehicle configuration information 1071. The vehicle configuration information 1071 is information related to the current configuration of the vehicle 10. The vehicle configuration information 1071 includes information related to the configuration of software currently set in the vehicle 10. The vehicle configuration information 1071 includes information in which software identifiers, software versions, and their last update dates are associated with each other for a plurality of pieces of software. The vehicle configuration information 1071 may have a data structure as shown in FIG. 6. FIG. 6 is a diagram showing the data structure of the vehicle configuration information 1071.
[0075] The vehicle configuration information 1071 includes an identifier column 1071a, a version column 1071b, and a last update date column 1071c. The identifier column 1071a records the software identifier. The version column 1071b records the software version. The last update date column 1071c records the software last update date. By referring to the vehicle configuration information 1071, it is possible to know the software version currently set in the vehicle 10 and the last update date thereof.
[0076] In the case of FIG. 6 , “1001,” “200a1,” “200b1,” “200c1,” and “200d1” are recorded in the identifier column 1071a. “3.0,” “1.0,” “3.0,” “2.0,” and “1.0” are recorded in the version column 1071b. “2022.6.1,” “2021.10.1,” “2022.6.1,” “2022.3.10,” and “2021.10.1” are recorded in the last update date column 1071c. By referring to the vehicle configuration information 1071, it is possible to know that the version of software “1001” is “3.0” and that the last update date was “2022.6.1.” It is possible to know that the version of software “200a1” is “1.0” and that the last update date was “2022.3.10.” It can be seen that the version of software "200b1" is "3.0" and that the last update date is "2022.6.1", that the version of software "200c1" is "2.0" and that the last update date is "2022.3.10", and that the version of software "200d1" is "1.0" and that the last update date is "2021.10.1".
[0077] 3 can access the vehicle configuration storage unit 107 and update the vehicle configuration information 1071. The central ECU 100 may communicate with other ECUs (ECUs 200a to 200d) in the vehicle 10 via the vehicle network communication unit 104, collect information about software currently set in the central ECU 100 and the other ECUs, and update the vehicle configuration information 1071 based on the collected information.
[0078] The central ECU 100 may update the vehicle configuration information 1071 at predetermined intervals.
[0079] The central ECU 100 may monitor information relating to the software set in each ECU, and update the vehicle configuration information 1071 every time it detects a change in the information relating to the software set in each ECU.
[0080] Alternatively, each ECU (central ECU 100, ECUs 200a to 200d) may monitor information related to the software installed in itself, and notify the central ECU 100 whenever it detects a change in the information related to the installed software. When the central ECU 100 receives a notification of a change in the information related to the installed software, it may update the vehicle configuration information 1071 in accordance with the notification.
[0081] The server communication unit 101 may refer to the vehicle configuration storage unit 107, acquire vehicle configuration information 1071 from the vehicle configuration storage unit 107, and transmit the vehicle configuration information 1071 to the vehicle management server 20 via a wireless communication line. This allows the vehicle management server 20 to manage the current configuration of the vehicle 10 (for example, information related to software currently set in the vehicle 10).
[0082] Note that Figure 6 illustrates vehicle configuration information 1071 in the case where one piece of software 1001, 200a1 to 200d1 is set in each ECU (central ECU 100, ECUs 200a to 200d), but if there is an ECU in which one or more pieces of software are set, information about that software may also be included in vehicle configuration information 1071.
[0083] The vehicle configuration information 1071 may also be protected from tampering. For example, the central ECU 100 stores a private key, and the vehicle management server 20 stores a public key. The private key and the public key form a key pair. The central ECU 100 may generate a hash value of the vehicle configuration information 1071 and encrypt the hash value with the private key to generate a message authentication code. The central ECU 100 may transmit the vehicle configuration information 1071 and the message authentication code to the vehicle management server 20. The vehicle management server 20 generates a hash value of the vehicle configuration information 1071. The vehicle management server 20 decrypts the message authentication code with the public key to restore the hash value. If the generated hash value matches the decrypted hash value, the vehicle management server 20 determines that the vehicle configuration information 1071 has not been tampered with, and can update the management information it holds in accordance with the vehicle configuration information 1071. If the generated hash value does not match the decrypted hash value, the vehicle management server 20 can notify the vehicle 10 that the vehicle configuration information 1071 has been tampered with and send an alert.
[0084] The ECU 200a may be configured as shown in Fig. 7. Fig. 7 is a diagram showing the configuration of the ECU 200a. While Fig. 7 illustrates the configuration of the ECU 200a, the other ECUs 200b to 200d have the same configuration as the ECU 200a.
[0085] The ECU 200a includes an application unit 201a, a communication unit 202a, and a version storage unit 203b.
[0086] Each unit in ECU 200a may be realized in software as a module configured within ECU 200a by executing software 200a1 (see FIG. 2). For example, ECU 200a may be a system including a processor, a nonvolatile memory, and a volatile memory. The nonvolatile memory stores a program. The processor may read and start the program from the nonvolatile memory when triggered by, for example, power-on of vehicle 10, and may load modules corresponding to each unit onto the volatile memory either collectively at the time of compilation or sequentially as processing progresses. In this way, the processor may operate according to the program. Alternatively, each unit in ECU 200a may be realized in hardware as a circuit configured within ECU 200a. Alternatively, some of the units in ECU 200a may be realized in software and the rest may be realized in hardware.
[0087] The communication unit 202a functions as a communication interface via a vehicle network, and is capable of communicating with various components (e.g., the central ECU 100) within the vehicle 10 via the vehicle network.
[0088] The application unit 201a can execute applications corresponding to the functions of the ECU 200a. The application unit 201a can execute applications that manage the battery 300. The application units 201a of the ECUs 200a to 200d may have different processing contents depending on the functions of the ECUs.
[0089] In the case of the ECU 200a, the application unit 201a accesses the battery 300 and acquires the state of the battery 300 (e.g., the remaining charge of the battery). The application unit 201a may notify the central ECU 100 of information about the state of the battery 300 via the communication unit 202a and the vehicle network in response to a request from the central ECU 100 or autonomously when triggered by the establishment of a predetermined condition. The predetermined condition may include a change in the state of the battery 300 (e.g., the remaining charge of the battery) exceeding a predetermined amount. As a result, the central ECU 100 can update the vehicle state information 1051 (see FIG. 4 ) stored in the vehicle state storage unit 105 with the notified information about the state of the battery 300.
[0090] When charging device 601 is connected to battery 300, application unit 201a may receive a connection signal indicating the connection, and in response to the connection signal, supply a charging start request to charging device 601 via battery 300. In this way, charging device 601 may start supplying power to battery 300 in response to the charging start request.
[0091] The application unit 201a may monitor the charge amount while the battery 300 is being charged, and when the charge amount of the battery 300 reaches an upper limit threshold, may supply a charge end request to the charging device 601 via the battery 300. In response to the charge end request, the charging device 601 may thereby end the supply of power to the battery 300.
[0092] The version storage unit 203a stores version information 203a1. The version information 203a1 is information relating to the version of software set in the ECU 200a. The version information 203a1 is information in which a software identifier is associated with its version. The version information 203a1 may have a data structure as shown in FIG. 8. FIG. 8 is a diagram showing the data structure of the version information 203a1.
[0093] The version information 203a1 includes an identifier field 203a1a and a version field 203a1b. The identifier field 203a1a stores a software identifier. The version field 203a1b stores a software version. By referring to the version information 203a1, it is possible to know the version of the software set in the ECU 200a.
[0094] In the case of Figure 8, "200a1" is recorded in the identifier field 203a1a. "1.0" is recorded in the version field 203a1b. By referring to the version information 203a1, it can be determined that the version of the software "200a1" set in the ECU 200a is "1.0".
[0095] 7 can access the version storage unit 203a and update the version information 203a1. When the software 200a1 configured in the ECU 200a is upgraded, the ECU 200a may obtain the upgraded version and update the version information 203a1 in accordance with the obtained result.
[0096] The ECU 200a may notify the central ECU 100 of the version information 203a1 via the communication unit 202a and the vehicle network in response to a request from the central ECU 100 or autonomously when a predetermined condition is met. The predetermined condition may be a software version upgrade. As a result, the central ECU 100 may update the vehicle configuration information 1071 (see FIG. 6 ) stored in the vehicle configuration storage unit 107 using the notified version information 203a1.
[0097] Note that Figure 8 illustrates the configuration of version information 203a1 when one piece of software 200a1 is set in ECU 200a, but if one or more pieces of software are set in ECU 200a, information about those pieces of software may also be included in version information 203a1.
[0098] The vehicle management server 20 may be configured as shown in Fig. 9. Fig. 9 is a diagram showing the configuration of the vehicle management server 20.
[0099] The vehicle management server 20 includes a communication unit 501 , a charging point search unit 502 , a security level determination unit 503 , a server access information storage unit 504 , and a vehicle information storage unit 505 .
[0100] The communication unit 501 may function as a communication interface via a wireless communication line, or may function as a communication interface via a wireless communication line and / or a wired communication line. The communication unit 501 is capable of communicating with the vehicle 10 via a wireless communication line. The communication unit 501 is capable of communicating with the station management server 40 via a wireless communication line and / or a wired communication line.
[0101] The charge point searching unit 502 searches for a charge point in response to a search request from the vehicle 10 or autonomously when triggered by the establishment of a predetermined condition. The predetermined condition may be that the remaining charge of the vehicle 10 falls below a lower limit threshold. The charge point includes the location of a charge station 30 that includes one or more charging devices 601. The charge point searching unit 502 may search for a charge point by making an inquiry to the station management server 40.
[0102] The security level determination unit 503 determines the security level of the vehicle 10 according to management information related to the security of the vehicle 10. The management information of the vehicle 10 may include information as to whether the version of software installed in the vehicle 10 is the latest version. The management information of the vehicle 10 may include information as to whether the vehicle 10 has been previously compromised by a cyber-attack and / or unauthorized operation of malware. The management information of the vehicle 10 may include information as to whether a security monitoring service is enabled for the vehicle 10.
[0103] The security level determination unit 503 may determine the security level of the vehicle 10 using a continuous numerical value or using a rank in multiple stages.
[0104] When making the determination using a continuous numerical value, the security level determination unit 503 may obtain a score for each of a plurality of evaluation items and total or average the scores of the plurality of evaluation items to quantify the security level. The plurality of evaluation items may include whether the version of the software installed in the vehicle 10 is the latest version, whether the vehicle 10 has been previously compromised by a cyber attack and / or unauthorized operation of malware, whether a security monitoring service is enabled for the vehicle 10, etc.
[0105] When making a judgment based on multiple ranks, the security level judgment unit 503 may rank the security level of the vehicle 10 in multiple stages while judging multiple evaluation items in stages. The multiple stages may be, for example, three stages: low, medium, and high.
[0106] The server access information holding unit 504 holds server access information 5041. The server access information 5041 includes access information to the station management server 40 to which inquiries are directed. The server access information 5041 is information in which the identifier of the station management server 40 is associated with its access path. The server access information 5041 may have a data structure as shown in FIG. 10. FIG. 10 is a diagram showing the data structure of the server access information 5041.
[0107] The server access information 5041 includes an identifier column 5041a and an access path column 5041b. The identifier column 5041a records the identifier of the station management server 40. The access path column 5041b records the access path to the station management server 40. By referring to the server access information 5041, the access path to the station management server 40 can be determined.
[0108] 10, "40" is recorded in the identifier column 5041a, and "https: / / server40" is recorded in the access path column 5041b. By referring to the server access information 5041, it can be determined that the access path to the station management server "40" is "https: / / server40".
[0109] The charge point searching unit 502 receives a search request for a charge point from the vehicle 10. The search request may include the current location of the vehicle 10. In response to the search request, the charge point searching unit 502 generates a station search request that requests a search for a charge station 30. The station search request may include the current location of the vehicle 10. The charge point searching unit 502 accesses the server access information holding unit 504, refers to the server access information 5041, and acquires an access path to the station management server 40. In accordance with the acquired access path, the charge point searching unit 502 transmits the station search request to the station management server 40 via the communication unit 501, a wireless communication line, and / or a wired communication line, and waits for a response. When the charge point searching unit 502 receives station information as a response, it transmits the station information to the vehicle 10 via the communication unit 501 and a wireless communication line. The station information includes information about the location of the charge station 30 searched for by the station management server 40. As a result, in the vehicle 10, information about the location of the charging station 30 according to the station information can be displayed on the display 400, and the information about the location of the charging station 30 can be notified to the user (e.g., the driver or passenger).
[0110] The vehicle information holding unit 505 holds vehicle information 5051. The vehicle information 5051 includes management information related to the security of the vehicle 10. The vehicle information 5051 is information in which the identifier of the vehicle 10, items related to the attributes of the vehicle 10, and the status of the vehicle 10 are associated with each other. The vehicle information 5051 may have a data structure as shown in FIG. 11. FIG. 11 is a diagram showing the data structure of the vehicle information 5051.
[0111] The vehicle information 5051 includes an identifier column 5051a, an item column 5051b, and a status column 5051c. The identifier column 5051a records the identifier of the vehicle 10. The item column 1051a records items related to the attributes of the vehicle 10. The status column 5051c records the status related to the attributes of the vehicle 10. By referring to the vehicle information 5051, it is possible to understand the current status of the attributes of the vehicle 10.
[0112] In the case of FIG. 11 , "10" is recorded in the identifier column 5051a. "Software version," "security intrusion history," "security monitoring," "remaining battery charge," and "location" are recorded in the item column 5051b. "Latest (1001: ver. 3.0, ...)," "None," "Yes," "50%," and "XXX, YYY" are recorded in the status column 5051c. By referring to the vehicle information 5051, it is possible to know that for vehicle "10," the "software version" is "latest," the "security intrusion history" is "none," the "security monitoring" service is "Yes," the "remaining battery charge" is "50%, and the current "location" is "XXX, YYY."
[0113] 9 can access the vehicle information storage unit 505 and update the vehicle information 5051. The vehicle management server 20 can communicate with the vehicle 10, collect vehicle status information 1051 (see FIG. 4), security abnormality information 1061 (see FIG. 5), and vehicle configuration information 1071 (see FIG. 6), and update the vehicle information 5051 according to the collected information.
[0114] The vehicle management server 20 may update the vehicle information 5051 at predetermined intervals.
[0115] The vehicle management server 20 may monitor the vehicle status information 1051, security anomaly information 1061, and vehicle configuration information 1071, and update the vehicle information 5051 each time a change in the vehicle status information 1051, security anomaly information 1061, or vehicle configuration information 1071 is detected.
[0116] The security level determination unit 503 may access the vehicle information storage unit 505, refer to the vehicle information 5051, and determine the security level of the vehicle 10 according to the vehicle information 5051. The security level determination unit 503 may determine the security level of the vehicle 10 according to the states of the items "software version," "security intrusion history," and "security monitoring," and add the determination result to the vehicle information 5051.
[0117] 11, for vehicle "10," the "software version" is "latest," there is "no security intrusion history," and the "security monitoring" service is "present," so security level determination unit 503 determines that the "security level" is "high." In response to this determination, security level determination unit 503 adds the item "security level" and the status "high" to vehicle information 5051 for vehicle "10."
[0118] The communication unit 501 may refer to the vehicle information storage unit 505, acquire vehicle information 5051 from the vehicle information storage unit 505, and transmit the vehicle information 5051 to the station management server 40 via a wireless communication line and / or a wired communication line. The vehicle information 5051 includes the determination result of the security level of the vehicle 10. This allows the station management server 40 to generate station information to be provided to the vehicle 10 according to the current security level of the vehicle 10.
[0119] When the vehicle management server 20 receives a reservation request from the vehicle 10 requesting a reservation for use of the charging device 601 , the vehicle management server 20 may transfer the received reservation request to the station management server 40 .
[0120] The station management server 40 can be configured as shown in Fig. 12. Fig. 12 is a diagram showing the configuration of the station management server 40.
[0121] The station management server 40 includes a communication unit 701 , a scheduling unit 702 , a station search unit 703 , a billing amount determination unit 704 , a station information storage unit 705 , and a power price storage unit 706 .
[0122] The communication unit 701 may function as a communication interface via a wireless communication line and / or a wired communication line. The communication unit 701 can communicate with the vehicle management server 20 via a wireless communication line and / or a wired communication line. The communication unit 701 can communicate with the charging station 30 via a wireless communication line and / or a wired communication line.
[0123] The station search unit 703 searches for information on available charging stations 30 under its management in response to a station search request from the vehicle management server 20. The station search request may include the current location of the vehicle 10. The station search unit 703 may search for available charging stations 30 that are located within a predetermined distance from the current location of the vehicle 10. The station search unit 703 generates station information that includes the locations of the found charging stations 30.
[0124] The station search unit 703 may change the time at which the vehicle 10 can make a reservation for the searched charging station 30 depending on the security level of the vehicle 10 .
[0125] For example, when the security level of the vehicle 10 is a first level, the station search unit 703 determines the time during which the vehicle 10 can reserve the charging station 30 to be a first time. In response to the time during which the vehicle 10 can reserve the charging station 30 being determined to be the first time, the station search unit 703 generates station information including information about the first time.
[0126] When the security level of the vehicle 10 is the second level, the station search unit 703 determines the time during which the vehicle 10 can reserve the charging station 30 to be the second time. The second level is higher than the first level. The second time is longer than the first time. The second time includes the first time and includes a time further in the future than the first time. In response to the time during which the vehicle 10 can reserve being determined to be the second time, the station search unit 703 generates station information including information about the second time. This makes it possible to generate station information that treats the vehicle 10 more preferentially than when the security level of the vehicle 10 is the first level.
[0127] As a response to the station search request, the station search unit 703 returns the station information to the vehicle management server 20 via the communication unit 701, a wireless communication line, and / or a wired communication line. The vehicle management server 20 can transfer the station information to the vehicle 10, and the station information can be displayed on the display 400 of the vehicle 10, whereby the station information can be notified to a user (for example, a driver or a passenger).
[0128] When the scheduling unit 702 receives a reservation request from the vehicle 10 via the vehicle management server 20, it identifies a charging station 30 in response to the reservation request. The scheduling unit 702 acquires information about the identified charging station 30. The scheduling unit 702 uses the acquired information to perform a predetermined calculation for the identified charging station 30 and generate a reservation schedule. The scheduling unit 702 may calculate the charging start time, charging speed, charging amount, etc. of the charging station 30 in response to the reservation request to generate the reservation schedule. The scheduling unit 702 may further calculate an estimated usage fee and include it in the reservation schedule. The scheduling unit 702 may further adjust the reservation schedule, such as reducing the charging amount by a predetermined percentage, depending on the status of the charging station 30 (e.g., a power shortage situation).
[0129] The scheduling unit 702 may receive the security level of the vehicle 10 from the vehicle management server 20, change the charging speed according to the security level of the vehicle 10, and generate a reservation schedule.
[0130] For example, when the security level of the vehicle 10 is a first level, the scheduling unit 702 determines the charging rate of the charging station 30 to be a first rate. In response to the determination of the charging rate as the first rate, the scheduling unit 702 performs calculations using the charging rate of the charging station 30 as the first rate and generates a reservation schedule.
[0131] When the security level of the vehicle 10 is the second level, the scheduling unit 702 determines the charging rate of the charging device to be the second rate. The second level is higher than the first level. The second rate is higher than the first rate. In response to determining the charging rate to be the second rate, the scheduling unit 702 performs calculations using the charging rate of the charging station 30 as the second rate and generates a reservation schedule. This makes it possible to generate a reservation schedule that gives more preferential treatment to the vehicle 10 than when the security level of the vehicle 10 is the first level.
[0132] The scheduling unit 702 may generate a reservation schedule by calculating and changing the discount rate for the charge station 30 usage fee depending on the security level of the vehicle 10 .
[0133] For example, when the security level of the vehicle 10 is a first level, the scheduling unit 702 determines the discount rate for the usage fee of the charging station 30 by the vehicle 10 to be a first rate. In response to determining the discount rate to be the first rate, the scheduling unit 702 calculates an amount obtained by discounting an amount based on the standard electricity price by the first rate. The scheduling unit 702 includes the calculated amount in the reservation schedule as an estimated amount of the usage fee.
[0134] When the security level of the vehicle 10 is the second level, the scheduling unit 702 determines the discount rate for the usage fee of the charging station 30 by the vehicle 10 to be a second rate. The second level is higher than the first level. The second rate is higher than the first rate. In response to determining the discount rate to be the second rate, the scheduling unit 702 calculates an amount obtained by discounting an amount based on the standard electricity price by the second rate. The scheduling unit 702 includes the calculated amount in the reservation schedule as an estimated amount of the usage fee. This makes it possible to generate a reservation schedule that treats the vehicle 10 more favorably than when the security level of the vehicle 10 is the first level.
[0135] The scheduling unit 702 transmits the reservation schedule to the charging station 30 via a wireless communication line and / or a wired communication line. As a result, the reservation schedule can be registered in the charging station 30.
[0136] If there is a prior booking at charging station 30, users can wait for a reservation, which is basically on a first-come, first-served basis, but users with a higher security level are given priority and enter the reservation waiting queue. At charging station 30, the higher the security level, the more reservation slots can be secured. For example, it may be possible to reserve different time slots, with one slot for a "low" security level, three slots for a "medium" security level, and up to five slots for a "high" security level.
[0137] As a response to the reservation request, the scheduling unit 702 returns the reservation schedule to the vehicle management server 20 via the communication unit 701, a wireless communication line, and / or a wired communication line. The vehicle management server 20 can transfer the reservation schedule to the vehicle 10, and the reservation schedule can be displayed on the display 400 of the vehicle 10, thereby notifying the user (e.g., the driver or a passenger) of the reservation schedule.
[0138] For example, when the security level of vehicle 10 is the first level, display 400 may display a reservation schedule as shown in Fig. 13(a). Fig. 13 is a diagram showing a reservation schedule notified to vehicle 10. In the case of Fig. 13(a), an example reservation schedule is shown that includes an expected charging time of 1 hour, an average output of charging device 601 of 20 kW, a discount rate of 0%, and an expected usage fee of 400 yen.
[0139] Alternatively, when the security level of vehicle 10 is a second level higher than the first level, display 400 may display a reservation schedule as shown in Fig. 13(b). In the case of Fig. 13(b), an example reservation schedule is shown including an expected charging time of 30 minutes, an average output of charging device 601 of 40 kW, a discount rate of 10% (a discount amount of -40 yen), and an expected usage fee of 360 yen. In this way, a reservation schedule determined to treat vehicle 10 more favorably than when the security level of vehicle 10 is the first level can be announced.
[0140] 12 determines the amount to be charged to the vehicle 10 for the use of the charging device 601 by the vehicle 10. The charging amount determination unit 704 receives usage history information indicating the usage history of the charging device 601 by the vehicle 10 from the charging station 30 via a wireless communication line and / or a wired communication line. The charging amount determination unit 704 calculates the amount to be charged to the vehicle 10 according to the usage history information and generates billing information including the amount to be charged.
[0141] The charge amount determination unit 704 may receive the security level of the vehicle 10 from the vehicle management server 20, change the discount rate for the usage fee of the charging station 30 depending on the security level of the vehicle 10, and generate billing information including the charge amount.
[0142] For example, when the security level of the vehicle 10 is a first level, the charge amount determination unit 704 determines the discount rate for the usage fee of the charging station 30 by the vehicle 10 to be a first rate. In response to the discount rate being determined to be the first rate, the charge amount determination unit 704 calculates an amount obtained by discounting the amount based on the standard electricity price by the first rate. The charge amount determination unit 704 generates billing information with the calculated amount as the amount to be charged to the vehicle 10.
[0143] When the security level of the vehicle 10 is at the second level, the billing amount determination unit 704 determines the discount rate for the usage fee of the charging station 30 by the vehicle 10 to be a second rate. The second level is higher than the first level. The second rate is higher than the first rate. In response to the discount rate being determined to be the second rate, the scheduling unit 702 calculates an amount obtained by discounting the amount based on the standard electricity price by the second rate. The billing amount determination unit 704 generates billing information with the calculated amount as the amount to be charged to the vehicle 10. This makes it possible to generate billing information that treats the vehicle 10 more favorably than when the security level of the vehicle 10 is at the first level.
[0144] The charge amount determination unit 704 may transmit the charge information to the charging station 30 via a wireless communication line and / or a wired communication line. As a result, the charge amount according to the charge information may be displayed on the display of the charging device 601 at the charging station 30, and the charge amount may be notified to a user (e.g., a driver or a passenger).
[0145] Alternatively, the charge amount determination unit 704 may transmit the charge information to the vehicle management server 20 via a wireless communication line and / or a wired communication line. The vehicle management server 20 can transfer the charge information to the vehicle 10, and the charge information can be displayed on the display 400 of the vehicle 10, thereby notifying the user (e.g., the driver or a passenger) of the charge amount.
[0146] When payment is made offline according to the notified charge amount, the user can pay the charge amount directly at charging station 30, and the settlement of the charge amount to vehicle 10 is completed.
[0147] When payment is made online according to the notified charge amount, the user inputs an instruction to select online payment at the vehicle 10, and the instruction is transmitted from the vehicle 10 to the charging station 30. In response to the instruction, the charging station 30 enters a state in which it can accept input of online payment information. The user performs an operation such as inputting online payment information at the charging station 30, and in response, the online payment information can be transmitted from the charging station 30 to the vehicle management server 20 via the station management server 40. If the vehicle management server 20 has been previously entrusted by the owner (e.g., the driver) of the vehicle 10 to act as an agent for online payments, the vehicle management server 20 executes online payment according to the online payment information on behalf of the owner of the vehicle 10. This completes the settlement of the charge amount to the vehicle 10.
[0148] The station information storage unit 705 stores station information 7051. The station information 7051 is management information for the charging station 30. The station information 7051 is information in which an identifier of the charging station 30 is associated with items related to the attributes of the charging station 30 and their contents. The station information 7051 may have a data structure as shown in FIG. 14. FIG. 14 is a diagram showing the data structure of the station information 7051.
[0149] The station information 7051 includes an identifier column 7051a, an item column 7051b, and a content column 7051c. The identifier column 7051a records the identifier of the charging station 30. The item column 7051a records items related to the attributes of the charging station 30. The content column 7051c records content related to the attributes of the charging station 30. By referring to the station information 7051, it is possible to grasp the current content related to the attributes of the charging station 30.
[0150] In the case of FIG. 14 , "30" is recorded in the identifier column 7051a. "Location," "Access Destination," "Power Utilization Rate," and "Schedule" are recorded in the item column 7051b. "X1, Y1," "https: / / station30," "40%," "Charging Device 601a: 10:00 to 15:00," "Charging Device 601b: 12:00 to 14:00," and "Charging Device 601c: 11:00 to 15:00" are recorded in the content column 7051c. By referring to the station information 7051, it is possible to determine that for charging station "30," the "Location" is "X1, Y1," the "Access Destination" via communication is "https: / / station30," the current "Power Utilization Rate" is "40%, and the currently reserved reservation "Schedule" includes "Charging Device 601a: 10:00 to 15:00," "Charging Device 601b: 12:00 to 14:00," and "Charging Device 601c: 11:00 to 15:00."
[0151] 12 can access the station information storage unit 705 and update the station information 7051. The station management server 40 can communicate with the charging station 30, collect information registered in the charging station 30, and update the station information 7051 in accordance with the collected information.
[0152] The station management server 40 may update the station information 7051 at predetermined intervals.
[0153] The station management server 40 may monitor the information registered in the charging station 30 and update the station information 7051 every time a change in the information registered in the charging station 30 is detected.
[0154] The power price holding unit 706 holds power price information 7061. The power price information 7061 is information on power prices that is referenced when calculating the usage fee for the charging device 601. The power price information 7061 is information in which time periods are associated with prices per unit of power. The power price information 7061 may have a data structure as shown in FIG. 15 . FIG. 15 is a diagram showing the data structure of the power price information 7061.
[0155] The electricity price information 7061 includes a time period column 7061a and a price column 7061b. The time period column 7061a records the time period during which the charging station 30 is used. The price column 7061b records the standard price per unit of power (e.g., per kWh) charged at the charging station 30. By referring to the electricity price information 7061, it is possible to ascertain the standard price for each time period during which the charging station 30 is used.
[0156] 15 , "8 to 18," "18 to 22," and "22 to 8" are recorded in the time period column 7061a, and "30 yen," "20 yen," and "10 yen" are recorded in the price column 7061b. By referring to the power price information 7061, it is possible to know that if charging station 30 is used from "8 to 18," the standard price per unit of power is "30 yen," if charging station 30 is used from "18 to 22," the standard price per unit of power is "20 yen," and if charging station 30 is used from "22 to 8," the standard price per unit of power is "10 yen."
[0157] The station management server 40 may obtain basic information on electricity prices from the electric power company's server (not shown) at predetermined intervals (e.g., daily) and update the electricity price information 7061 according to the basic information on electricity prices.
[0158] The station management server 40 may update the power price information 7061 in real time. The station management server 40 may receive basic information on the power price from the power company's server when the power price is changed, and update the power price information 7061 in response to receiving the basic information on the power price.
[0159] In Figure 15, three time periods are shown as an example of a day divided into three parts, but the time periods included in the electricity price information 7061 may be two time periods divided into two parts, or four or more time periods divided into four or more parts.
[0160] The charging station 30 may be configured as shown in Fig. 16. Fig. 16 is a diagram showing the configuration of the charging station 30.
[0161] Charging station 30 has multiple charging devices 601a to 601c, a station management unit 602, a communication unit 603, and a station network 604. Multiple charging devices 601a to 601c, station management unit 602, and communication unit 603 are communicably connected via station network 604. Note that the number of charging devices 601 included in charging station 30 is not limited to three (charging devices 601a to 601c) as illustrated in Fig. 16, and may be two or less, or four or more.
[0162] Each charging device 601 can be connected to the battery 300 of the vehicle 10. Each charging device 601 is connected to the power distribution network 50 via a station management unit 602 and a communication unit 603, and can receive power supply from the power distribution network 50 via the communication unit 603 and the station management unit 602. When the battery 300 of the vehicle 10 is connected to the charging device 601, the charging device 601 can charge the battery 300 in accordance with control by the station management unit 602.
[0163] The charging device 601 has a charging interface 6011 and a charging circuit 6012. The charging interface 6011 has an outlet corresponding to the charging interface 301 of the battery 300. The outlet complies with a predetermined charging standard (for example, the CHAdeMO standard, the GB / T standard, the CCS standard, etc.).
[0164] The charging circuit 6012 can turn on and off the power supply to the charging interface 6011 in accordance with the control of the station management unit 602. The charging circuit 6012 can adjust the output of the power supply to the charging interface 6011 in accordance with the control of the station management unit 602.
[0165] The communication unit 603 functions as a communication interface with the outside of the charging station 30. The communication unit 603 is capable of communicating with the station management server 40 via a wireless communication line and / or a wired communication line.
[0166] The communication unit 603 functions as an interface with the power distribution network 50. The communication unit 603 supplies the power received from the power distribution network 50 to each of the plurality of charging devices 601a to 601c via the station management unit 602.
[0167] The station management unit 602 manages the usage status (output, usage time) and future usage schedule of each of the charging devices 601a to 601c.
[0168] When the station management unit 602 receives a reservation schedule from the station management server 40, it registers the reservation schedule. The station management unit 602 selects one of the charging devices 601a to 601c and makes it operable in accordance with the reservation schedule. When the vehicle 10 is connected to the charging device 601a, for example, and the station management unit 602 receives a charging start request from the vehicle 10 via the charging device 601a, the station management unit 602 controls the charging device 601a in response to the charging start request to supply power under conditions in accordance with the reservation schedule. In this way, the vehicle 10 can be charged.
[0169] When the station management section 602 receives an inquiry from the station management server 40, it returns the registered information (e.g., reservation schedule) in response to the inquiry. This enables the station management server 40 to access the station information holding section 705 and update the station information 7051 (see FIG. 14 ) held therein.
[0170] When the station management unit 602 receives billing information from the station management server 40, it displays the billing amount according to the billing information on a display (not shown) of the charging station 30. This allows the user (e.g., the driver or a passenger) of the vehicle 10 that has charged using the charging device 601 to be notified of the billing amount for using the charging device 601.
[0171] As described above, in the embodiment, in the charge management system 1, the station management server 40 determines parameters related to charging of the vehicle 10 according to the security level of the vehicle 10. The station management server 40 may determine the parameters such that the higher the security level of the vehicle 10, the more favorable the conditions under which the vehicle 10 can charge. According to the determined parameters, the charge station 30 performs processing related to the vehicle 10's use of the charging device 601. In this way, the charge management system 1 can provide preferential treatment to the vehicle 10 according to the security level regarding the use of the charging device 601, and can provide the user of the vehicle 10 with an incentive to improve security and encourage them to ensure security. As a result, the security of the vehicle 10 can be ensured by the user of the vehicle 10 taking security measures, such as updating the software used in the vehicle 10.
[0172] Furthermore, in the embodiment, in the charge management system 1, the communication unit 701 of the station management server 40 receives a request related to the vehicle 10 using the charging device 601. The scheduling unit 702, the station search unit 703, and the billing amount determination unit 704 of the station management server 40 control the charging station 30 so as to perform processing related to the vehicle 10 using the charging device 601. In this way, the charge management system 1 can perform processing related to the vehicle 10 using the charging device 601 in response to the request related to the use of the charging device 601.
[0173] Furthermore, in the embodiment, in the charge management system 1, the security level determination unit 503 of the vehicle management server 20 determines the security level of the vehicle 10 according to management information related to the security of the vehicle 10. The scheduling unit 702, the station search unit 703, and the charge amount determination unit 704 of the station management server 40 determine parameters related to charging of the vehicle 10 according to the determination result of the security level. The scheduling unit 702, the station search unit 703, and the charge amount determination unit 704 perform processing related to the vehicle 10's use of the charging device 601 according to a request related to the use of the charging device 601 and the determined parameters. In this way, the charge management system 1 can provide preferential treatment to the vehicle 10 regarding the use of the charging device 601 according to the level of the security level.
[0174] Furthermore, in the embodiment, in the charge management system 1, when the security level of the vehicle 10 is a first level, the station search unit 703 of the station management server 40 determines the time during which the vehicle 10 can reserve the charging device 601 to be a first time. When the security level of the vehicle 10 is a second level higher than the first level, the station search unit 703 determines the time during which the vehicle 10 can reserve the charging device 601 to be a second time longer than the first time. When the time is determined to be the first time, the communication unit 701 of the station management server 40 notifies the vehicle 10 of information about the first time. When the time is determined to be the second time, the communication unit 701 notifies the vehicle 10 of information about the second time. In this way, the charge management system 1 can provide preferential treatment to the vehicle 10 depending on the security level with respect to the time during which the charging device 601 can be used, and notify the vehicle 10 of this.
[0175] Furthermore, in the embodiment, in the charge management system 1, when the security level of the vehicle 10 is a first level, the scheduling unit 702 of the station management server 40 determines the charging rate of the charging device 601 to be a first rate. When the security level of the vehicle 10 is a second level higher than the first level, the scheduling unit 702 determines the charging rate of the charging device 601 to be a second rate higher than the first rate. When the charging rate is determined to be the first rate, the scheduling unit 702 controls the charging device 601 to charge the vehicle 10 at the first rate. When the charging rate is determined to be the second rate, the scheduling unit 702 controls the charging device 601 to charge the vehicle 10 at the second rate. In this way, the charge management system 1 can provide preferential treatment to the vehicle 10 with respect to the charging rate of the charging device 601 depending on the level of the security level.
[0176] Furthermore, in the embodiment, in the charge management system 1, when the security level of the vehicle 10 is a first level, the scheduling unit 702 of the station management server 40 determines the discount rate of the usage fee for the charging device 601 by the vehicle 10 to be a first rate. When the security level of the vehicle 10 is a second level higher than the first level, the scheduling unit 702 determines the discount rate of the usage fee for the charging device 601 by the vehicle 10 to be a second rate higher than the first rate. When the discount rate is determined to be the first rate, the communication unit 701 of the station management server 40 notifies the vehicle 10 of the amount obtained by discounting the first rate. When the discount rate is determined to be a second rate, the communication unit 701 notifies the vehicle 10 of the amount obtained by discounting the second rate. In this way, the charge management system 1 can provide preferential treatment to the vehicle 10 with respect to the usage fee for the charging device 601 depending on the security level and notify the vehicle 10 of this.
[0177] Furthermore, in the embodiment, in the charge management system 1, the vehicle information 5051 held in the vehicle information holding unit 505 of the vehicle management server 20 includes at least one of information related to the version of software set in the vehicle 10, whether security monitoring is performed on the vehicle 10, whether a security intrusion has occurred on the vehicle 10, the number of security intrusions on the vehicle 10, and the recency of the security intrusions on the vehicle 10. This allows the vehicle management server 20 to determine the security level of the vehicle 10 according to the vehicle information 5051.
[0178] The security levels may be standardized so that the criteria for determining the security levels are unified. The security level standards may be set in advance in the vehicle management server 20. The vehicle management server 20 can determine the security level of the vehicle 10 in accordance with the security level standards.
[0179] When the vehicle management server 20 determines the security level of the vehicle 10, the vehicle management server 20 may issue an electronic certificate including the security level determination result and transmit the electronic certificate to the vehicle 10. In this case, when the central ECU 100 of the vehicle 10 receives the electronic certificate, the central ECU 100 stores the electronic certificate. This allows the vehicle 10 to present the electronic certificate to the charging station 30 when using the charging device 601, for example. In response to this, the vehicle 10 may be able to use the charging device 601 under favorable conditions according to the security level indicated in the electronic certificate.
[0180] Although not shown, the charge management system 1 may include a plurality of station management servers 40. In this case, the server access information storage unit 504 of the vehicle management server 20 may include access information of the plurality of station management servers 40.
[0181] (First Modification of the Embodiment) The charge management system 1 may have a plurality of charge stations 30a to 30c, as shown in Fig. 17. Fig. 17 is a diagram showing the configuration of the charge management system 1 according to the first modification of the embodiment. Fig. 17 illustrates a configuration in which the charge management system 1 has three charge stations 30a to 30c, but the number of charge stations included in the charge management system 1 may be two or less, or four or more.
[0182] In the charge management system 1, the station management server 40 and the plurality of charging stations 30a to 30c are communicatively connected via wireless communication lines and / or wired communication lines. The station management server 40 can manage the plurality of charging stations 30a to 30c.
[0183] In this case, the charge management system 1 may make it easier for the vehicle 10 to find a charging environment depending on the security level of the vehicle 10. The charge management system 1 may increase the number of charging stations 30 that can be searched for by the reservation application software depending on the security level of the vehicle 10. The charge management system 1 may expand the search range for charging stations 30 by the reservation application software depending on the security level of the vehicle 10.
[0184] 12 , the station search unit 703 may receive the security level of the vehicle 10 from the vehicle management server 20, and may search for charging stations 30 that are available to the vehicle 10 by changing the distance range to the charging station 30 depending on the security level of the vehicle 10. The distance range refers to the range contained in a circle centered on the vehicle 10 and having a radius corresponding to the distance.
[0185] For example, when the security level of the vehicle 10 is a first level, the station search unit 703 determines the distance range to charging stations 30 available to the vehicle 10 to be a first range. In response to the distance range being determined to be the first range, the station search unit 703 searches for charging stations 30 available to the vehicle 10 within the first range. The station search unit 703 can search for multiple charging stations 30 included in the first range. The station search unit 703 generates station information including the positions of each of the multiple charging stations 30 included in the first range.
[0186] When the security level of the vehicle 10 is the second level, the station search unit 703 determines the distance range to charging stations 30 available to the vehicle 10 to be a second range. The second level is higher than the first level. The second range is wider than the first range. In response to the distance range being determined to be the second range, the station search unit 703 searches for charging stations 30 available to the vehicle 10 within the second range. The station search unit 703 can search for multiple charging stations 30 included in the second range. The station search unit 703 generates station information including the respective positions of the multiple charging stations 30 included in the second range. This makes it possible to generate station information that treats the vehicle 10 more preferentially than when the security level of the vehicle 10 is the first level.
[0187] As a response to the station search request, the station search unit 703 returns the station information to the vehicle management server 20 via the communication unit 701, a wireless communication line, and / or a wired communication line. The vehicle management server 20 can transfer the station information to the vehicle 10, and the vehicle 10 can display the station information on the display 400, thereby notifying the user (e.g., the driver or a passenger) of the station information including the locations of each of the multiple available charging stations 30.
[0188] For example, when the security level of the vehicle 10 is the first level, the display 400 may display station information as shown in Fig. 18(a). Fig. 18 is a diagram showing station information notified to the vehicle 10 in a first modified example of the embodiment. In the case of Fig. 18(a), station information including the fact that the distance range is R1 and the number of available charging stations 30 is four is illustrated.
[0189] Alternatively, when the security level of the vehicle 10 is a second level higher than the first level, the display 400 may display station information such as that shown in FIG. 18( b). In the case of FIG. 18( b), station information including the fact that the distance range is R2 and the number of available charging stations 30 is seven is illustrated. The distance range R2 is wider than the distance range R1. The distance range R2 is a circle with a larger radius than the distance range R1. This allows the searched station information to be presented in a manner that treats the vehicle 10 more favorably than when the security level of the vehicle 10 is the first level.
[0190] In this way, the charge management system 1 makes it easier for the vehicle 10 to find a charging environment depending on the security level of the vehicle 10. This also makes it possible to provide preferential treatment to the vehicle 10 depending on the security level, and to provide an incentive to the user of the vehicle 10 to improve security and encourage the user to ensure security.
[0191] Furthermore, in the charge management system 1, when the security level of the vehicle 10 is a first level, the station search unit 703 of the vehicle management server 20 determines the distance range to a charging device 601 available to the vehicle 10 to be a first range. When the security level of the vehicle 10 is a second level higher than the first level, the station search unit 703 determines the distance range to a charging device 601 available to the vehicle 10 to be a second range wider than the first range. When the distance range is determined to be the first range, the communication unit 701 of the station management server 40 notifies the vehicle 10 of information about charging devices 601 present within the first range. When the distance range is determined to be the second range, the communication unit 701 notifies the vehicle 10 of information about charging devices 601 present within the second range. This allows the charge management system 1 to provide preferential treatment to the vehicle 10 for available charging devices 601 depending on the security level.
[0192] (Second Modification of the Embodiment) A charge management system 1 having a plurality of charge stations may operate as shown in Fig. 19 with respect to a reservation for use of a charge station 30 by a vehicle 10. Fig. 19 is a sequence diagram showing the operation of the charge management system 1 according to the second modification of the embodiment.
[0193] When a search instruction for a charging point is input to the display 400, the vehicle 10 acquires management information indicating the status of the vehicle 10 in response to the search instruction and generates a search request. The search request may include the current location of the vehicle 10. The search request may further include information indicating whether the vehicle 10 will go directly to the charging station 30 immediately after the reservation. The vehicle 10 transmits the management information related to the security of the vehicle 10 and the search request for a charging point to the vehicle management server 20 via a wireless communication line (S100).
[0194] When the vehicle management server 20 receives the management information of the vehicle 10 and a request to search for a charging point, it updates the vehicle information 5051 indicating the status of the vehicle 10 according to the management information of the vehicle 10 and determines the security level of the vehicle 10 (S101).
[0195] The vehicle management server 20 may determine the security level of the vehicle 10 as shown in Fig. 20. Fig. 20 is a flowchart showing a process for determining the security level in a second modified example of the embodiment. Fig. 20 illustrates a process in which the security level is ranked into multiple stages (e.g., three stages) and determined.
[0196] The vehicle management server 20 extracts information about the version of the software of the vehicle 10 from the management information of the vehicle 10. The vehicle management server 20 has pre-stored therein information about the latest version of each of a plurality of pieces of software that may be installed in the vehicle 10. The vehicle management server 20 determines whether the version of the software of the vehicle 10 is the latest, based on the information about the version of the software of the vehicle 10 (ST1).
[0197] When multiple pieces of software are installed in the vehicle 10, the vehicle management server 20 can determine that the software version of the vehicle 10 is the latest (Yes in ST1) if all of the multiple pieces of software are the latest. If at least one of the multiple pieces of software is not the latest, the vehicle management server 20 can determine that the software version of the vehicle 10 is not the latest (No in ST1).
[0198] If the software version of the vehicle 10 is the latest (Yes in ST1), the vehicle management server 20 extracts information indicating the presence or absence of a security intrusion history from the management information of the vehicle 10. Based on the information indicating the presence or absence of a security intrusion history, the vehicle management server 20 determines whether or not the vehicle 10 has a security intrusion history (ST2).
[0199] If the software version of the vehicle 10 is not the latest (No in ST1), the vehicle management server 20 extracts information indicating the presence or absence of security monitoring from the management information of the vehicle 10. The vehicle management server 20 determines whether security monitoring is being performed on the vehicle 10 according to the information indicating the presence or absence of security monitoring (ST3).
[0200] If security monitoring is being performed on the vehicle 10 (Yes in ST3), the vehicle management server 20 extracts information indicating whether or not there is a history of security intrusion from the management information of the vehicle 10. The vehicle management server 20 determines whether or not there is a history of security intrusion on the vehicle 10 based on the information indicating the presence or absence of a history of security intrusion (ST2).
[0201] If there is no security monitoring for the vehicle 10 (No in ST3), the vehicle management server 20 extracts information indicating whether or not there is a history of security intrusion from the management information of the vehicle 10. The vehicle management server 20 determines whether or not there is a history of security intrusion for the vehicle 10 according to the information indicating the presence or absence of a history of security intrusion (ST5).
[0202] If the software version of the vehicle 10 is the latest (Yes in ST1) and there is no history of security breaches in the vehicle 10 (Yes in ST2), the vehicle management server 20 determines that the security level of the vehicle 10 is "high" (ST4).
[0203] If the software version of the vehicle 10 is not the latest (No in ST1), the vehicle 10 is under security monitoring (Yes in ST3), and the vehicle 10 has no history of security breaches (Yes in ST2), the vehicle management server 20 determines that the security level of the vehicle 10 is "high" (ST4).
[0204] If the software version of the vehicle 10 is the latest (Yes in ST1) and the vehicle 10 has a history of security breaches (No in ST2), the vehicle management server 20 determines that the security level of the vehicle 10 is "medium" (ST6).
[0205] If the software version of the vehicle 10 is not the latest (No in ST1), the vehicle 10 is under security monitoring (Yes in ST3), and the vehicle 10 has a history of security breaches (No in ST2), the vehicle management server 20 determines that the security level of the vehicle 10 is "medium" (ST6).
[0206] If the software version of the vehicle 10 is not the latest (No in ST1), there is no security monitoring of the vehicle 10 (No in ST3), and there is no history of security breaches in the vehicle 10 (Yes in ST5), the vehicle management server 20 determines that the security level of the vehicle 10 is "medium" (ST6).
[0207] If the software version of the vehicle 10 is not the latest (No in ST1), there is no security monitoring of the vehicle 10 (No in ST3), and there is a history of security breaches in the vehicle 10 (No in ST5), the vehicle management server 20 determines that the security level of the vehicle 10 is "low" (ST7).
[0208] In S101 shown in FIG. 19, the vehicle management server 20 further updates the vehicle information 5051 in accordance with the result of the security level determination.
[0209] The vehicle management server 20 generates a station search request in response to the request to search for a charging point. The station search request may include the current location of the vehicle 10. The station search request may further include information indicating whether the vehicle 10 will go directly to the charging station 30 immediately after the reservation. The vehicle management server 20 transmits the station search request and vehicle information 5051 to the station management server 40 via a wireless communication line and / or a wired communication line (S102).
[0210] Upon receiving the station search request and the vehicle information 5051, the station management server 40 extracts information on the security level of the vehicle 10 from the vehicle information 5051. In response to the station search request, the station management server 40 searches for information on available charging stations 30 under its management, performs calculations for each of the found charging stations 30, and generates a reservation schedule. At this time, the station management server 40 may estimate a charge amount and include the estimated amount in the reservation schedule (S103).
[0211] During the search ( S103 ), the station management server 40 may change the distance range to the charging station 30 that the vehicle 10 can use, depending on the station search request and the security level of the vehicle 10 .
[0212] The station management server 40 may search for a charging station 30 that can be used by the vehicle 10, as shown in Fig. 21. Fig. 21 is a flowchart illustrating the station search process in a second modified example of the embodiment. Fig. 21 illustrates the station search process when security levels are ranked into three stages.
[0213] The station management server 40 determines whether the security level of the vehicle 10 is "low" (ST11).
[0214] If the security level of the vehicle 10 is "low" (Yes in ST11), the station management server 40 searches for one or more available charging stations 30 within the last hour and within a 50-km radius of the current location of the vehicle 10 (ST12). The station management server 40 generates station information including the locations of each of the one or more found charging stations 30.
[0215] If the security level of the vehicle 10 is not "low" (No in ST11), the station management server 40 determines whether the security level of the vehicle 10 is "medium" (ST13).
[0216] If the security level of the vehicle 10 is "medium" (Yes in ST13), the station management server 40 searches for one or more charging stations 30 that have been found within the last three hours and are reachable based on the remaining power of the vehicle 10 (ST14). The station management server 40 generates station information including the locations of each of the one or more charging stations 30 found.
[0217] If the security level of the vehicle 10 is not "medium" (No in ST13), the station management server 40 does not impose any search restrictions (ST15). The station management server 40 generates station information including the locations of all of the charging stations 30 under its management.
[0218] In addition, when estimating the billing amount in generating a reservation schedule (S103 shown in Figure 19), the station management server 40 may calculate the estimated amount by changing the discount rate of the usage fee depending on the security level of the vehicle 10.
[0219] The station management server 40 may estimate the billing amount as shown in Fig. 22. Fig. 22 is a flowchart showing the billing amount estimation process in the second modified example of the embodiment. Fig. 22 illustrates the billing amount estimation process when the security level is ranked into three stages.
[0220] The station management server 40 extracts, from the station search request, information indicating whether the vehicle 10 will go directly to the charging station 30 immediately after the reservation. Based on the extracted information, the station management server 40 determines whether the vehicle 10 will go directly to the charging station 30 immediately after the reservation (ST21).
[0221] If vehicle 10 goes directly to charging station 30 immediately after the reservation (Yes in ST21), station management server 40 extracts information on the remaining battery charge and current location of vehicle 10 from vehicle information 5051. Station management server 40 calculates the remaining power of vehicle 10 when vehicle 10 arrives at charging station 30 based on the information on the remaining battery charge and current location of vehicle 10 and the location of charging station 30, and calculates the amount of charge required for full charging (ST22).
[0222] The station management server 40 calculates a standard estimated price from the amount of charge and the unit price of electricity for the reserved time period (ST23).
[0223] If the vehicle 10 does not go directly to the charging station 30 immediately after the reservation (No in ST21), the station management server 40 calculates a standard estimated charge based on the average charge amount and the electricity unit price for the reserved time period (ST23). The average charge amount is the average value of the amounts of charge performed by the vehicle 10 in the past, and is assumed to have been calculated in advance by the vehicle management server 20 and notified to the station management server 40.
[0224] The station management server 40 determines whether the security level of the vehicle 10 is "high" (ST25).
[0225] If the security level of the vehicle 10 is not "high" (No in S25), the station management server 40 determines whether the security level of the vehicle 10 is "medium" (ST27).
[0226] If the security level of the vehicle 10 is "high" (Yes in ST25), the station management server 40 discounts the standard estimated amount by 10%, generates a reservation schedule including the discounted estimated amount as the final estimated amount, and generates station information including the reservation schedule (ST26).
[0227] If the security level of the vehicle 10 is "medium" (Yes in ST27), the station management server 40 discounts the standard estimated amount by 5%, generates a reservation schedule including the discounted estimated amount as the final estimated amount, and generates station information including the reservation schedule (ST26).
[0228] If the security level of the vehicle 10 is not "medium" (No in ST27), the station management server 40 discounts the standard estimated amount by 0% and sets the discounted estimated amount as the final estimated amount. In other words, the station management server 40 generates a reservation schedule that includes the standard estimated amount as the final estimated amount, and generates station information that includes the reservation schedule.
[0229] When the station information is generated in S103 shown in FIG. 19, the station management server 40 notifies the vehicle 10 of the station information via the vehicle management server 20 (S104).
[0230] When vehicle 10 receives the station information, information such as the location of available charging stations 30 can be displayed on display 400. When vehicle 10 receives a reservation confirmation instruction including the selection of charging stations 30 via display 400, vehicle 10 transmits a reservation request requesting a reservation for use of charging stations 30 to station management server 40 via vehicle management server 20 in response to the reservation confirmation instruction (S105).
[0231] Upon receiving the reservation request, the station management server 40 generates a reservation schedule in accordance with the reservation request. The station management server 40 generates a schedule update request in accordance with the reservation schedule and transmits the schedule update request to the charging station 30 (S106). The schedule update request may include the reservation schedule to be registered.
[0232] Upon receiving the schedule update request, the charging station 30 registers the reservation schedule in response to the schedule update request, thereby completing the reservation for use of the charging device 601 at the charging station 30 (S107).
[0233] In this way, the higher the security level of the vehicle 10, the more favorable the conditions under which the charge management system 1 reserves the use of the charging device 601 for the vehicle 10. This also makes it possible to provide preferential treatment to the vehicle 10 according to the security level, and to provide an incentive to the user of the vehicle 10 to improve security and encourage the user to ensure security.
[0234] (Third Modification of the Embodiment) The charging management system 1 may operate as shown in Fig. 23 with respect to the use of the charging station 30 by the vehicle 10 and the payment of the fee. Fig. 23 is a sequence diagram showing the operation of the charging management system 1 according to the third modification of the embodiment. Fig. 23 illustrates the operation when online payment is made by the vehicle 10.
[0235] When the battery 300 is connected to the charging device 601 of the charging station 30, the vehicle 10 supplies a charging start request to the charging device 601 (S200).
[0236] When the charging station 30 receives a charging start request from the vehicle 10 via the charging device 601a, the charging station 30 recognizes that the vehicle 10 is connected to the charging device 601 in response to the charging start request (S201).
[0237] The charging station 30 accesses the battery 300 to acquire the charging state thereof, and notifies the station management server 40 of the charging state of the battery 300 of the vehicle 10 (S202).
[0238] If the state of charge of the battery 300 conforms to the reservation schedule, the charging station 30 controls the charging device 601a to supply power under conditions in accordance with the reservation schedule. If the state of charge of the battery 300 does not conform to the reservation schedule, the charging station 30 adjusts the reservation schedule to conform. For example, if the sum of the remaining amount of received power and the charge amount in the reservation schedule exceeds the full charge amount of the vehicle 10, the charging station 30 reduces the charge amount in the reservation schedule so that the sum is equal to or less than the full charge amount of the vehicle 10. The charging station 30 controls the charging device 601a to supply power under conditions in accordance with the adjusted reservation schedule. In this way, the battery 300 of the vehicle 10 is charged.
[0239] When charging of the battery 300 of the vehicle 10 is completed, the charging station 30 generates usage history information including the amount of charge of the vehicle 10, and transmits the usage history information and a billing amount determination request to the station management server 40 (S203).
[0240] When the station management server 40 receives the usage history information and the billing amount determination request, it calculates the billing amount to the vehicle 10 according to the usage history information and generates billing information including the billing amount.
[0241] At this time, station management server 40 may calculate the usage fee for charging station 30 by changing the discount rate according to the security level of vehicle 10, and generate billing information including the billing amount. For example, station management server 40 may increase the discount rate the higher the security level of vehicle 10, and calculate the billing amount by discounting the standard billing amount for charging station 30 by that discount rate. In this way, the higher the security level of vehicle 10, the more advantageous the conditions for calculating the usage fee for charging station 30 and generating billing information.
[0242] The station management server 40 transmits the billing information to the vehicle 10 via the vehicle management server 20 .
[0243] Vehicle 10 displays the billing information on display 400. An instruction to select online payment is input in vehicle 10 (S204), and the instruction is transmitted from vehicle 10 to charging station 30.
[0244] In response to the selection instruction, charging station 30 enters a state in which it can accept input of online payment information. The user performs an operation to input online payment information at charging station 30, and in response, charging station 30 notifies station management server 40 of the online payment information (S205).
[0245] The station management server 40 transmits the online payment information to the vehicle management server 20 as billing information (S206). If the vehicle management server 20 has been previously entrusted by the owner (e.g., the driver) of the vehicle 10 to handle online payments, the vehicle management server 20 executes online payment according to the online payment information on behalf of the owner of the vehicle 10. This completes the settlement of the amount charged to the vehicle 10.
[0246] In this way, the higher the security level of vehicle 10, the more advantageous the conditions under which charging management system 1 calculates the usage fee for charging station 30 and generates billing information for vehicle 10. This also makes it possible to provide preferential treatment to vehicle 10 according to the security level, and to provide an incentive to the user of vehicle 10 to improve security and encourage the user to ensure security.
[0247] (Fourth Modification of the Embodiment) The charge management system 1 may include a plurality of vehicles 10a to 10c, as shown in Fig. 24. Fig. 24 is a diagram showing the configuration of the charge management system 1 according to the fourth modification of the embodiment. Fig. 24 illustrates a configuration in which the charge management system 1 includes three vehicles 10a to 10c, but the number of vehicles included in the charge management system 1 may be two or less, or four or more.
[0248] In the charge management system 1, a vehicle management server 20 and a plurality of vehicles 10a to 10c are communicably connected via wireless communication lines. The vehicle management server 20 can manage the plurality of vehicles 10a to 10c.
[0249] In this case, the charge management system 1 may assign priorities to the multiple vehicles 10a-10c according to the level of their security levels. The charge management system 1 adjusts parameters related to the charging of the multiple vehicles 10a-10c according to the priorities of the multiple vehicles 10a-10c. The charge management system 1 may adjust the parameters so that the higher the priority of the multiple vehicles 10a-10c, the more advantageous conditions are included. The charge management system 1 uses the adjusted parameters of the multiple vehicles 10a-10c to perform processing related to the multiple vehicles 10a-10c using the charging station 30. In this way, the higher the security level of the multiple vehicles 10a-10c, the more preferential treatment can be given to the multiple vehicles 10a-10c.
[0250] In the vehicle management server 20 shown in Fig. 9, the security level determination unit 503 may determine the security levels of the multiple vehicles 10a to 10c using multiple ranks, and the vehicle information storage unit 505 may store vehicle information 5051 as shown in Fig. 25. Fig. 25 is a diagram showing the data structure of the vehicle information 5051 in a fourth modified example of the embodiment.
[0251] 25 , “10a,” “10b,” and “10c” are recorded in the identifier column 5051a. “Software version,” “Security intrusion history,” “Security monitoring,” “Remaining battery level,” and “Location” are recorded three times in the item column 5051b. “Latest,” “No,” “Yes,” “50%,” “XXX, YYY,” “Slightly old,” “No,” “Yes,” “50%,” “VVV, WWW,” “Old,” “No,” “No,” “50%,” and “UUU, ZZZ” are recorded in the status column 5051c.
[0252] By referring to vehicle information 5051, it is possible to determine that for vehicle "10a," the "software version" is "latest," there is "no security intrusion history," the "security monitoring" service is "available," the "remaining battery charge" is "50%," and the current "location" is "XXX, YYY."
[0253] For vehicle "10b," it can be determined that the "software version" is "slightly old," there is "no history of security intrusion," the "security monitoring" service is "available," the "remaining battery capacity" is "50%," and the current "location" is "VVV, WWW."
[0254] For vehicle "10c," it can be determined that the "software version" is "old," there is "no security breach history," the "security monitoring" service is "no," the "remaining battery level" is "50%," and the current "location" is "UUU, ZZZ."
[0255] The security level determination unit 503 may access the vehicle information storage unit 505, refer to the vehicle information 5051, and determine the security levels of the multiple vehicles 10a to 10c according to the vehicle information 5051. The security level determination unit 503 may determine the security levels of the vehicles 10a to 10c according to the states of the items "software version," "security intrusion history," and "security monitoring," and add the determination results to the vehicle information 5051.
[0256] 25, for vehicle "10a," the "software version" is "latest," there is "no security intrusion history," and the "security monitoring" service is "present," so security level determination unit 503 determines that the "security level" is "high." In response to this determination, security level determination unit 503 adds the item "security level" and the status "high" to vehicle information 5051 of vehicle "10a."
[0257] For vehicle "10b," the "software version" is "slightly old," there is "no security intrusion history," and the "security monitoring" service is "present," so security level determination unit 503 determines that the "security level" is "medium." In response to this determination, security level determination unit 503 adds the item "security level" and the status "medium" to vehicle information 5051 of vehicle "10b."
[0258] For vehicle "10c," the "software version" is "old," there is "no security intrusion history," and the "security monitoring" service is "not available," so security level determination unit 503 determines that the "security level" is "low." In response to this determination, security level determination unit 503 adds the item "security level" and the status "low" to vehicle information 5051 of vehicle "10c."
[0259] The communication unit 501 may refer to the vehicle information storage unit 505, acquire vehicle information 5051 from the vehicle information storage unit 505, and transmit the vehicle information 5051 to the station management server 40 via a wireless communication line and / or a wired communication line. The vehicle information 5051 includes the determination results of the security levels of the multiple vehicles 10a to 10c.
[0260] This allows the station management server 40 to prioritize the vehicles 10a to 10c according to the security levels of the vehicles 10a to 10c. For example, the station management server 40 may prioritize the vehicles 10a, 10b, and 10c as "high," "medium," and "low" depending on whether the security levels of the vehicles 10a, 10b, and 10c are "high," "medium," and "low," respectively.
[0261] The station management server 40 may adjust the reservation schedules of the multiple vehicles 10a-10c according to the priorities of the multiple vehicles 10a-10c. The station management server 40 adjusts the reservation schedule for each of the multiple vehicles 10a-10c so that the higher the priority of the vehicle, the more advantageous the conditions. The station management server 40 notifies the charging station 30 of the adjusted reservation schedule for each of the vehicles 10a-10c. As a result, each of the vehicles 10a-10c can use the charging station 30 according to the adjusted reservation schedule.
[0262] In this way, the charge management system 1 can provide more preferential treatment to the vehicles 10 a to 10 c with higher security levels, thereby providing incentives to the users of the vehicles 10 a to 10 c to improve security and encouraging them to ensure security.
[0263] Furthermore, in the charge management system 1, the security level determination unit 503 of the vehicle management server 20 determines the security levels of the multiple vehicles 10 according to management information related to the security of the multiple vehicles 10. The scheduling unit 702, the station search unit 703, and the charge amount determination unit 704 of the station management server 40 adjust parameters related to charging of the multiple vehicles 10 according to the determined security levels of the multiple vehicles 10. The scheduling unit 702, the station search unit 703, and the charge amount determination unit 704 use the adjusted parameters of the multiple vehicles 10 to perform processing related to the multiple vehicles 10 using the charging device 601. In this way, the charge management system 1 can provide preferential treatment for the use of the charging device 601 to each of the multiple vehicles 10 according to the level of the security level.
[0264] (Fifth Modification of the Embodiment) The charge management system 1 having a plurality of vehicles may perform, for each vehicle, operations basically similar to those of the second modification of the embodiment with regard to the vehicle's reservation for use of the charge station 30. That is, the charge management system 1 may allow a plurality of vehicles to concurrently make reservations for use of the charge station 30. In this case, coordination among the plurality of vehicles is performed when the schedule is updated (S106).
[0265] As shown in Fig. 26 , the station management server 40 may allocate schedules to a plurality of vehicles and adjust reservation schedules among the plurality of vehicles. Fig. 26 is a flowchart showing the schedule allocation process in a fifth modified example of the embodiment. Fig. 26 illustrates an example of the schedule allocation process when security levels are ranked into three levels. As in the fourth modified example of the embodiment, Fig. 26 illustrates an example in which the charge management system 1 has three vehicles 10a, 10b, and 10c, and the security levels of the three vehicles 10a, 10b, and 10c are determined to be "high," "medium," and "low."
[0266] When the station management server 40 receives reservation requests from a plurality of vehicles 10a, 10b, and 10c via the vehicle management server 20, it acquires information on the time periods during which charging is possible for each of the vehicles 10a, 10b, and 10c in response to the reservation requests (ST31).
[0267] The station management server 40 assigns schedules to the plurality of vehicles 10a, 10b, and 10c in descending order of security level.
[0268] First, the station management server 40 assigns a schedule to the vehicle 10a with a security level of "high" (ST32). The station management server 40 assigns the time requested in the reservation request of the vehicle 10a to the vehicle 10a's usage time from among the available times of the charging station 30 assigned to the vehicle 10a. The station management server 40 may assign high-output charging power to the vehicle 10a starting from an available time slot with low electricity prices. The station management server 40 creates a reservation schedule for the vehicle 10a based on the result of the charging power assignment.
[0269] Next, the station management server 40 assigns a schedule to vehicle 10b, which has a medium security level (ST33). The station management server 40 assigns the time requested in the reservation request for vehicle 10b, from among the available time of the charging station 30, excluding the time assigned to vehicle 10a, as the usage time for vehicle 10b. The station management server 40 may assign high-output charging output to vehicle 10a starting from an available time slot with low electricity prices. The station management server 40 creates a reservation schedule for vehicle 10b based on the result of the charging output assignment.
[0270] Next, the station management server 40 assigns a schedule to vehicle 10b, which has a security level of "low" (ST34). The station management server 40 assigns the time requested in the reservation request for vehicle 10c, from among the available time of the charging station 30, excluding the time assigned to vehicles 10a and 10b, to vehicle 10c's usage time. The station management server 40 may assign a high output charging output to vehicle 10c starting from an available time slot with low electricity prices. The station management server 40 creates a reservation schedule for vehicle 10c based on the result of the usage time assignment.
[0271] When the coordination among the plurality of vehicles is completed, station management server 40 generates a schedule update request for each of vehicles 10 a, 10 b, and 10 c in accordance with the reservation schedule, and transmits the schedule update request to charging station 30 (S106). The schedule update request may include the reservation schedule to be registered.
[0272] When the charging station 30 receives the schedule update request, the charging station 30 registers a reservation schedule for each of the vehicles 10a, 10b, and 10c in response to the schedule update request. This completes the reservation for use of the charging device 601 at the charging station 30 (S107).
[0273] In this way, the charge management system 1 can provide more preferential treatment to the vehicles 10 a to 10 c with higher security levels, thereby providing incentives to the users of the vehicles 10 a to 10 c to improve security and encouraging them to ensure security.
[0274] (Sixth Variation of the Embodiment) The charging management system 1 having a plurality of vehicles may basically perform the same operation as in the third variation of the embodiment for each vehicle with regard to the use of the charging station 30 by the vehicles, but when the power supply and demand is tight, adjustments are made between the plurality of vehicles regarding the charging output during charging (S202).
[0275] When the power supply and demand is tight, the station management server 40 may adjust the charging output among a plurality of vehicles, as shown in Fig. 27 . Fig. 27 is a flowchart showing the charging output adjustment process in a sixth modified example of the embodiment. Fig. 27 illustrates the charging output adjustment process when the security level is ranked into three stages. As in the sixth modified example of the embodiment, Fig. 27 illustrates an example in which the charging management system 1 has three vehicles 10a, 10b, and 10c, and the security levels of the three vehicles 10a, 10b, and 10c are determined to be "high," "medium," and "low."
[0276] The station management server 40 collects information on the power utilization rate from the charging station 30. The station management server 40 determines whether the power utilization rate is equal to or greater than a threshold value (for example, 80%) (ST41).
[0277] If the power utilization rate is less than the threshold (No in ST41), the station management server 40 determines that the power supply and demand is not tight, and ends the process.
[0278] If the power utilization rate is above the threshold (Yes in ST41), the station management server 40 determines that the power supply and demand is tight and adjusts the charging output among multiple vehicles by reducing the charging output in order of lowest security level.
[0279] The station management server 40 inquires about the current usage status of the charging station 30 and acquires usage status information regarding the current usage status. Based on the usage status information, the station management server 40 determines whether a vehicle with a security level of "low" is currently charging (ST42).
[0280] If a vehicle with a security level of "low" is currently charging (Yes in ST42), the station management server 40 reduces the charging output to that vehicle by 50% (ST43).
[0281] The station management server 40 collects information relating to the power utilization rate from the charging station 30. The station management server 40 determines whether the power utilization rate is equal to or greater than a threshold value (for example, 80%) (ST44).
[0282] If the power utilization rate is less than the threshold (Yes in ST44), the station management server 40 determines that the tight power supply and demand situation has been resolved, and ends the process.
[0283] If a vehicle with a security level of "low" is not charging (No in ST42) or if the power usage rate is equal to or greater than the threshold (No in ST44), the station management server 40 inquires about the current usage status of the charging station 30 and acquires usage status information relating to the current usage status. Based on the usage status information, the station management server 40 determines whether a vehicle with a security level of "medium" is charging (ST45).
[0284] If a vehicle with a medium security level is currently charging (Yes in ST45), the station management server 40 reduces the charging output to that vehicle by 50% (ST46).
[0285] The station management server 40 collects information on the power utilization rate from the charging station 30. The station management server 40 determines whether the power utilization rate is equal to or greater than a threshold value (for example, 80%) (ST47).
[0286] If the power utilization rate is less than the threshold (Yes in ST47), the station management server 40 determines that the tight power supply and demand situation has been resolved, and ends the process.
[0287] If a vehicle with a medium security level is not charging (No in ST45) or if the power utilization rate is equal to or greater than the threshold (No in ST47), the station management server 40 inquires about the current utilization status of the charging station 30 and acquires utilization status information relating to the current utilization status. In accordance with the utilization status information, the station management server 40 reduces the charging output to vehicles with a high security level so that the power utilization rate falls below the threshold (ST48).
[0288] As a result, when the tightness in the power supply and demand is resolved, the charge management system 1 performs charging (S202) and subsequent operations in the same manner as in the third modified example of the embodiment.
[0289] While Fig. 27 illustrates an example of a control operation in which charging output is reduced starting with vehicles with low security levels when the power supply and demand is tight, charging output may be reduced in a manner that is graded according to the security level. For example, the required reduction amount may be reduced in a ratio of 60:30:10 between "vehicles with a security level of 'low'," "vehicles with a security level of 'medium'," and "vehicles with a security level of 'high'." The threshold value of "80%" and the reduction amount of "50%" illustrated in Fig. 27 are arbitrary values and can be changed depending on how easily the power supply and demand tightness can be alleviated.
[0290] In this way, the higher the security level of the multiple vehicles 10 a to 10 c, the later the reduction in charging output when the power supply and demand is tight, and the more preferential treatment can be given to the vehicles 10 a to 10 c. This also makes it possible to provide an incentive for users of the vehicles 10 a to 10 c to improve security and encourage them to ensure security.
[0291] Furthermore, in the charge management system 1, when the supply and demand of power is tight, the station management server 40 adjusts parameters related to charging of the plurality of vehicles 10a-10c according to the priority of each of the plurality of vehicles 10a-10c that can be charged. The station management server 40 uses the adjusted parameters of the plurality of vehicles 10a-10c to perform processing related to the use of the charging device 601 by the plurality of vehicles 10a-10c. This allows the charge management system 1 to provide preferential treatment for the use of the charging device 601 to each of the plurality of vehicles 10 according to the priority.
[0292] Furthermore, in the charge management system 1, the vehicle management server 20 determines the priorities of the multiple vehicles 10a-10c according to management information related to the security of the multiple vehicles 10a-10c. When the supply and demand of electricity is tight, the station management server 40 adjusts parameters related to charging of the multiple vehicles 10a-10c according to the priorities of the multiple vehicles 10a-10c determined by the vehicle management server 20. This allows the charge management system 1 to provide preferential treatment for the use of the charging device 601 to each of the multiple vehicles 10 according to the level of priority corresponding to the security level.
[0293] (Seventh Modification of the Embodiment) In the charge management system 101, as shown in FIG. 28 , the vehicle management server 20 and the station management server 40 may be integrated into a server 120. FIG. 28 is a diagram showing the configuration of the charge management system 101 according to the seventh modification of the embodiment. In this case, the vehicle 10 and the server 120 are connected to each other so as to be able to communicate with each other via a wireless communication line. The server 120 and the charging station 30 are connected to each other so as to be able to communicate with each other via a wireless communication line and / or a wired communication line. The server 120 may include the configuration shown in FIG. 9 and the configuration shown in FIG. 12 . The communication unit 501 and the communication unit 701 may be integrated into a single communication unit.
[0294] As in the embodiment, the server 120 may determine parameters such that the higher the security level of the vehicle 10, the more advantageous the conditions under which the vehicle 10 can be charged.
[0295] In this way, the charging management system 101 can provide preferential treatment to the vehicle 10 in relation to the use of the charging station 30 depending on the security level, thereby providing the user of the vehicle 10 with an incentive to improve security and encouraging them to ensure security.
[0296] 29 , in the charge management system 201, a server 260 connectable to a user terminal 270 may be added between the vehicle management server 20 and the station management server 40. FIG. 29 is a diagram showing the configuration of the charge management system 201 according to the eighth modification of the embodiment.
[0297] In this case, the vehicle management server 20 and the server 260 are communicably connected to each other via a wireless communication line and / or a wired communication line. The server 260 and the station management server 40 are communicably connected to each other via a wireless communication line and / or a wired communication line. The user terminal 270 and the server 260 are communicably connected to each other via a wireless communication line.
[0298] Information to be notified to the display 400 may be notified to the user terminal 270 via the server 260 instead of or in addition to being notified to the display 400 .
[0299] The server 260 can execute processing of the intermediation service between the vehicle management server 20 and the station management server 40. The user terminal 270 may be configured with an application that provides a user interface for using the intermediation service processing. When the user terminal 270 receives a request to use the intermediation service, it transmits the request to the server 260 via a wireless communication line and / or a wired communication line. In response to the request, the server 260 may execute processing of the intermediation service and transmit information corresponding to the execution result to the station management server 40 via a wireless communication line and / or a wired communication line.
[0300] For example, a user ID is preset in the user terminal 270. In the vehicle management server 20, the vehicle information 5051 (see FIG. 11 ) stored in the vehicle information storage unit 505 may be information in which the user ID is further associated with the identifier of the vehicle 10, items related to the attributes of the vehicle 10, and the vehicle's status. When the user terminal 270 receives a reservation request for the use of the charging device 601 from a user, the user terminal 270 generates a reservation request including the request for reservation for the use of the charging device 601 and the user ID, and transmits the reservation request to the server 260 via a wireless communication line and / or a wired communication line. When the server 260 receives the reservation request, the server 260 inquires of the vehicle corresponding to the user ID included in the reservation request and its security level via a wireless communication line and / or a wired communication line to the vehicle management server 20. The vehicle management server 20 accesses the vehicle information storage unit 505 and refers to the vehicle information 5051 to return a response containing the identifier of the vehicle corresponding to the user ID and information about its security level. The server 260 may determine parameters based on the vehicle identifier and information about the security level of the vehicle 10 so that the higher the security level of the vehicle 10, the more advantageous the conditions under which the vehicle 10 can be charged, and transmit the determined parameters to the station management server 40. Upon receiving the parameters, the station management server 40 may perform processing in accordance with the parameters in the same manner as in the embodiment.
[0301] In this way, the charging management system 201 can provide preferential treatment to the vehicle 10 in relation to the use of the charging station 30 depending on the security level, thereby providing the user of the vehicle 10 with an incentive to improve security and encouraging them to ensure security.
[0302] (Ninth Modification of the Embodiment) In a charge management system 301, as shown in Fig. 30 , the vehicle management server 20 and the server 260 may be integrated into a server 320. Fig. 30 is a diagram showing the configuration of a charge management system 301 according to a ninth modification of the embodiment.
[0303] In this case, the server 320 and the station management server 40 are communicably connected to each other via a wireless communication line and / or a wired communication line. The user terminal 270 and the server 320 are communicably connected to each other via a wireless communication line.
[0304] Information to be notified to the display 400 may be notified to the user terminal 270 via the server 320 instead of or in addition to being notified to the display 400 .
[0305] The server 320 can execute predetermined processing equivalent to integrating the vehicle management server 20 and the server 260. The user terminal 270 may be configured with an application that provides a user interface for using the predetermined processing. When the user terminal 270 receives a request to use the predetermined processing, it transmits the request to the server 320 via a wireless communication line and / or a wired communication line. In response to the request, the server 320 may execute the predetermined processing and transmit information corresponding to the execution result to the station management server 40 via a wireless communication line and / or a wired communication line.
[0306] For example, a user ID may be preset in the user terminal 270. In the server 320, the vehicle information 5051 (see FIG. 11 ) stored in the vehicle information storage unit 505 may be information that associates the user ID with the identifier of the vehicle 10, attributes of the vehicle 10, and the vehicle's status. When the user terminal 270 receives a reservation request for the use of the charging device 601 from a user, the user terminal 270 generates a reservation request including the request for reservation for the use of the charging device 601 and the user ID, and transmits the reservation request to the server 320 via a wireless communication line and / or a wired communication line. Upon receiving the reservation request, the server 320 accesses the vehicle information storage unit 505 and identifies the vehicle identifier and its security level corresponding to the user ID, by referring to the vehicle information 5051. The server 260 may determine parameters based on the information regarding the vehicle identifier and its security level, so that the higher the security level of the vehicle 10, the more favorable the conditions under which the vehicle 10 can be charged. Upon receiving the parameters, the station management server 40 may perform processing in accordance with the parameters, as in the embodiment.
[0307] In this way, the charging management system 301 can provide preferential treatment to the vehicle 10 in relation to the use of the charging station 30 depending on the security level, thereby providing the user of the vehicle 10 with an incentive to improve security and encouraging them to ensure security.
[0308] In the above embodiment and its modified examples, the present disclosure has been described as being applied to security measures in a vehicle 10 (e.g., an automobile), but the scope of application of the present disclosure is not limited thereto. For example, the present disclosure may be applied to security measures in any mobile object 410 that is rechargeable, has communication capabilities, and is mobile. Mobile objects 410 include, in addition to vehicles (e.g., automobiles) 10, construction machinery, agricultural machinery, ships, submarines, railways, linear motor cars, airplanes, gliders, hovercraft, spacecraft, and the like.
[0309] For example, in the charge management system 1, the station management server 40 determines parameters related to charging of the mobile unit 410 according to the security level of the mobile unit 410. The station management server 40 may determine the parameters such that the higher the security level of the mobile unit 410, the more favorable the conditions under which the mobile unit 410 can use the charging station 30. According to the determined parameters, the charging station 30 performs processing related to the mobile unit 410's use of the charging device 601. As a result, the charge management system 1 can provide preferential treatment to the mobile unit 410 according to the security level regarding the use of the charging device 601, and can provide the user of the mobile unit 410 with an incentive to improve security and encourage them to ensure security. As a result, the security of the mobile unit 410 can be ensured by the user of the mobile unit 410 taking security measures, such as updating the software used by the mobile unit 410.
[0310] Furthermore, in the charge management system 1, the communication unit 701 of the station management server 40 receives a request related to the mobile object 410 using the charging device 601. The scheduling unit 702, the station search unit 703, and the charge amount determination unit 704 of the station management server 40 control the charging station 30 so as to perform processing related to the mobile object 410 using the charging device 601. In this way, the charge management system 1 can perform processing related to the mobile object 410 using the charging device 601 in response to the request related to the use of the charging device 601.
[0311] Furthermore, in the charge management system 1, the security level determination unit 503 of the vehicle management server 20 determines the security level of the mobile object 410 in accordance with management information related to the security of the mobile object 410. The scheduling unit 702, the station search unit 703, and the charge amount determination unit 704 of the station management server 40 determine parameters related to charging of the mobile object 410 in accordance with the security level determination result. The scheduling unit 702, the station search unit 703, and the charge amount determination unit 704 perform processing related to the mobile object 410's use of the charging device 601 in accordance with a request related to use of the charging device 601 and the determined parameters. This allows the charge management system 1 to provide preferential treatment to the mobile object 410 in relation to use of the charging device 601 in accordance with the level of the security level.
[0312] Furthermore, in the charge management system 1, when the security level of the mobile object 410 is a first level, the station search unit 703 of the vehicle management server 20 determines the distance range to a charging device 601 available to the mobile object 410 to be a first range. When the security level of the mobile object 410 is a second level higher than the first level, the station search unit 703 determines the distance range to a charging device 601 available to the mobile object 410 to be a second range wider than the first range. When the distance range is determined to be the first range, the communication unit 701 of the station management server 40 notifies the mobile object 410 of information about charging devices 601 present within the first range. When the distance range is determined to be the second range, the communication unit 701 notifies the mobile object 410 of information about charging devices 601 present within the second range. This allows the charge management system 1 to provide preferential treatment to the mobile object 410 for available charging devices 601 depending on the security level.
[0313] Furthermore, in the charge management system 1, when the security level of the mobile object 410 is a first level, the station search unit 703 of the station management server 40 determines the time during which the mobile object 410 can reserve the charging device 601 to be a first time. When the security level of the mobile object 410 is a second level higher than the first level, the station search unit 703 determines the time during which the mobile object 410 can reserve the charging device 601 to be a second time longer than the first time. When the time is determined to be the first time, the communication unit 701 of the station management server 40 notifies the mobile object 410 of information about the first time. When the time is determined to be the second time, the communication unit 701 notifies the mobile object 410 of information about the second time. In this way, the charge management system 1 can provide preferential treatment to the mobile object 410 depending on the security level with respect to the time during which the charging device 601 can be used, and notify the mobile object 410 of this.
[0314] Furthermore, in the charge management system 1, when the security level of the mobile object 410 is a first level, the scheduling unit 702 of the station management server 40 determines the charging rate of the charging device 601 to be a first rate. When the security level of the mobile object 410 is a second level higher than the first level, the scheduling unit 702 determines the charging rate of the charging device 601 to be a second rate higher than the first rate. When the charging rate is determined to be the first rate, the scheduling unit 702 controls the charging device 601 to charge the mobile object 410 at the first rate. When the charging rate is determined to be the second rate, the scheduling unit 702 controls the charging device 601 to charge the mobile object 410 at the second rate. In this way, the charge management system 1 can provide preferential treatment to the mobile object 410 with respect to the charging rate of the charging device 601 depending on the level of the security level.
[0315] Furthermore, in the charge management system 1, when the security level of the mobile object 410 is a first level, the scheduling unit 702 of the station management server 40 determines the discount rate for the usage fee of the charging device 601 by the mobile object 410 to be a first rate. When the security level of the mobile object 410 is a second level higher than the first level, the scheduling unit 702 determines the discount rate for the usage fee of the charging device 601 by the mobile object 410 to be a second rate higher than the first rate. When the discount rate is determined to be the first rate, the communication unit 701 of the station management server 40 notifies the mobile object 410 of the amount obtained by discounting the first rate. When the discount rate is determined to be the second rate, the communication unit 701 notifies the mobile object 410 of the amount obtained by discounting the second rate. In this way, the charge management system 1 can provide preferential treatment to the mobile object 410 with respect to the usage fee of the charging device 601 depending on the security level and notify the mobile object 410 of this.
[0316] Furthermore, in the charge management system 1, the vehicle information 5051 stored in the vehicle information storage unit 505 of the vehicle management server 20 includes at least one of information related to the version of software installed in the mobile object 410, whether security monitoring is performed on the mobile object 410, whether a security intrusion has occurred on the mobile object 410, the number of security intrusions on the mobile object 410, and the recency of the security intrusion history on the mobile object 410. This allows the vehicle management server 20 to determine the security level of the mobile object 410 according to the vehicle information 5051.
[0317] The charge management system 1 may also include a plurality of mobile objects 410. In this case, the security level determination unit 503 of the vehicle management server 20 determines the security levels of the plurality of mobile objects 410 according to management information related to the security of the plurality of mobile objects 410. The scheduling unit 702, the station search unit 703, and the charge amount determination unit 704 of the station management server 40 adjust parameters related to charging of the plurality of vehicles 10 according to the determined security levels of the plurality of vehicles 10. The scheduling unit 702, the station search unit 703, and the charge amount determination unit 704 use the adjusted parameters of the plurality of vehicles 10 to perform processing related to the use of the charging device 601 by the plurality of vehicles 10. In this way, the charge management system 1 can provide preferential treatment for the use of the charging device 601 to each of the plurality of vehicles 10 according to the level of the security level.
[0318] Furthermore, in the charge management system 1, when the supply and demand of power is tight, the station management server 40 may adjust parameters related to charging of the plurality of mobile bodies 410 in accordance with the priority of each of the plurality of mobile bodies 410 that can be charged. In this case, the station management server 40 uses the adjusted parameters of the plurality of mobile bodies 410 to perform processing related to the plurality of mobile bodies 410 using the charging device 601. In this way, the charge management system 1 can provide preferential treatment for the use of the charging device 601 to each of the plurality of mobile bodies 410 in accordance with the priority.
[0319] Furthermore, in the charge management system 1, the vehicle management server 20 determines the priorities of the multiple mobile objects 410 according to management information related to the security of the multiple mobile objects 410. When the supply and demand of electricity is tight, the station management server 40 adjusts parameters related to charging of the multiple mobile objects 410 according to the priorities of the multiple mobile objects 410 determined by the vehicle management server 20. This allows the charge management system 1 to provide preferential treatment for the use of the charging device 601 to each of the multiple mobile objects 410 according to the level of priority corresponding to the security level.
[0320] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention described in the claims and their equivalents.
[0321] REFERENCE SIGNS LIST 1, 101, 201 Charging management system 10, 10a, 10b, 10c Vehicle 20 Charging management server 30, 30a, 30b, 30c Charging station 40 Station management server 50 Power distribution network 120 Server 260 Server 270 User terminal
Claims
1. A charging management system comprising: a reception unit that receives a request for a mobile object capable of charging to use a charging device; and a processing unit that performs processing related to the mobile object's use of the charging device in accordance with the request and the security level of the mobile object.
2. A charging management system as described in claim 1, further comprising: a judgment unit that judges a security level of the mobile body in accordance with management information regarding the security of the mobile body; and a decision unit that determines parameters regarding charging of the mobile body in accordance with the security level of the mobile body, wherein the processing unit performs processing related to the mobile body's use of a charging device in accordance with the request and the determined parameters.
3. The charging management system of claim 2, wherein the determination unit determines the distance range to charging devices available to the mobile body to be a first range when the security level of the mobile body is a first level, and determines the distance range to charging devices available to the mobile body to be a second range wider than the first range when the security level of the mobile body is a second level higher than the first level; and the processing unit notifies the mobile body of information about charging devices present in the first range when the distance range is determined to be the first range, and notifies the mobile body of information about charging devices present in the second range when the distance range is determined to be the second range.
4. The charging management system of claim 2, wherein the determination unit determines the time at which the mobile body can reserve a charging device to be a first time when the security level of the mobile body is a first level, and determines the time at which the mobile body can reserve a charging device to be a second time longer than the first time when the security level of the mobile body is a second level higher than the first level; and the processing unit notifies the mobile body of information of the first time when the time is determined to be the first time, and notifies the mobile body of information of the second time when the time is determined to be the second time.
5. The charging management system of claim 2, wherein the determination unit determines the charging speed of the charging device to a first speed when the security level of the mobile body is a first level, and determines the charging speed of the charging device to a second speed faster than the first speed when the security level of the mobile body is a second level higher than the first level; and the processing unit controls the charging device to charge the mobile body at the first speed when the charging speed is determined to be the first speed, and controls the charging device to charge the mobile body at the second speed when the charging speed is determined to be the second speed.
6. The charging management system of claim 2, wherein the determination unit determines a discount rate for the usage fee of the charging device by the mobile body to a first rate when the security level of the mobile body is a first level, and determines a discount rate for the usage fee of the charging device by the mobile body to a second rate greater than the first rate when the security level of the mobile body is a second level higher than the first level; and the processing unit notifies the mobile body of the amount obtained by discounting the amount at the first rate when the discount rate is determined to be the first rate, and notifies the mobile body of the amount obtained by discounting the amount at the second rate when the discount rate is determined to be the second rate.
7. The charging management system of claim 2, wherein the management information regarding the security of the mobile body includes at least one of the following information: the version of software installed in the mobile body, whether or not the mobile body is monitored for security, whether or not the mobile body has a history of security intrusions, the number of times the mobile body has had a history of security intrusions, and how recent the history of security intrusions is in the mobile body.
8. The charging management system described in claim 2, wherein the judgment unit judges security levels of the multiple mobile bodies according to management information regarding the security of the multiple mobile bodies, the decision unit adjusts parameters related to charging of the multiple mobile bodies according to the judged security levels of the multiple mobile bodies, and the processing unit uses the adjusted parameters of the multiple mobile bodies to perform processing related to the multiple mobile bodies using a charging device.
9. A charging management system comprising: an adjustment unit that adjusts parameters related to the charging of multiple mobile bodies in accordance with the priority of each of the multiple mobile bodies that can be charged when power supply and demand are tight; and a processing unit that uses the adjusted parameters of the multiple mobile bodies to perform processing related to the multiple mobile bodies using a charging device.
10. A charging management system as described in claim 9, further comprising a judgment unit that judges the priority of the multiple mobile bodies according to management information regarding the security of the multiple mobile bodies, and when power supply and demand are tight, the adjustment unit adjusts parameters related to charging of the multiple mobile bodies according to the judged priority of the multiple mobile bodies.
11. A charging management method comprising: determining parameters related to charging of a mobile body in accordance with a security level of the mobile body that can be charged; and using the determined parameters, performing processing related to the mobile body's use of a charging device.
12. The charging management method according to claim 11, further comprising: determining a security level of the mobile body in response to management information regarding the security of the mobile body; and said determination comprises determining a parameter related to charging of the mobile body in response to the determined security level.
13. A charging management method comprising: when power supply and demand is tight, adjusting parameters related to the charging of a plurality of mobile bodies in accordance with the priority of each of the mobile bodies that can be charged; and using the adjusted parameters of the plurality of mobile bodies to perform processing related to the use of a charging device by the plurality of mobile bodies.
14. The charging management method of claim 13, further comprising determining priorities of the plurality of moving bodies in accordance with management information relating to security of the plurality of moving bodies, and the adjustment includes, when power supply and demand are tight, adjusting parameters relating to charging of the plurality of moving bodies in accordance with the determined priorities of the plurality of moving bodies.
Citation Information
Patent Citations
Mobile robot charging system
JP2010237924A
Charge control system
JP2012147651A
Vehicle power charge controller
JP2013062918A
Website alteration monitoring device and website alteration monitoring system and website alteration monitoring method
JP2019200506A
Automobile charge control device and information terminal
WO2013057879A1
Cited By
Systems and methods for data integrity verification of messages for vehicle marshaling
US20260128862A1
