Backup Electric Vehicle Charging Management

Abstract

The present invention aims to provide a backup electric vehicle (EV) charging management device. In one embodiment, the backup EV charging management device is configured to execute the following steps: when a primary EV charging management system is available, synchronizing an identity cache of the backup EV charging management system with an identity cache of the primary EV charging management system; when the primary EV charging management system is unavailable, receiving a message from an EV charging station; in response to the message being a request to charge using the EV charging station, confirming whether the request should be granted by comparing identity information of a user who wishes to use the EV charging station with the identity cache of the backup EV charging management system; and in response to determining that the request should be granted, sending an acceptance message to the EV charging station.

Description

[Technical field]

[0001] TECHNICAL FIELD This disclosure relates to charging electric vehicles, and more particularly to methods and apparatus for managing backup electric vehicle charging. [Background technology]

[0002] Electric vehicle (EV) charging stations are typically managed by a management system such as a charging point management system (CPMS). The CPMS can perform different operations related to EV charging. Typically, the CPMS has a very complex technical architecture and logic. In order for the CPMS to return a valid response to a request from an EV charging station, all technical components must be functioning properly. However, no technology is perfect, and the CPMS may have technical issues. When this issue occurs, customers usually cannot use the EV charging station to charge their vehicles until the CPMS issue is resolved. Summary of the Invention [Problem to be solved by 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] The present invention aims to provide a backup electric vehicle charging management device and a corresponding method. The above and other objects are achieved by the features of the independent claims. Further embodiments are evident from the dependent claims, the description and the drawings. [Means for solving the problem]

[0005] A backup electric vehicle (EV) charging management device according to a first aspect includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code, together with the at least one processor, are configured to cause the backup EV charging management device to execute the following steps: when a primary EV charging management system is available, synchronizing an identification cache of a backup EV charging management system with an identification cache of the primary EV charging management system, where the identification cache of the primary EV charging management system includes identification information of an EV charging station user authorized to use an EV charging station; when the primary EV charging management system is unavailable, receiving a message from an EV charging station; in response to the message being a request to charge using the EV charging station, confirming whether the request should be granted by comparing an identification information of the user who wishes to use the EV charging station with the identification information cache of the backup EV charging management system, where the request includes the identification information of the user who wishes to use the EV charging station; and in response to determining that the request should be granted, sending an acceptance message to the EV charging station indicating that use of the EV charging station is accepted. The backup EV charging management system allows users to charge using an EV charging station, for example, when the primary EV charging management system is unavailable.

[0006] In one embodiment of the first aspect, the at least one memory and the computer program code, together with the at least one processor, are further configured to cause the backup EV charging management device to execute, when comparing the identity of the user who wishes to use the EV charging station with an identity cache of the backup EV charging management system, in response to an error in the identity cache of the backup EV charging management system, sending an acceptance message to the EV charging station indicating acceptance of use of the EV charging station. The backup EV charging management device allows, for example, a user to charge using an EV charging station when a primary EV charging management system is unavailable and there is an error in the identity cache.

[0007] In another embodiment of the first aspect, the error of the identity cache of the backup EV charging management system includes the identity cache of the backup EV charging management system being unavailable or out of date. The backup EV charging management device allows a user to charge using an EV charging station, for example, when the primary EV charging management system is unavailable and the identity cache is unavailable or out of date.

[0008] In another embodiment of the first aspect, the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the backup EV charging management device to perform the step of sending a confirmation message to the EV charging station in response to a message including a boot notification, a status notification, a meter value, and / or a heartbeat, The backup EV charging management device may respond to less critical messages with reduced complexity and / or increased reliability, for example, when a primary EV charging management system is unavailable.

[0009] In another embodiment of the first aspect, the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the backup EV charging management device to: store the message and the response sent by the backup EV charging management device in response to the message in a message cache; and, in response to the primary EV charging management system becoming available, provide the message and the response from the message cache to the primary EV charging management system, where the backup EV charging management device can, for example, provide the stored message to the primary EV charging management system for appropriate processing of the message.

[0010] In another embodiment of the first aspect, the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the backup EV charging management device to perform the step of storing in the message cache the message and a response sent by the backup EV charging management device in response to the message, together with an identification of the EV charging station and / or a status indicating whether the message was provided to the primary EV charging management system. The backup EV charging management device can, for example, track which messages have been processed by the primary EV charging management system.

[0011] In another embodiment of the first aspect, the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the backup EV charging management device to perform the steps of: receiving, for each message, an indication from the primary EV charging management system of whether the message was accepted or rejected by the primary EV charging management system; and generating an offload report based at least on the received indication.

[0012] In another embodiment of the first aspect, the offload report includes an indication of each message rejected by the primary EV charging management system and an identifier of the EV charging station that sent the message. A backup EV charging management system can, for example, track which EV charging stations may be having charging issues.

[0013] In another embodiment of the first aspect, the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the backup EV charging management device to perform the step of providing the offload report to an administrator, where the backup EV charging management device can conveniently provide the administrator with information regarding which EV charging stations may have charging issues, for example.

[0014] It should be understood that the embodiments of the first aspect described above can be used in combination with each other. Some embodiments can be combined together to form further embodiments.

[0015] An electric vehicle (EV) charging system according to a second aspect includes a primary EV charging management system, a backup EV charging management system including the backup EV charging management device according to the first aspect, at least one EV charging station, and a load balancer configured to forward messages from the at least one EV charging station to the primary EV charging management system when the primary EV charging management system is available, and to forward messages from the at least one EV charging station to the backup EV charging management system when the primary EV charging management system is unavailable.

[0016] A method according to a third aspect includes the steps of: when a primary electric vehicle (EV) charging management system is available, synchronizing an identity cache of a backup EV charging management system with an identity cache of the primary EV charging management system, where the identity cache of the primary EV charging management system includes identity information of an EV charging station user authorized to use an EV charging station; when the primary EV charging management system is unavailable, receiving a message from the EV charging station, and in response to the message being a request to charge using the EV charging station, verifying whether the request should be authorized by comparing identity information of the user attempting to use the EV charging station with an identity cache of the backup EV charging management system, where the request includes identity information of the user attempting to use the EV charging station; and in response to determining that the request should be authorized, sending an acceptance message to the EV charging station indicating acceptance of use of the EV charging station.

[0017] In one embodiment of the third aspect, the method further includes, when comparing an identification information of the user who wishes to use the EV charging station with an identification information cache of the backup EV charging management system, in response to an error in the identification information cache of the backup EV charging management system, sending an acceptance message to the EV charging station indicating acceptance of use of the EV charging station.

[0018] In one embodiment of the third aspect, the error in an identity cache of the backup EV charging management system includes an identity cache of the backup EV charging management system being unavailable or out of date.

[0019] It should be understood that the embodiments of the third aspect described above can be used in combination with each other. Some embodiments can be combined together to form further embodiments.

[0020] A computer program product according to a fourth aspect comprises program code configured to perform the method according to the third aspect when said computer program is run on a computer.

[0021] 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 connection with the accompanying drawings. [Brief description of the drawings]

[0022] Hereinafter, the embodiments will be described in more detail with reference to the accompanying drawings.

[0023] [Figure 1] 1 illustrates a backup electric vehicle charging management device according to one embodiment. [Diagram 2] 1 shows a schematic diagram of an electric vehicle charging system according to an example. [Diagram 3] 1 shows a schematic diagram of an electric vehicle charging system according to one embodiment. [Figure 4] FIG. 2 illustrates a schematic diagram of the functionality of an electric vehicle charging system when a primary system is available, according to one embodiment. [Diagram 5] FIG. 2 illustrates a schematic diagram of the functionality of an electric vehicle charging system when the primary system is unavailable, according to one embodiment. [Figure 6] FIG. 2 illustrates a schematic diagram of the functionality of an electric vehicle charging system when a primary system goes from unavailable to available again, according to one embodiment. [Figure 7] FIG. 2 illustrates a schematic diagram of the functionality of an electric vehicle charging system when a primary system is available and a backup system is in advanced mode, according to one embodiment. [Figure 8] FIG. 2 illustrates a schematic diagram of the functionality of an electric vehicle charging system when the primary system is unavailable and the backup system is in advanced mode, according to one embodiment. [Figure 9] 1 illustrates a schematic diagram of a message cache according to one embodiment. [Figure 10] 1 illustrates a schematic diagram of an offload report according to one embodiment. [Figure 11] 1 shows a schematic diagram of a method according to an embodiment.

[0024] Hereinafter, like reference numbers will be used to denote like parts in the accompanying drawings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] In the following description, reference is made to the accompanying drawings which form a part of this disclosure, and in which are shown by way of illustration specific aspects in which the present disclosure may be arranged. It is to be understood that other aspects may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Thus, the following detailed description is not to be taken in a limiting sense, with the scope of the present disclosure being defined by the appended claims.

[0026] For example, it should be understood that disclosure related to a described method also applies to a corresponding apparatus or system configured to perform the method, and vice versa. For example, when describing a particular method step, a corresponding apparatus may include units that perform the described method step, even if not explicitly described or shown. Conversely, when describing a particular apparatus, for example, in terms of functional units, a corresponding method may include steps that perform the described function, even if not explicitly described or shown. Furthermore, it should be understood that features of the various exemplary aspects described herein can be combined with each other, unless otherwise specified.

[0027] FIG. 1 illustrates a backup electric vehicle (EV) charge management device according to one embodiment.

[0028] In one embodiment, the backup EV charging management device 100 includes at least one processor 101 and at least one memory 102 that includes computer program code.

[0029] In one embodiment, the at least one memory 102 and the computer program code, together with the at least one processor 101, are configured to cause the backup EV charging management device 100 to perform a step of synchronizing an identification information cache of the backup EV charging management system with an identification information cache of the primary EV charging management system when the primary EV charging management system is available, where the identification information cache of the primary EV charging management system includes identification information of EV charging station users authorized to use the EV charging station.

[0030] In this specification, the primary EV charging management system may be referred to simply as a primary system or the like, and the backup EV charging management system may be referred to simply as a backup system or the like.

[0031] Backup EV charging management device 100 may correspond to any device configured to control a backup EV charging management system. Where a backup system is disclosed herein to perform several functions, backup EV charging management device 100 may be configured to at least partially perform those functions.

[0032] Herein, identification information may for example comprise the so-called idTag of the user.

[0033] The backup EV charging management device 100 may further be configured to perform the step of receiving a message from an EV charging station when the primary EV charging management system is unavailable.

[0034] The primary EV charging management system may be “unavailable” at any time if the EV charging station cannot access the primary EV charging management system. For example, the communication link between the EV charging station and the primary EV charging management system may have failed, the primary EV charging management system or a portion thereof may have failed, and / or the primary EV charging management system may be offline for maintenance or similar purposes.

[0035] The message may include, for example, information related to the operation of the EV charging station and / or a request related to the operation of the EV charging station.

[0036] The backup EV charging management device 100 may further be configured to perform a step of verifying whether the request should be granted by comparing, in response to a message that is a request to charge using an EV charging station, an identification information of a user who wishes to use the EV charging station with an identification information cache of the backup EV charging management system, where the request includes an identification information of the user who wishes to use the EV charging station.

[0037] Because the identity cache of the backup system is synchronized with the identity cache of the primary system, the backup EV charging management device 100 can check whether the request should be granted even if the primary system is unavailable, so that the user can still use the EV charging station even if the primary system is unavailable.

[0038] The identity cache may, for example, contain a simple whitelist of identities that should be allowed to charge, or alternatively, the identity cache may contain more complex information / data that enables the backup EV charging management device 100 to verify whether a request should be allowed or not.

[0039] The backup EV charging management device 100 may further be configured to perform the step of sending an acceptance message to the EV charging station indicating acceptance of use of the EV charging station, in response to determining that the request should be granted.

[0040] The acceptance message may include any data that enables the EV charging station to recognize that the EV charging station should be accepted for use. The content of the acceptance message may be defined in a standard / protocol such as, for example, the open charge point protocol (OCPP).

[0041] The backup EV charging management device 100 may further be configured to perform the step of sending a denial message to the EV charging station indicating denial of use of the EV charging station, in response to determining that the request should not be granted.

[0042] The backup EV charging management device 100 may include at least one processor 101. The at least one processor 101 may include one or more of a variety of 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 a variety of other processing devices including integrated circuits, such as 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.

[0043] The backup EV charging management device 100 may further include a memory 102. The memory 102 may be configured to store, for example, a computer program, etc. The memory 102 may include one or more volatile memory devices, one or more non-volatile memory devices, and / or a combination of one or more volatile and non-volatile memory devices. For example, the memory 102 may be embodied as a magnetic storage device (e.g., a hard disk drive, a floppy disk, a magnetic tape, etc.), a magneto-optical storage device, 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.).

[0044] If the backup EV charging management apparatus 100 is configured to implement several functions, a component and / or several parts of the backup EV charging management apparatus 100, such as the at least one processor 101 and / or the memory 102, may be configured to implement the functions. Further, if the at least one processor 101 is configured to implement several functions, the functions may be implemented using, for example, program code included in the memory 102. For example, if the backup EV charging management apparatus 100 is configured to perform an operation, the at least one memory 102 and the computer program code, together with the at least one processor 101, may be configured to cause the backup EV charging management apparatus 100 to perform the operation.

[0045] In some embodiments, the backup EV charging management apparatus 100 may be implemented as and / or as part of a cloud computing system.

[0046] The backup system can have a simple and lightweight structure and therefore can be more robust and fault tolerant than the primary system.

[0047] The backup system may be compatible with a variety of different EV charging station models. Alternative solutions may be proprietary and specific to the EV charging station model.

[0048] A backup system can ensure, at least in most cases, that only authorized people can use EV charging stations to charge, so that invalid data is not recorded and data is not lost, which allows, for example, correct billing of users.

[0049] FIG. 2 illustrates a schematic diagram of an EV charging system 200 according to an example.

[0050] The system 200 may include one or more EV charging stations (CSs) 201 connected to a primary EV charging management system 202. The system 200 may further include a load balancer 210. The load balancer 210 may forward messages from the one or more EV charging stations 201 to the primary EV charging management system 202 when the primary EV charging management system 202 is available. The load balancer 210 may further forward messages from the primary EV charging management system 202 to the one or more EV charging stations 201 when the primary EV charging management system 202 is available. The load balancer 210 may implement, for example, an application programming interface (API), and the one or more EV charging stations 201 may communicate with the primary system 202 using the application programming interface.

[0051] The primary EV charging management system 202 may include, for example, a charging point management system (CPMS). The primary system 202 can handle different operations related to EV charging. The one or more EV charging stations 201 and the primary system 202 can communicate using, for example, the OCPP.

[0052] As used herein, any message sent and / or received by any system / device / component may include an OCPP message.

[0053] For example, when a user wants to start charging using the EV charging station 201, he or she can present a radio frequency identification (RFID) card to the EV charging station 201. The station 201 can query the primary system 202 whether the RFID is valid, for example, using the OCPP protocol. The primary system 202 can process this request and reply to the EV charging station 201 whether charging via RFID is allowed.

[0054] The primary system 202 can have a very complex technical architecture and logic. A modern CPMS can include dozens or hundreds of different services, parts, data storage, complex business logic, integration with third-party systems, etc. For example, in the example of Fig. 2, the primary system 202 includes various interconnected services and parts 203, data storage 204, and integration with third parties 205. All technical parts need to function correctly in order for the primary system 202 to return a valid response, such as accepting or rejecting a charging request from the EV charging station 201.

[0055] Thus, the primary system 202 may have a technical problem, which typically prevents users from using the EV charging station 201 to charge until the problem in the primary system 202 is resolved.

[0056] FIG. 3 shows a schematic diagram of an EV charging system 200 according to one embodiment.

[0057] In one embodiment, the EV charging system 200 includes a primary EV charging management system 202, a backup EV charging management system 301 including the backup EV charging management device 100, at least one EV charging station 201, and a load balancer 210 configured to forward messages from the at least one EV charging station 201 to the primary EV charging management system 202 when the primary EV charging management system 202 is available and to forward messages from the at least one charging station 201 to the backup EV charging management system 301 when the primary EV charging management system 202 is unavailable.

[0058] Backup system 301 can function as a lightweight, simple backup system that does not have all the complex business logic, integration, data storage, etc. of primary system 202. Thus, backup system 301 can be more fault tolerant and less expensive.

[0059] The backup system 301 may have the capability to process important OCPP messages such as heartbeat, boot notification, authentication, start and stop messages even if the primary system 202 is offline.

[0060] In case of a critical problem in the primary system 202, all OCPP traffic from the EV charging station 201 can be directed to the backup system 301, for example by the load balancer 210. The backup system 301 can then process some critical OCPP messages from the EV charging station 201, and respond to the EV charging station 201 based on limited simple logic, allowing the user to continue charging using the EV charging station 201. The backup system 301 can also store some or all OCPP messages in a local message cache 304, so that when the primary system 202 becomes available again, these messages can be processed by the primary system 202, ensuring that no data is lost during the downtime of the primary system 202.

[0061] Any of the devices / systems / components / modules disclosed herein can communicate with each other using, for example, a data connection. The data connection may be any connection that allows the devices / systems / components / modules to communicate with each other. The data connection may include, for example, the Internet, Ethernet, 3G, 4G, 5G, long-term evolution (LTE), new generation mobile communications (NR), Wi-Fi, other wired or wireless connections, or some combination thereof. For example, the data connection may include a wireless connection, such as a Wi-Fi, an Internet connection, and an Ethernet connection.

[0062] FIG. 4 illustrates a schematic diagram of the functionality of an EV charging system when a primary system is available, according to one embodiment.

[0063] In normal circumstances, when the primary system 202 is available, all traffic from the EV charging station 201 may be directed to the primary system 202. The primary system 202 may then handle the traffic in a normal manner according to the normal logic of the primary system 202.

[0064] Backup system 301 may be idle under normal circumstances.

[0065] FIG. 5 illustrates a schematic diagram of the functionality of an EV charging system when the primary system is unavailable, according to one embodiment.

[0066] If the primary system 202 is unavailable, for example due to technical issues, traffic from the EV charging station 201 can be directed to the backup system 301. This can be done manually or automatically, for example based on a health check of the primary system 202.

[0067] When traffic is directed to the backup system 301, the backup system 301 can function in the so-called "simple mode" in the following manner.

[0068] In one embodiment, the backup EV charging management device 100 is configured to perform the step of sending a confirmation message to the EV charging station in response to a message including a boot notification, a status notification, a meter value, and / or a heartbeat.

[0069] The backup system 301 can be configured with static response messages to important OCPP messages, for example, in response to boot notification, status notification, meter value, and heartbeat messages, the backup system 301 can simply respond with an acknowledgement message, for example, as defined in the OCPP protocol.

[0070] When in simple mode, for grant, start transaction and stop transaction messages, the backup system 301 can always give a static "accept" response regardless of the idTag used to start or stop charging.

[0071] In addition to providing standard responses, the backup system 301 may store all sent and received request and response messages in a message cache 304 .

[0072] FIG. 6 illustrates a schematic diagram of the functionality of an EV charging system when the primary system goes from unavailable to available again, according to one embodiment.

[0073] In one embodiment, the backup EV charging management device 100 is further configured to perform the steps of storing the message and a response sent by the backup EV charging management device 100 in response to the message in a message cache 304, and providing the message and the response from the message cache 304 to the primary EV charging management system 202 in response to the primary EV charging management system 202 becoming available.

[0074] After the problem with the primary system 202 has been resolved and the primary system 202 is available again, traffic can be switched back to the primary system 202 .

[0075] When the primary system 202 becomes available, the backup system 301 can provide new messages stored in the message cache 304 to the primary system 202. This may be referred to as message offloading. The primary system 202 can then process the messages. This may be necessary, for example, to ensure that correct charging detail records are created for the primary system 202, e.g., so that a user is billed correctly.

[0076] The backup system 301 can read all outstanding messages from the message cache 304. The messages may include, for example, BootNotification, StatusNotification, Authorize, StartTransaction, and / or StopTransaction messages.

[0077] The backup system 304 can provide each message to the primary system 202, for example via an API. The primary system 202 can then process the message normally and handle normal logic such as creating a charging detail record.

[0078] It is possible that the primary system 202 may reject some messages, e.g., authorization messages with invalid user identification information such as an idTag. Because of this, the backup system 301 may track which messages were processed, approved, or rejected. The backup system 301 may then generate reports of successful or problematic charging during periods when the primary system 202 was unavailable.

[0079] FIG. 7 illustrates a schematic diagram of the functionality of an EV charging system when the primary system is available and the backup system is in advanced mode, according to one embodiment.

[0080] 4 embodiment, under normal circumstances, if the primary system 202 is available, all traffic from the EV charging station 201 may be directed to the primary system 202. The primary system 202 may then handle the traffic in the normal manner according to the normal logic of the primary system 202.

[0081] When in so-called "advanced mode," backup system 301 can synchronize its identity cache 303 with the identity cache of primary system 202 when primary system 202 is available. The identity cache of primary system 202 may be embodied, for example, in any of data storages 204 of primary system 202.

[0082] The identity cache of the primary system 202 may contain identities of EV charging station users who are authorized to use the EV charging station 201. For example, when a new user registers with the system, a new RFID may be created and linked to the customer's account.

[0083] In advanced mode, all changes to user identities, such as idTags, made on the primary system 202 can be mirrored to the backup system 301. As a result, the backup system 301 always has a valid copy of all user identities.

[0084] FIG. 8 illustrates a schematic diagram of the functionality of an EV charging system when the primary system is unavailable and the backup system is in advanced mode, according to one embodiment.

[0085] In an error situation, if the primary system 202 is unavailable, traffic can be switched to the backup system 301 as in the simple mode. Messages can be processed in a similar manner to the simple mode, with the following exceptions:

[0086] For the accept and / or stop processing messages, instead of always responding with "accept", the backup system 301 can check whether the identity in the message is valid from the identity cache 303. If so, the backup system 303 can respond with "accept" to the EV charging station 201, but if the idTag is found to be invalid, the backup system 301 can respond with "reject" to the message.

[0087] One benefit of the advanced mode is that only users with valid identification information can charge using the EV charging station 201. Thus, users cannot initiate charging using a random RFID token.

[0088] In one embodiment, the backup EV charging management device 100 is further configured to perform a step of, when comparing the identification information of a user who wishes to use the EV charging station with the identification information cache 303 of the backup EV charging management system 301, sending an acceptance message to the EV charging station indicating that use of the EV charging station 201 is accepted in response to an error in the identification information cache 303 of the backup EV charging management system 301.

[0089] In one embodiment, the error in the identity cache 303 of the backup EV charging management system 301 includes the identity cache 303 of the backup EV charging management system 301 being unavailable or out of date.

[0090] For example, if the identity cache 303 has not been updated recently, the identity cache may be out of date, and therefore the information content of the identity cache 303 may also be out of date. For example, the backup EV charging management device 100 may be further configured to check whether the identity cache 303 has been updated within a preset period of time. If the identity cache 303 has not been updated within a preset period of time, the backup EV charging management device 100 may consider the identity cache 303 to be out of date. Alternatively or additionally, the out-of-date status of the identity cache 303 may be identified using some other procedure.

[0091] By default, the backup system 301 may be in an advanced mode so that it can authenticate users attempting to charge and ensure that only valid users can use the EV charging station 201 .

[0092] In simple mode, where the backup system 301 can accept all messages, anyone can theoretically charge for free, for example, using any owned RFID token.

[0093] However, the advanced mode is more error prone than the simple mode, as it requires synchronizing data between the primary and backup systems, additional logic, etc., which can fail, but the simple mode can be robust and essentially foolproof.

[0094] When traffic is directed to the backup system 301, the backup system 301 may always start operating in advanced mode initially. However, if there is any technical issue, such as the identity cache 303 not working or out of date, the backup system 301 may switch to simple mode to ensure that users can use the EV charging station 201.

[0095] FIG. 9 illustrates a schematic diagram of a message cache according to one embodiment.

[0096] In one embodiment, the backup EV charging management device 100 is further configured to perform the step of storing in the message cache 304 the identification information of the EV charging station and / or a status indicating whether the message has been provided to the primary EV charging management system, along with the message and a response sent by the backup EV charging management device 100 in response to the message.

[0097] The message cache 304 may store, for each message stored in the message cache 304, at least a portion of: a unique identifier 901 of the EV charging station that sent the message; an OCPP raw message 902, which is the content of the request message and / or response message sent to and / or received from the EV charging station; a status 903 indicating whether the message is new or has already been offloaded to the primary system 202; and a primary system response 904 indicating the primary system's 202 response to the message, e.g., indicating that the primary system 202 rejects the authorization message or start processing message if the idTag in the message is invalid.

[0098] The backup system 301 can send a raw message 902 to the primary system 202 once the primary system 202 becomes available again.

[0099] Once the primary system 202 becomes available again, the backup system 301 can begin offloading messages from the message cache 304 to the primary system 202 .

[0100] For example, backup system 301 can provide all messages with a status of "new" to primary system 202. A message sending component of backup system 301 can wait for a response from primary system 202 to each message. After receiving a response, backup system 301 can update status 903 to "upload to primary system" and update primary system response 904 to either "accept" or "reject."

[0101] FIG. 10 illustrates a schematic diagram of an offload report according to one embodiment.

[0102] In one embodiment, the backup EV management device 100 is further configured to perform the steps of receiving, for each message, an indication from the primary EV charging management system 202 of whether the message was approved or rejected by the primary EV charging management system 202, and generating an offload report based at least on the received indication.

[0103] In one embodiment, the offload report includes an indication of each message that was rejected by the primary EV charging management system 202 and an identifier of the EV charging station that sent the message.

[0104] After messages are offloaded from the backup system 301 to the primary system 202 , the backup system 301 can generate an offload report 1000 .

[0105] The offload report 1000 can conveniently report when some information is lost, such as when the system fails to create important charging details.

[0106] The offload report 1000 may include at least some of the following: the number of authorization, start processing, and stop processing messages processed, the number of messages accepted or rejected by the primary system 202, a list of station identifiers for rejected messages, and the number of rejected messages (in other words, no charging detail records).

[0107] In one embodiment, the backup EV charging management device 100 is further configured to perform the step of providing the offload report 1000 to an administrator.

[0108] After the report 1000 is ready, the backup system 301 can send / provide the report to an administrator of the primary system 202. The administrator can verify that all data was processed and manually check for possible errors, such as rejected messages.

[0109] FIG. 11 shows a schematic diagram of a method 1100 according to an embodiment.

[0110] In one embodiment, method 1100 includes step 1101, when the primary EV charging management system is available, synchronizing an identity cache of the backup EV charging management system with an identity cache of the primary EV charging management system, where the identity cache of the primary EV charging management system includes identities of EV charging station users authorized to use the EV charging station.

[0111] The method 1100 may further include receiving 1102 a message from an EV charging station if the primary EV charging management system is unavailable.

[0112] Method 1100 may further include step 1103, in response to the message being a request to charge using the EV charging station, determining whether the request should be granted by comparing an identity of a user attempting to use the EV charging station with an identity cache of the backup EV charging management system, where the request includes an identity of the user attempting to use the EV charging station.

[0113] The method 1100 may further include, in response to determining that the request should be granted, sending 1104 an acceptance message to the EV charging station indicating acceptance of use of the EV charging station.

[0114] The method 1100 may be performed by the backup EV charging management apparatus 100 of Figure 1. Further features of the method 1100 result directly from the functionality and parameters of the backup EV charging management apparatus 100. The method 1100 may be performed, at least in part, by a computer program.

[0115] The apparatus may include means for performing any aspect of the methods described herein. In one embodiment, the means includes at least one processor and a memory including program code, the at least one processor and the program code configured, when executed by the at least one processor, to perform any aspect of the methods.

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

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

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

[0119] The steps of the methods described herein may be performed in any suitable order, or simultaneously if desired. Additionally, individual blocks may be deleted from any method without departing from the spirit and scope of the subject matter described herein. Also, any aspect of any of the embodiments described above may be combined with any aspect of any of the other embodiments described above to form further embodiments without losing the desired effect.

[0120] As used herein, the term "comprising" means including the specified methods, blocks, or elements, but such blocks or elements do not constitute an exclusive list and the method or apparatus may include additional blocks or elements.

[0121] It should 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 spirit or scope of the present specification.

Claims

1. A backup electric vehicle (EV) charging management device (100), At least one processor (101); at least one memory (102) containing computer program code; The at least one memory (102) and the computer program code, together with the at least one processor (101), cause the backup EV charging management device (100) to: When a primary EV charging management system (202) is available, synchronizing an identification information cache (303) of a backup EV charging management system (301) with an identification information cache of the primary EV charging management system (202), wherein the identification information cache of the primary EV charging management system includes identification information of EV charging station users authorized to use the EV charging station (201); receiving a message from the EV charging station (201) when the primary EV charging management system (202) is unavailable; responding to a message that is a request to charge using the EV charging station (201), verifying whether the request should be granted by comparing an identification information of a user who wishes to use the EV charging station with an identification information cache of the backup EV charging management system, the request including an identification information of a user who wishes to use the EV charging station; in response to determining that the request should be granted, sending an acceptance message to the EV charging station indicating acceptance of use of the EV charging station; a backup EV charging management device (100) configured to execute a step of: when comparing the identification information of the user who wishes to use the EV charging station with the identification information cache (303) of the backup EV charging management system, in response to an error in the identification information cache of the backup EV charging management system, sending an acceptance message to the EV charging station indicating that use of the EV charging station is accepted.

2. The backup EV charging management device (100) of claim 1, wherein an error in the identification information cache (303) of the backup EV charging management system includes the identification information cache (303) of the backup EV charging management system (301) being unavailable or out of date.

3. The at least one memory (102) and the computer program code, together with the at least one processor (101), further configure the backup EV charging management device (100) to: The backup EV charging management device (100) of claim 1 or claim 2, configured to execute a step of sending a confirmation message to the EV charging station in response to a message including a boot notification, a status notification, a meter value, and / or a heartbeat.

4. The at least one memory (102) and the computer program code, together with the at least one processor (101), further configure the backup EV charging management device (100) to: storing the message and a response sent by the backup EV charging management device (100) in response to the message in a message cache (304); and providing the message and the response to the primary EV charging management system from the message cache (304) in response to the primary EV charging management system (202) becoming available.

5. The at least one memory (102) and the computer program code, together with the at least one processor (101), further configure the backup EV charging management device (100) to: The backup EV charging management device (100) of claim 4, configured to execute a step of storing in the message cache (304) identification information of the EV charging station and / or a status indicating whether the message has been provided to the primary EV charging management system, together with the message and the response sent by the backup EV charging management device in response to the message.

6. The at least one memory (102) and the computer program code, together with the at least one processor (101), further configure the backup EV charging management device (100) to: receiving, for each message, from the primary EV charging management system, an indication of whether the message was approved or rejected by the primary EV charging management system; and generating an offload report based on at least the received instruction.

7. 7. The backup EV charging management device (100) of claim 6, wherein the offload report includes an indication of each message rejected by the primary EV charging management system (202) and an identifier of the EV charging station that sent the message.

8. The backup EV charging management device (100) of claim 6 or claim 7, wherein the at least one memory (102) and the computer program code, together with the at least one processor (101), are further configured to cause the backup EV charging management device (100) to perform a step of providing the offload report to an administrator.

9. An electric vehicle (EV) charging system (200), comprising: A primary EV charging management system (202); A backup EV charge management system (301) including the backup EV charge management device (100) according to claim 1 or 2; At least one EV charging station (201); a load balancer (210) configured to forward messages from the at least one EV charging station (201) to the primary EV charging management system (202) when the primary EV charging management system (202) is available, and to forward messages from the at least one EV charging station (201) to the backup EV charging management system (202) when the primary EV charging management system (202) is unavailable.

10. A backup electric vehicle (EV) charging management device (100), At least one processor; a memory containing program code; The at least one processor and the program code, when executed by the at least one processor, the method includes: When a primary electric vehicle (EV) charging management system is available, the at least one processor synchronizes an identity cache of a backup EV charging management system with an identity cache of the primary EV charging management system (1101), the identity cache of the primary EV charging management system including identities of EV charging station users authorized to use the EV charging station; receiving a message from the EV charging station when the primary EV charging management system is unavailable (1102); a step (1103) of confirming whether the request should be granted by the at least one processor in response to a message that is a request to charge using the EV charging station by comparing an identification information of a user who wishes to use the EV charging station with an identification information cache of the backup EV charging management system, the request including an identification information of a user who wishes to use the EV charging station; In response to the at least one processor determining that the request should be granted, sending an acceptance message to the EV charging station indicating acceptance of use of the EV charging station (1104); and when the at least one processor attempts to compare the identification information of the user attempting to use the EV charging station with an identification information cache of the backup EV charging management system, in response to an error in the identification information cache of the backup EV charging management system, sending an acceptance message to the EV charging station indicating acceptance of use of the EV charging station.

11. The method of claim 10 , wherein an error in the identity cache of the backup EV charging management system includes the identity cache of the backup EV charging management system being unavailable or out of date.

12. A computer program comprising a program code arranged to perform the method according to claim 10 or 11, when the computer program is run on a computer.

Images