Blockchain NFT Firmware Authentication Without a Central Signing Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing firmware management models, particularly those using a top-down topology, are vulnerable to security breaches due to the assumption that the central signing and update servers are invincible, which can lead to system failure if the private key is compromised.
Innovation Solution
Implementing a decentralized firmware management model based on blockchain Non-Fungible Tokens (NFTs) where each firmware layer, including devices and the server, has a unique NFT token for authentication and updates, ensuring no single point of failure, and all transactions are recorded on the blockchain for verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a top-down topology with central signing server is used, then firmware management can be centralized and simplified, but security reliability deteriorates when the private key is compromised
Solution Approach 1:
The patent segments the centralized firmware management system into decentralized components by introducing blockchain technology and smart contracts. Each firmware update and device authentication is independently recorded as a transaction on the blockchain, eliminating the single point of failure represented by the central signing server. This segmentation allows the system to maintain functionality even if one component is compromised.
Solution Approach 2:
The patent introduces blockchain as an intermediary between the firmware management server and devices. Instead of direct trust in a central authority, the system uses blockchain as a neutral mediator that records all firmware transactions immutably. The smart contract serves as an intermediary that automatically executes firmware updates and authentication without requiring trust in a central server's private keys.
2Reliability
If a decentralized NFT-based model is implemented, then security reliability is improved by eliminating single point of failure, but device complexity increases due to blockchain integration
Solution Approach 1:
The patent makes the blockchain infrastructure universal by designing a single blockchain-based system that handles multiple firmware management functions: authentication, authorization, firmware distribution, and verification. The smart contract serves multiple purposes simultaneously, reducing the need for separate complex systems for each function and thereby limiting the increase in overall device complexity.
Solution Approach 2:
The patent uses NFTs (non-fungible tokens) as digital copies that represent firmware ownership and authenticity. Instead of requiring complex cryptographic verification systems, the system uses NFTs as self-contained copies that encode all necessary firmware information and authentication data. This copying approach simplifies the verification process while maintaining security.
3Reliability
If blockchain and NFTs are used for firmware management, then trustlessness and security are improved, but manufacturing and implementation complexity increases
Solution Approach 1:
The patent implements preliminary action by pre-deploying smart contracts on the blockchain before the firmware management system is fully operational. The smart contracts are prepared in advance with all necessary logic for authentication, authorization, and firmware updates, eliminating the need for complex real-time decision-making during firmware operations. This preliminary preparation simplifies implementation.
Solution Approach 2:
The patent enables self-service by designing the system so that devices can autonomously verify firmware authenticity and execute updates without requiring continuous intervention from a central authority. The blockchain and NFTs automatically provide authentication and authorization services, reducing the complexity of manual implementation and maintenance.
Data Source
Figure 1a~1b
Figure 2a~2b
Figure 3
AI summary
Various examples relate to methods, apparatuses, devices and computer programs for a client device and a firmware management device, to the client device and the firmware management device, and to a system. The method for the client device comprises determining, on a blockchain, a non-fungible token (NFT) specifying a firmware for the client device, with the client device being set as owner of the NFT and managing a firmware of the client device based on the firmware specified by the NFT.