Communication system for pairing user devices with medical devices

• US 10,750,004 B2
• Filed: 12/18/2017
• Issued: 08/18/2020
• Est. Priority Date: 05/14/2015
• Status: Active Grant

• Current Assignee: Invoy Holdings, Inc.
• Original Assignee: Invoy Holdings, Inc.
• Inventors: Ahmad, Salman, Smith, Zachary, Ahmad, Lubna
• Primary Examiner(s): Urban, Edward F
• Assistant Examiner(s): Mathew, Max
• Application Number:
  US15/845,997
• Publication Number:
  US 20180270340A1
• Time in Patent Office: 974 Days
• CPC Class Codes: A61B 2562/08 Sensors provided with means for identification, e.g. barcodes or memory chips
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: A61B 5/024 Detecting, measuring or recording pulse rate or heart rate A61B5/0205, A61B5/021 take precedence
• CPC Class Codes: A61B 5/082 Evaluation by breath analysis, e.g. determination of the chemical composition of exhaled breath A61B5/083, A61B5/091 take precedence
• CPC Class Codes: A61B 5/4806 Sleep evaluation A61B5/4821 takes precedence; devices for inducing sleep A61M21/02
• CPC Class Codes: A61B 5/681 Wristwatch-type devices
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: H04M 1/72412 using two-way short-range wireless interfaces
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 76/11 Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/14 Direct-mode setup
• CPC Class Codes: H04W 8/005 Discovery of network devices, e.g. terminals
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks
• CPC Class Codes: H04W 88/04 adapted for relaying to or from another terminal or user
• CPC Class Codes: H05K 999/99 dummy group

Abstract

A user device and a breath analysis device (or other types of portable devices) use a pairing and communication protocol that address user convenience and connectivity issues. For example, a breath analysis device is associated with a unique identifier and the unique identifier is associated with an account corresponding to the user. Likewise, a user device is associated with a user device identifier and the user device identifier is associated with the account corresponding to the user. The breath analysis device and the user device can use at least one of the identifiers to determine whether the user device is authorized to pair with the breath analysis device, and vice-versa. If authorized, the breath analysis device and user device can pair with one another. Once paired, the user device may wirelessly communicate with the breath analysis device for various purposes, such as to retrieve and display breath analysis test results.

Claims

1. A system, comprising:

a portable medical device configured to generate medical measurement data, the portable medical device having a memory that stores an identifier of the portable medical device, the portable medical device further comprising a Bluetooth transceiver;

a server system that stores account information of a user to which the portable medical device is assigned, the account information associating the identifier of the portable medical device with an account of the user; and

a mobile application configured to run on a smartphone, the mobile application configured to communicate with the portable medical device using a Bluetooth transceiver of the smartphone, and configured to communicate with the server system using a cellular network;

wherein the portable medical device is configured to transmit, and the mobile application is configured to receive, the identifier of the portable medical device while no Bluetooth pairing exists between the portable medical device and the smartphone; and

wherein the mobile application is configured to determine whether to establish a Bluetooth pairing between the smartphone and the portable medical device based, as least partly, on an outcome of a comparison of the received identifier of the portable medical device to the account information stored by the server system.

2. The system of claim 1, wherein the portable medical device is incapable of communicating directly with the server system, and is configured to use the smartphone as a proxy for communicating with the server system.

3. The system of claim 2, wherein the portable medical device and server system are configured to indirectly communicate with each other via the smartphone with encryption using an encryption key that is not accessible to the smartphone, such that the smartphone cannot decrypt encrypted data passed between the portable medical device and the smartphone.

4. The system of claim 1, wherein the portable medical device is configured to use an encryption key of the server system to generate encrypted data, and to send the encrypted data to the server system via the smartphone, wherein the encryption key is not accessible to the smartphone.

5. The system of claim 1, wherein the server system is configured to use an encryption key of the portable medical device to generate encrypted data, and to send the encrypted data to the portable medical device via the smartphone, wherein the encryption key is not accessible to the smartphone.

6. The system of claim 1, wherein the mobile application is configured to pass an encrypted communication received from the portable medical device to the server system without decrypting the encrypted communication.

7. The system of claim 1, wherein the mobile application, in determining whether to establish a Bluetooth pairing between the smartphone and the portable medical device, is configured to compare the identifier received from the medical device to a medical device identifier received from the server system.

8. The system of claim 1, wherein the medical device is configured to initiate a pairing process in which the Bluetooth pairing is established.

9. The system of claim 1, wherein the mobile application is configured to initiate a pairing process in which the Bluetooth pairing is established.