MOBILE VIRTUALIZATION PLATFORM FOR THE REMOTE CONTROL OF A MEDICAL DEVICE

• US 20140298022A1
• Filed: 10/26/2012
• Published: 10/02/2014
• Est. Priority Date: 10/28/2011
• Status: Active Grant

• Current Assignee: Debiotech S.A.
• Original Assignee: Debiotech S.A.
• Inventors: Proennecke, Stephan, Neftel, Frdric, Francois, Oscar
• Granted Patent: US 9,967,739 B2
• Time in Patent Office: Days
• US Class Current: 713/168
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: H04L 2209/88 Medical equipments
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04W 12/43 using shared identity modules, e.g. SIM sharing
• CPC Class Codes: H04W 12/45 using multiple identity modules
• CPC Class Codes: H04W 12/50 Secure pairing of devices
• CPC Class Codes: H04W 12/55 involving three or more devices, e.g. group pairing

Abstract

The invention concerns a medical assembly which insures a secured communication between a medical device (like a insulin pump) and its remote control which manages the medical device. To this effect, said assembly use an external microcontroller (MCU) which contains the secured data and uses a cryptographic mechanism to communicate with the medical device. One single external microcontroller (MCU) is paired with only one medical device in such a way the patient can change several times of remote device although aware that the re mote device, in which said external protected MCU is inserted, is the single remote device paired with the medical device. In said assembly, said medical device and said external microcontroller (MCU) comprise secured memories which contain the wireless communication configuration in such a way the devices know in advance the good configuration.

Claims

1. A medical device which communicates securely with a remote control comprising:

A communication means permitting a wireless communication with a remote control,

An internal secured memory which contains the key information to secure said communication,

Wherein said medical device is already paired with only one microcontroller (MCU) which comprises a secured memory which further contains said key information.

Wherein said MCU is designed to be plugged in a remote control

2. A medical device according to claim 1, wherein said MCU is designed in such a way to pair and/or to encrypt the communication between said medical device and said remote control in which said MCU is plugged.

3. A medical device according to claim 1, wherein the key information contains the wireless communication configuration and/or the encryption parameters.

4. A medical device according to claim 1, wherein said medical device and/or said MCU contains secured processing means.

14. Use of a MCU as defined in claim 1 for pairing the remote control with the medical device comprising the following step:

Said MCU uses said wireless communication configuration for connecting the medical device with the remote control,

Said medical device uses said wireless communication configuration to be connected with the remote control.

15. Use of a MCU according to claim 14 further comprising the following step:

Said MCU and said medical device use a cryptographic mechanism to authenticate the connection.

16. Use of a MCU as defined claim 1 wherein said MCU further checks the integrity of the virtual platform and operating system(es) which is loaded in said remote control.

17. Use of a MCU as defined in claim 1 wherein an application is loaded from the MCU to the internal memory of the remote control and is running by said remote control.

29. Use of an MCU as defined in claim 1 with a loopback mechanism comprising the following step:

Done by the embedded software in the medical device;

Write the parameters that must be acknowledge in the secured memory in the medical device

Generate a challenge

Encrypt said parameters by using a temporary key Ks1

Indicate to the user that the medical device and remote control is in loopback mode by means of a vibration, sound, LED or any other method that informs the patient.

Send the encrypted parameters to the remote control

Done by the embedded software in the remote control

Send the encrypted parameters to the additional MCU.

Done by the embedded software in the additional MCU 4

Receive and write the encrypted parameters and the challenge to the secured memory area of the additional MCU.

Decrypt the parameters by using the key Ks1.

Send the decrypted parameters and the challenge to the memory of the remote control

Done by the embedded software in the remote control

Display the decrypted parameters in a “

Summary”

page.

Prompt the user to enter the authentication means of the user.

Build the acknowledgement ticket that will confirm the acceptance of these parameters by using the challenge, the parameters and said entered authentication means.

Write the ticket in secured memory area of the remote control.

Send said ticket to the additional MCU

Done by the embedded software in the additional MCU

Receive and write said ticket to the secured memory area of the additional MCU

Encrypt said ticket by using a temporary key Ks2

Send said encrypted ticket back to remote control

Done by the embedded software in the remote control

Send the encrypted ticket back to the medical device.

Done by the embedded software in the medical device

Calculate the expected ticket

Receive, decrypt and validate the acknowledgement ticket coming from the remote control.

When the ticket is validated the loopback process is closed and the medical device is allowed to use the updated parameters.

30. Use of a loopback mechanism according to the claim 29 wherein authentication means of the user may be a PIN Code, use a fingerprint reader or fingerprint retinal.

31. Use of assembly medical as defined in claim 1 using:

A loopback mechanism, and/or;

A virtualization platform, and/or;

An additional MCU-,

5. A medical assembly suitable for establishing a secured communication between a medical device and a remote control-comprising:

A remote control which comprises;

A communication means permitting a wireless communication with said medical device,

A connecting means to plug an additional microcontroller (MCU);

At least one input means,

At least one processor which is connected to said communication means, said connecting means and said input means;

A medical device which comprises;

A communication means permitting a wireless communication with said remote control,

An internal secured memory;

An MCU which is designed to be connected to said remote control;

said MCU further comprises a secured memory;

Wherein at least one medical device is exclusively paired with only one MCU;

Wherein the internal secured memory of said medical device and the secured memory of said MCU contain the key information to secure the communication.

6. Assembly according to claim 5, wherein the key information contains the wireless communication configuration and/or the encryption parameters.

7. Assembly according to claim 5, wherein said remote control comprises at least one display means.

8. Assembly according to claim 5, wherein said medical device and/or said MCU comprise secured processing means, which secure the communication of data between said medical device and said remote control.

9. Assembly according to claim 8, wherein said MCU keeps in secured memory said secured processing means in such a way that said remote control not access to said secured processing means.

10. Assembly according to claim 5 wherein said MCU may be a Universal Integrated Circuit Card, a Smart Card or a SIM Card or SD Card.

11. Assembly according to claim 5 wherein said secured memory of said MCU comprises an application which is executed within said MCU and is interfaced with the remote control.

12. Assembly according to claim 5 wherein an application is loaded in the internal memory of the remote control and is running within said remote control.

13. Assembly according to claim 5, wherein said MCU comprises an authentication means to check the integrity of said application.

18. A virtualization platform comprising:

a host operating system (hOS) emulating hardware components for at least one guest operating system (gOS),

a first gOS handling common functions such as but not limited to calendar or contacts, all those common functions being designed to be used in an uncontrolled environment,

a medical operating system (mOS) handling remote control functions for a medical device all those remote control functions being designed to be used in a controlled environment.

19. A virtualization platform according to claim 18 wherein said virtualization platform may be used by a remote control.

20. A virtualization platform according to claim 18 wherein said mOS constitutes another gOS.

21. A virtualization platform according to claim 18 wherein said first gOS is also handling wireless communication such as but not limited to web browsing or phone communication.

22. A virtualization platform to claim 18, wherein the mOS and/or hOS controls and blocks the application running in the gOS.

23. A virtualization platform to claim 18, wherein the mOS and/or hOS controls which application has the focus on the screen of the remote control.

24. A virtualization platform according to claim 18, wherein the remote control includes an indicator which signals to the user that the current application is running in the controlled environment.

25. A virtualization platform according to claim 24, wherein said indicator may be a LED, a part of said screen, another screen, a specific sound or a vibrator.

26. Use of a virtualization platform as defined in claim 18 with a loopback mechanism comprising the following steps:

Done by the embedded software in the medical device

Write the parameters that must be acknowledged in the secured memory area of the medical device

Generate a challenge

Open a secure pipe between the medical device and the mobile device

Indicate to the user that the medical device and remote control is in loopback mode by means such as a vibration, sound, LED or any other method that informs the patient.

Send the parameters encrypted by using an encryption key KP and the challenge to the mobile device.

Done by the software entity 1 in the remote control

Receive and write the encrypted parameters and the challenge to the secured memory area of the mobile device.

Done by the software entity 2 in the remote control

Decrypt the parameters by using the key KRC, which is the corresponding key to KP. These keys can be symmetric or asymmetric. The authorized application is validated by having the correct corresponding key KRC.

Display the decrypted parameters in a “

Summary”

page.

Enter the authentication means of the user.

Build the acknowledgement ticket that will confirm the acceptance of these parameters by using the challenge, the key KRC and said entered authentication means.

Write the ticket in secured memory area of the mobile device.

Done by the software entity 1 in the remote control

Send this ticket back to the medical device.

Done by the embedded software in the medical device

Calculate the expected ticket

Receive and validate the acknowledgement ticket coming from the mobile device

When the ticket is validated the loopback process is closed and the medical device allowed to use the updated parameters.

27. Use of a virtualization platform according to the claim 26 wherein authentication means of the user may be a PIN Code, use a fingerprint reader or fingerprint retinal.

28. Use of a virtualization platform according to claim 18 wherein the user has to enter a PIN code to confirm the entrance in loopback mechanism, such PIN code being entered on a random displayed array.