Medical Device Key Distribution via Computing Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Medical devices with low computational and memory capabilities, such as infusion pumps, face challenges in securely distributing and managing security keys for encrypted communication with servers due to the computational intensity of existing encryption algorithms.
Innovation Solution
A method and system utilizing public key cryptography for secure key distribution, where a computing device with sufficient capabilities receives encrypted security keys from a server via a secure link and transfers them to the medical device using a wired link, eliminating the need for complex encryption on the medical device, and employing key pairs for authentication and encryption.
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 become problematic for medical devices
Solution Approach 1:
The cryptographic system is segmented into two parts: complex asymmetric cryptography (RSA) is used only during the initial key distribution phase, while simpler symmetric cryptography (AES) is used for ongoing message encryption. This segmentation allows medical devices to benefit from high security during key exchange without requiring sustained high computational power during normal operation.
Solution Approach 2:
Complex cryptographic key pair generation and exchange is performed in advance during device setup and configuration, before the medical device begins its primary function. The server generates RSA key pairs and distributes public keys to medical devices beforehand, so that when messages are exchanged during operation, only lightweight symmetric encryption is needed.
2Ease of operation
If symmetric-key algorithms are used for encryption, then computational simplicity is improved, but key distribution security deteriorates
Solution Approach 1:
The server acts as an intermediary that facilitates secure key distribution using asymmetric cryptography. The server generates RSA key pairs for each medical device, securely transmits public keys to devices, and maintains private keys securely. This intermediary approach allows symmetric cryptography to be used between server and device without direct peer-to-peer key exchange vulnerabilities.
Solution Approach 2:
The system uses a composite cryptographic approach combining asymmetric cryptography (RSA for key distribution) and symmetric cryptography (AES for message encryption). Each component plays to its strengths: asymmetric crypto secures the key exchange channel while symmetric crypto provides efficient ongoing encryption, creating a composite security system that overcomes the limitations of either approach alone.
3Reliability
If asymmetric-key algorithms are used for key distribution, then security is improved, but device complexity and computational requirements increase
Solution Approach 1:
The computational burden of asymmetric cryptography is segmented and concentrated in the server, which has unlimited computational resources. The medical device only needs to perform basic asymmetric operations (generating a key pair and exchanging public keys) during setup, then relies on pre-distributed symmetric keys for ongoing communication. This segmentation allows high security without burdening the constrained medical device.
Solution Approach 2:
Each medical device autonomously generates its own RSA key pair during setup, and the server autonomously distributes the public key and configures the symmetric encryption parameters. This self-service approach minimizes manual configuration complexity while maintaining strong security through automated cryptographic key management.
Data Source
Figure 1
Figure 2~3
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.