Trusted Component Node Self-Revocation with Heartbeat Counters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing V2X communication protocols face challenges in timely and secure revocation of compromised vehicles, with methods like CRLs and short-lived pseudonyms leading to network congestion, high verification overhead, and vulnerability to network disruptions.
Innovation Solution
A method and system for self-revocation using heartbeat messages with freshness parameters and counter conditions, ensuring revocation occurs within a fixed time or operations, independent of network synchronization, and resistant to attacker interference.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If certificate revocation lists (CRLs) are used for revocation, then compromised vehicles can be removed from the network, but the lists grow larger over time causing increased verification overhead and slower message verification
Solution Approach 1:
The patent segments the monolithic CRL into multiple smaller lists organized by pseudonym generation time periods. Each TC node maintains only the relevant subset of revocation lists corresponding to its pseudonym generation time, rather than downloading and verifying the entire CRL. This segmentation reduces the verification overhead and maintains faster message verification speeds while preserving complete revocation coverage.
2Reliability
If short-lived pseudonyms are used, then compromised vehicles are removed from the network after pseudonym expiration, but vehicles must periodically fetch new pseudonyms from edge servers increasing network traffic
Solution Approach 1:
The patent implements preliminary action by having TC nodes proactively check revocation status before pseudonym expiration by monitoring heartbeat messages from RA nodes. When a TC node detects that its pseudonym is about to expire or has been revoked, it can proactively fetch new pseudonyms or update its revocation status before the expiration occurs. This prevents the need for frequent reactive fetches and reduces overall network traffic while maintaining security.
3Productivity
If self-revocation technique is used, then DAA credentials are automatically deleted upon receiving revocation request, but network disruptions or attacks can prevent the request from reaching the TC node
Solution Approach 1:
The patent implements feedback mechanisms where TC nodes periodically send status requests to RA nodes to verify whether their pseudonyms are still valid. RA nodes respond with confirmation or revocation status, providing continuous feedback to TC nodes. This feedback loop ensures that even if direct revocation requests are blocked by network disruptions, TC nodes will eventually detect the revocation status through their periodic status checks and complete the self-revocation process.
4Reliability
If heartbeat messages are sent periodically to trigger self-revocation, then revocation can be triggered even without direct contact, but the system requires fixed time or operation counters that may not align with network synchronization
Solution Approach 1:
The patent implements a universal counter mechanism that serves multiple functions: it tracks the number of operations performed by the TC node, monitors the time elapsed since the last heartbeat message, and determines when self-revocation should be triggered. This single counter structure can be configured with different thresholds and conditions to adapt to various network synchronization scenarios, making it a multi-functional tool that simplifies the overall system complexity while maintaining reliable revocation triggering.
Data Source
AI summary
There is provided techniques for self-revocation. A method is performed by a TC node (200a). The TC node (200a) is provided with an identifier and DAA credentials. The TC node (200a) is to receive a heartbeat message from an RA node (300). The heartbeat message comprises a freshness parameter and a revocation request with a list of identifiers for which revocation is pending. The method comprises revoking (S106a, S106b) the DAA credentials when either: the heartbeat message is received from the RA node (300) whilst a counter condition is satisfied, correctness of the freshness parameter is verified by the TC node (200a), and the identifier is present in the list of identifiers; or failing to receive the heartbeat message from the RA node (300) whilst the counter condition is satisfied.