EV Charging Authentication via Mobile Relay and Offline Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing real-time communication systems for electric vehicle charging, such as those using the Open Charge Point Protocol (OCPP), require infrastructure-side internet connections, leading to high operating costs, complex installations, and poor user experience, especially in areas without mobile network coverage.
Innovation Solution
A method that enables charging devices to authenticate users and report charging data to a central database unit without an infrastructure-side internet connection, using public key cryptography for secure authentication and reporting, and allowing operation in a partially disconnected state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If real-time communication systems (OCPP, proprietary protocols) are used for charging device authentication and reporting, then reliable user authentication and charging data reporting are achieved, but infrastructure-side internet connection is required, leading to high operating costs and complex installation
Solution Approach 1:
The patent introduces a mobile device as an intermediary between the charging device and the central server. The mobile device stores authentication credentials locally and communicates with the charging device via short-range wireless communication (NFC, Bluetooth, Wi-Fi Direct), eliminating the need for the charging device to have direct internet connectivity. This intermediary approach maintains authentication reliability while removing infrastructure complexity.
Solution Approach 2:
Authentication credentials and charging data are cached and prepared in advance on the mobile device and charging device respectively. The charging device stores charging session data locally, and the mobile device pre-loads authentication tokens, enabling offline authentication and data exchange without real-time server connection, thus reducing installation and operational complexity.
2Productivity
If infrastructure-side internet connection (WiFi, 3G, 4G, 5G) is provided for charging devices, then real-time communication with central server is enabled, but operating costs increase due to SIM card fees and connection charges
Solution Approach 1:
The system transitions from continuous real-time communication to periodic batch synchronization. The charging device accumulates charging data locally and synchronizes with the central server periodically when connectivity is available, rather than maintaining constant communication. This reduces data transmission frequency and associated costs while maintaining data accuracy.
Solution Approach 2:
The mobile device serves itself by storing authentication credentials and charging data locally, eliminating the need for the charging device to maintain expensive internet connections. The charging device performs self-authentication using credentials from the mobile device, and data synchronization occurs opportunistically when connectivity is available, reducing ongoing operational costs.
3Adaptability or versatility
If RFID reader is added to charging device for authentication in areas without mobile network coverage, then user access is enabled, but consumer acceptance decreases and hardware costs increase
Solution Approach 1:
The mobile device serves multiple functions: it acts as an authentication credential storage, a communication interface with the charging device, and a data synchronization point with the central server. This multi-functional approach eliminates the need for specialized RFID readers while maintaining broad compatibility and excellent user experience through the ubiquitous mobile device.
4Reliability
If central server is required to authenticate users at charging devices, then secure billing is achieved, but every installation requires infrastructure-side internet connection, increasing deployment complexity
Solution Approach 1:
The authentication system is segmented into three independent components: the central server for credential management, the mobile device for local authentication storage and charging data collection, and the charging device for charging delivery and data caching. This segmentation allows each component to be deployed and configured independently, eliminating the requirement for infrastructure-side internet connection at charging locations while maintaining billing security through the mobile device's role as secure intermediary.
Applied Scientific Principles
This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.
Function Achieved in This Case
This solution reduces operating costs and installation complexity, provides a more user-friendly and reliable authentication process, and ensures secure billing even in areas with low or no internet connectivity, by eliminating the need for WiFi/3G/4G/5G hardware and proprietary control protocols.
Implementation Method 1
using public key cryptography for secure authentication and reporting
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention relates to an authenticating and reporting system (10) for authenticating a user at and reporting about use of a charging device (40) comprising: - at least one database unit comprising: - at least one cryptography module (22) configured to sign and/or encrypt authentication elements (28) and to decrypt charging report elements (48), and - at least one transmitting and receiving module (26) configured to transmit encrypted authentication elements (28) and to receive encrypted charging report elements (48);- at least one charging device (40) comprising: - at least one wireless communication module (44), - at least one encrypting and decrypting unit (46), - at least one storage module (42), and - at least one control module, wherein the at least one charging device (40) is configured to decrypt the authentication elements (28), control a charging procedure of a connected chargeable device, provide encrypted charging report elements (48), and store a timestamp parameter of a transmitted encrypted charging report element (48) or a group of transmitted encrypted charging report elements (48); - and at least one mobile device (30) configured to transfer the authentication elements (28) from the database unit (20) to the charging device (40) and the charging report elements (28) from the charging device (40) to the database unit (20).