IP Library Granted Patent US 12,519,795
Granted Patent B2
US 12,519,795 · App. 18/605,607 · Granted Jan 6, 2026

Diabetes management partner interface for wireless communication of analyte data

Inventors: Apurv Ullas Kamath (San Diego, CA); Michael Robert Mensinger (San Diego, CA); Nicholas Polytaridis (San Diego, CA); Gary A. Morris (San Marcos, CA); Alexandra Elena Constantin (San Jose, CA); Douglas William Burnette (San Diego, CA); Mario Remon (Hallandale Beach, FL); Jorge R. Barreras (Dania Beach, FL); Benjamin Elrod West (San Diego, CA); Christopher Robert Hannemann (San Diego, CA)
Assignee: Dexcom, Inc.
H04L63/101A61B5/14532A61B5/686G16H10/60G16H10/65G16H50/20H04W12/06H04W52/0277H04W76/14A61B5/0002A61B5/0004A61B5/14503A61B5/14546A61B5/1495A61B5/486A61B5/7445A61B5/746H04L2209/88H04W4/38H04W4/80
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,519,795
App. No.
18/605,607
Granted
Jan 6, 2026
Kind
B2
Abstract

Systems, devices, and methods are disclosed for wireless communication of analyte data. In embodiments, a method of using a diabetes management partner interface to configure an analyte sensor system for wireless communication with a plurality of partner devices is provided. The method includes the analyte sensor system receiving authorization to provide one of the partner devices with access to a set of configuration parameters via the diabetes management partner interface. The set of configuration parameters is stored in a memory of the analyte sensor system. The method also includes, responsive to input received from the one partner device via the diabetes management partner interface, the analyte sensor system setting or causing a modification to the set of configuration parameters, according to a system requirement of the one partner device.

Claims (53)

1 . A method, performed by an analyte sensor system, for wireless communication, comprising:

establishing a first wireless connection with a first partner device, wherein establishing the first wireless connection with the first partner device causes:

a sensor session to be established for generating analyte data; and

a first identifier of the first partner device to be added to a whitelist, stored in the analyte sensor system, of devices that are permitted to wirelessly communicate with the analyte sensor system;

receiving an indication to remove the first identifier of the first partner device from the whitelist stored in the analyte sensor system;

removing the first identifier of the first partner device from the whitelist stored in the analyte sensor system in response to receiving the indication to remove the first identifier;

adding a second identifier of a second partner device to the whitelist after removing the first identifier of the first partner device; and

establishing a second wireless connection with the second partner device based on the second identifier being added to the whitelist.

2 . The method of claim 1 , wherein receiving the indication to remove the first identifier of the first partner device from the whitelist is based on an ending of a partner device session associated with the first partner device.

3 . The method of claim 2 , further comprising indicating to a user of the analyte sensor system that the partner device session associated with the first partner device is expected to end prior to the ending of the partner device session.

4 . The method of claim 3 , wherein indicating to the user of the analyte sensor system that the partner device session associated with the first partner device is expected to end comprises indicating to the user of the analyte sensor system that the partner device session associated with the first partner device is expected to end approximately 12 hours before the ending of the partner device session.

5 . The method of claim 2 , wherein the partner device session is approximately three days.

6 . The method of claim 2 , wherein the partner device session is different from the sensor session.

7 . The method of claim 1 , wherein the indication to remove the first identifier of the first partner device is received from a display device.

8 . The method of claim 7 , further comprising:

performing, after establishing the first wireless connection with the first partner device, analyte measurements associated with a user of the analyte sensor system; and

periodically transmitting analyte data, indicative of the analyte measurements, to a display device for display to the user.

9 . The method of claim 1 , wherein receiving the indication to remove the first identifier of the first partner device from the whitelist is based on a battery level associated with the first partner device.

10 . The method of claim 9 , wherein the indication to remove the first identifier of the first partner device from the whitelist is received when the battery level associated with the first partner device is less than or equal to a threshold.

11 . The method of claim 1 , wherein adding the second identifier of the second partner device comprises transmitting one or more advertisement messages to the second partner device.

12 . An analyte sensor system, comprising:

one or more processors configured to execute instructions stored on one or more memories to cause the analyte sensor system to:

establish a first wireless connection with a first partner device, wherein, based on the establishment of the first wireless connection with the first partner device, the one or more processors are further configured to cause the analyte sensor system to:

establish a sensor session for generating analyte data; and

add a first identifier of the first partner device to a whitelist, stored in the analyte sensor system, of devices that are permitted to wirelessly communicate with the analyte sensor system;

receive an indication to remove the first identifier of the first partner device from the whitelist stored in the analyte sensor system;

remove the first identifier of the first partner device from the whitelist stored in the analyte sensor system in response to reception of the indication to remove the first identifier;

add a second identifier of a second partner device to the whitelist after removal of the first identifier of the first partner device; and

establish a second wireless connection with the second partner device based on the second identifier being added to the whitelist.

13 . The analyte sensor system of claim 12 , wherein the one or more processors are configured to cause the analyte sensor system to receive the indication to remove the first identifier of the first partner device from the whitelist based on an ending of a partner device session associated with the first partner device.

14 . The analyte sensor system of claim 13 , wherein:

the one or more processors are further configured to cause the analyte sensor system to indicate to a user of the analyte sensor system that the partner device session associated with the first partner device is expected to end prior to the ending of the partner device session; and

in order to indicate to the user of the analyte sensor system that the partner device session associated with the first partner device is expected to end, the one or more processors are configured to cause the analyte sensor system to indicate to the user of the analyte sensor system that the partner device session associated with the first partner device is expected to end approximately 12 hours before the ending of the partner device session.

15 . The analyte sensor system of claim 13 , wherein the partner device session is approximately three days.

16 . The analyte sensor system of claim 13 , wherein the partner device session is different from the sensor session.

17 . The analyte sensor system of claim 12 , wherein:

the indication to remove the first identifier of the first partner device is received from a display device; and

the one or more processors are further configured to cause the analyte sensor system to:

perform, after establishment of the first wireless connection with the first partner device, analyte measurements associated with a user of the analyte sensor system; and

periodically transmit analyte data, indicative of the analyte measurements, to a display device for display to the user.

18 . The analyte sensor system of claim 12 , wherein:

the indication to remove the first identifier of the first partner device from the whitelist is based on a battery level associated with the first partner device; and

the one or more processors are configured to cause the analyte sensor system to receive the indication to remove the first identifier of the first partner device from the whitelist when the battery level associated with the first partner device is less than or equal to a threshold.

19 . The analyte sensor system of claim 12 , wherein, in order to add the second identifier of the second partner device, the one or more processors are configured to cause the analyte sensor system to transmit one or more advertisement messages to the second partner device.

20 . A non-transitory computer readable medium, comprising:

instructions that, when executed by one or more processors of an analyte sensor system, cause the analyte sensor system to:

establish a first wireless connection with a first partner device, wherein, based on the establishment of the first wireless connection with the first partner device, the instructions further cause the analyte sensor system to:

establish a sensor session for generating analyte data; and

add a first identifier of the first partner device to a whitelist, stored in the analyte sensor system, of devices that are permitted to wirelessly communicate with the analyte sensor system;

receive an indication to remove the first identifier of the first partner device from the whitelist stored in the analyte sensor system;

remove the first identifier of the first partner device from the whitelist stored in the analyte sensor system in response to reception of the indication to remove the first identifier;

add a second identifier of a second partner device to the whitelist after removal of the first identifier of the first partner device; and

establish a second wireless connection with the second partner device based on the second identifier being added to the whitelist.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 15, 2024
From: KAMATH, APURV ULLAS; POLYTARIDIS, NICHOLAS; MORRIS, GARY A.; CONSTANTIN, ALEXANDRA E.; BURNETTE, DOUGLAS WILLIAM; REMON, MARIO; BARRERAS, JORGE R.; WEST, BENJAMIN ELROD; HANNEMANN, CHRISTOPHER R.
To: DEXCOM, INC.
Reel/Frame 066780/0140 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 15, 2024
From: MENSINGER, MICHAEL R.
To: DEXCOM, INC.
Reel/Frame 066781/0540 →
Continuity (6)
Continuation 18484256 · Oct 10, 2023
Continuation 17661739 · May 2, 2022
Continuation 16169886 · Oct 24, 2018
Continuation 16169661 · Oct 24, 2018
Provisional Application 62579061 · Oct 30, 2017
Related Publication 20240223565A1 · Jul 4, 2024
References Cited (68)
US 5748882A · Huang · 1998 [cited by applicant]
US 7294105B1 · Islam · 2007 [cited by examiner]
US 8579853B2 · Reggiardo et al. · 2013 [cited by applicant]
US 9041730B2 · Johnson et al. · 2015 [cited by applicant]
US 9136973B2 · Huang et al. · 2015 [cited by applicant]
US 9152784B2 · Das et al. · 2015 [cited by applicant]
US 9804148B2 · Hayter · 2017 [cited by examiner]
US D852837S · Mazlish et al. · 2019 [cited by applicant]
US 10426896B2 · Desborough et al. · 2019 [cited by applicant]
US 11153317B2 · Kamath et al. · 2021 [cited by applicant]
US 20050283203A1 · Flaherty et al. · 2005 [cited by applicant]
US 20090076349A1 · Libbus · 2009 [cited by examiner]
US 20100161959A1 · Sood · 2010 [cited by applicant]
US 20110006876A1 · Moberg et al. · 2011 [cited by applicant]
US 20110201911A1 · Johnson · 2011 [cited by examiner]
US 20120096451A1 · Tenbarge et al. · 2012 [cited by applicant]
US 20120322461A1 · Ito et al. · 2012 [cited by applicant]
US 20130191513A1 · Kamen et al. · 2013 [cited by applicant]
US 20140235984A1 · Wilbur et al. · 2014 [cited by applicant]
US 20140369268A1 · Huang et al. · 2014 [cited by applicant]
US 20150018633A1 · Kovachev · 2015 [cited by examiner]
US 20150112264A1 · Kamen · 2015 [cited by examiner]
US 20150205947A1 · Berman · 2015 [cited by examiner]
US 20150207790A1 · Lu et al. · 2015 [cited by applicant]
US 20150221194A1 · Sarkar · 2015 [cited by examiner]
US 20150277845A1 · Kim · 2015 [cited by examiner]
US 20150341438A1 · Sloan · 2015 [cited by examiner]
US 20160055130A1 · Bentley et al. · 2016 [cited by applicant]
US 20160057196A1 · Bentley et al. · 2016 [cited by applicant]
US 20160066843A1 · Mensinger et al. · 2016 [cited by applicant]
US 20160174277A1 · Yoon · 2016 [cited by examiner]
US 20160183854A1 · Lee · 2016 [cited by examiner]
US 20160324463A1 · Simpson et al. · 2016 [cited by applicant]
US 20160328577A1 · Howley · 2016 [cited by examiner]
US 20170055890A1 · Kube · 2017 [cited by examiner]
US 20170080207A1 · Perez et al. · 2017 [cited by applicant]
US 20170173262A1 · Veltz · 2017 [cited by examiner]
US 20170181628A1 · Burnette et al. · 2017 [cited by applicant]
US 20170189614A1 · Mazlish et al. · 2017 [cited by applicant]
US 20170203030A1 · Brewer · 2017 [cited by examiner]
US 20170281000A1 · Wedekind et al. · 2017 [cited by applicant]
US 20180000395A1 · Lucisano · 2018 [cited by examiner]
US 20180047228A1 · Hyde et al. · 2018 [cited by applicant]
US 20180085532A1 · Desborough · 2018 [cited by examiner]
US 20180121610A1 · Cayle · 2018 [cited by examiner]
US 20180125689A1 · Perez · 2018 [cited by examiner]
US 20180144817A1 · Lofgren et al. · 2018 [cited by applicant]
US 20180172664A1 · Love · 2018 [cited by examiner]
US 20180279911A1 · Lucisano · 2018 [cited by examiner]
US 20190116088A1 · Mueglitz · 2019 [cited by examiner]
US 20190125224A1 · Kamath et al. · 2019 [cited by applicant]
US 20190132801A1 · Kamath et al. · 2019 [cited by applicant]
US 20190173885A1 · Kamath et al. · 2019 [cited by applicant]
US 20190246357A1 · Cole · 2019 [cited by examiner]
US 20230293060A1 · Duvall · 2023 [cited by examiner]
CN 107073207A · 2017 [cited by applicant]
EP 3704912A1 · 2020 [cited by applicant]
JP 2009535715A · 2009 [cited by applicant]
JP 2017503619A · 2017 [cited by applicant]
JP 7293217B2 · 2023 [cited by applicant]
WO 2016207206A1 · 2016 [cited by applicant]
Konstantia Zarkogianni; A Review of Emerging Technologies for the Management of Diabetes Mellitus; IEEE:2015; pp. 2735-2749. [cited by examiner]
Domingo-Lopez D. A., et al., “Medical Devices, Smart Drug Delivery, Wearables and Technology for the Treatment of Diabetes Mellitus”, Advance Drug Delivery Reviews, Science direct, vol. 185, Jun. 2022, pp. 1-5. [cited by applicant]
Fortino G., et al., “BodyCloud: Integration of Cloud Computing and Body Sensor Networks,” 2012, IEEE 4th International Conference on Cloud Computing Technology Science, 2012, 6 pages. [cited by applicant]
International Preliminary Report on Patentability for Application No. PCT/US2018/057390 mailed May 14, 2020, 18 pages. [cited by applicant]
International Search Report and Written opinion for Application No. PCT/US2018/057390 mailed Feb. 21, 2019, 20 pages. [cited by applicant]
Nathaniel D., et al., “A Digital Ecosystem of Diabetes Data and Technology: Services, Systems, and Tools Enabled by Wearables, Sensors, and Apps,” Journal of Diabetes Science and Technology, 2016, vol. 10, No. 1, pp. 35… [cited by applicant]
Valavanis E., et al., “MobiShare: Sharing Context-Dependent Data Services from Mobile Sources,” IEEE: 2003, pp. 1-8. [cited by applicant]