A scalable method for handling failures in a network of electric vehicle charging stations

The method addresses inefficiencies in managing faults in large electric vehicle charging station networks by calculating a failure priority index and initiating automated actions, enhancing fault management efficiency and reducing manual labor.

JP2024544300AActive Publication Date: 2024-11-28LIKENNEVIRTA OY VIRTA LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2024535973
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-04-22
Filing Date
2023-04-06
Publication Date
2024-11-28
Estimated Expiration
2043-04-06

AI Technical Summary

Technical Problem

Electric vehicle charging stations often fail due to various reasons, leading to inoperability or malfunctions, which require significant resources for manual fault management, especially in large networks with thousands of stations, resulting in inefficiencies and challenges in tracking and prioritizing faults.

Method used

A method and apparatus for managing faults in electric vehicle charging stations that involve detecting triggers, calculating a failure priority index based on indicators such as offline duration, frequency, and rejected commands, and initiating automated actions or maintenance alerts based on this index, allowing for hierarchical prioritization and streamlined fault management.

Benefits of technology

This approach enables efficient and automated fault management, reducing manual labor, prioritizing urgent issues, and optimizing maintenance efforts by providing actionable reports and alerts, thus improving the performance of charging station networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024544300000001_ABST
    Figure 2024544300000001_ABST
Patent Text Reader

Abstract

Exemplary embodiments enable a scalable method (200) for managing faults in an extensive network of electric vehicle charging stations, including thousands of electric vehicle charging stations. Faults that occur may be automatically resolved, if possible. Faults may be prioritized based on one or more criteria. A method (200) and an apparatus (600) for more efficiently handling faults are provided. The apparatus (600) comprises at least one processor (602) and at least one memory (604) that includes program code (606).
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE This application relates generally to electric vehicle charging stations. In particular, some exemplary embodiments of this application relate to fault management in a network of electric vehicle charging stations. [Background technology]

[0002] Electric vehicle charging stations sometimes experience faults for various reasons. Faults may cause the charging station to not work or may not operate properly. Handling faults may require a lot of resources. It would therefore be beneficial to mitigate at least some of these drawbacks. Summary of the Invention

[0003] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0004] Exemplary embodiments may enable more efficient and streamlined management of faults in electric vehicle charging stations. The proposed method is particularly useful for managing faults in a network of thousands of electric vehicle charging stations, where hundreds of faults may occur every day, for example.

[0005] According to a first aspect, a method for managing faults in an electric vehicle charging station is provided, the method being performed by an apparatus and including the steps of detecting a trigger for calculating a fault priority index for at least one electric vehicle charging station, determining one or more fault indicators at the electric vehicle charging station including at least one of a duration of an offline state, a frequency of an offline state, a duration of a fault, a frequency of a fault, or a number of rejected commands within a predetermined interval, determining a fault priority index by combining values ​​of the one or more fault indicators, and initiating at least one action to manage a fault in the at least one charging station based on the fault priority index.

[0006] In an embodiment, the trigger includes at least one of an indication that the electric vehicle charging station is offline, a notification of a fault status from the electric vehicle charging station, a rejection of a command by the electric vehicle charging station, a failure of the electric vehicle charging station to respond to a command, or a return to a normal state by the electric vehicle charging station.

[0007] In an embodiment, additionally or alternatively, the frequency of the offline state is determined based on the total duration of the electric vehicle charging station's offline state within a predetermined interval.

[0008] In an embodiment, additionally or alternatively, the frequency of the fault is determined based on the total duration of the electric vehicle charging station faults within a predetermined interval.

[0009] In an embodiment, additionally or alternatively, the at least one action includes at least one of providing a list of electric vehicle charging stations in order of urgency based on the fault priority index, providing a recommendation on how to correct the fault, rebooting the electric vehicle charging station, performing a firmware update for the electric vehicle charging station, resetting the charging station's internet connection, alerting remote maintenance, or alerting on-site maintenance.

[0010] In an embodiment, additionally or alternatively, the method further includes determining a priority level of the fault priority index based on a plurality of priority levels having different predetermined thresholds for the fault priority index, and initiating at least one action based on the priority level of the fault priority index.

[0011] In an embodiment, additionally or alternatively, the method further includes updating a fault priority index of the electric vehicle charging station after performing the at least one action, and initiating another action according to a priority level of the fault priority index if the updated fault priority index indicates that a fault still exists.

[0012] In an embodiment, additionally or alternatively, the method further includes grouping the plurality of electric vehicle charging stations into a plurality of child groups; grouping the plurality of child groups into one or more parent groups; determining an escalation index for each group by multiplying a number of faulty electric vehicle charging stations in the group by a sum of the fault priority indexes in the group and dividing that value by a number of non-faulty electric vehicle charging stations in the group; and providing a notification to a contact person of the parent group if the escalation index exceeds a predetermined limit for a child group.

[0013] According to a second aspect, an apparatus for managing faults in an electric vehicle charging station is provided, the apparatus comprising at least one processor and at least one memory, the at least one memory including program code configured, by the at least one processor, to cause the apparatus to at least detect a trigger to calculate a fault priority index for the at least one electric vehicle charging station; determine one or more fault indicators at the electric vehicle charging station including at least one of a duration of an offline state, a frequency of an offline state, a duration of a fault, a frequency of a fault, or a number of rejected commands within a predetermined interval; determine a fault priority index by combining values ​​of the one or more fault indicators; and initiate at least one action to manage faults in the at least one charging station based on the fault priority index.

[0014] In an embodiment, the trigger includes at least one of an indication that the electric vehicle charging station is offline, a notification of a fault status from the electric vehicle charging station, a rejection of a command by the electric vehicle charging station, a failure of the electric vehicle charging station to respond to a command, or a return to a normal state by the electric vehicle charging station.

[0015] In an embodiment, additionally or alternatively, the at least one action includes at least one of: creating a list of electric vehicle charging stations in order of urgency based on the fault priority index, providing a recommendation on how to correct the fault, rebooting the electric vehicle charging station, performing a firmware update for the electric vehicle charging station, resetting the charging station's internet connection, alerting remote maintenance, or alerting on-site maintenance.

[0016] In an embodiment, additionally or alternatively, the at least one memory further includes program code configured, by the at least one processor, to cause the apparatus to determine a priority level of the fault priority index based on a plurality of priority levels having different predetermined thresholds for the fault priority index, and to initiate at least one action based on the priority level of the fault priority index.

[0017] In an embodiment, additionally or alternatively, the at least one memory further includes program code configured, by the at least one processor, to cause the apparatus to update a fault priority index of the electric vehicle charging station after the at least one action, and to initiate another action according to a priority level of the fault priority index if the updated fault priority index indicates that a fault still exists.

[0018] In an embodiment, additionally or alternatively, the at least one memory further includes program code configured, by the at least one processor, to cause the apparatus to group the plurality of electric vehicle charging stations into a plurality of child groups; group the plurality of child groups into one or more parent groups; determine an escalation index for each group by multiplying the number of faulty electric vehicle charging stations in the group by the sum of the fault priority indexes in the group and dividing that value by the number of non-faulty electric vehicle charging stations in the group; and provide a notification to a contact person of the parent group if the escalation index exceeds a predetermined limit for a child group.

[0019] According to a third aspect, there is provided a computer readable medium comprising instructions which, when executed by a computer, cause the computer to perform the method of the first aspect.

[0020] Many of the attendant features will be more readily appreciated as the same becomes better understood by reference to the following detailed description considered in conjunction with the accompanying drawings, in which: [Brief description of the drawings]

[0021] The accompanying drawings, which are included to provide a further understanding of the exemplary embodiments and constitute a part of this specification, illustrate exemplary embodiments and, together with the description, serve to explain the principles of the exemplary embodiments.

[0022] [Figure 1] 1 illustrates an example of a fault management system for a network of electric vehicle charging stations in accordance with an illustrative embodiment. [Diagram 2] 1 illustrates an example flowchart of a method for managing faults in a network of electric vehicle charging stations according to an exemplary embodiment. [Diagram 3] 1 illustrates an example of a flowchart of a process for creating a maintenance alert in accordance with an illustrative embodiment. [Figure 4] 1 illustrates an example configuration of actions taken based on a failure priority index threshold according to an example embodiment. [Diagram 5] 1 illustrates an example of a hierarchical model of a network of electric vehicle charging stations for generating maintenance alerts in accordance with an illustrative embodiment. [Figure 6] 1 illustrates an example of an apparatus configured to implement one or more exemplary embodiments.

[0023] Like reference numbers may be used to designate like parts in the accompanying drawings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below in connection with the accompanying drawings is intended as an explanation of the embodiments, and is not intended to represent the only manner in which the embodiments may be constructed or utilized. The description sets forth functions of the embodiments and possible sequences of operations for constructing and operating the embodiments. However, the same or equivalent functions and sequences may be accomplished by different embodiments.

[0025] An electric vehicle charging station (CS) is used to charge an electric vehicle (EV). In this disclosure, the electric vehicle charging station may be referred to as a charging station. The charging station may be connected to a charging station management system (CSMS) by an OCPP protocol (Open Charge Point Protocol). EV drivers own electric vehicles (EVs) and charge their EVs at the charging stations.

[0026] Charging stations often have different technical faults: in a large charging station network that may comprise thousands or even tens of thousands of charging stations, at least hundreds, or even possibly thousands, of charging stations can fail for one reason or another at once.

[0027] Manually handling faults by a central organization is quite costly: for example, managing and resolving faults at over 1000 charging stations every day would require a large team of people, and managing faults globally would require a large and expensive arrangement to manually handle all faults.

[0028] To manage the network, information may be needed about which charging stations have faults, what kind of faults they are, how to fix the faults, and whether the faults have been fixed. For example, a ticket may be created for each fault, and then a support person may check each ticket. However, if there are thousands of charging stations, a ticketing system may cause too much work. It is also possible to automate ticketing and have a maintenance person responsible for each charging station, who automatically creates a ticket for each fault. However, in practice, there may be so many tickets and many false alarms. Because of this, people may very easily start ignoring the tickets and alerts. Maintenance people may also forget to keep updating the tickets, making it difficult to know which charging stations actually have faults and which ones have already been fixed.

[0029] If the charging station sends a fault alert, it may be automatically restarted. This may solve some problems, but not all of them. Furthermore, the charging station may be offline and therefore cannot be restarted remotely, or the charging station may not even send an alert that would trigger a restart.

[0030] Generally, a fault in a charging station can be detected by three standard methods. In the first method, a fault can be detected, for example, based on a disconnection of a web socket connection. When the web socket connection is disconnected, the charging station loses connection with the CSMS and can go offline. Furthermore, a fault can be detected based on a missing heartbeat, i.e., a periodic signal generated by the charging station to indicate normal operation and / or synchronization. If one or more heartbeats / signals are missed, the charging station may no longer communicate even if the web socket is open. Furthermore, a fault can be detected based on a status notification received from the charging station with a fault status indicating that the charging station has a fault.

[0031] However, there are two problems with the above detection method. Charging stations often send many status notifications, e.g., thousands per day. Furthermore, in many cases, the faults that charging stations report are automatically resolved. Therefore, it may not be reasonable to constantly alert maintenance personnel for each individual fault or offline period. Also, it may be common for charging to not work at a charging station for some reason, even though the charging station is online, sending heartbeats, and not sending any fault notifications.

[0032] The objective is to provide an automated system for recognizing and managing faults in electric vehicle charging stations, in a way that makes it possible to track which faults have been automatically resolved and which have not.

[0033] In an embodiment, a fault can be recognized even when the charging station is not transmitting fault information. In an embodiment, alerts regarding the fault can be created hierarchically. Thus, if a fault is not automatically resolved, the fault can be prioritized so that faults that require first attention can be handled before less critical faults. This method can improve the performance of a network of electric vehicle charging stations through improved fault management.

[0034] 1 illustrates an example of a fault management system for a network 100 of electric vehicle charging stations according to an exemplary embodiment. Network 100 may include hundreds of charging stations. In an embodiment, network 100 may include at least a thousand charging stations. In an embodiment, network 100 may include hundreds of thousands of charging stations.

[0035] Each charging station may be communicatively coupled to a CSMS server 102. The CSMS server 102 may be configured to perform one or more actions based on triggers received from the network 100. The CSMS server 102 may be configured to determine a fault priority index for each of the charging stations based on the triggers received from the respective charging stations.

[0036] One or more actions may be performed based on the fault priority index. The fault priority index may be used by the CSMS server 102 to prioritize some faults over others. Instead of reporting each fault 104 to the maintenance 106, the faults may be prioritized such that a notification is created only for those faults that are determined to require maintenance's attention. Notifications may be created after automated actions initiated by the CSMS server 102 do not resolve the fault and when the fault priority index exceeds a predefined threshold. Thus, maintenance of the network 100 may be automated and accelerated, since the number of alerts that the maintenance personnel 106 need to pay attention to is reduced and can be focused based on their urgency.

[0037] FIG. 2 illustrates an example flow chart of a method 200 for managing faults in a network of electric vehicle charging stations according to an example embodiment.

[0038] At 202, the method may include detecting a trigger for calculating a fault priority index for at least one electric vehicle charging station. In an embodiment, the trigger may be from a healthy charging station indicating that the charging station has gone offline or some other type of fault has occurred. A healthy charging station may refer to the charging station being online and functioning as it should, i.e., not faulted. In an embodiment, the trigger may be from a faulty charging station indicating that the charging station has recovered, meaning that the charging station may be back online and is no longer faulted, i.e., functioning as it should.

[0039] At 204, the method may include determining one or more fault indicators. The fault indicators may include at least one of a duration of an offline state, a frequency of an offline state, a duration of a fault, a frequency of a fault, or a number of commands rejected within a predetermined interval at the electric vehicle charging station.

[0040] The offline duration may provide information regarding how long each charging station was offline. The fault duration may provide information regarding how long each charging station was in a fault state. The duration may be measured, for example, in minutes. In an embodiment, a trigger may be used in calculating the duration. For example, the calculation of the duration may be started in response to a first trigger indicating a fault and stopped in response to a second trigger indicating recovery.

[0041] The offline frequency may provide information regarding how much time in total the charging station has been offline during a predetermined period, such as the past seven days. The fault frequency may provide information regarding the number of faults the charging station has reported during a predetermined period, such as the past seven days. In an embodiment, the number of faults may be determined based on triggers such that a first trigger received after receiving a second trigger may indicate a new fault.

[0042] The number of rejected commands may, for example, provide information about the number of commands (e.g., OCPP commands) sent by the CSMS to the charging station that the charging station rejected or did not respond to at all. The number of rejected commands may be compared to the number of accepted commands during a predefined period, such as the past seven days.

[0043] At 206, the method may include determining a fault priority index by combining values ​​of one or more fault indicators. The fault priority index may be calculated for each charging station in the network. In an embodiment, the fault priority index may have a value on a scale of 0 to 100, where 100 indicates the most urgent problem. However, this scale is only an example. In an embodiment, the calculation may also be triggered when a charging station previously indicated as faulty or offline returns to a normal state, i.e., when the charging station may send a notification of a normal (non-fault) status or when the charging station is online again.

[0044] Based on the fault priority index, it may be determined how urgent the fault is. For example, if the charging station has only been offline for 5 minutes, it may not be an urgent issue yet and may wait a while before an investigation of the problem is initiated. Thus, the total fault priority index may include a value determined based on the offline duration (time from offline to the current time). For example, if the charging station has been offline for less than 10 minutes, the fault priority index for the fault indicator may be 0 points. If the charging station has been offline for more than 24 hours, the fault priority index for the fault indicator may be 20 points. Other points from 1 to 19 may be determined linearly between the minimum (e.g., 10 minutes) and maximum (e.g., 24 hours) times. This is only an example, and the points and time limits are configurable.

[0045] The offline frequency may indicate whether the fault is a first problem or if the charging station has had problems before. The more problems the charging station has, the more urgent the fault may be. The fault priority index for the offline frequency may be calculated by summing the duration of all offline periods during a given time and calculating the offline percentage, where offline percentage=offline duration (min) / total given time (min). If the offline duration is less than 1%, the fault priority index value may be, for example, 0 points. If the offline duration is more than 80%, the fault priority index value may be, for example, 20 points. Other points may be calculated linearly between the minimum (1%) and maximum (80%) offline duration. This is only an example, and the points and percentage limits are configurable.

[0046] The duration of the fault may indicate the urgency of the fault. For example, if a charging station is faulty for only 5 minutes, it may not yet be an urgent issue. Thus, one may wait a while before an investigation of the problem can begin. The sum of the fault priority indexes may include a value determined based on the duration of the most recent fault time (time from fault state to non-fault state). For example, if a charging station is faulty for less than 10 minutes, the fault priority index for the fault indicator may be 0 points. If a charging station is faulty for more than 24 hours, the fault priority index for the fault indicator may be, for example, 20 points. Other points between 0 and 20 points may be determined linearly between the minimum (10 minutes) and maximum (24 hours) times. This is only an example, and the points and time limits are configurable.

[0047] The frequency of the fault may indicate whether the fault is a first time problem or if the charging station has had problems before. The more problems the charging station has, the more urgent the fault may be. The fault priority index for the frequency of the fault may be calculated by summing the duration of all fault times during a given time and calculating the percentage of faults, where percentage offline = duration of faults (min) / total of given time (min). If the duration of faults is less than 1%, the fault priority index value may be, for example, 0 points. If the duration of faults is more than 80%, the fault priority index value may be, for example, 20 points. Other points may be calculated linearly between the minimum (1%) and maximum (80%) of the fault duration. This is only an example, and the points and percentage limits are configurable.

[0048] A fault may occur even if the charging station is online and has not sent any fault notification. For example, if the charging station is not responding to some messages, it may be determined that the charging station is not functioning as intended. For example, the charging station may not respond to major OCPP messages such as "Allow charging", "Start charging", and "Stop charging". A fault priority index value may be calculated for the number of rejected commands by summing all of the unresponded and rejected messages for a given time period. In an embodiment, the fault priority index value may be determined based on the number of unresponded and / or rejected messages of a particular major message type. If the total count is greater than 50 messages, the fault priority index value may be, for example, 20 points. If the total number of messages is less than 5, the fault priority index value may be, for example, 0 points. Other points from 1 to 19 may be calculated linearly with respect to the number of messages, for example, between 5 and 50 messages. This is only an example, and the points and limits for messages are configurable.

[0049] At 208, the method may include initiating at least one action based on the fault priority index. The at least one action may include, for example, sending one or more commands configured to reboot or change one or more settings in the charging station. At least some of the commands may be sent automatically. If such remote action does not resolve the issue, a next action may be to send a message to maintenance personnel for further investigation.

[0050] Different alerts can be handled in different ways: An alert may point to a created or updated fault priority index. One option is to do nothing (e.g. wait and see how the situation develops). This may be the case for example for low priority alerts. A low priority alert may point to an updated fault priority index below a certain threshold. A low priority alert may be caused by some random error that disappears by itself and no interaction may be required.

[0051] Another option is to use some automated actions. In many cases, rebooting the charging station helps to correct the fault. In addition to rebooting, for example updating the firmware to the latest firmware version may also help to overcome the problem. Furthermore, automated actions may include sending a "cancel location" message to the SIM card of the charging station to reset the internet connection of the charging station.

[0052] After one or more automatic actions are performed, the method may include determining whether manual action is required, and if so, the method may include hierarchically creating a ticket to a remote or on-site maintenance person.

[0053] For example, a reboot can be attempted first, and if that does not resolve the fault, then the method may include attempting a remote firmware update. If that does not help, the method may include attempting to reset the Internet connection. One further option is to alert remote maintenance. Some faults may be caused, for example, by invalid settings, old firmware versions, etc., which can be resolved remotely by maintenance personnel. One further option is to alert on-site maintenance. For example, if something is physically broken, it may be necessary to alert maintenance personnel to replace one or more components of the charging station or to perform other maintenance work on-site.

[0054] The fault priority index may be updated each time a new trigger is detected. The method may include providing an updated report of the charging stations in the network. The report may include fault priority ordering of the charging stations based on the fault priority index, with the charging stations having the highest fault priority index first. Thus, the report indicates the most urgent faults. This may help a maintenance person select which alert to respond to. The report may further include information about which company owns the charging stations and who is the maintenance contact.

[0055] The report may include detailed information about the charging station, such as the owner and contact person of the charging station. The user can select any of the reported charging stations to see further details about the individual fault. The detailed fault report may include basic information about the charging station, such as the name of the charging station, location, company, contact information, and POI (Point of Interest) information. The report may detail what the priority index of the fault comes from (the fault indicator), how serious the problem is, and possible actions required to resolve the problem.

[0056] Exemplary embodiments may allow manual work to be avoided as much as possible through automated actions. Moreover, if manual work is necessary, it may be widely distributed so that it can be done as close as possible to the location where the fault can be fixed manually. For example, a global platform company may operate in dozens of different countries. If a high priority alert is received from one country, the central personnel of the platform company may not be able to resolve it. Therefore, based on the report, it may be determined from which country the fault information was received, which company the faulty charging station is associated with, and at which location of that company, and if possible, a maintenance person at that location may be directly alerted to see what is wrong with the charging station. A high priority alert may refer to an updated fault priority index above a certain threshold.

[0057] For example, the report may show issues with a selected charging station within a selected time interval, such as 1.1.2022 to 7.1.2022. The report may show that the charging station had, for example, three faults within that time. The first issue may be that the charging station was offline, which may be marked as a high priority fault. The report may show details about the event, such as that the charging station was offline 73% of the time in the past seven days. Additionally, the report may show a recommended action based on the type of fault and its priority. The second issue may be a medium priority fault, and the details may show that the charging station had poor GSM signal 15 times within the selected time. Again, the report may show a recommended action based on the faults and their priorities. The third issue may be a low priority fault. The details may show that the charging station reported two connector lock faults within the selected time interval. A low priority fault may not have a recommended action if no action is currently required based on the type and priority of the fault.

[0058] If any fault occurs in a charging station, it may get worse and worse over time. On the other hand, some maintenance action, such as a firmware update, may improve the situation. Therefore, it may be beneficial to track not only the current situation but also the trend of faults. Each trigger may be associated with a timestamp. The trend of faults may make it possible to track the overall status and directionality of the entire network. The trend of faults of the network may be determined by summing all fault priority index values ​​from all charging stations in the network for a given period based on the timestamps. Each trigger may be associated with a timestamp. Alternatively, or additionally, the trend of faults of individual charging stations may be tracked by summing the fault priority index values ​​of individual charging stations for a given period. In an embodiment, the method may include providing such trend of faults displayed to a user.

[0059] In an embodiment, the automated actions may be performed hierarchically. The method may include determining multiple priority levels based on the fault priority index value and respective actions for the different priority levels. The actions dedicated to each priority level may also be in a hierarchical order, so that if a first action does not resolve the issue (does not reduce the fault priority index), the next action may be performed, and so on.

[0060] FIG. 3 illustrates an example flow chart of a process 300 for creating a maintenance alert according to an example embodiment.

[0061] At 302, the method may include determining a current fault priority index for the charging station. Based on the current fault priority index, the method may include determining a priority level for the charging station. The method may include setting multiple priority levels having different thresholds for the fault priority index. Based on the priority level, the method may include determining whether one or more actions should be performed and what those actions are.

[0062] 4 illustrates an example configuration 400 of actions to be taken based on thresholds for the fault priority index according to an example embodiment. The priority levels and respective actions may be configurable by a user. Thus, different needs and practices, such as different service levels, of different entities may be taken into account. In an embodiment, the method may include, at 304, determining a group to which the charging station belongs and determining an action to be taken based on a configuration of thresholds and respective actions for the group.

[0063] For example, a fault priority index having a value between 0 and 4 points (out of 100) may be the lowest priority level and may not require any action. A second priority level may be determined for a fault priority index between 5 and 25 points. At the second priority level, the method may include performing a first automatic action, which may be restarting the charging station. A third priority level may be determined for a fault priority index between 25 and 59 points. At the third priority level, the method may include performing a first automatic action. If the first automatic action does not correct the fault, the problem may be alerted to remote maintenance personnel. A fourth priority level may be determined for a fault priority index between 50 and 79 points. At the fourth priority level, the automatic action may include a first automatic action and a second automatic action. The second automatic action may include performing a remote firmware update if a newer firmware version exists. If the first automatic action and the second automatic action do not correct the problem, the problem may be reported to remote maintenance. A fifth priority level may be determined for a fault priority index between 80 and 100 points. At a fifth priority level, the automatic actions may include a first, a second, and a third automatic action. The third automatic action may include resetting the charging station's Internet connection. For example, the method may include executing each of the automatic actions in response to the alert. Alternatively, the automatic actions may be executed one by one until the problem is corrected or until the problem is not corrected and each automatic action is executed, e.g., the alert is forwarded to remote maintenance or local maintenance.

[0064] At 306, the method may include calculating a new fault priority index value after the automatic action. At 308, the method may include determining whether the new fault priority index value still requires a maintenance action. For example, if the priority level has not changed, at 310, another automatic action configured for that priority level may be executed. If none of the automatic actions fixes the fault, the problem may be reported to remote maintenance. If that does not help, the problem may be reported to local maintenance. As shown in the example of FIG. 4, if the configured automatic action is not sufficient to solve the problem, only problems with higher levels of priority may be notified to remote or on-site maintenance. Thus, only the most urgent problems that cannot be solved automatically or remotely may be reported to on-site maintenance.

[0065] FIG. 5 illustrates an example of a hierarchical model of a network 500 of electric vehicle charging stations for generating maintenance alerts, according to an example embodiment.

[0066] Each electric vehicle charging station may belong to one or more groups 502, 504, 506, 508, 510, 512, 514. The groups may form a hierarchy where one parent group 514 may have multiple child groups 502, 504, 506, 508, 510, 512. A higher level child group 506, 512 may also be a parent group for a lower level child group 502, 504, 508, 510. Each group level may have a dedicated maintenance contact. The maintenance contact may be responsible for remote maintenance tasks or on-site maintenance tasks. Thus, maintenance may be considered at multiple levels and alerts may be escalated along the group levels as needed. For example, if a group does not manage and fix some faults for some reason, the issue may be escalated to a parent group. In general, parent groups may be responsible for their child groups.

[0067] In an embodiment, the method may include a step of prioritizing alerts hierarchically. Alerts and their urgency may be determined for each group. At the parent group level, several parent groups may be counted together to see the picture of several groups. Furthermore, groups may be grouped together at several levels to create drill-down possibilities of where the fault is. This may further enable escalation logic from one level to another at the hierarchical level of the groups.

[0068] Each child group 502, 504, 506, 508, 510, 512 may have a certain number of faults. Furthermore, a sum of the fault priority index points of the faults may be determined for the group. The fault and fault priority index of the parent group 514 is determined based on the sum of the values ​​of all the child groups 502, 504, 506, 508, 510, 512. If a lower level group 502, 504, 506, 508, 510, 512 fails to manage and correct one or more faults, the problem may be escalated to the parent group 514. However, the problem should not be escalated immediately or too easily. The objective is to escalate the problem only if one or more charging stations may have a serious problem.

[0069] In an embodiment, the method may include determining an escalation index, which refers to a number indicating how severe a fault can be in a group of charging stations before an alert about the fault is escalated to a higher level group, and may not be just a simple sum or average value of the faults.

[0070] For example, if a group has 10 charging stations and one of them has a serious fault, the average number of faults is high, i.e., 10% of the charging stations have faults. In this case, there is no need to trigger an escalation since only one charging station has a fault.

[0071] To make the escalation logic more appropriate, two indicators are combined for an escalation index, which is the sum of the charging stations with faults in each group and the fault priority index of those faults. Thus, if there are many charging stations with low priority faults, there may be no need for escalation. On the other hand, if there are many charging stations with high priority faults, escalation may be triggered.

[0072] In an embodiment, the escalation index may be determined based on the number of faulty charging stations having a fault priority index value equal to or greater than 25 points, the sum of the fault priority index points equal to or greater than 25 points, and the number of healthy charging stations having a fault priority index value less than 25 points. The escalation index may be determined as follows: Escalation index = (number of faulty charging stations * sum of fault priority index points) / (number of healthy stations).

[0073] For example, there may be 10 charging stations in a first group with a total number of fault priority index points of 920 (1000 points is the maximum). Additionally, the first group may have 500 healthy charging stations. Therefore, the escalation index is (10*920) / 500=18.4.

[0074] As another example, in a second group, there may be 20 charging stations with a total number of failure priority index points of 500 (maximum points is 2000) and there may be 30 healthy charging stations, where the escalation index is (20*500) / 30=333. Therefore, based on the escalation index, the situation of the second group is much worse than that of the first group, even though the total number of failure priority index points is higher in the first group.

[0075] In an embodiment, the method may include determining an escalation index limit for each child group before management of the fault is escalated to the respective parent group. For example, the escalation index limit for group 1 506 may be 150, the escalation index limit for group 2 512 may be 100, and the escalation index limit for group 1.1 504 may be 130. Thus, group 1 506 may receive an escalation alert if the escalation index of the lower levels (group 1.1 504 and group 1.2 502) is equal to or greater than 150. Either of the escalation index limits may be updated, for example, when the number of charging stations in the group changes. If the escalation index limit is exceeded, the method may include sending a report to maintenance. For example, each group may have a main maintenance contact person. The report may be sent, for example, via email or a web page. The report may include an overview of which organizations are having problems where, with drill-down to details also possible.

[0076] In an embodiment, the report may include data regarding an overall fault priority index for the group, the number of unhealthy charging stations, the number of healthy charging stations, and one or more sums of the fault indicators for the group. The maintenance personnel may retrieve further details, such as a list of faulty charging stations in the group and their individual fault priority indexes. Additionally, the report may enable the maintenance personnel to examine details regarding individual charging stations, such as each fault that occurred, the fault priority level, the fault indicator, the recommended action, and the action taken. Thus, management of urgent faults may be optimized.

[0077] FIG. 6 illustrates an example of an apparatus 600 configured to perform one or more exemplary embodiments.

[0078] The apparatus 600 may comprise at least one processor 602. The at least one processor 602 may comprise one or more of various processing devices, such as, for example, a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), processing circuitry with or without a DSP, or various other processing devices including integrated circuits, such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a dedicated computer chip, or the like.

[0079] The device 600 may further comprise at least one memory 604. The memory may be configured to store, for example, computer program code 606, for operating, for example, system software and application software. The memory 604 may comprise one or more volatile memory devices, one or more non-volatile memory devices, and / or a combination thereof. For example, the memory may be embodied as a magnetic storage device (e.g., a hard disk drive, a magnetic tape, etc.), a magneto-optical storage device, or a semiconductor memory (e.g., a mask ROM, a PROM (programmable ROM), an EPROM (erasable PROM), a flash ROM, a RAM (random access memory), etc.).

[0080] The device 600 may further comprise a communication interface 608 configured to enable the device 200 to transmit and / or receive information to / from other devices, such as a charging station. The communication interface may be configured to provide at least one wireless communication connection, such as, for example, a 3GPP® mobile broadband connection (e.g., 3G, 4G, 5G). However, the communication interface may be configured to provide one or more other types of connections, such as, for example, a wireless local area network (WLAN) connection, such as those standardized in the IEEE 802.11 series or the Wi-Fi Alliance, a short-range wireless network connection, such as, for example, a Bluetooth®, NFC (Near Field Communication) or RFID connection, a wired connection, such as, for example, a local area network (LAN) connection, a universal serial bus (USB) connection or an optical network connection, or a wired Internet connection. The communication interface 208 may include at least one antenna or be configured to be coupled to at least one antenna to transmit and / or receive radio frequency signals. One or more of the various types of connections may also be implemented as a separate communication interface that may be coupled or configured to be coupled to multiple antennas. The apparatus 600 may further comprise a user interface 610 comprising input and / or output devices.

[0081] If the device 600 is configured to implement several functions, several components and / or multiple components of the device 600, such as, for example, the at least one processor 602 and / or the memory 604, may be configured to implement the functions. Further, if the at least one processor 602 is configured to implement several functions, the functions may be implemented using, for example, program code 606 contained in the memory 604.

[0082] The functionality described herein may be performed, at least in part, by one or more computer program product components, such as software components. According to an embodiment, an apparatus includes a processor or processor circuitry, such as a microcontroller, configured to perform the operations and functional embodiments described herein by program code when executed. Alternatively or additionally, the functionality described herein may be performed, at least in part, by one or more hardware logic components. For example, but not limited to, exemplary types of hardware logic components that may be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and graphics processing units (GPUs).

[0083] The apparatus 600 comprises means for performing at least one of the methods described herein. In one embodiment, the means comprises at least one processor 602 and at least one memory 604 including program code 606 configured, when executed by the at least one processor 602, to cause the apparatus 600 to perform the method.

[0084] Apparatus 600 may comprise a computing device, such as, for example, a server device, a client device, a mobile phone, a tablet computer, a laptop, etc. Although apparatus 600 is shown as a single device, it will be appreciated that the functionality of apparatus 600 may be distributed across multiple devices, where applicable. In one embodiment, apparatus 600 may comprise a CSMS server device.

[0085] It is obvious to those skilled in the art that with the advancement of technology, the basic concept of the present invention can be implemented in various ways. Therefore, the present invention and its embodiments are not limited to the above examples, but may instead vary within the scope of the claims.

[0086] Further features of the method result directly from the functionality and parameters of the apparatus as described in the appended claims and throughout the specification, and therefore will not be repeated here. It should be noted that one or more operations of the method may be performed in a different order.

[0087] The apparatus may perform or be configured to perform any aspect of the method described herein. Furthermore, the computer program may include instructions that, when executed, cause the apparatus to perform any aspect of the method described herein. Furthermore, the apparatus may include means for performing any aspect of the method described herein. According to an exemplary embodiment, the means comprises at least one processor and a memory including program code, the at least one memory and the program code, when executed by the at least one processor, are configured to perform any aspect of the method.

[0088] Any ranges or device values ​​given herein may be expanded or modified without losing the effect sought, and any embodiment may be combined with another embodiment, unless expressly prohibited.

[0089] Although the subject matter has been described in language specific to structural features and / or acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example implementations of the claims and other equivalent features and acts are intended to be within the scope of the claims.

[0090] It should be understood that the benefits and advantages described above may relate to one embodiment or to multiple embodiments. The embodiments are not limited to those that solve any or all of the problems described or those that have any or all of the benefits and advantages described. Further, it should be understood that references to "an" or "an" item may refer to one or more of those items.

[0091] The operations of the methods described herein may be performed in any suitable order, or simultaneously as appropriate. Additionally, individual blocks may be deleted from any of the methods without departing from the scope of the subject matter described herein. Aspects of any of the embodiments described above may be combined with aspects of any of the other embodiments described to form further embodiments without losing the desired effect.

[0092] The term "comprising" is used herein to mean including specified methods, blocks, or elements, but such blocks or elements are not inclusive of an exclusive list and a method or apparatus may include additional blocks or elements.

[0093] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations with only analog and / or digital circuitry), and (b) combinations of hardware circuitry and software, such as (where applicable): (i) combinations of analog and / or digital hardware circuitry and software / firmware, and (ii) any portion of a hardware processor (including a digital signal processor) along with software that cooperates to cause a device such as a cell phone or server to perform various functions, software, and memory, and (c) hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (e.g., firmware) for operation (although the software may not be present if not required for operation). This definition of circuitry applies to all uses of the term in this application, including any claims.

[0094] As a further example, the term circuitry as used in this application covers merely a hardware circuit or processor (or processors), or a portion of a hardware circuit or processor, as well as its (or their) associated software and / or firmware implementations. The term circuitry also covers, for example, a baseband or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device, if applicable to certain claim elements.

[0095] It is to be understood that the above description is given by way of example only, and that various modifications may be made by those skilled in the art. The above specification, examples, and data provide a complete description of the structure and use of the exemplary embodiments. Although various embodiments have been described above with a degree of particularity, or with reference to one or more individual embodiments, those skilled in the art may make numerous modifications to the disclosed embodiments without departing from the scope of the present specification.

Claims

1. A method (200) performed by an apparatus (600), comprising: Detecting (202) a trigger for calculating a fault priority index for at least one electric vehicle charging station; Determining (204) one or more fault indicators at the electric vehicle charging station, the fault indicator including at least one of a duration of an offline state, a frequency of the offline state, a duration of a fault, a frequency of a fault, or a number of rejected commands within a predetermined interval; calculating (206) the fault priority index by combining values ​​of the one or more fault indicators; initiating (206) at least one action to manage a fault in the at least one charging station based on the fault priority index; The method (200).

2. 2. The method (200) of claim 1 , wherein the trigger comprises at least one of an indication that the electric vehicle charging station is offline, a notification of a fault status from the electric vehicle charging station, a rejection of a command by the electric vehicle charging station, a failure of the electric vehicle charging station to respond to a command, or a return to a normal state by the electric vehicle charging station.

3. The method (200) of claim 1 or 2, wherein the frequency of the offline states is determined based on a total duration of the offline states of the electric vehicle charging station within the predetermined interval.

4. The method (200) of any one of claims 1 to 3, wherein the frequency of the faults is determined based on a total duration of the faults at the electric vehicle charging station within the predetermined interval.

5. 5. The method (200) of any one of claims 1 to 4, wherein the at least one action includes at least one of: providing a list of the electric vehicle charging stations in order of urgency based on the fault priority index, providing a recommendation on how to correct the fault, rebooting the electric vehicle charging station, performing a firmware update on the electric vehicle charging station, resetting an internet connection for the charging station, alerting remote maintenance, or alerting on-site maintenance.

6. determining (302) a priority level of the fault priority index based on a plurality of priority levels having different predefined thresholds for the fault priority index; Initiating the at least one action based on the priority level of the fault priority index (304); The method (200) of any one of claims 1 to 5, further comprising:

7. updating (306) the fault priority index of the electric vehicle charging station after performing the at least one action; if the updated fault priority index indicates that the fault still exists, initiating another action according to the priority level of the fault priority index (310); The method of claim 6, further comprising:

8. Grouping a plurality of electric vehicle charging stations into a plurality of child groups; grouping the plurality of child groups into one or more parent groups; determining an escalation index for each group by multiplying the number of faulty electric vehicle charging stations in the group by the sum of the fault priority indexes in the group and dividing that value by the number of non-faulty electric vehicle charging stations in the group; providing a notification to a contact person of the parent group if the escalation index exceeds a predetermined limit for the child group; The method (200) of any one of claims 1 to 7, further comprising:

9. An apparatus (600) for managing faults in an electric vehicle charging station, the apparatus comprising at least one processor (602) and at least one memory (604), the at least one memory (604) configured to cause the apparatus (600) to, by the at least one processor (602), Detecting a trigger for calculating a fault priority index for the at least one electric vehicle charging station; determining one or more fault indicators at the electric vehicle charging station, the fault indicator including at least one of a duration of an offline condition, a frequency of the offline condition, a duration of the fault, a frequency of the fault, or a number of rejected commands within a predetermined interval; calculating the fault priority index by combining values ​​of the one or more fault indicators; Initiating at least one action to manage a fault in the at least one charging station based on the fault priority index. The apparatus (600) includes program code (606) configured to:

10. 10. The apparatus (600) of claim 9, wherein the trigger comprises at least one of an indication that the electric vehicle charging station is offline, a notification of a fault status from the electric vehicle charging station, a rejection of a command by the electric vehicle charging station, a failure of the electric vehicle charging station to respond to a command, or a return to a normal state by the electric vehicle charging station.

11. The apparatus (600) of any one of claims 1 to 10, wherein the at least one action includes at least one of: providing a list of the electric vehicle charging stations in order of urgency based on the fault priority index, providing a recommendation on how to correct the fault, rebooting the electric vehicle charging station, performing a firmware update on the electric vehicle charging station, resetting an internet connection for the charging station, alerting remote maintenance, or alerting on-site maintenance.

12. The at least one memory is configured to, by the at least one processor, determining a priority level of the fault priority index based on a plurality of priority levels having different predetermined thresholds for the fault priority index; Initiating the at least one action based on the priority level of the fault priority index. The apparatus (600) of any one of claims 1 to 11, further comprising program code configured to:

13. The at least one memory is configured to, by the at least one processor, updating the fault priority index of the electric vehicle charging station after the at least one action; If the updated fault priority index indicates that the fault still exists, initiate another action according to the priority level of the fault priority index. The apparatus (600) of claim 12, further comprising program code configured to:

14. The at least one memory is configured to, by the at least one processor, Group multiple electric vehicle charging stations into multiple child groups, grouping said plurality of child groups into one or more parent groups; determining an escalation index for each group by multiplying the number of faulty electric vehicle charging stations in the group by the sum of the fault priority indexes in the group and dividing that value by the number of non-faulty electric vehicle charging stations in the group; Providing a notification to a contact person of the parent group when the escalation index exceeds a predetermined limit for the child group. The apparatus (600) of any one of claims 9 to 13, further comprising program code configured to:

15. A computer readable medium comprising instructions which, when executed by a computer, cause the computer to perform the method (200) of any one of claims 1 to 8.

Citation Information

Patent Citations

  • Network failure diagnostic device, network failure diagnostic method and network failure diagnostic program

    JP2007096796A

  • Statistical methods and systems for detecting network anomalies

    JP2010531553A

  • Estimation of the severity level of network failures

    JP2015519812A

  • Network management device, network management system, and network management method

    JP2016009982A

  • Identification of Troubleshooting Options for Network Failures

    JP2017509262A