Token Management for Secure D2D IoT Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Device-to-device (D2D) communication in IoT services faces challenges in securing data transmission due to low power and low specification platforms, making existing security techniques inadequate in preventing data leakage.
Innovation Solution
A server-based system generates and manages key tokens with a validity period, using hash values to secure data transmission between devices, where the token manager generates and updates hash values, and discards them based on validity periods and input policies, ensuring secure synchronization and authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional security techniques are used in D2D communication, then implementation is simpler, but security against data leakage is insufficient
Solution Approach 1:
The security mechanism is segmented into multiple components: key tokens for authentication, hash values for integrity verification, and policy-based control rules. This segmentation allows each component to perform its specific security function independently, improving overall security reliability without requiring a single complex security system
Solution Approach 2:
Key tokens and hash values are generated and distributed to devices before actual D2D communication occurs. This preliminary security setup ensures that authentication and integrity verification mechanisms are already in place, enabling secure communication without adding complexity during the actual data transmission process
2Reliability
If key tokens are managed with fixed validity periods, then security is improved, but token management complexity increases
Solution Approach 1:
Key tokens are configured with validity periods and are automatically renewed or revoked based on time-based policies. This periodic management approach ensures that security credentials remain current and revocable, improving security without requiring continuous manual intervention
Solution Approach 2:
The server monitors token usage and validity status, automatically generating new tokens or revoking expired ones based on policy feedback. This automated feedback loop manages token lifecycle complexity on the server side, keeping device-side implementation relatively simple
3Reliability
If hash values are generated multiple times, then security against replay attacks is improved, but computational overhead increases
Solution Approach 1:
Multiple hash values are generated and stored locally in device memory rather than computing them repeatedly during communication. This local caching approach ensures protection against replay attacks while minimizing computational energy consumption during actual data transmission
Solution Approach 2:
Hash values are pre-computed and stored in device memory before communication occurs. This preliminary generation of multiple hash values eliminates the need for repeated computational operations during data transmission, reducing energy overhead while maintaining security
4Reliability
If token lifecycle is automatically managed, then security is enhanced, but system complexity increases
Solution Approach 1:
The server acts as an intermediary that automatically manages token lifecycle including generation, distribution, renewal, and revocation. This centralizes complexity in the server infrastructure, keeping device-side implementation simpler while maintaining enhanced security through automated lifecycle management
Solution Approach 2:
The system implements automated token management where tokens self-renew or self-revoke based on embedded validity periods and server policies. This self-service approach enhances security through consistent automated management without requiring complex manual intervention systems
Data Source
AI summary
A method of managing a token and a server for performing the same are provided. According to the embodiments of the present disclosure, it is possible to easily authenticate a counterpart device using a one-time key HN(T) for a D2D communication between a first device and a second device, without using a separate secure channel (e.g., secure sockets layer (SSL), transport layer security (TLS), or the like) in an environment where it is difficult to synchronize the first device with the second device without intervention of a server.