System for implementing a predefined function of an electric vehicle supply equipment and method thereof

Abstract

The present application provides a system (100) for implementing a predefined function of an electric vehicle supply equipment (EVSE), said system (100) comprising: at least one EVSE (10), and at least one local, self-contained Open Charge Point Protocol (OCPP) translator said OCPP translator (12), said OCPP translator comprising: an embedded compute platform; at least one network interface (14) for establishing a bi-directional communication with the at least one EVSE (10) for bi-directional exchange of OCPP commands, and a power supply means, wherein the embedded compute platform comprises a computing means configured to run a software means, said computing means including: an OCPP local server (16), and an internal Application Programming Interface (API) (18), configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE (10). Optionally, said computing means may further include: a Dynamic Host Configuration Protocol (DHCP) server (70), and / or a Domain Name Service (DNS) server (72). The invention further provides a method of implementing a predefined function of an EVSE though the system defined above.

Description

[0001] System for implementing a predefined function of an electric vehicle supply equipment and method thereof

[0002] The present invention belongs to the technical field of electric vehicle (EV) charging.

[0003] In particular, the present invention refers to an improved system for implementing a predefined function of an electric vehicle supply equipment (EVSE) and a local, self-contained Open Charge Point Protocol (OCPP) translator for use therein.

[0004] The present invention further refers to methods using the above-mentioned system.

[0005] EVSEs, also known as wallboxes, electric vehicle charging points (EVCS), or EV charging stations, are designed to supply electric power for charging plug-in electric vehicles.

[0006] For instance, those EVSEs can be modules that are applied to or built into a wall for the purpose of supplying electric power to an electric vehicle to be charged.

[0007] EVSEs can be located in either public or private areas.

[0008] EV charging systems are well-known in the art.

[0009] An example of a known EV charging system is shown in Fig. 1 .

[0010] A quite large number of these known system rely on Open Charge Point Protocol (OCPP) technology for communication with an OCPP remote server, usually a cloud-based server, implemented with a management platform (Fig. 1).

[0011] This management platform advantageously provides a large variety of high-level functions and / or features to the EVSE.

[0012] As a non-limiting example, said high-level functions and / or features for the EVSE may include one or more among user authentication and management, consumption recording (for later invoicing or analytics), load management, load shedding, software / firmware updates, or the like.

[0013] As shown in Fig. 1 , these known systems may include one or more EVSEs operatively connected to remote server, usually a cloud-based OCPP server.

[0014] Typically, the OCPP protocol runs on top of standard Transmission Control Protocol (TCP) / lnternet Protocol (IP), which itself is customarily carried via ethernet, WiFi, or mobile network (2 / 3 / 4 / 5G+) network interfaces. In this regard, one crucial aspect is that EVSEs are often located in underground sites, where internet connection can be poor or even absent.

[0015] This may hinder stability of communications relying on internet connection.

[0016] Therefore, there is a strongly-felt need for an enhanced solution allowing to ensure proper and efficient functionalities of EV charging systems, even in case one or more EVSEs of the system are located in an underground site with poor or even absent internet connection.

[0017] Additionally, it might be the case that high-level functions and / or features need being added to an already existing EVSE.

[0018] Usually, in these cases, the OCPP protocol interface is the existing interface available externally.

[0019] Leveraging this interface could be convenient in order to add functions and / or features to an existing EVSE without major interventions, e.g. requiring opening the EVSE to intervene on its hardware and / or software components.

[0020] In view of the above, it is an object of the present invention to provide an improved solution allowing easily and reliably implementing either a new or an already existing EVSE with high- level functions and / or features, without the need of major intervention on hardware and / or software level, further without requiring connection to the internet.

[0021] This object is achieved by the provision of a system according to independent claim 1 .

[0022] The present invention provides a system for implementing a predefined function of an electric vehicle supply equipment (EVSE), said system comprising: at least one electric vehicle supply equipment (EVSE), and at least one local, self-contained Open Charge Point Protocol (OCPP) translator said OCPP translator comprising: an embedded compute platform; at least one network interface for establishing a bi-directional communication with the at least one EVSE for bi-directional exchange of OCPP commands, and a power supply means, wherein the embedded compute platform comprises a computing means configured to run a software means, said computing means including: an OCPP local server, and an internal Application Programming Interface (API), configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE, optionally wherein said computing means further includes: a Dynamic Host Configuration Protocol (DHCP) server, and / or a Domain Name Service (DNS) server.

[0023] The aforesaid object is further accomplished by the provision of methods as defined in claims 13 to 15, respectively.

[0024] The present invention relates to a system for implementing a predefined function of an electric vehicle supply equipment (EVSE).

[0025] In a first embodiment, the system comprises at least one electric vehicle supply equipment (EVSE).

[0026] For example, the system may comprise a plurality of EVSEs.

[0027] Alternatively, the system may comprise a single EVSE.

[0028] This may be the case of an EV charging system installed in a private area for private use.

[0029] The system further comprises at least one local, self-contained Open Charge Point Protocol (OCPP) translator.

[0030] The OCPP translator comprises embedded compute platform.

[0031] The OCPP translator further comprises at least one network interface for establishing a bidirectional communication with the at least one EVSE for bi-directional exchange of OCPP commands.

[0032] There is also a power supply means provided in the OCPP translator.

[0033] This allows supplying power to the electronic components of the OCPP translator. The embedded compute platform comprises a computing means.

[0034] In particular, said computing means is configured to run a software means, preferably a dedicated software means.

[0035] The computing means comprises an OCPP local server.

[0036] The computing means further comprises an internal Application Programming Interface (API).

[0037] In particular, the API is configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE.

[0038] Advantageously, said computing means may further include a Dynamic Host Configuration Protocol (DHCP) server.

[0039] Additionally or alternatively, said computing means may further include Domain Name Service (DNS) server.

[0040] The DHCP server and the DNS server are optional components of the computing means.

[0041] That is the DHCP server and / or the DNS server may be absent without prejudice to the functionalities of the computing means.

[0042] The DHCP server and the DNS server are useful to provide the EVSE the “impression” of being connected to a local network infrastructure, provided with internet access.

[0043] The invention is based on the basic idea that, by packaging an OCPP local server into simple, low-power small device which does not require connection to the internet, and using it to expose the logical functions provided by the OCPP local server (e.g. start / stopping charging session, retrieving consumption information regarding completed charging sessions, smart charging / load management, or the like) to another device, e.g. a controller, it is possible to implement high level features and / or functionalities to an either new or existing EVSE without major interventions on the hardware and / or software level, further without the need of any connection to the internet.

[0044] This is particularly convenient when new functions and / or features must be implemented to existing EVSEs, e.g. already installed or unsold EVSEs, as it allows retrofitting said functions and / or features in a simple and effective manner.

[0045] In particular, major modifications (or even the complete substitution) of already installed EVSEs can be avoided. Also, unsold EVSEs can be easily retrofitted with new functions and / or features, thereby preventing said EVSEs from remaining unsold due to hardware and / or software obsolescence.

[0046] Also, since no connection to the internet is required, EVSEs can be reliably implemented with new functions and / or features even when internet connection is unstable or absent, as in the case of an underground site.

[0047] A large number among existing EVSEs are based on OCPP technology, which allows easily implementing retrofitting with the system of the invention.

[0048] The system according to the invention is also cost-effective, as it provides a low-cost retrofit solution that prevents more significant costs deriving from major structural interventions on the EVSE, if not the entire replacement of the same.

[0049] Indeed, the above-described system is not only designed for retrofit on already installed or unsold EVSEs.

[0050] Conversely, the system of the invention may as well be implemented with newly-produced EVSEs.

[0051] In a non-limiting example, the embedded compute platform can be a Raspberry Pi.

[0052] Different boards, even customized boards, may also be used, provided that they have a sufficiently small size to be packaged into an enclosure to be installed either next to or inside of the EVSE.

[0053] The OCPP translator configures a self-contained device providing all the necessary network interfaces (in hardware) and network services (in software) to make the EVSE “believe” it is connected to a local network, and able to communicate with a remote, preferably cloud-based, OCPP server.

[0054] The application logic behind this OCPP server must expose an API to an internal application.

[0055] The OCPP translator can be placed either inside the EVSE or in the proximity of the same.

[0056] The latter option is more convenient in case of retrofit to an already installed EVSE.

[0057] According to a second embodiment, a system is provided having structural and functional features that are similar to those of the above-described first embodiment, but further comprising a back-end system. In this embodiment, the system also comprises at least one mobile device, capable to implement smart functionalities.

[0058] Conveniently, said at least one mobile device can be a smartphone of the user.

[0059] The at least one mobile device is configured to establish bi-directional communication with the back-end system and the at least one OCPP translator for data exchange.

[0060] This solution is convenient as it allows to easily and intuitively implementing data exchange between the OCPP translator and the back-end system.

[0061] In case of poor or absent internet connection (e.g., in an underground site), the mobile device will trigger data exchange as soon as an internet connection becomes available again.

[0062] According to a third embodiment, a system is provided having structural and functional features that are similar to those of the above-described second embodiment, but where the at least one OCPP translator further comprises and additional hardware module.

[0063] In particular, the additional hardware module may comprise a Short Range Device (SRD) for establishing a bi-directional communication with the mobile device.

[0064] Preferably, said SRD is a Bluetooth® module.

[0065] Additionally or alternatively, the additional hardware module may comprise a clock.

[0066] Additionally or alternatively, the additional hardware module may comprise a nonvolatile storage means.

[0067] Additionally or alternatively, the additional hardware module may comprise a cryptographic device.

[0068] The above-listed components of the additional hardware module do not need to be present altogether.

[0069] According to a fourth embodiment, a system is provided having structural and functional features that are similar to those of the above-described third embodiment, but further comprising an OCPP back-end system.

[0070] Also, in this embodiment, the at least one OCPP translator comprises a local OCPP client.

[0071] The OCPP back-end system may establish bi-directional communication with the local OCPP client for bi-directional exchange of OCPP commands. Otherwise stated, in the present embodiment, the OCPP translator not only includes the OCPP server, operatively connected to the EVSE, but also the OCPP client which is configured to connect to the OCPP back-end system (e.g., in the cloud), to which the EVSE originally connected to.

[0072] Accordingly, OCPP translator is enabled implementing a “passthrough” OCPP function.

[0073] According to a fifth embodiment, a system is provided having features similar to those of the above-described system according to the fourth embodiment, but where the OCPP translator further comprises a local payment client.

[0074] The system further comprises a payment processing back-end system.

[0075] There is also a payment terminal provided in the system.

[0076] In particular, the payment terminal is configured to establish a bi-directional communication with the local payment client of the at least one OCPP translator and with the payment processing back-end system for bi-directional data exchange.

[0077] The payment terminal can be a device allowing the user to proceed with the payment after completion of an EV charging session, e.g. by credit card.

[0078] The payment terminal and the OCPP back-end system, which can be both cloud-based, are adapted to locally control EV charging sessions and retrieve consumption data after completion of each EV charging session.

[0079] The user is thus enabled to proceed with the payment after completion of the charging session in an intuitive, comfortable and safe manner.

[0080] Also, this solution is particularly convenient since some countries are starting to mandate the provision of payment terminals on public EVSEs.

[0081] The local payment client, the payment terminal, and the payment processing back-end system as described above can be easily retrofitted to already installed or unsold EVSEs.

[0082] Also, said components can be conveniently provided on newly manufactured EVSEs.

[0083] Optionally, the system according to the present fifth embodiment may include an OCPP client, such as the OCPP client described above with respect to the fourth embodiment. According to a sixth embodiment, the system may comprise a plurality of EVSEs arranged on a site, and a plurality of OCPP translators.

[0084] In particular, each EVSE of said plurality of EVSEs is operatively connected to a respective OCPP translator of said plurality of OCPP translators.

[0085] Here, the system further comprises a local load management feature, said load management feature being configured to run a software means for operating a local load management algorithm.

[0086] The local load management feature is configured to establish bi-directional communication with each of said plurality of OCPP devices for load management through a network.

[0087] Preferably, said network is a mesh network.

[0088] Even more preferably, said network is a wireless mesh network.

[0089] Load management is in particular needed in a condition where a plurality of EVSEs share a limited allocation of power.

[0090] For instance, in case an overall power of 16A is available and a plurality of EVSEs, e.g. three EVSEs, must share this capacity, a single user can draw 16A, but multiple users (using a respective EVSE) must be controlled in such a way that the total amount of power remains under 16A.

[0091] In the state of the art, this is typically performed as a part of the remote, e.g. cloud-based, management platform and uses standard OCPP messages to modulate or control the power from each individual EVSE based on a model of the power constraints on a given site.

[0092] An OCPP client, such as the OCPP client described above with respect to the fourth embodiment, is provided in order to implement a “passthrough” function, allowing “passing through” OCPP sessions between the locally-provided OCPP translator and the OCPP back- end system, preferably a cloud-based OCPP back-end system.

[0093] The local load management feature is capable of functioning independently from remote, e.g. cloud-based, management features, e.g. implemented in the OCPP back-end system.

[0094] The provision of a local load management feature as defined above allows improving the level of reliability in load management, especially because said local load management feature does not fail in case internet connection and / or an OCPP back end provider are unstable or unavailable. In the above described second to sixth embodiments, the embedded compute platform of the at least one OCPP translator may be configured to run a software means for: determining that a vehicle is connected to an EVSE for EV charging; upon determining that a vehicle has been connected to the EVSE, receiving a user ID from the at least one mobile device; mapping credentials of the connected vehicle to the received user ID; authenticating the connected vehicle, and providing a command to the EVSE to trigger a charging session for the connected vehicle.

[0095] This solution is particularly convenient since the user is not requested to implement any other action to trigger the charging session, other than plugging his / her vehicle to the EVSE.

[0096] Also, in the above-described first to sixth embodiments, the embedded compute platform of the at least one OCPP translator may be configured to run a software means for: determining that at least one EVSE is connected to a respective OCPP translator; upon determining that the at least one EVSE has been connected to the respective OCPP translator, identifying the connected at least one EVSE, and automatically implementing a configuration process for the connected at least one EVSE.

[0097] Accordingly, the efforts and knowledge that are required for implementing a configuration / update process for the EVSE can be significantly reduced.

[0098] In particular, in the absence of these features, a technician would be required to implement a quite complex, error-prone configuration process.

[0099] Conversely, with these features, an OCPP Gateway can, upon initial connection to the EVSE, detect and automatically configure / update settings in the EVSE, without any additional and complex manual step.

[0100] The configuration process can therefore be implemented in an easier and more intuitive manner, which is less time-consuming and less prone to error when compared to known manual configuration processes. In the present embodiment, the software means of the embedded compute platform may be configured to perform identification of the at least one connected EVSE through an ethernet or WiFi MAC address.

[0101] Additionally or alternatively, the embedded compute platform may be configured to perform identification of the at least one connected EVSE through OS fingerprinting.

[0102] Additionally or alternatively, the embedded compute platform may be configured to perform identification of the at least one connected EVSE through port scanning.

[0103] Additionally or alternatively, the embedded compute platform may be configured to perform identification of the at least one connected EVSE through web interface characterization / recognition.

[0104] Additionally or alternatively, the embedded compute platform may be configured to perform identification of the at least one connected EVSE through Bluetooth® scanning.

[0105] In the present embodiment, the software means of the embedded compute platform may be configured to perform automatic configuration of the at least one connected EVSE through web configuration.

[0106] Additionally or alternatively, the software means of the embedded compute platform may be configured to perform automatic configuration of the at least one connected EVSE through Bluetooth® configuration via Bluetooth® Low Energy (BLE) Generic ATTribute Profile (GATT).

[0107] Additionally or alternatively, the software means of the embedded compute platform may be configured to perform automatic configuration of the at least one connected EVSE through a vendor proprietary configuration protocol via a network socket.

[0108] In the above-described embodiments, the at least one network interface of the at least one OCPP translator may include a WiFi connection interface and / or an Ethernet connection interface.

[0109] Advantageously, the at least one network interface of the at least one OCPP translator includes both a WiFi connection interface and an Ethernet connection interface.

[0110] In the above-described embodiments, the at least one OCPP translator may further include at least one additional network interface for connection to the internet.

[0111] Preferably, said at least one additional network interface includes a WiFi connection interface and / or an Ethernet connection interface. Advantageously, the at least one additional network interface includes both a WiFi connection interface and an Ethernet connection interface.

[0112] In the above-described embodiments, the predefined function for the at least one EVSE may include user authentication.

[0113] Additionally or alternatively, said predefined function may include charging sessions control.

[0114] Additionally or alternatively, said predefined function may include consumption recording.

[0115] Additionally or alternatively, said predefined function may include load management.

[0116] Additionally or alternatively, said predefined function may include load shedding.

[0117] Additionally or alternatively, said predefined function may include software and / or firmware update.

[0118] The present invention further provides a local, self-contained Open Charge Point Protocol (OCPP) translator.

[0119] In particular, said OCPP translator is adapted for use in a system according to any one of the above-described embodiments.

[0120] The OCPP translator comprises an embedded compute platform.

[0121] The OCPP translator further comprises at least one network interface for establishing a bidirectional communication with the at least one EVSE for bi-directional exchange of OCPP commands.

[0122] There is also a power supply means provided in the OCPP translator.

[0123] This allows supplying power to the electronic components of the OCPP translator.

[0124] The embedded compute platform comprises a computing means.

[0125] In particular, said computing means is configured to run a software means.

[0126] The computing means comprises an OCPP local server.

[0127] The computing means further comprises an internal Application Programming Interface (API).

[0128] In particular, the API is configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE. Advantageously, said computing means may further include a Dynamic Host Configuration Protocol (DHCP) server.

[0129] Additionally or alternatively, said computing means may further include Domain Name Service (DNS) server.

[0130] The DHCP server and the DNS server are optional components of the computing means.

[0131] Advantageously, the OCPP translator may further comprise a local OCPP client.

[0132] Advantageously, the at least one network interface of the OCPP translator may include a WiFi connection interface and / or an Ethernet connection interface.

[0133] Preferably, the at least one network interface of the at least one OCPP translator includes both a WiFi connection interface and an Ethernet connection interface.

[0134] Advantageously, the OCPP translator may further comprise at least one additional network interface for connection to the internet.

[0135] Preferably, said at least one additional network interface may include a WiFi connection interface and / or an Ethernet connection interface.

[0136] More preferably, the at least one additional network interface includes both a WiFi connection interface and an Ethernet connection interface.

[0137] Advantageously, the OCPP translator may further comprise an additional hardware module.

[0138] In particular, the additional hardware module may comprise a Short Range Device (SRD) for establishing a bi-directional communication with the mobile device.

[0139] Preferably, said SRD is a Bluetooth® module.

[0140] Additionally or alternatively, the additional hardware module may comprise a clock.

[0141] Additionally or alternatively, the additional hardware module may comprise a nonvolatile storage means.

[0142] Additionally or alternatively, the additional hardware module may comprise a cryptographic device. The present invention further provides a method of implementing a predefined function of an electric vehicle supply equipment (EVSE) though the system according to the system according to the above-described first embodiment, the method comprising: providing at least one electric vehicle supply equipment (EVSE); providing at least one local, self-contained Open Charge Point Protocol (OCPP) translator; operatively connecting the at least one EVSE to a respective OCPP translator through at least one network interface of the OCPP translator, and running a software means of the OCPP translator to operate a dedicated application for implementing a predefined function for the at least one EVSE.

[0143] As mentioned, said predefined function for the at least one EVSE may include one or more among user authentication, charging sessions control, consumption recording, load management, load shedding, and / or software and / or firmware update.

[0144] The present invention further provides a method of implementing a predefined function of an electric vehicle supply equipment (EVSE) through the system according to any one of abovedescribed second to sixth embodiments, the method comprising: providing at least one electric vehicle supply equipment (EVSE); providing at least one local, self-contained Open Charge Point Protocol (OCPP) translator; operatively connecting the at least one EVSE to a respective OCPP translator through at least one network interface of the OCPP translator; operating a back-end system to define a command regarding a predefined function for the at least one EVSE; transmitting the defined command to a mobile device of a user, said mobile device being configured to establish bi-directional communication with the back-end system and with the at least one OCPP translator for bi-directional data exchange; forwarding the received command from the mobile device to the at least one OCPP translator, and running a software means of the OCPP translator to operate a dedicated application for implementing the predefined function for the at least one EVSE.

[0145] Similar as above, said predefined function for the at least one EVSE may include one or more among user authentication, charging sessions control, consumption recording, load management, load shedding, and / or software and / or firmware update.

[0146] The present invention further provides a method of performing load management for a plurality of electric vehicle supply equipment (EVSEs) arranged on a site through the system according to the above-described sixth embodiment, the method comprising: providing said electric vehicle supply equipment (EVSEs), each EVSE of said plurality of EVSEs being operatively connected to a respective local, self-contained Open Charge Point Protocol (OCPP) translator among a plurality of OCPP translators; providing a local load management feature, said local load management feature being configured to establish bi-directional communication with each of said plurality of OCPP translators through a network, preferably a mesh network, more preferably a wireless mesh network; running a software means of the local load management feature to operate a local load management algorithm for defining a load control command for said plurality of EVSEs present on the site, and transmitting the defined load control command to each of said plurality of OCPP translators through the network, wherein each of said plurality of OCPP translators is configured to forward the received load control command to a respective EVSE.

[0147] The present invention further provides a method of automatically authenticating a vehicle and triggering an electric vehicle (EV) charging session for said vehicle through the system according to any one of the above-described second to sixth embodiments, the method comprising: running a software means implemented on an embedded compute platform of a local, self-contained Open Charge Point Protocol (OCPP) translator, operatively connected to a respective electric vehicle supply equipment (EVSE), to determine that a vehicle is connected to the EVSE for EV charging; upon determining that a vehicle has been connected to the EVSE, receiving a user ID from at least one mobile device of a user; mapping credentials of the connected vehicle to the received user ID; authenticating the connected vehicle, and providing a command to the EVSE to trigger a charging session for the connected vehicle.

[0148] Accordingly, the user is enabled to easily and intuitively triggering a charging session, without being required to implement any actions other than plugging his / her vehicle to the EVSE.

[0149] The present invention further provides a method of performing configuration and / or update of an electric vehicle supply equipment (EVSE) through the system according to any one of the above-described second to sixth embodiments, the method comprising: running a software means implemented on an embedded compute platform of a local, self-contained Open Charge Point Protocol (OCPP) translator, the OCPP translator being operatively connected to the EVSE, to perform the following steps: determining that the EVSE is connected to the OCPP translator; upon determining that the EVSE has been connected to the OCPP translator, identifying the connected EVSE, and automatically implementing a configuration process for the connected EVSE.

[0150] Accordingly, efforts and knowledge that are required for implementing a configuration / update process for the EVSE can be significantly reduced.

[0151] Advantageously, the step of identifying the connected EVSE can be implemented through an ethernet or WiFi MAC address.

[0152] Additionally or alternatively, the step of identifying the connected EVSE can be implemented through OS fingerprinting.

[0153] Additionally or alternatively, the step of identifying the connected EVSE can be implemented through port scanning.

[0154] Additionally or alternatively, the step of identifying the connected EVSE can be implemented through web interface characterization / recognition. Additionally or alternatively, the step of identifying the connected EVSE can be implemented through Bluetooth® scanning.

[0155] Advantageously, the step of implementing a configuration process for the connected EVSE can be implemented through web configuration.

[0156] Additionally or alternatively, the step of implementing a configuration process for the connected EVSE can be implemented through Bluetooth® configuration via Bluetooth® Low Energy (BLE) Generic ATTribute Profile (GATT).

[0157] Additionally or alternatively, the step of implementing a configuration process for the connected EVSE can be implemented through a vendor proprietary configuration protocol via a network socket.

[0158] Further details and advantages of the present invention shall now be disclosed in connection with the drawings, where:

[0159] Fig. 1 is a diagram illustrating an EV charging system according to the prior art;

[0160] Fig. 2 is a diagram illustrating a system for implementing a predefined function of an EVSE according to a first embodiment of the invention;

[0161] Fig. 3 is a diagram illustrating a system for implementing a predefined function of an EVSE according to a second embodiment of the invention. The system is structurally similar to that of Fig. 2, but further includes a back-end system and at least one mobile device;

[0162] Fig. 4 is a diagram illustrating a system for implementing a predefined function of an EVSE according to a third embodiment of the invention. The system is structurally similar to that of Fig. 3, but further includes an additional hardware module;

[0163] Fig. 5 is a diagram that schematically illustrates interactions in the system of Fig. 4;

[0164] Fig. 6 is a diagram illustrating a system for implementing a predefined function of an EVSE according to a fourth embodiment of the invention. The system is structurally similar to that that of Fig. 4, but further includes, inter alia, a local OCPP client;

[0165] Fig. 7 is a diagram that schematically illustrates interactions in the system of Fig. 6;

[0166] Fig. 8 is a diagram illustrating a system for implementing a predefined function of an EVSE according to a fifth embodiment of the invention. The system is structurally similar to that of Fig. 6, but further includes a local payment client, a payment terminal, and a payment processing back-end system;

[0167] Fig. 9 is a diagram illustrating a system for implementing a predefined function of an EVSE according to a sixth embodiment of the invention. Here, the system includes a plurality of EVSEs arranged on a site and a plurality of respective OCPP translators. Also, the system is implemented with a local load management feature;

[0168] Fig. 10 is a diagram that schematically illustrates interactions for translating a local load management message to OCPP in the system of Fig. 9.

[0169] Fig. 2 schematically shows a system 100 for implementing a predefined function of an electric vehicle supply equipment (EVSE) according to a first embodiment of the invention.

[0170] The system 100 comprises at least one electric vehicle supply equipment 10, hereinafter referred to with its acronym EVSE 10.

[0171] The system 100 further comprises at least one local, self-contained Open Charge Point Protocol (OCPP) translator 12.

[0172] In particular, the OCPP translator 12 comprises an embedded compute platform.

[0173] The OCPP translator 12 further comprises at least one network interface 14 for establishing a bi-directional communication with the at least one EVSE 10, for bi-directional exchange of OCPP commands.

[0174] The OCPP translator 12 further comprises a power supply means (not shown), for supplying power to the electronic components of the OCPP translator 12.

[0175] The embedded compute platform comprises a computing means configured to run a software means.

[0176] In particular, said computing means comprise an OCPP local server 16.

[0177] The computing means further comprise an internal Application Programming Interface (API) 18, configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE 10.

[0178] In the shown embodiment, the computing means further comprises a Dynamic Host Configuration Protocol (DHCP) server 70 and a Domain Name Service (DNS) server 72 (Fig. 2). The DHCP server 70 and the DNS server 72 are optional components of the OCPP translator 12.

[0179] That is, the DHCP server 70 and / or the DNS server 72 may also be absent without prejudice to the functionalities of the OCPP translator 12.

[0180] The OCPP translator 12 can be installed either within the EVSE 10 or in the proximity of the same.

[0181] As mentioned, the latter option is preferred in case the system 100 is retrofitted to an already installed EVSE 10.

[0182] By packaging the OCPP local server 16 within a simple, low-power small device, such as the OCPP translator 12, which does not require connection to the internet, and using it to expose the logical functions provided by the OCPP local server 16 to another device, e.g. a controller, it is possible to implement high-level features and / or functionalities to the EVSE without major interventions on its hardware and / or software components, even in the absence of an internet connection.

[0183] The latter aspect is particularly convenient considering that EVSEs are often installed in underground sites where internet connection might be poor or even absent.

[0184] Fig. 3 schematically shows a system 200 for implementing a predefined function of an EVSE according to a second embodiment of the present invention.

[0185] Similar to the system 100 of the first embodiment, the system 200 of the present embodiment includes at least one EVSE 20 and at least one OCPP translator 22.

[0186] The OCPP translator 22 comprises an embedded compute platform, at least one network interface 24 for establishing a bi-directional communication with the at least one EVSE 20 for bi-directional exchange of OCPP commands, and a power supply means.

[0187] Also, the embedded compute platform comprises a computing means configured to run a software means, said computing means including an OCPP local server 26 and an internal Application Programming Interface (API) 18, configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE 20.

[0188] Optionally, the computing means may further include a DHCP server 70 and / or a DNS server 72. In the shown embodiment, the computing means includes both a DHCP server 70 and a DNS server 72 (Fig. 3).

[0189] In the present embodiment, the system 200 further comprises a back-end system 74 and at least one mobile device 76, capable of implementing smart functionalities.

[0190] In the shown embodiment, the back-end system 74 is cloud-based.

[0191] Also, in the shown embodiment, the at least one mobile device 76 is a smartphone of the user (Fig. 3).

[0192] The at least one mobile device 76 is adapted to establish bi-directional communication with the back-end system 74 and the at least one OCPP translator 22 for data exchange (Fig. 3).

[0193] Fig. 4 schematically shows a system 300 for implementing a predefined function of an EVSE according to a third embodiment of the invention.

[0194] The system 300 is structurally similar to the system 200 according to the above-described second embodiment, shown in Fig. 3.

[0195] In particular, the system 300 according to the present embodiment comprises at least one EVSE 30 and at least one OCPP translator 32.

[0196] The OCPP translator 32 comprises an embedded compute platform, at least one network interface 34 for establishing a bi-directional communication with the at least one EVSE 30 for bi-directional exchange of OCPP commands, and a power supply means.

[0197] Also, the embedded compute platform comprises a computing means configured to run a software means, said computing means including an OCPP local server 36 and an internal Application Programming Interface (API) 18, configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE 30.

[0198] Optionally, the he computing means may further include DHCP server 70 and / or a DNS server 72.

[0199] In the shown embodiment, the computing means includes both DHCP server 70 and a DNS server 72 (Fig. 4).

[0200] Similar to the system 200 of the second embodiment, the system 300 of the present embodiment comprises a back-end system 74 and at least one mobile device 76 capable of implementing smart functionalities, e.g. a smartphone. In the shown embodiment, the back-end system 74 is cloud-based.

[0201] In the present embodiment the at least one OCPP translator 32 further comprises and additional hardware module 84 (Fig. 4).

[0202] In the shown embodiment, the additional hardware module 84 comprises: a Short Range Device (SRD) for establishing a bi-directional communication with the mobile device, preferably wherein said SRD is a Bluetooth® module 86; a clock 88; a nonvolatile storage means 90, and; a cryptographic device 92.

[0203] Not shown is that the above-listed components of the additional hardware module 84 do not need to be present altogether.

[0204] To the contrary, only few among those components can be provided in the additional hardware module 84, without prejudice to its functionality.

[0205] Exemplary interactions between components of the system 300 according to the present embodiment are schematically illustrated in Fig. 5.

[0206] Fig. 6 schematically shows a system 400 for implementing a predefined function of an EVSE according to a fourth embodiment of the invention.

[0207] The system 400 is structurally similar to the system 300 according to the above-described third embodiment, shown in Fig. 4.

[0208] In particular, the system 400 according to the present embodiment includes at least one EVSE 40 and at least one OCPP translator 42.

[0209] The OCPP translator 42 comprises an embedded compute platform, at least one network interface 44 for establishing a bi-directional communication with the at least one EVSE 40 for bi-directional exchange of OCPP commands, and a power supply means.

[0210] Also, the embedded compute platform comprises a computing means configured to run a software means, said computing means including an OCPP local server 46, and an internal Application Programming Interface (API) 18, configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE 40. Optionally, the computing means may further include DHCP server 70 and / or a DNS server 72.

[0211] In the shown embodiment, the computing means includes both DHCP server 70 and a DNS server 72 (Fig. 6).

[0212] Similar as above, the system 400 of the present embodiment comprises a back-end system 74 and at least one mobile device 76 capable of implementing smart functionalities, e.g. a smartphone.

[0213] In the shown embodiment, the back-end system 74 is cloud-based.

[0214] In the present embodiment, the system 400 further comprises an OCPP back-end system 80.

[0215] In the shown embodiment, the OCPP back-end system 80 is cloud-based (Fig. 6).

[0216] Also, in the present embodiment, the at least one OCPP translator 42 further comprises a local OCPP client 78.

[0217] In particular, the OCPP back-end system 80 is configured to establish bi-directional communication with the local OCPP client 78 for bi-directional exchange of OCPP commands.

[0218] Here, the OCPP translator 42 not only includes the OCPP server 46, operatively connected to the EVSE 40, but also the OCPP client 78 which is configured to connect to the OCPP back- end system 80 (e.g., cloud-based), to which the EVSE 40 originally connected to (Fig. 6).

[0219] Accordingly, the OCPP translator 42 is enabled implementing a “passthrough” OCPP function.

[0220] For instance, the OCPP translator 42 may act such a charging session appears to the EVSE 40 as being initiated from the OCPP server 46, and at the same time appears to the OCPP server 46 as being initiated from the EVSE 40.

[0221] In the shown embodiment, the system 400 further includes an additional hardware module 84, having the same features of the additional hardware module 84 described above with respect to the system 300 of the third embodiment.

[0222] The additional hardware module 84 is an optional feature of the system 400.

[0223] That is, the additional hardware module 84 may as well be absent without prejudice to the functionality of the system 400. Exemplary interactions between components of the system 400 according to the present embodiment are schematically shown in Fig. 7

[0224] Fig. 8 schematically shows a system 500 for implementing a predefined function of an EVSE according to a fifth embodiment of the invention.

[0225] The system 500 of the present embodiment is structurally similar to the system 400 of the above-described fourth embodiment, shown in Fig. 6.

[0226] Similar as above, the system 500 according to the present embodiment includes at least one EVSE 50 and at least one OCPP translator 52.

[0227] The OCPP translator 52 comprises an embedded compute platform, at least one network interface 54 for establishing a bi-directional communication with the at least one EVSE 50 for bi-directional exchange of OCPP commands, and a power supply means.

[0228] Also, the embedded compute platform comprises a computing means configured to run a software means, said computing means including an OCPP local server 56, and an internal Application Programming Interface (API) 18, configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE 50.

[0229] Optionally, the computing means may further include DHCP server 70 and / or a DNS server 72.

[0230] In the shown embodiment, the computing means includes both DHCP server 70 and a DNS server 72 (Fig. 8).

[0231] Similar as above, the system 500 of the present embodiment comprises a back-end system 74 and at least one mobile device 76 capable of implementing smart functionalities, e.g. a smartphone.

[0232] Similar as above, the system 500 of the present embodiment further comprises a back-end system 74 and at least one mobile device 76 capable of implementing smart functionalities, e.g. a smartphone.

[0233] In the shown embodiment, the back-end system 74 is cloud-based.

[0234] Also, the system 500 comprises an OCPP back-end system 80, such as the OCPP back-end system 80 described above with respect to the system 400 of the fourth embodiment.

[0235] In the shown embodiment, the OCPP back-end system 80 is cloud-based (Fig. 8). In the shown embodiment, the system 500 comprises a local OCPP client 78 (Fig. 8).

[0236] The local OCPP client 78 is identical in structure and function to the local OCPP client 78 described above with respect to the system 400 of the fourth embodiment.

[0237] In the present embodiment, the OCPP translator 52 further comprises a local payment client 94.

[0238] Also, the system 500 comprises a payment processing back-end system 96.

[0239] In the shown embodiment, the payment processing back-end system 96 is cloud-based (Fig. 8).

[0240] Still further, the system 500 comprises a payment terminal 98.

[0241] In particular, the payment terminal 98 is configured to establish a bi-directional communication with the local payment client 94 of the at least one OCPP translator 52 and with the payment processing back-end system 96 for bi-directional data exchange.

[0242] With the system 500 according to the present embodiment, the user is enabled to easily, intuitively and safely perform payment after completion of an EV charging session, e.g. by credit card, by using the payment terminal 98 installed in, or in the proximity of, the EVSE 50.

[0243] In the shown embodiment, the system 500 further includes an additional hardware module 84, having the same features of the additional hardware module 84 described above with respect to the system 300 of the second embodiment.

[0244] The additional hardware module 84 is an optional feature of the system 500.

[0245] That is, the additional hardware module 84 may as well be absent without prejudice to the functionality of the system 500.

[0246] Fig. 9 schematically shows a system 600 for implementing a predefined function of an EVSE according to a sixth embodiment of the present invention.

[0247] The system 600 comprises a plurality of EVSEs 60 arranged on a site.

[0248] The system 600 further comprises a plurality of OCPP translators 62.

[0249] As shown in Fig. 9, each EVSE 60 of said plurality of EVSEs is operatively connected to a respective OCPP translator 62 of said plurality of OCPP translators 62. Similar as above, each OCPP translator 62 comprises an embedded compute platform, at least one network interface 64 for establishing a bi-directional communication with the at least one EVSE 60 for bi-directional exchange of OCPP commands, and a power supply means.

[0250] Also, the embedded compute platform comprises a computing means configured to run a software means, said computing means including an OCPP local server 66, and an internal Application Programming Interface (API) 18, configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE 60.

[0251] Optionally, the he computing means may further include DHCP server 70 and / or a DNS server 72.

[0252] In the shown embodiment, the computing means includes both DHCP server 70 and a DNS server 72 (Fig. 9).

[0253] In the shown embodiment, the system 600 comprises a local OCPP client 78.

[0254] The local OCPP client 78 is similar in structure and function to the local OCPP client 78 described above with respect to the system 400 according to the fourth embodiment.

[0255] Not shown is that the system 600 may further comprise back-end system and at least one mobile device, such as the back-end system 74 and the at least one mobile device 76 described above.

[0256] For instance, the back-end system can be a cloud-based back-end system, in the same way as illustrated in Figs. 3-4, 6 and 8.

[0257] In the present embodiment, the system 600 further comprises a local load management feature 900 configured to run a software means for operating a local load management algorithm (Fig. 9).

[0258] The local load management feature 900 is configured to establish bi-directional communication with each of said plurality of OCPP devices 60 for load management, through a network.

[0259] Preferably, said network is a mesh network.

[0260] Even more preferably, said network is a wireless mesh network.

[0261] In the shown embodiment, the system 600 further includes an additional hardware module 84, having the same features of the additional hardware module 84 described above with respect to the system 300 of the second embodiment. The additional hardware module 84 is an optional feature of the system 600.

[0262] That is, the additional hardware module 84 may as well be absent without prejudice to the functionality of the system 600.

[0263] Advantageously, in the above-described second to sixth embodiments, the embedded compute platform of the at least one OCPP translator 22; 32; 42; 52; 62 may be configured to configured to run a software means for: determining that a vehicle is connected to an EVSE 20; 30; 40; 50; 60 for EV charging; upon determining that a vehicle has been connected to the EVSE 20; 30; 40; 50; 60, receiving a user ID from the at least one mobile device 76; mapping credentials of the connected vehicle to the received user ID; authenticating the connected vehicle, and providing a command to the EVSE 20; 30; 40; 50; 60 to trigger a charging session for the connected vehicle.

[0264] Accordingly, the user is enabled to trigger a charging session without implementing any action other than connecting his / her vehicle (not shown) to the EVSE 20; 30; 40; 50; 60.

[0265] Advantageously, in the above-described embodiments, the embedded compute platform of the at least one OCPP translator 12; 12; 22; 32; 42; 52; 62 is configured to run a software means for: determining that at least one EVSE 10; 20; 30; 40; 50; 60 is connected to a respective OCPP translator 12; 22; 32; 42; 52; 62; upon determining that the at least one EVSE 10; 20; 30; 40; 50; 60 has been connected to the respective OCPP translator 12; 22; 32; 42; 52; 62, identifying the connected at least one EVSE 10; 20; 30; 40; 50; 60, and automatically implementing a configuration process for the connected at least one EVSE 10; 20; 30; 40; 50; 60.

[0266] Accordingly, a configuration process for an EVSE 10; 20; 30; 40; 50; 60 can be easily implemented, without requiring the intervention of highly-trained technicians for manually setup of the EVSE to work with the connected OCPP translator. Advantageously, in the above-described embodiments, the at least one network interface 14; 24; 34; 44; 54; 64 of the at least one OCPP translator 12; 22; 32; 42; 52; 62 includes a WiFi connection interface and / or an Ethernet connection interface.

[0267] In the shown embodiments, the at least one network interface 14; 24; 34; 44; 54; 64 of the at least one OCPP translator 12; 22; 32; 42; 52; 62 includes both a WiFi connection interface and Ethernet connection interface.

[0268] Also, in the above-described fourth to sixth embodiments, the at least one OCPP translator 42; 52; 62 further includes at least one additional network interface 82 for connection to the internet.

[0269] In particular, said at least one additional network interface 82 serves for the purpose of establishing a bi-directional connection with the remote OCPP back-end system 80, preferably a cloud-based OCPP back-end system 80 (Figs. 6 and 8-9).

[0270] Preferably, the at least one additional network interface 82 includes a WiFi connection interface and / or an Ethernet connection interface.

[0271] Even more preferably, the at least one additional network interface 82 includes both a WiFi connection interface and an Ethernet connection interface (Figs. 6 and 8-9).

[0272] Advantageously, in the above-described embodiments, said predefined function for the at least one EVSE 10; 20; 30; 40; 50; 60 includes one or more among: user authentication; charging sessions control; consumption recording; load management; load shedding, and / or software and / or firmware update.

[0273] Advantageously, in the above-described embodiments, the software means of the embedded compute platform may be configured to perform identification of the at least one connected EVSE 10; 20; 30; 40; 50; 60 through: an ethernet or WiFi MAC address; OS fingerprinting; port scanning; web interface characterization / recognition, and / or

[0274] Bluetooth® scanning.

[0275] Advantageously, in the above-described embodiments, the software means of the embedded compute platform is configured to perform automatic configuration of the at least one connected EVSE 10; 20; 30; 40; 50; 60 through: web configuration;

[0276] Bluetooth® configuration via Bluetooth® Low Energy (BLE) Generic ATTribute Profile (GATT), and / or a vendor proprietary configuration protocol via a network socket.

[0277] The present invention further provides local, self-contained Open Charge Point Protocol (OCPP) translator 12; 22; 32; 42; 52; 62.

[0278] In particular, the OCPP translator 12; 22; 32; 42; 52; 62 is adapted for use in any of the systems 100; 200; 300; 400; 500; 600 according to the above-described embodiments, respectively shown in Figs. 2-4, 6 and 8-9.

[0279] In particular, the OCPP translator 12; 22; 32; 42; 52; 62 comprises at least one network interface 14; 24; 34; 44; 54; 64 for establishing a bi-directional communication with at least one electric vehicle supply equipment (EVSE) 10; 20; 30; 40; 50; 60 for bi-directional exchange of OCPP commands.

[0280] The OCPP translator 12; 22; 32; 42; 52; 62 further comprises a power supply means, supplying power to the electronic components of the OCPP translator 12; 22; 32; 42; 52; 62.

[0281] The embedded compute platform comprises a computing means configured to run a software means.

[0282] In particular, said computing means include: an OCPP local server 16; 26; 36; 46; 56; 66, and an internal Application Programming Interface (API) 18 configured to interface with a dedicated software application to implement a function for the at least one EV charging device 10; 20; 30; 40; 50; 60.

[0283] In shown embodiments, the computing means further include a Dynamic Host Configuration Protocol (DHCP) server 70 and a Domain Name Service (DNS) server 72 (Figs. 2-4, 6 and 8- 9).

[0284] The DHCP server 70 and the DNS server are optional components of the computing means.

[0285] That is, the DHCP server 70 and / or the DNS server may also be absent without prejudice to the functionality of the computing means.

[0286] In some embodiments, as shown in Figs. 6 and 8-9, the OCPP translator 42; 52; 62 further comprises a local OCPP client 78.

[0287] The structural and functional features of the local OCPP client 78 have been described in the foregoing, in particular with reference to the system 400 according to the fourth embodiment.

[0288] The at least one network interface 14; 24; 34; 44; 54; 64 of the OCPP translator 12; 22; 32; 42; 52; 62 may include a WiFi connection interface and / or an Ethernet connection interface.

[0289] Preferably, the at least one network interface 14; 24; 34; 44; 54; 64 of the OCPP translator 12; 22; 32; 42; 52; 62 includes both a WiFi connection interface and an Ethernet connection interface (Figs. 2-4, 6 and 8-9).

[0290] In some embodiments, as shown in Figs. 6 and 8-9, the OCPP translator 42; 52; 62 further comprises at least one additional network interface 82 for connection to the internet.

[0291] In particular, said at least one additional network interface 82 serves for the purpose of establishing a bi-directional connection with the remote OCPP back-end system 80, preferably a cloud-based OCPP back-end system 80 (Figs. 6 and 8-9).

[0292] Preferably, the at least one additional network interface 82 includes a WiFi connection interface and / or an Ethernet connection interface.

[0293] Even more preferably, the at least one additional network interface 82 includes both a WiFi connection interface and an Ethernet connection interface (Figs. 6 and 8-9).

[0294] In some embodiments, as shown in Figs. 4, 6 and 8-9, the OCPP translator 32; 42; 52; 62 further comprises an additional hardware module 84. In the shown embodiments, the additional hardware module 84 comprises: a Short Range Device (SRD), preferably wherein said SRD is a Bluetooth® module 86; a clock 88; a nonvolatile storage means 90, and a cryptographic device 92.

[0295] Not shown is that the above-listed components of the additional hardware module 84 do not need to be present altogether.

[0296] To the contrary, only few among those components can be provided in the additional hardware module 84, without prejudice to its functionality.

[0297] The present invention further provides a method of implementing a predefined function of an electric vehicle supply equipment (EVSE), in particular through the system 100 according to the first embodiment described above and shown in Fig. 2.

[0298] In particular, the method comprises: providing at least one electric vehicle supply equipment (EVSE) 10; providing at least one local, self-contained Open Charge Point Protocol (OCPP) translator 12; operatively connecting the at least one EVSE 10 to a respective OCPP translator 12 through at least one network interface of the OCPP translator 12, and running a software means of the OCPP translator 12 to operate a dedicated application for implementing a predefined function for the at least one EVSE 10.

[0299] As mentioned, said predefined function for the at least one EVSE includes one or more among: user authentication; charging sessions control; consumption recording; load management; load shedding, and / or software and / or firmware update.

[0300] The present invention further provides a method of implementing a predefined function of an electric vehicle supply equipment (EVSE), in particular through the system 200; 300; 400; 500; 600 according to any of the second to sixth embodiments described above and respectively shown in Figs. 3-4, 6 and 8-9.

[0301] In particular, the method comprises: providing at least one electric vehicle supply equipment (EVSE) 20; 30; 40; 50; 60; providing at least one local, self-contained Open Charge Point Protocol (OCPP) translator 22; 32; 42; 52; 62; operatively connecting the at least one EVSE 20; 30; 40; 50; 60 to a respective OCPP translator 22; 32; 42; 52; 62 through at least one network interface 24; 34; 44; 54; 64 of the OCPP translator 22; 32; 42; 52; 62; operating a back-end system 74 to define a command regarding a predefined function for the at least one EVSE 20; 30; 40; 50; 60; transmitting the defined command to a mobile device 76 of a user, said mobile device 76 being configured to establish bi-directional communication with the back-end system 74 and with the at least one OCPP translator 22; 32; 42; 52; 62 for bi-directional data exchange; forwarding the received command from the mobile device 76 to the at least one OCPP translator 22; 32; 42; 52; 62, and running a software means of the OCPP translator 22; 32; 42; 52; 62 to operate a dedicated application for implementing the predefined function for the at least one EVSE 20; 30; 40; 50; 60.

[0302] As mentioned, said predefined function for the at least one EVSE includes one or more among: user authentication; charging sessions control; consumption recording; load management; load shedding, and / or software and / or firmware update.

[0303] The present invention further provides a method of performing load management for a plurality of electric vehicle supply equipment (EVSEs) 60 arranged on a site, in particular through the system 600 according to the sixth embodiment described above and shown in Fig. 9.

[0304] In particular, the method comprises: providing said electric vehicle supply equipment (EVSEs) 60, each EVSE 60 of said plurality of EVSEs 60 being operatively connected to a respective local, self-contained Open Charge Point Protocol (OCPP) translator 62 among a plurality of OCPP translators 62; providing a local load management feature 900, said local load management feature 900 being configured to establish bi-directional communication with each of said plurality of OCPP translators 62 through a network, preferably a mesh network, more preferably a wireless mesh network; running a software means of the local load management feature 900 to operate a local load management algorithm for defining a load control command for said plurality of EVSEs 60 present on the site, and transmitting the defined load control command to each of said plurality of OCPP translators 62 through the network, wherein each of said plurality of OCPP translators 62 is configured to forward the received load control command to a respective EVSE 60.

[0305] The present invention further provides a method of automatically authenticating a vehicle and triggering an electric vehicle (EV) charging session for said vehicle, in particular through the system 200; 300; 400; 500; 600 according to any of the second to sixth embodiments described above and respectively shown in Figs. 3-4, 6 and 8-9.

[0306] In particular, the method comprises: running a software means implemented on an embedded compute platform of a local, self-contained Open Charge Point Protocol (OCPP) translator 22; 32; 42; 52; 62, operatively connected to a respective electric vehicle supply equipment (EVSE) 20; 30; 40; 50; 60, to determine that a vehicle is connected to the EVSE 20; 30; 40; 50; 60 for EV charging; upon determining that a vehicle has been connected to the EVSE 20; 30; 40; 50; 60, receiving a user ID from at least one mobile device 76 of a user; mapping credentials of the connected vehicle to the received user ID; authenticating the connected vehicle, and providing a command to the EVSE 20; 30; 40; 50; 60 to trigger a charging session for the connected vehicle.

[0307] Accordingly, the user is enabled to trigger a charging session without taking any action other than connecting his / her vehicle (not shown) to the EVSE 20; 30; 40; 50; 60.

[0308] The present invention further provides a method of performing configuration and / or update of an electric vehicle supply equipment (EVSE) 10; 20; 30; 40; 50; 60 through the system 100; 200; 300; 400; 500; 600 according to any of the first to sixth embodiments described above and respectively shown in Figs. 2-4, 6 and 8-9.

[0309] In particular, the method comprises: running a software means implemented on an embedded compute platform of a local, self-contained Open Charge Point Protocol (OCPP) translator 12; 22; 32; 42; 52; 62, the OCPP translator 12; 22; 32; 42; 52; 62 being operatively connected to the EVSE 10; 20; 30; 40; 50; 60, to perform the following steps: determining that the EVSE 10; 20; 30; 40; 50; 60 is connected to the OCPP translator 12; 22; 32; 42; 52; 62; upon determining that the EVSE 10; 20; 30; 40; 50; 60 has been connected to the OCPP translator 12; 22; 32; 42; 52; 62, identifying the connected EVSE 10; 20; 30; 40; 50; 60, and automatically implementing a configuration process for the connected EVSE 10; 20; 30; 40; 50; 60. Accordingly, a configuration process for an EVSE 10; 20; 30; 40; 50; 60 can be easily implemented, without requiring the intervention of highly-trained technicians for setting up the EVSE to work with the connected OCPP translator.

[0310] Advantageously, the step of identifying the connected EVSE 10; 20; 30; 40; 50; 60 may be implemented through: an ethernet or WiFi MAC address;

[0311] OS fingerprinting; port scanning; web interface characterization / recognition, and / or

[0312] Bluetooth® scanning.

[0313] Details of the above-listed techniques for identifying a connected EVSE are provided in Table 1.

[0314] These techniques are per se known in the art.

[0315] Advantageously, the step of implementing a configuration process for the connected EVSE 10; 20; 30; 40; 50; 60 can be implemented through: web configuration;

[0316] Bluetooth® configuration via Bluetooth® Low Energy (BLE) Generic ATT ribute Profile (GATT), and / or a vendor proprietary configuration protocol via a network socket.

[0317] Details of the above-listed techniques for implementing a configuration process for the EVSE are provided in Table 2.

[0318] In connection with the above disclosure, the following aspects are explicitly disclosed:

[0319] Aspect 1: A system (100; 200; 300; 400; 500; 600) for implementing a predefined function of an electric vehicle supply equipment (EVSE), said system (100; 200; 300; 400; 500; 600) comprising: at least one electric vehicle supply equipment (EVSE) (10; 20; 30; 40; 50; 60), and at least one local, self-contained Open Charge Point Protocol (OCPP) translator said OCPP translator (12; 22; 32; 42; 52; 62) comprising: an embedded compute platform; at least one network interface (14; 24; 34; 44; 54; 64) for establishing a bi-directional communication with the at least one EVSE (10; 20; 30; 40; 50; 60) for bi-directional exchange of OCPP commands, and a power supply means, wherein the embedded compute platform comprises a computing means configured to run a software means, said computing means including: an OCPP local server (16; 26; 36; 46; 56; 66), and an internal Application Programming Interface (API) (18), configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE (10; 20; 30; 40; 50; 60), optionally wherein said computing means further include: a Dynamic Host Configuration Protocol (DHCP) server (70), and / or a Domain Name Service (DNS) server (72).

[0320] Aspect 2: The system (200; 300; 400; 500) according to Aspect 1 , wherein: the system (200; 300; 400; 500) further comprises: a back-end system (74), and at least one mobile device (76) capable to implement smart functionalities, said mobile device (76) being configured to establish bi-directional communication with the back- end system (74) and the at least one OCPP translator (12; 22; 32; 42; 52; 62) for data exchange.

[0321] Aspect 3: The system (400; 500; 600) according to Aspect 2, wherein: the system (400; 500; 600) further comprises an OCPP back-end system (80). Aspect 4: The system (400; 500; 600) according to Aspect 3, wherein: the at least one OCPP translator (42; 52; 62) further comprises a local OCPP client (78), and wherein the OCPP back-end system (80) is configured to establish bi-directional communication with the local OCPP client (78) for bi-directional exchange of OCPP commands.

[0322] Aspect 5: The system (100; 200; 300; 400; 500; 600) according to any one of the preceding Aspects, wherein: the at least one network interface (14; 24; 34; 44; 54; 64) of the at least one OCPP translator (12; 22; 32; 42; 52; 62) includes a WiFi connection interface and / or an Ethernet connection interface.

[0323] Aspect 6: The system (400; 500; 600) according to any one of the preceding Aspects, wherein: the at least one OCPP translator (42; 52; 62) further includes at least one additional network interface (82) for connection to the internet, preferably wherein said at least one additional network interface (82) includes a WiFi connection interface and / or an Ethernet connection interface.

[0324] Aspect 7: The system (300; 400; 500; 600) according to any one of Aspects 2 to 6, wherein: the at least one OCPP translator (32; 42; 52; 62) further comprises and additional hardware module (84), the additional hardware module (84) comprising one or more among: a Short Range Device (SRD) for establishing a bi-directional communication with the mobile device, preferably wherein said SRD is a Bluetooth® module (86); a clock (88); a nonvolatile storage means (90), and / or; a cryptographic device (92). Aspect 8: The system (100; 200; 300; 400; 500; 600) according to any one of the preceding Aspects, wherein: said predefined function for the at least one EVSE (10; 20; 30; 40; 50; 60) includes one or more among: user authentication; charging sessions control; consumption recording; load management; load shedding, and / or software and / or firmware update.

[0325] Aspect 9: The system (500) according to any one of the preceding Aspects, wherein: the at least one OCPP translator (52) further comprises a local payment client (94), wherein the system (500) further comprises: a payment processing back-end system (96), and a payment terminal (98), configured to establish a bi-directional communication with the local payment client (94) of the at least one OCPP translator (52) and with the payment processing back-end system (96) for bi-directional data exchange.

[0326] Aspect 10: The system (600) according to any one of the preceding Aspects, wherein: the system includes a plurality of EVSEs (60) arranged on a site and a plurality of OCPP translators (62), wherein each EVSE (60) of said plurality of EVSEs is operatively connected to a respective OCPP translator (62) of said plurality of OCPP translators (62), wherein the system (600) further comprises a local load management feature (900) configured to run a software means for operating a local load management algorithm, and wherein the local load management feature (900) is configured to establish bidirectional communication with each of said plurality of OCPP devices (60) for load management through a network, preferably a mesh network, more preferably a wireless mesh network.

[0327] Aspect 11 : The system (200; 300; 400; 500) according to any one of Aspects 2 to 10, wherein: the embedded compute platform of the at least one OCPP translator (22; 32; 42; 52) is configured to run a software means for: determining that a vehicle is connected to an EVSE (20; 30; 40; 50) for EV charging; upon determining that a vehicle has been connected to the EVSE (20; 30; 40; 50), receiving a user ID from the at least one mobile device (76); mapping credentials of the connected vehicle to the received user ID; authenticating the connected vehicle, and providing a command to the EVSE (20; 30; 40; 50) to trigger a charging session for the connected vehicle.

[0328] Aspect 12: The system (100; 200; 300; 400; 500; 600) according to any one of Aspects 1 to 10, wherein: the embedded compute platform of the at least one OCPP translator (12; 22; 32; 42; 52; 61) is configured to run a software means for: determining that at least one EVSE (10; 20; 30; 40; 50; 60) is connected to a respective OCPP translator (12; 22; 32; 42; 52; 62); upon determining that the at least one EVSE (10; 20; 30; 40; 50; 60) has been connected to the respective OCPP translator (12; 22; 32; 42; 52; 62), identifying the connected at least one EVSE (10; 20; 30; 40; 50; 60), and automatically implementing a configuration process for the connected at least one EVSE (10; 20; 30; 40; 50; 60).

[0329] Aspect 13: The system (100; 200; 300; 400; 500) according to Aspect 12, wherein: the software means of the embedded compute platform is configured to perform identification of the at least one connected EVSE (10; 20; 30; 40; 50; 60) through: an ethernet or WiFi MAC address;

[0330] OS fingerprinting; port scanning; web interface characterization / recognition, and / or

[0331] Bluetooth® scanning.

[0332] Aspect 14: The system (100; 200; 300; 400; 500) according to Aspects 12 or 13, wherein: the software means of the embedded compute platform is configured to perform automatic configuration of the at least one connected EVSE (10; 20; 30; 40; 50; 60) through: web configuration;

[0333] Bluetooth® configuration via Bluetooth® Low Energy (BLE) Generic ATT ribute Profile (GATT), and / or a vendor proprietary configuration protocol via a network socket.

[0334] Aspect 15: A local, self-contained Open Charge Point Protocol (OCPP) translator (12; 22; 32; 42; 52; 62) for use in the system (100; 200; 300; 400; 500) according to any one of Aspects 1 to 15, said OCPP translator comprising: an embedded compute platform; at least one network interface (14; 24; 34; 44; 54; 64) for establishing a bidirectional communication with at least one electric vehicle supply equipment (EVSE) (10; 20; 30; 40; 50; 60) for bi-directional exchange of OCPP commands, and a power supply means; wherein the embedded compute platform comprises a computing means configured to run a software means, said computing means including: an OCPP local server (16; 26; 36; 46; 56; 66), and an internal Application Programming Interface (API) (18) configured to interface with a dedicated software application to implement a function for the at least one EV charging device (10; 20; 30; 40; 50; 60), optionally wherein said computing means further includes: a Dynamic Host Configuration Protocol (DHCP) server (70), and or a Domain Name Service (DNS) server (72).

[0335] Aspect 16: The OCPP translator (42; 52; 62) according to Aspect 15, wherein: the OCPP translator (42; 52; 62) further comprises a local OCPP client (78).

[0336] Aspect 17: The OCPP translator (12; 22; 32; 42; 52; 62) according to Aspects 15 or 16, wherein: the at least one network interface (14; 24; 34; 44; 54; 64) of the OCPP translator (12; 22; 32; 42; 52; 62) includes a WiFi connection interface and / or an Ethernet connection interface.

[0337] Aspect 18: The OCPP translator (42; 52; 62) according to any one of Aspects 15 to 17, wherein: the OCPP translator (42; 52; 62) further comprises at least one additional network interface (82) for connection to the internet, preferably wherein said at least one additional network interface (82) includes a WiFi connection interface and / or an Ethernet connection interface.

[0338] Aspect 19: The OCPP translator according (32; 42; 52; 62) to any one of Aspects 15 to 18, wherein: the OCPP translator (32; 42; 52; 62) further comprises an additional hardware module (84), the additional hardware module (84) comprising one or more among: a Short Range Device (SRD), preferably wherein said SRD is a Bluetooth® module (86); a clock (88); a nonvolatile storage means (90), and / or a cryptographic device (92).

[0339] Aspect 20: A method of implementing a predefined function of an electric vehicle supply equipment (EVSE) though the system (100) according to Aspect 1 , the method comprising: providing at least one electric vehicle supply equipment (EVSE) (10); providing at least one local, self-contained Open Charge Point Protocol (OCPP) translator (12); operatively connecting the at least one EVSE (10) to a respective OCPP translator (12) through at least one network interface of the OCPP translator (12), and running a software means of the OCPP translator (12) to operate a dedicated application for implementing a predefined function for the at least one EVSE (10).

[0340] Aspect 21 : A method of implementing a predefined function of an electric vehicle supply equipment (EVSE) (20; 30; 40; 50; 60) through the system (200; 300; 400; 500; 600) according to Aspect 2, the method comprising: providing at least one electric vehicle supply equipment (EVSE) (20; 30; 40; 50; 60); providing at least one local, self-contained Open Charge Point Protocol (OCPP) translator (22; 32; 42; 52; 62); operatively connecting the at least one EVSE (20; 30; 40; 50; 60) to a respective OCPP translator (22; 32; 42; 52; 62) through at least one network interface (24; 34; 44; 54; 64) of the OCPP translator (22; 32; 42; 52; 62); operating a back-end system (74) to define a command regarding a predefined function for the at least one EVSE (20; 30; 40; 50; 60); transmitting the defined command to a mobile device (76) of a user, said mobile device (76) being configured to establish bi-directional communication with the back-end system (74) and with the at least one OCPP translator (22; 32; 42; 52; 62) for bidirectional data exchange; forwarding the received command from the mobile device (76) to the at least one OCPP translator (22; 32; 42; 52; 62), and running a software means of the OCPP translator (22; 32; 42; 52; 62) to operate a dedicated application for implementing the predefined function for the at least one EVSE (20; 30; 40; 50; 60).

[0341] Aspect 22: A method of performing load management for a plurality of electric vehicle supply equipment (EVSEs) (60) arranged on a site through the system (600) according to Aspect 10, the method comprising: providing said electric vehicle supply equipment (EVSEs) (60), each EVSE (60) of said plurality of EVSEs (60) being operatively connected to a respective local, self-contained Open Charge Point Protocol (OCPP) translator (62) among a plurality of OCPP translators (62); providing a local load management feature (900), said local load management feature (900) being configured to establish bi-directional communication with each of said plurality of OCPP translators (62) through a network, preferably a mesh network, more preferably a wireless mesh network; running a software means of the local load management feature (900) to operate a local load management algorithm for defining a load control command for said plurality of EVSEs (60) present on the site, and transmitting the defined load control command to each of said plurality of OCPP translators (62) through the network, wherein each of said plurality of OCPP translators (62) is configured to forward the received load control command to a respective EVSE (60).

[0342] Aspect 23: A method of automatically authenticating a vehicle and triggering an electric vehicle (EV) charging session for said vehicle through the system (200; 300; 400; 500; 600) according to Aspect 11 , the method comprising: running a software means implemented on an embedded compute platform of a local, self-contained Open Charge Point Protocol (OCPP) translator (22; 32; 42; 52; 62), operatively connected to a respective electric vehicle supply equipment (EVSE) (20; 30; 40; 50; 60), to determine that a vehicle is connected to the EVSE (20; 30; 40; 50; 60) for EV charging; upon determining that a vehicle has been connected to the EVSE (20; 30; 40; 50; 60), receiving a user ID from at least one mobile device (76) of a user; mapping credentials of the connected vehicle to the received user ID; authenticating the connected vehicle, and providing a command to the EVSE (20; 30; 40; 50; 60) to trigger a charging session for the connected vehicle.

[0343] Aspect 24: A method of performing configuration and / or update of an electric vehicle supply equipment (EVSE) (10; 20; 30; 40; 50; 60) through the system (100; 200; 300; 400; 500) according to Aspect 12, the method comprising: running a software means implemented on an embedded compute platform of a local, self-contained Open Charge Point Protocol (OCPP) translator (12; 22; 32; 42; 52; 62), the OCPP translator (12; 22; 32; 42; 52; 62) being operatively connected to the EVSE (10; 20; 30; 40; 50; 60), to perform the following steps: determining that the EVSE (10; 20; 30; 40; 50; 60) is connected to the OCPP translator (12; 22; 32; 42; 52; 62); upon determining that the EVSE (10; 20; 30; 40; 50; 60) has been connected to the OCPP translator (12; 22; 32; 42; 52; 62), identifying the connected EVSE (10; 20; 30; 40; 50; 60), and automatically implementing a configuration process for the connected EVSE (10; 20; 30; 40; 50; 60).

[0344] Aspect 25: The method according to Aspect 24, wherein: the step of identifying the connected EVSE (10; 20; 30; 40; 50; 60) is implemented through: an ethernet or WiFi MAC address;

[0345] OS fingerprinting; port scanning; web interface characterization / recognition, and / or

[0346] Bluetooth® scanning.

[0347] Aspect 26: The method according to Aspects 24 or 25, wherein: the step of implementing a configuration process for the connected EVSE (10; 20; 30;

[0348] 40; 50; 60) is implemented through: web configuration;

[0349] Bluetooth® configuration via Bluetooth® Low Energy (BLE) Generic ATTribute

[0350] Profile (GATT), and / or a vendor proprietary configuration protocol via a network socket.

[0351] Table 1 - Techniques for EVSE identification

[0352] Table 2 - Techniques for implementing an EVSE configuration process References 0; 200; 300; 400; 500; 600 Electric vehicle (EV) charging system ; 20; 30; 40; 50; 60 Electric vehicle supply equipment (EVSE); 22; 32; 42; 52; 62 OCPP translator ; 24; 34; 44; 54; 64 Network interface ; 26; 36; 46; 56; 66 Open Charge Point Protocol (OCPP) local server

[0353] Application Programming Interface (API)

[0354] Dynamic Host Configuration Protocol (DHCP)

[0355] Domain Name Service (DNS) server

[0356] Back-end system

[0357] Mobile device (smartphone)

[0358] Local OCPP client

[0359] OCPP back-end system

[0360] Additional network interface

[0361] Additional hardware module

[0362] Bluetooth® module (Short Range Device)

[0363] Clock

[0364] Nonvolatile storage means

[0365] Cryptographic device

[0366] Local payment client

[0367] Payment processing back-end system

[0368] Payment terminal 0 Local load management feature

Claims

Claims1. A system (100; 200; 300; 400; 500; 600) for implementing a predefined function of an electric vehicle supply equipment (EVSE), said system (100; 200; 300; 400; 500; 600) comprising: at least one electric vehicle supply equipment (EVSE) (10; 20; 30; 40; 50; 60), and at least one local, self-contained Open Charge Point Protocol (OCPP) translator said OCPP translator (12; 22; 32; 42; 52; 62) comprising: an embedded compute platform; at least one network interface (14; 24; 34; 44; 54; 64) for establishing a bi-directional communication with the at least one EVSE (10; 20; 30; 40; 50; 60) for bi-directional exchange of OCPP commands, and a power supply means, wherein the embedded compute platform comprises a computing means configured to run a software means, said computing means including: an OCPP local server (16; 26; 36; 46; 56; 66), and an internal Application Programming Interface (API) (18), configured to interface with a dedicated software application to implement a predefined function for the at least one EVSE (10; 20; 30; 40; 50; 60), optionally wherein said computing means further include: a Dynamic Host Configuration Protocol (DHCP) server (70), and / or a Domain Name Service (DNS) server (72).

2. The system (200; 300; 400; 500) according to claim 1 , characterized in thatthe system (200; 300; 400; 500) further comprises: a back-end system (74), and at least one mobile device (76) capable to implement smart functionalities, said mobile device (76) being configured to establish bi-directional communication with the back-end system (74) and the at least one OCPP translator (12; 22; 32; 42; 52; 62) for data exchange.

3. The system (400; 500; 600) according to claim 2, characterized in that the system (400; 500; 600) further comprises an OCPP back-end system (80).

4. The system (400; 500; 600) according to claim 3, characterized in that the at least one OCPP translator (42; 52; 62) further comprises a local OCPP client (78), wherein the OCPP back-end system (80) is configured to establish bi-directional communication with the local OCPP client (78) for bi-directional exchange of OCPP commands.

5. The system (100; 200; 300; 400; 500; 600) according to any one of the preceding claims, characterized in that the at least one network interface (14; 24; 34; 44; 54; 64) of the at least one OCPP translator (12; 22; 32; 42; 52; 62) includes a WiFi connection interface and / or an Ethernet connection interface.

6. The system (400; 500; 600) according to any one of the preceding claims, characterized in that the at least one OCPP translator (42; 52; 62) further includes at least one additional network interface (82) for connection to the internet, preferably wherein said at least one additional network interface (82) includes a WiFi connection interface and / or an Ethernet connection interface.

7. The system (300; 400; 500; 600) according to any one of claims 2 to 6, characterized in that the at least one OCPP translator (32; 42; 52; 62) further comprises and additional hardware module (84), the additional hardware module (84) comprising one or more among: a Short Range Device (SRD) for establishing a bi-directional communication with the mobile device, preferably wherein said SRD is a Bluetooth® module (86); a clock (88); a nonvolatile storage means (90), and / or; a cryptographic device (92).

8. The system (100; 200; 300; 400; 500; 600) according to any one of the preceding claims, characterized in that said predefined function for the at least one EVSE (10; 20; 30; 40; 50; 60) includes one or more among: user authentication; charging sessions control;consumption recording; load management; load shedding, and / or software and / or firmware update.

9. The system (500) according to any one of the preceding claims, characterized in that the at least one OCPP translator (52) further comprises a local payment client (94), wherein the system (500) further comprises: a payment processing back-end system (96), and a payment terminal (98), configured to establish a bi-directional communication with the local payment client (94) of the at least one OCPP translator (52) and with the payment processing back-end system (96) for bi-directional data exchange.

10. The system (600) according to any one of the preceding claims, characterized in that the system includes a plurality of EVSEs (60) arranged on a site and a plurality of OCPP translators (62), wherein each EVSE (60) of said plurality of EVSEs is operatively connected to a respective OCPP translator (62) of said plurality of OCPP translators (62), wherein the system (600) further comprises a local load management feature (900) configured to run a software means for operating a local load management algorithm, and wherein the local load management feature (900) is configured to establish bidirectional communication with each of said plurality of OCPP devices (60) for loadmanagement through a network, preferably a mesh network, more preferably a wireless mesh network.11 . The system (200; 300; 400; 500) according to any one of claims 2 to 10, characterized in that the embedded compute platform of the at least one OCPP translator (22; 32; 42; 52) is configured to run a software means for: determining that a vehicle is connected to an EVSE (20; 30; 40; 50) for EV charging; upon determining that a vehicle has been connected to the EVSE (20; 30; 40;50), receiving a user ID from the at least one mobile device (76); mapping credentials of the connected vehicle to the received user ID; authenticating the connected vehicle, and providing a command to the EVSE (20; 30; 40; 50) to trigger a charging session for the connected vehicle.

12. The system (100; 200; 300; 400; 500; 600) according to any one of claims 1 to 10, characterized in that the embedded compute platform of the at least one OCPP translator (12; 22; 32; 42;52; 61) is configured to run a software means for: determining that at least one EVSE (10; 20; 30; 40; 50; 60) is connected to a respective OCPP translator (12; 22; 32; 42; 52; 62); upon determining that the at least one EVSE (10; 20; 30; 40; 50; 60) has been connected to the respective OCPP translator (12; 22; 32; 42; 52; 62), identifying the connected at least one EVSE (10; 20; 30; 40; 50; 60), and automatically implementing a configuration process for the connected at least one EVSE (10; 20; 30; 40; 50; 60),preferably wherein the software means of the embedded compute platform is configured to perform identification of the at least one connected EVSE (10; 20; 30; 40; 50; 60) through: an ethernet or WiFi MAC address;OS fingerprinting; port scanning; web interface characterization / recognition, and / orBluetooth® scanning, preferably wherein the software means of the embedded compute platform is configured to perform automatic configuration of the at least one connected EVSE (10; 20; 30; 40; 50; 60) through: web configuration;Bluetooth® configuration via Bluetooth® Low Energy (BLE) Generic ATTribute Profile (GATT), and / or a vendor proprietary configuration protocol via a network socket.

13. A method of implementing a predefined function of an electric vehicle supply equipment (EVSE) though the system (100) according to claim 1 , the method comprising: providing at least one electric vehicle supply equipment (EVSE) (10); providing at least one local, self-contained Open Charge Point Protocol (OCPP) translator (12); operatively connecting the at least one EVSE (10) to a respective OCPP translator (12) through at least one network interface of the OCPP translator (12), and running a software means of the OCPP translator (12) to operate a dedicated application for implementing a predefined function for the at least one EVSE (10).

14. A method of implementing a predefined function of an electric vehicle supply equipment (EVSE) (20; 30; 40; 50; 60) through the system (200; 300; 400; 500; 600) according to claim 2, the method comprising: providing at least one electric vehicle supply equipment (EVSE) (20; 30; 40; 50; 60); providing at least one local, self-contained Open Charge Point Protocol (OCPP) translator (22; 32; 42; 52; 62); operatively connecting the at least one EVSE (20; 30; 40; 50; 60) to a respective OCPP translator (22; 32; 42; 52; 62) through at least one network interface (24; 34; 44; 54; 64) of the OCPP translator (22; 32; 42; 52; 62); operating a back-end system (74) to define a command regarding a predefined function for the at least one EVSE (20; 30; 40; 50; 60); transmitting the defined command to a mobile device (76) of a user, said mobile device (76) being configured to establish bi-directional communication with the back-end system (74) and with the at least one OCPP translator (22; 32; 42; 52; 62) for bi-directional data exchange; forwarding the received command from the mobile device (76) to the at least one OCPP translator (22; 32; 42; 52; 62), and running a software means of the OCPP translator (22; 32; 42; 52; 62) to operate a dedicated application for implementing the predefined function for the at least one EVSE (20; 30; 40; 50; 60).

15. A method of performing load management for a plurality of electric vehicle supply equipment (EVSEs) (60) arranged on a site through the system (600) according to claim 10, the method comprising: providing said electric vehicle supply equipment (EVSEs) (60), each EVSE (60) of said plurality of EVSEs (60) being operatively connected to a respective local, self-contained Open Charge Point Protocol (OCPP) translator (62) among a plurality of OCPP translators (62);providing a local load management feature (900), said local load management feature (900) being configured to establish bi-directional communication with each of said plurality of OCPP translators (62) through a network, preferably a mesh network, more preferably a wireless mesh network; running a software means of the local load management feature (900) to operate a local load management algorithm for defining a load control command for said plurality of EVSEs (60) present on the site, and transmitting the defined load control command to each of said plurality of OCPP translators (62) through the network, wherein each of said plurality of OCPP translators (62) is configured to forward the received load control command to a respective EVSE (60).

Images