Blockchain-Based Public Key Management for ICN Data Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Information-Centric Networking (ICN) and hybrid ICN, public keys used for authenticating and validating data become obsolete when cached at intermediate network nodes, and content producers cannot change these keys in real time, leading to security and integrity issues.
Innovation Solution
A blockchain is used to store information related to public keys, allowing content producers to generate and update keys dynamically, and enabling user devices to access and verify the authenticity of data using these keys, while ensuring that only current public keys are used for authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If public keys are cached at intermediate network nodes, then authentication efficiency is improved, but key obsolescence occurs leading to security issues
Solution Approach 1:
The system implements feedback by having user devices continuously monitor the blockchain for key update notifications. When a new public key is published, the user device receives notification and updates its cached key, ensuring the cache remains valid while maintaining authentication efficiency.
Solution Approach 2:
The blockchain acts as an intermediary between the content producer and user devices for key management. It provides a decentralized, tamper-proof mechanism for publishing key updates, which intermediate nodes and user devices can verify without relying on centralized authority.
2Ease of operation
If public keys are distributed in advance, then authentication setup is simplified, but real-time key changes cannot be implemented
Solution Approach 1:
The system transitions from static key distribution to dynamic key management. Public keys are initially cached for efficient authentication, but the system dynamically updates keys in real-time through blockchain-based notifications when key rotation is needed, combining both simplicity and adaptability.
Solution Approach 2:
User devices perform preliminary action by caching public keys in advance from the blockchain, enabling efficient authentication. The system prepares for future key changes by continuously monitoring the blockchain for updates, so when key rotation occurs, the device can quickly switch to the new key without disruption.
3Reliability
If blockchain is used to store public keys, then key management security is improved, but system complexity increases
Solution Approach 1:
The blockchain provides self-service key management by automatically publishing new public keys when content producers generate them. User devices automatically monitor the blockchain for updates and self-update their cached keys without manual intervention, reducing operational complexity despite the added architectural layer.
Solution Approach 2:
The blockchain serves multiple functions: it stores content metadata, manages public key distribution, and provides a notification mechanism for key updates. This multi-functionality consolidates several systems into one, reducing overall system complexity while maintaining high security standards.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
An electronic device of a content producer generates a chunk of data, associates a location- independent name with the chunk of data, generates a signature for the chunk of data, attaches the signature to the chunk of data, and transmits the chunk of data, with the signature attached, to one or more user devices in response to respective requests. The signature is generated based on the data in the chunk, using a private key of the electronic device. The electronic device also stores information, including a specification of a public key associated with the private key, in a first ledger entry of a blockchain, to provide the one or more user devices with access to the public key. A user device may obtain the public key and use it to verify the chunk of data.