Scalable software stack
US-2016335002-A1 · Nov 17, 2016 · US
US11969578B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11969578-B2 |
| Application number | US-202117202845-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 16, 2021 |
| Priority date | Mar 31, 2016 |
| Publication date | Apr 30, 2024 |
| Grant date | Apr 30, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. A method of providing an alert to a user using a mobile computing device, comprising: receiving analyte data from a continuous analyte monitor; determining the analyte data warrants providing an alert to the user; determining an alert level of the alert based on an alert profile of the user; detecting the mobile computing device is in a state inhibiting a first notification type; in response to detecting the mobile computing device is in the state inhibiting the first notification type, providing the alert via the mobile computing device with a second notification type; determining whether the user has acknowledged the alert provided with the second notification type within a first defined time period; in response to determining the user has not acknowledged the alert via the second notification type within the first defined time period, escalating the alert based on the alert level, wherein escalating the alert comprises overriding the state inhibiting the first notification type; and providing the alert via the mobile computing device with the first notification type. 2. The method of claim 1 , wherein: the alert profile comprises different notification settings for different alert levels, determining the alert level of the alert comprises determining a notification setting for the alert level from the different notification settings for the different alert levels, the determined notification setting indicates that the alert is escalatable, and the escalating is based on the determined notification setting. 3. The method of claim 2 , wherein determining that the alert is escalatable comprises determining an escalating override procedure, the escalating override procedure comprising a sequence of notification types, and wherein the overriding the state inhibiting the first notification type is based on the sequence of notification types. 4. The method of claim 1 , further comprising: determining whether the user has acknowledged the alert provided via the first notification type within a second defined time period; and in response to determining the user has not acknowledged the alert via the first notification type within the second defined time period, further escalating the alert based on the alert level, wherein further escalating the alert comprises providing the alert via a third notification type. 5. The method of claim 1 , wherein the state inhibiting the first notification type is a muted state, a low volume state, or a do not disturb mode. 6. The method of claim 1 , wherein the first notification type is a high-volume audible notification type and the second notification type is a low-volume audible notification type. 7. The method of claim 1 , wherein the first notification type is an audible notification type and the second notification type is a haptic notification type. 8. A mobile computing device, comprising: a memory comprising executable instructions; a processor in data communication with the memory and configured to execute the instructions to: receive analyte data from a continuous analyte monitor; determine the analyte data warrants providing an alert to a user; determine an alert level of the alert based on an alert profile of the user; detect the mobile computing device is in a state inhibiting a first notification type; in response to detecting the mobile computing device is in the state inhibiting the first notification type, providing the alert via the mobile computing device with a second notification type; determine whether the user has acknowledged the alert provided with the second notification type within a first defined time period; in response to determining the user has not acknowledged the alert via the second notification type within the first defined time period, escalating the alert based on the alert level, wherein escalating the alert comprises overriding the state inhibiting the first notification type; and provide the alert via the mobile computing device with the first notification type. 9. The mobile computing device of claim 8 , wherein: the alert profile comprises different notification settings for different alert levels, determining the alert level of the alert comprises determining a notification setting for the alert level from the different notification settings for the different alert levels, the determined notification setting indicates that the alert is escalatable, and the escalating is based on the determined notification setting. 10. The mobile computing device of claim 9 , wherein determining that the alert is escalatable comprises determining an escalating override procedure, the escalating override procedure comprising a sequence of notification types, and wherein the overriding the state inhibiting the first notification type is based on the sequence of notification types. 11. The mobile computing device of claim 8 , wherein the processor is further configured to execute the instructions to: determine whether the user has acknowledged the alert provided via the first notification type within a second defined time period; and in response to determining the user has not acknowledged the alert via the first notification type within the second defined time period, further escalate the alert based on the alert level, wherein further escalating the alert comprises providing the alert via a third notification type. 12. The mobile computing device of claim 8 , wherein the state inhibiting the first notification type is a muted state, a low volume state, or a do not disturb mode. 13. The mobile computing device of claim 8 , wherein the first notification type is a high-volume audible notification type and the second notification type is a low-volume audible notification type. 14. The mobile computing device of claim 8 , wherein the first notification type is an audible notification type and the second notification type is a haptic notification type. 15. A non-transitory computer readable medium comprising instructions for causing a mobile computing device to perform a method of alerting a user, the method comprising: receiving analyte data from a continuous analyte monitor; determining the analyte data warrants providing an alert to a user; determining an alert level of the alert based on an alert profile of the user; detecting the mobile computing device of the user is in a state inhibiting a first notification type; in response to detecting the mobile computing device is in the state inhibiting the first notification type, providing the alert via the mobile computing device with a second notification type; determining whether the user has acknowledged the alert provided with the second notification type within a first defined time period; in response to determining the user has not acknowledged the alert via the second notification type within the first defined time period, escalating the alert based on the alert level, wherein escalating the alert comprises overriding the state inhibiting the first notification type; and providing the alert via the mobile computing device with the first notification type. 16. The non-transitory computer readable medium of claim 15 , wherein: the alert profile comprises different notification settings for different alert levels, determining the alert level of the alert comprises determining a notification setting for the alert level from the different notification settings for the different alert levels, the determined notification setting indicates that the alert is escalatable, and the escalating is based on the determined no
using feedback of body parameters, e.g. blood-sugar, pressure (measurement of body parameters A61B5/00) · CPC title
for measuring glucose, e.g. by tissue impedance measurement · CPC title
combined with drug delivery · CPC title
using sound · CPC title
using visual displays (displays for heart-related electrical signals, e.g. ECG, A61B5/339) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.