Diabetes management partner interface for wireless communication of analyte data

Abstract

To provide systems and methods for analyte data communication between multiple devices.SOLUTION: 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 multiple 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, in response to input received from the one partner device via the diabetes management partner interface, the analyte sensor system setting or causing a modification of the set of configuration parameters according to a system requirement of the one partner device.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] INCORPORATION-BY-REFERENCE TO RELATED APPLICATIONS Any and all priority claims identified in the Application Data Sheet, or any amendments thereto, are incorporated herein by reference under 37 CFR 1.57. This application claims the benefit of U.S. Provisional Patent Application No. 62 / 579,061, filed October 30, 2017. The foregoing application is incorporated herein by reference in its entirety and expressly made a part hereof.

[0002] The present disclosure relates generally to interfaces for wireless communication of analyte data collected using an analyte sensor system. More specifically, the present disclosure is directed to systems, methods, apparatus, and devices for using a diabetes management partner interface to improve the flexibility of an analyte sensor system in wireless communication with display devices, medical devices, and / or other (e.g., electronic) devices. [Background technology]

[0003] Diabetes mellitus is a disease in which the pancreas cannot produce enough insulin (type 1, or insulin-dependent) and / or insulin is ineffective (type 2, or non-insulin-dependent). In the diabetic state, the victim suffers from hyperglycemia, which leads to a number of physiological disorders associated with the deterioration of small blood vessels (kidney failure, skin ulcers, or bleeding into the vitreous humor of the eye). A hypoglycemic reaction (low blood sugar) can be precipitated by inadvertent overdosing of insulin or after normal administration of insulin or glucose-lowering drugs accompanied by abnormal exercise or inadequate food intake.

[0004] Traditionally, people with diabetes carry self-monitoring blood glucose (SMBG) monitors, which can require uncomfortable finger-prick techniques. Due to a lack of comfort and convenience, diabetics typically only measure their glucose levels two to four times per day. Unfortunately, these time intervals are so far apart that diabetics may be alerted to a hyperglycemic or hypoglycemic state too late, resulting in dangerous side effects. In fact, not only are diabetics unlikely to obtain SMBG readings in a timely manner, but limitations of traditional methods mean they do not know whether their blood glucose levels are rising (getting high) or falling (getting low).

[0005] As a result, a variety of noninvasive, transdermal (e.g., transcutaneous) and / or implantable electrochemical sensors have been developed to continuously detect and / or quantify blood glucose levels. These devices typically transmit raw or minimally processed data for subsequent analysis at a remote device, which may include a display. The transmission to a wireless display device may be wireless. The remote device can then provide the user with information regarding their blood glucose level. Systems using such implantable sensors may provide the user with more up-to-date information, thereby reducing the risk of the user failing to regulate their blood glucose level. Nevertheless, such systems typically still rely on the user to take action to regulate their blood glucose level, for example, by administering an injection.

[0006] Certain devices have been introduced that automate the regulation of a user's blood glucose level. The introduction of such devices can create interoperability issues with other devices that may be utilized for blood glucose monitoring (e.g., the remote devices described above), especially if, for example, such devices are deployed by different manufacturers. For example, devices introduced for automatic blood glucose level regulation may be subject to specific requirements regarding interference, battery life, accuracy, reliability, etc. Such requirements may not be known in advance by the monitoring device manufacturer and / or, in some cases, may be desirable to change from time to time, including based on ecosystem configurations such as available network connectivity, number of connected devices, etc. Additionally, as more electronic devices become network-enabled, more devices can be used to manage health conditions such as diabetes. However, maintaining synchronized analyte data communication between multiple devices, while useful, is becoming increasingly difficult for users.

[0007] Thus, conventional systems are not well suited to deployment and integration of devices that monitor blood glucose levels with additional devices that regulate blood glucose levels, particularly when such devices are provided by different manufacturers, when such devices communicate wirelessly over different types of communication networks and / or mediums, and when a certain level of flexibility and / or adaptability is desired. Summary of the Invention [Means for solving the problem]

[0008] A first aspect of the present disclosure includes a method for configuring an analyte sensor system for wireless communication with a plurality of partner devices using a diabetes management partner interface. The method includes the analyte sensor system receiving, via the diabetes management partner interface, authorization from one of the partner devices to provide access to a configuration parameter set. The set of configuration parameters is stored in a memory of the analyte sensor system. The method also includes, in response to input received from one of the partner devices via the diabetes management partner interface, the analyte sensor system setting or causing modification of the configuration parameter set according to system requirements of the one of the partner devices.

[0009] In a particular implementation of the first aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the first aspect, one of the partner devices is an automatic insulin delivery device or a manual insulin delivery device.

[0010] In a particular implementation of the first aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the first aspect, the set of configuration parameters includes one or more of a wireless connectivity parameter set, an access control parameter set, and an analyte data parameter set.

[0011] In a particular implementation of the first aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the first aspect, the system requirements are associated with one of: a battery capacity of the one partner device; an accuracy requirement of the one partner device; a communication protocol used by the one partner device; a regulatory requirement applicable to the one partner device; and an expected uptime of the one partner device.

[0012] In a particular implementation of the first aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the first aspect, the wireless connectivity parameter set includes a condition under which a partner device will be removed from a whitelist maintained for the analyte sensor system. In an embodiment, the analyte sensor system setting or causing a modification of the configuration parameter set in response to system requirements of the partner device includes the analyte sensor system setting a condition under which a partner device will be removed from the whitelist when a battery level of the partner delivery device meets a threshold.

[0013] In particular implementations of the first aspect, which may be generally applicable but also particularly applicable in relation to any other implementations of the first aspect, the wireless connectivity parameter set includes an advertisement structure. In embodiments, the analyte sensor system setting or causing modification of the configuration parameter set in response to system requirements of one partner device includes the analyte sensor system setting or modifying the advertisement structure using a diabetes management partner interface.

[0014] In a particular implementation of the first aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the first aspect, the access control parameter set includes one or more of the number of display devices to which the analyte sensor system may be connected and the level of access or control that the analyte sensor system may grant to one or more of the display devices.

[0015] In particular implementations of the first aspect, which may be generally applicable but also particularly applicable in conjunction with any other implementations of the first aspect, the analyte data parameter set includes a calibration period for the analyte sensor system. In embodiments, the analyte sensor system setting or causing modification of the configuration parameter set in response to system requirements of one partner device includes the analyte sensor system setting or modifying the calibration period using a diabetes management partner interface.

[0016] In particular implementations of the first aspect, which may be generally applicable but also particularly applicable in conjunction with any other implementations of the first aspect, the analyte data parameter set includes a factory calibration code. In embodiments, the analyte sensor system receives, using a diabetes management partner interface, an indication from a partner device in accordance with system requirements of the partner device that uses the factory calibration code. Setting or causing modification of the configuration parameter set in accordance with system requirements of the partner device by the analyte sensor system may include the analyte sensor system setting or modifying a calibration period to zero or none using the diabetes management partner interface.

[0017] In a particular implementation of the first aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the first aspect, the wireless connectivity parameter set includes a setting on a remote server. Setting or causing a modification of the configuration parameter set in response to system requirements of one partner device by the analyte sensor system may include configuring the analyte sensor to perform several operations using a diabetes management partner interface. Such operations may include using a service provided via the remote server. Such operations may include transmitting diabetes management feedback to one or more display devices connected to the analyte sensor system in response to the service provided via the remote server. Such operations may include disabling use of the service and sending an associated notification to a display device connected to the analyte sensor system if the service provided via the remote server becomes unavailable.

[0018] In particular implementations of the first aspect, which may be generally applicable but also particularly applicable in conjunction with any other implementations of the first aspect, the analyte date parameter set includes bolus calculation parameters. In embodiments, the analyte sensor system setting or causing modification of the configuration parameter set in response to system requirements of one partner device includes the analyte sensor system providing access to the bolus calculation parameters to one partner device using a diabetes management partner interface. In embodiments, the method also includes the analyte sensor system providing a bolus recommendation based on calculations performed using the bolus calculation parameters.

[0019] A second aspect of the present disclosure includes an analyte sensor system for wireless communication with multiple partner devices. The analyte sensor system is configurable through use of a diabetes management partner interface. The analyte sensor system includes an analyte sensor used to generate analyte information. The analyte sensor system includes a transceiver adapted to transmit and receive wireless signals. Further, the analyte sensor system includes a memory that stores a configuration parameter set used by the transceiver to transmit and receive the wireless signals. The analyte sensor system also includes circuitry operatively coupled to the transceiver and the memory and adapted to cause the analyte sensor system to perform several operations. Such operations include receiving, via the diabetes management partner interface, authorization from one of the partner devices to provide access to the configuration parameter set. Such operations include setting or causing modification of the configuration parameter set according to system requirements of the partner device in response to input received from one of the partner devices via the diabetes management partner interface.

[0020] In a particular implementation of the second aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the second aspect, one of the partner devices is an automatic insulin delivery device or a manual insulin delivery device.

[0021] In a particular implementation of the second aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the second aspect, the set of configuration parameters includes one or more of a wireless connectivity parameter set, an access control parameter set, and an analyte data parameter set.

[0022] In a particular implementation of the second aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the second aspect, the system requirements are associated with one of: a battery capacity of the one partner device; an accuracy requirement of the one partner device; a communication protocol used by the one partner device; a regulatory requirement applicable to the one partner device; and an expected uptime of the one partner device.

[0023] In a particular implementation of the second aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the second aspect, the wireless connectivity parameter set includes a condition under which a partner device will be removed from a whitelist maintained for the analyte sensor system. In an embodiment, the circuitry is further adapted to cause the analyte sensor system to set a condition, according to a system requirement of the partner device, such that a battery level of the partner delivery device meets a threshold value and the partner device will be removed from the whitelist.

[0024] In particular implementations of the second aspect, which may be generally applicable but also particularly applicable in relation to any other implementations of the second aspect, the wireless connectivity parameter set includes an advertisement structure. In embodiments, the circuitry is further adapted to cause the analyte sensor system to set or modify the advertisement structure using a diabetes management partner interface.

[0025] In a particular implementation of the second aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the second aspect, the access control parameter set includes one or more of the number of display devices to which the analyte sensor system may be connected and the level of access or control that the analyte sensor system may grant to one or more of the display devices.

[0026] In particular implementations of the second aspect, which may be generally applicable but also particularly applicable in conjunction with any other implementations of the second aspect, the analyte data parameter set includes a calibration period for the analyte sensor system. In embodiments, the circuitry is further adapted to cause the analyte sensor system to set or modify the calibration period using a diabetes management partner interface.

[0027] In particular implementations of the second aspect, which may be generally applicable but also particularly applicable in conjunction with any other implementations of the second aspect, the analyte data parameter set includes a factory calibration code. In embodiments, the circuitry is further adapted to cause the analyte sensor system to receive, using a diabetes management partner interface, an indication from a partner device using the factory calibration code according to system requirements of the partner device. In embodiments, the circuitry is further adapted to cause the analyte sensor system to set or modify a calibration period to zero or none using the diabetes management partner interface.

[0028] In particular implementations of the second aspect, which may be generally applicable but also particularly applicable in relation to any other implementations of the second aspect, the wireless connectivity parameter set includes settings for a remote server. In embodiments, the circuitry is further adapted to cause the analyte sensor system to perform additional operations using the diabetes management partner interface. One such operation is to use a service provided via the remote server. One such operation is to transmit diabetes management feedback to one or more display devices connected to the analyte sensor system in response to the service provided via the remote server. One such operation is to disable use of the service and send an associated notification to a display device connected to the analyte sensor system if a service provided via the remote server becomes unavailable.

[0029] In particular implementations of the second aspect, which may be generally applicable but also particularly applicable in conjunction with any other implementations of the second aspect, the analyte date parameter set includes bolus calculation parameters. In embodiments, the circuitry is further adapted to cause the analyte sensor system to configure, using a diabetes management partner interface, the analyte sensor system to provide access to the bolus calculation parameters to one partner device according to the system requirements of the partner device. In embodiments, the method is further adapted to cause the analyte sensor system to provide a bolus recommendation based on calculations performed using the bolus calculation parameters.

[0030] A third aspect of the present disclosure includes a system. The system includes one or more partner devices adapted to deliver insulin to a user. The system includes an analyte sensor system adapted to generate analyte information. The analyte sensor system includes a configuration parameter set used to transmit and receive wireless signals. The configuration parameters are configurable through use of a diabetes management partner interface. The system also includes a display device connectable to the analyte sensor system and adapted to display the analyte information, and for the analyte sensor system to provide permission to one of the partner devices to provide access to the configuration parameter set via the diabetes management partner interface. One partner device is adapted to use the diabetes management partner interface to set or cause modifications to the configuration parameter set according to the system requirements of the partner device.

[0031] In a particular implementation of the third aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the third aspect, one partner device is an automatic insulin delivery device or a manual insulin delivery device.

[0032] In a particular implementation of the third aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the third aspect, the configuration parameter set includes one or more of a wireless connectivity parameter set, an access control parameter set, and an analyte data parameter set.

[0033] In a particular implementation of the third aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the third aspect, the system requirements are associated with one of the following: a battery capacity of the one partner device; an accuracy requirement of the one partner device; a communication protocol used by the one partner device; a regulatory requirement applicable to the one partner device; and an expected uptime of the one partner device.

[0034] In a particular implementation of the third aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the third aspect, the wireless connectivity parameter set includes a condition under which the one partner device will be removed from a whitelist maintained for the analyte sensor system. In an embodiment, the one partner device is further adapted to set or modify, according to system requirements of the one partner device, the condition under which the one partner device will be removed from the whitelist when a battery level of the one partner delivery device meets a threshold.

[0035] In a particular implementation of the third aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the third aspect, the wireless connectivity parameter set includes an advertisement structure, and in an embodiment, one partner device is further adapted to set or modify the advertisement structure using a diabetes management partner interface.

[0036] In a particular implementation of the third aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the third aspect, the access control parameter set includes one or more of the number of display devices to which the analyte sensor system may be connected and the level of access or control that the analyte sensor system may grant to one or more of the display devices.

[0037] In particular implementations of the third aspect, which may be generally applicable but also particularly applicable in conjunction with any other implementations of the third aspect, the analyte data parameter set includes a calibration period for the analyte sensor system. In embodiments, one partner device is further adapted to set or modify the calibration period using a diabetes management partner interface.

[0038] In particular implementations of the third aspect, which may be generally applicable but also particularly applicable in connection with any other implementations of the third aspect, the analyte data parameter set includes a factory calibration code. In embodiments, the one partner device is further adapted to use a diabetes management partner interface to provide an indication to the analyte sensor system using the factory calibration code according to system requirements of the one partner device, and to set or modify the calibration period to zero or none.

[0039] In particular implementations of the third aspect, which may be generally applicable but also particularly applicable in relation to any other implementations of the third aspect, the wireless connectivity parameter set includes settings for a remote server. In embodiments, the one partner device is further adapted to configure the analyte sensor to perform several operations using a diabetes management partner interface. The one partner device is further adapted to use services provided via the remote server. The one partner device is further adapted to transmit diabetes management feedback to a display device connectable to the analyte sensor system in response to the services provided via the remote server. The one partner device is further adapted to disable use of the services and send an associated notification to a display device connectable to the analyte sensor system if the services provided via the remote server become unavailable.

[0040] In particular implementations of the third aspect, which may be generally applicable but also particularly applicable in conjunction with any other implementations of the third aspect, the analyte date parameter set includes bolus calculation parameters. In embodiments, one partner device is further adapted to configure the analyte sensor system using a diabetes management partner interface to provide the one partner device with access to the bolus calculation parameters according to system requirements of the partner device. In embodiments, one partner device is further adapted to receive bolus recommendations from the analyte sensor system using the diabetes management partner interface based on calculations performed using the bolus calculation parameters.

[0041] A fourth aspect of the present disclosure includes a method for configuring wireless communication between an analyte sensor system and one or more of a display device and a partner device using a diabetes management partner interface. The method includes the analyte sensor system enabling a first wireless signal communication path. The first wireless communication signal path is between the analyte sensor system and the display device. Over the first wireless communication path, the analyte sensor system provides a first degree of access or control over the analyte sensor system to the display device. The method also includes the analyte sensor system enabling a second wireless signal communication path. The second wireless signal communication path is between the analyte sensor system and the partner device. The analyte sensor system enabling the second wireless signal communication path includes causing a modification of the first degree of access or control to implement the second degree of access or control in accordance with system requirements of the partner device. The modification is caused in response to input received from the partner device via the diabetes management partner interface.

[0042] In a particular implementation of the fourth aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the fourth aspect, causing the modification of the first degree of access or control includes using a diabetes management partner interface to set or change a set of configuration parameters implemented by the analyte sensor system according to system requirements of the partner device.

[0043] In particular implementations of the fourth aspect, which may be generally applicable but also particularly applicable in relation to any other implementations of the fourth aspect, the configuration parameter set includes one or more of access control parameters of the display device or partner device, accuracy or calibration parameters of the analyte sensor system, and wireless communication parameters of communications exchanged between the analyte sensor system and one or more of the display device and partner device.

[0044] In a particular implementation of the fourth aspect, which may be generally applicable but also particularly applicable in connection with any other implementation of the fourth aspect, setting or modifying the configuration parameter set using the diabetes management partner interface includes granting permission to a partner device to configure accuracy or calibration parameters of the analyte sensor system via the diabetes management partner interface.

[0045] In a particular implementation of the fourth aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the fourth aspect, setting or changing the configuration parameter set using the diabetes management partner interface includes revoking permission from the display device to configure accuracy or calibration parameters of the analyte sensor system via the diabetes management partner interface.

[0046] In a particular implementation of the fourth aspect, which may be generally applicable but also particularly applicable in conjunction with any other implementation of the fourth aspect, the access control parameters include a whitelist of devices that can connect to the analyte sensor system. The method also includes setting or changing the configuration parameter set using the diabetes management partner interface to set or modify an amount of time that a partner device will remain on the whitelist before being removed from the whitelist.

[0047] A fifth aspect of the present disclosure includes an analyte sensor system for wireless communication with one or more of a display device and a partner device. The analyte sensor system is configurable through use of a diabetes management partner interface. The analyte sensor system includes a memory that stores a set of configuration parameters used by the transceiver to transmit and receive wireless signals. The analyte sensor system also includes circuitry operatively coupled to the transceiver and the memory and adapted to cause the analyte sensor system to perform several operations. One such operation is enabling a first wireless signal communication path. The first wireless communication signal path is between the analyte sensor system and a display device. Over the first wireless communication path, the analyte sensor system provides the display device with a first degree of access or control over the analyte sensor system. Another such operation is enabling a second wireless signal communication path. The second wireless signal communication path is between the analyte sensor system and a partner device. The second wireless signal communication path is enabled by a modification of the first degree of access or control made by the analyte sensor system. In response to input received from a partner device via a diabetes management partner interface, a modification of the first degree of access or control is made to implement a second degree of access or control in accordance with system requirements of the partner device.

[0048] In a particular implementation of the fifth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the fifth aspect, to modify the first degree of access or control, the circuitry is further adapted to cause the analyte sensor system to use a diabetes management partner interface to set or change a set of configuration parameters implemented by the analyte sensor system in accordance with system requirements of the partner device.

[0049] In a particular implementation of the fifth aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the fifth aspect, the configuration parameter set includes one or more of access control parameters of the display device or partner device, accuracy or calibration parameters of the analyte sensor system, and wireless communication parameters of communications exchanged between the analyte sensor system and one or more of the display device and partner device.

[0050] In a particular implementation of the fifth aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the fifth aspect, the circuitry is further adapted to cause the analyte sensor system to grant permission to a partner device to configure accuracy or calibration parameters of the analyte sensor system via a diabetes management partner interface.

[0051] In a particular implementation of the fifth aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the fifth aspect, the circuitry is further adapted to cause the analyte sensor system to revoke permission from the display device to configure accuracy or calibration parameters of the analyte sensor.

[0052] In a particular implementation of the fifth aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the fifth aspect, the access control parameters include a whitelist of devices that can connect to the analyte sensor system, and in an embodiment, the circuitry is further adapted to set or modify a time that a partner device will remain on the whitelist before being removed from the whitelist.

[0053] A sixth aspect of the present disclosure includes a method for controlling wireless communication between an analyte sensor system and one or more remote devices connectable to the analyte sensor system using a diabetes management partner interface of the analyte sensor system. The one or more remote devices include a display device and a partner device. The method includes the analyte sensor system determining whether a connection request received from one of the remote devices originates from a partner class within the one or more remote devices. The remote devices within the partner class are adapted to deliver medication. The partner class includes the partner device. The method includes the diabetes management partner interface enabling selection of an operating mode corresponding to the partner class if the connection request originates from the partner class. The operating mode uses a configuration parameter set of the partner class to support system requirements of the partner device.

[0054] In a particular implementation of the sixth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the sixth aspect, the method includes exchanging wireless communications with at least one of the remote devices using an operating mode corresponding to a partner class.

[0055] In a particular implementation of the sixth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the sixth aspect, exchanging wireless communications using an operating mode corresponding to the partner class includes transmitting a mode indicator available by at least one of the remote devices to determine the operating mode being used.

[0056] In a particular implementation of the sixth aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the sixth aspect, the configuration parameter set includes one or more of access control parameters of the display device or partner device, accuracy or calibration parameters of the analyte sensor system, and wireless communication parameters of communications exchanged between the analyte sensor system and one or more of the remote devices.

[0057] In a particular implementation of the sixth aspect that is generally applicable, but also particularly applicable in connection with any other implementation of the sixth aspect, the mode indicator is operable by the analyte sensor system to deactivate access by a set of remote devices not in the partner class to one or more of the access control parameters, the accuracy or calibration parameters, and the wireless communication parameters using the diabetes management partner interface. In an embodiment, access by the set of remote devices to one of the access control parameters, the accuracy or calibration parameters, and the wireless communication parameters is activated when the analyte sensor system uses an operating mode that corresponds to the set of remote devices.

[0058] In a particular implementation of the sixth aspect that is generally applicable but also particularly applicable in relation to any other implementations of the sixth aspect, the method also includes determining that the analyte sensor system has not received wireless communication from the partner device for at least a predetermined amount of time. The method also includes, in response to the determination and further in response to receiving a connection request from one of the remote devices in the set of remote devices not in the partner class, the analyte sensor system selecting an operating mode corresponding to the set of remote devices not in the partner class. The operating mode corresponding to the set of remote devices not in the partner class is according to a configuration parameter set specific to the set of remote devices not in the partner class. In an embodiment, the method also includes removing the partner device from the whitelist.

[0059] In a particular implementation of the sixth aspect that is generally applicable, but also particularly applicable in conjunction with any other implementation of the sixth aspect, the method includes the analyte sensor system receiving, from a partner device using a diabetes management partner interface, a value for one of the configuration parameters. The method also includes the analyte sensor system modifying the one configuration parameter using the value received from the partner device.

[0060] In a particular implementation of the sixth aspect that is generally applicable, but also particularly applicable in relation to any other implementation of the sixth aspect, the method includes the analyte sensor system transmitting values ​​of configuration parameters to the display device, the values ​​including one or more of a designated time after which the partner device will be removed from a whitelist maintained for the analyte sensor system and a designated time after which the display device will be removed from the whitelist.

[0061] In a particular implementation of the sixth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the sixth aspect, exchanging wireless communications using an operating mode corresponding to the partner device includes one or more of: modifying a whitelist managed for the analyte sensor system to switch off slots for devices other than the partner device; and transmitting advertisement messages directed only to the partner device.

[0062] In a particular implementation of the sixth aspect that is generally applicable, but also particularly applicable in relation to any other implementation of the sixth aspect, the method includes, if the connection request does not originate from the partner class, the analyte sensor system selecting an operating mode corresponding to a set of remote devices not in the partner class, wherein the operating mode corresponding to the set of remote devices not in the partner class uses a configuration parameter set specific to the set of remote devices not in the partner class.

[0063] In a particular implementation of the sixth aspect that is generally applicable, but also particularly applicable in conjunction with any other implementation of the sixth aspect, the display device is in the set of remote devices that are not in the partner class. In an embodiment, the method further includes providing the display device with access to a set of configuration parameters specific to the set of remote devices that are not in the partner class using a diabetes management partner interface. The method may further include the analyte sensor system setting or modifying a value of one of the configuration parameters specific to the set of remote devices that are not in the partner class in response to input received from the display device.

[0064] In a particular implementation of the sixth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the sixth aspect, exchanging wireless communications using an operating mode corresponding to a partner class includes modifying an advertisement slot to advertise only to partner devices or partner device controllers.

[0065] In a particular implementation of the sixth aspect that is generally applicable, but also particularly applicable in relation to any other implementation of the sixth aspect, exchanging wireless communications using an operating mode corresponding to a partner class includes, in response to a command received via a diabetes management partner interface, the analyte sensor system only accepting connection requests received from the partner device. The command may be received from a partner device.

[0066] A seventh aspect of the present disclosure includes an analyte sensor system that uses a diabetes management partner interface to control wireless communication between the analyte sensor system and one or more remote devices connectable to the analyte sensor system. The one or more remote devices include a display device and a partner device. The analyte sensor system includes circuitry operably coupled to a memory that stores instructions that, when executed, cause the analyte sensor system to perform several operations. One such operation is for the analyte sensor system to determine whether a connection request received from one of the remote devices originates from a partner class within the one or more remote devices. The remote devices within the partner class are adapted to deliver medication. The partner class includes partner devices. Another such operation is for the analyte sensor system to use the diabetes management partner interface to enable selection of an operating mode corresponding to the partner class. The operating mode uses a configuration parameter set of the partner class to support the system requirements of the partner device.

[0067] In a particular implementation of the seventh aspect that is generally applicable but also particularly applicable in relation to any other implementation of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to exchange the wireless communications with at least one of the remote devices using the operational mode corresponding to the partner class.

[0068] In a particular implementation of the seventh aspect that is generally applicable, but also particularly applicable in connection with any other implementation of the seventh aspect, wireless communications exchanged using an operational mode corresponding to a partner class include a mode indicator transmitted by the analyte sensor system to at least one remote device, the mode indicator usable by at least one of the remote devices to determine the operational mode being used.

[0069] In a particular implementation of the seventh aspect, which may be generally applicable but also particularly applicable in relation to any other implementation of the seventh aspect, the configuration parameter set used to support the system requirements of the partner device includes one or more of: access control parameters of the display device or partner device, accuracy or calibration parameters of the analyte sensor system, and wireless communication parameters of communications exchanged between the analyte sensor system and one or more of the remote devices.

[0070] In a particular implementation of the seventh aspect that is generally applicable, but also particularly applicable in conjunction with any other implementation of the seventh aspect, the mode indicator is operable by the analyte sensor system to deactivate access by a set of remote devices not in the partner class to one or more of the access control parameters, the accuracy or calibration parameters, and the wireless communication parameters using the diabetes management partner interface. In an embodiment, the memory further stores instructions that, when executed, cause the analyte sensor system to provide access by the set of remote devices to one or more of the access control parameters, the accuracy or calibration parameters, and the wireless communication parameters when the analyte sensor system uses an operational mode corresponding to the set of remote devices.

[0071] In a particular implementation of the seventh aspect that is generally applicable but also particularly applicable in relation to any other implementation of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to perform additional operations. One such operation is determining that the analyte sensor system has not received wireless communications from a partner device for at least a predetermined amount of time. Another such operation is selecting, in response to the determination and further in response to a connection request received from one of the remote devices in the set of remote devices not in the partner class, an operational mode corresponding to the set of remote devices not in the partner class. The operational mode corresponding to the set of remote devices not in the partner class is according to a set of configuration parameters specific to the set of remote devices not in the partner class.

[0072] In a particular implementation of the seventh aspect that is generally applicable but also particularly applicable in relation to any other implementation of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to remove the partner device from the whitelist.

[0073] In particular implementations of the seventh aspect that are generally applicable, but also particularly applicable in conjunction with any other implementations of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to perform additional operations. One such operation is receiving a value for one of the configuration parameters from a partner device using the diabetes management partner interface. Another such operation is modifying the one configuration parameter using the value received from the partner device.

[0074] In a particular implementation of the seventh aspect that is generally applicable, but also particularly applicable in relation to any other implementation of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to transmit values ​​of configuration parameters to the display device, the values ​​including one or more of a designated time after which the partner device will be removed from a whitelist maintained for the analyte sensor system and a designated time after which the display device will be removed from the whitelist.

[0075] In particular implementations of the seventh aspect that are generally applicable but also particularly applicable in relation to any other implementations of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to perform additional operations. One such operation is modifying a whitelist maintained for the analyte sensor system to switch off slots of devices other than partner devices. Another such operation is transmitting advertisement messages directed only to partner devices.

[0076] In a particular implementation of the seventh aspect that is generally applicable but also particularly applicable in relation to any other implementation of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to select an operating mode corresponding to a set of remote devices not in the partner class if the connection request is not from the partner class, and wherein the operating mode corresponding to the set of remote devices not in the partner class uses a configuration parameter set specific to the set of remote devices not in the partner class.

[0077] In a particular implementation of the seventh aspect that is generally applicable but also particularly applicable in conjunction with any other implementation of the seventh aspect, the display device is in a set of remote devices that are not in a partner class, and the memory further stores instructions that, when executed, cause the analyte sensor system to perform additional operations. One such operation is to provide the display device with access to a set of configuration parameters specific to the set of remote devices that are not in the partner class using the diabetes management partner interface. Another such operation is to set or modify the value of one of the configuration parameters specific to the set of remote devices that are not in the partner class in response to input received from the display device.

[0078] In a particular implementation of the seventh aspect that is generally applicable but also particularly applicable in relation to any other implementation of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to modify the advertisement slot to advertise only to partner devices or partner device controllers.

[0079] In a particular implementation of the seventh aspect that is generally applicable, but also particularly applicable in connection with any other implementation of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to only accept connection requests received from partner devices in response to commands received via the diabetes management partner interface, where the commands may be received from the partner devices.

[0080] An eighth aspect of the present disclosure includes a method for enabling configurability of an analyte sensor system that exchanges wireless communications with one or more of a partner device and a display device using a diabetes management interface. The method includes the analyte sensor system determining that a first connection request has been sent from a remote device in a first class of remote devices. The method includes the analyte sensor system determining that a second connection request has been sent from a remote device in a second class of remote devices. A remote device in the second class of remote devices is adapted to deliver medication. A remote device in the first class of remote devices does not belong to the second class of remote devices. The method includes the analyte sensor system using any one of a plurality of operating modes. A first operating mode of the plurality is specific to a first configuration that utilizes a remote device in the second class of remote devices and does not utilize a remote device in the first class of remote devices. A second operating mode of the plurality is specific to a second configuration that does not utilize a device from the second class of remote devices. A third mode of operation of the plurality is specific to a third configuration utilizing remote devices in the first class of remote devices and remote devices from the second class of remote devices.

[0081] In a particular implementation of the eighth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, using a first operating mode of the plurality includes providing a remote device in a second class of remote devices with authority to modify permissions provided to a remote device in the first class of remote devices using a diabetes management partner interface.

[0082] In a particular implementation of the eighth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, using the first operating mode of the plurality further includes the analyte sensor system receiving, from a remote device in the first class of remote devices, permission for a remote device in the second class of remote devices to communicate with the analyte sensor system.

[0083] In a particular implementation of the eighth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, using the first operating mode further includes, in response to input received via the diabetes management partner device from a remote device in the second class of remote devices, preventing the analyte sensor system from connecting with devices other than a remote device in the second class of remote devices.

[0084] In a particular implementation of the eighth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, preventing the connection includes advertising to a remote device in the second class of remote devices using a first advertisement slot, and preventing the connection also includes advertising to a remote device in the second class of remote devices or a controller of a remote device in the second class of remote devices using a second advertisement slot.

[0085] In a particular implementation of the eighth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, preventing the connection includes the analyte sensor system using the diabetes management partner interface to set or cause a modification of the advertisement structure to include a single advertisement period dedicated to remote devices in the second class of devices.

[0086] In a particular implementation of the eighth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, preventing the connection includes the analyte sensor system accepting connection requests only from remote devices in the second class of remote devices.

[0087] In a particular implementation of the eighth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, using the first operating mode of the plurality further includes the analyte sensor system modifying a timeout rule associated with a remote device in the second class of remote devices using input received from the remote device in the second class of remote devices via the diabetes management interface.

[0088] In a particular implementation of the eighth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, using the second operating mode of the plurality includes one or more of the following operations: modifying the whitelist to exclude remote devices in the second class of remote devices; rejecting connection requests received from remote devices in the second class of remote devices; and advertising exclusively to remote devices in the first class of remote devices.

[0089] In a particular implementation of the eighth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, using the third operating mode of the plurality includes the analyte sensor system receiving, via the diabetes management interface, from a remote device in the second class of remote devices an indication of the level of access to the analyte sensor system that will be granted to the remote device in the first class of remote devices.

[0090] In a particular implementation of the eighth aspect that is generally applicable, but also particularly applicable in relation to any other implementation of the eighth aspect, the method includes the analyte sensor system implementing the access level using a diabetes management interface. The method also includes communicating the access level to a remote device in a first class of remote devices.

[0091] In a particular implementation of the eighth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the eighth aspect, depending on the access level, a remote device in the first class of remote devices can receive analyte data from the analyte sensor system but cannot access accuracy or calibration parameters used by the analyte sensor system for the third operating mode.

[0092] A ninth aspect of the present disclosure includes an analyte sensor system that exchanges wireless communications with one or more of a partner device and a display device. The analyte sensor system is configurable by a diabetes management partner interface. The analyte sensor system includes circuitry operably coupled to a memory storing instructions that, when executed, cause the analyte sensor system to perform several operations. One such operation is determining that a first connection request has been sent from a remote device in a first class of remote devices. Another such operation is determining that a second connection request has been sent from a remote device in a second class of remote devices. A remote device in the second class of remote devices is adapted to deliver medication. A remote device in the first class of remote devices does not belong to the second class of remote devices. Another such operation is using any one of a plurality of operating modes. A first operating mode of the plurality is specific to a first configuration that utilizes a remote device in the second class of remote devices and does not utilize a remote device in the first class of remote devices. A second operating mode of the plurality is specific to a second configuration utilizing no devices from the second class of remote devices, and a third operating mode of the plurality is specific to a third configuration utilizing remote devices from the first class of remote devices and remote devices from the second class of remote devices.

[0093] In a particular implementation of the ninth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system, in a first operational mode of the plurality, to provide a remote device in the second class of remote devices with authority to modify permissions provided to a remote device in the first class of remote devices using the diabetes management partner interface.

[0094] In a particular implementation of the ninth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to receive, in a first operational mode of the plurality, from a remote device in a first class of remote devices, permission for a remote device in the second class of remote devices to communicate with the analyte sensor system.

[0095] In a particular implementation of the ninth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system, in a first operational mode of the plurality, to prevent connection with devices other than remote devices in the second class of remote devices in response to input received via the diabetes management partner device from a remote device in the second class of remote devices.

[0096] In a particular implementation of the ninth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, the memory stores instructions that, when executed, cause the analyte sensor system to advertise to a remote device in the second class of remote devices using the first advertisement slot and to advertise a remote device in the second class of remote devices or a controller to a remote device in the second class of remote devices using the second advertisement slot.

[0097] In a particular implementation of the ninth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to use the diabetes management partner interface to configure or cause a modification of the advertisement structure to include a single advertisement period dedicated to remote devices in the second class of devices.

[0098] In a particular implementation of the ninth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to accept connection requests only from remote devices in the second class of remote devices.

[0099] In a particular implementation of the ninth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system, in a first operational mode of the plurality, to modify a timeout rule associated with a remote device in the second class of remote devices using input received from the remote device in the second class of remote devices via the diabetes management interface.

[0100] In particular implementations of the ninth aspect that are generally applicable, but also particularly applicable in relation to any other implementations of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to perform additional operations in a second mode of operation of the plurality. One such operation is modifying the whitelist to exclude remote devices in the second class of remote devices. Another such operation is rejecting connection requests received from remote devices in the second class of remote devices. Another such operation is advertising exclusively to remote devices in the first class of remote devices.

[0101] In a particular implementation of the ninth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to receive, in a third operational mode of the plurality, an indication of the level of access to the analyte sensor system from a remote device in the second class of remote devices via the diabetes management interface that will be given to a remote device in the first class of remote devices.

[0102] In a particular implementation of the ninth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, the memory further describes instructions that, when executed, cause the analyte sensor system to implement the access level using a diabetes management interface and notify a remote device in the first class of remote devices of the access level.

[0103] In a particular implementation of the ninth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the ninth aspect, depending on the access level, a remote device in the first class of remote devices can receive analyte data from the analyte sensor system but cannot access accuracy or calibration parameters used by the analyte sensor system for the third operating mode.

[0104] A tenth aspect of the present disclosure includes a method for facilitating wireless communication exchange with an analyte sensor system using a diabetes management interface. The method includes establishing a first connection between the analyte sensor system and a first partner device using a diabetes management partner interface. The method includes the analyte sensor system providing the first partner device with access to a configuration parameter set via the diabetes management interface. The method further includes setting or causing a first modification of the configuration parameter set in response to input received from the first partner device via the diabetes management partner interface. Setting or causing the first modification is performed according to system requirements of the first partner device. Additionally, the method includes establishing a second connection between the analyte sensor system and a second partner device using the diabetes management partner interface. The method also includes the analyte sensor system providing the second partner device with access to the configuration parameter set via the diabetes management interface. The method further includes causing a second modification of the configuration parameter set in response to input received from the second partner device via the diabetes management partner interface. The second modification is made according to the system requirements of the second partner device.

[0105] In a particular implementation of the tenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the tenth aspect, establishing a second connection using a diabetes management partner interface occurs after the first connection is terminated.

[0106] In a particular implementation of the tenth aspect that is generally applicable but also particularly applicable in conjunction with any other implementations of the tenth aspect, the method, in response to the analyte sensor system receiving identification information for the third partner device, attempts to establish a third connection between the analyte sensor system and the third partner device using a diabetes management partner interface. The method also includes, in response to establishing the third connection between the analyte sensor system and the third partner device, causing a third modification of the configuration parameter set in response to input received via the diabetes management partner interface. The third modification is made according to system requirements of the third partner device.

[0107] In a particular implementation of the tenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the tenth aspect, identification information for a third partner device is stored in a server system. In an embodiment, the identification information indicates whether the third partner device is authorized to communicate with the analyte sensor system.

[0108] In a particular implementation of the tenth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the tenth aspect, the analyte sensor system receiving identification information for the third partner device includes the analyte sensor system receiving identification information for the third partner device from a display device that received the identification information for the third partner device from the server system.

[0109] In particular implementations of the tenth aspect, which are generally applicable but also particularly applicable in conjunction with any other implementations of the tenth aspect, the method includes additional operations. One such operation involves, in response to the analyte sensor system receiving identification information for the third partner device, determining whether the third partner device is authorized to communicate with the analyte sensor system using the identification information for the third partner device. Another such operation involves, in response to determining that the third partner device is not authorized to communicate with the analyte sensor system, canceling an attempt to establish a third connection between the analyte sensor system and the third partner device. Another such operation involves, in response to determining that the third partner device is authorized to communicate with the analyte sensor system, establishing a third connection between the analyte sensor system and the third partner device using a diabetes management partner interface.

[0110] In particular implementations of the tenth aspect that are generally applicable, but also particularly applicable in conjunction with any other implementations of the tenth aspect, determining that the third partner device is not authorized to communicate with the analyte sensor system occurs at a first time. In embodiments, determining that the third partner device is authorized to communicate with the analyte sensor system occurs at a second time. Identification information for the third partner device can be updated at the server system between the first time and the second time.

[0111] In a particular implementation of the tenth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the tenth aspect, system requirements for the third partner device are stored in a server system. The method further includes causing a fourth modification of the configuration parameter set in response to input received via the diabetes management partner interface. The fourth modification is made in response to an updated version of the system requirements for the third partner device.

[0112] An eleventh aspect of the present disclosure includes an analyte sensor system that facilitates the exchange of wireless communications using a diabetes management interface. The analyte sensor system includes circuitry operably coupled to a memory that stores instructions that, when executed, cause the analyte sensor system to perform several operations. One such operation includes establishing a first connection between the analyte sensor system and a first partner device using the diabetes management partner interface. Another such operation is providing the first partner device with access to a configuration parameter set via the diabetes management interface. Another such operation is setting or causing a first modification of the configuration parameter set in response to input received from the first partner device via the diabetes management partner interface. The first modification is made in response to system requirements of the first partner device. Another such operation is establishing a second connection between the analyte sensor system and a second partner device using the diabetes management partner interface. Another such operation is providing the second partner device with access to the configuration parameter set via the diabetes management interface. Yet another such action is to cause a second modification of the configuration parameter set in response to input received from a second partner device via the diabetes management partner interface, the second modification being made in response to system requirements of the second partner device.

[0113] In a particular implementation of the eleventh aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the eleventh aspect, the second connection is established after the first connection is terminated.

[0114] In a particular implementation of the eleventh aspect, which is generally applicable but also particularly applicable in relation to any other implementations of the eleventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to perform additional operations. One such operation is receiving identification information for a third partner device. Another such operation is, in response to receiving the identification information for the third partner device, attempting to establish a third connection between the analyte sensor system and the third partner device using the diabetes management partner interface. Another such operation is, in response to establishing the third connection between the analyte sensor system and the third partner device, causing a third modification of the configuration parameter set in response to input received via the diabetes management partner interface. The third modification is made in response to system requirements of the third partner device.

[0115] In a particular implementation of the eleventh aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the eleventh aspect, identification information for the third partner device is stored in the server system, the identification information indicating whether the third partner device is authorized to communicate with the analyte sensor system.

[0116] In a particular implementation of the eleventh aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the eleventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to receive identification information for the third partner device from the display device that received the identification information for the third partner device.

[0117] In particular implementations of the eleventh aspect, which are generally applicable but also particularly applicable in conjunction with any other implementations of the eleventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to perform additional operations. One such operation is, in response to receiving identification information for the third partner device, determining whether the third partner device is authorized to communicate with the analyte sensor system using the identification information for the third partner device. Another such operation is, in response to determining that the third partner device is not authorized to communicate with the analyte sensor system, canceling an attempt to establish a third connection between the analyte sensor system and the third partner device. Another such operation is, in response to determining that the third partner device is authorized to communicate with the analyte sensor system, establishing a third connection between the analyte sensor system and the third partner device using the diabetes management partner interface.

[0118] In particular implementations of the eleventh aspect that are generally applicable, but also particularly applicable in relation to any other implementations of the eleventh aspect, a determination is made at a first time that the third partner device is not authorized to communicate with the analyte sensor system. In embodiments, a determination is made at a second time that the third partner device is authorized to communicate with the analyte sensor system. In embodiments, identification information for the third partner device is updated at the server system between the first time and the second time.

[0119] In a particular implementation of the eleventh aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the eleventh aspect, system requirements for a third partner device are stored in a server system. The memory, when executed, causes the analyte sensor system to perform a fourth modification of the configuration parameter set in response to input received via the diabetes management partner interface. The fourth modification is performed in response to an updated version of the system requirements for the third partner device.

[0120] A twelfth aspect of the present disclosure includes a method. The method includes receiving an indication by the analyte sensor system to enter an operational mode specific to use of a partner device. The method further includes establishing a connection between the analyte sensor system and the partner device. The method also includes the analyte sensor system setting or modifying configuration parameters in response to input received from the partner device via a diabetes management partner interface. The input received from the partner device indicates corresponding operational parameters used by the partner device to communicate with the analyte sensor system using the operational mode. The configuration parameters are configured according to system requirements of the partner device. The method also includes implementing the operational mode specific to use of the partner device using the operational parameters of the analyte sensor system to conform to the system requirements of the partner device.

[0121] In a particular implementation of the twelfth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the twelfth aspect, the configuration parameters include one or more of: permission parameters for the display device to issue commands or control signals to start, stop, calibrate, or set the length of a sensor session to the analyte sensor system; battery or power management parameters; connection model parameters; timeout parameters, one or more of which relate to the length of time to keep a partner device on a whitelist, an advertising timeout, a connection establishment timeout, and an authorization timeout; alert parameters; configuration settings that govern the operating mode of the analyte sensor system; and remote server parameters.

[0122] In a particular implementation of the twelfth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the twelfth aspect, the method further includes the analyte sensor system receiving an indication of a transition from implementation in the operational mode specific to the use of the partner device. The method further includes the analyte sensor system restoring configuration parameters to a previous state that existed before setting or changing the configuration parameters in response to input received from the partner device. Restoring the set of configuration parameters to the previous state may include removing the partner device from a whitelist.

[0123] A thirteenth aspect of the present disclosure includes a method. The method includes an analyte sensor system determining whether a wireless communication system includes one or more of a display device and a partner device. If the wireless communication system includes a display device, the method also includes determining whether the analyte sensor system connects to the display device using one of an intermittent connection model or a continuous connection model. If the system includes a partner device, the method includes determining whether the analyte sensor system connects to the partner device using one of an intermittent connection model or a continuous connection model. Determining whether the analyte sensor system uses the intermittent connection model or the continuous connection model to connect to the one or more of the display device and the partner device includes using configuration parameters set or modified using input received from the partner device via a diabetes management partner interface.

[0124] In a particular implementation of the thirteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the thirteenth aspect, determining that the analyte sensor system connects to the partner device according to an intermittent connection model is made using one of the configuration parameters set in response to the power requirements of the partner device.

[0125] In a particular implementation of the thirteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the thirteenth aspect, determining that the analyte sensor system connects to a partner device according to a serial connection model is made using a determination that the system includes a display device.

[0126] A fourteenth aspect of the present disclosure includes a method. The method includes an analyte sensor application of a display device receiving an interface to a partner device application associated with a partner device. The method includes the analyte sensor application using the interface to collect information collected by the partner device application. The information includes one or more of pairing data and analyte dosage data. The method also includes the analyte sensor application using the interface to provide analyte sensor system information. The analyte sensor information is used to indicate one or more of: that the analyte sensor system is functioning; a connection model utilized by the analyte sensor system with respect to the partner device or the display device; and configuration parameters used by the analyte sensor system to communicate with one or more of the partner device and the display device.

[0127] In a particular implementation of the fourteenth aspect that is generally applicable, but also particularly applicable in relation to any other implementation of the fourteenth aspect, the method further includes the analyte sensor application receiving analyte data from the analyte sensor system. The method also includes the analyte sensor application providing a visual display that includes the analyte data and information collected by the partner device application.

[0128] In a particular implementation of the fourteenth aspect that is generally applicable, but also particularly applicable in relation to any other implementation of the fourteenth aspect, the method also includes the analyte sensor application receiving information regarding the analyte value from the analyte sensor system. The method also includes the analyte sensor application communicating the analyte value to the partner device via the partner device application using the interface.

[0129] In a particular implementation of the fourteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the fourteenth aspect, the method also includes the analyte sensor application receiving, via the interface, drug delivery information collected by the partner device.

[0130] In a particular implementation of the fourteenth aspect that is generally applicable, but also particularly applicable in relation to any other implementation of the fourteenth aspect, the method also includes the analyte sensor application receiving, via the interface, an alert from the partner device, the alert relating to a problem with the functionality of the partner device.

[0131] In a particular implementation of the fourteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the fourteenth aspect, the method also includes causing an analyte sensor application of the display device to provide an alert via a user interface.

[0132] In a particular implementation of the fourteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the fourteenth aspect, the method also includes causing an analyte sensor application of the display device to cause an alert to be provided via a remote server.

[0133] A fifteenth aspect of the present disclosure includes a method. The method includes establishing a connection between an analyte sensor system and a partner device. The method further includes the analyte sensor system receiving configuration parameter information from the partner device using a diabetes management partner interface. The configuration parameter information relates to operation of the analyte sensor system according to system requirements of the partner device. The configuration parameter information may include a degree of access granted to a remote device connectable to the analyte sensor system. The configuration parameter information may include one or more values ​​of a configurability parameter set used in the connection established between the analyte sensor system and the partner device. The one or more values ​​of the configurability parameter set are selected according to the system requirements of the partner device.

[0134] In particular implementations of the fifteenth aspect, which are generally applicable but also particularly applicable in relation to any other implementations of the fifteenth aspect, the configurability parameter set includes one or more of the following: The configurability parameter set may include connection information for a remote device. The configurability parameter set may include a connection model used for a particular device connectable to the analyte sensor system. The configurability parameter set may include connection command related data to be read by or sent to the remote device. The configurability parameter set may include information related to non-use of a partner device. The configurability parameter set may include security or privacy related parameters. The configurability parameter set may include information related to power control or battery usage. The configurability parameter set may include a number of devices connectable to the analyte sensor system. The configurability parameter set may include a device type for each device connectable to the analyte sensor system. The configurability parameter set may include a type of information related to analyte data that may be read by and sent to a remote device connectable to the analyte sensor system.

[0135] In particular implementations of the fifteenth aspect that are generally applicable but also particularly applicable in relation to any other implementations of the fifteenth aspect, the connection command-related data includes one or more of the following: The connection command-related data may indicate whether the partner device or remote device is eligible for inclusion on a whitelist of the analyte sensor system. The connection command-related data may indicate whether the partner device or remote device is in compliance with an expired whitelist. If the partner device or remote device is in compliance with an expired whitelist, the connection command-related data may indicate the amount of time until the partner device or remote device sets the whitelist to expire.

[0136] In a particular implementation of the fifteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the fifteenth aspect, the information related to power control includes suggestions to expire particular devices to extend the battery life of the analyte sensor system.

[0137] In a particular implementation of the fifteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the fifteenth aspect, information related to power control or battery usage is collected via a control mechanism that balances the battery life of the analyte sensor system against the connection reliability between the analyte sensor system and a partner or remote device.

[0138] In a particular implementation of the fifteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the fifteenth aspect, information related to power control triggers a low power mode of the analyte sensor system.

[0139] In a particular implementation of the fifteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the fifteenth aspect, the degree of access is received only after the analyte sensor system receives permission for the degree of access to be modified using parameter information received from the partner device.

[0140] A sixteenth aspect of the present disclosure includes a method. The method includes establishing a connection between a display device and an analyte sensor system. The method also includes the display device receiving an indication that the analyte sensor system is connecting to a partner device. The method also includes receiving configuration parameters for alerts originating from the partner device via the diabetes management partner interface after receiving authorization to provide the partner device with access to a set of configuration parameters via the diabetes management partner interface. The method also includes the display device providing a user interface for configuring the alerts originating from the analyte sensor system and the alerts originating from the partner device. The method further includes causing modification of the configuration parameters for the alerts originating from the partner device using input received via the user interface. The change is made according to system requirements of the partner device.

[0141] In a particular implementation of the sixteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the sixteenth aspect, the method also includes receiving, via a user interface, a selection of a partner device or a remote device from a plurality of remote devices, including a display device, to be used as a primary device for providing one or more of the alerts originating from the analyte sensor system and the alerts originating from the partner device.

[0142] In a particular implementation of the sixteenth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the sixteenth aspect, the method also includes providing a warning to a device other than the primary device when the battery capacity of the primary device falls below a threshold.

[0143] In a particular implementation of the sixteenth aspect, which is generally applicable but also particularly applicable in relation to any other implementation of the sixteenth aspect, the method also includes the display device receiving, via a user interface, a selection of alert types to be provided for alerts originating from the partner device and alerts originating from the analyte sensor system, respectively.

[0144] In a particular implementation of the sixteenth aspect that is generally applicable but also particularly applicable in relation to any other implementation of the sixteenth aspect, the method also includes providing an alert via the primary notification device. The method also includes providing an alert via the secondary notification device if no acknowledgment is received in response to providing the alert via the primary notification device. The primary notification device and the secondary notification device are at least one of a partner device, an analyte sensor system, and / or a plurality of remote devices.

[0145] A sixteenth aspect of the present disclosure includes a method for monitoring an operability status of a drug delivery device. The method includes receiving drug delivery device information from the drug delivery device related to one or more of the following: The drug delivery device information may be related to reservoir changes. The drug delivery device information may be related to pump rewind. The drug delivery device information may be related to pump priming. The drug delivery device information may be related to cannula filling. The drug delivery device information may be related to fluid pressure. The drug delivery device information may be related to determining a combination of analyte delivery device information and analyte data generated using an analyte sensor system. The drug delivery device information may be related to the analyte sensor system using the combination to determine the operability status of the drug delivery device.

[0146] Further aspects of the present disclosure will be more readily understood by considering the following detailed description of various disclosed embodiments in conjunction with the accompanying drawings. [Brief explanation of the drawings]

[0147] [Figure 1] 1 illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the present disclosure. [Figure 2A] 1 illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the present disclosure. [Figure 2B] 1 illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the present disclosure. [Figure 3A] FIG. 1 is a perspective view of an exemplary housing that may be used in connection with implementing embodiments of an analyte sensor system. [Figure 3B] FIG. 1 is a side view of an exemplary housing that may be used in connection with implementing embodiments of an analyte sensor system. [Figure 3C] 1 illustrates aspects of an exemplary analyte sensor system according to an embodiment of the present disclosure. [Figure 4] 1 illustrates aspects of an exemplary display device according to an embodiment of the present disclosure. [Figure 5A] 1 illustrates aspects of an exemplary partner device according to an embodiment of the present disclosure. [Figure 5B] 1 illustrates aspects of an exemplary partner device according to an embodiment of the present disclosure. [Figure 6] FIG. 10 is a timing diagram illustrating aspects of an advertisement message that may be transmitted in accordance with an embodiment of the present disclosure. [Figure 7A] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 7B] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 7C] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 7D] 1 illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the present disclosure. [Figure 8] 1 illustrates aspects of an exemplary system that may be used in connection with practicing embodiments of the present disclosure. [Figure 9A]1 illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the present disclosure. [Figure 9B] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9C] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9D] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9E] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9F] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9G] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9H] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9J] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9K] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9L] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9M] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9N] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9P] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9Q] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9R] FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 9S]FIG. 1 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure. [Figure 10A] 1 illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the present disclosure. [Figure 10B] 1 illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the present disclosure. [Figure 11] 1 illustrates an exemplary computing module according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0148] The drawings, which are described in more detail in the following description and examples, are provided for illustrative purposes only and merely depict typical or exemplary embodiments of the present disclosure. The drawings are not intended to be exhaustive or to limit the disclosure to the precise form disclosed. It should also be understood that the present disclosure may be practiced with modification or alteration and may be limited only by the claims and their equivalents.

[0149] Embodiments of the present disclosure are directed to systems, methods, and devices for wireless communication of analyte data, as well as interfaces for wireless communication of analyte data collected using an analyte sensor system. In various deployments described herein, the analyte data is glucose data generated by an analyte sensor system configured to connect to a display device, a partner device (e.g., a medical device such as an insulin pump), etc. More specifically, implementation of aspects of the present disclosure, including the systems, methods, apparatus, and devices described herein that use a diabetes management partner interface, may improve the flexibility of an analyte sensor system in wireless communication with a display device, one or more partner devices, and / or other (e.g., electronic) devices.

[0150] Moreover, implementing aspects of the present disclosure may enable improved performance with respect to the reliability, speed, and accuracy of wireless communications, including to partner devices and display devices (e.g., such devices may be manufactured by various third parties), and associated connection protocols and configurations. Additionally, in some cases, system requirements such as those with respect to accuracy, power consumption, and reliability may be less critical, and in such cases, different configurations and connection modes may be utilized to optimize or adapt system performance. In particular, some aspects of the present disclosure relate to setting or modifying connection parameters of an analyte sensor system based, for example, on the system requirements of a partner device, among other factors.

[0151] Details of several exemplary embodiments of the systems, methods, and devices of the present disclosure are set forth in this description, and in some cases elsewhere in the present disclosure. Other features, objects, and advantages of the present disclosure will become apparent to those skilled in the art upon review of the disclosure, description, drawings, examples, and claims. All such additional systems, methods, devices, features, and advantages are intended to be included (expressly or by reference) in this description, be within the scope of the present disclosure, and be protected by one or more of the accompanying claims.

[0152] A. System Overview and Example Configuration 1 illustrates a system 100 that may be used in connection with embodiments of the present disclosure that involve collecting, monitoring, and / or providing information regarding analyte levels present in a user's body, including, for example, the user's blood glucose level. System 100 illustrates aspects of an analyte sensor system 8 that may be communicatively coupled to display devices 110, 120, 130, and 140, a partner device 136, and / or a server system 134.

[0153] Analyte sensor system 8 in the illustrated embodiment includes sensor electronics module 12 and continuous analyte sensor 10 associated with sensor electronics module 12. Sensor electronics module 12 may wirelessly communicate (e.g., directly or indirectly) with one or more of display devices 110, 120, 130, and 140. In addition to or instead of display devices 110, 120, 130, and 140, sensor electronics module 12 may wirelessly communicate (e.g., directly or indirectly) with partner device 136 and / or server system 134. Similarly, in some examples, display devices 110-140 may additionally or alternatively wirelessly communicate (e.g., directly or indirectly) with partner device 136 and / or server system 134. The various couplings illustrated in FIG. 1 can be facilitated using wireless access point 138, as also mentioned below.

[0154] In certain embodiments, the sensor electronics module 12 includes electronic circuitry associated with measuring and processing continuous analyte sensor data, including candidate algorithms associated with processing and calibrating the sensor data. The sensor electronics module 12 can be physically connected to the continuous analyte sensor 10 and can be integral (permanently attached) or removably attached to the continuous analyte sensor 10. The sensor equipment unit 12 can include hardware, firmware, and / or software that enable measurement of analyte levels via the glucose sensor. For example, the sensor electronics module 12 can include a potentiostat, a power supply for powering the sensor, other components useful for signal processing and data storage, and a remote measurement module for transmitting data from the sensor electronics module to one or more display devices. The electronics can be affixed to a printed circuit board (PCB) or the like and can take a variety of forms. For example, the electronics can take the form of an integrated circuit (IC), such as an application-specific integrated circuit (ASIC), a microcontroller, and / or a processor.

[0155] Sensor electronics module 12 may include sensor electronics configured to process sensor information, such as sensor data, and generate transformed sensor data and displayable sensor information. Examples of systems and methods for processing sensor analyte data are described in more detail herein and in U.S. Pat. Nos. 7,310,544 and 6,931,327 and U.S. Patent Publication Nos. 2005 / 0043598, 2007 / 0032706, 2007 / 0016381, 2008 / 0033254, 2005 / 0203360, 2005 / 0154271, 2005 / 0192557, 2006 / 0222566, 2007 / 0203966, and 2007 / 0208245, all of which are incorporated by reference in their entireties.

[0156] 1 , display devices 110, 120, 130, and / or 140 may be configured to display (and / or alert) displayable sensor information that may be transmitted by sensor electronics module 12 (e.g., customized data packages transmitted to the display devices based on their respective preferences). Each of display devices 110, 120, 130, or 140 may include a display, such as touchscreen display 112, 122, 132, / or 142 (respectively), to display sensor information and / or analyte data to a user and / or receive input from a user. For example, a graphical user interface may be presented to the user for such purposes. In embodiments, the display device may include other types of user interfaces, such as a voice user interface, instead of or in addition to a touchscreen display for communicating sensor information to a user of the display device and / or receiving user input. In an embodiment, one, some, or all of display devices 110, 120, 130, 140 may be configured to display or otherwise communicate sensor information as it is communicated from sensor electronics module 12 (e.g., in a data package transmitted to the respective display device) without any additional future processing required for calibration and real-time display of the sensor data.

[0157] 1 may include a custom display device, such as analyte display device 110, specifically designed to display a particular type of displayable sensor information associated with analyte data received from sensor electronics module 12 (e.g., in embodiments, numerical values ​​and / or arrows). In an embodiment, one of display devices 110, 120, 130, 140 includes a smartphone, such as mobile phone 120, based on an Android, iOS, or other operating system, configured to display a graphical representation of continuous sensor data (e.g., including current and / or historical data). Other display devices 110, 120, 130, 140 may include other handheld devices, such as a tablet 130, a smartwatch 140, a partner device 136 (e.g., an insulin delivery device, whether automatic or manual, or a blood glucose meter), a smart refrigerator, a vehicle, a smart mirror, a smart clock, a smart drink, an implantable insulin delivery device, and / or a desktop or laptop computer.

[0158] The different display devices 110, 120, 130, 140, etc. and partner device(s) 136 may have different user interfaces, data package contents (e.g., amount, format, and / or type of data displayed, alarms, etc.) that can be customized (e.g., programmed differently by the manufacturer and / or end user) for each particular display device 110, 120, 130, 140, etc. and / or partner device(s) 136. Thus, in embodiments, multiple different display devices 110, 120, 130, 140 may wirelessly communicate directly with the sensor electronics module 12 (e.g., an on-skin sensor electronics module physically connected to the continuous analyte sensor 10) to enable multiple different types and / or levels of display and / or functionality associated with displayable sensor information during a sensor session, as described in more detail elsewhere herein.

[0159] 1 and described above, system 100 may also include a wireless access point (WAP) 138 that may be used to couple one or more of analyte sensor system 8, multiple display devices 110, 120, 130, 140, etc., server system 134, and medical device 136 to one another. For example, WAP 138 may provide WiFi and / or cellular or other wireless connectivity within system 100. Near field communication (NFC) may also be used between devices in system 100. Server system 134 may be used to collect analyte data from analyte sensor system 8 and / or multiple display devices to provide services or feedback, including, for example, performing analyses, generating universal or personalized models of glucose levels and profiles, remotely monitoring individuals or systems for analyte data, etc.

[0160] Referring now to Figure 2A, system 200 is depicted. System 200 may be used in connection with implementing embodiments of the disclosed systems, methods, apparatuses, and / or devices, including, for example, aspects described above in connection with Figure 1. By way of example, various below-described components of Figure 2A may be used to provide wireless communication of analyte (e.g., glucose) data between / among, for example, analyte sensor system 308, display device 310, partner device 315, and / or one or more server systems 334.

[0161] 2A , system 200 may include an analyte sensor system 308, one or more display devices 310, and / or one or more partner devices 315. Additionally, in the illustrated embodiment, system 200 includes a server system 334, which includes a server 334a coupled to a processor 334c and a storage device 334b. Analyte sensor system 308 may be coupled to display device 310, partner device 315, and / or server system 334 via a communication medium 305. Numerous details of the processing, collection, exchange of data, and / or performance of actions (e.g., execution of medication or related instructions) by analyte sensor system 308, partner device 315, and / or display device 310, etc., are provided below.

[0162] As described in detail herein, the analyte sensor system 308, the display device 310, and / or the partner device 315 can exchange messaging (e.g., control signaling) over the communication medium 305, and the communication medium 305 can be used to distribute analyte data to the display device 310, the partner device 315, and / or the server system 334. As alluded to above, the display device 310 can include a variety of electronic computing devices, such as, for example, smartphones, tablets, laptops, wearable devices, etc. The display device 310 can also include an analyte display device 110 customized for displaying and communicating analyte data and associated notifications. The partner device 315 can include medical devices such as insulin pumps or pens, connectable devices such as smart refrigerators or mirrors, key fobs, and other devices.

[0163] In embodiments, the communication medium 305 may be based on one or more wireless communication protocols, such as, for example, Bluetooth, Bluetooth Low Energy (BLE), ZigBee, WiFi, IEEE 802.11 protocols, infrared (IR), radio frequency (RF), 2G, 3G, 4G, 5G, etc., and / or wired protocols and media. It will also be understood, upon review of this disclosure, that the communication medium may, in some cases, be implemented as one or more communication links, including separate links between components of the system 200, regardless of whether such links are explicitly shown in or mentioned in connection with FIG. 2A . As an example, the analyte sensor system 308 may be coupled to the display device 310 via a first link of the communication medium 305 using BLE, while the display device 310 may be coupled to the server system 334 by a second link of the communication medium 305 using a cellular communication protocol (e.g., 4G LTE).

[0164] In embodiments, elements of system 200 may be used to perform the various processing operations described herein and / or to implement the various operations and / or features described herein with respect to one or more of the disclosed systems and / or methods. Upon reviewing this disclosure, one skilled in the art will understand that system 200 may include single or multiple analyte sensor systems 308, communication medium 305, and / or server system 334.

[0165] As described above, the communication medium 305 may be used to connect or communicatively couple the analyte sensor system 308, the display device 310, the partner device 315, and / or the server system 334 to one another or to a network. The communication medium 305 may be implemented in a variety of forms. For example, the communication medium 305 may include one or more of an Internet connection, such as a local area network (LAN), a person area network (PAN), a wide area network (WAN), an optical fiber network, power line Internet, a hardwired connection (e.g., a bus), DSL, etc., or any other type of network connection or communication coupling. The communication medium 305 may be implemented using any combination of routers, cables, modems, switches, optical fibers, wires, wireless (e.g., microwave / RF, AM, FM links, etc.), etc. Additionally, the communication medium 305 may be implemented using various wireless standards, such as Bluetooth, BLE, Wi-Fi, IEEE 802.11, 3GPP standards (e.g., 2G GSM / GPRS / EDGE, 3G UMTS / CDMA2000, or 4G LTE / LTE-A / LTE-U, 5G, or subsequent generations). Upon reading this disclosure, those skilled in the art will recognize other ways to implement the communication medium 305 for communication purposes and will also recognize that the communication medium 305 may implement features of the present disclosure using undeveloped communication standards that may be deployed in the future.

[0166] 2A , server 334a may receive, collect, and / or monitor information including analyte data, drug data, and related information from analyte sensor system 308, partner device 315, and / or display device 310, such as input responsive to analyte data or drug data, or input received in connection with an analyte monitoring application executing on analyte sensor system 308 or display device 310 (e.g., analyte sensor application application 425a, with reference to FIG. 4 ), or a drug delivery application executing on display device 310 or partner device 315 (e.g., drug delivery application 625, with reference to FIG. 5B ). Thus, server 334a may receive, collect, and / or monitor information from partner device 315, such as, for example, information regarding the provision of drugs to a user and / or information regarding the operation of one or more partner devices 315. Server 334a may also receive, collect, and / or monitor information regarding users of analyte sensor system 308, display device 310, and / or partner device 315.

[0167] In embodiments, server 334a may be adapted to receive such information via communication medium 305. This information may be stored in storage 334b ​​and processed by processor 334c. For example, processor 334c may include an analysis engine capable of performing analysis of information collected, received, etc. by server 334a via communication medium 305. In embodiments, server 334a, storage 334b, and / or processor 334c may be implemented as a distributed computing network, such as a Hadoop® network, or as a relational database, etc. Such information may then be processed at server 334a such that services may be provided to analyte sensor system 308, display device 310, and / or partner device 315, and / or its user(s). For example, such services may include diabetes management feedback to the user.

[0168] The server 334a may include, for example, an internet server, a router, a desktop or laptop computer, a smartphone, a tablet, a processor, a module, etc., and may be implemented in various forms, including, for example, an integrated circuit or collection of integrated circuits, a printed circuit board or collection of printed circuit boards, or a separate housing / package / rack, or multiple thereof. In an embodiment, the server 334a at least partially directs communications that occur over the communication medium 305. Such communications may include delivery of analyte data, drug data, and / or messaging related thereto (e.g., advertisements, authentication, commands, or other messaging). For example, the server 334a may process and exchange messages between and / or among the analyte sensor system 308, the display device 310, and / or the partner device 315, related to frequency bands, timing of transmissions, security / encryption, alarms, warnings, notifications, etc. The server 334a may update information stored in the analyte sensor system 308, the partner device 315, and / or the display device 310, for example, by distributing or updating applications thereto and / or by reconfiguring system parameters or other settings of the analyte sensor system 308, the partner device 315, and / or the display device 310. The server 334a may send and receive information to and from the analyte sensor system 308, the partner device 315, and / or the display device 310 in real time, periodically, sporadically, or on an event-driven basis. Additionally, the server 334a may implement cloud computing functionality for the analyte sensor system 308, the partner device 315, and / or the display device 310.

[0169] Referring now to FIG. 2B , a system 202 is depicted in accordance with an embodiment of the present disclosure, some of which involve the configuration and / or setup of a type of mesh network for connecting various devices described herein. As shown, an embodiment of system 202 includes an analyte sensor system 308 communicatively coupled to one or more of display devices 310 a, 310 b and / or partner devices 315 via a communication medium 305. Display device 310 a may be communicatively coupled to display device 310 b via communication medium 305 a. By way of example, FIG. 2B illustrates that in an exemplary implementation of the present disclosure, display device 310 a may connect to analyte sensor system 308 via communication medium 305 using a first connection scheme and a first wireless protocol (e.g., BLE). In turn, display device 310 a may also connect to display device 310 b via communication medium 305 a using a second connection scheme and a second wireless protocol (e.g., Wi-Fi, NFC, etc.). In embodiments, the connection between display device 310a and analyte sensor system 308 may then be closed, and display device 310b may establish a connection with analyte sensor system 308 while maintaining its connection with display device 310a. Additionally, display devices 310a and 310b may exchange analyte data with each other via communication medium 305a, for example, when either or each of display devices 310a, 310b receives analyte data via communication medium 305, i.e., from analyte sensor system 308.

[0170] Partner device 315 may also connect to display device 310b via communication medium 305 and / or communication medium 305b. Partner device 315 may also connect to analyte sensor system 308 via communication medium 305. It will be understood that any number of different connection schemes / protocols may be used to communicatively couple the components of system 202. For example, some network connections may be intermittently available and / or may not be available or preferred in some cases (due to system conditions such as device capabilities, geography, time, battery life, or interference requirements). Thus, in some cases, partner device 315 may not connect directly to analyte sensor system 308, but rather may connect indirectly to analyte sensor system 308 via display device 310b, which may be connected to analyte sensor system 308 via communication medium 305. In some cases, the display device 310b may not directly connect to the analyte sensor system 308, but rather may connect to the analyte sensor system 308 indirectly via a partner device 315, which may be connected to the analyte sensor system 308 via a communication medium 305. Additional aspects and features represented by FIG. 2B will become apparent upon review of this disclosure in its entirety.

[0171] In embodiments, the partner device 315 may not support the communication protocol utilized by the analyte sensor system 308 and / or it may otherwise be undesirable for the partner device 315 to connect directly to the analyte sensor system 308. Thus, the display device 310 (which, in examples, may support the communication protocol utilized by the analyte sensor system 308 and / or may otherwise be more preferable for connecting with the analyte sensor system 308) may connect to the analyte sensor system 308 and essentially act as a gateway device to the partner device 315. Thus, the partner device 315 may indirectly receive analyte data, etc. from and / or exchange information with the analyte sensor system 308. In some cases, this may be referred to as tethering. It will also be understood that in some cases, the partner device 315 may act as a gateway device for the display devices 310a, 310b such that the display devices 310a, 310b can connect to and receive analyte data from the analyte sensor system 308 via the partner device 315. It will also be understood that in example implementations of the system 304, one or more display devices 310a, 310b can be connected to the analyte sensor system 308 in parallel with each other and / or in parallel or series with one or more partner devices 315. Each display device 310a, 310b and / or partner device 315 can also connect a chain of display devices 310a, 310b and / or partner devices 315 to each display device 310a, 310b and / or partner device 315.

[0172] As alluded to above, wireless communication protocols may be used to transmit and receive analyte-related data, medication-related data, and other messaging or information (e.g., control signals, etc.) between the analyte sensor system 308, the display device 310, the partner device 315, and / or the server system 334 via the communication medium 305. In embodiments, such wireless protocols may be designed for use in wireless networks optimized for periodic small data transmissions (which may be transmitted at low rates, if necessary) between multiple devices over short distances (e.g., personal area networks). For example, one such protocol may be optimized for periodic data transfers in which the transceiver may be configured to transmit data at short intervals and then enter a low-power mode at longer intervals. The protocol may have low overhead requirements for both normal data transmissions and initializing the communication channel to reduce power consumption (e.g., reducing overhead). In some embodiments, a burst broadcast scheme (e.g., one-way communication) may be used. This eliminates the overhead required for acknowledgment signals, allowing for periodic transmissions that consume little power. In other embodiments, passive or active proximity-based protocols, of which NFC is one particular example, may be used to reduce overhead (e.g., overhead associated with typical pairing operations) and / or increase security.

[0173] The protocol may further be configured to establish communication channels with multiple devices while implementing an interference avoidance scheme. In some embodiments, the exemplary protocol described above may utilize an adaptive isochronous network topology that defines various time slots and frequency bands for communication with several devices. Accordingly, the protocol may change transmission windows and frequencies in response to interference to support communication with multiple devices. Accordingly, the wireless protocol may use a time- and frequency-division multiplexing (TDMA / FDMA)-based scheme. The wireless protocol may also use direct-sequence spread spectrum (DSSS) and frequency-hopping spread spectrum techniques. Various network topologies may be used to support short-range and / or low-power wireless communications, such as peer-to-peer, start, tree, or mesh network topologies, such as WiFi, Bluetooth, and BLE. The wireless protocol may operate in various frequency bands, such as the open ISM band, e.g., 2.4 GHz. Furthermore, to reduce power usage, the wireless protocol may adaptively configure data rates depending on power consumption.

[0174] In embodiments related to the configuration shown in FIG. 2B , a user interface, such as the GUI provided by user interface 435 of FIG. 4 , can present information about the mesh network to a user so that the user may maintain some level of control and / or input over its configuration. For example, the topography / topology of the mesh network can be provided, and the user can access connection links to change the connection model used, the connection parameters used, and / or the advertisement characteristics associated with various connections, etc. Moreover, the user may be able to switch between the display device 310 and / or the partner device 315 with respect to which devices can act as gateways to other devices. Additionally, the user, the analyte sensor system 308, the display device 315, and / or the partner device 315 may send control signaling to other network elements to manage the permissions / capabilities of other connected devices and / or the number / types of devices that can connect to the analyte sensor system 308, etc. In embodiments, the display device 310 and / or partner device 315 may be able to manage the network topography / configuration in an automated manner, for example, based on the system requirements of the partner device 315. To facilitate such automatic or semi-automatic management, the partner device 315 may access mesh network configuration information via a diabetes management partner interface, as described herein.

[0175] With the above description of aspects of the disclosed systems and methods for wireless communication of analyte data, examples of several specific features of the present disclosure are now provided. Those skilled in the art will understand, upon reviewing this disclosure, that these features may be implemented using aspects and / or combinations of aspects of the above exemplary configurations, regardless of whether explicit reference to these features is made.

[0176] B. Analyte Data 1 , as described above, in embodiments, an analyte sensor system 8 is provided for continuous measurement of an analyte in a host or user. By way of overview and example, the analyte sensor system 8 may be implemented as an encapsulated microcontroller that performs sensor measurements, generates analyte data (e.g., by calculating values ​​of continuous glucose monitoring data), and engages in wireless communications (e.g., Bluetooth and / or other wireless protocols) to transmit such data to remote devices (e.g., display devices 110, 120, 130, 140, partner device 136, and / or server system 134).

[0177] Analyte sensor system 8 may include a continuous analyte sensor 10 configured to continuously measure the concentration of an analyte in a host and a sensor electronics module 12 typically physically connected to the continuous analyte sensor 10 during sensor use. In an embodiment, sensor electronics module 12 includes electronics configured to process a data stream associated with the analyte concentration measured by the continuous analyte sensor 10 to generate sensor information including, for example, raw sensor data, converted sensor data, and / or other sensor data. Sensor electronics module 12 may be further configured to generate sensor information customized for each display device 110, 120, 130, 140, partner device 136, and / or server system 134. Sensor electronics module 12 may be further configured to enable different devices to receive different sensor information and may be further configured to wirelessly transmit the sensor information to such display devices 110, 120, 130, 140, partner device 136, and / or server system 134.

[0178] The term "analyte," as used herein, is a broad term and is to be given its ordinary and customary meaning to those skilled in the art (and is not limited to any special or customized meaning), and further refers to, but is not limited to, a substance or chemical constituent in a bodily fluid (e.g., blood, interstitial fluid, cerebrospinal fluid, lymph, or urine) that may be analyzed. Analytes may include naturally occurring substances, man-made substances, metabolites, and / or reaction products. In some embodiments, the analyte measured by the sensor head, devices, systems, and methods is glucose. However, acarboxyprothrombin, acylcarnitines, adenine phosphoribosyltransferase, adenosine deaminase, albumin, α-fetoprotein, amino acid profile (arginine (Krebs cycle), histidine / urocanic acid, homocysteine, phenylalanine / tyrosine, tryptophan), andrenostenedione, antipyrine, arabinitol enantiomers, arginase, benzoylecgonine (cocaine), biotinidase, biopterin, c-reactive protein, carnitine, carnosinase, CD4, ceruloplasmin, chenodeoxycholic acid, chloroquine, cholesterol, cholinesterase, conjugated 1-β-hydroxycholic acid, cortisol, creatine kinase, creatine kinase MM isoenzyme, cyclosporin A, d-penicillamine, dextromethorphan, ethoxybenzone, methylparaben ... fluchloroquine, dehydroepiandrosterone sulfate, DNA (acetylation polymorphism, alcohol dehydrogenase, alpha 1-antitrypsin, cystic fibrosis, Duchenne / Becker muscular dystrophy, glucose-6-phosphate dehydrogenase, hemoglobin A, hemoglobin S, hemoglobin C, hemoglobin D, hemoglobin E, hemoglobin F, D Punjab, beta-thalassemia, hepatitis B virus, HCMV, HIV-1, HTLV-1, Leber's hereditary optic neuropathy, MCAD, RNA, PKU, Plasmodium vivax, sex differentiation, 21-deoxycortisol), desbutylhalofantrine, dihydropteridine reductase, diphtheria / tetanus antitoxin, erythrocyte arginase, erythrocyte protoporphyrin, esterase D, fatty acids / acylglycines, free beta-human chorionic gonadotropin, free erythrocyte porphyrinFree thyroxine (FT4), free tri-iodothyronine (FT3), fumarylacetoacetase, galactose / gal-1-phosphate, galactose-1-phosphate uridyltransferase, gentamicin, glucose-6-phosphate dehydrogenase, glutathione, glutathione peroxidase, glycocholate, glycosylated hemoglobin, halofantrine, hemoglobin variants, hexosaminidase A, human erythrocyte carbonic anhydrase I, 17-α-hydroxyprogesterone, hypoxanthine phosphoribosyltransferase, immunoreactive trypsin, lactate , lead, lipoproteins ((a), B / A-1, β), lysozyme, mefloquine, netilmicin, phenobarbitone, phenytoin, phytanic acid / pristanic acid, progesterone, prolactin, prolidase, purine nucleoside phosphorylase, quinine, inverted tri-iodothyronine (rT3), selenium, serum pancreatic lipase, sisomicin, somatomedin C, specific antibodies (adenovirus, antinuclear antibody, anti-zeta antibody, arbovirus, Aujeszky's disease virus, dengue virus, guinea worm, Echinococcus granulosus, Entamoeba histolytica, enterovirus, Giardia lamblia (giardia duodenalisa), Helicobacter pylori, Hepatitis B virus, Herpes virus, HIV-1, IgE (atopic disease), Influenza virus, Leishmania donovani, Leptospirosis, Measles / Mumps / Rubella, Mycobacterium leprae, Mycoplasma pneumoniae, Myoglobin, Onchocerciasis volvulus, Parainfluenza virus, Plasmodium falciparum, Poliovirus, Pseudomonas aeruginosa, Respiratory syncytial virus, Rickettsia (scrub typhus), Schistosoma mansoni, Toxoplasma gondii, Treponema pallidum, Trypanosoma cruzi / Langer, Vesicular stomatitis virus virus), Wuchereria bancrofti, Yellow fever virus), specific antigens (Hepatitis B virus, HIV-1), succinylacetone, sulfadoxine, theophylline, thyrotropin (TSH), thyroxine (T4), thyroxine-binding globulin, trace elements, transferrin, UDP-galactose-4-epimerase, urea, uroporphyrinogen I synthase, vitamin A, leukocytes,Other analytes are contemplated, including, but not limited to, zinc protoporphyrin. Salts, sugars, proteins, fats, vitamins, and hormones naturally occurring in blood or interstitial fluid may also constitute analytes in certain embodiments. Analytes, such as metabolites, hormones, antigens, antibodies, and the like, may be naturally present in bodily fluids. Alternatively, analytes, such as contrast agents for diagnostic imaging, radioisotopes, chemical agents, fluorocarbon-based artificial blood, or drugs or pharmaceutical compositions, may be introduced into the body, including insulin, glucagon, ethanol, cannabis (marijuana, tetrahydrocannabinol, hashish), inhalants (nitrous oxide, amyl nitrite, butyl nitrite, chlorohydrocarbons, hydrocarbons), cocaine (crack cocaine), stimulants (amphetamines, methamphetamines, Ritalin, Cylert, Preludin, Didrex, PreState, Voranil, Sandrex, Plegine), depressants (barbiturates, methaqualone, tranquilizers), and the like. , e.g., Valium, Librium, Miltown, Serax, Equanil, Tranxene), hallucinogens (phencyclidine, lysergic acid, mescaline, peyote, psilocybin), narcotics (heroin, codeine, morphine, opium, meperidine, Percocet, Percodan, Tussionex, Fentanyl, Darvon, Talwin, Lomotil), designer drugs (fentanyl, meperidine, amphetamine, methamphetamine, and phencyclidine analogs, e.g., Ecstasy), anabolic steroids, and nicotine. Metabolites of drugs and pharmaceutical compositions are also contemplated as analytes. For example, analytes such as neurochemicals and other chemicals produced in the body, such as ascorbic acid, uric acid, dopamine, noradrenaline, 3-methoxytyramine (3MT), 3,4-dihydroxyphenylacetic acid (DOPAC), homovanillic acid (HVA), 5-hydroxytryptamine (5HT), and 5-hydroxyindoleacetic acid (FHIAA), may be analyzed.

[0179] C. Analyte Sensor System As alluded to above with reference to FIG. 1 , in embodiments, analyte sensor 10 comprises a continuous glucose sensor, such as, for example, a subcutaneous, transcutaneous (e.g., transdermal), or intravascular device. In embodiments, such a sensor or device is capable of analyzing multiple intermittent blood samples. Analyte sensor 10 can use any method of analyte measurement, including glucose measurement, including, for example, enzymatic, chemical, physical, electrochemical, spectrophotometric, polarimetric, calorimetric, iontophoretic, radiometric, immunochemical, etc.

[0180] In embodiments in which the analyte sensor 10 is a glucose sensor, the analyte sensor 10 can provide a data stream indicative of the glucose concentration in the host using any method, including invasive, minimally invasive, and non-invasive sensing techniques (e.g., fluorescence monitoring). The data stream is typically a raw data signal that can be converted into a calibrated and / or filtered data stream that can be used to provide a useful glucose value to a user, such as a patient or caregiver (e.g., a parent, relative, guardian, teacher, doctor, nurse, or any other individual interested in the health of the host).

[0181] The glucose sensor may be any device capable of measuring the concentration of glucose. According to one exemplary embodiment described below, an implantable glucose sensor may be used. However, it should be understood that the devices and methods described herein are applicable to any device capable of detecting the concentration of an analyte, such as glucose, and providing an output signal (e.g., as a form of analyte data) representative of the concentration of the analyte, also glucose.

[0182] In an embodiment, analyte sensor 10 is an implantable glucose sensor as described with reference to U.S. Patent No. 6,001,067 and U.S. Patent Publication No. US2005 / 0027463-A1. In an embodiment, analyte sensor 10 is a transcutaneous glucose sensor as described with reference to U.S. Patent Publication No. US2006 / 0020187-A1. In an embodiment, analyte sensor 10 is configured to be implanted in a host vessel or externally to the body as described in U.S. Patent Publication No. US2007 / 0027385-A1, co-pending U.S. Patent Publication No. US2008 / 0119703-A1, filed October 4, 2006, U.S. Patent Publication No. US2008 / 0108942-A1, filed March 26, 2007, and U.S. Patent Application No. US2007 / 0197890-A1, filed February 14, 2007. In embodiments, the continuous glucose sensor includes a transcutaneous sensor, such as described in U.S. Pat. No. 6,565,509 to Say et al. In embodiments, sensor 10 is a continuous glucose sensor including a subcutaneous sensor, such as described in U.S. Pat. No. 6,579,690 to Bonnecaze et al. or U.S. Pat. No. 6,484,046 to Say et al. In embodiments, the continuous glucose sensor includes a refillable subcutaneous sensor, such as described in U.S. Pat. No. 6,512,939 to Colvin et al. The continuous glucose sensor may include an intravascular sensor, such as described in U.S. Pat. No. 6,477,395 to Schulman et al. The continuous glucose sensor may include an intravascular sensor, such as described in U.S. Pat. No. 6,424,847 to Mastrototaro et al.

[0183] 3A and 3B depict perspective and side views of an enclosure 200 that may be used in connection with implementing an embodiment of an analyte sensor system 8 according to certain aspects of the present disclosure. The enclosure 200, in certain embodiments, includes a mounting unit 214 and a sensor electronics module 12 mounted to the mounting unit 214. The housing 200 is shown in a functional position including the mounting unit 214 and the sensor electronics module 12 matingly engaged with the mounting unit 214. In embodiments, the mounting unit 214, also referred to as a housing or sensor pod, includes a base 234 adapted to be secured to the skin of a host or user. The base 234 can be formed from a variety of rigid or flexible materials and can include a low profile to minimize protrusion of the device from the host during use. In embodiments, the base 234 is formed at least in part from a flexible material, which may provide advantages over other transcutaneous sensors that, unfortunately, may suffer from motion-related artifacts associated with host movement when the host is using the device. The mounting unit 214 and / or sensor electronics module 12 may be positioned over the sensor insertion site to protect the site and / or provide a minimal footprint (utilization of the surface area of ​​the host's skin).

[0184] In embodiments, a removable connection is provided between the mounting unit 214 and the sensor electronics module 12, which may allow for improved manufacturability, i.e., when refurbishing or maintaining the analyte sensor system 8, the potentially relatively inexpensive mounting unit 214 can be discarded, while the relatively expensive sensor electronics module 12 can be reused across multiple sensor systems. In embodiments, the sensor electronics module 12 is configured with signal processing (programming) configured to, for example, filter, calibrate, and / or execute other algorithms useful for calibrating and / or displaying sensor information. However, an integral (non-removable) sensor electronics module may be configured as well.

[0185] In an embodiment, the contacts 238 are mounted on or within a subassembly, hereafter referred to as the contact subassembly 236, configured to fit within the base 234 of the mounting unit 214 and a hinge 248 that allows the contact subassembly 236 to pivot between a first position (for insertion) and a second position (for use) relative to the mounting unit 214. As used herein, the term "hinge" is a broad term and is used in its original sense inclusively and without limitation to refer to any of a variety of pivoting, articulating, and / or hinge mechanisms, such as adhesive hinges, sliding joints, etc., and the term hinge does not necessarily imply a fulcrum or fixed point at which articulation occurs. In an embodiment, the contacts 238 are formed from a conductive elastomeric material, such as a carbon black elastomer, through which the sensor 10 passes.

[0186] 3A and 3B, in embodiments, the mounting unit 214 includes an adhesive pad 208 disposed on the back surface of the mounting unit and includes a peelable backing layer. Thus, when the backing layer is removed and a portion of the base 234 of the mounting unit 214 is finally pressed against the host's skin, the mounting unit 214 adheres to the host's skin. Additionally or alternatively, adhesive pads can be placed over some or all of the analyte sensor system 8 and / or sensor 10 after sensor insertion is complete to ensure adhesion and, optionally, an airtight or waterproof seal around the wound exit site (or sensor insertion site) (not shown). Appropriate adhesive pads can be selected and designed to stretch, stretch, conform, and / or vent the area (e.g., the host's skin). The specific embodiment described with reference to FIGS. 2A and 2B is described in more detail with reference to U.S. Pat. No. 7,310,544, the entire contents of which are incorporated herein by reference. The configuration and arrangement can provide water-resistant, waterproof, and / or sealed properties associated with the mounting unit / sensor electronics module embodiments described herein.

[0187] Various methods and apparatus suitable for use in conjunction with aspects of the embodiments described herein are disclosed in U.S. Patent Publication No. US2009 / 0240120-A1, which is incorporated herein by reference in its entirety.

[0188] 3C, a more detailed functional block diagram of the analyte sensor system 308 (e.g., described above in connection with FIGS. 2A and 2B) is provided. As shown in FIG. 3C, the analyte sensor system 308 may include an analyte sensor 535 (e.g., which may also be designated by reference numeral 10 in FIG. 1) coupled to a sensor measurement circuit 525 for processing and managing sensor data. The sensor measurement circuit 525 may be coupled to a processor / microprocessor 530 (e.g., which may be part of item 12 in FIG. 1). In some embodiments, the processor 530 may perform some or all of the functions of the sensor measurement circuit 525 to obtain and process sensor measurements from the sensor 535.

[0189] The processor 530 may further be coupled to a wireless unit or transceiver 510 (which may be part of item 12 in FIG. 1 ) for transmitting sensor and other data and receiving requests and commands and other signaling from an external device, such as a display device 310, which may be used to display or otherwise provide the sensor data (or analyte data) or data derived therefrom to a user, a server system 334, and / or a partner device 315, which may utilize the sensor data or derived data for medication (e.g., insulin) administration and / or diabetes management guidance to the user. As used herein, the terms “wireless unit” and “transceiver” may be used interchangeably and generally refer to devices capable of transmitting and receiving data wirelessly.

[0190] The analyte sensor system 308 may further include a memory device 515 (e.g., which may be part of item 12 in FIG. 1 ) and a real-time clock (RTC) 545 (e.g., which may be part of item 12 in FIG. 1 ) for storing and tracking sensor data and other data. For example, the memory device 515 may store configuration parameters 520. In general, the configuration parameters 520 relate to the operation of the analyte sensor system 308, and in embodiments, particularly to the operation of the analyte sensor system 308 relative to the partner device 315 and / or the display device 315. In embodiments, the configuration parameters 520 may be accessed (directly or indirectly) by the partner device 315 using a diabetes management partner interface 550. In this manner, the configuration parameters 520 may be set and / or modified according to the system requirements 650 (see FIG. 5B ) of the partner device 315. For example, the configuration parameters 520 may be modified to cause the analyte sensor system 308, the display device 310, and / or the partner device 315 to operate such that one or more system requirements 650 of the partner device 315 are met.

[0191] 3C , an embodiment of the analyte sensor system 308 includes a diabetes management partner interface (DMPI) 550. The diabetes management partner interface 550 may enable a partner device 315 connected to the analyte sensor system 308 to set and / or configure / modify configuration parameters 520 such that operation of the analyte sensor system 308, the display device 310, and / or the partner device 315 may meet the system requirements 650 of the partner device 315. The DMPI 550 may provide the partner device 315 with access to the configuration parameters 520 for configuration of the partner device 315. When the partner device 315 and / or the display device 310 are provided by different manufacturers and have different design goals / constraints, the DMPI 550 enables a flexible system that may access, set, and / or modify the configuration parameters 520 of the analyte sensor system 308 according to the system requirements and / or design constraints of the partner device 315 and / or the display device 310, respectively. This flexibility may improve the integration and interoperability of such devices, resulting in a more user-friendly and versatile ecosystem. Additional aspects of the DMPI 550 are further described below.

[0192] 3C , embodiments of the analyte sensor system 308 also include an interface dedicated to the display device 310 (as distinguished from the partner device 315). This interface may be a wireless interface that allows the display device 310 to connect to the analyte sensor system 308 and access, set, and / or modify / configure its configuration parameters 520 to facilitate communication with the analyte sensor system 308. As discussed further in connection with FIGS. 10A and 10B , this interface may be part of the DMPI 550, implemented within the DMPI 550 (e.g., as DMPI 750a), or implemented separately. In embodiments, the DMPI 550 is reconfigurable to adapt the characteristics of the display device 310 and / or partner device 315 that may connect to the analyte sensor system 308, as well as the overall system requirements and dynamics of, for example, system 200 (see FIG. 2A ).

[0193] Some components of the analyte sensor system 308 may periodically require replacement. For example, the analyte sensor system 308 may include an implantable sensor 535 that may be attached to a sensor electronics module that includes the sensor measurement circuitry 525. In addition, the analyte sensor system 308 may include a processor 530, a memory device 515, a transceiver 510, and a battery (not shown). The sensor 535 may require periodic replacement (e.g., every 7-30 days). The sensor electronics module may be configured to be powered and active for much longer than the sensor 535 (e.g., 3-6 months or longer) before the battery requires replacement. Replacing these components may be difficult and may require the assistance of trained personnel. Reducing the need to replace such components, particularly the battery, can significantly improve the convenience and cost of use of the analyte sensor system 308, including for users. In an embodiment, when the sensor electronics module is used for the first time (or, in some cases, restarted after the battery is replaced), the sensor electronics module is connected to the sensor 535 and a sensor session may be established. As described further below, there may be a process to initially establish communication between the display device 310 and the sensor electronics module when the module is first used or restarted (e.g., after a battery is replaced). Once the display device 310 and the sensor electronics module have established communication, they may communicate periodically and / or continuously over the life of several sensors 535, until, for example, the battery needs to be replaced. A new sensor session may be established each time a sensor 535 is replaced. A new sensor session may be initiated through a process completed using the display device 310, or the process may be triggered by notification of a new sensor 535 via communication between the sensor electronics module and the display device 310, which may persist between sensor sessions.

[0194] The analyte sensor system 308 of the example implementation collects analyte data using a sensor 535 and transmits the analyte data or a derivative of the analyte data to a display device 310, a partner device 315, and / or a server system 334. Data points regarding analyte values ​​may be collected and transmitted over the life of the sensor 535. New measurements and / or related information may be transmitted frequently enough for a remote device / individual to adequately monitor analyte (e.g., glucose) levels.

[0195] It should be understood that many details of the processing, collection, and exchange of data by the analyte sensor system 308, partner device 315, and / or display device 310, etc., are provided elsewhere herein. Upon review of this disclosure, it will be understood that the analyte sensor system 308, for at least some embodiments herein, may include some similar components described with respect to Figures 4 and 5B. Accordingly, details and use of such similar components may be understood for the analyte sensor system 308 even if not explicitly described herein with reference to Figure 3C.

[0196] D. Display Device 1 by way of example, aspects of display devices 110, 120, 130, and 140 that may be used in system 100 will now be described. In embodiments of the present disclosure, sensor electronics module 12 is configured to search for and / or attempt wireless communication with display devices from a list of display devices. By way of overview and example, typical display devices 110, 120, 130, 140 can wirelessly communicate with analyte sensor system 8, including for authentication of display device 110, 120, 130, 140 and / or analyte sensor system 8, and for exchange of analyte data and control signaling.

[0197] In an embodiment, the sensor electronics module 12 is configured to search for and / or attempt wireless communication with a list of display devices 110, 120, 130, 140, for example, in a predetermined and / or programmable order (e.g., grading and / or escalation), and a failed attempt to communicate and / or alert with a first display device among the display devices 110, 120, 130, 140 triggers an attempt to communicate and / or alert with a second display device among the display devices 110, 120, 130, 140, etc. In an exemplary embodiment, sensor electronics module 12 is configured to sequentially seek and attempt to alert the host or caregiver using a list of display devices 110, 120, 130, 140, such as: (1) a default display device (e.g., one of display devices 110, 120, 130, 140) or a custom analyte monitoring device (e.g., display device 110); (2) a cell phone (e.g., display device 120) via audible, tactile, and / or visual methods, such as a text message to the host and / or caregiver, a voice message to the host and / or caregiver, and / or 911; (3) a tablet (e.g., display device 130); (4) a smartwatch (e.g., display device 140). Of course, other types of display devices are encompassed and / or described herein, and alarms may additionally or alternatively be sent to partner device 136 and / or server system 334.

[0198] Depending on the embodiment, one or more display devices 110, 120, 130, 140 that receive data packages from sensor electronics module 12 can be adapted to be “dummy displays” and display the displayable sensor information received from sensor electronics module 12 without additional processing (e.g., predictive algorithm processing that may be necessary for real-time display of sensor information). In embodiments, the displayable sensor information includes transformed sensor data that does not require processing by the display device before displaying the displayable sensor information. Some display devices 110, 120, 130, 140 can include software (software programming including instructions configured to display the displayable sensor information and optionally query sensor electronics module 12 to obtain the displayable sensor information) including display instructions configured to enable display of the displayable sensor information on the display device. In embodiments, display devices 110, 120, 130, 140 are programmed with the display instructions at the manufacturer and can include security and / or authentication to prevent theft of and / or unauthorized access to the display devices 110, 120, 130, 140. In an embodiment, the display devices 110, 120, 130, 140 are configured to display the displayable sensor information via a downloadable program (e.g., a downloadable Java script via the Internet), and therefore any display device 110, 120, 130, 140 that supports downloading programs (e.g., any display device 110, 120, 130, 140 such as a mobile phone, tablet, PDA, PC, etc. that supports Java applets) can be configured to display the displayable sensor information.

[0199] In embodiments, a particular display device 110, 120, 130, 140 may wirelessly communicate directly with sensor electronics module 12, although intermediate network hardware, firmware, and / or software may be included in the direct wireless communication path. In embodiments, a repeater (e.g., a Bluetooth repeater) may be used to retransmit the transmitted displayable sensor information beyond the immediate range of the remote measurement module of sensor electronics module 12, the repeater enabling direct wireless communication when no substantial processing of the displayable sensor information occurs. In embodiments, a receiver / transmitter (e.g., a Bluetooth receiver / transmitter) may be used to retransmit the transmitted displayable sensor information, possibly in a different format, such as a text message to a television screen, the receiver / transmitter enabling direct wireless communication when no substantial processing of the sensor information occurs. In an embodiment, the sensor electronics module 12 wirelessly transmits the displayable sensor information directly to one or more of the display devices 110, 120, 130, 140, such that the displayable sensor information transmitted from the sensor electronics module 12 is received by one or more of the display devices 110, 120, 130, 140 without intermediate processing of the displayable sensor information.

[0200] In embodiments, one or more of the display devices 110, 120, 130, 140 may include a built-in authentication mechanism, and authentication may be required for communications between the sensor electronics module 12 and the display devices 110, 120, 130, 140. In embodiments, a challenge-response protocol, such as key authentication, is provided to authenticate data communications between the sensor electronics module 12 and the display devices 110, 120, 130, 140, where the challenge is a request for a key or hash or other value based on or derived from the key, and a valid response is the correct key or hash or other value based on or derived from the key, such that pairing of the sensor electronics module 12 and the display devices 110, 120, 130, 140 can be achieved by a user and / or manufacturer via a key. This may, in some cases, be referred to as two-way authentication. The key may be a software or hardware-level key. Additionally, the key may be a password (e.g., randomly generated or set by a user or other entity) and / or may be derived from a uniquely identifying characteristic (e.g., fingerprint, facial, or retinal information) or information, etc.

[0201] In embodiments, one or more display devices 110, 120, 130, 140 are configured to query sensor electronics module 12 for displayable sensor information, with display devices 110, 120, 130, 140 acting as master devices that request sensor information from sensor electronics module 12 (e.g., slave devices), e.g., in response to a query and on-demand. In some cases, display devices 110, 120, 130, 140 act as masters and sensor electronics module 12 act as slaves, although in other cases these roles may be reversed. For example, roles may be reversed depending on the nature of the communication, etc.

[0202] In embodiments, sensor electronics module 12 is configured for periodic, systematic, and / or regular transmission of sensor information (e.g., at 1, 2, 5, or 10 minute intervals, or at longer or shorter intervals) to one or more display devices 110, 120, 130, 140. In embodiments, sensor electronics module 12 is configured to transmit data packages associated with triggered alerts (e.g., triggered by one or more alert conditions). However, any combination of the above-described data transmission statuses can be implemented with any combination of paired sensor electronics module 12 and display devices 110, 120, 130, 140. For example, one or more display devices 110, 120, 130, 140 can be configured to query sensor electronics module 12 (directly or indirectly) to receive alarm information triggered by one or more alarm conditions being met. Additionally, the sensor electronics module 12 can be configured for periodic transmission of sensor information to one or more display devices 110, 120, 130, 140 (the same or different display devices as described in the previous examples), such that the system can include display devices 110, 120, 130, 140 that function differently with respect to how they obtain sensor information.

[0203] In embodiments, display devices 110, 120, 130, 140 are configured to query data storage memory within sensor electronics module 12 (e.g., with reference to FIG. 3C , storage device 515) for particular types of data content, including directly querying a database within the memory or storage device of sensor electronics module 12 and / or requesting a configured or configurable package of data content from a database; i.e., data stored in sensor electronics module 12 may be configurable, queriable, predetermined, and / or pre-packaged based on the characteristics and / or requirements of display devices 110, 120, 130, 140 with which sensor electronics module 12 is communicating. In additional or alternative embodiments, sensor electronics module 12 generates displayable sensor information based on information known to sensor electronics module 12 regarding which display devices 110, 120, 130, 140 are to receive a particular transmission. Additionally, some display devices 110, 120, 130, 140 may be capable of obtaining calibration information and transmitting the calibration information wirelessly to sensor electronics module 12, such as by manual entry of calibration information, automatic delivery of calibration information, and / or an integrated reference analyte monitor incorporated into display device 110, 120, 130, 140. U.S. Patent Publication Nos. 2006 / 0222566, 2007 / 0203966, 2007 / 0208245, and 2005 / 0154271, which are incorporated herein by reference in their entireties, describe systems and methods for providing an integrated reference analyte monitor incorporated into a display device (e.g., display device 110, 120, 130, 140) and / or other calibration methods in which embodiments disclosed herein may be implemented. In an embodiment, some display devices 110 , 120 , 130 , 140 may transmit calibration information to partner device(s) 136 .

[0204] In general, multiple display devices (e.g., a custom analyte monitoring device, sometimes referred to as analyte display device 110, a mobile phone 120, a tablet 130, a smartwatch 140, a reference analyte monitor, a drug delivery or medication device, a medical device, and a personal computer, etc.) may be configured to communicate wirelessly with sensor electronics module 12. Multiple display devices 110, 120, 130, 140 may be configured to display at least some of the displayable sensor information wirelessly communicated from sensor electronics module 12. The displayable sensor information may include, for example, sensor data, such as raw data, and / or converted sensor data, such as analyte concentration values, rate-of-change information, trend information, alert information, sensor diagnostic information, and / or calibration information. In an embodiment, display devices 110, 120, 130, 140 may receive analyte data from analyte sensor system 8 indirectly via another device (e.g., partner device 136 and / or server system 134). In embodiments, display devices 110, 120, 130, 140 may send commands or other control / configuration signaling to analyte sensor system 8 indirectly via another device (e.g., partner device 136 and / or server system 134). Display devices 110, 120, 130, 140 may also be used to provide warnings, alarms, and / or notifications (either visually, audibly, and / or tactilely) related to analyte data. Additional types of information that may be received at display devices 110, 120, 130, 140 may include information related to battery life or power consumption, other diagnostics, timing, etc.

[0205] In some cases, a display device 110, 120, 130, 140 that successfully communicates with analyte sensor system 8 and successfully completes the authentication process can be considered an authorized display device 110, 120, 130, 140. In some cases, display device 110, 120, 130, 140 can be configured in a display-only state where display device 110, 120, 130, 140 can access analyte data in a read-and-display manner. In this state, display device 110, 120, 130, 140 typically does not send commands related to continuous glucose monitoring (CGM) to analyte sensor system 8. However, other commands may be sent in this state. Exemplary CGM commands include commands to start, stop, or calibrate a CGM sensor session that generates analyte data using analyte sensor system 8. Examples of non-CGM commands include commands that do not affect the calculation of CGM data. Such non-CGM commands include, for example, commands to change advertisement parameters, modify whitelist criteria, and add additional display devices 110, 120, 130, 140 in read-only mode. Examples of display devices 110, 120, 130, 140 that may typically operate in a display-only state include small devices such as key fobs, where the key fob displays analyte data and associated warnings / alarms / notifications. However, in some circumstances, as described herein, display devices 110, 120, 130, 140 may operate in a display-only state.

[0206] In some cases, display devices 110, 120, 130, 140 may be configured in a display and control state, where in addition to accessing analyte data in a read and display manner, display devices 110, 120, 130, 140 may transmit CGM-related and other commands. In this state, other types of data may be readable / displayable, and as described above, display devices 110, 120, 130, 140 may transmit various types of commands to analyte sensor system 12 in addition to CGM commands.

[0207] 4 illustrates an exemplary aspect of the present disclosure that may be used in connection with the implementation of a display device 310 connectable to, for example, an analyte sensor system 308 and / or a partner device 315. It should be understood that many details of the processing, collection, and exchange of data by, for example, the analyte sensor system 308, the partner device 315, and / or the display device 310 are provided elsewhere herein. Upon review of the present disclosure, it will be understood that the display device 310 may include, for at least embodiments, several similar components that may be described with respect to FIG. 3C and / or FIG. 5B. Accordingly, details and use of such similar components may be understood for the display device 310 even if not explicitly described herein with reference to FIG. 4.

[0208] 4, the display device 310 may include several components for communicatively coupling with the analyte sensor system 308 and / or partner device 315 via a communication medium 305. The display device 310 may be used to alert a user and / or provide sensor or analyte data, control signaling, and / or other information (e.g., related to the partner device 315 and / or delivery of an agent) to the user and / or the analyte sensor system 308, another display device 310, and / or partner device 315. The display device 310 may include one or more of a connectivity interface 405 (which includes a transceiver 320), a memory device 415 (which stores the analyte sensor application 425 a, the partner device application 425 b, and / or additional applications), a processor / microprocessor 430 that processes and manages sensor and / or other data, a user interface 435 (e.g., a human-machine interface, an audio or visual interface (display, LEDs, speakers, microphones, etc.), haptic feedback, etc.) that may be used to provide / present information to and / or receive input from a user, and a real-time clock (RTC) 445. A bus (not shown here) may be used to interconnect the various elements of the display device 310 and transfer data between these elements.

[0209] The transceiver 410 may be used to receive sensor and / or other data and to send / receive requests, commands, other signaling, and / or data to / from the analyte sensor system 308, the partner device 315, and / or the server system 334. The transceiver 410 may use a communication protocol for sending and receiving such information. In embodiments, when a standardized communication protocol is used to communicate with (or between) the display device 310, commercially available transceiver circuitry may be utilized in the transceiver 410 that incorporates processing circuitry to handle low-level data communication functions, such as managing data encoding, transmission frequency, handshaking protocols, etc. In these embodiments, the processor 430 may not necessarily manage these activities, but rather may provide desired data values ​​for transmission and manage higher-level functions, such as powering up or down, setting the rate at which messages are transmitted, etc. Instructions and data values ​​for performing these high-level functions may be stored in the memory device 415 and provided to the transceiver circuitry via a data bus and transfer protocol established by the manufacturer of the transceiver 410.

[0210] The connectivity interface 405 may be used to interface the display device 310 to a communication medium 305 via which the display device 310 may be communicatively coupled (directly or indirectly) to the analyte sensor system 308, another display device 310, and / or a partner device 315 (see, e.g., FIG. 2A ). The transceiver 410 of the connectivity interface 405 may include multiple transceiver modules capable of operating with different wireless standards and / or frequency bands. The transceiver 410 may be used to transmit and receive analyte or drug delivery data and / or related commands and messages to and from the analyte sensor system 308, as well as to wirelessly communicate with the partner device 315. Additionally, the connectivity interface 405 may, in some cases, include additional components for controlling wireless and / or wired connections, such as a baseband and / or Ethernet modem, an audio / video codec, etc.

[0211] The storage device 415 may be used to store the operating system of the display device 310 and / or custom (e.g., proprietary) applications designed for wireless data communication between a remote transceiver and the display device 310. The storage device 415 may be a single memory device or multiple memory devices and may include volatile or non-volatile memory for storing data and / or instructions for software programs and applications. The instructions may be executed by the processor / microprocessor 430, for example, to control and manage the transceiver 410, the user interface 435, the applications 425a, 425b, and / or other components of the display device 310. The storage device 415 may include volatile memory (e.g., RAM) and / or non-volatile memory (e.g., flash storage), and may include EPROM, EEPROM, cache, and / or combinations / variations thereof. In various embodiments, the storage device 415 may store user input data and / or other data collected by the display device 310 (e.g., input from other users collected via the analyte sensor application 425a and / or the partner device application 425b, and / or information related to the partner device 315, including medication delivery data and related information). The storage device 415 may also be used to store the volume of analyte-related data received from the analyte sensor system 308 and / or the volume of medication-related data received from the partner device 315 for later retrieval and use, for example, to determine trends and / or trigger alerts.Additionally, the memory device 415 may store, for example, an analyte sensor application 425a and / or a partner device application 425b that, when executed using the processor 430, receives input (e.g., by conventional hard / soft keys or touch screen, voice detection, or other input mechanism or user interface 435) and allows a user to interact with analyte-related data and related content, and / or medication-related data and related content, and / or other information (e.g., related to system configuration), for example, via a GUI.

[0212] In embodiments, a user may interact with the analyte sensor application 425a and / or partner device application 425b via a GUI, which may be provided by a display of the user interface 435 of the display device 310. The GUI of the display device 310 may perform functions such as, for example, accepting user input and displaying menus and information derived from analyte or drug data. The GUI may be provided by various operating systems known in the art, such as, for example, iOS, Android, Windows Mobile, Windows, Mac OS, Chrome OS, Linux, Unix, gaming platform OS (e.g., Xbox, PlayStation, Wii), etc. By way of example, the display may be a touchscreen display that accepts various hand gestures as input.

[0213] In embodiments, application 425a may process and / or present analyte-related data received by display device 310 and present such data via a display of user interface 435 according to various operations described herein. Additionally, application 425a may be used to acquire, access, display, control, and / or interface with analyte data and associated messaging and processing related to analyte sensor system 308, as described in further detail herein.

[0214] The application 425a may be downloaded, installed, and initialized / setup on the display device 310. For example, the display device 310 may obtain the application 425a from the server system 334 or from another source accessed via the communication medium 305, such as an application store. Following installation and setup, the application 425a may be used to access and / or interface with analyte data (e.g., whether stored on the server system 334, locally from the storage device 415, or from the analyte sensor system 308). By way of example, the application 425a may present a menu including various controls or commands that may be performed in connection with the operation of the analyte sensor system 308 and one or more display devices 310. The application 425a may also be used to interface with or control other display devices 310 and / or partner devices 315 to distribute or make available analyte-related data, including, for example, by receiving / transmitting analyte data directly to the other display devices 310 and / or partner devices 315 and / or by transmitting instructions to the analyte sensor system 308 and other connected display devices 310 and / or partner devices 315, as described herein. Additionally, the application 425a in some implementations may interact with one or more additional applications supported by the display device 310, for example, to retrieve or provide relevant data. Such applications may include, by way of example, fitness / lifestyle monitoring applications, social media applications, etc. Such applications may also include applications associated with the partner device 315, including partner device application 425b, which will be described in more detail below.

[0215] The analyte sensor application 425a may include various code / functional modules, such as, for example, a display module, a menu module, a list module, etc., as will become apparent in light of the description of various functionalities herein (e.g., related to the disclosed methods). These modules may be implemented individually or in combination. Each module may include a (non-transitory) computer-readable medium upon which computer-executable code is stored, such that the code is operably coupled to and / or executed by the processor 430 (e.g., may include circuitry for such execution) to perform a particular function (e.g., as described herein with respect to various operations and flowcharts, etc.) related to interfacing with analyte-related data and performing tasks related thereto, and interfacing with other applications / devices.

[0216] As described further below, the display module may present various screens to the user (e.g., via a display of the user interface 435) with screens including graphical representations of information provided by the application 425a. In further embodiments, the application 425a may be used to display to the user an environment for viewing and interacting with the analyte sensor system 308 and various display devices 310 that may be connectable with the analyte sensor system 308 itself and / or with partner devices 315. The sensor application 425a may include native applications modified with a software design kit (e.g., depending on the operating system) to perform the functionality / features described herein.

[0217] 4 , a partner device application 425b may also be included in the storage device 415, and when executed, for example, using the processor 430, the application 425b may accept input (e.g., via conventional hard / soft keys or a touch screen, voice detection, or other input mechanism or user interface 435) to enable a user to interact with medication-related data and associated content, for example, via a GUI of the user interface 435. The application 425b may process and / or present medication-related and other partner device or system data received by or transmitted from the display device 310, and present such data via a display of the user interface 435, according to various operations described herein. Additionally, as described in further detail herein, the application 425b may be used to retrieve, access, display, control, and / or interface with medication, analyte, and / or other data and related messaging and processing associated with the partner device 315, the display device 310, and / or the server system 334.

[0218] In embodiments, the application 425b may be downloaded, installed, and initialized / setup on the display device 310. For example, the display device 310 may obtain the application 425b from the server system 334, where the application 425b may in some cases be provided by the manufacturer of the partner device 315 or from another source accessed via the communication medium 305, such as an application store. Following installation and setup, the application 425b may be used to access and / or interface with the partner device 315 including medication-related data (e.g., whether stored on the server system 334, locally from the storage device 415, or from the partner device 315 and / or analyte sensor system 308). As an example, the application 425b may cause the user interface 435 to present menus including various controls or commands that can be executed in connection with the operation of the partner device 315, the analyte sensor system 308, and / or one or more display devices 310.

[0219] The application 425b may interface with or control other display devices 310 and / or the partner device 315 for operation of the partner device 315 in the system / ecosystem described herein, for example, to receive / deliver or make available medication-related data, including, for example, by receiving medication-related data from the partner device 315 and / or the analyte sensor system 308 and / or by sending instructions for the analyte sensor system 308 and / or partner device 315 to be connected to or operate in a particular manner, as described herein. Additionally, the application 425b in some implementations may interact with one or more additional applications supported by the display device 310, for example, to retrieve or provide relevant data. Such applications may include, by way of example, fitness / lifestyle monitoring applications, social media applications, etc. Such applications may also include applications associated with the analyte sensor system 308 and / or display device 310, including the analyte sensor application 425a. As an example, communication between the analyte sensor application 425a and the partner device application 425b may facilitate sharing and coordination of alert information originating from the analyte sensor system 308 and / or the partner device 315.

[0220] The analyte sensor application 425b may include various code / functional modules, such as, for example, a display module, a menu module, a list module, etc., as will become apparent in light of the description of various functionalities herein (e.g., related to the disclosed methods). These modules may be implemented individually or in combination. Each module may include a (non-transitory) computer-readable medium on which computer-executable code is stored, such that the code is operatively coupled to and / or executed by the processor 430 to perform a particular function related to interfacing with the partner device 315, the display device 310, the server system 334, and / or performing tasks related thereto, and interfacing with other applications / devices.

[0221] As described further below, the display module may present various screens to the user (e.g., via a display of the user interface 435) with screens including graphical representations of information provided by the application 425b. In further embodiments, the application 425b may be used to display to the user an environment for viewing and interacting with various partner devices 315 that may be connectable with the analyte sensor system 308 and / or display device 310. The sensor application 425b may include a native application modified with a software design kit (e.g., depending on the operating system) to perform the functionality / features described herein. Such a software design kit may be provided by the manufacturer of the partner device 315 or by another entity.

[0222] 4, the storage device 415 of the display device 310 may also include configuration parameters 420. In an embodiment, the configuration parameters 420 govern aspects of wireless communication between / among the display device 310, the analyte sensor system 308, and / or the partner device 315. The configuration parameters 420 are described in further detail below, e.g., with reference to FIGS. 5B, 8, 9A-9S, 10A, and 10B. System requirements 450 may also be stored in the storage device 415. The system requirements 450 may relate to the partner device 315 and are described in further detail with reference to, e.g., FIGS. 5B, 8, 9A-9S, 10A, and 10B.

[0223] 4 , as described above, the display device 310 also includes a processor / microcontroller 430. The processor 430 may include, by way of example, a processor sub-module, including an application processor, that interfaces with and / or controls other elements of the display device 310 (e.g., the connectivity interface 405, the applications 425a, 425b, the user interface 435, and their components, the RTC 445, etc.). The processor 430 may include a controller and / or microcontroller that provides various controls (e.g., interfacing with virtual buttons / inputs, switches, etc.) related to device management, such as, for example, a list of available or previously paired devices, information related to measurements including analytes and medications, information related to network conditions (e.g., link quality, etc.), information related to the timing, type, and / or structure of messaging exchanged between the analyte sensor system 308, the display device 310, and / or the partner device 315, information related to diagnostics of various systems, information related to power management of the analyte sensor system 308, the display device 310, and / or the partner device 315, etc. Additionally, the controller may include various controls related to user input, such as a user fingerprint (e.g., for use in granting access to the user's data or authorizing / encrypting data, including analyte data) or other identifying information, and collection of analyte data and / or drug delivery data and / or related information.

[0224] The processor 430 may include circuits such as logic circuits, memory, battery and power-related management circuits, and other circuit drivers for peripheral components and audio / video and other components of the display device 310. The display device 310 may include other peripheral components not shown in detail in FIG. 4, and the processor 430 may be adapted to drive such peripheral components. The processor 430 and any sub-processors thereof may include logic circuits for receiving, processing, and / or storing data received and / or input to the display device 310 and data transmitted or distributed by the display device 310. The processor 430 may be coupled (e.g., by a bus) to the user interface 435, as well as the connectivity interface 405 and the storage device 415 (including the applications 425a, 425b). Thus, the processor 430 may receive and process electrical signals generated by each of these elements and thus perform various functions. As an example, processor 430 may access stored content in storage device 415 at the direction of applications 425a and / or 425b and process the stored content for display and / or output by a display or other mechanism of user interface 435. Additionally, processor 430 may process the stored content for transmission to other display devices 310, analyte sensor systems 308, server systems 334, and / or partner devices 315 via connectivity interface 405 and communication medium 305.

[0225] In embodiments, processor 430 may further acquire, detect, calculate, and / or store data input by a user via user interface 435 or data received from analyte sensor system 308 (e.g., analyte sensor data and associated messaging) and / or data received from partner device 315 (e.g., drug delivery data and associated data / messaging) over a period of time. Processor 430 may use this input to gauge the user's physical and / or psychological response to the analytes, drugs, or data, and other factors (e.g., time of day, location, etc.). In various embodiments, the user's responses or other factors may indicate recommendations regarding the use of particular display device 310 and / or partner device 315 under particular conditions, preferred dosages under particular conditions, and / or the use of particular connection / transmission schemes under various conditions, as described in further detail herein.

[0226] E. Partner Devices 1 , in an embodiment of the present disclosure, the above-described sensor electronics module 12 is configured to seek and / or attempt wireless communication with a partner device 136. By way of overview and example, a typical partner device 136 may wirelessly communicate with the analyte sensor system 8, including for authentication of the partner device 136 and / or the analyte sensor system 8, and for the exchange of analyte data, medication data, other data, and / or control signaling. The partner device 136 may include a passive device in an exemplary embodiment of the present disclosure.

[0227] FIG. 5A illustrates an example of a partner device 136, which, as shown, may be an insulin pump for administering insulin to a user. For various reasons, it may be desirable for such an insulin pump to receive and track glucose values ​​transmitted from the analyte sensor system 8 (see, e.g., FIG. 1 ). One reason for this is to provide the insulin pump with the ability to suspend / activate insulin administration based on glucose values ​​falling below / above a threshold. One exemplary solution for allowing a passive device (e.g., partner device 136) to receive analyte data (e.g., glucose values) without coupling to the analyte sensor system 8 is to include the analyte data in an advertisement message transmitted from the analyte sensor system 8 (as described by way of example with reference to FIG. 7C ). The data included in the advertisement message may be encoded such that only a device having an identity associated with the analyte sensor system 8 can decode the analyte data.

[0228] Partner device 136 may include an input / output 136a that may display, for example, glucose and other values ​​and may receive input via buttons, a wireless connection, or other mechanisms, including various user interface mechanisms. Partner device 136 may also include a connection 136b that interfaces with a user, for example, to administer insulin in response to input received at input / output 136a. In some cases, connection 136b may provide sensory alerts or other notifications to the user, for example, based on input received at input / output 136a and / or calculated values. It should be understood that an insulin pump may be implemented with many additional or alternative configurations of partner device 136.

[0229] More generally, partner device 136 may include medical and other devices configured to use analyte data received from analyte sensor system 8 for patient treatment and / or guidance. Partner device 136 may generally include medication delivery devices, where delivery of medication to a patient is conditioned, among other factors, on characteristics of the analyte data received from analyte sensor system 8. One example of a partner device 136 is an insulin pump. Another example of a partner device 136 is an insulin pen. Partner device 136 may be adapted to execute medication delivery applications using code or instructions stored in memory or storage of partner device 136, as described in more detail herein (e.g., with reference to FIG. 5B ).

[0230] For example, a partner device 136, such as an insulin pump that automatically delivers medication to a patient, may impose requirements on the quality and / or nature of the wireless connection / link through which the partner device 136 receives analyte data used to make decisions about medication delivery, and on the configuration of the ecosystem in which the partner device 136 is used. Additional types of partner devices 136 may impose similar or other requirements. For example, some partner devices 136 may require a more dedicated and robust connection, e.g., to ensure that a user or patient who relies on the pump for insulin delivery does not miss an insulin dose. In such an example, the connection through which the insulin pump receives analyte data should be relatively secure and reliable, and should reduce interference from other devices (e.g., display devices 110, 120, 130, 140). As another example, a partner device 136 may have certain constraints regarding battery life, accuracy with respect to calculations of CGM data, etc. The partner device 136 may be capable of sending CGM commands and other types of commands to the analyte sensor system 8 as described herein (e.g., see FIG. 5B) and also controlling the operating mode of the analyte sensor system 8 according to the system requirements 650 of the partner device 136.

[0231] In an exemplary implementation in which partner device 136 is an insulin pump, the insulin pump that is receiving analyte data from analyte sensor system 8 and engaged in automatic insulin delivery may, for example, request that other display devices 110, 120, 130, 140 not send CGM control commands to analyte sensor system 8. Such CGM control commands may affect the algorithms used to calculate the CGM data and, as a result, the amount of insulin delivered by the insulin pump, which may be undesirable / unexpected. To maintain control over the amount of insulin delivered, it may be desirable for the insulin pump to be able to prevent display devices 110, 120, 130, 140 from sending such CGM control commands. This may be done using various techniques described herein.

[0232] Other types of partner devices 136, such as insulin pens, smart refrigerators, smart mirrors, vehicles, and any other connected devices, may impose different or similar requirements and / or may have more relaxed requirements for wireless communication and other performance aspects. An injection device such as an insulin pen may receive analyte data from analyte sensor system 8 and use the analyte data to provide instructions or guidance (e.g., graphical, audible, tactile, etc.) to a user that they should (or should not) administer medication (e.g., inject insulin), and may also include dosage or injection timing suggestions. That is, unlike an insulin pump implementation of partner device 136, an insulin pen may rely on user action / intervention. A smart refrigerator implementation of partner device 136 may connect to analyte sensor system 8, monitor the analyte data and the user's food / drink consumption, and provide the user with feedback regarding the user's expected or resulting blood glucose levels associated with the food / drink consumption. A smart mirror implementation of partner device 136 may connect to analyte sensor system 8 and / or display devices 110, 120, 130, 140 and provide a heads-up display of analyte information and / or other guidance cues to the user for diabetes management and other types of healthcare suggestions.

[0233] As will be appreciated, just as many different types of partner devices 136 are possible, there are also numerous manufacturers that may provide partner devices 136 for operation with the analyte sensor system 8 and / or display devices 110, 120, 130, 140. There is a need for flexibility and adaptability in the system so that the interaction and performance of the various devices can be controlled and / or optimized so that interoperability, predictability, and extended use can be maintained and promoted across a wide range of device types and manufacturers, etc.

[0234] 5B, a more detailed exemplary functional block diagram of partner device 315 is provided. Upon review of this disclosure, it will be apparent that, for at least some embodiments, with respect to partner device 315, several similar components are described with respect to FIGS. 4 and 5 and display device 310 and analyte sensor system 308, and that details of the applicability and use of such similar components will be understood with respect to partner device 315, even if not explicitly described with reference to FIG.

[0235] 5B, embodiments of the partner device 315 may include a medication delivery mechanism 640 that may be used to deliver medication (e.g., insulin) to a user, such as based on analyte data generated using the analyte sensor system 308 and received at the partner device 315 via the communication medium 305. For example, if the partner device 315 is an insulin pump, the medication delivery mechanism 640 may, in embodiments, include an infusion set that can deliver insulin from a cannula or other type of reservoir internal or external to the partner device 315. Or, for example, if the partner device 315 is an insulin pen, the medication delivery mechanism 640 may include a needle that may be used to inject insulin into a user.

[0236] The partner device 315 may also include a processor / microcontroller 630 that may be coupled to a wireless unit or transceiver 610 for sending and receiving sensor data and requests and commands and other signals to and from external devices, such as the display device 310 and / or the analyte sensor system 308 and / or another partner device 315. The transceiver 610 may be part of a connectivity interface 605 within the partner device 315 and may be used to transmit medication-related information, including dosage, bolus information, warnings / alarms / notifications, etc., to the analyte sensor system 308, the display device 310, other partner devices 315, and / or the server system 334 (see FIG. 2A ).

[0237] The partner device 315 may further include a memory device 615 and a real-time clock (RTC) 645 for storing and tracking medication delivery data, sensor data, and / or other information (e.g., command / control signaling, link characteristics, user input, etc.). The memory device 615 may store, among other information / items, the medication delivery application 625 and / or other applications, and / or system requirements 650. The system requirements 650 of the partner device 315 may be imposed to address safety, regulatory, user experience, power consumption, reliability, and / or accuracy requirements for the operation and / or performance of the partner device 315, and in some cases other requirements applicable to the ecosystem in which the partner device 315 is used.

[0238] The medication delivery application 625 may process and / or present analyte, medication, and / or other data received or transmitted by the partner device 315 (e.g., received from the analyte sensor system 308, the display device 310, another partner device 315, and / or the server system 334) in accordance with various operations described herein, and may present aspects of some such data via the user interface 635. Additionally, the application 625 may be used in conjunction with the user interface 635 to obtain, access, display, control, and / or interface with medication, analyte, and / or other data and associated messaging and processing associated with the partner device 315, the display device 310, the analyte sensor system 308, and / or the server system 334. For example, the user interface 635 may allow a user to input user or other information into the partner device 315 to assist in administering medication to the user, authenticate the user (e.g., by fingerprint, face, voice, security code, etc.), and / or input user preferences or plans for operation of the partner device 315 (e.g., planned use or non-use, mode control, etc.), and / or the analyte sensor system 308 (e.g., sensor replacement, expected operation time, etc.), and / or the display device 310 (e.g., permissions for accessing data from the partner device 315). It will also be understood that the application 625 may execute on the partner device 315 but may not be visible to the user on the partner device 315. For example, the application 625 may be used to execute instructions to control the operation of the partner device 315, but the user's interface with the application 625 may be (or in some, but not all, cases) via the display device 310.

[0239] The application 625 may be downloaded, installed, and initialized / setup on the display device 315. For example, the partner device 315 may obtain the application 625 from the server system 334, where the application 625 may in some cases be provided by the manufacturer of the partner device 315 or from another source accessed via the communication medium 305, such as an application store. Following installation and setup, the application 625 may be used to access and / or interface with the partner device 315 including medication-related data (e.g., whether stored on the server system 334, locally from the storage device 615, or from the display device 310 and / or analyte sensor system 308). By way of example, the application 625 may be used to present menus (whether on the display device 310, the analyte sensor system 308, and / or the partner device 315) including various controls or commands that may be performed in connection with the operation of the partner device 315, the analyte sensor system 308, and / or one or more display devices 310.

[0240] The application 625 may also interface with or control the display device 310 and / or other partner devices 315 for the operation of the partner devices 315 in the system / ecosystem described herein (see, e.g., FIGS. 8 and 9A-9S) to receive / deliver or make available medication-related data, including, for example, by receiving medication-related or analyte-related data from the partner device 315, the display device 310, and / or the analyte sensor system 308 and / or by sending instructions to the analyte sensor system 308, the display device 310, and / or the partner device 315 to which it is connected in a particular manner, mode, etc. Additionally, the application 625 in some implementations may interact with one or more additional applications supported by the display device 310, for example, to retrieve or provide relevant data. Such applications may include, by way of example, fitness / lifestyle monitoring applications, social media applications, etc. Such applications may also include applications associated with the analyte sensor system 308 and / or the display device 310, including an analyte sensor application 425a and a partner device application 425b.

[0241] The medication delivery application 625 may include various code / functional modules, such as, for example, a medication delivery module, an authentication module, a system configuration module, etc., as will become apparent in light of the description of various functionality herein (e.g., related to the disclosed methods). These modules may be implemented individually and / or in combination. Each module may include a (non-transitory) computer-readable medium on which computer-executable code is stored, such that the code is operatively coupled to and / or executed by the processor 630 to perform a particular function related to interfacing with the partner device 315 and / or medication-related data and / or performing tasks related thereto, and interfacing with other applications / devices (e.g., the display device 310, the analyte sensor system 308, etc.).

[0242] As described further below, the display device 310 or the display module of the partner device 615 (e.g., via the display of the user interface 435 with reference to FIG. 4 and / or the display of the user interface 635 with reference to FIG. 5B ) may present various screens to the user including graphical representations of information provided by the application 625 (e.g., insulin dosage information). In further embodiments, the application 625 may be used to display to the user of the display device 310 an environment for viewing and interacting with the partner device 315. In embodiments, the partner device 315 may include a display as part of the user interface 635, in which case the application 625 may provide information for display directly on the partner device 315 (rather than using the display device 310). The medication delivery application 625 may include a native application modified with a software design kit (e.g., operating system dependent) to perform the functionality / features described herein. Such a software design kit may be provided by the manufacturer of the partner device 315 or by another entity.

[0243] 5B , the partner device 315 optionally includes a partner device controller 645. The partner device controller 645 may be used in conjunction with the partner device 315 to add functionality to the partner device controller 645. For example, in embodiments, the partner device 315 may not be equipped with wireless connectivity hardware / software. In such embodiments, the partner device controller 645 may be a “bolt-on” piece of hardware that couples to the partner device 315 via the connectivity interface 605 and can augment the operational capabilities and / or processing capabilities of the partner device 315 (e.g., by providing or adding a transceiver, memory, etc.) (e.g., including software code / instructions supporting that processing capability). Thus, in an example implementation, the partner device controller 645 may include a BLE or other radio for communicatively coupling the partner device 315 to the analyte sensor system 308 and / or the display device 310. In embodiments, the medication delivery application 625 may reside at least partially on the partner device controller 645. In an embodiment, the user interface 635 may reside at least in part on the partner device controller 645. For example, if the partner device does not have a user interface such as a display, the partner device controller may be used to add display functionality to the partner device 315.

[0244] At this point, it should be noted that similarly named elements, such as among the display device 310, analyte sensor system 308, and / or partner device 315 described in Figures 3C, 4, 5A, and 5B, may in some cases include similar features and / or functionality. Accordingly, with respect to such elements, a description of such elements with respect to any one of the display device 310, analyte sensor system 308, and partner device 315 above may apply to corresponding or similar elements within any one of the display device 310, analyte sensor system 308, and partner device 315.

[0245] F. Timing and Structure of Advertisements Additional aspects of the present disclosure include the order and manner in which various devices (e.g., display device 310 and partner device 315) connect to analyte sensor system 308, which may depend on the order, timing, structure, and manner of advertisement messages transmitted to such display device 310 and / or partner device 315. One potential scheme for the connection order of various devices may be described as follows:

[0246] In an embodiment, the analyte sensor system 308 advertises to and establishes a connection with display devices 310 and / or partner devices 315 that it is available for connection (e.g., within range and / or otherwise available). This may be done, for example, by transmitting an advertisement message. See, for example, operation 1005a shown in FIG. 7A . On the display device 310 / partner device 315 side, a display device 310 and / or partner device 315 seeking to connect with the analyte sensor system 308 may, in an exemplary embodiment, scan for and proceed with connection to the analyte sensor system 308 or another similar sensor system. This generally involves receiving and processing advertisement messages being broadcast by the analyte sensor system 308, etc., to determine whether such messages are being transmitted by a compatible / desired analyte sensor system 308.

[0247] The display device 310 and / or partner device 315 may then respond to the advertisement message by sending a connection request back to the analyte sensor system 308. For example, see operation 1005b shown in FIG. 7A . Upon receiving the connection request, the analyte sensor system 308 may accept, reject, or simply ignore the request. In an exemplary implementation, the analyte sensor system 308 services the connection of only one display device 310 or partner device 315 at a time. Thus, one reason for rejecting or ignoring a connection request may be that the analyte sensor system 308 is already connected to the display device 310 or partner device 315. If there is no basis for rejecting or ignoring the connection request, the analyte sensor system 308 may accept the request and connect to the display device 310 or partner device 310 that sent the request. For example, operation 1005b indicates the analyte sensor system 308 accepting the request by sending signaling to the display device 310 or partner device 315 indicating that the connection request has been granted. Aspects of advertisements and associated context are also illustrated by way of example with reference to Figures 6 and 7A-7C (see, e.g., operations 1065a, 1095a). A detailed discussion of these figures is included further below.

[0248] 7A , once the display device 310 (or partner device 315) and the analyte sensor system 308 are connected, messaging may be exchanged, including, for example, the analyte sensor system 308 transmitting analyte data to the display device 310 or partner device 315. See, for example, operation 1005d shown in FIG. 7A . In an embodiment, to prevent the display device 310 or partner device 315 from remaining connected to the analyte sensor system 308 longer than expected or desired, the analyte sensor system 308 may enforce a timeout and / or cause a timeout to be enforced. That is, for example, there may be a predetermined limit set on the duration of the connection, the expiration of which may terminate the connection to the analyte sensor system 308. See, for example, operation 1015 shown in FIG. 7A , where the data connection is closed and, optionally, the transceiver 410 is deactivated. Terminating a connection may allow the analyte sensor system 308 and other display devices 310 and / or partner devices 315 to connect, or at least attempt to connect. The analyte sensor system 308 may maintain a list of display devices 310 and / or partner devices 315 that have recently connected to the analyte sensor system 308. In some cases, this may be known as a whitelist. The analyte sensor system 308 may use this list to allow only the listed display devices 310 and / or partner devices 315 (i.e., recently connected or otherwise listed) to connect to the analyte sensor system 308.

[0249] 6 is a timing diagram illustrating an example of transmission of an advertisement message according to an embodiment of the present disclosure. More specifically, FIG. 6 provides an example of an advertisement duration structure 622 that may be used in connection with establishing a pairing or connection between / among an analyte sensor system 308, a display device 310, and / or a partner device 315. In this regard, according to an embodiment of the advertisement duration structure 622, the advertisement message 618 may be transmitted according to a time interval that occurs periodically based on a schedule, which may be referred to herein in some cases as an advertisement window interval 612. The period of recurrence of the advertisement window interval 612 may be of any length.

[0250] In embodiments, the advertisement window interval 612 may be configured or set to vary depending on the nature of the analyte sensor system 308's operation with respect to collecting and processing analyte data, and / or depending on the nature of the partner device 315's operation with respect to administering medication, and / or based on other considerations. In an example implementation, the advertisement window interval 612 may be configured or set to vary based on whether the partner device 315 is connectable to the analyte display device 308. In an example implementation, the advertisement window interval 612 may be configured or set to vary based on the system requirements 650 of the partner device 315. In an example implementation, the advertisement window interval 612 may be configured or set to vary based on the network topology of the system in which the analyte sensor system 308 communicates with one or more of the partner device 315, the display device 310, and the server system 334 (e.g., system 200 with reference to FIG. 2A , system 800 with reference to FIG. 8 , and / or system 900 with reference to FIG. 9A ). For example, the advertisement window interval 1012 may be configured or set to vary based on the number of display devices 310 connectable to the analyte sensor system 308, based on whether the partner device 315 is an automatic insulin delivery device, and / or based on the system requirements 650 of a partner device 315 that is an automatic insulin delivery device. In one particular example, the advertisement window interval 612 is approximately 5 minutes. Therefore, in this particular example, every 5 minutes there is a time window during which the advertisement message 618 is transmitted.

[0251] The time window of the advertisement message 618 may be considered the period during which the advertisement message 618 may actually be transmitted. This may also be referred to as the advertisement period 614 in some cases. By way of example, in some exemplary implementations, the advertisement period 614 may range in length from 7 to 22 seconds. However, upon reviewing this disclosure, one skilled in the art will understand that the length (in time) of the advertisement period 614 may range from 0 to any reasonable amount of time. In some cases, the advertisement period 1014 is shorter than the advertisement window interval 612. However, this may change based on system configuration / requirements, as described in detail elsewhere herein.

[0252] During the advertisement period 614, the advertisement messages 618 may, in some cases, but not necessarily, be transmitted periodically according to an advertisement message interval 616. The advertisement message interval 616 may be considered the time interval between sequential or consecutive transmissions of the advertisement messages 618. A particular example range for the advertisement message interval 616 is 20 to 90 milliseconds, although review of this disclosure will understand that the advertisement message interval 616 may be shorter or longer and / or may be adaptively variable, programmable, and / or configurable in length depending on the relevant circumstances, including adapting or (re)configuring the advertisement message interval 616 during the advertisement period 614.

[0253] In embodiments, the advertisement message interval 616 may be configured or set to vary depending on the nature of the analyte sensor system 308's operation with respect to collecting and processing analyte data, and / or depending on the nature of the partner device 315's operation with respect to administering medication, and / or based on other considerations. In an example implementation, the advertisement message interval 616 may be configured or set to vary based on whether the partner device 315 is able to connect to the analyte display device 308. In an example implementation, the advertisement message interval 616 may be configured or set to vary based on the system requirements 650 of the partner device 315. In an example implementation, the advertisement message interval 616 may be configured or set to vary based on the network topology of the system in which the analyte sensor system 308 communicates with one or more of the partner device 315, the display device 310, and the server system 334 (e.g., system 200 with reference to FIG. 2A , system 800 with reference to FIG. 8 , and / or system 900 with reference to FIG. 9A ). For example, the advertisement window interval 612 may be configured or set to vary based on the number of display devices 310 that can be connected to the analyte sensor system 308, based on whether the partner device 315 is an automatic insulin delivery device, and / or based on the system requirements 650 of a partner device 315 that is an automatic insulin delivery device.

[0254] After the advertisement window interval 612 has elapsed, the advertisement message 1018 may resume transmission, and the advertisement duration structure 622 may be repeated (e.g., as advertisement duration structure 622′). Also, note that one or more of the advertisement message interval 616, the advertisement period 1014, and the advertisement window interval 612 may be reconfigured between the advertisement period structures 622 and 622′ and / or within the respective advertisement periods of the advertisement period structures 622, 622′ (e.g., 614, etc.).

[0255] The above-described features of the advertisement period structure 622, including the advertisement window interval 612, the advertisement period 614, and the advertisement message interval 616, may each vary based on a variety of factors. For example, the values ​​of these parameters may vary based on the type and / or number of display devices 310 present, as well as the system requirements of such display devices 310 and / or the time since such display devices 310 have been connected to the analyte sensor system 308. As another example, the values ​​of these parameters may vary based on the type and / or number of partner devices 315 present, as well as the system requirements 650 and / or other characteristics of such partner devices 315 (e.g., whether automatic insulin delivery is provided). The values ​​of these parameters may also vary to optimize connection reliability, accuracy, battery life, speed connection times, etc. of the display devices 310 and / or partner devices 315. Any one of decreasing the advertisement window interval 612, increasing the advertisement period 614, and decreasing the advertisement message interval 616 may increase the likelihood of successfully establishing a connection between a particular display device 310 and / or partner device 315 and the analyte sensor system 308 or other device, although, in examples, changing parameters in this manner may simultaneously increase power consumption.

[0256] It should also be appreciated that one or more advertisement periods 614 may be individually assigned to particular display devices 310 or partner devices 315 for connection. Thus, by revoking the assignment of an advertisement period 614 from a particular device, or not assigning an advertisement period 614 to such a device in the first place, it is possible to prevent a connection from being established between such a device and the analyte sensor system 308. This may be done, for example, when a dedicated connection between the partner device 315 and the analyte sensor system 308 is desired; such a dedicated connection may be substantially immune to potential interference caused by devices other than the partner 315 responding to advertisements transmitted by the analyte sensor system 308.

[0257] Accordingly, aspects of the present disclosure include configuring an advertisement period structure 622, which includes configuring an advertisement window interval 612, an advertisement period 1014, and / or an advertisement message interval 616, as well as other functions associated with and / or related to advertisement messaging. Aspects of the present disclosure also include controlling the allocation of advertisement periods 614 to particular devices (e.g., display device 310 and / or partner device 315) to create advertisement slots dedicated to such particular devices.

[0258] The aforementioned aspects of the present disclosure may be used to increase the likelihood of successfully establishing a connection with the analyte sensor system 308. Additionally, configuring the advertisement period 612 and / or controlling the allocation of the advertisement period 614 may also reduce power consumption associated with establishing a connection due to increased efficiency of the connection protocol. In this manner, the overall reliability of communications related to analyte data and / or drug delivery may be increased while simultaneously reducing power consumption. In embodiments, the aforementioned aspects of advertisement messaging may be configured to provide intelligent trade-offs between reliability, speed, power consumption / efficiency, etc., including being dynamically implemented based on, for example, the system requirements 650 of the partner device 315, which may be unknown prior to the partner device 315 attempting to establish a connection with the analyte sensor system 308.

[0259] Now, with regard to the above-described features of connection establishment and / or advertisement messaging, in addition to the analyte sensor system 308 transmitting advertisement messages to the display device 310 and / or partner device 315 for connection establishment purposes, the display device 310 and / or partner device 315 may similarly send advertisement messages for connection establishment purposes. In such cases, it will be understood upon review of this disclosure that the above-described features may be used in a similar manner.

[0260] G. Connection Model As alluded to above, embodiments of the present disclosure also include various connection models for communication between or among the analyte sensor system 308, the display device 310, the server system 334, and / or the partner device 315. One connection model of communication may be referred to as an intermittent connection model (or, in some cases, a connect / disconnect model). According to an intermittent connection model, communication between / among the analyte sensor system 308, the display device 310, the server system 334, and / or the partner device 315 may be periodic or intermittent in nature according to a defined or event-based / asynchronous schedule. For example, the display device 310 and / or the partner device 315 may periodically (e.g., once every five minutes) establish a connection with the analyte sensor system 308 to exchange analyte and / or other data with the analyte sensor system 308.

[0261] In example implementations, rather than the transmit and receive circuitry of the analyte sensor system 308, the display device 310, and / or the partner device 315 communicating continuously, the analyte sensor system 308, the display device 310, and / or the partner device 315 may establish communication channels therebetween intermittently, regularly, and / or periodically. Thus, for example, the analyte sensor system 308 may in some cases communicate via wireless transmission with the display device 310 and / or the partner device 315 at predetermined time intervals. The duration of the predetermined time interval may be selected to be long enough so that the analyte sensor system 308 does not consume too much power by transmitting data more frequently than necessary, but frequent enough to provide substantially real-time sensor information (e.g., measured glucose values ​​or analyte data) to the display device 310 for output to a user and / or to the partner device 315 (e.g., via a display as part of the user interface 435), for use in, for example, administering medication. The predetermined time interval may be, for example, every five minutes in some embodiments, although it should be understood that this time interval may be changed to any desired length of time (e.g., as described above in connection with FIG. 6).

[0262] In embodiments, the intermittent connection model may result in power savings compared to other connection models. Thus, when battery power is a primary concern related to packet loss and / or latency, etc., the intermittent connection model may be preferred over the continuous connection model. Additionally, it will be understood that, according to the intermittent connection model, the display device 310 and / or partner device 315 in the example implementation are not simultaneously connected to the analyte sensor system 308. Rather, different display devices 310 and / or partner devices 315 connect, in some cases, for different, limited amounts of time. Which display devices 310 and / or partner devices 315 can connect, and when such devices can connect to the analyte sensor system 308, may be controlled, for example, using a list, such as a whitelist, and / or by modifying the advertisement structure used, as described above with reference to FIG. 6 . Thus, in some situations, the intermittent model may be appropriate and / or preferred. One such situation may be when a user prefers to monitor analyte values ​​using multiple display devices 310. For example, if a user has type 1 diabetes, monitoring analyte (e.g., glucose) data may be relatively important, and thus multiple display devices 310 may be used for greater coverage / redundancy.

[0263] 7A is an operational flow diagram illustrating various operations that may be performed in connection with an embodiment of a method 700 for wireless communication of analyte data between / among an analyte sensor system 308, a display device 310, a server system 334, and / or a partner device 315 according to the intermittent connection model described above. Features of method 700 may also be applicable in connection with related system, apparatus, and device embodiments. More specifically, as shown in FIG. 7A, a communication session 720 may include operations 1005a-1015, although in an embodiment, not all of these operations are necessarily performed.

[0264] 7A may be performed, for example, by processors 430, 530, and / or 630 executing instructions embodied in storage devices 415, 515, and / or 615 (which may include, for example, non-transitory computer-readable media), respectively. The tasks or operations performed in connection with the procedure may be performed by hardware, software, firmware, and / or combinations thereof incorporated into one or more computing devices, such as one or more of analyte sensor system 308, display device 310, server system 334, and / or partner device 315.

[0265] Upon review of this disclosure, it will be understood that a procedure may include any number of additional or alternative tasks or actions. This is generally, but not necessarily always, true of all procedures and / or methods described herein. The exemplary actions shown in FIG. 7A do not necessarily have to be performed in the order shown, and procedures may be combined into more comprehensive procedures or processes having additional functionality not described in detail herein with particular reference to FIG. 7A. Again, this is generally, but not necessarily always, true of all procedures and / or methods described herein.

[0266] In some examples described below, the analyte value is a glucose value based on one or more measurements made by the analyte sensor system 308 and / or sensor 535 (see FIG. 3C ). Nevertheless, upon review of this disclosure, it should be understood that, in embodiments, the analyte value may be any other analyte value described herein or known in the art. Wireless data communication between the analyte sensor system 308, the display device 310, the server system 334, and / or the partner device 315 may be referred to as a “T” time period, which may correspond to the duration between successive wireless communication sessions between the transceiver 510 of the analyte sensor system 308 (see FIG. 3C ), the transceiver 410 of the display device 310 (see FIG. 4 ), and / or the transceiver 610 of the partner device (see FIG. 5B ). interval" may occur periodically in time separated by an update interval, denoted "." Alternatively or additionally, an update interval may be considered a period of time during which recently measured or generated glucose values, medication-related data, or other data is obtained and transmitted. Transmission of advertisement signals or messages, establishment of data connections (e.g., communication channels, etc.), and requesting and transmitting data each occur within an update interval T interval Inside "T Active This may occur during a wireless communication session that lasts for an active time or period marked "." One note here is that T interval and / or T Active Between successive wireless communication sessions, the components of the analyte sensor system 308 (e.g., transceiver 510), the components of the display device 310 (e.g., transceiver 410), and / or the components of the partner device 315 (e.g., transceiver 610) may use the "T Inactive The device may enter a low power mode or similar mode, such as an inactive or sleep mode during periods of inactivity marked "." This may allow, for example, to preserve battery life and reduce peak voltage requirements.

[0267] Thus, in some connection schemes used for communicating analyte data, medication data, and / or other data and control signaling, a connection may be established periodically between / among the analyte sensor system 308, the display device 310, the server system 334, and / or the partner device 315. For example, and with further reference to FIG. 7A , a communication session 720 may implement one such connection scheme (optionally including authentication). More specifically, the communication session 720 may be established over a time interval T interval As suggested above, T interval is T Active and the active part corresponding to T Inactive Generally speaking, T ActiveDuring this time, the analyte sensor system 308 and the display device 310 and / or partner device 315 are connected and actively exchanging messaging (e.g., pursuant to operation 1005 and / or sub-operations thereof), but as described above, the analyte sensor system 308, the display device 310, and / or the partner device 315 may transition to a low power mode, etc., T Active There may be periods in between.

[0268] With respect to connections, in an example implementation, the analyte sensor system 308 may transmit one or more advertisement messages at operation 1005 during the communication session 720. The advertisement messages may be viewed as invitations for the display device 310 and / or the partner device 315 to establish a data connection with the analyte sensor system 308 (e.g., via the transceiver 510). An example structure of an advertisement message that may be transmitted in some cases for the purpose of establishing a connection between two devices according to various aspects of the present disclosure is described above in connection with FIG. 6 and in U.S. Provisional Patent Applications Nos. 62 / 364,771 and 62 / 409,677, which are incorporated herein by reference in their entireties. The transmitted advertisement messages may then be received at the display device 310 (e.g., via the transceiver 410) and / or the partner device 315 (e.g., via the transceiver 610).

[0269] As alluded to above, during the communication session 720, an authentication procedure may optionally be performed in connection with the data connection process corresponding to operation 1005b and / or the data transmission process corresponding to operation 1005d. To establish a data connection with the analyte sensor system 308, the display device 310 and / or the partner device 315 may wait or scan until an advertisement message transmitted by the analyte sensor system 308 is received. Thus, operation 1005b may involve the analyte sensor system 308 receiving a connection request from the display device 310 and / or the partner device 315 and responding thereto by granting or denying the request. If the analyte sensor system 308 grants the connection request, an acknowledgment or other message may be transmitted to the display device 310 and / or the partner device 315 as part of operation 1005b. A data connection between the analyte sensor system 308 and the display device 310 and / or the partner device 315 may then be established.

[0270] According to act 1005c, an authentication procedure may be used before data is actually exchanged in act 1005d. Authentication may involve the exchange of various messages, including challenge and hash values ​​and associated signaling, between the analyte sensor system 308 and the display device 310 and / or partner device 315 according to a one-way or two-way handshake process per act 1005c. Once authenticated, the analyte sensor system 308 and the display device 310 and / or partner device 315 may exchange information to determine how data will be exchanged (e.g., specific frequencies, time slot allocations, encryption, etc.). Additionally, the communication session 720 may also include the exchange of application keys between the analyte sensor system 308 and the display device 310 and / or partner device 315. Through the exchange of challenge and hash values ​​described in connection with act 1005c, such application keys may be effectively shared between the analyte sensor system 308 and the display device 310 and / or partner device 315. Thus, in an embodiment, the application key may be used for both authentication and encryption purposes.

[0271] 7A , after completion of the optional authentication process per act 1005c, the analyte sensor system 308 and the connected display device 310 and / or partner device 315 may engage in data communication per act 1005d, during which the connected display device 310 and / or partner device 315 may request and receive desired information (e.g., analyte data, control information, identification information, and / or instructions) from the analyte sensor system 308 and / or may transmit information including command and control signaling or other information, such as, for example, medication-related information. Upon completion of the data communication per act 1005d, the data connection may be terminated per act 1015 (e.g., by closing the established communication channel).

[0272] However, in other situations, a continuous connection model may be appropriate and / or preferable compared to the intermittent connection model described above. At a high level, the continuous connection model may involve an initial pairing between the analyte sensor system 308 and the display device 310 and / or partner device 315, after which the analyte sensor system 308 and the display device 310 and / or partner device 315 remain connected and do not inherently close or disconnect the connection. That is, the connection and data exchange in the exemplary implementation does not occur periodically or intermittently as in the intermittent connection model (e.g., as described with reference to FIG. 7A ); instead, the connected devices periodically exchange messaging to maintain the connection. As data becomes available at the analyte sensor system 308, the data may be transmitted to the display device 310 and / or partner device 315 in near real-time, or at least near real-time. In this manner, the overall accuracy and responsiveness of communications related to analyte data may be improved. An additional benefit associated with the serial connection model is that it may enable the analyte sensor system 308 to better mitigate interference caused by unwanted devices (e.g., in some cases, unwanted display devices 310) that seek to connect with the analyte sensor system 308. Thus, the reliability of data exchange and the robustness of the connection may be increased, which may be particularly important when a user relies on the partner device 315 for the administration of medications such as insulin.

[0273] As an example, a potential increase in reliability of data exchange may be beneficial, for example, when partner device 315 is an insulin pump used to automatically deliver insulin to a user based on analyte data generated using analyte sensor system 308 and transmitted to partner device 315. In some such cases, connection reliability / robustness between analyte sensor system 308 and partner device 315 is more important compared to the ability to establish connections with multiple display devices 310, and, as mentioned above, connection requests from display devices 310 may cause interference with the connection, or establishment of a connection, between partner device 315 and analyte sensor system 308. For example, a serial connection model used between analyte sensor system 308 and partner device 315 can serve as a means to increase connection reliability / robustness and, therefore, may be preferred in certain embodiments involving partner device 315, as well as other situations described and / or suggested herein.

[0274] Accordingly, embodiments of the present disclosure include using a serial connectivity model between certain devices. Such a connectivity model may, in some cases, reduce the latency between the collection and / or generation of analyte data at the analyte sensor system 308 and the transmission of such data and associated data and control signaling to the connected display device 310 and / or partner device 315, as well as the exchange of medication-related data and control signaling, while maintaining sufficiently low power consumption of the analyte sensor system 308. Furthermore, as discussed above, the serial connectivity model may increase the reliability / robustness and predictability of the connection between the analyte sensor system 308 and the display device 310 and / or partner device 315.

[0275] In this regard, Figure 7B illustrates an example implementation of a method 702 for wireless communication of analyte data between / among analyte sensor system 308 and display device 310 and / or partner device 315 according to an example implementation of the serial connectivity model suggested above. A communication session 740 can be initiated in connection with method 702. More specifically, as shown in Figure 7B, communication session 740 can involve operations 1095a-g and / or 1095a', although in an embodiment, not all of these operations are necessarily performed.

[0276] Similar to FIG. 7A , the various tasks performed in connection with the procedures shown in FIG. 7B may be performed, for example, by processors 430, 530, and / or 630 executing instructions embodied in storage devices 415, 515, and / or 615, respectively (which may include, for example, non-transitory computer-readable media). The tasks or operations performed in connection with the procedures generally, and not necessarily, relate to all of the procedures, operations, and methods described herein, and may be performed by hardware, software, firmware, and / or any combination thereof, incorporated into one or more computing devices, such as analyte sensor system 308, display device 310, server system 334, and / or partner device 315. It will be understood, upon review of this disclosure, that a procedure may include any number of additional or alternative tasks or operations. The operations illustrated by way of example in FIG. 7B need not necessarily be performed in the order shown, and the procedures may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein with particular reference to FIG. 7B .

[0277] With respect to the continuous connection model, if the connection between / among the analyte sensor system 308 and the display device 310 and / or partner device 315 is not maintained, analyte data may be dropped or lost. This may lead to an inappropriate or inaccurate representation of analyte information, such as an estimated glucose value, and in some cases, may lead to the administration of medication that is not as accurate or precise as desired. Therefore, embodiments herein related to the continuous connection model involve persisting and / or maintaining an established connection between / among the analyte sensor system 308 and the display device 310 and / or partner device 315. Furthermore, with respect to maintaining the connection, it may be useful to monitor the connection status and derive and / or provide instructions therefor. One way this may be done is by using connection parameters.

[0278] At operation 1095a, the method 702 may involve activating a transmitter of the analyte sensor system 308 and / or transmitting an advertisement message. This transmission of the advertisement message may be substantially similar to operation 1005a described above. The advertisement message transmitted at operation 1095a may be received by, for example, one or more display devices 310 and / or partner devices 315.

[0279] At operation 1095b, a connection may be established between the analyte sensor system 308 and the display device 310 and / or partner device 315 that are responsive to the advertisement message. As part of operation 1095b, connection parameters may be exchanged between the analyte sensor system 308 and the display device 310 and / or partner device 315. In this regard, the analyte sensor system 308, the display device 310, and / or the partner device 315 may propose and set up a set of connection parameters upon which aspects of the connection with the analyte sensor system 308 may be based.

[0280] Examples of connection parameters include a connection interval (which in some cases may be referred to herein as a ping interval), a slave delay, and a monitor timeout. The analyte sensor system 308 and / or display device 310 and / or partner device 315 may use one or more of such connection parameters to maintain a connection for continuous exchange of data related to, for example, analyte levels, drug delivery, related control signaling, system configuration signaling, etc. Additional connection parameters may relate to control signaling, such as mode control of the display device 310 and / or partner device 315, and / or control signaling related to network topologies that may be implemented in accordance with embodiments described herein.

[0281] Following the connection determination resulting in the establishment of a connection, at operation 1095c, method 702 may optionally involve authentication. At operation 1095d, embodiments of method 702 include exchanging data between / among the analyte sensor system 308, the display device 310, and / or the partner device 315. For a continuous connection model, operation 1095d is repeated periodically as data transmission becomes available (e.g., aperiodically in some cases) and / or whenever data is desired to be exchanged (e.g., on-demand). The exchange of data per operation 1095d may be interspersed with the exchange of other messaging, such as, for example, ping messaging or other control-related messaging exchanged with the analyte sensor system 308. In FIG. 7B, this may be represented, by way of example, using the operations intervening between operations 1095d and 1095d′ (i.e., operations 1095e and 1095f), although the particular type of control signaling may not be explicitly shown.

[0282] In embodiments, connection parameters agreed upon in connection establishment (e.g., as part of operation 1095b), as well as other configuration aspects, may be updated / modified, for example, after a connection decision is made. Thus, at operation 1095f, method 702 may involve updating one or more of the connection parameters. As shown in operation 1095g, in some cases, a connection with the analyte sensor system 308 may be terminated or lost. This may have various causes. In response to the connection loss at operation 1095g, the analyte sensor system 308 may transmit an advertisement message, per operation 1095a′. In accordance with an example embodiment of the continuous connection model, when the analyte sensor system 308 and the display device 310 and / or partner device 315 become disconnected, the analyte sensor system 308 may resume transmitting advertisement messages at least approximately immediately in some cases.

[0283] A user of the display device 310 and / or partner device 315 may not be aware that operation 1095g caused a disconnection. This may result in dropped packets or loss of data in some cases. Therefore, in some cases, the analyte sensor system 308 may automatically resume advertising without user intervention. Alternatively or additionally, the user may receive notification via the analyte sensor system 308, display device 310, and / or partner device 315 that the connection has been lost.

[0284] 7C illustrates that in addition to the intermittent and continuous connection models, embodiments of the present disclosure also involve communicating data via packet broadcasts where establishing such a connection is not necessary. As described in more detail herein, the broadcasting of data packets indicates that a particular device connectable to the analyte sensor system 308, e.g., display device 310, is set to a display-only state, and another connectable device(s), e.g., partner device 315, has established a connection with the analyte sensor system 308 and is exchanging data and command / control messaging with the analyte sensor system 308.

[0285] 7C, a method 706 for wireless communication of analyte-related data, medication-related data, and / or other information between / among analyte sensor system 308, display device 310, and / or partner device 315 is shown in connection with an implementation of the present disclosure. An exemplary embodiment of method 706 involves, for example, establishing a first connection between analyte sensor system 308 and display device 310 and / or partner device 315. This is optional and may include establishing a first connection between analyte sensor system 308 and display device 310 and / or partner device 315. interval Establishing the first connection may occur in association with a communication session 720 corresponding to the analyte sensor system 308. Accordingly, establishing the first connection may optionally include authentication between the analyte sensor system 308 and the display device 310 and / or the partner device 315.

[0286] The method 706 also includes interval may be the same as or different from the time interval T interval Establishing a communication session 760 that may be implemented between the interval 'T Active ' and the active part corresponding to T Inactive and an inactive portion corresponding to T Active During ', the communication session 760 may involve operation 1065 and its sub-operations.

[0287] It should be noted here that, as discussed above, the communication session 760 may not include establishing connections between / among the analyte sensor system 308, the display device 310, and / or the partner device. For example, the illustrated communication session 760 does not include the data connection aspect of operation 1005b shown in FIG. 7A in connection with the communication session 720. The illustrated communication session 760 also does not include authentication processing (e.g., at operation 1005c) that may be included in the communication session 720. Rather, at operation 1065a, the method 706 involves sending one or more advertisement messages to the display device 310 and / or the partner device 315.

[0288] Thus, as part of the communication session 760, the analyte sensor system 308 may transmit a first advertisement message (e.g., act 1065a). The first advertisement message may include at least a first portion of the analyte value. The analyte value may not need to be encrypted (e.g., using an application key) prior to transmission. In other words, with respect to the communication session 760, the analyte sensor system 308 may use one or more advertisement messages to transmit encrypted or unencrypted analyte values ​​or analyte data and / or other signaling (e.g., timing and control information, etc.), in addition to other information that may be included in the advertisement message.

[0289] In some cases, the advertisement message may take the form of a packet. By way of example, the analyte value (encrypted or not) may be included in a reserved field or other field of the advertisement message packet and / or may be encoded in the packet. The advertisement message may also or additionally include other information, such as a timestamp associated with the analyte value. In an example implementation, method 706 may involve splitting a payload that may include the (encrypted) analyte value and associated data into multiple portions. In that case, a first advertisement message may indicate that a second advertisement message includes a second portion of the analyte value and / or associated data. The first advertisement may indicate this by tagging the first portion of the payload, where the tag indicates that a subsequent advertisement message may include the second portion of the payload.

[0290] In other words, according to the communication session 760, an advertisement message may be transmitted in connection with operation 1065a for the purpose of communicating analytes and / or other data to the display device 310 and / or the partner device 315. Encrypting the payload using an application key may maintain privacy / security even in the absence of an authentication procedure performed during the communication session 760. Similarly, because the payload is included in the advertisement message, the data connection request and data transmission process (e.g., operations 1005b and 1005d, respectively, with reference to FIG. 7A ) may also be bypassed or avoided. In this manner, the number of messages exchanged according to the communication session 760 (and thus power consumption) may be reduced compared to other communication sessions. Additionally, analytes and other data may be provided to the display device 310 even when, for example, the partner device 315 maintains a dedicated connection to the analyte sensor system 308 and serves as the only device authorized to send command and control signals (e.g., calibration commands associated with the sensor session) to the analyte sensor system 308.

[0291] 7C , the communication session 760 may also include, at act 1065b, the display device 310 and / or the partner device 315 acknowledging receipt of the advertisement message(s) transmitted during act 1065a by transmitting an acknowledgement (ACK) message. In some cases, this acknowledgement may trigger a data connection process between the analyte sensor system 308 and the acknowledging display device 310 and / or the partner device 315. For example, the analyte sensor system 308 may then transmit an ACK to the display device 310 and / or the partner device 315, thereby establishing a connection therewith. This data connection process, in an exemplary deployment, may be used for updating application and / or encryption key(s), and / or for exchanging other data, such as calibration data, timing information, authorization exchange, mode control signaling, etc. Upon completion of the communication at act 1065, the data transmission may terminate at act 1075. At this point, the transceiver 510 and / or processor 530 of the analyte sensor system 308 may be deactivated. In FIG. 7C, this generally corresponds to operation 1075, where T Inactive ' is added.

[0292] As described above, various trade-offs may exist between the intermittent connection model and the continuous connection model. For example, using the continuous connection model may consume battery power faster in some cases, but may provide improved reliability / robustness. Therefore, in some cases, it may be desirable to switch to the intermittent connection model. In another example, operating in the intermittent connection model may increase the likelihood of dropped / lost data due to multiple connection requests / acknowledgments. Therefore, in some cases, it may be desirable to switch to the continuous connection model. In an additional example, the control / command signaling permissions of a particular device may change, for example, due to changes in network topology and / or operating mode, and in such cases, the connection model may change (e.g., including a broadcast scheme for advertisements, as described with reference to FIG. 7C).

[0293] Accordingly, embodiments of the present disclosure involve switching between these connectivity models to provide a flexible and adaptable system that can be optimized for a variety of applications, operating conditions, and user / system preferences. Adaptively switching (whether in an automated manner or based on user input, both of which are contemplated herein) can enable optimization of battery power usage, as well as transmission efficiency, data accuracy, and connection reliability / robustness. Additionally, in accordance with exemplary embodiments, device performance and behavior can be tracked over time and used to develop optimization profiles for situations in which different connectivity models may be preferable.

[0294] In some cases, the connection model may be automatically switched depending on various criteria. For example, the connection model may be set depending on the type of display device 310 and / or partner device 315 connected to the analyte sensor system 308. For example, the connection model may be set based on the number of display devices 310 being used, such that if a single dedicated device is being used (e.g., for a predetermined amount of time), the system may switch to a continuous connection model. Or, if many display devices 310 are being used, multiple display devices 310 may utilize the communication session 740. In another example, the connection model may be switched based on the current or predicted battery life of the analyte sensor system 308, the display device 310, and / or the partner device 315. The quality of the exchanged signals may also be used to determine whether switching between connection models is appropriate. Additionally, switching between connection models may be based on the time and / or location of the analyte sensor system 308, the partner device 315, and / or the display device 310. The switching may be initiated by the display device 310, the partner device 315, and / or the analyte sensor system 308 (eg, using mode control signaling).

[0295] In embodiments, the switch may be based on user input or may be semi-automatic. For example, a user may manipulate a GUI provided by the user interface 435 of the display device 310 to implement the switch. In another example, the switch may be triggered automatically or without user intervention (e.g., by or in response to the partner device 315), which may then trigger a prompt to be presented to the user on the display device 310 via the GUI of the user interface 435. The user may then approve or reject the switch (thus making the switch semi-automatic). The prompt may provide information about the connection model currently being used, the reason for the proposed switch, and, in some cases, the consequences of rejecting and / or accepting the proposed switch. In other examples, no prompt may be provided to the user.

[0296] Turning now to FIG. 7D , embodiments of the present disclosure involve configuring and / or setting up a type of mesh network using the various connectivity models described herein (e.g., with reference to FIGS. 7A-7C ). For example, display device 310 and / or partner device 315 (and / or multiple, any devices) can connect with analyte sensor system 308 using different connectivity models. With reference to FIG. 7D and the example system 304 shown, analyte sensor system 308 may be connectable to display device 310 and / or partner device 315 via communication medium 305 (see FIG. 2B ). Additionally, display device 310 and partner device 315 may be connectable to each other via communication medium 305 (again with reference to FIG. 2B ). While communication medium 305 is referenced here, it will be understood that additional communication media and / or links can be included in the mesh network described herein and / or using various connectivity models (e.g., communication media 305a, 305b, etc., see FIG. 2B ).

[0297] 7D , for example, communication session 740 can be used between analyte sensor system 308 and partner device 315, while simultaneously using a different communication session (e.g., 720, 760, etc.) between display device 310 on one side and analyte sensor system 308 on the other side. Furthermore, yet another communication session can be used between display device 310 and partner device 315. FIG. 7D illustrates, with respect to system 304, that analyte sensor system 308 can be connectable to display device 310 and / or partner device 315 using various communication media (e.g., communication media 305) and / or connection models (e.g., intermittent connection model, continuous connection model, etc., as described in further detail with reference to FIGS. 7A-7C ), illustratively represented here as connection A and connection B. Additionally, display device 310 and partner device 315 may be connectable to each other using various communication media 305 and / or connection models, illustratively represented here as connection C. Specific details of the continuous and intermittent connection models are described in more detail in US Provisional Patent Applications Nos. 62 / 364,771 and 62 / 409,677, which are incorporated herein by reference in their entireties.

[0298] For example, if the display device 310 and partner device 315 are within range and connectable to the analyte sensor system 308, the analyte sensor system 308 and display device 310 may connect to the analyte sensor system 308 using an intermittent connection model (e.g., connection A), and the partner device 315 may connect to the analyte sensor system 308 using a continuous connection model (e.g., connection B). Under the intermittent connection model, as an example, the display device 310 periodically connects to the analyte sensor system 308, exchanges data with the analyte sensor system 308, and then disconnects. Under the continuous connection model, as an example, the partner device 315 and the analyte sensor system 308 establish a connection and then continuously exchange signaling to maintain the connection during data exchange. As a further example, in an intermittent connection model, between subsequent periodic connections, other devices may connect to the analyte sensor system 308 or may attempt to connect simultaneously with the display device 310, which may result in the display device 310 failing to reconnect with the analyte sensor system 308 (a variety of other circumstances may also lead to this). In contrast, under a continuous connection model, the connection between the partner device 315 and the analyte sensor system 308 is likely to be maintained and uninterrupted, typically absent a critical event. In this manner, the partner device 315 may be able to maintain a more reliable and prioritized connection with the analyte sensor system 308 and may have a better quality of service as a result. Thus, for example, in patient-critical applications, such as automated delivery of insulin by the partner device 315, a continuous connection model may be preferred, such as between the partner device 315 and the analyte sensor system 308.

[0299] 7D , the partner device 315 and the display device 310 may maintain communication over connection C using any of the connection models described herein. Thus, the partner device 315 may share medication delivery data and other information directly with the display device 310. It will be further understood that the respective connection models used by the display device 310 and the partner device 315 to connect to the analyte sensor system 308 may switch. It will also be understood that both the display device 310 and the partner device 315 may connect to the analyte sensor system 308 using an intermittent connection model or a continuous connection model. It will also be understood and described herein that in embodiments, one or more of the analyte sensor system 308, the display device 310, and the partner device 315 may use an advertisement broadcast connection scheme of the communication session 760 for any of connection A, connection B, and / or connection C of the system 304.

[0300] Regardless of the connection model used between the analyte sensor system 308 on one side and the display device 310 and / or partner device 315 on the other side, the display device 310 and partner device 315 can connect to each other using either an intermittent connection model, a continuous connection model, and / or an advertisement broadcast connection scheme (see FIG. 7C ) of a communication session 760. Furthermore, any of the communication mediums and / or connection models used (e.g., Connection A, Connection B, and Connection C) can be switched to different connection models after connection establishment, including during subsequent communication sessions.

[0301] H. Warning Summary In certain embodiments, one or more alerts, alarms, and / or notifications (in some cases, simply “alerts”) are associated with the analyte sensor system 308, the display device 310, and / or the partner device 315. For example, an alert may be accompanied by one or more alert conditions that indicate when the respective alert is triggered. An alert may be triggered based on characteristics of analyte data generated using the analyte sensor system 308. For example, a hypoglycemic alert may include an alert condition that indicates a minimum glucose level. An alert condition may also be based on transformed sensor data, such as trend data, and / or sensor data from multiple different sensors (e.g., an alert may be based on sensor data from both a glucose sensor and a temperature sensor). For example, a hypoglycemic alert may include an alert condition that indicates a minimum required trend in the host's glucose level that must exist before triggering the alert. As used herein, the term “trend” generally refers to data that indicates some attribute of data acquired over time, such as calibrated or filtered data from a continuous glucose sensor. Trends may indicate the amplitude, rate of change, acceleration, direction, etc. of data such as sensor data, including transformed or raw sensor data.

[0302] In embodiments, an alert may be triggered based on an event or condition monitored or detected at the partner device 315. For example, an alert may be triggered when the partner device is determined to have a mechanical or other fault (e.g., based on self-diagnostics). In an exemplary implementation where the partner device 315 is an insulin pump, an alert may be triggered based on a pump fault, such as an occlusion. In embodiments, an alert may be triggered if the partner device 315 is not delivering insulin to the user or has not delivered insulin according to a calculated dosage (e.g., based on analyte data).

[0303] In certain embodiments, each alert is associated with one or more actions to be performed in response to triggering the alert. An alert action may include activating an alarm via a user interface of the analyte sensor system 308, such as displaying information on a display of the analyte sensor system 308, activating an audible or vibration alarm of the analyte sensor system 308, etc. In embodiments, the alert action includes transmitting data to one or more display devices 310 and / or partner devices 315 so that an alert may be provided via the user interface 435 and / or 635 (see FIGS. 4 and 5B). For alert actions associated with a triggered alert, one or more delivery options may define the content and / or format of the data to be transmitted, the destination devices to which the data may be transmitted, the timing to which the data may be transmitted, and / or the communication protocols that may be used to deliver the data. For example, propagation of the alert may be prioritized to the partner device 315. However, in embodiments, due to the number of connected devices that may be used in connection with the collection and use of analyte data, a user may be inundated with alerts. In such cases, it may be beneficial to coordinate alerts and notifications across a user's devices according to an escalation scheme that may be predefined, adaptive based on network topology, and / or based on user preferences, for example.

[0304] In particular embodiments, multiple alert actions (each with respective delivery options) may be associated with a single alert, thereby enabling, for example, displayable sensor information or other alert information having different content and formatting to be transmitted to respective display devices 310 and / or partner devices 315 or other devices in response to the triggering of a single alert. For example, a mobile phone may receive a data package (which may be specially formatted for display on the mobile phone) containing minimal displayable sensor information, whereas a desktop computer may receive a data package containing most (or all) of the displayable sensor information generated by the sensor electronics module of the analyte sensor system 308 in response to the triggering of a general alert. Advantageously, the sensor electronics module need not be tied to a single display device 310, but rather can be configured to communicate with multiple different display devices 310 directly, systematically, simultaneously (e.g., via broadcast), regularly, periodically, randomly, on-demand, in response to a query, based on a warning or alarm, etc.

[0305] In embodiments, the analyte sensor system 308 is configured to provide one or more different alarms directly and / or via transmission (e.g., sequentially and / or simultaneously) of a data package indicating that an alarm should be initiated by one or more display devices 310. In certain embodiments, the analyte sensor system 308 simply provides a data field indicating that an alarm condition exists, and the display device 310 may determine to trigger an alarm upon reading the data field indicating the existence of an alarm condition. In some embodiments, the sensor electronics module determines which of the one or more alarms to trigger based on the one or more alarms that are triggered. For example, if the alarm trigger indicates severe hypoglycemia, the analyte sensor system 308 can perform multiple actions, such as activating an alert for the sensor electronics module, transmitting a data package to a monitoring device indicating the activation of an alarm for a display, and transmitting the data package as a text message to a care provider.

[0306] In an embodiment, the analyte sensor system 308 is configured to wait a time for the host to respond to a triggered alert (e.g., by pressing or selecting a snooze and / or off function and / or button on the analyte sensor system 308 and / or display device 310), and then can trigger additional alerts (e.g., in a cascading manner) until one or more alerts have been responded to. In an embodiment, the analyte sensor system can be configured to send a control signal (e.g., a stop signal) to a partner device 315 associated with the alarm condition (e.g., hypoglycemia), such as an insulin pump, where the stop alert triggers the pump to stop delivering insulin. While reference is made above to configuring the analyte sensor system to provide and / or trigger alerts, it should be understood that the display device 310 and / or partner device 315 may additionally or alternatively provide and / or trigger alerts.

[0307] I. Partner Device Connectivity Integration 8 depicts a system 800 that may be used, for example, in connection with wireless analyte (e.g., glucose) monitoring and, in some cases, for diabetes management, including, for example, medication delivery. System 800 may involve various components interconnected via one or more wired and / or wireless connections for communication and exchange of information, such as analyte data, medication delivery data, diabetes management feedback and related guidance and services, alerts / notifications, control signaling, and other information.

[0308] 8, an embodiment of system 800 includes one or more analyte sensor systems 308, display devices 310a, 310b, and / or 310c, partner device 315, server systems 334a and / or 334b, and services 805 that may be provided via server systems 334a and / or 334b. Note that in embodiments, server system 334b ​​may be associated with and / or maintained by the manufacturer or provider of partner device 315, and server system 334a may be associated with and / or maintained by the manufacturer or provider of analyte sensor system 308. Additionally, embodiment services 805 may be divided into separate services that are supported, maintained, promoted, and / or provided by the manufacturer / provider of analyte sensor system 308 on the one hand and partner device 315 on the other hand, respectively. Thus, server systems 334a and / or 334b ​​may provide a gateway for receiving services 805 (e.g., back-end cloud services). For services 805 supported only for the manufacturer of partner device 315 (e.g., in some cases, insulin pump-related information, alerts, malfunction support, etc.), such services 805 may be provided via server system 334b. For services 805 supported only for the manufacturer of analyte sensor system 308 (e.g., in some cases, a separate individual / entity provides users of display device 310 with the ability to monitor analyte data), such services 805 may be provided via server system 334a in this example. In an embodiment, service 805 may utilize both server systems 334a and 334b ​​(e.g., in some cases, a separate individual / entity provides users of display device 310 and partner device 315 with the ability to monitor analyte data and insulin administration data). Additional aspects of remote services that may be provided via cloud servers, eg, server systems 334a / 334b, are described below.

[0309] Certain of the aforementioned components and features of what is shown in Figure 8 have been described in large part above with reference to, for example, Figures 1, 2A, 2B, 3A-C, 4, 5A, 5B, 6, and 7A-D. Component system 800 may be interconnected by various links 802a-d, 804a-b, 806a-b, 808a-b, and 810, as shown in Figure 8, each of which may be implemented using communications medium 305 for communications purposes. It should be understood that links 802a-d, 804a-b, 806a-b, 808a-b, and 810 may be any type of communications link, including, for example, point-to-point, broadcast, multicast, etc. It should be understood that, with respect to an embodiment, like numbers shown in system 800 may be implemented in the manner described above.

[0310] 9A depicts a system 900 that may be used, for example, in connection with wireless analyte (e.g., glucose) monitoring and, in some cases, for diabetes management, including, for example, medication delivery. System 900 may involve various components interconnected via one or more wired and / or wireless connections for communication and exchange of information, such as analyte data, medication delivery data, diabetes management feedback and related guidance and services, alerts / notifications, control signaling, and other information. An embodiment of system 900 includes one or more of: an analyte sensor 308; a display device 910 including a mobile phone 910a, an analyte display device 910b, and / or a wearable device 910c; partner devices 915 that may include a medication delivery device 915a, a first insulin pump 915b, a second insulin pump 915c, and an insulin pen 915d; and / or a display device 910′ that may include a mirror 910d, a vehicle 910e, and / or a key fob 910f. In the example implementation shown in Figure 9A, these components are configured to be part of a personal area network (PAN) 902 and are interconnected by links 906a-j, 908, 916, and 918 as shown in Figure 9A, where each of these links may be implemented using communication medium 305 for communication purposes. PAN 902 may use at least one or more of BLE, Wi-Fi, etc.

[0311] System 900 may also include router 920a coupled to one or more devices in PAN 920 (e.g., to mirror 910d via link 914), although not all possible links are explicitly shown. Router 920a may then be coupled to server(s) 920(b) (e.g., server system 334, with reference to FIG. 2A ) via link 922, which may be coupled to a cell network 920c (e.g., a 4G LTE network, etc.) via link 924. Cell network 920c may also be coupled to a cellular-enabled device in PAN 902, such as mobile phone 910a, via link 926. In embodiments, any of the devices shown in FIG. 9A may be cellular-enabled and therefore directly coupleable to cell network 920c and / or WAN 904, or elements thereof. For example, analyte sensor system 308 may be equipped with cellular or other longer-range wireless components and therefore directly coupled to cell network 920c and / or WAN 904, or elements thereof. As shown in FIG. 9A , router 920a, server(s) 920b, and cell network 920c may be configured to be part of wide area network (WAN) 904. Links 914, 922, 924, and 926 may be implemented using communication medium 305 (e.g., wired, wireless, etc.). WAN 904 may generally provide cloud services to one or more devices in PAN 902. Again, not all possible links between devices in WAN 904 and devices in PAN 902 are explicitly shown, but they will be understood by those skilled in the art upon reviewing this disclosure. It should also be understood that in some cases, elements of WAN 904 may be incorporated into PAN 902, or vice versa.

[0312] Some of the aforementioned components of system 900 and their features have been described above, e.g., with reference to at least Figures 1, 2A, 2B, 3A-C, 4, 5A, 5B, 6, and 7A-C. Those skilled in the art will, upon reviewing this disclosure, recognize where and how the above description of these components may be applicable herein, whether or not it is expressly conveyed herein.

[0313] With respect to system 900, when system 900 includes partner device 915, two examples may drive a particular arrangement and / or implementation of the above-listed components of system 900 for wireless analyte monitoring and / or diabetes management. The first example does not involve medication (e.g., insulin) delivery by partner device 915 (e.g., by medication delivery device 915a). Under this example, in an embodiment, system 900 includes analyte sensor system 308, one or more display devices 910, 910′ (e.g., cell phone 910a and / or analyte display 910b) authorized to send command / control signals to analyte sensor system 308, and one or more display devices 910, 910′ (e.g., wearable device 910c and / or key fob 910f) configured to be in a display-only state. In an embodiment, this example involves display devices 910a and 910b (e.g., referring to FIG. 1 , smartphone 120, etc. and analyte display device 110) operating in a command / control state, and one or more display devices 910, 910′ operating in a display-only state (e.g., key fob 910f and smart mirror 910d or wearable device 910c, etc.).

[0314] The second example differs from the first example in that it involves medication (e.g., insulin) delivery by at least one of the partner devices 915 (e.g., medication delivery device 915a). The medication delivery by the medication delivery device 915 in this example may or may not be automated (e.g., an automatic insulin pump or a non-automatic insulin pen). In this second example, in which the medication delivery device 915a that delivers the medication is part of the system 900, interoperability issues may be introduced regarding which device (e.g., medication delivery device 915, analyte sensor system 308, and / or display device 910, 910′) may control / manage the generation of analyte data, including, for example, calculation of CGM values, etc.

[0315] Regarding this second example, to flexibly and adaptively support potentially changing, a priori unknown system requirements 650 (see, e.g., FIG. 5B ) of various partner devices 915 from an interoperability perspective, where such partner devices 915 may be provided by different manufacturers / developers distinct from the manufacturers / developers of other components of system 900 (e.g., display devices 910, 910′ and / or analyte sensor system 308, etc.), in some cases drug delivery device 915a (or a similar partner device 915) must be able to control the data exchange between analyte sensor system 308 and display device 910, 910′ via links 906a-g. Such control may be provided, for example, by a user of display device 910, 910a (e.g., a user of phone 910a who is granted control over drug delivery device 915 via link 916 using mobile phone 910a).

[0316] In embodiments, aspects of the communication session and / or sensor session should also be controlled (e.g., the partner device 915, the analyte sensor system 308, and / or the display device 910, 910′ should be able to limit command / control signaling in some cases, including when such signaling relates to analyte data). For example, if the drug delivery device 915a is used for insulin delivery, transmission of command signaling to the analyte sensor system 308 may be limited to only certain devices in the system 900. A particular partner device 915 may, in some cases, be generally less robust, e.g., in terms of maintaining accuracy in relatively high interference environments. In such cases, if the display device 910, 910′ is limited from sending control / command signaling, e.g., related to starting, stopping, and calibrating a sensor session, due to, e.g., the system requirements 650 of the drug delivery device 915a, the probability of the drug delivery device 915a inaccurately receiving analyte data from the analyte sensor system 308 may be reduced. For example, such signaling may cause the analyte sensor system 308 to operate in an incompatible, suboptimal, or undesirable manner with respect to drug delivery 915a, as may be reflected, for example, by its system requirements 650. In embodiments, it may be beneficial to delegate authority to send control / command signals only to certain devices within the system 900 based on device type and / or based on the operational mode of the system 900. In embodiments, it may be beneficial to flexibly add or remove devices (e.g., partner devices 915 and / or display devices 910, 910′) to or from the system 900, whether in the PAN 902 or the WAN 904, to manage access of such devices to the analyte sensor system 308 and / or manage how alerts propagate across various such and other devices within the system 900.

[0317] In embodiments, it may also be beneficial for the system 900 (e.g., including the medication delivery device 915a) to provide a means of controlling alert settings for safety and / or robustness purposes. In embodiments, it may be beneficial to adaptively change aspects of the system 900 if a particular link becomes unavailable (e.g., link 906d between the analyte sensor system 308 and the medication delivery device 915a, link 922 between the mobile phone 910a and the cell network 920c, etc.), whether literally or due to system constraints such as power and / or in response to other network conditions / configurations of the PAN 902 and / or WAN 904 described herein. Additionally, in some cases, it may be beneficial to authenticate partner devices 915 attempting to establish a connection with the analyte sensor system 308 and / or prevent unauthorized partner devices 915 from accessing the analyte sensor system 308.

[0318] Accordingly, embodiments of the present disclosure provide a more flexible / adaptable system of analyte sensor system 308, display device 910, 910′ and / or partner device 915, and methods of use thereof, where such flexibility / adaptability may include setting or modifying configuration parameters 520 of analyte sensor system 308, warnings / alarms that may propagate through system 900, control / command functions of display device 910, 910′ and / or partner device 915, connection models used between devices in system 900, etc. In embodiments, flexibility / adaptability is facilitated at least in part through the use of a diabetes management partner interface (DMPI) 750, which may be implemented using analyte sensor system 308. As will be described in further detail, in embodiments, various devices in the system 900, including, for example, the partner device 915, can utilize the DMPI 750 to access / modify the configuration parameters 520 of the analyte sensor system 308 and / or (re)configure aspects thereof and / or aspects of the display device 910, 910′ for operation in accordance with, for example, the system requirements 650 of the partner device 915 (e.g., the drug delivery device 915a). For example, the system requirements 650 may be driven based on safety and / or regulatory requirements applicable to the drug delivery device 915a, user experience configurations / settings / constraints, power consumption specifications / constraints, etc. The system requirements 650 may be used to determine the format of data packages to be transmitted to the partner device 915 and / or the display device 910, 910′, as well as the protocols used to transmit such data packages based on the respective preferences / specifications / etc. of the partner device 915 and / or the display device 910, 910′.

[0319] 9A , an exemplary embodiment involving various partner devices 915 in system 900 will now be described. In the exemplary implementation described below, system 900 may involve three partner devices 915: a first insulin pump 915b, a second insulin pump 915c, and an insulin pen 915d. Generally, these three partner devices 915 may each have different functionality and performance characteristics that may be reflected in their respective specific system requirements 650 (see FIG. 5B ), and each of the three partner devices 915 may use the DMPI 750 of the analyte sensor system 308 (see FIG. 10A , for example) to modify the configuration parameters 520 of the analyte sensor system 308 according to their respective system requirements 650. In this manner, the analyte sensor 308 can be adapted for better interoperability with either the first or second insulin pump and insulin pen at any time any partner device 915 is connected within the analyte sensor system 308 and / or system 900. It will be understood upon review of this disclosure that this description of the first insulin pump 915b, the second insulin pump 915c, and the insulin pen 915d is equally applicable to any example of a partner device 915, including medication delivery device 915a and similar devices.

[0320] For illustrative purposes, further details are provided regarding the respective characteristics of the first and second insulin pumps 915b, 915c and insulin pen 915d in these exemplary implementations. By way of example, the first insulin pump 915b may have a relatively robust algorithm for medication administration, may have a larger (or higher-capacity) battery or power source, and may require blood glucose calibration to be performed every 12 hours. The relatively robust algorithm of the first insulin pump 915b may inherently mean that it may be relatively less susceptible to interference from other devices that may attempt to connect to the analyte sensor system 308, such as the display device 910, 910′, including where such interference may involve interference during connection establishment or interference incidental to the transmission of command signaling to the analyte sensor system 308. For example, the algorithm of the first insulin pump 915b may be better able to operate over a wider range of configuration parameters 520 and may be better able to handle calibration and start / stop events initiated by other devices. The 12-hour blood glucose calibration requirement may reflect the accuracy constraints of the first insulin pump (and may be reflected in the system requirements 650 of the first insulin pump 915b, for example).

[0321] As a further example, the second insulin pump 915c may have a less robust algorithm used for administering medication, may be less constrained with respect to blood glucose accuracy calibration (e.g., it may be possible to use a factory-calibrated accuracy level), and may support remote services provided by the server 920b (e.g., via a connection / link to the server 920b via a cell network 920c (link not shown in FIG. 9A ), indirectly via a router 920a (link also not shown), or indirectly, for example, via a mobile phone 910a). The less robust algorithm of the second insulin pump 915c may inherently mean that the second insulin pump 915c is designed to operate well in high interference environments where other devices in the system 900 may be competing to establish a connection with the analyte sensor system 308 and / or sending command / control signals to other devices.

[0322] Continuing with the illustrative example, insulin pen 915d may have hard / soft keys for receiving user input or may include a simple user interface, both of which may be represented, for example, by user interface 635 (see FIG. 5B). Insulin pen 915d may be further adapted to query and share data with analyte sensor system 308, for example, to read analyte data from analyte sensor system 308 and share insulin-related information (e.g., related to dosage) with analyte sensor system 308.

[0323] Given the above exemplary information regarding the first insulin pump 915b and the second insulin pump 915c and the insulin pen 915d, exemplary scenarios of how the DMPI 750 may be used to flexibly adapt the system 900 are now provided. The first exemplary scenario may involve using the first insulin pump 915b with the analyte sensor 308. Once the first insulin pump 915b and the analyte sensor system 308 are configured for use (e.g., applied to a user, powered on, etc.), the user's permission may be requested for the first insulin pump 915b to control the analyte sensor system 308 and initiate administration of medication to the user. For example, such a request may be provided to the user via the user interface 435 of the mobile phone 910a (see FIG. 4), which may be connected to the analyte sensor system 308 and / or the first insulin pump, via the user interface 635 of the first insulin pump 915b (see FIG. 5B), and / or via the user interface of the analyte sensor system 308. If the user authorizes the request, the first insulin pump 915b may use the DMPI 750 to access the configuration parameters 520 of the analyte sensor system 308 to set and / or change the configuration parameters 520 in accordance with the system requirements 650 of the first insulin pump 915b (see, for example, FIG. 10A).

[0324] In this example, in that the first insulin pump 915b accesses the configuration parameters 520 via the DMPI 750, the developer of the first insulin pump 915b may have already integrated and tested the pump 915b with the analyte sensor system 308 before the product is sold or provided to a user. In this manner, the first insulin pump 915b may include instructions, code, or other files in the storage device 615 that enable the first insulin pump 915b to properly operate the DMPI 750 and the configuration parameters 520. In an embodiment, such instructions may be obtained by the first insulin pump 915b by downloading and / or installing a software design kit associated with the analyte sensor system 308. For example, the insulin pump 915b may obtain such instructions or other information from the server 920b and / or the WAN 904 or elements thereof.

[0325] As an example, the first insulin pump 915b can use the DMPI 750 to modify one or more wireless connectivity parameters of the configuration parameters 520. The wireless connectivity parameters can include settings related to a database that contains / stores information related to device accessibility (e.g., a whitelist) maintained by the analyte sensor system 308, and the first insulin pump 915b can modify such whitelist settings, for example, so that the first insulin pump 915b does not have to age off the whitelist until the battery level of the first insulin pump 915b falls below a certain threshold (e.g., 5%). As mentioned above, the first insulin pump 915b may set its wireless connectivity parameters in this manner because the first insulin pen 915b has a larger battery (e.g., higher battery capacity), and if for some reason the first insulin pump 915b becomes disconnected from the analyte sensor system 308 (e.g., by going out of range), it may be beneficial for the first insulin pump 915b to attempt to re-establish a connection with the analyte sensor system 308 as soon as an opportunity arises.

[0326] The first insulin pump 915b may use the DMPI 750 to set or modify additional wireless connectivity parameters, such as a timeout setting for transmission of advertisement messages, so that the analyte sensor system 308 advertises for a total of one second before stopping transmission of advertisement messages. That is, in this example, the advertisement period 614 (see FIG. 6) may be set to one second. The first insulin pump 915b may set the wireless connectivity parameters in this manner because the first insulin pump 915b may have a relatively accurate scanning algorithm (e.g., as may have been determined by the developer of the first insulin pump 915b or by other means) such that the first insulin pump 915b may be able to reliably establish a connection with the analyte sensor system 308 if appropriate without advertising for a longer period of time (e.g., once every advertisement window interval 612, which in some cases may be five minutes). Reducing the advertisement window interval 612 may conserve battery power.

[0327] Additionally, the first insulin pump 915b can use the DMPI 750 to modify one or more access control parameters of the configuration parameters 520. The access control parameters can include, for example, the number of display devices 910, 910′ to which the analyte sensor system 308 can maintain a connection and / or the level of access or control that such display devices 910, 910′ can have over the analyte sensor system 308. By way of example, the first insulin pump 915b may set either or both of these access control parameters so that no restrictions are imposed. As discussed above, the first insulin pump 915b may set the access control parameters in this manner because the first insulin pump 915b has a relatively robust algorithm for insulin administration, and thus does not need to prevent other devices from sending calibrations, etc. (e.g., because the algorithm of the first insulin pump 915b may be able to process such external events and adjust the external events accordingly).

[0328] Additionally, the first insulin pump 915b in this example may use DMPI 750 to modify one or more analyte data parameters of configuration parameters 520. The analyte data parameters may include a calibration period for analyte sensor system 308. For example, the first insulin pump 915b may set the calibration period to 12 hours in accordance with the above-described system requirements 650 for the first insulin pump 915b.

[0329] A second illustrative scenario may involve using a second insulin pump 915c with the analyte sensor 308. Similar to the example above involving the first insulin pump 915b, after setup and authorization, the second insulin pump 915c may use the DMPI 750 to access the configuration parameters 520 of the analyte sensor system 308 to set and / or modify the configuration parameters 520 in accordance with the second insulin pump's 915c system requirements 650 (see, e.g., FIG. 10A ). Similar to the previous example, in that the second insulin pump 915c accesses the configuration parameters 520 via the DMPI 750, the developer of the second insulin pump 915c may have already integrated and tested the pump with the analyte sensor system 308 before the product is sold or provided to users. In this manner, the second insulin pump 915c may be adapted to properly operate the DMPI 750 and the configuration parameters 520. In an embodiment, the second insulin pump may also reconfigure the DMPI 750 before accessing the configuration parameters 520.

[0330] Regarding the second exemplary scenario, several situations are envisioned here. In the first situation, when deciding to use an insulin delivery device, the user first selects the second insulin pump 915c instead of the first insulin pump 915b or insulin pen 915d. In the second situation, the user may have already been using the first insulin pump 915b or insulin pen 915d for a while, but may then switch to the second insulin pump 915c. That is, the first insulin pump 915b and the second insulin pump 915c and / or insulin pen 915d are not necessarily used simultaneously, but this example illustrates a situation in which the first insulin pump 915b and the second insulin pump 915c and / or insulin pen 915d are used consecutively (e.g., the user decides to use a different pump product, or the first pump product breaks, etc.). It should also be understood that the partner device 915 may be used consecutively.

[0331] As an example, the second insulin pump 915c may use the DMPI 750 to set or modify the wireless connectivity parameters of the analyte sensor system 308, including, for example, a timeout setting for transmission of advertisement messages, such that the analyte sensor system 308 may advertise for a total of five seconds before stopping transmitting advertisement messages. The second insulin pump 915c may set the wireless connectivity parameters in this manner because the second insulin pump 915c may have a relatively inaccurate scanning algorithm (e.g., as may have been determined by a developer of the second insulin pump 915c or by other means) such that the second insulin pump 915c may not be able to reliably establish a connection with the analyte sensor system 308 if appropriate without advertising for a relatively longer period of time (e.g., once every advertisement window interval 612, which in some cases may be five minutes).

[0332] Additionally, the second insulin pump 915c in this example may modify additional wireless connectivity parameters using the DMPI 750. Such wireless connectivity parameters may be associated with the use of a remote (e.g., cloud-based) service (e.g., service 805, with reference to FIG. 8 ), which may be provided, for example, by the server 920b. By way of example, the second insulin pump 915c may set wireless connectivity parameters to enable the use of such a remote service (e.g., a cloud-based support module) and to configure the analyte sensor system 308 to transmit diabetes management feedback received in association with such a remote service to a display device 910, 910′ (e.g., in some cases the display device 910, 910′ may be in a display-only state / mode) that may be within range of and / or connectable to the analyte sensor system 308. The second insulin pump 915c may set these wireless connectivity parameters in this manner because the second insulin pump 915c may be authorized to propagate such diabetes management feedback to other display devices 910, 910′, etc. Additionally, the second insulin pump 915c may configure its wireless connectivity such that if the remote service becomes unavailable (e.g., due to loss of links 914, 922, 924 or 926, for example, to the server 920b), the diabetes management feedback functionality may be disabled, and may configure associated notifications to display devices 910, 910′, etc., within range of and / or that may be connected to the analyte sensor system 308.

[0333] Additionally, the second insulin pump 915c may use the DMPI 750 to modify one or more access control parameters of the configuration parameters 520, including, for example, by setting the number of display devices 910, 910' that the analyte sensor system 308 can connect to the three devices and by setting the level of access or control of such display devices 910, 910' to the analyte sensor system 308, so that up to three display devices 910, 910' operate in a display-only state or mode, where such display devices 910, 910' may be capable of displaying analyte and / or insulin delivery data, related notifications / alarms, and other information, but are not capable of sending control / command signaling to the analyte sensor 308. As mentioned above, the second insulin pump 915c may set the access control parameters in this manner because the second insulin pump 915c may have a relatively less robust algorithm for insulin administration, and therefore does not need to prevent other devices from sending calibrations, etc. (e.g., because the algorithm of the second insulin pump 915c may not be able to process such external events and adjust the external events accordingly).

[0334] Moreover, with regard to the analyte data parameters that may be included in the configuration parameters 520, the second insulin pump 915c may not make any changes to the factory calibration parameters (e.g., including the factory calibration period) that may be default for the analyte sensor system 308 when provided commercially or by its manufacturer. This may be because, as described above, the second insulin pump 915c can use the factory calibration accuracy level. In this situation, the analyte sensor system 308 may not need to generate a calibration prompt and may simply follow the default calibration schedule.

[0335] A third illustrative scenario may involve using an insulin pen 915d with the analyte sensor system 308. Similar to the example above involving the first insulin pump 915b and the second insulin pump 915c, after setting up and authorizing the insulin pen 915d for use, including multiple daily injections of insulin, which may be administered manually, the insulin pen 915d may use the DMPI 750 to access the configuration parameters 520 of the analyte sensor system 308 to set and / or modify the configuration parameters 520 in accordance with the insulin pen 915d's system requirements 650 (see, e.g., FIG. 10A ). Similar to the previous example, in that the insulin pen 915d accesses the configuration parameters 520 via the DMPI 750, the developer of the insulin pen 915d may have already integrated and tested the pump with the analyte sensor system 308 before the product is sold or provided to users. In this manner, the insulin pen 915d may be adapted to properly operate the DMPI 750 and the configuration parameters 520.

[0336] As an example, insulin pen 915d may use DMPI 750 to change one or more access control parameters in configuration parameters 520, including, for example, selecting to establish a direct connection with analyte sensor system 308 as opposed to establishing a connection with analyte sensor system 308 indirectly, for example, via mobile phone 910a. Despite this selection, mobile phone 910a may still establish a connection with and exchange information with analyte sensor system 308 and / or insulin pen 915d, depending on how configuration parameters 520 may otherwise be set.

[0337] The insulin pen 915d may also use the DMPI 750 to change the wireless connectivity parameters of the analyte sensor system 308, including those related to transmission of advertisement messages, such that the analyte sensor system 308 may advertise according to the default settings for the display device 910, 910′, but for the insulin pen 915d, the analyte sensor system 308 may advertise using an extended advertisement period 614 and / or a shortened advertisement window interval 612 (see FIG. 6 ). For devices such as the insulin pen 615d, the insulin pen 615d may set its wireless connectivity parameters in this manner because a user may require a more responsive system that has access to, for example, up-to-date glucose data that is readily available to the user.

[0338] Additionally, the insulin pen 615d may use the DMPI 750 to access the analyte data parameters of the configuration parameters 520 to enable use of a bolus calculator that may be implemented by, for example, the analyte sensor system 308. For example, the DMPI 750 may provide the insulin pen 915d with access to bolus calculation parameters that may be maintained by the analyte sensor system 308 so that the analyte sensor system 308 can modify the bolus calculation parameters. In embodiments of the present disclosure, the analyte sensor system 308 may use the bolus calculation parameters to provide bolus-related recommendations to the user, the recommendations being based on calculations performed by the analyte sensor system 308 using the bolus calculation parameters (e.g., and the bolus calculator 308 of the analyte sensor system).

[0339] The insulin pen 915d in this example may also use DMPI 750 to modify one or more additional analyte data parameters in configuration parameters 520. For example, the insulin pen 915d may, in some cases, set the calibration period to 12 hours for reasons similar to those described above with respect to the system requirements 650 of the first insulin pump 915b.

[0340] With further regard to an exemplary scenario involving an insulin pen 915d, in some cases, a user may desire and / or need to administer insulin and may select a bolus value for the insulin pen 915d accordingly (e.g., using the user interface 635, with reference to FIG. 6 ). A connection may then be established between the insulin pen 915d and the analyte sensor system 308 such that the insulin pen 915d may transmit the user's selected bolus value to the analyte sensor system 308. If the user's blood glucose level is lower than desired / normal and / or the user has already loaded a significant amount of insulin, the analyte sensor system 308 may use the bolus calculator described above to make bolus-related recommendations to the user and / or determine safety. The analyte sensor system 308 may, in this situation, send a notification or warning to the user regarding the amount of insulin selected by the user (e.g., that the selected bolus value is too high). In such cases, the analyte sensor system 308 may attempt to prevent the user from injecting the selected bolus value. For example, there may be a mechanical prevention feature on the insulin pen 915d that prevents the user from injecting a bolus that exceeds the bolus value calculated by the analyte sensor system 308. Such a mechanical prevention feature may be implemented, for example, by disabling (retracting) the drug delivery mechanism 640 (e.g., needle) and / or preventing an excessively large bolus from moving into the insulin pen's injection reservoir. Signaling from the analyte sensor system 308 may, for example, trigger the mechanical prevention feature.

[0341] As described below, additional configuration parameters 520 and / or system requirements 650 may be present in embodiments of system 900, and those skilled in the art will, upon reviewing this disclosure, understand additional aspects of using configuration parameters 520 and / or system requirements 650 in the context of the above example scenarios, as well as in other contexts explicitly or implicitly described or suggested herein. It should be understood that the above example scenarios and features thereof are not necessarily required in all embodiments of the present disclosure, and that features may be disclosed with respect to embodiments for illustrative purposes only.

[0342] Given the general context of the above example scenario, additional details regarding configuration parameters 520 and system requirements 650 will be described with reference to FIG. 10A . For example, as shown in FIG. 10A , within system 1000, partner device 315 may include system requirements 650 associated with partner device 315 that must be met to support functionality according to predetermined expectations, design constraints, system specifications, and / or the like. To support system requirements 650, partner device 315 may access configuration parameters 520 (e.g., of analyte sensor system 308) using DMPI 750 of analyte sensor system 308. Configuration parameters 520 can serve as flexible settings that can be adapted, changed, programmed, set, and / or modified by partner device 315 using DMPI 750 such that communication between / among analyte sensor system 308, partner device 315, and / or display device 310 enables system requirements 650 to be met.

[0343] By way of example, the configuration parameters 520 may include wireless connectivity parameters, access control parameters, power management parameters, and / or analyte data parameters. The wireless connectivity parameters may generally relate to wireless connectivity and communications within the system 900 (such as with reference to FIG. 9A and / or system 800 with reference to FIG. 8), and processing of wireless communications, and connectivity with the analyte sensor system 308, including with and / or by one or more of the display device 310 and partner device 315 and other connections described herein (e.g., between the display device and partner device 315).

[0344] The wireless connectivity parameters may relate to aspects of a whitelist that may be maintained by the analyte sensor system 308. For example, the wireless connectivity parameters may relate to aging-off settings by a particular device or group of devices. For example, if the partner device 315 is an empty insulin pump, a default aging-off time may be used as a backup mechanism to stop use of the insulin pump if the user is unaware that the pump is empty, but the aging-off in this scenario may be subject to override by the user if the user approves not to age-off the pump. In an example implementation, the pump may have a known lifespan, and the aging-off time may be set to correspond to this. For example, the known lifespan may be battery-powered, and / or the pump may require replacement / repair after a known time, which may be reflected in the system requirements 650, and the pump may set its aging-off time accordingly by modifying the configuration parameters 520 using the DMPI 750. For example, this aging-off can be adjusted on the fly if a problem occurs sooner than expected or if an expected problem is eliminated in time due to intervening circumstances (e.g., due to efficient power management or lower power consumption than expected). Additionally, the partner device 315 may be able to modify the whitelist settings using the DMPI 750 to forcefully remove certain devices from the whitelist so that battery budget can be conserved for the analyte sensor system 308 and / or the partner device 315.

[0345] In embodiments, the wireless connectivity parameters may relate to a hierarchy / prioritization of connection order among connectable devices (e.g.,...

Claims

1. 1. A method of configuring an analyte sensor system for wireless communication with a plurality of partner devices using a diabetes management partner interface, comprising: receiving, by the analyte sensor system via the diabetes management partner interface, authorization to provide one of the partner devices with access to a configuration parameter set, wherein the configuration parameter set is stored in a memory of the analyte sensor system; and in response to input received from the one partner device via the diabetes management partner interface, the analyte sensor system sets or causes modification of the configuration parameter set according to system requirements of the one partner device.

2. The method of claim 1 , wherein the one partner device is an automatic insulin delivery device or a manual insulin delivery device.

3. The method of claim 1 , wherein the configuration parameter set includes one or more of a wireless connectivity parameter set, an access control parameter set, and an analyte data parameter set.

4. The system requirements are: the battery capacity of said one partner device; an accuracy requirement of said one partner device; a communication protocol used by said one partner device; regulatory requirements applicable to said one partner device; and an expected uptime of the one partner device.

5. the wireless connectivity parameter set includes a condition under which the one partner device will be removed from a whitelist maintained for the analyte sensor system; 4. The method of claim 3, wherein the analyte sensor system setting or causing the modification of the configuration parameter set in response to the system requirements of the one partner device includes the analyte sensor system setting the condition such that when a battery level of the one partner delivery device meets a threshold, the one partner device is removed from the whitelist.

6. the wireless connectivity parameter set includes an advertisement structure; 4. The method of claim 3, wherein the analyte sensor system setting or causing the modification of the configuration parameter set in response to the system requirements of the one partner device comprises the analyte sensor system setting or modifying the advertisement structure using the diabetes management partner interface.

7. The access control parameter set is the number of display devices to which the analyte sensor system can be connected; and 4. The method of claim 3, comprising one or more of: a level of access or control the analyte sensor system may provide to one or more of the display devices.

8. the analyte data parameter set includes a calibration period for the analyte sensor system; 4. The method of claim 3, wherein the analyte sensor system setting or causing the modification of the configuration parameter set in response to the system requirements of the one partner device comprises the analyte sensor system setting or modifying the calibration period using the diabetes management partner interface.

9. the analyte data parameter set includes a factory calibration code; the analyte sensor system receiving, using the diabetes management partner interface, an indication from the one partner device using the factory calibration code in accordance with the system requirements of the one partner device; 9. The method of claim 8, wherein the analyte sensor system setting or causing the modification of the configuration parameter set in response to the system requirements of the one partner device comprises the analyte sensor system setting or modifying the calibration period to zero or none using the diabetes management partner interface.

10. The wireless connectivity parameter set includes settings on a remote server, and the analyte sensor system configures or causes the modification of the configuration parameter set according to the system requirements of the one partner device by connecting the analyte sensor to a diabetes management partner interface; using a service provided via the remote server; transmitting diabetes management feedback to one or more display devices coupled to the analyte sensor system in response to services provided via the remote server; 4. The method of claim 3, further comprising configuring: if the service provided via the remote server becomes unavailable, to disable use of the service and send an associated notification to a display device connected to the analyte sensor system.

11. the analyte date parameter set includes bolus calculation parameters; 11. The method of claim 10, wherein the analyte sensor system setting or causing the modification of the configuration parameter set in response to the system requirements of the one partner device comprises the analyte sensor system providing the one partner device with access to the bolus calculation parameters using the diabetes management partner interface.

12. The method of claim 11 , further comprising the analyte sensor system providing a bolus recommendation based on a calculation performed using the bolus calculation parameters.

13. 1. An analyte sensor system for wireless communication with a plurality of partner devices, the analyte sensor system being configurable through use of a diabetes management partner interface, the analyte sensor system comprising: an analyte sensor used to generate the analyte information; a transceiver adapted to transmit and receive radio signals; a memory for storing a set of configuration parameters used by the transceiver to transmit and receive the wireless signals; operatively coupled to the transceiver and the memory, to the analyte sensor system; receiving, via the diabetes management partner interface, authorization to provide one of the partner devices with access to a configuration parameter set; and circuitry adapted to, in response to input received from the one partner device via the diabetes management partner interface, set or cause modification of the configuration parameter set according to system requirements of the partner device.

14. 14. The analyte sensor system of claim 13, wherein the one partner device is an automatic insulin delivery device or a manual insulin delivery device.

15. The analyte sensor system of claim 13 , wherein the configuration parameter set comprises one or more of a wireless connectivity parameter set, an access control parameter set, and an analyte data parameter set.

16. The system requirements are: the battery capacity of said one partner device; an accuracy requirement of said one partner device; a communication protocol used by said one partner device; regulatory requirements applicable to said one partner device; 14. The analyte sensor system of claim 13, wherein the sensor is associated with one of: an expected uptime of the one partner device;

17. the wireless connectivity parameter set includes a condition under which the one partner device will be removed from a whitelist maintained for the analyte sensor system; 16. The analyte sensor system of claim 15, wherein the circuitry is further adapted to cause the analyte sensor system to set the condition according to the system requirements of the one partner device such that when a battery level of the one partner delivery device meets a threshold, the one partner device is removed from the whitelist.

18. the wireless connectivity parameter set includes an advertisement structure; 16. The analyte sensor system of claim 15, wherein the circuitry is further adapted to cause the analyte sensor system to set or modify the advertisement structure using the diabetes management partner interface.

19. The access control parameter set is the number of display devices to which the analyte sensor system can be connected; and 16. The analyte sensor system of claim 15, comprising one or more of: a level of access or control the analyte sensor system may provide to one or more of the display devices.

20. the analyte data parameter set includes a calibration period for the analyte sensor system; 16. The analyte sensor system of claim 15, wherein the circuitry is further adapted to cause the analyte sensor system to set or modify the calibration period using the diabetes management partner interface.

21. the analyte data parameter set includes a factory calibration code; The circuitry is connected to the analyte sensor system. receiving an indication using the factory calibration code from the one partner device according to the system requirements of the one partner device using the diabetes management partner interface; 21. The analyte sensor system of claim 20, further adapted to cause the diabetes management partner interface to be used to set or modify the calibration period to zero or none.

22. the wireless connectivity parameter set includes a remote server configuration; the circuitry connecting the analyte sensor to the analyte sensor system using the diabetes management partner interface; using a service provided via the remote server; transmitting diabetes management feedback to one or more display devices coupled to the analyte sensor system in response to services provided via the remote server; 16. The analyte sensor system of claim 15, further adapted to: disable use of the service if the service provided via the remote server becomes unavailable; and configure to send an associated notification to a display device connected to the analyte sensor system.

23. the analyte date parameter set includes bolus calculation parameters; 23. The analyte sensor system of claim 22, wherein the circuitry is further adapted to cause the analyte sensor system to configure, using the diabetes management partner interface, the analyte sensor system to provide the one partner device with access to the bolus calculation parameters according to the system requirements of the partner device.

24. 24. The analyte sensor system of claim 23, wherein the circuitry is further adapted to cause the analyte sensor to provide a bolus recommendation based on a calculation performed using the bolus calculation parameters.

25. 1. A system comprising: one or more partner devices adapted to deliver insulin to a user; an analyte sensor system adapted to generate analyte information, the analyte sensor system including a set of configuration parameters used to transmit and receive wireless signals, the configuration parameters being configurable through use of a diabetes management partner interface; and a display device connectable to the analyte sensor system and adapted to display analyte information and for the analyte sensor system to provide authorization to provide access to the configuration parameter set to one of the partner devices via the diabetes management partner interface; The system, wherein the one partner device is adapted to use the diabetes management partner interface to set or cause modifications of the set of configuration parameters according to system requirements of the partner device.

26. 26. The analyte sensor system of claim 25, wherein the one partner device is an automatic insulin delivery device or a manual insulin delivery device.

27. 26. The system of claim 25, wherein the configuration parameter set includes one or more of a wireless connectivity parameter set, an access control parameter set, and an analyte data parameter set.

28. The system requirements are: the battery capacity of said one partner device; the accuracy requirements of said one partner device; the communication protocol used by said one partner device; regulatory requirements applicable to said one partner device; and 26. The system of claim 25, wherein the device is associated with one of: an expected uptime of the one partner device;

29. the wireless connectivity parameter set includes a condition under which the one partner device will be removed from a whitelist maintained for the analyte sensor system; 28. The system of claim 27, wherein the one partner device is further adapted to set or modify the condition using the diabetes management partner interface according to the system requirements of the one partner device, such that the one partner device is removed from the whitelist when a battery level of the one partner delivery device meets a threshold.

30. the wireless connection parameter set includes an advertisement structure; 30. The system of claim 27, wherein the one partner device is further adapted to set or modify an advertisement structure using the diabetes management partner interface.

31. The access control parameter set is the number of display devices to which the analyte sensor system can be connected; and 30. The sensor system of claim 27, comprising one or more of: a level of access or control the analyte sensor system may provide to one or more of the display devices.

32. the analyte data parameter set includes a calibration period for the analyte sensor system; 28. The system of claim 27, wherein the one partner device is further adapted to set or modify the calibration period using the diabetes management partner interface.

33. the analyte data parameter set includes a factory calibration code; The one partner device uses the diabetes management partner interface to: providing an indication using the factory calibration code to the analyte sensor system according to the system requirements of the one partner device; and 33. The system of claim 32, further adapted to set or modify the calibration period to zero or none.

34. the wireless connection parameter set includes a remote server setting; the one partner device communicating the analyte sensor using the diabetes management partner interface; using a service provided via the remote server; transmitting diabetes management feedback to a device connectable to the analyte sensor system in response to services provided via the remote server; 28. The system of claim 27, further adapted to configure: if a service provided via the remote server becomes unavailable, disable use of the service and send an associated notification to a display device connectable to the analyte sensor system.

35. the analyte date parameter set includes bolus calculation parameters; 35. The system of claim 34, wherein the one partner device is further adapted to configure the analyte sensor system to provide the one partner device with access to the bolus calculation parameters according to the system requirements of the partner device using the diabetes management partner interface.

36. 36. The system of claim 35, wherein the one partner device is further adapted to use the diabetes management partner interface to receive bolus recommendations from the analyte sensor system based on calculations performed using the bolus calculation parameters.

37. 1. A method for configuring wireless communication between an analyte sensor system and one or more display devices and partner devices using a diabetes management partner interface, comprising: an analyte sensor system enabling a first wireless signal communication path, the first wireless communication signal path being between the analyte sensor system and the display device, the analyte sensor system providing the display device with a first degree of access or control over the analyte sensor system for the first wireless communication path; and wherein the analyte sensor system enables a second wireless signal communication path, the second wireless signal communication path being between the analyte sensor system and the partner device, and wherein the enabling of the second wireless signal communication path by the analyte sensor system includes causing a modification of the first degree of access or control to implement a second degree of access or control in accordance with system requirements of the partner device, the modification being caused in response to input received from the partner device via the diabetes management partner interface.

38. 38. The method of claim 37, wherein causing the modification of the first degree of access or control using the diabetes management partner interface comprises setting or changing a configuration parameter set implemented by the analyte sensor system according to the system requirements of the partner device.

39. 39. The method of claim 38, wherein the set of configuration parameters includes one or more of access control parameters of the display device or the partner device, accuracy or calibration parameters of the analyte sensor system, and wireless communication parameters for communications exchanged between the analyte sensor system and one or more of the display device and the partner device.

40. 40. The method of claim 39, wherein setting or modifying the configuration parameter set using the diabetes management partner interface comprises granting the partner device permission to configure accuracy or calibration parameters of the analyte sensor system via the diabetes management partner interface.

41. 40. The method of claim 39, wherein setting or changing the set of configuration parameters using the diabetes management partner interface comprises revoking permission from the display device to configure the accuracy or calibration parameters of the analyte sensor.

42. the access control parameters include a whitelist of devices that can connect to the analyte sensor system; 40. The method of claim 39, wherein setting or changing the configuration parameter set using the diabetes management partner interface includes setting or modifying an amount of time the partner device will remain on the whitelist before being removed from the whitelist.

43. 1. An analyte sensor system for wireless communication with one or more of a display device and a partner device, the analyte sensor system being configurable through use of a diabetes management partner interface, the analyte sensor system comprising: a memory for storing a set of configuration parameters used by a transceiver for transmitting and receiving wireless signals; an analyte sensor system operably coupled to the transceiver and the memory; enabling a first wireless signal communication path, the first wireless communication signal path being between the analyte sensor system and the display device, the first wireless communication path being such that the analyte sensor system provides the display device with a first degree of access or control over the analyte sensor system; enabling a second wireless signal communication path, the second wireless signal communication path being between the analyte sensor system and the partner device, the second wireless signal communication path being enabled by a change to the first degree of access or control made by the analyte sensor system, the change to the first degree of access or control being made in response to input received from the partner device via the diabetes management partner interface, and the change to the first degree of access or control being made to implement a second degree of access or control pursuant to system requirements of the partner device.

44. 44. The analyte sensor system of claim 43, wherein the circuitry is further adapted to cause the analyte sensor system to set or change a set of configuration parameters implemented by the analyte sensor system using the diabetes management partner interface according to the system requirements of the partner device to modify the first degree of access or control.

45. 45. The analyte sensor system of claim 44, wherein the configuration parameter set includes one or more of access control parameters of the display device or the partner device, accuracy or calibration parameters of the analyte sensor system, and wireless communication parameters for communications exchanged between the analyte sensor system and one or more of the display device and the partner device.

46. 46. ​​The analyte sensor system of claim 45, wherein the circuitry is further adapted to cause the analyte sensor system to grant permission to the partner device to configure the accuracy or calibration parameters of the analyte sensor system via the diabetes management partner interface.

47. 46. ​​The analyte sensor system of claim 45, wherein the circuitry is further adapted to cause the analyte sensor system to revoke permission from the display device to configure the accuracy or calibration parameters of the analyte sensor.

48. access control parameters include a whitelist of devices that can connect to the analyte sensor system; 46. ​​The analyte sensor system of claim 45, wherein the circuitry is further adapted to set or modify an amount of time the partner device will remain on the whitelist before being removed from the whitelist.

49. 1. A method for controlling wireless communication between an analyte sensor system and one or more remote devices connectable to the analyte sensor system using a diabetes management partner interface of the analyte sensor system, the one or more remote devices including a display device and a partner device, the method comprising: the analyte sensor system determining whether a connection request received from one of the remote devices originated from a partner class within the one or more remote devices, wherein the remote devices within the partner class are adapted to provide medication, and the partner class includes the partner device; and if the connection request originates from the partner class, the diabetes management partner interface enabling selection of an operating mode corresponding to the partner class, the operating mode using a configuration parameter set of the partner class to support system requirements of the partner device.

50. 50. The method of claim 49, further comprising exchanging the wireless communications with at least one of the remote devices using the operational mode corresponding to the partner class.

51. 51. The method of claim 50, wherein exchanging the wireless communications using the operational mode corresponding to the partner class includes transmitting a mode indicator available by the at least one of the remote devices to determine the operational mode being used.

52. 52. The method of claim 51 , wherein the configuration parameter set used to support the system requirements of the partner device includes one or more of: access control parameters of the display device or the partner device, accuracy or calibration parameters of the analyte sensor system, and wireless communication parameters for communications exchanged between the analyte sensor system and one or more of the remote devices.

53. the mode indicator is operable by the analyte sensor system to deactivate access to one of the access control parameter, the accuracy or calibration parameter, and the wireless communication parameter by the set of remote devices not within the partner class using the diabetes management partner interface; 53. The method of claim 52, wherein access by the set of remote devices to one of the access control parameter, the accuracy or calibration parameter, and the wireless communication parameter is activated when the analyte sensor system uses an operating mode corresponding to the set of remote devices.

54. determining that the analyte sensor system has not received wireless communication from the partner device for at least a predetermined amount of time; 50. The method of claim 49, further comprising: in response to the determination, and further in response to receiving a connection request from one of the remote devices in the set of remote devices not in the partner class, the analyte sensor system selecting an operational mode corresponding to the set of remote devices not in the partner class, wherein the operational mode corresponding to the set of remote devices not in the partner class is according to a configuration parameter set specific to the set of remote devices not in the partner class.

55. 55. The method of claim 54, further comprising removing the partner device from a whitelist.

56. receiving, by the analyte sensor system, a value for one of the configuration parameters from the partner device using the diabetes management partner interface; 50. The method of claim 49, further comprising: the analyte sensor system modifying the one of the configuration parameters using the value received from the partner device.

57. The analyte sensor system further includes transmitting a value of the configuration parameter to the display device, the value being: a specified time period after which the partner device is removed from a whitelist maintained for the analyte sensor system; a specified time period after which the display device is removed from the whitelist.

58. exchanging said wireless communications using said mode of operation corresponding to said partner device; modifying a whitelist maintained for the analyte sensor system to switch off slots for devices other than the partner device; and transmitting an advertisement message directed only to the partner device.

59. 50. The method of claim 49, further comprising: if the connection request does not originate from the partner class, the analyte sensor system selecting an operating mode corresponding to the set of remote devices not in the partner class, wherein the operating mode corresponding to the set of remote devices not in the partner class uses a configuration parameter set specific to the set of remote devices not in the partner class.

60. the display device is in the set of remote devices that are not in the partner class; using the diabetes management partner interface to provide a display device with access to the set of configuration parameters specific to the set of remote devices not within the partner class; 60. The method of claim 59, further comprising: the analyte sensor system, in response to input received from the display device, setting or modifying a value of one of the configuration parameters specific to the set of the remote devices not in the partner class.

61. 51. The method of claim 50, wherein exchanging the wireless communications using the operational mode corresponding to the partner class includes modifying an advertisement slot to advertise only to the partner device or partner device controller.

62. 51. The method of claim 50, wherein exchanging the wireless communications using the operational mode corresponding to the partner class includes the analyte sensor system only accepting connection requests received from the partner device in response to commands received via the diabetes management partner interface.

63. 63. The method of claim 62, wherein the command is received from the partner device.

64. 1. An analyte sensor system, the analyte sensor system using a diabetes management partner interface to control wireless communication between the analyte sensor system and one or more remote devices connectable to the analyte sensor system, the one or more remote devices including a display device and a partner device, the analyte sensor system comprising: a circuit operably coupled to a memory storing instructions that, when executed, cause the analyte sensor system to: determining whether a connection request received from one of the remote devices originates from a partner class within the one or more remote devices, the remote devices within the partner class being adapted to provide medication, the partner class including the partner device; If the connection request originates from the partner class, the analyte sensor system uses the diabetes management partner interface to enable selection of an operating mode corresponding to the partner class, and the operating mode uses a configuration parameter set of the partner class to support system requirements of the partner device.

65. 65. The analyte sensor system of claim 64, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to exchange the wireless communications with at least one of the remote devices using the operational mode corresponding to the partner class.

66. 66. The analyte sensor system of claim 65, wherein the wireless communications exchanged using the operational mode corresponding to the partner class include a mode indicator sent by the analyte sensor system to the at least one of the remote devices, the mode indicator usable by the at least one of the remote devices to determine the operational mode being used.

67. 67. The analyte sensor system of claim 66, wherein the configuration parameter set used to support the system requirements of the partner device includes one or more of: access control parameters of the display device or the partner device, accuracy or calibration parameters of the analyte sensor system, and wireless communication parameters for communications exchanged between the analyte sensor system and one or more of the remote devices.

68. the mode indicator is operable by the analyte sensor system to deactivate access to one or more of the access control parameters, the accuracy or calibration parameters, and the wireless communication parameters by the set of remote devices not within the partner class using the diabetes management partner interface; 68. The analyte sensor system of claim 67, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to provide access by the set of remote devices to one or more of the access control parameters, the accuracy or calibration parameters, and the wireless communication parameters when the analyte sensor system uses an operating mode corresponding to the set of remote devices.

69. The memory, when executed, provides the analyte sensor system with: determining that the analyte sensor system has not received wireless communication from the partner device for at least a predetermined amount of time; 65. The analyte sensor system of claim 64, further storing instructions to: in response to the determining, further in response to a connection request received from one of the remote devices in the set of remote devices not in the partner class, select an operating mode corresponding to the set of remote devices not in the partner class, wherein the operating mode corresponding to the set of remote devices not in the partner class is in accordance with a configuration parameter set specific to the set of remote devices not in the partner class.

70. 70. The analyte sensor system of claim 69, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to remove the partner device from a whitelist.

71. The memory, when executed, provides the analyte sensor system with: receiving a value of one of the configuration parameters from a partner device using the diabetes management partner interface; 65. The analyte sensor system of claim 64, further storing instructions to: modify the one of the configuration parameters using the value received from the partner device.

72. The memory, when executed, provides the analyte sensor system with: further comprising instructions to cause sending the value of the configuration parameter to the display device, the value being: a specified time period after which the partner device is removed from a whitelist maintained for the analyte sensor system; and and a specified amount of time before the display device is removed from the whitelist.

73. The memory, when executed, provides the analyte sensor system with: modifying a whitelist maintained for the analyte sensor system to switch off slots for devices other than the partner device; 66. The analyte sensor system of claim 65, further storing instructions to: transmit an advertisement message directed only to the partner device.

74. 65. The analyte sensor system of claim 64, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to select an operating mode corresponding to the set of remote devices not in the partner class if the connection request is not from the partner class, and wherein the operating mode uses a configuration parameter set specific to the set of remote devices not in the partner class.

75. The display device is within the set of remote devices that are not within the partner class, and the memory, when executed, provides the analyte sensor system with: using the diabetes management partner interface to provide the display device with access to the set of configuration parameters specific to the set of remote devices not within the partner class; 75. The analyte sensor system of claim 74, further storing instructions for setting or changing a value of one of the configuration parameters specific to the set of the remote devices not within the partner class in response to input received from the display device.

76. 66. The analyte sensor system of claim 65, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to modify an advertisement slot to advertise only to the partner device or partner device controller.

77. 66. The analyte sensor system of claim 65, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to only accept connection requests received from the partner device in response to commands received via the diabetes management partner interface.

78. 78. The analyte sensor system of claim 77, wherein the command is received from the partner device.

79. 1. A method for enabling configurability of an analyte sensor system that exchanges wireless communications with one or more of a partner device and a display device using a diabetes management interface, the method comprising: determining, by the analyte sensor system, that a first connection request has been sent from a remote device in a first class of remote devices; determining, by the analyte sensor system, that a second connection request has been sent from a remote device in a second class of remote devices, wherein the remote device in the second class of remote devices is adapted to deliver a medication, and the remote device in the first class of remote devices does not belong to the second class of remote devices; the analyte sensor system using any one of a plurality of modes of operation; a first operational mode of the plurality is specific to a first configuration that utilizes a remote device in the second class of remote devices and does not utilize a remote device in the first class of remote devices; a second operational mode of the plurality is specific to a second configuration that does not utilize devices from the second class of remote devices; A method wherein a third operational mode of the plurality is specific to a third configuration utilizing remote devices in the first class of remote devices and remote devices from the second class of remote devices.

80. 80. The method of claim 79, wherein using the first operational mode of the plurality includes providing the remote device in the second class of remote devices with the authority to modify permissions provided to the remote device in the first class of remote devices using the diabetes management partner interface.

81. 81. The method of claim 80, wherein using the first operational mode of the plurality further comprises receiving permission from the remote device in the first class of remote devices for the remote device in the second class of remote devices to communicate with the analyte sensor system.

82. 80. The method of claim 79, wherein using the first mode of operation further comprises: in response to input received from the remote devices in the second class of remote devices via the diabetes management partner device, the analyte sensor system preventing connection with devices other than the remote devices in the second class of remote devices.

83. Blocking the connection advertising to the remote device in the second class of remote devices using a first advertisement slot; 83. The method of claim 82, comprising: advertising using a second advertisement slot to the remote device in the second class of remote devices or to a controller for the remote device in the second class of remote devices.

84. 83. The method of claim 82, wherein preventing the connection includes the analyte sensor system using the diabetes management partner interface to configure or cause a modification of an advertisement structure to include a single advertisement period dedicated to the remote device in the second class of devices.

85. 83. The method of claim 82, wherein the blocking of connections includes the analyte sensor system accepting connection requests only from the remote devices in the second class of remote devices.

86. 80. The method of claim 79, wherein using the first operating mode of the plurality further comprises the analyte sensor system modifying a timeout rule associated with the remote device in the second class of remote devices using input received from the remote device in the second class of remote devices via the diabetes management interface.

87. using the second mode of operation of the plurality, modifying a whitelist to exclude the remote device in the second class of remote devices; rejecting connection requests received from the remote devices in the second class of remote devices; and b. advertising exclusively to remote devices in the first class of remote devices.

88. 88. The method of claim 87, wherein using the third operational mode of the plurality includes the analyte sensor system receiving, via the diabetes management interface, from a remote device in the second class of remote devices an indication of a level of access to the analyte sensor system that will be granted to the remote device in the first class of remote devices.

89. the analyte sensor system implementing the access level using the diabetes management interface; 90. The method of claim 88, further comprising: notifying the remote devices in the first class of remote devices of the access level.

90. 89. The method of claim 88, wherein, depending on the access level, the remote devices in the first class of remote devices can receive analyte data from the analyte sensor system but cannot access accuracy or calibration parameters used by the analyte sensor system for the third operation.

91. 1. An analyte sensor system for exchanging wireless communications with one or more partner devices and a display device, the analyte sensor system being configurable by a diabetes management partner interface, the analyte sensor system comprising: a circuit operably coupled to a memory storing instructions that, when executed, cause the analyte sensor system to: determining that a first connection request is sent from a remote device in a first class of remote devices; determining that a second connection request is sent from a remote device in a second class of remote devices, wherein the remote device in the second class of remote devices is adapted to deliver medication, and the remote device in the first class of remote devices does not belong to the second class of remote devices; using any one of a plurality of operating modes; a first operational mode of the plurality is specific to a first configuration that utilizes a remote device in the second class of remote devices and does not utilize a remote device in the first class of remote devices; a second operational mode of the plurality is specific to a second configuration that does not utilize devices from the second class of remote devices; The analyte sensor system, wherein a third operational mode of the plurality is specific to a third configuration utilizing a remote device in the first class of remote devices and a remote device from the second class of remote devices.

92. 92. The analyte sensor system of claim 91, wherein the memory further stores instructions that, when executed, cause the analyte sensor system, in the first operational mode of the plurality, to provide the remote device in the second class of remote devices with authority to modify permissions provided to the remote device in the first class of remote devices using the diabetes management partner interface.

93. 93. The analyte sensor system of claim 92, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to receive, in the first operational mode of the plurality, from a remote device in the first class of remote devices, permission for a remote device in the second class of remote devices to communicate with the analyte sensor system.

94. 92. The analyte sensor system of claim 91 , wherein the memory further stores instructions that, when executed, cause the analyte sensor system, in the first operational mode of the plurality, to prevent connection with devices other than the remote devices in the second class of remote devices in response to input received via the diabetes management partner device from the remote devices in the second class of remote devices.

95. The memory, when executed, provides the analyte sensor system with: advertising to the remote device in the second class of remote devices using a first advertisement slot; 95. The analyte sensor system of claim 94, further comprising instructions to advertise to the remote device in the second class of remote devices or a controller for the remote device in the second class of remote devices using a second advertisement slot.

96. 95. The analyte sensor system of claim 94, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to use the diabetes management partner interface to configure or cause a modification of an advertisement structure to include a single advertisement period dedicated to the remote devices in the second class of devices.

97. 95. The analyte sensor system of claim 94, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to accept connection requests from only the remote devices in the second class of remote devices.

98. 92. The analyte sensor system of claim 91 , wherein the memory further stores instructions that, when executed, cause the analyte sensor system, in the first operational mode of the plurality, to modify a timeout rule associated with the remote device in the second class of remote devices using input received from the remote device in the second class of remote devices via the diabetes management interface.

99. The memory, when executed, causes the analyte sensor system, in the second operational mode of the plurality, to: modifying a whitelist to exclude the remote device in the second class of remote devices; rejecting connection requests received from the remote devices in the second class of remote devices; 92. The analyte sensor system of claim 91, further storing instructions to advertise exclusively to remote devices in the first class of remote devices.

100. 100. The analyte sensor system of claim 99, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to receive, via the diabetes management interface, an indication of a level of access to the analyte sensor system from a remote device in the second class of remote devices that will be given to the remote device in the first class of remote devices in the third operating mode of the plurality.

101. The memory, when executed, provides the analyte sensor system with: implementing the access levels using the diabetes management interface; 101. The analyte sensor system of claim 100, further comprising instructions for notifying the remote devices in the first class of remote devices of the access level.

102. 101. The analyte sensor system of claim 100, wherein, depending on the access level, the remote devices in the first class of remote devices can receive analyte data from the analyte sensor system but cannot access accuracy or calibration parameters used by the analyte sensor system for the third mode of operation.

103. 1. A method for facilitating wireless communication exchange with an analyte management system using a diabetes management interface, comprising: establishing a first connection between the analyte sensor system and a first partner device using the diabetes management partner interface; the analyte sensor system providing the first partner device with access to a configuration parameter set via a diabetes management interface; setting or causing a first modification of the configuration parameter set in response to input received from the first partner device via the diabetes management partner interface, wherein the setting or causing of the first modification is made according to system requirements of the first partner device; establishing a second connection between the analyte sensor system and a second partner device using the diabetes management partner interface; the analyte sensor system providing the second partner device with access to the configuration parameter set via the diabetes management interface; causing a second modification of the configuration parameter set in response to input received from the second partner device via the diabetes management partner interface, the second modification being made in response to system requirements of the second partner device.

104. 104. The method of claim 103, wherein establishing the second connection using the diabetes management partner interface occurs after the first connection is terminated.

105. In response to the analyte sensor system receiving identification information for a third partner device, attempting to establish a third connection between the analyte sensor system and the third partner device using the diabetes management partner interface; 104. The method of claim 103, further comprising: in response to establishing the third connection between the analyte sensor system and the third partner device, causing a third modification of the configuration parameter set in response to input received via the diabetes management partner interface, the third modification being made according to system requirements of the third partner device.

106. 106. The method of claim 105, wherein the identification information for the third partner device is stored in a server system, and the identification information indicates whether the third partner device is authorized to communicate with the analyte sensor system.

107. 107. The method of claim 106, wherein the analyte sensor system receiving the identification information for the third partner device comprises the analyte sensor system receiving the identification information for the third partner device from a display device that received the identification information for the third partner device from the server system.

108. responsive to the analyte sensor system receiving the identification information for the third partner device, using the identification information for the third partner device to determine whether the third partner device is authorized to communicate with the analyte sensor system; canceling the attempt to establish the third connection between the analyte sensor system and the third partner device in response to determining that the third partner device is not authorized to communicate with the analyte sensor system; and 107. The method of claim 106, further comprising: in response to determining that the third partner device is not authorized to communicate with the analyte sensor system, establishing the third connection between the analyte sensor system and the third partner device using the diabetes management partner interface.

109. determining that the third partner device is not authorized to communicate with the analyte sensor system occurs at a first time; determining that the third partner device is authorized to communicate with the analyte sensor system occurs at a second time; 109. The method of claim 108, wherein the identification information for the third partner device is updated at the server system between the first time and the second time.

110. 109. The method of claim 108, wherein system requirements for the third partner device are stored in a server system, and the method further includes causing a fourth modification of the configuration parameter set in response to input received via the diabetes management partner interface, the fourth modification being made in response to an updated version of the system requirements for the third partner device.

111. 1. An analyte sensor system that facilitates wireless communication exchange using a diabetes management interface, comprising: a circuit operably coupled to a memory storing instructions that, when executed, cause the analyte sensor system to: establishing a first connection between the analyte sensor system and a first partner device using the diabetes management partner interface; providing the first partner device, via the diabetes management interface, access to a set of configuration parameters; setting or causing a first modification of the configuration parameter set in response to input received from the first partner device via the diabetes management partner interface, the first modification being made according to system requirements of the first partner device; establishing a second connection between the analyte sensor system and a second partner device using the diabetes management partner interface; providing the second partner device with access to the configuration parameter set via the diabetes management interface; and causing a second modification of the configuration parameter set in response to input received from the second partner device via the diabetes management partner interface, the second modification being made according to system requirements of the second partner device.

112. 112. The analyte sensor system of claim 111, wherein the second connection is established after the first connection is terminated.

113. The memory, when executed, provides the analyte sensor system with: receiving identification information for a third partner device; In response to receiving identification information for the third partner device, attempting to establish a third connection between the analyte sensor system and the third partner device using the diabetes management partner interface; 112. The analyte sensor system of claim 111, further storing instructions to: in response to the third connection being established between the analyte sensor system and a third partner device, cause a third modification of the configuration parameter set in response to input received via the diabetes management partner interface, the third modification being made according to requirements of the third partner device.

114. 114. The analyte sensor system of claim 113, wherein the identification information for the third partner device is stored in a server system, and the identification information indicates whether the third partner device is authorized to communicate with the analyte sensor system.

115. 115. The analyte sensor system of claim 114, wherein the memory further stores instructions that, when executed, cause the analyte sensor system to receive identification information for the third partner device from a display device that received the identification information for the third partner device.

116. The memory, when executed, provides the analyte sensor system with: responsive to receiving the identification information for the third partner device, using the identification information for the third partner device to determine whether the third partner device is authorized to communicate with the analyte sensor system; canceling the attempt to establish the third connection between the analyte sensor system and the third partner device in response to determining that the third partner device is not authorized to communicate with the analyte sensor system; 115. The analyte sensor system of claim 114, further storing instructions for: establishing the third connection between the analyte sensor system and the third partner device using the diabetes management partner interface in response to determining that the third partner device is authorized to communicate with the analyte sensor system.

117. the determination that the third partner device is not authorized to communicate with the analyte sensor system is made at a first time; the determining that the third partner device is authorized to communicate with the analyte sensor system occurs at a second time; 117. The analyte sensor system of claim 116, wherein the identification information for the third partner device is updated at the server system between the first time and the second time.

118. 114. The analyte sensor system of claim 113, wherein system requirements for the third partner device are stored in a server system, and the memory further stores instructions that, when executed, cause the analyte sensor system to cause a fourth modification of the configuration parameter set in response to input received via the diabetes management partner interface, the fourth modification being made in accordance with an updated version of the system requirements for the third partner device.

119. 1. A method comprising: receiving an indication that the analyte sensor system is entering an operational mode specific to the use of the partner device; establishing a connection between the analyte sensor system and the partner device; setting or modifying configuration parameters by the analyte management system in response to input received from the partner device via a diabetes management partner interface, the input received from the partner device indicating corresponding operating parameters to be used by the partner device to communicate with the analyte sensor system using the operating mode, the configuration parameters configured according to system requirements of the partner device; and implementing the operational mode specific to the use of the partner device using the operational parameters of the analyte sensor system to conform to the system requirements of the partner device.

120. The configuration parameters are: an authorization parameter for a display device to issue command or control signals to start, stop, calibrate, or set the length of a sensor session for the analyte sensor system; Battery or power management parameters, connection model parameters, timeout parameters, one or more of which relate to a length of time to keep the partner device on a whitelist, an advertising timeout, a connection establishment timeout, and an authorization timeout; warning parameters, configuration settings that govern the operational modes of the analyte sensor system; and 120. The method of claim 119, further comprising one or more of: a remote server parameter.

121. receiving, by the analyte sensor system, an indication of a transition from implementation in the mode of operation specific to the use of the partner device; 120. The method of claim 119, further comprising: restoring the configuration parameters to a previous state that existed before the analyte sensor system set or modified the configuration parameters in response to the input received from the partner device.

122. 122. The method of claim 121, wherein restoring the configuration parameter set to the previous state comprises removing the partner device from a whitelist.

123. 1. A method comprising: the analyte sensor system includes determining whether the wireless communication system includes one or more of a display device and a partner device; When the wireless communication system includes the display device, determining whether the analyte sensor system connects to the display device using one of an intermittent connection model and a continuous connection model; If the system includes the partner device, determining whether the analyte sensor system connects to the partner device using one of the intermittent connection model and the continuous connection model; the analyte sensor system determining whether to use the intermittent connection model or the continuous connection model to connect to one or more of the display device and the partner device includes using configuration parameters set or modified using input received from the partner device via a diabetes management partner interface.

124. 124. The method of claim 123, wherein determining that the analyte sensor system connects to the partner device according to the intermittent connection model is performed using one of the configuration parameters set in response to a power requirement of the partner device.

125. 124. The method of claim 123, wherein determining that the analyte sensor system connects to the partner device according to the serial connection model is performed using a determination that the system includes the display device.

126. 1. A method comprising: receiving, by an analyte sensor application of the display device, an interface to a partner device application associated with the partner device; the analyte sensor application using the interface to collect information collected by the partner device application, the information including one or more of pairing data and analyte dosage data; the analyte sensor application providing analyte sensor system information using the interface, the analyte sensor information comprising: the analyte sensor system is functional; a connectivity model utilized by the analyte sensor system with respect to the partner device or the display device; and configuration parameters used by the analyte sensor system to communicate with one or more of the partner device and the display device.

127. the analyte sensor application receiving analyte data from the analyte sensor system; 127. The method of claim 126, further comprising the analyte sensor application providing a visual display including the analyte data and the information collected by the partner device application.

128. the analyte sensor application receiving information regarding an analyte value from the analyte sensor system; 127. The method of claim 126, further comprising the analyte sensor application using the interface to communicate the analyte value to the partner device via the partner device application.

129. 127. The method of claim 126, further comprising the analyte sensor application receiving, via the interface, medication delivery information collected by the partner device.

130. 127. The method of claim 126, further comprising the analyte sensor application receiving an alert from the partner device via the interface, the alert relating to an issue with functionality of the partner device.

131. 131. The method of claim 130, further comprising the analyte sensor application of the display device causing the alert to be provided via a user interface.

132. 131. The method of claim 130, further comprising the analyte sensor application of the display device causing the alert to be provided via a remote server.

133. 1. A method comprising: establishing a connection between the analyte sensor system and a partner device; the analyte sensor system receiving configuration parameter information from the partner device using a diabetes management partner interface, the configuration parameter information relating to operation of the analyte sensor system in accordance with system requirements of the partner device, the configuration parameter information comprising: accessibility provided to a remote device connectable to the analyte sensor system; and one or more values ​​of a configurable parameter set to be used in a connection established between the analyte sensor system and the partner device, wherein the one or more values ​​of the configuration parameter set are selected according to the system requirements of the partner device.

134. the configurability parameter set is connection information of the remote device; a connectivity model used for a particular device connectable to the analyte sensor system; connection command related data to be read by or sent to said remote device; information regarding non-use of said partner device; security or privacy related parameters, Information about power management or battery usage, the number of devices connectable to the analyte sensor system; a device type for each device connectable to the analyte sensor system; and 134. The method of claim 133, comprising one or more of: types of information related to analyte data that can be read and transmitted by a remote device connectable to the analyte sensor system.

135. The connection command related data is whether the partner device or the remote device is eligible for inclusion on a whitelist of the analyte sensor system; whether the partner device or the remote device complies with the expiration of the whitelist; and and an amount of time until the partner device or remote device sets the whitelist to expire if the partner device or remote device complies with the whitelist expiration.

136. 135. The method of claim 134, wherein the information related to power control includes suggestions to expire certain devices to extend battery life of the analyte sensor system.

137. 135. The method of claim 134, wherein the information related to power control or battery usage is collected via a control mechanism that balances battery life of the analyte sensor system against connection reliability between the analyte sensor system and the partner device or the remote device.

138. 135. The method of claim 134, wherein the information related to power control triggers a low power mode of the analyte sensor system.

139. 134. The method of claim 133, wherein the degree of access is received only after the analyte sensor system receives permission for the degree of access to be modified using the parameter information received from the partner device.

140. 1. A method comprising: establishing a connection between a display device and an analyte sensor system; receiving, by the display device, an indication that the analyte sensor system is connected to a partner device; receiving, via the diabetes management partner interface, configuration parameters for an alert originated from the partner device after receiving authorization to provide the partner device with access to a set of configuration parameters via the diabetes management partner interface; the display device providing a user interface for configuring alerts generated by the analyte sensor system and alerts generated by the partner device; and using input received via the user interface to cause modification of the configuration parameters of the alert issued from the partner device, the modification being made in accordance with system requirements of the partner device.

141. 141. The method of claim 140, further comprising receiving, via the user interface, a selection of the partner device or a remote device among a plurality of remote devices, including the display device, to be used as a primary device for providing one or more of alerts originating from the analyte sensor system and alerts originating from the partner device.

142. 142. The method of claim 141, further comprising providing the alert to a device other than the primary device when the battery capacity of the primary device falls below a threshold.

143. 141. The method of claim 140, further comprising the display device receiving, via the user interface, a selection of respective alert types to be provided for the alerts originating from the partner device and the alerts originating from the analyte sensor system.

144. providing said alert via a primary notification device; 141. The method of claim 140, further comprising: if no acknowledgment is received in response to providing the alert via the primary notification device, providing the alert via a secondary notification device, wherein the primary notification device and the secondary notification device are selected from the group consisting of the partner device, the analyte sensor system, and at least one of the plurality of remote devices.

145. 1. A method for monitoring the operability status of a medication delivery device, comprising: from the drug delivery device Reservoir change, Pump rewind, Pump priming, Cannula filling, and receiving medication delivery device information relating to one or more of: determining a combination of the analyte delivery system information and analyte data generated using the analyte sensor system; the analyte sensor system using the combination to determine an operability status of the medication delivery device.

Images