EV Charge Authentication Key Switching During Certificate Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing charge control systems in electric vehicles fail to consider the update of certificates, leading to potential loss of private keys and authentication failures when new certificates are installed, disrupting continuous charging operations.
Innovation Solution
The charge control device stores a first private key corresponding to a current certificate in a first memory area and generates a second private key for a new certificate in a separate second area, allowing both keys to be used sequentially to maintain continuous charging authorization during the certificate update process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new certificate and private key are generated to update an existing certificate, then the certificate can be renewed or upgraded, but the original private key may be overwritten and lost, causing authentication failure
Solution Approach 1:
The patent segments the storage space into multiple distinct areas (first area and second area) within the memory. The first private key is stored in the first area, while the second private key is stored in the second area. This segmentation prevents the second private key from overwriting the first private key, thereby maintaining authentication continuity while enabling certificate updates.
2Device complexity
If the private key storage area is reused for new certificate installation, then storage space is efficiently utilized, but the existing private key is lost and charging authentication fails
Solution Approach 1:
The memory is divided into multiple dedicated storage areas for different private keys. This segmentation allows efficient storage management without overwriting existing keys, as each key has its designated space. The controller can selectively access different areas based on certificate validity, maintaining both storage efficiency and authentication reliability.
Solution Approach 2:
The patent establishes a predetermined storage structure with multiple designated areas for private keys before certificate updates occur. This preliminary arrangement ensures that when a new certificate is installed, its private key can be placed in a pre-designated area without affecting existing keys, preventing authentication failures.
3Speed
If the system immediately switches to the new private key upon generation, then the new certificate is activated quickly, but the transition may cause authentication interruptions if the new key is not properly installed
Solution Approach 1:
The controller dynamically selects which private key to use based on the installation status of the new certificate. During the transition period, the controller continues to use the first private key from the first area. Once the second certificate is fully installed, the controller switches to using the second private key from the second area. This dynamic approach ensures smooth transitions without authentication interruptions.
Solution Approach 2:
The system implements feedback mechanisms to monitor the certificate installation status. The controller receives notifications about installation completion and adjusts its behavior accordingly - continuing to use the first private key during installation and switching to the second private key after installation completion. This feedback-driven approach ensures authentication stability during the transition.
Data Source
AI summary
A charge control device for a vehicle includes: a controller configured to communicate with a charging facility for a charge authentication, the controller storing a first private key corresponding to a first certificate in a first area of a memory, wherein the controller is configured to: generate a second private key and a public key in response to a request from a certificate issuer; store the second private key in a second area of the memory different from the first area; transmit the public key to the certificate issuer to receive a second certificate issued by the certificate issuer; maintain use of the first private key until an installation completion of the second certificate; and use the second private key upon the installation completion.