Medical Device Key Distribution via Intermediary Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Medical devices like infusion pumps face challenges in securely distributing security keys due to limited computational and memory capabilities, making it difficult to implement complex encryption algorithms for secure communication with servers.
Innovation Solution
A method and system that utilize a computing device to retrieve and transmit security keys from a server to a medical device via a secured communication link, leveraging asymmetric-key algorithms for key distribution and symmetric-key algorithms for encryption, allowing for secure communication and authentication without requiring extensive computational power on the medical device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If complex cryptographic algorithms (such as HTTPS) are used for data protection, then security is improved, but computational power and energy consumption requirements increase
Solution Approach 1:
The cryptographic system is segmented into two distinct components: asymmetric-key algorithms for key distribution and symmetric-key algorithms for data encryption. This segmentation allows each component to use the most appropriate algorithm type for its specific function, reducing overall computational burden on the medical device.
Solution Approach 2:
A server acts as an intermediary that generates and distributes security keys to medical devices. The server performs the computationally intensive asymmetric-key operations, while medical devices only need to perform simpler symmetric-key operations for actual data encryption, thus reducing the computational requirements at the device level.
2Reliability
If asymmetric-key algorithms are used for key distribution, then security is improved, but device complexity increases
Solution Approach 1:
The system segments the cryptographic functionality: the server handles complex asymmetric-key operations for key generation and distribution, while medical devices use simpler symmetric-key operations for data protection. This segmentation reduces the complexity burden on resource-constrained medical devices.
Solution Approach 2:
The server automatically generates and distributes security keys to medical devices without requiring complex key management infrastructure at the device level. The medical device simply receives and uses the provided keys, eliminating the need for sophisticated local key generation and management capabilities.
3Power
If symmetric-key algorithms are used for encryption, then computational requirements are reduced, but key distribution vulnerability increases
Solution Approach 1:
The system employs asymmetric-key algorithms specifically for the key distribution phase, where security is most critical. The asymmetric nature provides inherent security advantages during key exchange, while symmetric-key algorithms are used only for data encryption where computational efficiency is prioritized.
Solution Approach 2:
Security keys are distributed and established through asymmetric-key algorithms before the actual data encryption process begins. This preliminary secure key distribution ensures that subsequent symmetric-key encryption operations can proceed efficiently without compromising security, as the keys are already securely established.
Data Source
AI summary
A method for key distribution between a server (1) and a medical device (3A, 3B), in particular an infusion device, comprises: providing, at the server (1), a security key (4A, 4B) to be used for a secure data communication of the medical device (3A, 3B); establishing a first communication link (11) between the server (1) and a computing device (2); establishing a second communication link (30A, 30B) between the computing device (2) and the medical device (3A, 3B); retrieving, by the computing device (2), the security key (4A, 4B) from the server (1) via the first communication link (11); and transmitting, by the computing device (2), the retrieved security key (4A, 4B) to the medical device (3A, 3B) via the second communication link (30A, 30B). In this way a method for the security key distribution between a server and a medical device is provided, the method being suitable even for medical devices having low computational and memory capabilities.