A method and an apparatus to manage electric vehicle charging station identifier

Abstract

An example embodiment provides an apparatus for managing changed identifiers of charging stations. The apparatus is configured to at least obtain at least one routing rule, wherein a first charging station identifier is linked to a second charging station identifier; receive a message for a charging station management system sent by a charging station with the first charging station identifier; detect there is a routing rule for the first charging station identifier; replace the first charging station identifier associated with the message with the second charging station identifier based on the routing rule; and forward the message to be processed by the charging station management system with the second charging station identifier. Apparatuses and methods are disclosed.

Description

[0001] A METHOD AND AN APPARATUS TO MANAGE ELECTRIC VEHICLE CHARGING STATION IDENTIFIER

[0002] TECHNICAL FIELD

[0003] The present application generally relates to electric vehicle charging stations . In particular, some example embodiments of the present application relate to management of electric vehicle charging stations when an electric vehicle charging station or a component of an electric vehicle charging station gets replaced by a new one .

[0004] BACKGROUND

[0005] Electric vehicle charging stations , or charging stations for short , may have faults for different reasons from time to time . The fault may cause the charging station to stop working, or the charging station may not work properly . When a charging station, or a component therein, breaks , the charging station or the component may need to be replaced with a new one . However, the new charging station may comprise different settings than the old one which may complicate usage of the charging station . Hence , it would be beneficial to alleviate at least some of these drawbacks .

[0006] SUMMARY

[0007] 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 subj ect matter, nor is it intended to be used to limit the scope of the claimed subj ect matter .

[0008] Example embodiments may enable more efficient and reasoned management of electric vehicle charging station identifiers . The proposed method is particularly useful for managing electric vehicle charging station identifier in an identifier router .

[0009] According to a first aspect , an apparatus for charging station identifier management is provided . The apparatus comprises at least one processor ; and at least one memory comprising instructions which, when executed by the at least one processor, cause the apparatus at least to obtain at least one routing rule , wherein a first charging station identifier is linked to a second charging station identifier ; receive a message for a charging station management system sent by a charging station with the first charging station identifier ; detect there is a routing rule for the first charging station identifier ; replace the first charging station identifier associated with the message with the second charging station identifier based on the routing rule ; and forward the message to be processed by the charging station management system with the second charging station identifier . An identifier comprised in the message may be changed to an original identifier of the charging station based on which original identifier relevant data is stored at the charging station management system . Hence , no changes may be required at the charging station or to stored charging station data at the charging station management system to enable control of the charging station in despite of the changed identifier .

[0010] In an embodiment , the at least one memory further comprises instructions which, when executed by the at least one processor, cause the apparatus to receive a message for a charging station with the second charging station identifier ; detect there is a routing rule for the second charging station identifier ; replace the second charging station identifier associated with the message with the first charging station identifier based on the routing rule ; and forward the message to the charging station with the first charging station identifier .

[0011] In an embodiment , in addition or alternatively, the apparatus i s coupled between at least one charging station and the charging station management system; and wherein the at least one memory comprises instruction which, when executed by the at least one processor, cause the apparatus to detect a connection is established with the charging station with the first charging station identifier ; establish a connection with the charging station management system with the second charging station identifier based on the routing rule after detecting the connection with the charging station ; and wherein the message for the charging station management system is forwarded through the connection established with the second charging station identifier .

[0012] In an embodiment , in addition or alternatively, the memory comprises instructions which, when executed by the at least one processor, cause the apparatus to receive the message for the charging station via the connection established with the second charging station identifier ; and forward the message to the charging station through the connection established with the first charging station identifier .

[0013] In an embodiment , in addition or alternatively, the apparatus comprises the charging station management system; and wherein the charging station management system is configured to connect with at least one charging station for message exchange and execute the at least one routing rule for messages exchanged through the connection .

[0014] In an embodiment , in addition or alternatively, the at least one memory comprises instructions which, when executed by the at least one processor, cause the apparatus to receive a message for the charging station management system sent by a charging station with the second charging station identifier ; detect that messages sent for the charging station management system with the second charging station identifier are configured to be routed with a third charging station identifier ; and forward the message to be processed by the charging station management system with the third charging station identifier .

[0015] In an embodiment , in addition or alternatively, the at least one memory comprises instructions which, when executed by the at least one processor, cause the apparatus to detect that there is no routing rule for an identifier associated with a received message , and forward the message without changes .

[0016] In an embodiment , in addition or alternatively, the at least one memory comprise instructions which, when executed by the at least one processor, cause the apparatus to provide a user interface for setting the at least one routing rule ; and obtain the at least one routing rule from a user via the user interface .

[0017] According to a second aspect , a method carried out by a computing device is provided . The method comprises obtaining at least one routing rule , wherein a first charging station identi fier is linked to a second charging station identifier ; receiving a message for a charging station management system sent by a charging station with the first charging station identifier ; detecting there is a routing rule for the first charging station identifier ; replacing the first charging station identifier associated with the message with the second charging station identifier based on the routing rule ; and forwarding the message to be processed by the charging station management system with the second charging station identifier .

[0018] In an embodiment, the method further comprises receiving a message for a charging station with the second charging station identifier ; detecting there is a routing rule for the second charging station identifier ; replacing the second charging station identifier associated with the message with the first charging station identifier based on the routing rule ; and forwarding the message to the charging station with the first charging station identifier .

[0019] In an embodiment , in addition or alternatively, the method comprises receiving a message for the charging station management system sent by a charging station with the second charging station identifier ; detecting that messages sent for the charging station management system with the second charging station identifier are configured to be routed with a third charging station identifier ; and forwarding the message to be processed by the charging station management system with the third charging station identifier .

[0020] In an embodiment , in addition or alternatively, the method comprises detecting a connection is established with the charging station with the first charging station identifier ; caus ing a connection to be established with the charging station management system with the second charging station identifier based on the routing rule after detecting the connection with the charging station ; and wherein the message for the charging station management system is caused to be forwarded through the connection established with the second charging station identifier .

[0021] In an embodiment , in addition or alternatively, the method comprises receiving the message for the charging station via the connection established with the second charging station identifier ; and causing the message to the charging station to be forwarded through the connection established with the first charging station identifier .

[0022] According to a third aspect , there is provided a computer program product comprising instructions which, when executed by a computer, cause the computer to carry out the method of the second aspect .

[0023] According to a fourth aspect , there is provided a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the method of the second aspect .

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

[0025] BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings , which are included to provide a further understanding of the example embodiments and constitute a part of this specification, illustrate example embodiments and together with the description help to explain the principles of the example embodiments . In the drawings :

[0027] FIG. 1 illustrates an example of an apparatus configured to practice one or more example embodiments ;

[0028] FIG. 2 illustrates an example of managing electric vehicle charging station identifiers with an apparatus according to an example embodiment ;

[0029] FIG. 3 illustrates an example of a graphical user interface for managing electric vehicle charging station identifiers according to an example embodiment ;

[0030] FIG. 4 illustrates an example of managing electric vehicle charging station identifiers with an apparatus comprising a routing logic for identifiers according to an example embodiment ;

[0031] FIG. 5 illustrates an example of managing electric vehicle charging station identifiers with an apparatus comprising a routing logic for identifiers and a charging station management system according to an example embodiment ; FIG . 6 illustrates an example of a flow chart of a data model for managing electric vehicle charging station identifiers according to an example embodiment ;

[0032] FIG . 7 illustrates an example of a flow chart of a routing algorithm in an apparatus according to an example embodiment ;

[0033] FIG . 8 illustrates an example of a flow chart of another implementation of a routing algorithm in an apparatus according to an example embodiment ;

[0034] FIG . 9. illustrates an example of a flow chart of a routing algorithm in an apparatus when a message is received from a charging station management system according to an example embodiment ; and

[0035] FIG . 10 illustrates an example of a method for managing electric vehicle charging station identifiers according to an example embodiment .

[0036] Like references may be used to designate like parts in the accompanying drawings .

[0037] DETAILED DESCRIPTION

[0038] Reference will now be made in detail to example embodiments , examples of which are illustrated in the accompanying drawings . The detailed description provided below in connection with the appended drawings is intended as a description of the present examples and is not intended to represent the only forms in which the present examples may be constructed or utili zed . The description sets forth the functions of the example and a possible sequence of operations for constructing and operating the example . However, the same or equivalent functions and sequences may be accomplished by different examples .

[0039] Electric vehicle charging stations (CS ) are used to charge electric vehicles (EV) . In this disclosure , the electric vehicle charging stations can be called charging stations or EVC stations . The charging stations may be connected to a Charging Station Management System (CSMS ) , for example , with OCPP protocol (Open Charge Point Protocol ) . A CSMS may refer to an apparatus configured to manage one or more operations of the charging stations . The CSMS may be an entity responsible for maintaining registries of one or more charging stations . The CSMS may comprise , for example , one or more servers . The CSMS may be configured to communicate with the charging stations , in order to view and manage status and data of the charging stations . OCPP messages may be related to communication between a charging station and a CSMS . EV drivers use electric vehicles (EV) and charge their EVs at charging stations .

[0040] Each charging station may have a unique identifier . An identifier may be also referred to as an identity . The identifier may take any configured form . For example , an identif ier may comprise a prefix and a running number, for example "AA_001" . When a charging station connects to a CSMS , it may open a websocket connection which includes the identi fier at the end of the connection URL, for example "wss : / / csms . example . com / ocpp / AA_001" . The CSMS may be configured to recogni ze which charging station it is communicating with based on the identifier in the URL or in a message received from the charging station . Websocket refers to a computer communications protocol , providing full-duplex communication channels over a single TCP connection . Websocket may enable real-time , bidirectional communication between clients and servers , for example .

[0041] CSMS systems may store various data linked to a charging station . The linked data may be identified by the identifier of the charging station . The data may comprise , for example , Point-of- Interest ( POT ) data such as address , Global Positioning System (GPS ) coordinates , photos , and the like . As an example of the POT data, the CSMS system could keep track that the charging station "AA_001" is located at coordinates " 60 . 16545910678517 , 24 . 9019667367794" . A CSMS may al so keep track of other features defined by the identifier of charging station, such as charging transactions , access rights and audit trails . Access rights may refer to data indicating which EV drivers are allowed to charge on which charging stations . Audit trails may refer to data indicating which events have been happening on which charging stations . The identifier of a charging station may be key information that is linked to various data in the CSMS .

[0042] Charging stations are physical devices . The charging stations may comprise a plurality of electrical components . The electrical components may comprise , for example , a socket configured for charging an EV and an energy meter configured for monitoring charging transactions at the EV charging station . One of main components of a charging station is a controller . The identifier of the charging station may be configured to the controller . A casing of the charging station may also have a sticker with the same identity printed on it . With the sticker, EV drivers can identify correct charging stations , for example, when they want to start charging using a mobile application .

[0043] I f the controller or some other component of the charging station breaks , the broken component may need to be replaced . It might be possible to replace only the broken component , but it is more common to replace the whole broken charging station ( including the controller) with a new working charging station .

[0044] When a controller ( or the whole charging station) gets replaced, the new controller may have a new identifier configured for a charging station . This creates problems when configurations the old ( replaced) charging station are stored at a CSMS with the old identifier . The old charging station may have also had some POI data set stored by the CSMS . The old and the new charging stations may be physically different charging stations . Alternatively, the old and the new charging stations may refer to the same charging station with different controllers ( and consequently, with different identifiers for the charging station) . For example , the casing may not be replaced, and none of the other components such as contactors , energy meter, sockets , etc . Physically everything may be the same as before , and j ust the controller inside the charging station is new .

[0045] For example , after replacement of the controller, the CSMS may get a connection from a charging station AA_052 . The identifier AA_052 may be different than an identifier AA_001 stored on the replaced controller . Hence , from perspective of the CSMS , the charging station with the identifier AA_052 is a totally new charging station, and the charging station may not have any POI data, charging transaction history, any settings , etc . , stored at the CSMS . As far as the CSMS is concerned, the charging station AA_052 is a blank new charging station, even though only one component , the controller, is being replaced . However, when looking at a physical appearance of the charging station, nothing may have changed . The charging station may look exactly the same as before , with the sticker AA_001 on it . As a result , the CSMS may not recogni ze the charging station , and the charging station may not be used .

[0046] An obj ective is to provide a method for managing charging station identifiers . The method may enable usage of a charging station with a replaced controller, and therefore changed identifier, by routing messages from the charging station with automatically changed identifiers . Charging station identifiers of messages exchanged between charging stations and a charging station management system may be changed on the fly such that the charging station management server is able to process the messages with an old charging station identifier when the identifier of the charging station has changed after maintenance . Hence , a replacement process of charging stations or components of charging stations may be made more convenient . Maintaining and fixing charging may become easier and faster since identifier changes can easily be managed in one place with an entity configured to perform the routing service . The replacement process of a controller may be simplified as no special skills are required from an installer . For example , the installer does not need to change the identifier stored at the controller manually . Further, a correct functioning of the charging station may be enabled also in case the identifier is hard coded to the control ler and may not be changed .

[0047] In addition, messages received from a charging station with an identifier configured at the replaced controller may be configured to be routed with a changed identifier . For example , if the old controller / charging station was fixed and reinstalled at another location later, messages from two charging stations with the same identifier will not be routed to the CSMS . Hence , proper functioning of a network of charging stations may be ensured after the replacement .

[0048] FIG . 1 illustrates an example of an apparatus 100 configured to practice one or more example embodiments .

[0049] The apparatus 100 may comprise at least one processor 102 . The at least one processor 102 may comprise , for example , one or more of various processing devices , such as for example 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 (AS IC) , a field programmable gate array ( FPGA) , a microcontroller unit (MCU) , a hardware accelerator, a special-purpose computer chip, or the like .

[0050] The apparatus 100 may further comprise at least one memory 104 . The memory may be configured to store , for example, computer program code 106 or the like , for example operating system software and application software . The memory 104 may comprise one or more volatile memory devices , one or more non-volatile memory devices , and / or a combination thereof . For example , the memory may be embodied as magnetic storage devices ( such as hard disk drives , magnetic tapes , etc . ) , optical magnetic storage devices , or semiconductor memories ( such as mask ROM, PROM (programmable ROM) , EPROM (erasable PROM) , flash ROM, RAM ( random access memory) , etc . ) .

[0051] The apparatus 100 may further comprise communication interface 108 configured to enable apparatus 200 to transmit and / or receive information, to / from other apparatuses , such as the charging stations . The communication interface may be configured to provide at least one wireless radio connection, such as for example a 3GPP mobile broadband connection (e . g . 3G, 4G, 5G) . However, the communication interface may be configured to provide one or more other type of connections , for example a wireless local area network (WLAN) connection such as for example standardi zed by IEEE 802 . 11 series or Wi-Fi alliance ; a short range wireless network connection such as for example a Bluetooth, NFC (near-field communication) , or RFID connection ; a wired connection such as for example a local area network (LAN) connection, a universal serial bus (USB) connection or an optical network connection, or the like ; or a wired Internet connection . Communication interface 108 may comprise , or be configured to be coupled to, at least one antenna to transmit and / or receive radio frequency signals . One or more of the various types of connections may be also implemented as separate communication interfaces , which may be coupled or configured to be coupled to a plurality of antennas .

[0052] When the apparatus 100 is configured to implement some functionality, some component and / or components of the apparatus 100 , such as for example the at least one processor 102 and / or the memory 104 , may be configured to implement this functionality . Furthermore , when the at least one processor 102 is configured to implement some functionality, this functionality may be implemented using program code 106 comprised, for example , in the memory 104 .

[0053] The apparatus 100 may comprise for example a computing device such as for example a server device , a client device , a routing device , or the l ike . Although the apparatus 100 is il lustrated as a single device it is appreciated that , wherever applicable , functions of the apparatus 100 may be distributed to a plurality of devices .

[0054] In an embodiment , the apparatus 100 may comprise a device configured to forward received messages after processing an identifier of the message according to stored routing instructions . The apparatus 100 may comprise , for example , a server configured with a routing logic for one or more identifiers . The server may be referred to as an identifier router . The apparatus 100 may be configured to forward messages between charging stations and a charging station management server, such as a CSMS . Before the message is forwarded, the apparatus 100 may be configured to change an identifier associated with the message . For example, the apparatus 100 may be configured to receive a message with a source identifier, and forward the message with a target identifier, or vice versa . The identif ier may be at least one of an identifier of the charging station or an identifier of a charging station controller . The identifier associated with the message may be used by the CSMS for managing a charging station and for determining configurations of the charging station . Once the identifier is changed by the apparatus 100 , the CSMS is able to manage the charging station configured with the source identifier with data stored under another charging station identifier . The CSMS may be further configured to store the configurations . The apparatus 100 may be an independent server coupled between the charging station ( s ) and the CSMS . The apparatus 100 may be configured to detect when a connection is established with a charging station with the source identifier, and establish a connection with the CSMS with the target identifier . The apparatus 100 may be then forward messages received with the connection established with the source identifier via the connection established with the target identifier such that the CSMS sees that the message is received from a charging station with the target identifier .

[0055] Alternatively, the routing instructions may be implemented inside the CSMS . In an embodiment , the apparatus 100 may comprise the CSMS . Hence , a charging station may establish a connection directly with the CSMS with a source identifier . The source identifier may be translated internally to the target identifier for messages received via the connection . The CSMS may then process a message received with the source identifier according to the target identif ier . For example , the CSMS may search configurations of the charging station (having the source identifier) based on the target identifier . The CSMS may respond to the charging station with the target identifier . Before the CSMS forwards the response to the charging station via the connection established with the source identifier, the CSMS is configured to change the target identifier to the source identifier based on the routing instructions . The apparatus 100 may be configured with different routing rules for different source and target identifiers . In addition, there may be configured more than one routing rule for a target identifier, depending on from which entity a message with the target identifier is received from . For example , messages with the target identifier coming from a charging station may be routed with a second target identifier, and messages with the target identifier coming from the CSMS may be routed with the source identifier . Hence , it may be avoided that the CSMS manages two charging stations based on the same identifier .

[0056] The apparatus 100 may further comprise a user interface 110 comprising an input device and / or an output device . The user interface 110 may be configured to provide means for receiving the routing instructions from a user .

[0057] The functionality described herein may be performed, at least in part , by one or more computer program product components such as software components . According to an embodiment , the apparatus comprises a processor or processor circuitry, such as for example a microcontroller, configured by the program code when executed to execute the embodiments of the operations and functionality described . Alternatively, or in addition, the functionality described herein can be performed, at least in part , by one or more hardware logic components . For example , and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays ( FPGAs ) , application-specific Integrated Circuits (AS ICs ) , application-specific Standard Products (ASSPs ) , System- on-a-chip systems ( SOCs ) , Complex Programmable Logic Devices (CPLDs ) , Graphics Processing Units (GPUs ) .

[0058] The apparatus 100 comprises means for performing at least one method described herein . In one example , the means comprises the at least one processor 102 , the at least one memory 104 including program code 106 configured to , when executed by the at least one processor 102 , cause the apparatus 100 to perform the method .

[0059] FIG . 2 illustrates an example of managing electric vehicle charging station identifiers with an apparatus , such as the apparatus 100 .

[0060] The apparatus 100 may comprise or be communicatively couple to a CSMS 202 . The CSMS 202 may be configured to manage a network of charging stations . The network may comprise , for example , one or more groups of EV charging stations . A group may comprise at least one charging station, such as a charging station 200 . The CSMS 202 may be communicatively coupled with each charging station of the network, including the charging station 200 . The apparatus 100 may be wirelessly coupled with the charging stations and / or the CSMS 202 . The CSMS 202 may be configured to perform operations via a cloud .

[0061] The charging station 200 may comprise a first controller . The first controller may be configured with an identifier for the charging station 200 . An identifier may def ine one or more configurations for a charging station . The one or more configurations may be stored at the CSMS 202 , together with the identifier . The CSMS 202 may be further configured to store PCI data associated with the charging station 200 . The PCI data may comprise , for example , at least one of an address or geographical coordinates of the charging station 200 . The CSMS 202 may store configurations and other data of a plurality of charging stations having different identifiers .

[0062] I f the first controller of the charging station 200 gets broken, it may be replaced with a second controller . The first controller may be also referred to as an old controller, and the second controller may be referred to as a new controller ( replacing the old controller) .

[0063] The first controller and the second controller may be configured with different identifiers ( identities ) for the charging station 200 . An identifier of the first controller may be , for example , "AA_001" . The identif ier of the f irst controller may be referred to as target identifier . An identifier of the second controller may be , for example , "AA_052" . The identifier of the second controller may be referred to as source identifier . The source identifier may be linked with one or more configurations at the CSMS 202 , which may be different from the configurations of the first controller and the target identifier . Alternatively, the CSMS 202 may not have any data stored for the source identifier . In any case , because the CSMS 202 may have correct configurations of the charging station 200 stored with the target identifier, the CSMS 202 may not be able to manage operations of the charging station 200 correctly based on messages received from the charging station 200 with the second controller and the new identifier .

[0064] In an example embodiment , the apparatus 100 may be configured to update an identifier of a charging station associated with messages sent between the charging station and a CSMS . The apparatus 100 may obtain one or more routing rules for identifiers and update identifiers based on the one or more routing rules . The routing rules may be obtained from an operator . The apparatus 100 may be configured to provide a user interface for the operator to set the routing rule ( s ) .

[0065] The apparatus 100 may be configured between one or more charging stations and the CSMS . The apparatus 100 may be configured to communicate with the charging stations and the CSMS . When a charging station opens a connection with a source identifier to the apparatus 100 , the apparatus 100 may be configured to detect that the source identifier should be translated to a target identifier . The apparatus 100 may change the identifier on the fly, and then forward the connection to the CSMS with the target identifier . Hence , the CSMS sees that the connection is coming from the target identifier, and finds correct configurations based on the target identifier . From a perspective of the charging station management system, nothing has changed at the charging station and the CSMS may continue operating based on the target identifier even though the actual identifier of the charging station has been changed to the source identifier .

[0066] For example , the charging station 200 may connect to the apparatus 100 using a source identi fier AA_0052 of the second controller . Even though the charging station identifier has internally changed, the charging station 200 may still have a sticker on its casing showing the old identifier, such as a target identifier AA_001 . Hence , users may still try to operate the charging station with the old identifier . The apparatus 100 may obtain a routing rule indicating that the source identifier should be updated to the target identifier, such as from AA_052 to AA_001 .

[0067] The apparatus 100 may connect to the CSMS 202 by using the target identifier AA_001 . The CSMS 202 may see that the connection is associated with target identifier AA_001 . The CSMS 202 search for configurations and perform management processes based on messages received from the connection and therefore associated with the target identifier AA_001 . These configurations may be applied to the second controller via the apparatus 100 . The CSMS 202 may not know that the first controller has been replaced, since the communication between apparatus 100 and the CSMS 202 is established with the old ( target ) identifier . I f the CSMS 202 transmits a message to the charging station 200 , the apparatus 100 may receive the message . The apparatus 100 may receive the message with target identifier AA_001 and update the target identifier to the source identifier AA_052 based on the one or more routing rules . Apparatus 100 may then transmit the message to the second control ler by us ing the source identifier .

[0068] I f the first controller is later taken into use , the apparatus 100 may be configured to update the identifier of the first controller to a second target identifier . For example , the apparatus 100 may update the identifier A_001 to a second target identifier A_001_l . Hence , when there is a routing rule instructing that messages coming from a source identifier are routed a target identifier corresponding to the identifier of the first controller, the apparatus 100 may also obtain or automatically create a routing rule for messages coming from a charging station with said target identifier . In other words , for a certain target identifier, the routing rules may be applied in three ways : messages coming from a source identifier are forwarded with the target identifier as the sender, messages coming with the target identifier as a recipient are forwarded to the source identifier, and messages coming from the target identifier as the sender are forwarded with a different target identifier as the sender . This may assure that multiple charging stations or controllers are not managed with the same identifier in the CSMS .

[0069] In an example embodiment , EV users may have identifiers associated with them such as RFID ( radio frequency identification) tags . The RFID tag may comprise an identifier such as "A1B2" . These user identifiers may be associated with charging station identifiers . The users may have authori zation to certain charging stations . The CSMS 202 may verify the authorizations based on the user identifiers and the charging station identifiers. If a controller of a charging station is changed, it may affect the authorization process.

[0070] For example, if the apparatus 100, the CSMS 202 and charging stations operate according to OCPP, the second controller may send an authorization request (e.g., "authorize . req (idTag = "A1B2") ") comprising the source identifier and an identifier of the user, such as the RFID tag "A1B2". The apparatus 100 may receive the message and update the source identifier to the target identifier. The apparatus 100 may transmit the message to the CSMS 202 with the target identifier. The CSMS may check if the user is allowed to charge on the charging station based on the target identifier and the identifier of the user. The CSMS 202 may transmit an authorization response message (e.g., "authorize . resp (status = "Accepted")") to the apparatus 100 by using the target identifier. Apparatus 100 may update the target identifier to the source identifier and transmit the authorization response to the second controller .

[0071] In an example embodiment, a support person may try to remotely start charging via the CSMS 202. The support person may try to start charging on a charging station with the target identifier AA_001. The first controller of the charging station may have been replaced with the second controller with source identifier AA_052. The CSMS 202 and the support person may not know that there is a controller with identifier AA_0052. When the support person starts the charging process, CSMS 202 may send an OCPP start-message "remoteStartTransaction . req" with the target identifier AA_001. The apparatus 100 may receive the start-message comprising the target identifier AA_001. The apparatus 100 may detect there is a routing rule for the target identifier and update the target identifier AA_001 to the source identifier AA_052 based on the routing rule . The apparatus 100 may forward the start-message now comprising the source identifier AA_052 to the second controller . The second controller may receive the startmessage and process it . The second control ler may send a response message comprising the source identifier AA_052 (e . g . , "remoteStartTransaction . resp" ) to the CSMS 202 . The apparatus 100 may receive the response message . The apparatus 100 may again detect the routing rule to update the identifiers . The apparatus 100 may update the source identifier AA_052 to the target identifier AA_001 . The apparatus 100 may transmit the response message now comprising the target identifier AA_001 to the CSMS 202 . The CSMS 202 may then determine based on the response message that the remote start of charging was successful .

[0072] Although the old controller may be replaced with the new controller within a charging station, the procedure is also applicable when the whole charging station is replaced, and consequently, also the controllers . When the CSMS exchanges messages with charging stations , the CSMS may exchange messages with the controllers .

[0073] FIG . 3 illustrates an example of a graphical user interface for managing electric vehicle charging station identifiers . The graphical user interface 300 may be provided by the apparatus 100 , for example , via the user interface 110 . The apparatus 100 may be configured to receive user inputs via the graphical user interface 300 . The apparatus 100 may be further configured to display data for the user via the graphical user interface 300 . The data may comprise , for example , instructions for setting one or more routing rules and a list of previously set routing rules .

[0074] The apparatus 100 may be configured to receive , via the graphical user interface 300 , an indication of which controller will be replaced . The indication may comprise a charging station identifier of the controller to be set as a target identifier (e . g . , AA_0052 ) . The apparatus 100 may further receive from the user an indication of which controller replaces the first one . The indication may comprise a charging station identifier of the second controller to be set as a source identifier (e . g . , AA_0001 ) .

[0075] For example , the graphical user interface 300 may comprise one or more interface elements 302 for receiving an user input to indicate a charging station identifier, such as text fields , drop-down buttons or lists , list boxes or checkboxes . The graphical user interface 300 may further comprise one or more other user interface elements 304 allowing the user to save or cancel their selections or indications of the identifiers . The apparatus 100 may be configured to output a preview of changes made by the user . The apparatus 100 may be configured to output a list of identifiers of a network of charging stations to the graphical user interface 300 . The apparatus 100 may be further configured to output routing rules for different identifiers . The apparatus 100 may be further configured to output other data to help the user to select a correct charging station, such as POT data associated with charging stations or a map with locations and identifiers of the charging stations . The apparatus 100 may also receive as an input from the user an identifier of a charging station not yet on a list of charging stations managed by the apparatus 100 . After obtaining the charging station identifiers of the new controller and the old controller as the source identifier and the target identifier, the apparatus 100 may be configured to initiate the identifier routing process as described herein .

[0076] For example , the graphical user interface 300 may be configured to display a preview of changes to be applied based on user inputs 308 , such as that messages coming with identi fier AA_0052 wi ll be routed with the identifier AA_0001 . The graphical user interface 300 may be further configured to suggest that messages coming from the identifier AA_0001 will be routed to another identifier AA_0001 - l to avoid overlap . These routing rules can be stored at the apparatus in response to receiving an approval from the user . The graphical user interface 300 may be configured to display a list of current routing rules 310 applied by the apparatus 100 , such as that messages coming with an identifier AA_0002 are routed with identif ier AA_0002 , i . e . with the same identifier . As another example , the graphical user interface 300 may show that messages coming from a charging station AA_0057 will be routed with identifier AA_0003 , and that messages coming from a charging station with the identifier AA_0003 will be routed with identifier AA_0003- l to avoid that CSMS manages two charging station with the same identifier . The graphical user interface 300 may be configured to provide means for the user to edit 306 or delete any existing routing rule .

[0077] FIG . 4 illustrates an example of managing electric vehicle charging station identifiers with an apparatus comprising a routing logic for identifiers , such as the apparatus 100 . The apparatus 100 may be , for example , an independent server storing a routing logic 404 for charging station identifiers . The server with the routing logic 404 may comprise , for example , a websocket proxy configured to perform identifiertranslation . The apparatus 100 and a CSMS 202 may be configured to have independent connection URLs . For example , the apparatus 100 may be configured to have URL wss : / / example . com / router . For example , the CSMS 202 may be configured to have URL wss : / / example . com / csms .

[0078] A first controller of a charging station 200 may be replaced with a second controller . The second controller may be configured to open a websocket connection 400 to the URL of apparatus 100 . The second controller may have a source identi fier AA_052 . The connection URL may be for example , wss : / / example . com / router / AA_052 . The second controller may transmit messages to the apparatus 100 via the websocket connection 400 . Hence , the messages are associated with the source identifier AA_052 . The apparatus 100 may receive the messages and obtain an indication to apply a routing rule for the source identifier of the message based on the routing logic 404 . Based on the routing rule , the apparatus 100 may update the source identifier AA_052 to target identifier AA_001 . When the apparatus 100 has updated the identifier, the apparatus 100 may open a websocket connection 402 to the CSMS 202 by using the target identifier AA_001 . The websocket connection 402 may be , for example , wss : / / example . com / csms / AA_001 . The apparatus 100 may forward messages from the first controller to the CSMS 202 via the websocket connection 402 . The forwarded messages may include the target identifier . The forwarded messages may not include the source identifier . The CSMS 202 process the messages based on the target identifier . For example , the CSMS 202 may perform one or more operations according to a charging station control logic 406 and content of the message . The charging station control logic 406 may store data and configurations for a plurality of charging stations , wherein the data and configurations are retrievable based on charging station identifiers . The CSMS 202 may transmit response messages meant for the first controller to the apparatus 100 with the target identifier . The response messages may be received via the websocket connection 402 . The apparatus 100 may update the target identifier of the response message to the source identifier . Thereafter, the apparatus 100 may forward the response messages to the second controller via the websocket connection 400 . An apparatus according to the example embodiment may not require any changes to charging stations , controllers or CSMS s . This provides a way to manage charging station controller identifiers with any charging station or CSMS .

[0079] FIG . 5 illustrates an example of managing electric vehicle charging station identifiers with an apparatus comprising a routing logic for identifiers and a charging station management system . For example , the apparatus 100 may comprise a CSMS 202 , and the routing logic 404 may be configured inside the CSMS 202 .

[0080] A first controller of the charging station 200 may have been replaced with a second controller . The second controller may comprise a source identifier, e . g . , AA_052 , and the first controller may comprise a target identifier, e . g . , AA_001 . The second controller may open a websocket connection 502 , such as wss : / / example . com / csms / AA_052 to the apparatus 100 , i . e . , with the CSMS 202 . Once a message is received via the connection 502 , the apparatus 100 may update the source identifier AA_052 of the message to the target identifier AA_001 . Now the CSMS 202 can process content of the messages send from the second controller via the websocket connection 502 based on the target identifier instead of the source identifier . For example, the CSMS 202 may process identifiers of the received messages internally according to the routing logic 404 before the messages are forwarded to be processed according to a charging station control logic 406 of the CSMS 202 . The routing logic 404 may be also referred to as routing instructions . The charging station control logic 406 may be referred to as charging station control instructions . The routing instructions and / or charging station control instructions may be stored at a memory of the apparatus 100 or the CSMS .

[0081] When an apparatus comprises a CSMS configured to implement the routing logic, only one websocket connection may be used, which simplifies the architecture . For example , the routing logic may be a software component located inside the CSMS . Hence , no separate server may be needed between the charging stations and the CSMS for routing the messages .

[0082] FIG . 6 il lustrates an example of a flow chart of a data model for managing electric vehicle charging station identifiers .

[0083] At 600 , a charging station may comprise a first controller . The charging station and the controller may have identifiers such as AA_001 . The first controller may be connected to an apparatus 100 . The first controller may be replaced with a second controller . The second controller may have an identi fier AA_051 . The second controller may connect to apparatus 100 . The identifier of the first controller may be referred to as the target identifier and the identifier of the second controller may be referred to as the source identifier . In general , a charging station may comprise a controller configured with an identifier, wherein the identifier is a charging station identifier . A source identifier may refer to an identifier of a charging station sending a message . A target identifier may refer to an identifier based on which charging station related data is stored at a CSMS 202 .

[0084] At 602 , the apparatus 100 may be configured to perform routing operations for messages received from charging stations based on the routing rules . For example , the apparatus 100 may comprise instruction to at least one of update an identifier of received messages , establish connections for forwarding the messages with updated identifier or forward the messages with the updated identifier to a specified destination inside the apparatus . The apparatus 100 may be connected to the CSMS 202 .

[0085] At 604 , the apparatus 100 may be configured to obtain zero or more routing rules on how a source identifier of a controller is translated to a target identifier for routing purposes . The apparatus 100 may update the source identifier to the target identifier based on the routing rule ( s ) .

[0086] At 606 , the CSMS 202 may receive messages from the apparatus 100 . In an embodiment , the apparatus 100 comprises the CSMS 202 , and the CSMS 202 may be directly connected with the charging station 200 . The CSMS 202 may comprise charging station data 608 of a plurality of charging stations , identified by identifiers of zero or more charging stations . The charging station data 608 may include for example , PCI data, charging history, access rights and the like .

[0087] FIG . 7 il lustrates an example of a flow chart of a routing algorithm in an apparatus , such as the apparatus 100 .

[0088] At 700 , a controller of a charging station may open a connection to the apparatus 100 with a source identifier . The established connection may be a websocket connection, but could be also another type of a connection . The apparatus 100 may be configured to check if there is a routing rule for the source identifier of the controller .

[0089] At 702 , the apparatus 100 may be configured move to 704 if there is not a routing rule for the source identifier and to 706 if there is a routing rule for the source identifier .

[0090] At 704 , if a routing rule is not found, the apparatus 100 may be configured to determine that a target identif ier is the same as the source identifier of the controller . In other words , the apparatus may proceed without changing the source identifier .

[0091] At 706 , if a routing rule is found, the apparatus 100 may be configured to replace the source identity with a target identif ier of the routing rule . After the target identifier is set , the apparatus 100 may proceed to 708 . At 708 , the apparatus 100 may be configured to open a target connection to CSMS 202 with the target identifier, such as a websocket connection .

[0092] At 714 , the apparatus 100 may be configured to wait for a message from the controller from the connection established with the source identifier .

[0093] At 716, the apparatus 100 may be configured to detect that the message from the controller is received . Thereafter, the apparatus 100 may be configured to send the message to the CSMS through the target connection . Hence , the message is received by the CSMS with the target identifier . The apparatus 100 may be further configured to continue to wait for other messages coming through the connection established with the source identifier .

[0094] At 710 , the apparatus 100 may be configured to wait for a message from the CSMS 202 from the target connection .

[0095] At 712 , the apparatus 100 may receive a message associated with the target identifier from the CSMS 202 . The apparatus 100 may be configured to update the target identifier associated with the message based on the routing rule to the source identi fier . Then, the apparatus 100 may be configured to send the mes sage to the controller through the source connection based on the source identifier . The apparatus 100 may further continue to wait if other messages are received via the target connection from the CSMS , and forward them to the controller with the changed identifier .

[0096] FIG . 8 il lustrates an example of a flow chart of another implementation of a routing algorithm in an apparatus when a message is received from a charging station .

[0097] At 800 , a controller of the charging station may send a message to the CSMS 202 . The apparatus 100 may receive the message and check if there is a routing rule with the source identifier of the controller . At 802 , if a routing rule is found, the apparatus 100 may move to operation 804 . I f a routing rule is not found, the apparatus 100 may move to operation 806 .

[0098] At 804 , if a routing rule is found, the apparatus 100 may be configured to set a target identifier of the routing rule in place of the source identifier . The target identifier may be linked with correct data for the charging station in the CSMS 202 .

[0099] At 806 , if a routing rule is not found, the target identifier in the CSMS 202 may be the same as the source identifier of the controller .

[0100] At 808 , the apparatus 100 may update the source identifier of a message to the target identifier .

[0101] At 810 , the apparatus 100 may process the message with the target identifier by the CSMS .

[0102] FIG . 9 i llustrates an example of a flow chart of a routing algorithm in an apparatus when a message is received from a CSMS .

[0103] At 900 , the CSMS 202 may send a message to a controller of a charging station . The message may be sent based on a target identifier stored at the CSMS for the charging station . The apparatus 100 may check if there is a routing rule with the target identifier .

[0104] At 902 , if a routing rule is found, the apparatus 100 may move to 904 . I f a routing rule is not found, the apparatus 100 may move to operation 906 .

[0105] At 904 , if the routing rule is found, the target identifier is replaced with a source identifier of the routing rule .

[0106] At 906 , if the routing rule is not found, the apparatus may determine that a source identifier is the same as the target identifier .

[0107] At 908 , the apparatus 100 may change the target identifier of the message to the source identifier .

[0108] At 910 , the apparatus 100 may send the message with the updated identifier to the controller . Hence , the message is received by a correct charging station even when a different charging station identifier is configured for the controller of the charging station and the CSMS .

[0109] FIG . 10 illustrates an example of a method 1000 for managing electric vehicle charging station identifiers . The method may be performed by a computing device , such as the apparatus 100 .

[0110] At 1002 , the method may comprise obtaining at least one routing rule , wherein a first charging station identifier is linked to a second charging station identifier . The first charging station identifier may be a source identifier based on which messages received from a specific charging station are identified . The target identifier may be an earl ier charging station identifier based on which configurations of the charging station are stored at a charging station management system . The apparatus 100 may store a plurality of routing rules for different charging stations , wherein each routing rule links a current identifier of a charging station with an earlier identifier of the charging station . The identifier of the charging station may have changed, for example , due to a replacement of a broken controller of the charging station .

[0111] At 1004 , the method may comprise receiving a message for the CSMS sent by a charging station with the first charging station identifier .

[0112] At 1006 , the method may comprise checking if there i s a routing rule for the first charging station identifier . If a routing rule for the source identifier is detected, it may be checked what is the second charging station identifier linked with the first charging station identifier .

[0113] At 1008 , the method may comprise replacing the first charging station identifier associated with the message with the second charging station identifier based on the routing rule . For example , the message may be received by the apparatus 100 configured to translate charging station identifiers in messages to a given source identifier or target identi fier based on the routing rules stored at the apparatus . A charging station identifier may be associated with a message based on an established connection for sending the message and / or the message may comprise the charging station identifier as a parameter .

[0114] At 1010 , the method may comprise forwarding the message to be processed by the CSMS with the second charging station identifier . Hence, the CSMS is able to process the message as if it was received from a charging station having the second charging station identifier instead from a charging station having the first charging station identifier . Therefore , the CSMS is able to find data stored for managing operations of a specific charging station with a changed identifier . The charging station with the changed identifier may continue operating as before as the identifier is translated to the previous identifier for messages exchanged between the charging station and the CSMS .

[0115] It is obvious to a person skil led in the art that with the advancement of technology, the basic idea of the invention may be implemented in various ways . The invention and its embodiments are thus not limited to the examples described above , instead they may vary within the scope of the claims .

[0116] Further features of the methods directly result from the functionalities and parameters of the apparatus as described in the appended claims and throughout the specification and are therefore not repeated here . It is noted that one or more operations of the method may be performed in different order .

[0117] An apparatus , such as a server device configured with routing capabilities , may be configured to perform or cause performance of any aspect of the method ( s ) described herein . Further, a computer program may comprise instructions for causing, when executed, an apparatus to perform any aspect of the method ( s ) described herein . Further, an apparatus may comprise means for performing any aspect of the method ( s ) described herein . According to an example embodiment , the means comprises at least one processor , and memory including program code , the at one memory and the program code configured to, when executed by the at least one processor, cause performance of any aspect of the method ( s ) .

[0118] Any range or device value given herein may be extended or altered without losing the effect sought . Also , any embodiment may be combined with another embodiment unless explicitly disallowed .

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

[0120] Although subj ects may be referred to as ' first ' or ' second' subj ects , this does not necessarily indicate any order or importance of the subj ects . Instead, such attributes may be used solely for the purpose of making a difference between subj ects .

[0121] It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments . The embodiments are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages . It will further be understood that reference to ' an ' item may refer to one or more of those items . The operations 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 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.

[0122] The term 'comprising' is used herein to mean including the method, blocks, or elements identified, but that such blocks or elements do not comprise an exclusive list and a method or apparatus may contain additional blocks or elements.

[0123] As used in this application, the term 'circuitry' may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable) : (i) a combination of analog and / or digital hardware circuit (s) with sof tware / f irmware and (ii) any portions of hardware processor (s) with software (including digital signal processor ( s ) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit (s) and or processor ( s ) , such as a microprocessor ( s ) or a portion of a microprocessor ( s ) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims.

[0124] As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its ( or their) accompanying software and / or firmware . The term circuitry also covers , for example and if applicable to the particular claim element , a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device , or other computing or network device .

[0125] It will 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 exemplary embodiments . Although various embodiments have been described above with a certain degree of particularity, or with reference to one or more individual embodiments , those skilled in the art could make numerous alterations to the disclosed embodiments without departing from scope of this specification .

Claims

CLAIMS1 . An apparatus for charging station identifier management , comprising : at least one processor ; and at least one memory comprising instructions which, when executed by the at least one processor, cause the apparatus at least to : obtain at least one routing rule , wherein a first charging station identifier is linked to a second charging station identifier ; receive a message for a charging station management system sent by a charging station with the first charging station identifier ; detect there is a routing rule for the first charging station identifier ; replace the first charging station identifier associated with the message with the second charging station identifier based on the routing rule ; and forward the message to be processed by the charging station management system with the second charging station identifier .2 . The apparatus of claim 1 , wherein the at least one memory further comprises instructions which, when executed by the at least one processor, cause the apparatus to : receive a message for a charging station with the second charging station identifier ; detect there i s a routing rule for the second charging station identifier ; replace the second charging station identifier associated with the message with the first charging station identifier based on the routing rule ; and forward the message to the charging station with the first charging station identifier .3 . The apparatus of claim 1 or 2 , wherein the apparatus is coupled between at least one charging station and the charging station management system; and wherein the at least one memory comprises instruction which, when executed by the at least one processor, cause the apparatus to : detect a connection is established with the charging station with the first charging station identifier ; establish a connection with the charging station management system with the second charging station identifier based on the routing rule after detecting the connection with the charging station ; and wherein the message for the charging station management system is forwarded through the connection established with the second charging station identifier .4 . The apparatus of claim 3 , wherein the memory comprises instructions which, when executed by the at least one processor, cause the apparatus to : receive the message for the charging station via the connection established with the second charging station identifier ; and forward the message to the charging station through the connection established with the first charging station identifier .5 . The apparatus of claim 1 or 2 , wherein the apparatus comprises the charging station management system; and wherein the charging station management system is configured to connect with at least one charging station for message exchange and execute the at least one routing rule for messages exchanged through the connection .6 . The apparatus of any preceding claim, wherein the at least one memory comprises instructionswhich, when executed by the at least one processor, cause the apparatus to : receive a message for the charging station management system sent by a charging station with the second charging station identifier ; detect that messages sent for the charging station management system with the second charging station identifier are configured to be routed with a third charging station identifier ; and forward the message to be processed by the charging station management system with the third charging station identifier .7 . The apparatus of any preceding claim, wherein the at least one memory comprises instructions which, when executed by the at least one processor, cause the apparatus to : detect that there is no routing rule for an identifier associated with a received message , and forward the message without changes .8 . The apparatus of any preceding claim, wherein the at least one memory comprise instructions which, when executed by the at least one processor, cause the apparatus to : provide a user interface for setting the at least one routing rule ; and obtain the at least one routing rule from a user via the user interface .9 . A method carried out by a computing device, the method comprising : obtaining at least one routing rule , wherein a first charging station identifier is linked to a second charging station identifier ;receiving a message for a charging station management system sent by a charging station with the first charging station identifier ; detecting there is a routing rule for the first charging station identifier ; replacing the first charging station identifier associated with the message with the second charging station identifier based on the routing rule ; and forwarding the message to be processed by the charging station management system with the second charging station identifier .10 . The method of claim 9 , further comprising : receiving a message for a charging station with the second charging station identifier ; detecting there is a routing rule for the second charging station identifier ; replacing the second charging station identifier associated with the message with the first charging station identifier based on the routing rule ; and forwarding the message to the charging station with the first charging station identifier .11 . The method of claim 9 or 10 , comprising : receiving a message for the charging station management system sent by a charging station with the second charging station identifier ; detecting that messages sent for the charging station management system with the second charging station identifier are configured to be routed with a third charging station identifier ; and forwarding the message to be processed by the charging station management system with the third charging station identifier .12 . The method of any of claims 9 to 11 , comprising : detecting a connection is established with the charging station with the first charging station identifier ; causing a connection to be established with the charging station management system with the second charging station identifier based on the routing rule after detecting the connection with the charging station ; and wherein the message for the charging station management system is caused to be forwarded through the connection established with the second charging station identifier .13 . The method of claim 12 , comprising : receiving the message for the charging station via the connection established with the second charging station identifier ; and causing the message to the charging station to be forwarded through the connection established with the first charging station identifier .14 . A computer program product compri sing instructions which, when the program is executed by a computer , cause the computer to carry out the steps of the method of any of claims 9 to 13 .15 . A computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the method of any of claims 9 to 13 .

Images