Videoconference Meeting Key Exchange for Secure Participant Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing videoconferencing systems lack secure methods for handling participant joining and leaving with end-to-end encryption, as the video conference provider's servers may not be trusted by participants, potentially exposing confidential information.
Innovation Solution
Participants generate short-term encryption keypairs and meeting keys, using long-term public keys for authentication and encryption, ensuring only authorized participants can access meeting content without revealing keys to the video conference provider.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the video conference provider's servers are used to handle participant joining and leaving, then the system is easier to operate and manage, but the security and confidentiality of meeting keys cannot be guaranteed as servers may not be trusted
Solution Approach 1:
The patent introduces an intermediary key exchange mechanism where participants exchange encrypted meeting keys through a trusted intermediary process. The leader participant encrypts the meeting key with each participant's public key and transmits it through the video conference provider's server without the server being able to decrypt it. This allows the server to facilitate key distribution while maintaining end-to-end encryption security.
Solution Approach 2:
The patent segments the key management process into distinct phases: key generation by individual participants, key encryption by the leader participant, secure key transmission through the server, and key decryption by recipient participants. This segmentation allows the server to handle only the transmission of encrypted data rather than managing decryption, thereby maintaining both ease of operation and security.
2Reliability
If end-to-end encryption is implemented with individual key management for each participant, then security and confidentiality are improved, but the system complexity increases
Solution Approach 1:
The patent implements a universal key management approach where the leader participant performs multiple functions: generating the meeting key, encrypting it with each participant's public key, and managing the distribution process. This multi-functional role consolidates complex key management tasks into a single participant's responsibilities, reducing overall system complexity while maintaining end-to-end encryption security.
Solution Approach 2:
The patent creates encrypted copies of the meeting key for each participant individually. The leader participant encrypts the same meeting key multiple times using different public keys, creating participant-specific encrypted key copies. This copying mechanism simplifies key distribution by allowing the server to transmit the same encrypted data to multiple participants without increasing cryptographic complexity.
3Reliability
If meeting keys are updated when participants join or leave, then security is maintained against unauthorized access, but the frequency of key operations increases system load
Solution Approach 1:
The patent implements dynamic key management where the meeting key is updated based on real-time participant changes. When a participant joins or leaves, the leader participant generates a new meeting key and redistributes it to current participants. This dynamic approach maintains security by ensuring that participants who leave cannot access future meetings, while the key updates are triggered only by actual participant changes rather than continuously.
Solution Approach 2:
The patent changes the meeting key parameter in response to participant lifecycle events. The key remains static during the meeting to minimize computational overhead, but is changed (updated) only when necessary due to participant joining or leaving. This parameter change strategy balances security requirements with energy efficiency by avoiding unnecessary key operations.
Data Source
AI summary
One disclosed example method includes a leader client device associated with a leader participant generating a meeting key for a video meeting joined by multiple participants. For each participant, the leader client device obtains a long-term public key and a cryptographic signature associated with the participant. The leader client device verifies the cryptographic signature of the participant based on the long-term public key and the cryptographic signature. If the verification is successful, the leader client device encrypts the meeting key for the participant using a short-term private key generated by the leader client device, a short-term public key of the participant, a meeting identifier, and a user identifier identifying the participant. The leader client device further publishes the encrypted meeting key for the participant on the meeting system. The leader client device encrypts and decrypts meeting data communicated with other participants based on the meeting key.