Electric Vehicle Charging Certification and Verification

Abstract

A computing device, system, and method for verifying charging of an electric vehicle EV is provided. An internet-based communication, such as an API, receives encrypted energy measurements that authenticate and verify the amount of energy charged by the electric vehicle EV from the EV charging station CS. An internet-based communication, such as a web server, transmits these energy measurements for presentation to a user who has charged the EV at the CS, and the aforementioned energy measurements are configured to be output to the user by an internet-based user interface. A charging system compatible with regulations such as Eichrecht can be conveniently updated to existing or new parts of the charging system without a separate or manual authentication process.

Description

[Technical Field]

[0001] Various illustrative embodiments relate generally to the field of electric vehicle charging, and more particularly, to verification and authentication of electric vehicle charging. [Background technology]

[0002] The charging station CS is used to charge electric vehicles (EV). The CS is remotely controlled by the charging station management system CSMS. The Open Charging Point Protocol (OCPP) is the communication protocol between the CS and the CSMS.

[0003] Eichrecht is a German law that specifies how CS energy usage must be measured in an authenticated and trustworthy way. According to Eichrecht, encrypted energy measurements, so-called "signed meter values" (SMV), must be provided to customers so that they can verify that they are being billed for the correct amount of energy.

[0004] Eichrecht recognizes that only KWh consumption-based billing is fair. Therefore, purely time-based charges (per-minute billing) and flat-rate session charges per charging process (per-session billing) are not permitted. Eichrecht only uses fully regulated calibration and end-to-end data security of charging data. This means that CSs must have fully calibrated KWh measurement meters and guarantee users reliable transactions, in line with legal requirements.

[0005] A typical way to meet the Eichrecht regulation is to send customers a receipt or invoice for charges, usually via email or paper invoice. This receipt or invoice includes the SMV for each charge transaction. After customers receive the receipt with the SMV, they can use transparency software to verify that the correct amount was charged.

[0006] However, in order to send a receipt, the customer must have a registered customer account that includes contact information so that the charging operator knows where the receipt or invoice can be sent.

[0007] A payment terminal (PT) is a traditional fuel chain setup. Figure 1 shows a fuel pump (1), a PT (2), and a printed or electronic receipt (3). PTs are becoming commonplace in EV charging. Figure 1 also shows an alternative CS (4) that can be used in place of the fuel pump (1) for EV charging. Customers can use the PT (2) to pay directly with a credit or debit card. However, this raises a problem regarding Eichrecht. PT payments are processed by a payment service provider and a card issuer. As a company that provides EV charging and owns charging stations, we have no access to the personal information of those who pay for charging. This makes fulfilling Eichrecht difficult: how can we send SMV to customers in a reasonable and convenient way if we do not know their identity?

[0008] This is especially problematic every time there is a new hardware change or integration into the CS. A new Eichrecht certification is required. All of this is time-consuming and expensive. Eichrecht certification can take months, even a year. This means that adding payment terminals to existing stations is difficult, cumbersome and time-consuming, as each of the thousands of existing stations would have to be individually re-certified. Summary of the Invention [Problem to be solved by the invention]

[0009] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0010] It is an object to provide verification and authentication of charging of an EV. This object is achieved by the features of the independent claims. Some embodiments are set out in the dependent claims. [Means for solving the problem]

[0011] According to a first aspect, a computing device includes at least one processor and at least one memory containing computer program code. The at least one memory and the computer code are configured, by the at least one processor, to cause the computing device to at least: receive, via an application protocol interface API, data information including encrypted energy measurements authenticating and verifying the amount of energy charged to an electric vehicle (EV) from an EV charging station (CS); and provide the data information to a web server configured to be presented to a user who charges the EV at the CS, the data information being configured to be output to the user by a web-based user interface (21) that interacts with the web server. For example, one embodiment may enable the use of existing charging hardware without substantial modifications. The PT can be added to an existing older CS, further enabling Eichrecht compliance to be easily achieved without requiring a time-consuming and expensive new certification process.

[0012] According to one embodiment, the data information includes a signed meter reading SMV, which can be utilized to integrate energy supply regulation and authentication into various existing and new CSs.

[0013] According to one embodiment, the data information further includes payment card information used to charge EVs at the CS, which can be utilized to integrate energy supply regulation and authentication into various existing and new CSs.

[0014] According to one embodiment, the data information includes Eichrecht data information, for example, an Eichrecht compliant system can be conveniently integrated into a charging system.

[0015] According to one embodiment, the data information includes a link to the Eichrecht data information, for example, only the link without the Eichrecht information may be delivered to the user for later use.

[0016] According to one embodiment, the device is further configured to receive an identification of a charging event corresponding to the measurement value and to transmit data information corresponding to the identification to the UI, e.g., regulatory information is provided only to the UI identified for the CS.

[0017] According to one embodiment, the computing device is configured, after receiving information of a new charge from the charging station management system CSMS, to check which UI devices are logically linked to the CS where the charge has been made and to send data information to the checked UIs, e.g., only appropriate users receive energy measurements.

[0018] According to a second aspect, a system is configured to verify the charging of an electric vehicle (EV). The system includes a charging station management system (CSMS) configured to obtain encrypted energy measurements that authenticate and verify the amount of energy charged to the electric vehicle (EV) at a charging station (CS). The CSMS is further configured to transmit the measurements to a computing device via internet-based communication. The computing device is configured to store the measurements and transmit the measurements via internet-based communication to a user interface (UI) of a user who charged the EV at the charging station (CS) of the CSMS. The UI is configured to output the user's measurements. For example, one embodiment may enable the use of existing charging hardware without substantial modifications. A PT can be added to an existing older CS, further providing Eichrecht compliance easily without requiring a time-consuming and expensive new certification process.

[0019] According to one embodiment, the UI is configured to display the measurements to the user, and the system further includes transparency software configured to verify the measurements and the amount of energy the EV was charged with to the user. For example, the user can verify the correct energy meter for EV charging, such as an SMV.

[0020] According to one embodiment, the system further comprises a payment terminal PT configured to send a charging payment message to the CSMS. For example, an existing or new PT can be added to the system without an authentication process of the energy measurements.

[0021] According to one embodiment, the CSMS is further configured to send a charging enable message to the CS. The CSMS is further configured to receive a charging termination message and measurement values ​​from the CS. For example, the system can control existing and new CSs.

[0022] According to one embodiment, the CS is further configured to receive a charging enable message from the CSMS and send a charging completion message to the CSMS after charging is completed. For example, the system can control existing and new CSs.

[0023] According to one embodiment, the UI includes a screen located near the PT and the CS, or the UI includes a user's mobile phone, or the UI includes a printer configured to print measurements to the user. For example, various UIs can be used to provide authenticated energy measurements. The integration is convenient without an authentication process.

[0024] According to one embodiment, the UI is configured to present the user with a link to the measurements, for example, allowing the user to read the energy measurements at a later time.

[0025] According to one embodiment, the CSMS notifies the computing device that charging at the CS with a particular payment card has ended. The computing device is further configured to send measurements to a UI next to the CS. For example, a user who is next to the CS and using their personal payment card for charging may monitor the measurements.

[0026] According to a third aspect, a method for verifying charging of an electric vehicle (EV) includes: receiving, via internet-based communication, encrypted energy measurements that authenticate and verify the amount of energy charged to the electric vehicle EV from an EV charging station CS; and transmitting, via internet-based communication, the energy measurements for presentation to a user who charged the EV at the CS, the energy measurements configured to be output to the user by an internet-based user interface UI (21). For example, a charging system compatible with regulations such as Eichrecht can be conveniently updated to existing or new portions of the charging system without a separate or manual authentication process.

[0027] According to a further aspect, the computer program, when executed by a computing device, is configured to cause the computing device to at least: receive, via internet-based communication, encrypted energy measurements authenticating and verifying the amount of energy charged to the electric vehicle EV from the EV charging station CS (4); transmit, via internet-based communication, said energy measurements for presentation to a user who charged the EV at the CS, said energy measurements configured to be output to the user by an internet-based user interface UI (21).

[0028] Many of the attendant features will be more readily appreciated as the same becomes better understood by reference to the following detailed description considered in conjunction with the accompanying drawings.

[0029] The accompanying drawings are included to provide a further understanding of the exemplary embodiments, constitute a part of this specification, illustrate exemplary embodiments, and together with the description, serve to explain the exemplary embodiments. [Brief explanation of the drawings]

[0030] [Figure 1] FIG. 10 is a diagram illustrating an example of OTP setting according to a comparative example. [Figure 2] FIG. 1 illustrates an example of a computing device configured to charge an energy measurements portal, according to an exemplary embodiment. [Figure 3] FIG. 1 illustrates an example of a system having an Eichrecht portal, according to an exemplary embodiment. [Figure 4] FIG. 10 illustrates an example of charging summary information according to an exemplary embodiment. [Figure 5] FIG. 2 illustrates an example of the architecture of the Eichrecht portal, according to an exemplary embodiment. [Figure 6]FIG. 2 illustrates an example of a data model for a system with an Eichrecht portal, according to an exemplary embodiment. [Figure 7] FIG. 1 illustrates an example of a signaling diagram for authenticated charging, according to an exemplary embodiment. [Figure 8] FIG. 1 illustrates an example of a system with an Eichrecht portal using a user's mobile phone, according to an exemplary embodiment. [Figure 9] FIG. 10 illustrates an example of a system with an Eichrecht portal using a user's mobile phone, according to another exemplary embodiment. [Figure 10] FIG. 10 illustrates an example of a search interface for Eichrecht information, according to an exemplary embodiment. [Figure 11] FIG. 1 illustrates an example of a system having an Eichrecht portal with a printer, according to an exemplary embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0031] In the following, like reference numerals are used to denote like parts in the accompanying drawings.

[0032] Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below in connection with the accompanying drawings is intended as a description of the examples and is not intended to represent the only manner in which the examples may be constructed or utilized. The description sets forth functions of the examples and sequences of acts for construction and operation of the examples. However, the same or equivalent functions and sequences may be accomplished by different examples.

[0033] It has always been common for CSs to be connected to PTs. When a customer pays for charging using a PT, the system does not know the customer's name, email, or other contact information. At the same time, certification and verification regulations, such as the German Eichrecht Act, require CSs to send charging energy measurements, such as signed meter values ​​(SMV), to customers after charging is completed.

[0034] One embodiment addresses how the system can send an SMV to a customer after charging is complete, even if the system does not know the customer's contact information. The system can be configured to do this without any significant hardware-level modifications or hardware-level integration between the CS and PT. In fact, any hardware integration is intended to be avoided, as it would require a new, time-consuming and expensive authentication process.

[0035] In this embodiment, the integration is not performed at the hardware level, but the computing portal device is configured to enable Eichrecht information without any hardware modifications to existing CS and existing PT terminals.

[0036] One embodiment is configured to send information to customers that meets certification regulations without making any hardware changes to the CS. The certification regulation information may be charging energy measurements such as SMV or any other Eichrecht or regulation information. Therefore, the system may use a variety of existing hardware on the market. No significant hardware changes need to be made to the PT. The system is flexible to a variety of existing hardware on the market. The CSMS can be configured to use existing hardware without the need to Eichrecht certify it every time a change is made.

[0037] 2 illustrates an example of a computing device 7 configured to control credentials, according to an exemplary embodiment. The computing device 7 may also be referred to as a portal. The device 7 may be a cloud-based central portal configured for credentials and a web-based interface therefor.

[0038] There are many ways to access the web-based interface: A physical screen next to the CS where the information is automatically pushed after charging is finished. The possibility of accessing the same information on any device with a web browser, such as a mobile phone. The possibility of displaying a link to the information on the PT's screen, if the PT supports this. The possibility of later retrieval of the information based on payment card details.

[0039] According to one embodiment, the customer may order authentication information to their email. If there is a physical screen next to the CS, it may also be equipped with a printer, so the customer may choose to print the charging energy measurements such as SMV instead of getting them by email.

[0040] This embodiment may be configured without hardware level integration. This embodiment may be configured with fully cloud-based integration.

[0041] 2 shows an example embodiment of a computing device 7 for managing authentication and verification information to meet regulations regarding proper charging. The device 7 may include at least one processor 8. The at least one processor may include, for example, one or more of a variety of other processing devices including, for example, a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), processing circuitry with or without a DSP, or integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a dedicated computer chip, or the like.

[0042] The device 7 may further comprise at least one memory 9. The memory 9 may be configured to store, for example, computer program code 10, such as operating system software and application software. The memory may include one or more volatile memory devices, one or more non-volatile memory devices, and / or a combination thereof. For example, the memory may be embodied as a magnetic storage device (such as a hard disk drive, a floppy disk, or a magnetic tape), a magneto-optical storage device, or a semiconductor memory (such as a mask ROM, a programmable ROM (PROM), an erasable PROM (EPROM), a flash ROM, or a random access memory (RAM)).

[0043] Device 7 may further include a communication interface 11 configured to enable device 7 to send and / or receive information to and from other devices. Communication interface 11 is configured to provide at least a web-based interface, e.g., functioning as a web server. Communication interface 11 may be a wireless connection, e.g., a 3GPP® mobile broadband connection (e.g., 3G, 4G, 5G). However, communication interface 11 may be configured to provide one or more other types of connections, e.g., a wireless local area network (WLAN) connection, e.g., as standardized by the IEEE 802.11 series or the Wi-Fi Alliance; a short-range wireless network connection, e.g., Bluetooth, NFC (Near Field Communication), or RFID connection; a wired connection, e.g., a local area network (LAN) connection, a universal serial bus (USB) connection, or an optical network connection; or a wired Internet connection. Communication interface 11 may include or be configured to be coupled to at least one antenna for transmitting and / or receiving radio frequency signals. Also, one or more of the various types of connections may be implemented as separate communication interfaces that may be coupled or configured to be coupled to multiple antennas.

[0044] The device 7 may further include an application protocol interface API 12 configured for the CSMS. The CSMS API 12 is configured for connection between the device 7 and the CSMS, and receives data from the CSMS.

[0045] When device 7 is configured to implement functionality, several components of device 7 may be configured to implement this functionality, such as, for example, at least one processor 8 and / or memory 9. Furthermore, when at least one processor 8 is configured to implement a function, this function may be implemented using, for example, program code 10 contained in memory 9.

[0046] The functionality described herein may be performed, at least in part, by one or more computer program product components, such as software components. According to one embodiment, a device includes a processor or processor circuitry, such as a microcontroller, that, when executed, is configured to perform embodiments of the described operations and functions via program code. Alternatively or additionally, the functionality described herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), graphics processing units (GPUs), etc.

[0047] The device 7 comprises means for performing at least one of the methods described herein. In one example, the means comprises at least one processor 8 and at least one memory 9 including program code 10 configured, when executed by the at least one processor 8, to cause the device 7 to perform the method.

[0048] Device 7 may comprise, for example, a server device. Although device 7 is shown as a single device, it will be understood that the functionality of device 7 may be distributed across multiple devices, where applicable. In one embodiment, device 7 may comprise a cloud-based Eichrecht portal.

[0049] FIG. 3 shows an exemplary embodiment of a system 33 having an anonymous cloud-based Eichrecht portal 7 where anonymous customers 13 making payments with PT2 can view their Eichrecht information.

[0050] The customer 13 pays the charging fee at PT2, which notifies the CSMS 14 of the payment in operation 15.

[0051] In operation 16, CSMS 14 begins charging at CS4.

[0052] After charging for a while, the customer 13 stops charging. In operation 17, the CS4 sends a stop message to the CSMS 14, including the SMV.

[0053] The customer 13 pays the charging fee in action 15, starts charging in action 16, and stops charging in action 17 when ready to charge.

[0054] As a result, the CSMS14 obtains the following information from the CS4: a) the signed meter value SMV of the individual charging event, b) a payment token identifying the payment card used for the payment, as well as the last four digits and expiry date of the payment card.

[0055] In operation 18, the CSMS 14 notifies the Eichrecht portal 7 that charging with the payment card has finished on the CS4. When the CSMS 14 receives the SMVs as part of the OCPP StopTransaction message, it waits for a StatusNotification=Available message indicating how the customer 13 disconnected the EV from the CS4. The CSMS 14 then sends these SMVs along with the payment card information to the cloud-based Eichrecht portal 7.

[0056] In operation 19, the Eichrecht portal 7 pushes this information to an Eichrecht screen 20 that may be located next to the CS4. Each Eichrecht-compliant CS4 with PT2 is logically linked by the Eichrecht portal 7 to an Eichrecht screen 20 that may be physically located next to the CS4.

[0057] In operation 21, the customer 13 can view the Eichrecht information, including the SMV, on the screen 20. The customer 13 can also order this information by email if he wishes. After receiving the information of the new charge from the CSMS 14, the Eichrecht portal 7 checks that the Eichrecht screen 20 is logically linked to the CS4 where the charge took place and sends this information to the screen 20, where it is displayed to the customer 13.

[0058] If the customer 13 wishes, the customer 13 can also order this information to his / her email address, and the Eichrecht portal 7 then sends a receipt containing the SMV to the customer's email.

[0059] 4 shows an example of an Eichrecht screen mockup with information push, according to one embodiment. This information is automatically pushed to screen 20 after charging is finished and customer 13 unplugs the EV. A charging summary is displayed with the CS's identification, Eichrecht information for the charging event, and the customer's 13 email. Customer 13 can interact with screen 20 accordingly.

[0060] FIG. 5 shows one embodiment of the architecture of the Eichrecht portal 7 and the Eichrecht screen 20 .

[0061] The computing portal device 7 includes a processor 8 and memory 9, such as an Eichrecht database. The Eichrecht portal 7 is responsible for storing charging information, including SMV and payment card information, in the central database 8. The portal device 7 also includes an API 12 for the CSMS 14. The API 12 receives data from the CSMS 14. The portal device 7 includes a web interface 11, such as a web server. The Eichrecht portal 7 provides this information through the web-based interface 11. This information can be used by various web browsers 21, either on special on-site screens or on any device with a web browser, such as a mobile phone. The Eichrecht screen 20 can be a simple computer with a web browser 21 that connects to the Eichrecht portal 7. No logic or functionality is required other than opening a specific web page for the Eichrecht information.

[0062] 6 shows one embodiment of a data model for the Eichrecht system. The Eichrecht portal 7 is logically connected to an Eichrecht screen 20 with an SMV and a charging transaction 22. The charging transaction 22 is logically connected to a customer 13 and a payment card 23, and of course the customer 13 has the payment card 23. The charging transaction 22 is logically connected to the CS4 and the Eichrecht portal 7. The charging station 7 is logically connected to the Eichrecht screen 20.

[0063] FIG. 7 shows a signaling or process diagram for authentication and verification of an EV charging operation by an Eichrecht portal device 7. In operation 24, the CSMS 14 sends the SMV of a single charging operation performed at a single charging station 4 to the Eichrecht portal 7. In operation 25, the portal device 7 checks which screen is logically linked to the charging station 4. The Eichrecht portal 7 sends the Eichrecht information to the correct screen 20. In operation 26, the screen 20 displays the Eichrecht information to the customer 13. In operation 27, the customer 13 enters an email to order the Eichrecht information. In operation 28, the email order is submitted to the portal device 7. In operation 29, the portal device sends the Eichrecht information to the customer 13 via email.

[0064] FIG. 8 illustrates one embodiment for authenticating EV charging operations.

[0065] The PT 2 can also be configured to display a short message after charging is complete. In this case, a separate Eichrecht screen 20 is not required. In operation 15′, the CSMS 14 displays the message “Get Eichrecht information, for example, at http: / / chge.eu / r / ABC123” on the PT screen, which is a link to the Eichrecht portal 7. The last part of the link 30, 31 (in this example, “ABC123”) is a unique identifier for the single Eichrecht information for a single charge. The customer 13 can then open this link 30, 31, for example, on a mobile phone 32 or any other device with a web browser 21 and then view the Eichrecht information. In the embodiment of FIG. 8, a screen is not required, but the mobile phone 32 and the links 30, 31 to the Eichrecht information may be used.

[0066] FIG. 9 illustrates one embodiment of authenticating an EC charging operation that can be configured to look up Eichrecht information later. Sometimes, customers forget to check or email the Eichrecht information immediately and want to access the information later, for example, the next day. Customer 13 receives instructions on how to access the Eichrecht information, for example, on the CS4 owner's web page or on a sticker on the CS4. Customer 13 can open link 31' to Eichrecht portal 7 and search for Eichrecht information. If a charging operation is found using the criteria provided by customer 13, the Eichrecht information is displayed to customer 13. Customer 13's mobile phone 32 can indicate the charging operation.

[0067] FIG. 10 shows an embodiment of an Eichrecht information search user interface for customer 13. If customer 13 later wants to fetch Eichrecht information, customer 13 can do so using a simple UI. If Eichrecht information is found using this criteria, a link to that information may be presented to customer 13. The "Find Charging Information" includes the station ID, the last four digits of the payment card, and the charging date. This search user interface may be used to search for Eichrecht information corresponding to the search term.

[0068] FIG. 11 shows one embodiment of an Eichrecht screen 20 with a printer 3. The Eichrecht screen 20 can also be combined with a printer 3 that prints the Eichrecht information on paper or on a receipt, similar to receipt printers used in various locations. Once charging is complete, the Eichrecht information can be displayed on the screen 20. However, instead of ordering the Eichrecht information by email, the customer 13 can choose to print the information. In this case, the same Eichrecht information displayed on the screen 20 is printed on paper using the printer 3 attached to the screen 20.

[0069] Further features of the method result directly from the functionality of the computing device, for example, as described throughout the specification and in the appended claims, and therefore will not be repeated here. Also, different variations of the method can be applied, as described in connection with various exemplary embodiments. It is obvious to those skilled in the art that with the advancement of technology, the basic concept of the present disclosure can be implemented in various ways. Therefore, the present disclosure and embodiments are not limited to the above examples, but may instead vary within the scope of the claims.

[0070] A computing device may perform or be configured to cause any aspect of the methods described herein to be performed. Further, a computer program may include instructions that, when executed, cause the device to perform any aspect of the methods described herein. Further, the device may comprise means for performing any aspect of the methods described herein. According to an exemplary embodiment, the means comprises at least one processor and a memory containing program code, the at least one processor and the program code, when executed by the at least one processor, are configured to cause the execution of any aspect of the method.

[0071] The values ​​of any ranges or devices described herein may be expanded or modified without losing the desired effect, and any embodiment may be combined with another embodiment unless expressly prohibited.

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

[0073] It will be understood that the benefits and advantages described above may relate to one embodiment or several embodiments. The embodiments are not limited to those that solve any or all of the described problems or have any or all of the described benefits and advantages. Furthermore, it will be understood that references to "an" or "an" item may refer to one or more of those items.

[0074] The actions of the methods described herein may be performed in any suitable order, or simultaneously where appropriate. Additionally, individual blocks may be deleted from any method without departing from the scope of the subject matter described herein. Aspects of any of the above-described embodiments may be combined with aspects of any of the other embodiments described above to form further embodiments without losing the desired effect.

[0075] As used herein, the term "comprising" is used to mean including the specified methods, blocks, or elements, but not that such blocks or elements comprise an exclusive list, and that the methods or devices may include additional blocks or elements.

[0076] As used herein, the terms "automated," "automatically," and "automatic," and variations thereof, may refer to any process or operation that occurs without human input when the process or operation is performed. However, even if human input is used in the performance of the process or operation, the process or operation may be automatic if the input is received before the process or operation is performed.

[0077] A subject may be referred to as a "primary" or "secondary" subject, but this does not necessarily indicate the subject's order or importance. Instead, such an attribute may be used solely to differentiate between subjects.

[0078] It will be understood that the above description is provided by way of example only, and that various modifications may be made by those skilled in the art. The above specification, examples, and data provide a complete description of the structure and use of the exemplary embodiments. While various embodiments have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, those skilled in the art may make many modifications to the disclosed embodiments without departing from the scope of the present specification. [Explanation of symbols]

[0079] 1 fuel pump 2. Payment terminal 3. Electronic receipts 3. Printer 4 Charging Stations 7. Computing Devices 7. Eichrecht Portal 8 processors 8. Central Database 9. Memory 10 Computer Program Code 11 Communication Interface 11 Web Server 12 Application Protocol Interface 13 Customer 14 Charging Station Management System 20 Eichrecht Screen 21 User Interface 30 Links 31 Links 32 Mobile Phones 33 System

Claims

1. A computing device (7), at least one processor (8); at least one memory (9) containing computer program code (10); Equipped with The at least one memory and the computer program code are transmitted by the at least one processor to the computing device, at least: receiving data information including an encrypted energy measurement value that authenticates and verifies an amount of energy charged by an electric vehicle EV from an EV charging station CS (4) via an application protocol interface API (12), the data information further including at least a portion of least significant digits of a payment card used to charge the EV at the CS and a CS identification, the portion of least significant digits of the payment card and the CS identification being configured to associate with the encrypted energy measurement value that authenticates and verifies the amount of energy charged; the computing device is further configured to, after receiving the charging information from a charging station management system CSMS, check, based on the data information, which web-based UI device (21) is logically linked to the CS where the charging was performed; providing the data information to a web server (11) configured to be presented to an anonymous user who charged the EV at the CS, the data information being configured to be output to the anonymous user by the web-based UI device (21) interacting with the web server; configured to cause Computing devices (7).

2. The computing device of claim 1 , wherein the data information includes a signed meter value SMV.

3. The computing device of claim 1 , wherein the data information further comprises payment card information used to charge the EV at the CS.

4. The computing device of claim 1 , wherein the data information comprises Eichrecht-compliant data information.

5. The computing device of claim 1 , wherein the data information includes a link to Eichrecht-compliant data information.

6. 2. The computing device of claim 1, further configured to receive identification information of a charging event corresponding to the measurement value and to transmit the data information corresponding to the identification information to the UI device.

7. A system (33) for verifying charging of an electric vehicle (EV), comprising: a charging station management system CSMS (14) configured to acquire data information including encrypted energy measurements that authenticate and verify an amount of energy charged by an electric vehicle EV at a charging station CS; the CSMS is further configured to send the measurements to a computing device (7) by internet-based communication; the computing device is configured to store the measurements and transmit the measurements via the internet-based communication to a user interface UI (3', 20, 32) of an anonymous user who charged the EV at a charging station CS (4) of the CSMS; the UI is configured to output the measurements of the anonymous users; the data information further includes a portion of the least significant digits of a payment card used to charge the EV at the CS and a CS identification, and the portion of the least significant digits of the payment card and the CS identification are configured to associate with the encrypted energy measurement value that authenticates and verifies the amount of energy charged. System (33).

8. 8. The system of claim 7, wherein the UI is configured to display the measurements to the anonymous user, and wherein the system further comprises transparency software configured to verify the measurements and the amount of energy an EV was charged with to the anonymous user.

9. The system according to claim 7, further comprising a payment terminal PT(2) configured to send a charging payment message to the CSMS.

10. The system of claim 7 , wherein the CSMS is further configured to send a charging enable message to the CS and receive a charging termination message and the measurement values ​​from the CS.

11. The system of claim 7 , wherein the CS is further configured to receive a charging enable message from the CSMS and send a charging completion message to the CSMS after charging is completed.

12. The system of claim 7, wherein the UI includes a payment terminal PT and a screen located near the CS, or the UI includes a mobile phone of the anonymous user, or the UI includes a printer configured to print the measurement value to the anonymous user.

13. The system of claim 7 , wherein the UI is configured to present a link to the measurement to the anonymous user.

14. the CSMS notifying the computing device that charging at the CS with a particular payment card has ended; The system of claim 7 , wherein the computing device is further configured to send the measurements to the UI, the UI being located adjacent to the CS.

15. 1. A method for verifying charging of an electric vehicle (EV), comprising: receiving, via internet-based communication, data information including an encrypted energy measurement value that authenticates and verifies an amount of energy charged by an electric vehicle EV from an EV charging station CS (4), the data information further including a portion of least significant digits of a payment card used to charge the EV at the CS and a CS identification, the portion of least significant digits of the payment card and the CS identification configured to associate with the encrypted energy measurement value that authenticates and verifies the amount of energy charged; checking, based on the data information, which internet-based user interface device (21) is logically linked to the CS where the charging took place, and transmitting the energy measurements via the internet-based communication for presentation to the anonymous user who charged the EV at the CS, the energy measurements being configured to be output to the user by the internet-based user interface UI (21); A method comprising:

16. When executed by a computing device, the computing device performs at least: receiving, via internet-based communication, data information including an encrypted energy measurement value authenticating and verifying an amount of energy charged to an electric vehicle EV from an EV charging station CS (4), the data information further including a portion of least significant digits of a payment card used to charge the EV at the CS and a CS identification, the portion of least significant digits of the payment card and the CS identification configured to associate with the encrypted energy measurement value authenticating and verifying the amount of energy charged; checking, based on the data information, which internet-based user interface device (21) is logically linked to the CS where the charging took place, and transmitting the energy measurements by the internet-based communication for presentation to the anonymous user who charged the EV at the CS, the energy measurements being configured to be output to the user by the internet-based user interface UI (21); configured to cause the data information further includes a portion of the least significant digits of a payment card used to charge the EV at the CS and a CS identification, and the portion of the least significant digits of the payment card and the CS identification are configured to associate with the encrypted energy measurement value that authenticates and verifies the amount of energy charged. Computer program.

Images