Authentication Device Key Swap Certificate Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Manufacturers face challenges in protecting software and data within technical devices from tampering or modification, which can disrupt their business models and the intended device functionality.
Innovation Solution
The implementation of a private/public key pair system for authentication devices, where a private key is used for signing data and a public key for validation, with a key swap certificate mechanism allowing for multilevel customization and protection of software and data across different manufacturing levels without exposing sensitive information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single private key is used for signing software and data across multiple manufacturing levels, then key management is simplified, but security is compromised because exposure of the key at any level compromises all devices
Solution Approach 1:
The patent segments the single private key into multiple distinct private keys, each assigned to a specific manufacturing level (first level private key for factory, second level private key for customer). This segmentation allows each level to operate independently with its own key pair, eliminating the security risk of a single key compromise while maintaining manageable key structures at each level.
Solution Approach 2:
The patent introduces a hierarchical dimension to key management by creating multiple levels of private/public key pairs corresponding to different manufacturing stages. Instead of a flat single-key structure, the system organizes keys in a multi-level hierarchy where each level has its own cryptographic pair, adding structural depth to the key management system.
2Adaptability or versatility
If manufacturer secrets are shared with customers for programming purposes, then multilevel customization is enabled, but security is compromised because the customer could expose the secrets
Solution Approach 1:
The patent segments the manufacturing process into distinct levels, each with its own private key and authorization scope. The first level manufacturer uses its private key to sign software, and the customer uses a separate second level private key for customization. This segmentation enables multilevel customization while preventing secret exposure because each level operates with its own cryptographic credentials.
Solution Approach 2:
The patent introduces public keys and digital signatures as intermediaries between manufacturing levels. Instead of directly sharing private secrets, the system uses public key infrastructure where each level proves its authorization through digitally signed messages. The public key acts as a safe intermediary that enables communication and verification without exposing sensitive private information.
3Reliability
If existing authentication mechanisms are used, then software integrity can be verified, but the system requires continuous server dependencies and complex key management infrastructure
Solution Approach 1:
The patent enables the authentication device to perform self-verification of software integrity using embedded public keys and digitally signed messages. The device can independently verify the authenticity of factory-programmed software and customer-customized software without requiring continuous connection to external servers or complex key management infrastructure. Each level signs its contributions, and the device verifies them locally using the corresponding public keys.
Data Source
AI summary
An authentication device may be provided. The authentication device may include a memory configured to store: a first public key; and first data signed using a first private key corresponding to the first public key, the signed data including a second public key. The authentication device may further include a first verification circuit configured to verify the first data using the first public key; and a second verification circuit configured to verify second data using the second public key, the second data signed using a second private key corresponding to the second public key.


