Methods for providing an alert or an alarm to a user of a mobile communications device

Patent metadata

Field	Value
Publication number	US-12329932-B2
Application number	US-202418773421-A
Country	US
Kind code	B2
Filing date	Jul 15, 2024
Priority date	Mar 31, 2016
Publication date	Jun 17, 2025
Grant date	Jun 17, 2025

Abstract

Methods, devices and systems are disclosed for inter-app communications between software applications on a mobile communications device. In one aspect, a computer-readable medium on a mobile computing device comprising an inter-application communication data structure to facilitate transitioning and distributing data between software applications in a shared app group for an operating system of the mobile computing device includes a scheme field of the data structure providing a scheme id associated with a target software app to transition to from a source software app, wherein the scheme id is listed on a scheme list stored with the source software app; and a payload field of the data structure providing data and/or an identification where to access data in a shared file system accessible to the software applications in the shared app group, wherein the payload field is encrypted.

First claim

What is claimed is:

1. A mobile communications device, comprising:
a memory comprising a first software module and a second software module;
a processor in data communication with the memory and configured to:
receive, via the second software module, glucose measurements from a glucose monitoring system;
determine, via the first software module, an insulin dosage based on the received glucose measurements, wherein:
the first and second software modules are different software modules;
the first software module is operable to receive patient specific input data and calculate the insulin dosage based on the patient specific input data and the received glucose measurements; and
the second software module is a plug-in for a software application comprising the first software module; and

transmit a command indicative of the determined insulin dosage to an insulin delivery device to cause the insulin delivery device to administer the insulin dosage to a patient.

2. The mobile communications device of claim 1 , wherein the processor is configured to transmit the command via the first software module.

3. The mobile communications device of claim 1 , wherein the processor is further configured to store, via the second software module, the glucose measurements in a shared database.

4. The mobile communications device of claim 3 , wherein the processor is further configured to retrieve, via the first software module, the glucose measurements stored in the shared database.

5. The mobile communications device of claim 1 , wherein:
the memory further comprises a third software module, wherein the first software module, the second software module, and the third software module are different software modules; and
the processor is configured to transmit the command via the third software module.

6. The mobile communications device of claim 5 , wherein the processor is further configured to:
store, via the first software module, the determined insulin dosage; and
retrieve, via the third software module, the determined insulin dosage.

7. The mobile communications device of claim 1 , wherein the processor is further configured to:
generate, via the second software module, a symmetric database key for encryption of a shared database;
encrypt, via the second software module, information in the shared database using the symmetric database key;
create, via the second software module, an encrypted symmetric database key by encrypting a copy of the symmetric database key;
decrypt, via the first software module, the encrypted symmetric database key to obtain the copy of the symmetric database key; and
access, via the first software module, the information in the shared database using the copy of the symmetric database key.

8. The mobile communications device of claim 7 , wherein:
the copy of the symmetric database key is encrypted using a public key of the first software module; and
the encrypted symmetric database key is decrypted using a private key of the first software module.

9. The mobile communications device of claim 1 , wherein the first software module and the second software module communicate using an inter-application communications architecture.

10. The mobile communications device of claim 9 , wherein the inter-application communications architecture comprises a shared file system.

11. The mobile communications device of claim 9 , wherein the inter-application communications architecture comprises a shared database.

12. A method for use by a mobile communications device operable to execute a first software module and a second software module, the method comprising:
receiving, via the second software module, glucose measurements from a glucose monitoring system;
determining, via the first software module, an insulin dosage based on the received glucose measurements, wherein:
the first and second software modules are different software modules;
the first software module is operable to receive patient specific input data and calculate the insulin dosage based on the patient specific input data and the received glucose measurements; and
the second software module is a plug-in for a software application comprising the first software module; and

transmitting a command indicative of the determined insulin dosage to an insulin delivery device to cause the insulin delivery device to administer the insulin dosage to a patient.

13. The method of claim 12 , wherein the transmitting is performed via the first software module.

14. The method of claim 12 , further comprising storing, via the second software module, the glucose measurements in a shared database.

15. The method of claim 14 , further comprising retrieving, via the first software module, the glucose measurements stored in the shared database.

16. The method of claim 12 , wherein:
the transmitting is performed via a third software module stored in a memory of the mobile communications device, and
the third software module is a different software module than the first software module and the second software module.

17. The method of claim 16 , further comprising:
storing, via the first software module, the determined insulin dosage; and
retrieving, via the third software module, the determined insulin dosage.

18. The method of claim 12 , further comprising:
generating, via the second software module, a symmetric database key for encryption of a shared database;
encrypting, via the second software module, information in the shared database using the symmetric database key;
creating, via the second software module, an encrypted symmetric database key by encrypting a copy of the symmetric database key;
decrypting, via the first software module, the encrypted symmetric database key to obtain the copy of the symmetric database key; and
accessing, via the first software module, the information in the shared database using the copy of the symmetric database key.

19. The method of claim 18 , wherein:
the copy of the symmetric database key is encrypted using a public key of the first software module; and
the encrypted symmetric database key is decrypted using a private key of the first software module.

20. A non-transitory computer readable medium comprising instructions that, when executed by a processor, causes the processor to perform a method comprising:
receiving, via a second software module, glucose measurements from a glucose monitoring system;
determining, via a first software module, an insulin dosage based on the received glucose measurements, wherein:
the first and second software modules are different software modules;
the first software module is operable to receive patient specific input data and calculate the insulin dosage based on the patient specific input data and the received glucose measurements; and
the second software module is a plug-in for a software application comprising the first software module; and

transmitting a command indicative of the determined insulin dosage to an insulin delivery device to cause the insulin delivery device to administer the insulin dosage to a patient.

Assignees

• Dexcom Inc

Inventors

• Morris Gary A
• Belliveau Scott M
• Cabrera Jr Esteban
• Davis Anna Leigh
• Draeger Rian W
• Dunn Laura J
• Goldsmith Timothy Joseph
• Hampapuram Hari
• Hannemann Christopher Robert
• Kamath Apurv Ullas
• Koehler Katherine Yerre
• McBride Patrick Wile
• Mensinger Michael Robert
• Pascual Francis William
• Pellouchoud Philip Mansiel
• Polytaridis Nicholas
• Pupa Philip Thomas
• Shoemaker Kevin
• Smith Brian Christopher
• West Benjamin Elrod
• Wiley Atiim Joseph

Classifications

• H04L9/30

  Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy · CPC title

• H04L9/14

  using a plurality of keys or algorithms · CPC title

• H04L9/0861

  Generation of secret information including derivation or calculation of cryptographic keys or passwords · CPC title

• H04L9/0822

  using key encryption key · CPC title

• H04L9/0637

  Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM] · CPC title