Patent Description:
Electric vehicle (EV) charging stations are typically managed by a management system, such as a charging point management system (CPMS). A CPMS can handle different operations related to EV charging. Usually CPMSs have quite a complicated technical architecture and logic. In order for the CPMS to give a valid reply to a request by an EV charging station, all the technical components may need to be functioning properly. However, no technology is perfect, and sometimes CPMS systems have technical issues. When this occurs, it is quite common for customers to not be able to charge their vehicles using the EV charging stations until issues with the CPMS have been resolved.

Publication <CIT> discloses a method for controlling a vehicle that includes: establishing, by a vehicle controller, a connection between a client and a plurality of servers, the plurality of servers includes a primary server and at least one replica server, the at least one replica server is a replica of the primary server; making, by the vehicle controller, a data request about a given service to the plurality of servers; in response to the data request, receiving reply data from the plurality of servers to the data request via a middleware; fusing, by the middleware, the reply data from the plurality of servers to generate a resulting data; receiving, by the vehicle controller, the resulting data; and controlling, by the client, the vehicle based on the resulting data.

Publication <CIT> discloses a regional electric vehicle sharing and management system that includes a system backup server connected to a system management server via an Intranet wherein both the system management server and the system backup server are configured to access the Internet via the Intranet; mobile devices, each configured to access the Internet via a telecommunications network or a wireless network; computers, each configured to access the Internet via a wired network or a wireless network; battery exchange devices, each including batteries, a charging circuit, and a power monitoring system wherein the batteries, the charging circuit, and the power monitoring system are electrically connected together, and the batteries are respectively mounted in the charging circuit; and electric vehicles, each including batteries and vehicle control systems they are electrically connected together.

Publication <CIT> discloses a method comprising connecting, by a battery analytics server, to a blockchain network that includes a plurality of charging station nodes, acquiring, by the battery analytics server, a current battery data from a charging station node of the plurality of the charging station nodes, the current battery data includes a battery identification (ID), storing, by the battery analytics server, the current battery data with a timestamp onto a blockchain ledger, comparing, by the battery analytics server, the current battery data against a pre-stored battery data based on the battery ID, and in response to a match, issuing, by the battery analytics server, a certification for a battery to be released from the charging station node of the plurality of the charging station nodes to a user.

It is an object to provide a backup electric vehicle charging management device and a corresponding method.

According to a first aspect, a backup electric vehicle, EV, charging management device comprises: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the backup EV charging management device to: when a primary EV charging management system is available, synchronize an identification cache of a backup EV charging management system with an identification cache of the primary EV charging management system, wherein the identification cache of the primary EV charging management system comprises identifications of EV charging station users that are allowed to use an EV charging station; when the primary EV charging management system is unavailable, receive a message from the EV charging station; in response to the message being a request for charging using the EV charging station, wherein the request comprises an identification of a user trying to use the EV charging station, check whether the request should be allowed by comparing the identification of the user trying to use the EV charging station to the identification cache of the backup EV charging management system; and in response to determining that the request should be allowed, transmit an acceptance message, indicating to accept the use of the EV charging station, to the EV charging station. The backup EV charging management device can, for example, enable users to charge using the EV charging station while the primary EV charging management system is unavailable.

In an implementation form of the first aspect, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the backup EV charging management device to: in response to an error with the identification cache of the backup EV charging management system, when trying to compare the identification of the user trying to use the EV charging station to the identification cache of the backup EV charging management system, transmit an acceptance message, indicating to accept the use of the EV charging station, to the EV charging station. The backup EV charging management device can, for example, enable users to charge using the EV charging station while the primary EV charging management system is unavailable and there is an error with the identification cache.

In another implementation form of the first aspect, the error with the identification cache of the backup EV charging management system comprises the identification cache of the backup EV charging management system being unavailable or being out-of-date. The backup EV charging management device can, for example, enable users to charge using the EV charging station while the primary EV charging management system is unavailable and the identification cache is unavailable or out-of-date.

In another implementation form of the first aspect, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the backup EV charging management device to in response to the message comprising a boot notification, a status notification, a meter value, and/or a heartbeat, transmit an acknowledge message to the EV charging station. The backup EV charging management device can, for example, response to less critical messages with reduced complexity and/or greater reliability when the primary EV charging management system is unavailable.

In another implementation form of the first aspect, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the backup EV charging management device to: store the message and the response transmitted by the backup EV charging management device in response to the message to a message cache; and in response to the primary EV charging management system becoming available, provide the messages and the responses from the message cache to the primary EV charging management system. The backup EV charging management device can, for example, provide the stored messages to the primary EV charging management system so that the messages can be processed appropriately.

In another implementation form of the first aspect, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the backup EV charging management device to: store, with the message and a response transmitted by the backup EV charging management device in response to the message, an identification of the EV charging station and/or a status indicating whether the message has been provided to the primary EV charging management system, to the message cache. The backup EV charging management device can, for example, keep track of which messages have been processed by the primary EV charging management system.

In another implementation form of the first aspect, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the backup EV charging management device to: receive, from the primary EV charging management system, for each message, an indication whether the message is approved or rejected by the primary EV charging management system; and compose an offloading report based at least on the received indications. The backup EV charging management device can, for example,.

In another implementation form of the first aspect, the offloading report comprises an indication of each message rejected by the primary EV charging management system and an identifier of an EV charging station from which the message was sent. The backup EV charging management device can, for example, keep track of at which EV charging stations possibly problematic charging has occurred.

In another implementation form of the first aspect, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the backup EV charging management device to provide the offloading report to an administrator. The backup EV charging management device can, for example, conveniently provide to the administrator information about at which EV charging stations possibly problematic charging has occurred.

It is to be understood that the implementation forms of the first aspect described above may be used in combination with each other. Several of the implementation forms may be combined together to form a further implementation form.

According to a second aspect, an electric vehicle, EV, charging system comprises: a primary EV charging management system; a backup EV charging management system comprising a 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 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.

According to a third aspect, a method comprises: when a primary electric vehicle, 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, wherein the identification cache of the primary EV charging management system comprises identifications of EV charging station users that are allowed to use an EV charging station; when the primary EV charging management system is unavailable, receiving a message from the EV charging station; in response to the message being a request for charging using the EV charging station, wherein the request comprises an identification of a user trying to use the EV charging station, checking whether the request should be allowed by comparing the identification of the user trying to use the EV charging station to the identification cache of the backup EV charging management system; and in response to determining that the request should be allowed, transmitting an acceptance message, indicating to accept the use of the EV charging station, to the EV charging station.

In an implementation form of the third aspect, the method further comprises, in response to an error with the identification cache of the backup EV charging management system, when trying to compare the identification of the user trying to use the EV charging station to the identification cache of the backup EV charging management system, transmitting an acceptance message, indicating to accept the use of the EV charging station, to the EV charging station.

In an implementation form of the third aspect, the error with the identification cache of the backup EV charging management system comprises the identification cache of the backup EV charging management system being unavailable or being out-of-date.

It is to be understood that the implementation forms of the third aspect described above may be used in combination with each other. Several of the implementation forms may be combined together to form a further implementation form.

According to a fourth aspect, a computer program product is provided, comprising program code configured to perform a method according to the third aspect when the computer program is executed on a computer.

Many of the attendant features will be more readily appreciated as they become better understood by reference to the following detailed description considered in connection with the accompanying drawings.

In the following, embodiments of the disclosure are described in more detail with reference to the attached figures and drawings, in which:.

In the following, like reference numerals are used to designate like parts in the accompanying drawings.

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

On the other hand, for example, if a specific apparatus is described based on functional units, a corresponding method may include a step performing the described functionality, even if such step is not explicitly described or illustrated in the figures. Further, it is understood that the features of the various example aspects described herein may be combined with each other, unless specifically noted otherwise.

<FIG> illustrates a backup electric vehicle (EV) charging management device according to an embodiment.

According to an embodiment, a backup EV charging management device <NUM> comprises at least one processor <NUM> and at least one memory <NUM> including computer program code.

According to an embodiment, the at least one memory <NUM> and the computer program code are configured to, with the at least one processor <NUM>, cause the backup EV charging management device <NUM> to, when a primary EV charging management system is available, synchronize an identification cache of a backup EV charging management system with an identification cache of the primary EV charging management system, wherein the identification cache of the primary EV charging management system comprises identifications of EV charging station users that are allowed to use an EV charging station.

Herein, the primary EV charging management system may be referred to simply as the primary system or similar, and the backup EV charging management system may be referred to simply as the backup system or similar.

The backup EV charging management device <NUM> may correspond to any device that is configured to control the backup EV charging management system. Herein, when the backup system is disclosed to perform some functionality, the backup EV charging management device <NUM> may be configured to perform, at least partially, that functionality.

Herein, an identification may comprise, for example, a so-called idTag of a user.

The backup EV charging management device <NUM> is further configured to, when the primary EV charging management system is unavailable, receive a message from the EV charging station.

The primary EV charging management system may be "unavailable" any time that the EV charging station cannot reach the primary EV charging management system. For example, a communication link between the EV charging station and the primary EV charging management system may be malfunctioning, the primary EV charging management system or some part of it may be malfunctioning, and/or the primary EV charging management system may be offline for maintenance or similar purposes.

The message may comprise, 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.

The backup EV charging management device <NUM> is further configured to, in response to the message being a request for charging using the EV charging station, wherein the request comprises an identification of a user trying to use the EV charging station, check whether the request should be allowed by comparing the identification of the user trying to use the EV charging station to the identification cache of the backup EV charging management system.

Since the identification cache of the backup system is synchronized with the identification cache of the primary system, the backup EV charging management device <NUM> can check whether the request should be allowed even when the primary system is not available. Thus, users can still use the EV charging station even when the primary system is unavailable.

The identification cache may comprise, for example, a simple whitelist of identifications that should be allowed to charge. Alternatively, the identification cache may comprise more complex information/data based on which the backup EV charging management device <NUM> can check whether the request should be allowed.

The backup EV charging management device <NUM> is further configured to, in response to determining that the request should be allowed, transmit an acceptance message, indicating to accept the use of the EV charging station, to the EV charging station.

The acceptance message may comprise any data based on which the EV charging station can recognize that the use of the EV charging station should be accepted. The content of the acceptance message can be defined, for example, in a standard/protocol, such as the open charge point protocol (OCPP).

The backup EV charging management device <NUM> may be further configured to, in response to determining that the request should not be allowed, transmit a refusal message, indicating to refuse the use of the EV charging station, to the EV charging station.

The backup EV charging management device <NUM> comprises at least one processor <NUM>. The at least one processor <NUM> may comprise, for example, one or more of various processing devices, such as a co-processor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying 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 special-purpose computer chip, or the like.

The backup EV charging management device <NUM> further comprises a memory <NUM>. The memory <NUM> may be configured to store, for example, computer programs and the like. The memory <NUM> may comprise one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices. For example, the memory <NUM> may be embodied as magnetic storage devices (such as hard disk drives, floppy disks, magnetic tapes, etc.), optical magnetic storage devices, and semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).

When the backup EV charging management device <NUM> is configured to implement some functionality, some component and/or components of the backup EV charging management device <NUM>, such as the at least one processor <NUM> and/or the memory <NUM>, may be configured to implement this functionality. Furthermore, when the at least one processor <NUM> is configured to implement some functionality, this functionality may be implemented using program code comprised, for example, in the memory <NUM>. For example, if the backup EV charging management device <NUM> is configured to perform an operation, the at least one memory <NUM> and the computer program code can be configured to, with the at least one processor <NUM>, cause the backup EV charging management device <NUM> to perform that operation.

In some embodiments, the backup EV charging management device <NUM> may be implemented as and/or as a part of a cloud computing system.

The backup system can have a simple and lightweight structure. Thus, the backup system can be more robust and fault tolerant than the primary system.

The backup system can be compatible with various different EV charging station models. Alternative solutions may be proprietary and EV charging station model-specific.

The backup system can ensure that only authorized people can charge using the EV charging stations at least in most cases. Thus, no invalid data is recorded, and no data is lost, which can enable, for example, the correct invoicing of users.

<FIG> illustrates a schematic representation of an EV charging system <NUM> according to an example.

The system <NUM> may comprise one or more EV charging stations (CS) <NUM> that are connected to a primary EV charging management system <NUM>. The system <NUM> may further comprise a load balancer <NUM>. The load balancer <NUM> may forward messages from the one or more EV charging stations <NUM> to the primary EV charging management system <NUM> when the primary EV charging management system <NUM> is available. The load balancer <NUM> may also forward messages from the primary EV charging management system <NUM> to the one or more EV charging stations <NUM> when the primary EV charging management system <NUM> is available. The load balancer <NUM> may, for example, implement an application programming interface (API) using which the one or more EV charging stations <NUM> can communicate with the primary system <NUM>.

The primary EV charging management system <NUM> may comprise, for example, a charging point management system (CPMS). The primary system <NUM> can handle different operations related to EV charging. The one or more EV charging stations <NUM> and the primary system <NUM> can communicate using, for example, the OCPP.

Herein, any messages transmitted and/or received by any system/device/component may comprise an OCPP message.

For example, when a user wishes to start charging using an EV charging station <NUM>, the user can present a radio-frequency identification (RFID) card to the EV charging station <NUM>. The station <NUM> can asks from the primary system <NUM>, using for example the OCPP protocol, if the RFID is valid. The primary system <NUM> can process this request and respond back to the EV charging station <NUM> whether charging with the RFID can be allowed or not.

The primary system <NUM> can have quite a complicated technical architecture and logic. A modern CPMS can comprise tens or hundreds of different services, components, data storages, complex business logic, integrations to third party systems etc. For example, in the example of <FIG>, the primary system <NUM> comprises various interconnected services and components <NUM>, data storages <NUM>, and integration to third parties <NUM>. In order for the primary system <NUM> to give a valid reply, such as accepting or rejecting a charging request from an EV charging station <NUM>, all the technical components should be functioning correctly.

Thus, the primary system <NUM> can have technical issues. When this occurs, it is quite common for a user to not be able to charge using the EV charging station <NUM> until the issues with the primary system <NUM> have been resolved.

<FIG> illustrates a schematic representation of an EV charging system <NUM> according to an embodiment.

According to an embodiment, an EV charging system <NUM> comprises a primary EV charging management system <NUM>, a backup EV charging management system <NUM> comprising a backup EV charging management device <NUM>, at least one EV charging station <NUM>, and a load balancer <NUM> configured to forward messages from the at least one EV charging station <NUM> to the primary EV charging management system <NUM> when the primary EV charging management system <NUM> is available and forward messages from the at least one EV charging station <NUM> to the backup EV charging management system <NUM> when the primary EV charging management system <NUM> is unavailable.

The backup system <NUM> can function as a lightweight, simple backup system that lacks all the complex business logic, integrations, data storages etc. of the primary system <NUM>. Thus, the backup system <NUM> can be more fault tolerant and low cost.

The backup system <NUM> can have the capability to process critical OCPP messages, such as heartbeats, boot notifications, authentication, start- and stop-messages, even when the primary system <NUM> is offline.

In the case of major problems with the primary system <NUM>, all OCPP traffic from EV charging stations <NUM> can be directed to the backup system <NUM> by, for example, the load balancer <NUM>. The backup system <NUM> can then, for example, process few key OCPP messages from the EV charging stations <NUM>, transmit replies back to the EV charging stations <NUM> based on limited simple logic, and allowing users to still charge using the EV charging stations <NUM>. The backup system <NUM> may also store some or all OCPP messages to a local message cache <NUM> so that once the primary system <NUM> is available again, these messages can be processed by the primary system <NUM> to ensure that no data is lost during the downtime of the primary system <NUM>.

Any devices/systems/components/modules disclosed herein may communicate with each other using, for example, a data connection. The data connection may be any connection that enables devices/systems/components/modules to communicate with each other. The data connection may comprise, for example, internet, Ethernet, <NUM>, <NUM>, <NUM>, long-term evolution (LTE), new radio (NR), Wi-Fi, or any other wired or wireless connections or some combination of these. For example, the data connection may comprise a wireless connection, such as Wi-Fi, an internet connection, and an Ethernet connection.

<FIG> illustrates a schematic representation of functionality of the EV charging system when the primary system is available according to an embodiment.

In normal situations, when the primary system <NUM> is available, all traffic from the EV charging stations <NUM> can be directed to the primary system <NUM>. The primary system <NUM> can then handle traffic in a normal fashion, following the normal logic of the primary system <NUM>.

The backup system <NUM> can be idle in the normal situation.

<FIG> illustrates a schematic representation of functionality of the EV charging system when the primary system is unavailable according to an embodiment.

When the primary system <NUM> is unavailable due to, for example, technical issues, traffic from the EV charging stations <NUM> can be directed to the backup system <NUM>. This can be done manually or automatically based on, for example, health checks of the primary system <NUM>.

When the traffic is directed to the backup system <NUM>, the backup system <NUM> can function in the following fashion in a so-called "simple mode".

According to an embodiment, the backup EV charging management device <NUM> is configured to in response to the message comprising a boot notification, a status notification, a meter value, and/or a heartbeat, transmit an acknowledge message to the EV charging station.

The backup system <NUM> can be configured with static response messages for key OCPP messages. For example, in response to BootNotification-, StatusNotification-, Metervalues-, and Heartbeat- messages the backup system <NUM> can simply reply with an acknowledgement message, as defined, for example, in the OCPP protocol.

When in the simple mode, for Authorize, StartTransaction and StopTransaction messages, the backup system <NUM> can always give a static "Accepted" reply, regardless of the idTag which is used to start or stop charging.

In addition to giving standard responses, the backup system <NUM> can store all request- and reply-messages as they were sent and received to a message cache <NUM>.

<FIG> illustrates a schematic representation of functionality of the EV charging system when the primary system is again available after being unavailable according to an embodiment.

According to an embodiment, the backup EV charging management device <NUM> is further configured to store the message and the response transmitted by the backup EV charging management device <NUM> in response to the message to a message cache <NUM>, and in response to the primary EV charging management system <NUM> becoming available, provide the messages and the responses from the message cache <NUM> to the primary EV charging management system <NUM>.

After the issues with the primary system <NUM> are resolved, and the primary system <NUM> is available again, the traffic can be switched back to the primary system <NUM>.

Once the primary system <NUM> is available, the backup system <NUM> can provide the new messages, stored in the message cache <NUM>, to the primary system <NUM>. This may be referred to as message offloading. The primary system <NUM> can then processes the messages. This may be needed so that, for example, correct charge detail records are created to the primary system <NUM>, so that, for example, users are invoiced correctly.

Backup system <NUM> can read all unprocessed messages from the message cache <NUM>. The messages can comprise, for example, BootNotification, StatusNotification, Authorize, StartTransaction, and/or StopTransaction messages.

Backup system <NUM> can provide each message to the primary system <NUM> via, for example, an API. The primary system <NUM> can then process the messages normally and handle the normal logic, such as creating charge detail records.

It is possible that primary system <NUM> rejects some messages, such as Authorize-messages that had an invalid user identification, such as an idTag. For this reason, the backup system <NUM> can keep track of which messages are processed, approved or rejected. Backup system <NUM> can then create a report of successful or problematic charging during the time period when the primary system <NUM> was unavailable.

<FIG> illustrates a schematic representation of functionality of the EV charging system when the primary system is available, and the backup system is in advanced mode according to an embodiment.

Similarly to the embodiment of <FIG>, in normal situations, when the primary system <NUM> is available, all traffic from the EV charging stations <NUM> can be directed to the primary system <NUM>. The primary system <NUM> can then handle traffic in a normal fashion, following the normal logic of the primary system <NUM>.

When in a so-called "advanced mode", the backup system <NUM> can, when a primary system <NUM> is available, synchronize an identification cache <NUM> of a backup system <NUM> with an identification cache of the primary system <NUM>. The identification cache of the primary system <NUM> may be embodied in, for example, any of the data storages <NUM> of the primary system <NUM>.

The identification cache of the primary system <NUM> can comprise identifications of EV charging station users that are allowed to use an EV charging station <NUM>. For example, when a new user registers to the system, a new RFID can be created and linked to an account of the customer.

In the advanced mode, all user identification, such as idTag, changes done in the primary system <NUM> can be mirrored to the backup system <NUM>. As a result, the backup system <NUM> can have a valid copy of all user identifications at all times.

<FIG> illustrates a schematic representation of functionality of the EV charging system when the primary system is unavailable, and the backup system is in advanced mode according to an embodiment.

In an error situation, when the primary system <NUM> is not available, the traffic can be switched to the backup system <NUM> as in the simple mode. The messages can be processed in a similar fashion as in the simple mode with the following exceptions.

In the case of Authorize- and/or StopTransaction-messages, instead of always replying "Accepted", the backup system <NUM> can check from the identification cache <NUM> whether the identification in the message is valid. If yes, the backup system <NUM> can reply "Accepted" to the EV charging station <NUM>, but if the idTag is not found to be valid, the backup system <NUM> can reply "Rejected" to the message.

One benefit of the advanced mode is that only the users with a valid identification can charge using the EV charging station <NUM>. Thus, a user cannot use a random RFID token to start charging.

According to the invention, the backup EV charging management device <NUM> is further configured to, in response to an error with the identification cache <NUM> of the backup EV charging management system <NUM>, when trying to compare the identification of the user trying to use the EV charging station to the identification cache <NUM> of the backup EV charging management system <NUM>, transmit an acceptance message, indicating to accept the use of the EV charging station <NUM>, to the EV charging station.

According to the invention, the error with the identification cache <NUM> of the backup EV charging management system <NUM> comprises the identification cache <NUM> of the backup EV charging management system <NUM> being unavailable or being out-of-date.

The identification cache <NUM> may be out-of-date, for example, when the identification cache has not been updated recently, and therefore the information content of the identification cache <NUM> may be out-of-date. For example, the backup EV charging management device <NUM> may be further configured to check whether the identification cache <NUM> has been updated within a preconfigured time period. If the identification cache <NUM> has not been updated within the preconfigured time period, the backup EV charging management device <NUM> can deem the identification cache <NUM> to be out-of-date. Alternatively or additionally, the out-of-date status of the identification cache <NUM> may be identified using some other procedure.

By default, the backup system <NUM> can be in the advanced mode so that it will be possible to authenticate users trying to charge, and to ensure that only valid users can use the EV charging stations <NUM>.

In the simple mode, where the backup system <NUM> can accept all messages, anybody can in theory charge for free using, for example, any RFID token they may have.

However, the advanced mode can be more prone to errors than the simple mode. There is a need to synchronize data between the primary and backup systems, additional logic etc. which can fail. The simple mode can, however, be robust and basically fool-proof.

When traffic is directed to the backup system <NUM>, the backup system <NUM> can always start in the advanced mode first. However, if there are any technical issues, such as the identification cache <NUM> is not working, not being up-to-date etc., the backup system <NUM> can be switched to the simple mode in order to ensure that users can use the EV charging stations <NUM>.

<FIG> illustrates a schematic representation of a message cache according to an embodiment.

According to an embodiment, the backup EV charging management device <NUM> is further configured to store, with the message and a response transmitted by the backup EV charging management device <NUM> in response to the message, an identification of the EV charging station and/or a status indicating whether the message has been provided to the primary EV charging management system, to the message cache <NUM>.

The message cache <NUM> can store at least some of the following information for each message stored in the message cache <NUM>: individual identifier <NUM> of the EV charging station that sent the message, a raw OCPP message <NUM>: contents of the request- and/or reply-message sent to and/or received from the EV charging station, status <NUM>: indicates whether the message is new, or whether has already been offloaded to the primary system <NUM>, primary system response <NUM>: indicates response of the primary system <NUM> to the message - for example the primary system <NUM> may reject an Authorize-message or StartTransaction-message if the idTag in the message is invalid.

The backup system <NUM> may transmit the raw message <NUM> to the primary system <NUM> once the primary system <NUM> is again available.

Once the primary system <NUM> is again available, the backup system <NUM> can start to offload messages from the message cache <NUM> to the primary system <NUM>.

For example, the backup system <NUM> can provide all messages with a status "New" to the primary system <NUM>. The components of the backup system <NUM> transmitting the messages can wait for a reply from the primary system <NUM> for each message. After receiving a reply, the backup system <NUM> can update the status <NUM> to "Uploaded to primary system" and update the primary system response <NUM> to "accepted" or "rejected".

<FIG> illustrates a schematic representation of an offloading report according to an embodiment.

According to an embodiment, the backup EV management device <NUM> is further configured to receive, from the primary EV charging management system, for each message, an indication whether the message is approved or rejected by the primary EV charging management system <NUM>, and compose an offloading report based at least on the received indications.

According to an embodiment, the offloading report comprises an indication of each message rejected by the primary EV charging management system <NUM> and an identifier of an EV charging station from which the message was sent.

After the messages are offloaded from the backup system <NUM> to the primary system <NUM>, the backup system <NUM> can create an offloading report <NUM>.

The offloading report <NUM> can conveniently report if any information was lost, for example if the system was unable to create critical charge detail records.

The offloading report <NUM> can comprise at least some of the following information: Number of processed Authorize, StartTransaction and StopTransaction messages, how many of those messages where Accepted or Rejected by the primary system <NUM>, for the rejected messages, list of station identifiers and number of rejected messages (in other words missing charge detail records).

According to an embodiment, the backup EV charging management device <NUM> is further configured to provide the offloading report <NUM> to an administrator.

After the report <NUM> is ready, the backup system <NUM> can transmit/provide the report to an administrator of the primary system <NUM>. The administrator can verify that all data is processed, and to check for possible errors, such as rejected messages, manually.

<FIG> illustrates a schematic representation of a method <NUM> according to an embodiment.

According to the invention, the method <NUM> comprises, when a primary EV charging management system is available, synchronizing <NUM> an identification cache of a backup EV charging management system with an identification cache of the primary EV charging management system, wherein the identification cache of the primary EV charging management system comprises identifications of EV charging station users that are allowed to use an EV charging station.

The method <NUM> further comprises, when the primary EV charging management system is unavailable, receiving <NUM> a message from the EV charging station.

The method <NUM> further comprises, in response to the message being a request for charging using the EV charging station, wherein the request comprises an identification of a user trying to use the EV charging station, checking <NUM> whether the request should be allowed by comparing the identification of the user trying to use the EV charging station to the identification cache of the backup EV charging management system.

The method <NUM> further comprises, in response to determining that the request should be allowed, transmitting <NUM> an acceptance message, indicating to accept the use of the EV charging station, to the EV charging station.

The method <NUM> may be performed by the backup EV charging management device <NUM> of <FIG>. Further features of the method <NUM> directly result from the functionalities and parameters of the backup EV charging management device <NUM>. The method <NUM> can be performed, at least partially, by computer program(s).

An apparatus may comprise means for performing any aspect of the method(s) described herein. According to an embodiment, the means comprises at least one processor, and memory comprising program code, the at least one processor, and program code configured to, when executed by the at least one processor, cause performance of any aspect of the method.

Also any embodiment may be combined with another embodiment unless explicitly disallowed.

Rather, the specific features and acts described above are disclosed as examples of implementing the claims.

The steps of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate. Additionally, individual blocks may be deleted from any of the methods without departing from the spirit and 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 effect sought.

Claim 1:
A backup electric vehicle, EV, charging management device (<NUM>), comprising:
at least one processor (<NUM>); and
at least one memory (<NUM>) including computer program code;
the at least one memory (<NUM>) and the computer program code configured to, with the at least one processor (<NUM>), cause the backup EV charging management device (<NUM>) to:
when a primary EV charging management system (<NUM>) is available, synchronize an identification cache (<NUM>) of a backup EV charging management system (<NUM>) with an identification cache of the primary EV charging management system (<NUM>);
when the primary EV charging management system (<NUM>) is unavailable, receive a message from an EV charging station (<NUM>) that is connected to the primary EV charging management system (<NUM>) and to the backup EV charging management system (<NUM>);
characterised in that the identification cache of the primary EV charging management system comprises identifications of EV charging station users that are allowed to use the EV charging station (<NUM>) and in that the at least one memory (<NUM>) and the computer program code are further configured to, with the at least one processor (<NUM>), cause the backup EV charging management device (<NUM>) to:
in response to the message being a request for charging using the EV charging station (<NUM>), wherein the request comprises an identification of a user trying to use the EV charging station, check whether the request should be allowed by comparing the identification of the user trying to use the EV charging station to the identification cache of the backup EV charging management system;
in response to determining that the request should be allowed, transmit an acceptance message, indicating to accept the use of the EV charging station, to the EV charging station; and
in response to an error with the identification cache (<NUM>) of the backup EV charging management system, when trying to compare the identification of the user trying to use the EV charging station to the identification cache of the backup EV charging management system, transmit an acceptance message, indicating to accept the use of the EV charging station, to the EV charging station, wherein the error with the identification cache (<NUM>) of the backup EV charging management system comprises the identification cache (<NUM>) of the backup EV charging management system (<NUM>) being unavailable or being out-of-date.