system for charging electric vehicles and intermediary and user interface management controller for use in the system, charging station and system combination having the intermediary and user interface management controller

Abstract

The invention relates to a system for charging electric vehicles, comprising a charging station, a charging station management system as a backend system for the charging station, and an intermediary and user interface management controller having the functionalities of an industrial PC and comprising an intermediary unit and a user interface management unit, which are coupled to each other. The charging station comprises a charging interface for charging an electric vehicle, a human-machine user interface having a display, and a charging station controller for controlling the charging process. The intermediary and user interface management controller is interposed between the charging station controller and the charging station management system. The intermediary unit is functionally designed as a proxy control device such that the intermediary and user interface management controller can communicate with the charging station management system like a charging station by means of the intermediary unit and can communicate with the charging station like a charging station management system. The intermediary and user interface management control device is designed to control the display of the human-machine user interface of the charging station by means of the user interface management unit.

Description

[0001] System for charging electric vehicles and intermediary and user interface management control unit for use in the system, charging station and system combination with the intermediary and user interface management control unit

[0002] Field of invention

[0003] The invention relates to a system for charging electric vehicles. It further relates to a control unit for use in the system, a charging station with the control unit, and a system combination with the control unit.

[0004] Description of the state of the art

[0005] A primary function of charging stations for electric vehicles is the electrical charging of electric vehicles. In Germany, for example, wired charging of electric vehicles is defined for four charging modes, Mode 1 to 4, in the system standard DIN EN 61851-1 (VDE 0122-1). Charging mode Mode 3 is used for single-phase or three-phase AC charging at a permanently installed charging station, while charging mode Mode 4 is intended for DC charging at a permanently installed charging station. In charging modes 3 and 4, basic communication takes place between the charging station and the electric vehicle, during which information about the fundamental charging operating states is exchanged.

[0006] Modern charging stations for electric vehicles perform a variety of charging-related functions in addition to charging the vehicles themselves. These include, for example, collecting consumption data, providing status messages for upcoming maintenance, and controlling the charging process for dynamic load management.

[0007] These additional functions require communication between the charging station and a central unit, also known as a charging station management system or backend. For example, the charging station sends consumption and status data to the central unit for analysis, and the charging station receives instructions from the central unit to control its charging power over time. To exchange data and instructions between the charging station and the central unit, common charging stations have communication modules that communicate with the central unit via the internet or a mobile network.

[0008] Several players are involved in the charging infrastructure sector: The manufacturer of a charging station or charging point is not necessarily the same as the operator of a charging station or charging park, or even the energy supplier. The operator could be, for example, a hardware store or a supermarket chain. Furthermore, there are charging stations from different manufacturers, each with varying functionalities and designs. Even between charging stations from the same manufacturer, there are often significant technical differences due to the ongoing technological development of charging stations. For instance, charging stations may communicate with a backend system using different protocols.

[0009] Therefore, implementing new functions or functionalities across multiple charging stations is a significant technical challenge. Charging stations are subject to strict safety requirements, and the certification and testing process is complex.

[0010] One already known approach to achieving greater flexibility is the use of an intermediary between the charging station and the central unit:

[0011] German patent DE 102020202403A1 discloses a method for authorizing a vehicle charging process at a charging station, wherein the vehicle is connected to the charging station via a charging cable for charging its electrical energy storage system. In one embodiment, the control unit acts as a proxy / “man-in-the-middle” that mediates between the charging station and the backend. In other words, the control unit behaves vis-à-vis the backend like a charging station that wishes to authenticate itself with an authentication request, whereas the control unit behaves vis-à-vis the charging station like a backend that issues a start command to the charging station to initiate the charging process. In one embodiment, the authentication request, the authentication confirmation, and the start command are transmitted according to the Open Charge Point Protocol (OCPP), which is known per se.

[0012] EP 3872 954 A1 also reveals a proxy between charging stations and a backend.

[0013] In addition, a bypass channel for load management at multiple charging stations is disclosed. DE 10 2015 113 799 A1 addresses the problem of improving interoperability between charging stations and backend systems. To this end, an interface device is disclosed that is intended to ensure that charging stations from various manufacturers can communicate with a backend system using various protocols, and vice versa. The OCPP protocol is also mentioned. The interface device does not include a functional separation into an intermediary unit on the one hand and a user interface management unit on the other. Furthermore, the interface device is not designed as an industrial PC.

[0014] DE 10 2022 122 450 A1 pursues the objective of providing an improved charging station that facilitates compliance with calibration regulations and avoids many of the perceived disadvantages of service or maintenance interventions arising from existing calibration regulations. To this end, a charging module is described that is spatially and functionally integrated within the charging station and separated from other components. This allows the charging module to be considered a structural unit and treated as such for calibration purposes.DE 102022 122 450 A1 does not disclose a user interface management control unit with a strict functional separation into an intermediary unit, which is functionally configured as a proxy controller, on the one hand, and a user interface management unit, which controls the display of a human-machine interface, on the other. Furthermore, no industrial PC is disclosed.

[0015] DE 10 2022 103 282 A1 pursues the objective of providing cost-effective and / or rapid installation of charging points, as well as accurate and / or verifiable and / or legally compliant billing of the energy quantities transferred via the charging system between the participating parties. To this end, several functions of a charging station are combined in a centrally provided unit located on-site. The central unit comprises a communication module, enabling bidirectional communication, at least temporarily, with a remote computer or backend. The central unit includes an input module and a central control module. This control module is connected to several charging points, each equipped with an energy meter and a processing module. DE 10 2022 103 282 A1 makes no statements regarding the specific internal structure of the central control module or the communication module.The problem therefore remains that the functions of the charging station itself cannot be easily adapted or fundamentally expanded. This also negatively impacts the user-friendliness of charging stations, especially older ones.

[0016] Description of the invention

[0017] The object of the present invention is therefore to provide an improved system for charging electric vehicles that allows for the simple adaptation or improvement of charging station software functions and the addition of new software functions. In particular, the user-friendliness of charging stations is to be improved. This should not require the charging station to be recertified or retested.

[0018] The problem is solved by the subject matter of the independent patent claims. Advantageous embodiments of the invention are described in the dependent patent claims.

[0019] The present patent application claims priority from German patent application No. 10 2024 116 979.6 dated June 17, 2024, the disclosure of which is fully incorporated into the present patent application by reference.

[0020] A charging station, according to current technological standards, incorporates a charging station control unit. This control unit manages the charging process and also controls the charging station's human-machine user interface. The human-machine user interface includes at least a display device, such as a touchscreen. This allows a user to, for example, activate or stop the charging process and receive information about its progress.

[0021] The present invention is based on the realization that the direct link between the charging station control unit and the human-machine user interface must be broken in order to implement new software functions on the human-machine user interface without requiring recertification of the charging station. The existing functions and control tasks of a charging station control unit can be divided into those directly related to the physical charging process itself and electrical safety, and those not related to the physical charging process and electrical safety. The latter includes the control of the human-machine user interface.

[0022] According to the invention, an additional control unit is therefore proposed, which is specifically interposed between the charging station control unit, the charging station's human-machine user interface, and the charging station management system or backend, and optionally has various other communication interfaces. This control unit is functionally divided into two interconnected units. One unit mediates between the charging station control unit and the backend. The other unit controls functions that do not affect the physical charging process itself or electrical safety. This primarily includes the control of the human-machine user interface. This separation into two units allows new software functions for the human-machine user interface to be implemented on the charging station without requiring extensive testing or recertification.Various other communication interfaces of the control unit can provide further possibilities for controlling the human-machine user interface, which are not yet feasible in the state of the art.

[0023] Specifically, according to a first aspect, the invention relates to a system for charging electric vehicles. The system comprises a charging station for charging an electric vehicle, which includes a charging interface, a human-machine user interface with a display, and a charging station control unit for controlling the charging process. In principle, this could be an existing charging station. In addition to the display, for example a touchscreen, the human-machine user interface can include other human-machine user interfaces such as a payment terminal, etc. The charging station control unit for controlling the charging process is the control unit that manages the physical charging process itself and functions related to electrical safety.

[0024] Furthermore, the electric vehicle charging system includes a charging station management system for managing and monitoring the charging station, which forms the backend system for the charging station. Charging station management systems as backends for charging stations already exist in the prior art.

[0025] Furthermore, the electric vehicle charging system features an intermediary and user interface management control unit with the functionalities of an industrial PC, comprising an intermediary unit and a user interface management unit that are coupled together. The functionalities of an industrial PC include its software functionalities, but can also include hardware functionalities such as dustproofness and / or water resistance and / or temperature insensitivity, or similar features. The software functionalities of an industrial PC define the minimum requirements for the intermediary and user interface management control unit according to the invention.The software functionalities of an industrial PC provide a platform for function development based on modern web technologies, meaning that developing functions for the intermediary and user interface management control unit does not require any special knowledge of charging technology. This allows an operator to implement the same functions on charging stations from different manufacturers and with varying levels of development on the intermediary and user interface management control unit, thus creating a recognizable, standardized customer offering.

[0026] It should be noted that prior art charging station controllers are less advanced than the intermediary and user interface management controller according to the invention. A prior art charging station controller is typically an embedded system; it lacks a driver and does not include browser technology. The prior art intermediary and user interface management controller, with the functionalities of an industrial PC, also differs significantly from a prior art charging station controller in that it can include a desktop controller or can be based on a desktop architecture, which offers greater flexibility and various functionalities, and in particular, browser functionality.

[0027] According to the invention, the intermediary and user interface management control unit is interposed between the charging station control unit and the charging station management system, with the intermediary unit functionally configured as a proxy controller. This allows the intermediary and user interface management control unit to communicate with the charging station management system like a charging station, and vice versa. The proxy controller thus acts as an intermediary or adapter between the charging station control unit and the charging station management system. However, messages between the charging station control unit and the charging station management system are not necessarily simply passed through via the proxy controller.Alternatively, it is also possible to influence the communication between the charging station control unit and the charging station management system using proxy control. For example, data can be analyzed, requests can be filtered, and adjustments can be made as needed. It is also possible to decide whether, and if so, in what form, a message is forwarded to the charging station control unit or the charging station management system at all. Therefore, the term "proxy control" in connection with the present invention is to be interpreted broadly.

[0028] According to the invention, the intermediary and user interface management control unit is further configured to control the display of the charging station's human-machine user interface via the user interface management unit. It is also possible to control other elements of the charging station's human-machine user interface via the user interface management unit.

[0029] Furthermore, according to the invention, the intermediary unit and the user interface management unit are coupled together. Messages and / or information from the intermediary unit can thus be passed on to the user interface management unit and used there, for example, to control an application on the display. Conversely, messages and / or information from the user interface management unit can be provided to the intermediary unit and used in the intermediary unit, for example, to physically start a charging process.

[0030] According to a preferred embodiment of the invention, the user interface management unit is not configured to control the charging station control unit. This emphasizes the physical separation of functions on different control units, or the separation into an intermediary unit on the one hand and a user interface management unit on the other. The safety functions of the charging station control unit are thus ensured. Additionally or alternatively, the charging station control unit is not configured to control the display of the charging station's human-machine user interface. Instead, this control is handled by the user interface management unit of the intermediary and user interface management control unit.

[0031] Today, standardized charging communication is predominantly used in electric vehicle charging systems. The so-called OCPP protocol (Open Charge Point Protocol) is currently the most widely used protocol. Accordingly, the electric vehicle charging system according to the invention can also be configured for communication via OCPP. However, the electric vehicle charging system according to the invention, and in particular the intermediary and user interface management control unit, is fundamentally technology-open and can also be used for other future or existing protocols.

[0032] According to a preferred embodiment of the invention, the intermediary unit functionally comprises an OCPP server configured to communicate with the charging station control unit using OCPP messages. Furthermore, the intermediary unit functionally comprises an OCPP client configured to communicate with the charging station management system, i.e., the backend, using OCPP messages. The architecture of the intermediary unit is designed such that an OCPP client process and an OCPP server process can run independently of each other. This means that each process can generate OCPP messages without these messages appearing in or being required by the other process. This allows the OCPP client process and the OCPP server process to operate on different protocol versions. For example, the OCPP server process can run on the older OCPP-1.Version 6J is running, while the OCPP client process uses OCPP 2.0.1 for the charging station management system. Adaptations to future OCPP developments are also possible.

[0033] As previously described, the intermediary and user interface management control unit can also support protocols other than OCPP, either additionally or alternatively. For example, the proxy controller can also receive MQTT or CAN messages from the charging station and forward them, along with messages in other protocols such as MQTT or other IoT (Internet of Things) protocols, to the charging station management system.

[0034] According to a further preferred embodiment of the invention, the user interface management unit has an IPC bus by means of which processes of the user interface management unit communicate with each other. This allows events to be exchanged directly at the system level via internal process communication (IPC), for example, using Unix sockets, inter-container TCP / IP messages, desktop bus (D-Bus), or a dedicated messaging framework such as MQTT or Redis. Information about other processes of the user interface management unit is available to all processes via the IPC bus. According to a preferred embodiment of the invention, the intermediary unit has a message and load event manager configured to couple the proxy control of the intermediary unit with processes of the user interface management unit.The message and charging event manager thus represents the link between the intermediary unit on the one hand and the user interface management unit on the other. It can make messages from the intermediary unit usable for processes of the user interface management unit, and conversely, it can also forward messages or information, for example from the human-machine user interface, to the intermediary unit. The previously described separation of functions into those that relate to the physical charging process itself and electrical safety, and those that do not, is therefore specifically combined or coupled within the intermediary and user interface management control unit according to the invention by means of the message and charging event manager.

[0035] According to a preferred embodiment of the invention, the message and load event manager is configured to translate information from OCPP messages into events that can be made available to the processes of the user interface management unit via internal process communication (IPC). This embodiment describes a particularly preferred form of coupling the proxy control of the intermediary unit with the processes of the user interface management unit. However, the coupling could also be implemented differently (see above).

[0036] According to a further preferred embodiment of the invention, the message and load event manager is configured to generate IPC OCPP messages based on events of the internal process communication.

[0037] According to a preferred embodiment of the invention, the OCPP server is configured to interpret the OCPP messages and forward them to the message and load event manager, as well as to receive OCPP messages from the message and load event manager. Additionally or alternatively, the OCPP client is configured to interpret the OCPP messages and forward them to the message and load event manager, as well as to receive OCPP messages from the message and load event manager.

[0038] According to a preferred embodiment of the invention, the user interface management unit includes a user interface controller configured to control the human-machine user interface of the charging station. This allows, in particular, the control of the charging station's display, but also the control of other elements of the charging station's human-machine user interface.

[0039] According to a preferred embodiment of the invention, the system further comprises an external charging station content management system, and the user interface management unit further comprises a content manager. The content manager is configured to download content and / or applications from the external charging station content management system. Furthermore, the content manager is configured to control processes in the user interface control based on the downloaded content and / or applications. It thus controls the content that is available at the human-machine user interface and, in particular, at the display.

[0040] The charging station content management system can be implemented as a cloud solution, for example. However, it can also be implemented differently. The charging station content management system is external, meaning it is not located within the charging station itself, but can be accessed, for example, via a remote network or wide area network. The described application of an external charging station content management system to the electric vehicle charging system allows for the highly flexible integration of improved or entirely new functions into a charging station, and especially into the charging station's human-machine user interface. To control the human-machine user interface, the downloaded content and / or applications also include control information.Control information is the information the content manager needs to decide which content and / or application should be displayed on the charging station's human-machine user interface and at what time. This control information can relate to the charging status (e.g., free, charging starting, charging in progress, etc.) as well as the general status of the charging station, such as the time or weather information.

[0041] According to a preferred embodiment of the invention, the user interface management unit further comprises an application unit in which applications can be stored or are stored. These applications can be made available at the human-machine user interface of the charging station, and their contents can be displayed, in particular, on the display of the human-machine user interface of the charging station. The types of applications can be diverse. For example, the applications can include a basic application. This could be a simple image sequence that displays the relevant information depending on the charging process status. This image sequence can be freely designed by the operator of the charging station.It is particularly interesting for the operator of charging stations that, using the basic application which he can program, he can proactively point out frequently occurring errors or adapt specific instructions for his customers in order to reduce the frequency of errors at his charging stations.

[0042] According to a preferred embodiment of the invention, the application unit is designed as an isolated software environment, so that applications within this application unit can be used independently of the software on the charging station and independently of the charging station management system. This contributes significantly to the flexible design of applications without interfering with critical processes of the charging process itself.

[0043] According to a preferred embodiment of the invention, the application unit is configured to access a third-party server via remote communication. This allows the linking of content displayed on the charging station's screen with offers or services from a third party, such as a restaurant chain or a hardware store.

[0044] According to a preferred embodiment of the invention, the user interface management unit further comprises a hardware component manager configured to control a hardware component of the charging station that is not required for the charging process of the electric vehicle itself. This hardware component is therefore not related to the physical charging process itself or to electrical safety. For example, it is not a power electronics hardware component.

[0045] According to a preferred embodiment of the invention, the charging station, as a hardware component controllable via the hardware component manager, comprises at least one element from the following list: light element, loudspeaker, controllable and / or movable parking obstacle, QR code scanner, payment terminal, long-distance communication module, short-distance communication module, camera. A connection to an (additional) long-distance communication module can address the fact that the technical lifespan of charging stations is considerably longer than the pace of development of communication technologies. This is particularly true for charging stations in remote locations that rely on mobile communication technologies.If additional communication modules, and in particular remote communication modules, are connected to the intermediary and user interface management control unit via the hardware component manager, the additionally connected remote communication module can either take over all remote communication or be used only as a backup or for bandwidth expansion. Examples of remote communication modules as backup interfaces are LTE-M and LoRaWAN. They can serve as a secondary interface for status messages for remote maintenance if the primary interface(s) is / are unavailable. In particular, it is possible for the intermediary and user interface management control unit to receive a hardware reset command for the charging station or the intermediary and user interface management control unit via LTE-M or LoRaWAN if the charging station cannot be reached by other means.A near communication module can include, for example, Bluetooth, NFC, ultra-wideband, or another near communication technology.

[0046] According to a preferred embodiment of the invention, the intermediary and user interface management control unit has a firewall configured to protect it against interference during remote communication. Communication between the charging station and the intermediary and user interface management control unit, and in particular between the charging station control unit and the intermediary and user interface management control unit, is normally wired and therefore inherently meets higher security standards, since an attack or interference would only need to occur physically on-site and, in most cases, within the charging station's housing.By installing a firewall, the intermediary and user interface management control unit offers the operator of a charging station or charging park the option of securing the cybersecurity of their systems via the intermediary and user interface management control unit. (Briefly.)

[0047] Software development cycles and a simple mechanism for deploying new software versions on the intermediary and user interface management control unit allow the operator to keep cybersecurity up to date at all times.

[0048] According to a preferred embodiment of the invention, the electric vehicle charging system further comprises means for remote communication between the charging station and the charging station management system. Additionally or alternatively, the system further comprises means for remote communication between the intermediary and user interface management control unit on the one hand, and the charging station management system and / or an external charging station content management system and / or a third-party server on the other. In this embodiment as well, the intermediary and user interface management control unit can handle all remote communication.

[0049] According to a preferred embodiment of the invention, the intermediary and user interface management control unit is arranged in or on the housing of a charging station or in or on the housing of a charging point of a charging station. Mounting the intermediary and user interface management control unit within a housing contributes to its physical protection. During retrofitting of a charging station, the intermediary and user interface management control unit can also be arranged on the housing of a charging point or a charging station. Preferably, the intermediary and user interface management control unit is then itself housed in a housing to protect it from the elements and, if necessary, from tampering.

[0050] According to a further preferred embodiment of the invention, the industrial PC comprises at least the following: at least one processor with sufficient processing power for handling modern multimedia applications; a graphics unit that supports the display of modern multimedia applications; a working memory with a capacity sufficient for the parallel execution of multiple applications; and a hard disk with a capacity for local storage of content and / or applications.

[0051] The intermediary and user interface management control unit, as previously described, possesses functionalities, and in particular software functionalities, of an industrial PC. Advantageously, it therefore includes a multitude of communication interfaces. This wide range of interfaces significantly contributes to ensuring the described flexibility in adapting functions and implementing new functions on the display of a charging station or in other types of functions at the charging station.According to a preferred embodiment of the invention, the intermediary and user interface management control unit has the following communication interfaces: a communication interface for communication with the charging station control unit; a communication interface for communication with the charging station management system; a communication interface for communication with the display of the human-machine user interface of the charging station; and a communication interface for communication with the charging station content management system.

[0052] A communication interface for communicating with the charging station's human-machine user interface display can be established, for example, via HDMI or USB-C. The intermediary and user interface management control unit is designed, both in terms of hardware and software, for extensive multimedia applications. For example, it can support multimedia applications and implement various application libraries. Since no software element on the intermediary and user interface management control unit handles the safety functions of the charging station, the system is not affected.

[0053] Although the charging station control unit can be affected, new applications and application libraries can be installed and run without restriction on the intermediary and user interface management control unit or on its user interface management unit.

[0054] Additional communication interfaces can further expand the functionalities of the intermediary and user interface management control unit.

[0055] According to a preferred embodiment of the invention, the intermediary and user interface management control unit further comprises: at least one communication interface for communication with at least one third-party server; and / or at least one communication interface for communication with at least one hardware component of the charging station that is not required for the charging process of an electric vehicle.

[0056] It should be noted that the additional communication interfaces are not provided for in the standardized communication with OCPP according to the prior art: The intermediary and user interface management control unit according to the invention, on the other hand, can communicate with further servers and thus enables not only the display of further content, but also the execution of other applications, for example to link the available services of a location with the charging process and the human-machine user interface.

[0057] The above-described design variants of the system for charging electric vehicles can be combined in whole or in part, provided that this does not result in any technical contradictions.

[0058] According to a second aspect of the invention, it relates to an intermediary and user interface management control unit adapted for use in the system according to one of the embodiments described above. Everything stated in connection with the system for the intermediary and user interface management control unit also applies to the intermediary and user interface management control unit itself.

[0059] According to a third aspect of the invention, it relates to a charging station for electric vehicles with the intermediary and user interface management control unit as described above in several embodiments.

[0060] According to a fourth aspect of the invention, this relates to a system combination with the intermediary and user interface management control unit according to the invention, as described above in several embodiments, and with an external charging station content management system. The latter has also already been described in detail in connection with the system for charging electric vehicles.

[0061] The various aspects of the invention can also be combined wholly or partially, provided that this does not result in any technical contradictions.

[0062] The invention will be better understood with reference to the accompanying figures. These show:

[0063] Fig. 1: schematically shows a system for charging electric vehicles according to the

[0064] State of the art;

[0065] Fig. 2: schematically shows a system according to the invention for charging

[0066] Electric vehicles; Fig. 3: schematically shows communication interfaces of a vehicle according to the invention.

[0067] Intermediary and user interface management control unit;

[0068] Fig. 4: schematically shows a system according to the invention for charging

[0069] Electric vehicles with functional blocks of an intermediary and user interface management control unit according to the invention; and

[0070] Fig. 5: schematically illustrates processes in a system according to the invention for

[0071] Charging electric vehicles.

[0072] Figure 1 schematically shows a system 1000 for charging electric vehicles 2 according to the prior art. The system 1000 comprises a charging station 1 and a

[0073] Charging station management system 700 for managing and monitoring charging station 1, which forms the backend system for charging station 1. Charging station 1 and the

[0074] Charging station management systems 700 can communicate with each other via remote communication, for example, via mobile network. Charging station 1 has a charging interface for charging an electric vehicle 2 and a human-machine user interface with a display 4. A user 3 can interact with charging station 1 via the human-machine user interface and display 4, for example, to start and / or stop a charging process. The display 4 can, for example, be a touchscreen. The charging station control unit 5 is configured to control both the charging process of the electric vehicle 2 and the human-machine user interface or display 4.

[0075] To equip the human-machine user interface 4 or the display 4 with new or improved functions, modifications to the charging station control unit 5 are therefore necessary according to the current state of the art. However, due to the strict safety requirements for charging stations 1 for electric vehicles 2, these modifications to the control unit 5 necessitate renewed certification and testing processes for the charging station 1 and are therefore time-consuming.

[0076] Figure 2 schematically shows a system 1000 according to the invention for charging electric vehicles 2. Like the prior art system 1 according to Figure 1, the system 1 comprises a charging station 1 for charging an electric vehicle 2 with a charging interface, a human-machine user interface with a display 4, and a charging station control unit 5 for controlling the actual charging process. Controlling the charging process here refers to the physical charging process and related safety functions. The system 1000 also includes a charging station management system 700 for managing and monitoring the charging station 1, which forms the backend system for the charging station 1.

[0077] Unlike the prior art, system 1000 further comprises an intermediary and user interface management control unit 100 according to the invention, with the functionalities of an industrial PC, which includes an intermediary unit 110 and a user interface management unit 120 that are coupled together. The intermediary and user interface management control unit 100 is interposed between the charging station control unit 5 and the charging station management system 700, and the intermediary unit 110 is functionally configured as a proxy controller, so that the intermediary and user interface management control unit 100 can communicate with the charging station management system 700 via the intermediary unit 110 as if it were a charging station 1, and can communicate with the charging station 1 as if it were a charging station management system 700.Furthermore, the intermediary and user interface management control unit 100 is configured to control the display 4 of the human-machine user interface of the charging station 1 via the user interface management unit 100. In the embodiment shown in Figure 2, the user interface management unit 120 is therefore not configured to control the charging station control unit 5, and in the example shown, the charging station control unit 5 is also not configured to control the display 4 of the human-machine user interface of the charging station 1. Functionally, the intermediary and user interface management control unit 100 is thus divided into the intermediary unit 110 and the user interface management unit 120.The intermediary unit 110 handles the communication between the charging station control unit 5, which controls the (actual) charging process, and the external charging station management system 700. It can also transmit information about the charging process to the user interface management unit 120. The user interface management unit 120, in turn, handles communication with the display 4 and preferably one or more other hardware components 6 that are not directly involved in the charging process or are not safety-relevant. Changes can therefore be made in an associated control unit of the user interface management unit 120 completely independently of the actual physical charging process and its safety aspects. This allows for the provision of improved or entirely new functions both on the display 4 and on additional hardware components 6.Furthermore, the user interface management unit 120 is configured to transmit events and / or information from the environment of the user interface management unit 120 to the intermediary unit 110 and thus also to the charging station control unit 5 or to the charging station management system 700.

[0078] The intermediary and user interface management control unit 100 possesses the functionalities of an industrial PC. Its software architecture thus provides a platform for function development based on modern web technologies, without requiring any special knowledge of charging technology. This also makes it possible to download third-party applications or applications from external data sources into the intermediary and user interface management control unit 100 and use them to control processes that are not physically related to charging and are not safety-relevant. Figure 2 shows, as examples, a charging station content management system 800 and a third-party server 900. Both will be discussed in more detail later.

[0079] Using the system 1000 according to the invention for charging electric vehicles 2, charging stations 1 can be easily adapted and improved in their function. This applies even to charging stations 1 from different manufacturers. Operators of charging stations 1 can also develop a recognizable, nationwide, uniform customer offering. The use of charging stations 1 for the user 3 can be significantly influenced and made more convenient, and can optionally be combined with other offerings from a charging station operator, for example, with the services of a restaurant chain, a supermarket chain, a hotel, or a fleet operator.

[0080] Figure 3 schematically shows communication interfaces of an intermediary user interface management control unit 100 according to the invention. In the example shown, the intermediary and user interface management control unit 100 has, in the area of ​​the intermediary unit 110, a communication interface for communication with one or more charging station control units 5 and a communication interface for communication with the charging station management system 700, the backend of the charging station 1. Furthermore, in the example shown, the intermediary and user interface management control unit 100 comprises, in the area of ​​the user interface management unit 120, a communication interface for communication with the display 4 of the human-machine user interface of a charging station 1 and a communication interface for communication with the charging station content management system 800.Optionally, one or more additional communication interfaces can be provided. Figure 3 shows, by way of example, a communication interface for communication with at least one hardware component 6 of the charging station 1, which is not strictly required for the charging process of an electric vehicle 2. Also shown, by way of example, is a communication interface for communication with at least one third-party server 900. Due to the modern functionality of an industrial PC of the intermediary and user interface management control unit 100, one or more additional communication interfaces can easily be provided (not shown in Figure 3).

[0081] The communication interfaces shown on the left in Figure 3 are preferably implemented using wired connections. This inherently increases security against interference attacks in the area of ​​charging station 1. Communication via the communication interfaces shown on the right in Figure 3 is preferably external long-distance communication. Several options exist for this, including backup options. These will be discussed in more detail below. In the example shown, long-distance communication is protected against interference by a firewall (Firewall 101).

[0082] Figure 4 schematically shows a system 1000 according to the invention for charging electric vehicles 2 with functional blocks of an intermediary and user interface management control unit 100 according to the invention. The intermediary and user interface management control unit 100 has the functionalities of an industrial PC; in the example shown, it includes several communication interfaces, a random-access memory (RAM) for the programs, applications and content files, as well as sufficient permanent storage capacities, for example on a hard drive, NVM E storage and / or an SSD card, and one or more processor units (not all components of the industrial PC are shown in Figure 4).

[0083] In the example shown, the intermediary unit 110 functionally includes an OCPP server 111, which is configured to communicate with the charging station controller 5 (or with multiple charging station controllers 5) using OCPP messages. Furthermore, the intermediary unit 110 functionally includes an OCPP client, which is configured to communicate with the charging station management system 700, i.e., the backend, using OCPP messages. The architecture of the intermediary unit 110 is designed such that an OCPP client process and an OCPP server process can run independently of each other. This means that each process can generate messages without them appearing in the other process. This allows the two processes to operate on different protocol versions. For example, the OCPP server process can run on the older OCPP version 1.Version 6 is used, while the OCPP client process can use OCPP 2.0.1 for communication with the charging station management system 700. OCPP is currently the most widely used charging communication protocol, so it will be described in more detail as an example. However, it is also possible that the intermediary unit 110 supports protocols other than OCPP. For example, the proxy control of the intermediary unit 110 can receive MQTT or CAN messages from a charging station 5 in addition to or as an alternative to OCPP and send them to the backend 700 along with messages in other protocols such as MQTT or other IoT protocols.

[0084] In the example shown, the user interface management unit 120 has an IPC bus 130, which processes within the user interface management unit 120 use to communicate with each other. Within the user interface management unit 120, events can therefore be exchanged directly at the system level via internal process communication (IPC), for example, using Unix sockets, inter-container TCB / IP messages, desktop bus (D-Bus), or a dedicated messaging framework such as MQTT or Redis. Information about other processes is available to all processes via internal process communication (IPC).

[0085] In the example shown, the user interface management unit 120 comprises a user interface controller 121, which is configured to control the human-machine user interface 7 and, in particular, the display 4 of the charging station 1. Through internal process communication, the processes of the user interface controller 121 have access to information from the charging processes and also from processes of additional hardware components 6. In the example shown, additional hardware components 6 are controlled by a hardware component manager 123. These additional hardware components 6 are components that are not required for the charging process of the electric vehicle 1 and, in particular, are not safety-relevant. The display 4 and the additional hardware components 6 can be collectively combined to form the customer interface 7.Additional hardware components 6 can include, for example, one or more of the following: light element, speaker, controllable and / or movable parking obstacle, QR code scanner, payment terminal, camera, near-field communication module, long-distance communication module. One or more long-distance communication modules 6 can be used, in particular, as a backup long-distance communication module. This can operate, for example, via LoRaWAN or a Bluetooth beacon. However, other implementation methods are also possible. A near-field communication module can, for example, include Bluetooth, NFC, ultra-wideband, or another near-field communication technology.

[0086] In the example shown, the intermediary unit 110 has a message and load event manager 113. This manager is configured to couple the proxy control of the intermediary unit 110 with processes of the user interface management unit 120. In this example, the message and load event manager 113 is configured to translate information from OCPP messages into events that can be made available to the processes of the user interface management unit 120 via internal process communication (IPC). Additionally, in this example, the message and load event manager 113 is configured to generate OCPP messages based on events from internal process communication (IPC). In this example, the OCPP server 111 is configured to interpret OCPP messages and pass them to the message and load event manager 113, as well as to receive OCPP messages from the message and load event manager 113.In the example shown, the OCPP client 112 is also configured to interpret OCPP messages and forward them to the message and charging event manager 113, as well as to receive OCPP messages from the message and charging event manager 113. The message and charging event manager 113 is also connected to the IPC bus. This allows the message and charging event manager 113 to continuously provide all processes of the user interface management unit 110 with current charging information or a current charging status. This status includes not only the pure charging status (e.g., available, charging process being prepared, charging process in progress, charging process being completed, and error information) but also the data about the charging process that is regularly transmitted by the vehicle 2 and the charging station 1. This allows all applications on the intermediary and user interface management control unit 100, for example, to...Data such as charging duration, estimated remaining charging time, vehicle battery size, vehicle make and model, current charging power, and battery charge level are provided. It is also possible, for example in the case of fleets, for additional information such as travel route and / or planned duration of the stay at charging station 1 to be communicated to the intermediary and user interface management control unit 100. The message and charging event manager 113 preferentially provides all available data to the functions of the user interface management unit 110, so that customer functions can be directly tailored to the customer or user 3 of charging station 1.When a user 3 triggers an event at the customer interface 7, the message and charging event manager 113 translates the information from the IPC bus into OCPP events. These events are then forwarded by the OCPP server processes and the OCPP client process to the charging station controller 5 and the charging station management system 700, respectively. For example, a customer input on the touchscreen 4 can initiate the start or stop of a charging process, which is then forwarded via the message and charging event manager 113 to the charging station controller 5 and the charging station management system 700. This allows the key customer functions of a charging process to be controlled via the customer interface of the intermediary and user interface management controller 100, or via the user interface management unit 120.

[0087] In the example shown, system 1000 also includes an external charging station content management system 800, and the user interface management unit 120 also includes a content manager 122. The content manager 122 is configured to download content and / or applications from the external charging station content management system 800. Furthermore, the content manager 122 is configured to control processes in the user interface management controller 121 based on the downloaded content and / or applications 124a, b, c, d. The content and / or applications also contain control information. This control information is what the content manager 122 needs to decide which content should be displayed on the display 4 at any given time. The control information can relate to the charging status (e.g., free, charging starting, charging in progress, etc.).The content manager 122 can refer to the charging station's status, as well as its general status, such as the time or weather information. For example, after a charging process has started in the morning, it can offer a hot drink, a hot meal in bad weather, or ice cream on a summer day. Based on the control information, the content manager 122 controls the content and application 124a, b, c, d that corresponds to the current charging and system state according to the control information. It is important to note that, according to a preferred embodiment, the specific information from the charging process is also available for controlling the content. A possible application would be the display of vehicle advertisements, where, during a charging process, the model of the advertising brand that is most similar to the charging vehicle 2 is promoted.

[0088] The content of the customer interface 7, controlled by the content manager 121, can be diverse. It ranges from simple image sequences that guide the user 3 through a charging process, to advertising images or videos, to complex applications 124a, b, c, d that interact with other systems on-site or remotely. Applications 124a, b, c, d can also be used solely to improve charging station operation or to control charging stations 1. Additionally or alternatively, applications without impacting the customer can provide a charging station operator 1 with expanded data available for remote maintenance.

[0089] Basically, the content manager 122 controls which applications 124a, b, c, d and / or content run at the customer interface 7 or at the human-machine user interface with the display 4 (or possibly at other hardware components 6 of the customer interface 7) and in the intermediary and user interface management control unit 100, as well as their prioritization. One or more applications 124a, b, c, d or processes can run simultaneously on the intermediary and user interface management control unit itself and process information from the IPC bus 130.

[0090] In the example shown, the user interface management unit 120 also includes an application unit 124. This application unit 124 can contain one or more applications 124a, b, c, d. These applications of application unit 124 can provide the content that the user interface management unit 120 displays or makes available to a user 3 on the display 4 and / or another hardware component 6 of the customer interface 7. For example, application unit 124 includes a basic application in the form of a simple image sequence that displays the relevant information depending on the charging status. This image sequence can, in principle, be freely configured by the operator of the charging station 1.It can be particularly interesting for an operator that, using the basic application, he can proactively point out frequently occurring errors or adapt specific instructions for his customers, so that the frequency of errors at his charging stations 1 can be reduced.

[0091] For example, an extension of the basic application could include the display of media content, such as film sequences, during certain states of the charging station or the charging process. Another extension level could involve combining content from the display 4 with control of other hardware components 6 via the hardware component manager 123. For example, film sequences could be accompanied by music played through speakers, or lighting elements could be used to indicate, for instance, that a charging station is becoming available, perhaps in a digital queue.

[0092] In addition to the application examples for display-oriented applications 124a, b, c, d described above, the user interface management unit 120 also provides a framework for any applications developed by third parties and uploaded to the intermediary and user interface management control unit 100 or to the user interface management unit 120 via the charging station content management system 800. These applications 124a, b, c, d can access all information from the IPC in the user interface management unit 120 and send messages via the IPC to the other processes in the user interface management unit 120 and, using the message and charging event manager 113, to the OCPP proxy controller.

[0093] According to another example, applications 124a, b, c, d can also communicate with third-party servers 900. This allows, for example, an operator of a charging station 1 to link their service with services from other providers at or near the location. Examples of this could include discount promotions when combining a charging session with a meal at the on-site restaurant, the display of location-specific advertising, or the management of the load of multiple charging sessions according to the route planning of a logistics provider.

[0094] In general, in the example shown, the user interface management unit 120 controls the processes at the customer interface 7 with the display 4 and, if applicable, other hardware components 6, and thus also the customer application framework. This is shown in Figure

[0095] Application framework 4, designated with reference numeral 125, is an isolated software environment, so that applications 124a, b, c, d can be used within application framework 125 independently of the software on charging station 1 and independently of the charging station management system 700. Accordingly, applications 124a, b, c, d do not need to be specifically certified for operation on charging station 1.

[0096] Applications 124a, b, c, d can be used with charging station 1 or with charging station control unit.

[0097] 5 interact via the OCPP proxy control 111, 112. Charging processes can be started or stopped, the charging power adjusted, or a charging process rescheduled via the applications. In combination with additional hardware components 6, applications 124a, b, c, d can support new payment methods, operate a parking barrier, or use speakers or other lighting elements to enhance the user experience of the customer interface 7.

[0098] In application framework 125, applications 124a, b, c, and d have access to the information from the IPC bus, as already mentioned in principle. Accordingly, the applications can use all data from the charging process, such as the battery charge level, battery size, information on the make and model of the electric vehicle 2, estimated charging time, etc.

[0099] In the example shown, the applications 124a, b, c, d of the application unit 124 in the application framework 125 can access third-party servers 900 via remote communication. These could be, for example, ordering systems of nearby restaurants and service providers. Accordingly, one possible application for the intermediary and user interface management control unit 100 according to the invention is that, after starting their charging process, the customer orders a meal or a drink via the corresponding application on the display 4 of the charging station 1, which the customer can then pick up at the restaurant, thus reducing their waiting time.

[0100] Further applications and workflows will be described in more detail below.

[0101] Figure 5 schematically illustrates processes in a system 1000 according to the invention for charging electric vehicles 2. For better understanding, process steps Si in Figure 5 are arranged on hardware or software units to facilitate orientation and improve the understanding of the processes according to Figure 5. First, an application 124a is downloaded and saved, then the application 124a is played and displayed on the display 4 of the human-machine user interface of the charging station 1.

[0102] In a first step S1, the application 124a and associated data can be stored as a data package in a data source 901. The data package can be signed with a certificate from the charging station content management system 800. The data source 901 can be the charging station content management system 800, but it can also be another storage location, for example, accessible via the internet, which the user interface management control unit 100 can access.

[0103] In step S2, the charging station content management system 800 can provide the content manager 122 with the information that a new user application 124a is available for the user interface management control unit 100. The charging station content management system 800 typically provides the content manager 122 with two pieces of information: the link to a storage location from which the signed data package can be downloaded, and the control information for the application 124a, such as charging status, time of day, and prioritization.

[0104] In step S3, the content manager 122 can download the data packet from the data source as soon as sufficient bandwidth is available. This download process can occur in multiple steps; that is, a download that has already started can be resumed after a connection interruption, picking up where it left off.

[0105] Once the data package has been completely downloaded, the content manager 122, in the example shown, checks the downloaded files against their signature in step S4, or performs a signature verification. The content manager 122 then unpacks the data package and saves the files to a local storage medium 126, such as a hard drive, an SD card, or similar.

[0106] Now the application 124a can be played and displayed on screen 4:

[0107] In step S5, the content manager 122 in the example shown can continuously compare the current information it receives via the IPC bus with the control information of application 124a, which it receives from the charging station content management system 800. Based on this information, the content manager 122 coordinates the start and stop of application 124a. It is possible for the processes of several applications 124a, b, c, and d to run simultaneously. This is the case, for example, if, in addition to application 124a, which controls display 4 and user interface 7, an application 124b is also running, fulfilling an operational purpose without direct interaction with user interface 7. When several applications 124a, b, c, and d are running simultaneously, the content manager 122 can ensure that only one application 124a is responsible for controlling user interface 7 or display 4 at any given time.It is possible that this application 124a, for the control of individual hardware components 4, 6, accesses the processes of other applications 124b, c, d, which may also be active in the background.

[0108] In process step S6, the customer application 124a is started by the content manager 122. The application 124a then uses the information from the IPC bus 130 and the locally stored data to execute the functions of the user interface 4, 6. In addition to the locally available data, the application 124a can also use information from another server or cloud system 900 to enable extended functions, such as ordering coffee.

[0109] In step S7, the application 124 controls the content and functions of the user interface at the user interface control 121 and, if necessary, the hardware component manager 123.

[0110] In process step S8, the user interface controller 121 controls the display 4 and generates graphical content from the application 124a according to the properties of the display 4, for example dimensions, resolution, etc., whereby the display 4 is connected to the user interface management unit 120.

[0111] In process step S9, the hardware component manager 123, in the example shown, controls the hardware components 6 according to the specifications of the application 124a, taking into account the properties of the hardware components 6. In doing so, the hardware component manager 123, for example, forwards signals from the components 6 to the application 124a.

[0112] The process described above for downloading and saving an application 124a on the one hand and for playing the downloaded application 24a and displaying it, among other things, on the display 4 on the other hand, is only to be understood as an example and serves only to better understand the invention.

[0113] The following are further applications of the invention described by way of example:

[0114] Application example: Long-distance communication

[0115] The technical lifespan of charging stations 1 is considerably longer than the timescale at which communication technologies evolve, especially for charging stations 1 in remote locations that rely on mobile communication technologies.

[0116] The 100 Intermediary and User Interface Management Control Unit can be connected via the 123 Hardware Component Manager to one or more additional communication modules. These modules enable newer GSM standards, such as LTE, 4G, 5G, and LTE-M, in addition to the standard communication standard. WLAN or LoRaWAN communication can also be enabled in addition to or as an alternative to GSM. A single communication module of the 100 Intermediary and User Interface Management Control Unit can handle all communication or be used only as a backup or for bandwidth expansion. For example, the 100 Intermediary and User Interface Management Control Unit can use high-bandwidth communication interfaces such as LTE, 4G, 5G, or Wi-Fi as the primary interface for downloading media content, applications, and / or software updates.For example, backup interfaces such as LTE-M and LoRaWAN can serve as secondary interfaces for status messages for remote maintenance when the primary interface(s) are unavailable. In this scenario, the intermediary and user interface management control unit 100 can receive a hardware reset command for charging station 1 or for the intermediary and user interface management control unit 100 itself via LTE-M or LoRaWAN if charging station 1 is otherwise unreachable.

[0117] To improve hardware reliability, the intermediary and user interface management control unit 100 and the

[0118] User interface management unit 120 with “out-of-band” communication protocols: Control signals that communicate directly with the intermediary and user interface management control unit 100 hardware are reconfigured. Such an “out-of-band” mechanism can be implemented, for example, with technologies like vPro or AMT.

[0119] The intermediary and user interface management control unit 100 can handle all remote communication between the charging station 1 and the components and control systems connected via the hardware component manager 123. This effectively shields the charging station control unit 5 within the charging station 1 and the connected control systems from external interference. The typically wired communication between the charging station control unit 5 and the intermediary and user interface management control unit 100, as well as between the intermediary and user interface management control unit 100 and the human-machine user interface 4, 6, inherently meets higher security standards, since an attack can only occur physically on-site and, in most cases, within the housing of the charging station 1.This allows the Intermediary and User Interface Management Control Unit 100 to offer an operator the ability to secure the cybersecurity of their systems via the Intermediary and User Interface Management Control Unit 100. Short software development cycles and a simple mechanism for deploying new software versions on the Intermediary and User Interface Management Control Unit 100 allow the operator to keep their cybersecurity up to date at all times.

[0120] Application example: Connection problems and offline mode

[0121] Unreliable data connections are one of the biggest problems in the operation of charging stations 1, which are often installed in remote locations. This often limits charging reliability, even though the technical availability of the charging technology and the power grid connection is very stable. The charging station 1 requires and checks its data connection on a case-by-case basis, and especially at the beginning of each charging process. This successful check is a prerequisite for the authentication and payment process, which allows a charging process to be authorized and started for user 3. Due to the direct cable connection between the intermediary and user interface management control unit 100 and the charging station control unit 5, the charging station control unit 5 is always connected to the intermediary and user interface management control unit 100 and therefore always has a data connection.This allows the operator of charging station 1 to implement their own strategy for situations in which the intermediary and user interface management control unit 100 has no data connection. The intermediary and user interface management control unit 100 can support various options, such as a free mode without further verification of customer data, a whitelist mode in which known and accepted customer IDs are stored in the intermediary and user interface management control unit 100, or a cache mode in which the customer IDs are stored at the beginning of the charging process and only checked after the data connection is restored during the billing step. The different strategies represent different compromises between being accommodating to the customer and / orUser 3 on the one hand and the billing risk for the operator on the other hand, which is why, in the best case, the operator should be able to determine the strategy in the event of an interruption of the data connection.

[0122] With the option of connecting a secondary communication interface, the intermediary and user interface management control unit 100 offers operators yet another option: As a secondary interface, the intermediary and user interface management control unit 100 can also connect additional communication modules, such as a LoRaWAN module or an LTE-M module, via the hardware component manager 123. Normally, in the described example, the intermediary and user interface management control unit 100 forwards an authorization request from the charging station control unit 5 to start the charging process via the primary communication interface. However, if the data connection at the primary interface is interrupted, a charging station 1 cannot normally start the charging process without the intermediary and user interface management control unit 100 according to the invention, due to a lack of authorization.However, the intermediary and user interface management control unit 100 according to the invention can request release via the secondary data connection if the primary data connection is interrupted. In order for the charging station control unit 5 to receive release of the charging process within the time windows specified by the charging protocols, the intermediary and user interface management control unit 100 responds to the charging station control unit 5 with a release of the charging process as soon as the intermediary and user interface management control unit 100 detects that the data connection is interrupted. While the charging station 1 or the charging station control unit 5 starts the charging process, the intermediary and user interface management control unit 100 requests release of the process from the charging station management system 700 via the communication module of the secondary interface using the customer ID previously communicated by the charging station control unit 5.The charging station management system 5 also responds to the intermediary and user interface management control unit 100 via the secondary interface. During and after the charging process, the charging station control unit 5 sends the measured values ​​and billing data for the charging process to the intermediary and user interface management control unit 100. The intermediary and user interface management control unit 100 stores this data and sends it to the charging station management system 700 as soon as the primary data connection is re-established.

[0123] Application example: mobile device

[0124] Another way to increase the reliability of charging stations 1 with unreliable data connections involves local communication with a user's mobile device 3. In this example, the intermediary and user interface management control unit 100 can connect a communication module for local communication with mobile devices via the hardware component manager 123, thereby supporting direct NFC or Bluetooth communication with the device. This allows an application on the intermediary and user interface management control unit 100 to communicate directly with applications on the mobile device.For example, if an application is running on the customer's mobile device that is known to the application unit 124 on the intermediary and user interface management control unit 100 and provides trusted data, the application on the intermediary and user interface management control unit 100 can authorize a charging process without a data connection to the charging station management system 700. Through direct communication between the application on the customer's mobile device and an application 124a on the intermediary and user interface management control unit 100, the intermediary and user interface management control unit 100 can also implement customer interface personalization or support discount promotions via a third-party application.For example, customers using a supermarket chain's app could receive a price reduction when charging if they use the supermarket chain's app on their mobile device when starting or ending the charging process.

[0125] Application example with multiple charging stations 1

[0126] The intermediary and user interface management control unit 100 can technically connect multiple charging stations 1 or multiple charging station control units 4 simultaneously. It is not necessary for the intermediary and user interface management control unit 100 to be directly attached to the charging station 1. If the intermediary and user interface management control unit 100 is located at a central point in a larger charging park, it can handle the control and payment functions for multiple charging points. For example, in such a case, the OCPP proxy control can be connected to multiple charging station control units 5 simultaneously. The internal process communication (IPC) can share the events of the various charging points with the user interface management unit 120, which controls the display and customer functions on the display 4.

[0127] The described use case is particularly relevant for AC charging stations, which typically lack a display and card terminal. The intermediary and user interface management control unit 100 allows for the implementation of a central payment terminal without requiring any modifications to the AC charging stations. If the intermediary and user interface management control unit 100 controls an additional display, further customer applications, such as advertising or a digital queue, can also be integrated. Accessibility application example

[0128] Accessibility is a major challenge for charging stations, especially when accessibility requires different or differently installed operating elements at individual charging stations. By separating the customer interface 4, 6, 7 from the charging station 1 using the intermediary and user interface management control unit 100, an operator can freely configure a charging station 1 with a human-machine user interface 7 and, for example, optimize additional operating elements of the human-machine user interface 7 for accessibility without having to modify the charging station 1 itself.

[0129] Additionally, applications with specific user guidance can be installed on the intermediary and user interface management control unit 100. These applications adapt the customer interface precisely to the needs of a particular customer or customer from a specific customer group as soon as that customer is identified. The intermediary and user interface management control unit 100 identifies the customer, for example, via the customer ID during the authentication process or via a mobile device that communicates directly with the intermediary and user interface management control unit 100.

[0130] As soon as user 3 is recognized, the display 4 and the displayed information are adapted to the customer's needs and, for example, are only shown in the lower area, with particularly large font, or greatly simplified and without selection options.

[0131] Application example: Occupancy detection, parking barriers, and charging robots

[0132] To detect whether the parking space belonging to charging station 1 is occupied by a vehicle 2 that is not charging, additional occupancy sensors are necessary. Various technologies exist for this purpose, all of which function best when installed not within charging station 1, but rather in, under, or directly above a parking space. The same applies to parking barriers, which are typically mounted in a parking lot to prevent unwanted vehicles from blocking the space. A charging robot is also located outside the charging station at the same height as the charging port of vehicle 2.

[0133] The 100 intermediary and user interface management control unit enables the integration of these components into the extended charging process for a seamless customer experience. The components in the parking lot can be connected via wired or local wireless communication (Bluetooth, WLAN, etc.). This allows the 113 message and charging event manager to include the parking lot status in the charging station events. The OCPP proxy reports the parking lot occupancy to the 700 charging station management system. Using the roaming functionalities of charging apps, customers can then find out that a parking space is occupied even before they arrive.

[0134] The parking barrier and the charging robot can be controlled by the intermediary and user interface management control unit 100. The intermediary and user interface management control unit 100 receives information about a new charging process, for example, from the charging station management system 700 or via its local Bluetooth interface, with which the customer's mobile device communicates. As soon as the intermediary and user interface management control unit 100 has confirmed that the correct vehicle is approaching, it opens the parking barrier to allow the parking process. After the charging process is complete and the vehicle 2 has departed, the intermediary and user interface management control unit 100 uses the hardware component manager 123 to close the parking barrier again.

[0135] The charging robot can be controlled analogously. As soon as the charging station management system 700 or a local near-field communication (e.g., a Bluetooth interface or ultra-wideband technology) or other means signals that the charging process can begin, the intermediary and user interface management control unit 100, via the hardware component manager 123, commands the charging robot to insert the charging plug into the charging socket. Similarly, after charging is complete, the intermediary and user interface management control unit 100 commands the charging robot to unplug so that vehicle 2 can continue driving. It is irrelevant whether the intermediary and user interface management control unit 100 receives the information about the end of charging from the charging station control unit 5, the customer's mobile device, or the charging station management system 700.In all cases, the message and load event manager 113 forwards the event via the internal process communication IPC to the hardware component manager 123, which then issues the hardware command.

[0136] Application example: Charging park coordination

[0137] A special case of integrating additional control systems in the hardware component manager 123 is the integration of further intermediary and user interface management control units 100 of other charging stations 1 in a larger charging park. If several charging stations 1 are installed at a location, there is a need to coordinate the charging stations 1 with each other. This coordination can be achieved via one or more intermediary and user interface management control units 100, each connected to one or more charging station control units 5. The most important function requiring coordination of the charging stations 1 is load management, which prevents the charging stations 1 from consuming more electricity in total than the power grid at the location can supply.

[0138] The intermediary and user interface management controller(s) 100 operating at the site control the charging power consumed by the connected charging stations 1 for site load management via OCPP proxy control. Upon commissioning a load management application or at another time, the charging station management system 700 or the charging station content management system 800 determines which intermediary and user interface management controller 100 at the site assumes the coordination role for load management. This intermediary and user interface management controller 100 coordinates the load management of all charging points by regularly, for example,The system queries the current charging power and the desired charging power of the charging vehicles 2 every few seconds, then uses an algorithm to determine the maximum charging power for each charging point and communicates this information to the charging points via the hardware component manager 123.

[0139] The load management application can be configured with various algorithms such as "first-in-first-served," "first-in-last-served," "equal share," or individual prioritization of vehicles. By implementing the load management algorithm as application 124a in the application framework 125 of the intermediary and user interface management control unit 100, the operator can customize the function according to their needs and, for example, integrate information from other systems. This could include, for instance, data on current energy prices or, in the case of a larger fleet, the route planning of arriving vehicles.

[0140] Another function for which the coordination of all charging points at a location can be relevant is the digital queue and reservation function. This function manages the distribution of available charging points when a charging park is fully occupied. Similar to the load management function, the intermediary and user interface management control unit 100 can offer the option of implementing this function in applications on the intermediary and user interface management control units 100 at a location. The coordination role is assigned to one intermediary and user interface management control unit 100. This unit allocates available charging points to waiting drivers or vehicles.The queue algorithm and the integration of any reservations can be designed by the operator using all the information available to applications 124a, b, c, d on the intermediary and user interface management control unit 100.

[0141] In digital queues, communication with waiting customers can be of particular importance. In addition to communication via the display of the charging station, the intermediary and user interface management control units can use the extended interfaces of the charging stations to inform the customer via light signals and sounds that a charging process is finished and the charging point should be released, and to notify the next customer in the queue via a local radio connection (e.g.,Bluetooth) to inform the customer's mobile device which charging point they can go to next; to signal to the customer whose turn it is which charging point is free via light and sound signals at charging station 1; to display the status of all charging points and the queue via a central screen; to give customers the opportunity to join the digital queue via a local radio connection to mobile devices; and / or to give customers the opportunity to join the digital queue via various input options of the customer interfaces 7 at charging stations 1.

[0142] The embodiments of the invention described above and the application examples described are not to be understood as limiting the invention. They merely serve to improve understanding of the invention and can be combined in whole or in part, provided that no technical contradictions result.

[0143] Reference symbol list

[0144] 1 charging station

[0145] 2 electric vehicles

[0146] 3 users

[0147] 4 Display, human-machine user interface with display 5 Charging station control unit

[0148] 6 Hardware component (not used for charging in the strict sense)

[0149] 7 Customer interface

[0150] 100 Intermediary and User Interface Management Control Unit

[0151] 101 Firewall

[0152] 110 Intermediary unit, OCPP proxy control

[0153] 111 OCPP server

[0154] 112 OCPP Client

[0155] 113 Message and Load Event Manager

[0156] 120 User Interface Management Unit

[0157] 121 User Interface Control UIC

[0158] 122 Content Managers

[0159] 123 Hardware Component Manager

[0160] 124 application units

[0161] 124a Application 1

[0162] 124b Application 2

[0163] 124c Application 3

[0164] 124d Application 4

[0165] 125 isolated software environment, application framework

[0166] 126 local storage

[0167] 130 IPC bus

[0168] 700 charging station management system, backend

[0169] 800 charging station content management system

[0170] 900 third-party servers

[0171] 901 Data source

[0172] 1000 systems for charging electric vehicles

[0173] 1001 external area

[0174] 1002 Area of ​​the charging station

Claims

Patent claims 1. A system for charging electric vehicles, comprising: a charging station for charging an electric vehicle, comprising: a charging interface for charging an electric vehicle, a human-machine user interface with a display, a charging station controller for controlling the charging process, a charging station management system for managing and monitoring the charging station, which forms the backend system for the charging station, and an intermediary and user interface management controller with the functionalities of an industrial PC, comprising an intermediary unit and a user interface management unit coupled together, wherein the intermediary and user interface management controller is interposed between the charging station controller and the charging station management system, and wherein the intermediary unit is functionally configured as a proxy controller.so that the intermediary and user interface management control unit can communicate with the charging station management system like a charging station via the intermediary unit, and can communicate with the charging station like a charging station management system, and wherein the intermediary and user interface management control unit is configured to control the display of the human-machine user interface of the charging station via the user interface management unit.

2. System according to claim 1, wherein the user interface management unit is not configured to control the charging station control unit, and / or wherein the charging station control unit is not configured to control the display of the human-machine user interface of the charging station.

3. System according to one of the preceding claims, wherein the intermediary unit functionally comprises an OCPP server configured to communicate with the charging station controller via OCPP messages, and wherein the intermediary unit functionally includes an OCPP client which is configured to communicate with the charging station management system using OCPP messages, wherein the architecture of the intermediary unit is designed such that an OCPP client process and an OCPP server process can run independently of each other.

4. System according to one of the preceding claims, wherein the user interface management unit has an IPC bus by means of which processes of the user interface management unit communicate with each other.

5. System according to any of the preceding claims, wherein the intermediary unit comprises a message and load event manager configured to couple the proxy control of the intermediary unit with processes of the user interface management unit.

6. System according to claim 5, wherein the message and load event manager is configured to translate information from OCPP messages into events that can be made available to the processes of the user interface management unit via internal process communication (IPC).

7. System according to one of claims 5 to 6, wherein the message and load event manager is configured to generate IPC OCPP messages based on events of the internal process communication.

8. System according to claims 3 and 5, wherein the OCPP server is configured to interpret the OCPP messages and pass them to the message and load event manager, and to receive OCPP messages from the message and load event manager, and / or wherein the OCPP client is configured to interpret the OCPP messages and pass them to the message and load event manager, and to receive OCPP messages from the message and load event manager.

9. System according to any of the preceding claims, wherein the user interface management unit comprises a user interface controller configured to control the human-machine user interface of the charging station.

10. System according to the preceding claim, wherein the system further comprises an external charging station content management system, and wherein the user interface management unit further comprises a content manager, wherein the content manager is configured to download content and / or applications from the external charging station content management system, and wherein the content manager is further configured to control processes in the user interface control based on the downloaded content and / or applications.

11. System according to the preceding claim, wherein the user interface management unit further comprises an application unit in which applications can be stored or are stored, which can be made available at the human-machine user interface of the charging station and whose contents can be displayed, in particular, on the display of the human-machine user interface of the charging station.

12. System according to the preceding claim, wherein the application unit is designed as an isolated software environment, so that applications can be used within this application unit independently of software on the charging station and independently of the charging station management system.

13. System according to the preceding claim, wherein the application unit is configured to access a third-party server via remote communication.

14. System according to one of the preceding claims, wherein the user interface management unit further comprises a hardware component manager configured to control a hardware component of the charging station that is not required for the charging process of the electric vehicle.

15. System according to the preceding claim, wherein the charging station as a hardware component that can be controlled by means of the hardware component manager includes at least one element from the following list: light element, loudspeaker, controllable and / or movable parking obstacle, QR code scanner, payment terminal, camera, long-distance communication module, short-distance communication module.

16. System according to any of the preceding claims, wherein the intermediary and user interface management control unit has a firewall configured to protect the intermediary and user interface management control unit against interference during remote communication.

17. System according to one of the preceding claims, further comprising means for remote communication between the charging station and the charging station management system; and / or further comprising means for remote communication between the intermediary and user interface management control unit on the one hand and the charging station management system and / or an external charging station content management system and / or a third-party server on the other hand.

18. System according to one of the preceding claims, wherein the intermediary and user interface management control unit is arranged in or on the housing of a charging station or in or on the housing of a charging point of a charging station.

19. System according to any of the preceding claims, wherein the industrial PC comprises: at least one processor with a processing power sufficient for handling modern multimedia applications; a graphics unit that supports the display of modern multimedia applications; a main memory with a capacity sufficient for the parallel execution of multiple applications; and a hard disk with a capacity for local storage of content and / or applications.

20. System according to any of the preceding claims, wherein the intermediary and user interface management control unit has the following communication interfaces: a communication interface for communication with the charging station control unit; a communication interface for communication with the charging station management system; a communication interface for communication with the display of the human / machine user interface of the charging station; and a communication interface for communication with the charging station content management system.

21. System according to the preceding claim, wherein the intermediary and user interface management control unit further comprises: at least one communication interface for communication with at least one server of a third party; and / or at least one communication interface for communication with at least one hardware component of the charging station that is not required for the charging process of an electric vehicle.

22. Intermediary and user interface management control unit adapted for use in the system according to any of the preceding claims.

23. Charging station with the intermediary and user interface management control unit according to the preceding claim.

24. System combination with the intermediary and user interface management control unit according to claim 22 and with an external charging station. Content management system.

Images