Terminal Device Session Key Distribution via Management Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current encryption communication methods, such as SIP+SRTP, fail to update session keys during a session, are protocol-dependent, and are not suitable for multi-party communications like conference calls, limiting their effectiveness in securing communications against large-scale eavesdropping.
Innovation Solution
A terminal device in a server-client system that includes a key distribution management device and an authentication information database, allowing terminal devices to share a session key through an authentication-based multipoint key distribution algorithm, enabling key updates and multi-party communication without relying on existing servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If key exchange is performed only at the start of a session using existing protocols, then the communication setup is simple, but the session key cannot be updated during the session, reducing security
Solution Approach 1:
The patent implements periodic key exchange during the session using timestamp-based key update requests. The key management server receives key update requests from clients at specific time intervals, generating new session keys periodically to maintain security without requiring complete session re-establishment.
Solution Approach 2:
The patent introduces a key management server as an intermediary between clients to handle key distribution and updates. This mediator manages the complex key exchange process centrally, allowing clients to simply request and receive updated keys without implementing complex key exchange protocols themselves.
2Adaptability or versatility
If key exchange is embedded in protocol-specific messages, then the integration is tight, but the message format becomes dependent on a certain protocol, reducing versatility
Solution Approach 1:
The patent separates the key exchange function from protocol-specific messages by creating dedicated key management messages (key exchange requests, key update requests, key release requests) that are independent of application layer protocols. This segmentation allows the same key management infrastructure to serve multiple different communication protocols.
Solution Approach 2:
The key management server is designed with universal functionality to handle key distribution for multiple different protocols and application types. It processes various request types (initial key exchange, periodic updates, key release) in a unified manner, making the system adaptable to different communication scenarios without protocol-specific customization.
3Adaptability or versatility
If existing one-to-one encryption protocols are used, then the implementation is straightforward, but they are not available for communication among more than one-to-one parties, limiting functionality
Solution Approach 1:
The patent uses a key management server as a central intermediary to distribute session keys to multiple clients participating in a conference call or group communication. The server receives key update requests and distributes updated keys to all authorized participants, enabling multi-party secure communication without requiring direct peer-to-peer key exchange between all participants.
Solution Approach 2:
The patent implements a feedback mechanism where the key management server tracks which clients have received key updates and manages key distribution state. This feedback system allows the server to coordinate key updates across multiple participants efficiently, ensuring all parties have the current session key without requiring complex distributed consensus protocols.
Data Source
AI summary
To provide a terminal device that can share a session key for use in encryption communication with multiple terminal devices at a certain timing without relying on an existing server device. The terminal device includes: a list/request sending unit that, when the terminal device operates as an owner device, generates a key distribution request, signs the key distribution request, and transmits the key distribution request to a key distribution management device; a participation request sending unit that, when the terminal device operates as a general device, generates a participation request, signs the participation request, and transmits the participation request to the key distribution management device; a session key generating unit that executes an authentication-based multipoint key distribution algorithm of server-client type in cooperation with another terminal device participating in the session and with the key distribution management device to generate a session key; and a post-confirmation unit that, when the session key has been normally generated, transmits a success notice to the key distribution management device and receives a collective notice from the key distribution management device.