EP3921203A1 - Système de charge pour charger des véhicules électriques - Google Patents

Système de charge pour charger des véhicules électriques

Info

Publication number
EP3921203A1
EP3921203A1 EP20702627.9A EP20702627A EP3921203A1 EP 3921203 A1 EP3921203 A1 EP 3921203A1 EP 20702627 A EP20702627 A EP 20702627A EP 3921203 A1 EP3921203 A1 EP 3921203A1
Authority
EP
European Patent Office
Prior art keywords
charging
microservice
service
charging system
implemented
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP20702627.9A
Other languages
German (de)
English (en)
Inventor
Stephan CATER
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CCS Abwicklungs AG
Original Assignee
Innogy SE
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Innogy SE filed Critical Innogy SE
Publication of EP3921203A1 publication Critical patent/EP3921203A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60L—PROPULSION OF ELECTRICALLY-PROPELLED VEHICLES; SUPPLYING ELECTRIC POWER FOR AUXILIARY EQUIPMENT OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRODYNAMIC BRAKE SYSTEMS FOR VEHICLES IN GENERAL; MAGNETIC SUSPENSION OR LEVITATION FOR VEHICLES; MONITORING OPERATING VARIABLES OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRIC SAFETY DEVICES FOR ELECTRICALLY-PROPELLED VEHICLES
    • B60L53/00—Methods of charging batteries, specially adapted for electric vehicles; Charging stations or on-board charging equipment therefor; Exchange of energy storage elements in electric vehicles
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60L—PROPULSION OF ELECTRICALLY-PROPELLED VEHICLES; SUPPLYING ELECTRIC POWER FOR AUXILIARY EQUIPMENT OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRODYNAMIC BRAKE SYSTEMS FOR VEHICLES IN GENERAL; MAGNETIC SUSPENSION OR LEVITATION FOR VEHICLES; MONITORING OPERATING VARIABLES OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRIC SAFETY DEVICES FOR ELECTRICALLY-PROPELLED VEHICLES
    • B60L53/00—Methods of charging batteries, specially adapted for electric vehicles; Charging stations or on-board charging equipment therefor; Exchange of energy storage elements in electric vehicles
    • B60L53/30—Constructional details of charging stations
    • B60L53/305—Communication interfaces
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
    • Y02T10/00—Road transport of goods or passengers
    • Y02T10/60—Other road transportation technologies with climate change mitigation effect
    • Y02T10/70—Energy storage systems for electromobility, e.g. batteries
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
    • Y02T10/00—Road transport of goods or passengers
    • Y02T10/60—Other road transportation technologies with climate change mitigation effect
    • Y02T10/7072—Electromobility specific charging systems or methods for batteries, ultracapacitors, supercapacitors or double-layer capacitors
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
    • Y02T90/00—Enabling technologies or technologies with a potential or indirect contribution to GHG emissions mitigation
    • Y02T90/10—Technologies relating to charging of electric vehicles
    • Y02T90/12—Electric charging stations
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
    • Y02T90/00—Enabling technologies or technologies with a potential or indirect contribution to GHG emissions mitigation
    • Y02T90/10—Technologies relating to charging of electric vehicles
    • Y02T90/14—Plug-in electric vehicles
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
    • Y02T90/00—Enabling technologies or technologies with a potential or indirect contribution to GHG emissions mitigation
    • Y02T90/10—Technologies relating to charging of electric vehicles
    • Y02T90/16—Information or communication technologies improving the operation of electric vehicles

Definitions

  • the application relates to a charging system for charging electric vehicles, comprising at least one back-end system with at least one charging control application, set up to control a plurality of at least one
  • the application also relates to a front-end system for a charging system and a method for operating a charging system.
  • Known charging systems include a backend system and usually a large number of charging stations.
  • a charging station is set up for charging electric vehicles.
  • a charging station can be used in a conventional manner via the required
  • Charging technology and at least one charging connection like a fixed
  • Charging cable During a charging process, electrical power can then be exchanged between the charging station and an electric vehicle connected via a charging cable.
  • an electrical storage device e.g.
  • a loading control application is implemented in the jaw system, for example on a processing unit such as a server.
  • a processing unit such as a server.
  • a charge control application is the eOperate system from Innogy SE.
  • Implemented charging system services that are required when operating a charging system and are used, for example, as part of a charging process at a charging station.
  • an authentication service, a load management service, a payment service, a software update service, etc. can be implemented monolithically as charging system services in the charging control application.
  • Such a charging control application can in particular be used by a large number of charging stations (simultaneously). This can result in a significant temporary load on the charging control application, even if this is only due to a high load on a specific charging system service. This then requires a considerable scaling of the entire charge control application.
  • Charging system service of the charging control application leads to a temporary failure of the entire charging control application.
  • the application is therefore based on the object of providing a charging system for charging electric vehicles which at least reduces the downtime of the charging system and in particular improves the scalability of the charging control application.
  • the task is achieved by a charging system for charging
  • the charging system comprises at least one back-end system with at least one charging control application.
  • the charging control application is set up to control a plurality of charging stations that can be connected to the backend system via at least one communication network.
  • the backend system there is a first charging system service
  • Charging control application implemented in the form of a first microservice. At least one further charging system service is in the backend system
  • Load control application implemented in the form of another microservice.
  • the downtime of a charging system is at least reduced and the scalability of the charging control application is improved by implementing the at least two (different) charging control services of the charging control application in the form of microservices.
  • a first microservice can be maintained and thus temporarily not available, while the at least one additional microservice can is still available and can be used.
  • microservices can be scaled independently of one another.
  • the charging system comprises at least one backend system.
  • the backend system comprises at least one physical processing unit (e.g. in the form of a server), preferably a plurality of distributed physical processing units (e.g. in the form of networked physical processing units).
  • a charging control application in the form of by the processing unit (in particular at least one processor of the
  • Computing unit executable software implemented.
  • the charging system comprises a plurality of
  • the charging station comprises at least one charging connection configured to deliver electrical power.
  • the charging connection can preferably also be set up to receive electrical power.
  • the charging connection can in particular be an electrical interface, for example in the form of a firmly attached charging cable with a charging plug or a charging socket or in the form of a charging plug or a charging socket for connecting a separate charging cable (e.g. a charging plug receptacle,
  • a firmly attached charging cable is to be understood in particular to mean that a user cannot separate the charging cable from the charging device without destroying it.
  • the charging station can comprise a charging device, which can have components in a conventional manner in order to enable a current flow from a power source (for example a public power grid, energy generator, etc.) via the charging connection and a charging cable.
  • a power source for example a public power grid, energy generator, etc.
  • an electric vehicle in particular its electrical energy store, can be charged (or discharged).
  • an electric vehicle is to be understood as a vehicle which can be operated at least partially electrically and which includes a rechargeable electrical storage device (for example a traction battery).
  • the charging device can be integrated in the charging station or designed as a “wallbox”. In particular, the charging device can be part of the charging station.
  • the charging device, in particular the components or the charging technology can also be integrated in a wall or a floor. It goes without saying that a bidirectional current or power transmission can take place via the charging cable and the charging technology of the charging device.
  • the charge control application according to the application comprises at least two
  • the charging system services are used in particular to operate the charging system.
  • a charging system service is in particular made available to other entities and can be used or claimed by them. In other words, a certain functionality of the charging control application is mapped by a charging system service.
  • An authentication service can be used as charging system services
  • Billing service compliant with calibration law etc. must be implemented in the charging control application.
  • At least two charging system services are formed in the form of microservices.
  • the charging system service is (largely) decoupled from the at least one other charging system service implemented as a microservice and, in particular, performs its corresponding (individual) task independently of the other microservices.
  • microservices By using microservices, a modular structure of the
  • the first microservice can have a first interface with a first
  • Microservice can have another interface with another
  • each microservice can have a (data) interface with a communication address that is preferably unique in the charging system.
  • the associated charging system service can be used (or controlled) via the interface.
  • a standard interface can be provided as the interface.
  • an interface can hide the implementation details of the respective microservice. This makes it possible to implement the
  • the first microservice can be implemented in a first programming language and the further microservice in a further programming language.
  • the respective charging system service can nevertheless be used in a simple manner by a further entity due to the interface provided in each case.
  • the first microservice can be implemented on at least one first physical computing unit.
  • the first microservice can also run on a
  • a plurality of first computing units can be implemented.
  • the at least one further microservice can be implemented on at least one further physical computing unit independent of the at least one first computing unit.
  • the other microservice can also be based on a number of other
  • Microservice be implemented, while another charging system service, in which no safety-relevant data is processed, is implemented on another
  • Security level can be implemented as a further microservice.
  • the safety effort in the charging system can be reduced overall.
  • unauthorized access to the security-relevant data is made more difficult because of the separate processing units.
  • the first physical computing unit can be independent of the further physical
  • Computing unit (and preferably vice versa) be scalable.
  • an increase in resources to increase performance can be individual for each microservice
  • Charge control application must be scaled up, as is required in a monolithic application according to the prior art.
  • the backend system can comprise at least one load control module (for example in the form of a load balancer).
  • the load control module can be set up to record the (instantaneous) load of at least one physical processing unit and / or at least one microservice.
  • the load control module can be configured to scale the at least one physical one
  • Computing unit (and / or the corresponding microservice) based on the recorded (instantaneous) (computing) load of the at least one
  • Scaling is to be understood in particular as increasing or decreasing the performance of a physical computing unit and / or a microservice.
  • microservices that have high load fluctuations occur, be implemented in a cloud.
  • a cloud provides a high level of scalability.
  • the in the backend system can be in the form of
  • Microservices implemented charging system services are made available to other entities for use.
  • an entity can use the at least two charging system services to complete a specific task or several specific tasks.
  • the charging system can comprise at least one front-end system.
  • An entity can, for example, comprise or form the front-end system.
  • the front-end system can preferably include at least one routing module.
  • the routing module can be set up to cause a first service request to be sent to the first microservice for the use of the first charging system service, based on a received charging action request and a charging action assignment table
  • Routing module be set up to cause a further service request to be sent to the at least one further microservice for the use of the at least one further charging system service, based on a received charging action request and the charging action assignment table.
  • the charging action request can, for example, be based on a user action and require the execution of a specific task or functionality, which is implemented by a charging system service in the backend system, which is mapped as a microservice
  • a user can initiate a loading process which, for example, initially requires an authentication service to be carried out. If the front-end system detects a corresponding charging action request, the routing module can generate a corresponding service request, in the present example an authentication service request, in particular and its
  • Authentication service is implemented, effect.
  • a loading action assignment table can be stored in the front-end system.
  • Charging action requests and the charging system services required for this must be saved.
  • the respective (one-to-one) communication addresses of the respectively assigned interfaces of the microservices can additionally be stored in a charging action assignment table. This enables the routing module to send a service request to the interface of the associated (correct) charging system service or microservice.
  • the first service request by at least a first
  • Data message be formed, comprising at least the first communication address (in the header of the service message) and service user data.
  • an authentication service request (especially in the header of the message) can contain the communication address of the interface of the
  • Authentication service and, as service user data, at least the authentication data to be checked e.g. user name and / or password and / or
  • Data messages can be formed and in particular sent to
  • the authentication service can then check the authentication data received via the assigned interface in a conventional manner (regardless of other microservices).
  • the authentication data can be stored with (in a storage unit of the physical processing unit on which the
  • Authentication service is implemented as a microservice
  • the first charging process is enabled, in particular by sending a
  • Release message is effected to the corresponding charging station to be released. If the result of the check is negative, the charging process is blocked,
  • a blocking message is transmitted to the charging station or no release message is transmitted.
  • other charging system services (described above) can be carried out in a conventional manner.
  • At least one charging station can have the front-end system, which is formed in particular from hardware and / or software.
  • the charging system can comprise at least one mobile user terminal. The at least one mobile user terminal can advise the front-end system, in particular from
  • a front-end system can preferably have at least one connection to at least one user interface (e.g. keyboard, keys, touch display, RFID module, NFC module, card module, etc.) and / or at least one connection to at least one communication module (e.g. controller with antenna ) have and / or comprise a user interface and / or a communication module.
  • at least one user interface e.g. keyboard, keys, touch display, RFID module, NFC module, card module, etc.
  • at least one communication module e.g. controller with antenna
  • the front-end system comprises at least one communication connection to a user interface, set up to generate at least one charging action request.
  • a previously described charging action request can be generated or received based on a user input.
  • a charging process can be initiated as a charging action request via the user interface, which (conventionally) requires the completion of at least one charging system service or a charging system task.
  • the front-end system comprises at least one (in particular previously described) routing module.
  • the routing module is set up to cause a first service request to be sent to a first microservice to use a first charging system service, based on a received charging action request and a charging action allocation table, the first charging system service of a charging control application being implemented in a back-end system in the form of the first microservice.
  • the front-end system can be installed, for example, as an executable application (app) on a mobile user terminal and can be executed by the latter.
  • the front-end system can also be installed, for example, as an executable application in a charging station and can be executed by the latter.
  • a mobile user terminal is in particular a smartphone
  • Yet another aspect of the application is a method for operating a charging system comprising a backend system with at least one
  • Charge control application configured to control a plurality of over
  • At least one communication network can be connected to the backend system
  • Charging stations with a first (in particular previously described) charging system service of the charging control application being implemented in the form of a first microservice in the backend system.
  • the procedure includes:
  • Charging system can be used.
  • Fig. 1 is a schematic view of an embodiment of a
  • Fig. 2 is a schematic view of a further embodiment of a
  • FIG. 3 shows a diagram of an exemplary embodiment of a method according to the present application.
  • FIG. 1 shows a schematic view of an exemplary embodiment of a
  • the charging system 100 comprises a backend system 102 and a plurality of charging stations 104.
  • the charging stations 104 can be connected to the backend system 102 via a (wireless and / or wired) communication network 118.
  • a charging station 104 has at least one charging connection that has a
  • Charging cable 108 can be coupled to a charging connection of an electric vehicle 106 in order to charge the electric vehicle 106 or its rechargeable battery.
  • the backend system 102 is formed by at least one physical processing unit (e.g. a server). At least one charging control application 103 is implemented on the at least one processing unit. The (modular) charging control application 103 is set up to control a plurality of charging stations 104 that can be connected to the backend system 102 via the at least one communication network 118. This is to be understood in particular as the charging control application 103 providing at least two (different) charging system services 110, 112 for the operation of the Charging system 100 provides.
  • a charging system service 110, 112 is set up, in particular, to take over (precisely) a specific task of the charging system 100 and in particular to carry it out.
  • the first charging system service 110 is an authentication service 110 and the further charging system service 112 is a load management service 112. It goes without saying that further (or different)
  • Charging system services such as a payment service, a software update service
  • Billing service compliant with calibration law, etc. can be implemented in the charging control application.
  • the first charging system service 110 is the
  • the charging control application 103 is implemented in the form of a first microservice 110 and at least the at least one further charging system service 112 of the charging control application 103 is implemented in the backend system 102 in the form of a further microservice 112.
  • precisely one first interface 114 with a first communication address is clearly assigned to the first microservice 110.
  • the first microservice 110 can only be used via the first interface 114.
  • a further interface 116 with a further communication address can be assigned to the at least one further microservice 112.
  • the further microservice 112 can only be used via the further interface 116.
  • Each interface 114, 116 preferably has one that is unique in the charging system 100
  • a charging station 104 can preferably be a
  • Front end system 120 include.
  • the front end system 120 includes, in particular, a routing module 124.
  • a front end system 120 can use a
  • User interface 122 e.g. a keypad, a near-field interface (e.g. NFC, RFID or Bluetooth module) and a communication module 126 or at least be connectable to a user interface 122 and a communication module 126 via at least one connection each.
  • the mode of operation will be described below.
  • FIG. 2 shows a schematic view of a further exemplary embodiment of a charging system 200 according to the present application.
  • the first microservice 210 (and the associated interface 214) is implemented in the present exemplary embodiment on at least one first physical computing unit 230 and can be executed by this.
  • the further microservice 212 (and the associated interface 216) is implemented in the present exemplary embodiment on at least one further physical computing unit 232 and can be executed by this.
  • the two physical computing units 230, 232 are in particular independent or decoupled from one another.
  • the backend system 202 in the present case comprises a load control module 234.
  • the load control module 234 is set up in particular to detect the
  • Load control module 234 can also be set up to scale at least the first physical computing unit 230 and / or the first microservice 210 and the further physical computing unit 232 and / or the further microservice 212, based on the detected (instantaneous) load on the at least one physical computing unit and / or the at least one microservice.
  • a front-end system 220 has in each case a charging action assignment table 236.
  • a further front-end system 240 having a routing module 244 and a charging action assignment table 248, is implemented on a mobile user terminal 238 (e.g. a smartphone).
  • the front-end system 240 can in particular be an application (app) that can be installed on the user terminal 238.
  • the front-end system 240 comprises at least one connection to at least one user interface 242 (e.g. touch display of the terminal 238), set up to generate at least one charging action request, and preferably at least one connection to one
  • a communication module 226, 248 is set up in particular to communicate with the backend system 202 via the communication network 218.
  • FIG. 3 shows a diagram of an exemplary embodiment of a method according to the present application.
  • the front-end system 220, 238, in particular via the at least one user interface 222, 242 can receive a charging action request.
  • the following is an example for the better
  • a charging process initiation request which can be based in particular on at least one user action by which the user would like to start a charging process at a charging station 204 for charging his electric vehicle.
  • receipt of such a charging action request can be detected.
  • the routing module 224, 244 can receive the
  • the routing module 224, 244 can determine which at least one charging system service requires the charging operation initiation request.
  • Loading action allocation table 236, 248 can be stored in a simple manner, the routing module 224, 244 can determine the at least one required loading system service. It goes without saying that further charging system services, for example a load management service, etc., are required in the case of a charging process initiation request can. For the sake of clarity, only the implementation of the authentication service is described in more detail in the present example.
  • the routing module 224, 244 can preferably create at least one service request, in this case an authentication service request,
  • the data message can be the communication address of the first interface 214 implemented as the first microservice 210 in the backend system 202
  • Authentication service 210 have. In particular, in the
  • Load action allocation table 236, 248 the communication address associated with the authentication service must be stored.
  • a data message can receive at least part of the service payload data
  • the authentication data can be received via the user interface 222, 242, for example.
  • the routing module 224, 244 sends the
  • Authentication service request in particular the at least one data message, via the communication network 218 to the corresponding microservice 210 or the interface 214 associated with this microservice 210.
  • the routing module 224, 244 can control the at least one communication module 226, 246 accordingly and send the at least one Effect data message.
  • the microservice 210 can be executed, in particular based on the received user data in the form of the user's authentication data.
  • the first microservice 210 can be executed by the computing unit 230.
  • the authorization of the user to carry out a loading process based on the received authentication data and user authentication data that is to say in particular previously stored authentication data from registered Users to be checked.
  • user accounts or corresponding user data can be stored in the processing unit 230 and / or a database to which the
  • Computing unit 230 or microservice 210 can access, be stored.
  • User name and password While other user data, such as account data, which are required, for example, for billing the charging process, but not for an authentication process, are not in the database of the processing unit 230 and / or the database to which the processing unit 230 or the microservice access 210 can access are stored.
  • the check in step 304 can, for example, compare the received user name and the associated password with the stored ones
  • step 305 microservice 210 can in particular send a release message to release the charging process to the corresponding charging station 204 in the event of a positive
  • microservice 210 and / or the physical computing unit 230 can be recorded by load control module 234.
  • the microservice 210 and / or the physical computing unit 230 can be designed to be scalable.
  • load control module 234 can scale the load or load on microservice 210 and / or physical computing unit 230
  • Microservice 210 and / or the physical processing unit 230 an increase or decrease in the performance of the microservice 210 and / or the physical processing unit 230.

Landscapes

  • Engineering & Computer Science (AREA)
  • Power Engineering (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)

Abstract

L'invention concerne un système de charge (100, 200) pour charger des véhicules électriques (108), comprenant au moins un système de gestion (102, 202) comprenant au moins une application de commande de charge (103, 203), configurée pour la commande d'une pluralité de stations de charge (104, 204) pouvant être connectées avec le système de gestion (102, 202) à travers au moins un réseau de communication (118, 218), un premier service de système de charge (110, 210) de l'application de commande de charge (103, 203) étant mis en œuvre dans le système de gestion (102, 202) sous la forme d'un premier micro-service (110, 210), et au moins un autre service de système de charge (112, 212) de l'application de commande de charge (103, 203) étant mis en œuvre dans le système de gestion (102, 202) sous la forme d'un autre micro-service (112. 212).
EP20702627.9A 2019-02-06 2020-01-29 Système de charge pour charger des véhicules électriques Withdrawn EP3921203A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102019102890.6A DE102019102890A1 (de) 2019-02-06 2019-02-06 Ladesystem zum Laden von Elektrofahrzeugen
PCT/EP2020/052119 WO2020160972A1 (fr) 2019-02-06 2020-01-29 Système de charge pour charger des véhicules électriques

Publications (1)

Publication Number Publication Date
EP3921203A1 true EP3921203A1 (fr) 2021-12-15

Family

ID=69375360

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20702627.9A Withdrawn EP3921203A1 (fr) 2019-02-06 2020-01-29 Système de charge pour charger des véhicules électriques

Country Status (3)

Country Link
EP (1) EP3921203A1 (fr)
DE (1) DE102019102890A1 (fr)
WO (1) WO2020160972A1 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8421592B1 (en) * 2008-10-15 2013-04-16 Sprint Communications Company L.P. Mediation of electric vehicle charging by wireless network provider
DE102008037576A1 (de) * 2008-11-21 2010-06-10 EnBW Energie Baden-Württemberg AG Computergestütztes Verfahren zur Optimierung der Energienutzung
US20130046660A1 (en) * 2011-08-16 2013-02-21 Richard Lowenthal Taxable Fringe Benefit Accounting for Electric Vehicle Charging Service

Also Published As

Publication number Publication date
WO2020160972A1 (fr) 2020-08-13
DE102019102890A1 (de) 2020-08-06

Similar Documents

Publication Publication Date Title
EP2640596B1 (fr) Dispositif de charge conçu pour charger un accumulateur de véhicule
DE102018209761A1 (de) Verfahren zur Konfiguration eines Ladesystems und Ladesystem zum Laden des elektrischen Energiespeichers eines Fahrzeugs
WO2020164909A1 (fr) Procédé pour faire fonctionner un système de charge
DE102015016320A1 (de) Verfahren zur Verwaltung zumindest eines Parkplatzes
DE102016002945B4 (de) Kraftfahrzeug und Verfahren zum Bereitstellen mehrerer Online-Fahrzeugfunktionalitäten
DE102017202024B4 (de) Verfahren zum Koppeln eines portablen, mobilen Nutzergeräts mit einem in einem Kraftfahrzeug verbauten Fahrzeuggerät sowie Servervorrichtung
DE102009009310A1 (de) Kommunikation und Identifizierung zwischen einem Kraftfahrzeugbenutzergerät mit Head Unit und davon entfernt gelegener Vorrichtung
EP3921203A1 (fr) Système de charge pour charger des véhicules électriques
DE102018123601A1 (de) Mehrfachladeanschlussvorrichtung für Elektrofahrzeuge
EP3626514B1 (fr) Station de recharge
DE102019107071A1 (de) Ladestation zum Laden von Elektrofahrzeugen
DE102020107365A1 (de) Verfahren und System zum Freischalten eines elektrischen Ladevorgangs für ein Kraftfahrzeug sowie Servervorrichtung
DE102018201672A1 (de) Verfahren und System zum Nachweis eines Ladevertrags eines Benutzers zum Freigeben eines Ladevorgangs zum Laden eines Elektrofahrzeugs an einer Ladeinfrastruktur
EP3585028A1 (fr) Procédé de connexion d'un terminal à une infrastructure de calcul pouvant être connectée au réseau
WO2020164815A1 (fr) Procédé pour faire fonctionner un système de charge
EP4072180A1 (fr) Procédé d'autorisation d'un processus de charge à un point de charge
DE102018132979A1 (de) Abgesichertes und intelligentes Betreiben einer Ladeinfrastruktur
EP3328681B1 (fr) Système et procédé pour l'alimentation en énergie d'un consommateur électrique et station d'énergie
EP3898317A1 (fr) Système de charge pour véhicule
DE102019111273A1 (de) Verfahren zum Starten eines Ladevorgangs an einer Ladestation
WO2018153641A1 (fr) Dispositif de charge conçu pour charger un véhicule automobile à entraînement électrique avec accès à un réseau de données et procédé pour faire fonctionner un tel dispositif de charge
DE102016111858A1 (de) DLMS-Server, DLMS-Client und Verfahren für die DLMS-Kommunikationssicherheit
DE102022201082A1 (de) Verfahren zu einer eindeutigen Identifikation eines batterieelektrisch betriebenen Kraftfahrzeugs an einer Ladestation
DE102021121127A1 (de) Verfahren zum Betreiben eines Netzmanagementsystems für ein lokales Energienetz, Computerprogrammprodukt sowie Netzmanagementsystem
DE102021213161A1 (de) Ladesystem

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210713

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: COMPLEO CHARGING SOLUTIONS AG

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20230801