Diabetes Management Partner Interface for Wireless Transmission of Analyte Data

Abstract

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

Description

[0001] Incorporation by Reference into Related Applications

[0002] Any and all claims identified in the application data sheet, or any corrections thereof, are hereby incorporated by reference herein in accordance with 37 CFR 1.57. This application claims the benefit of U.S. Provisional Application No. 62 / 579,061, filed Oct. 30, 2017. The foregoing application is incorporated by reference in its entirety and is hereby expressly made a part of this specification. Field of the Invention

[0003] The present disclosure generally relates to an interface for wirelessly transmitting analyte data collected using an analyte sensor system. More specifically, the present disclosure relates to systems, methods, devices, and apparatuses for increasing the flexibility of an analyte sensor system for wireless communication with a display device, a medical device, and / or other (e.g., electronic) devices using a diabetes management partner interface. Background of the Invention

[0004] Diabetes is a disease in which the pancreas fails to produce sufficient insulin (type 1 or insulin-dependent) and / or insulin is ineffective (type 2 or non-insulin-dependent). In a diabetic state, a patient has hyperglycemia, which results in a series of physiological abnormalities associated with small blood vessel deterioration (renal failure, skin ulcers, or vitreous hemorrhage in the eye). Hypoglycemic reactions (hypoglycemia) can be caused by an overdose of insulin, or after normal doses of insulin or hypoglycemic agents and in conjunction with excessive exercise or insufficient food intake.

[0005] Conventionally, diabetics carry self-monitoring blood glucose (SMBG) monitors, which may require uncomfortable finger-pricking methods. Due to the lack of comfort and convenience, diabetic patients typically measure their glucose levels only two to four times per day. Unfortunately, these time intervals are spread too far apart, such that diabetic patients are likely to become aware of high or low blood glucose conditions too late, sometimes resulting in dangerous side effects. In fact, due to the limitations of conventional methods, diabetic patients are not only unlikely to obtain SMBG values in a timely manner, but also do not know whether their blood glucose values are rising (higher) or falling (lower).

[0006] Accordingly, various non-invasive, transdermal (e.g., percutaneous) and / or implantable electrochemical sensors for continuously detecting and / or quantifying blood glucose values are being developed. These devices typically emit raw or minimally processed data for subsequent analysis on a remote device that may include a display. The transmission to the wireless display device can be wireless. The remote device can then provide the user with information about the user's blood glucose level. Since systems using such implantable sensors can provide the user with more up-to-date information, such systems can reduce the risk that the user is unable to adjust the user's blood glucose level. However, such systems typically still rely on the user to take action to adjust the user's blood glucose level, such as by injection.

[0007] Certain devices have been introduced to automatically adjust the user's blood glucose level. The introduction of such devices creates interoperability issues with other devices available for blood glucose monitoring (e.g., the aforementioned remote devices), especially in cases where the devices are deployed by different manufacturers. For example, the introduction of devices for automatic blood glucose level adjustment may be affected by certain requirements regarding interference, battery life, accuracy, and reliability, etc. The manufacturer of the monitoring device may not know these requirements in advance and / or may wish to change these requirements from time to time in some cases, including based on ecosystem configurations (such as available network connections, the number of connected devices, etc.). In addition, as more and more electronic devices can be networked, more devices can be used to manage health conditions (such as diabetes). However, while maintaining synchronized analyte data communication among multiple devices is useful, it becomes increasingly difficult for the user.

[0008] Accordingly, traditional systems are not well-suited for the deployment and integration of devices for monitoring blood glucose levels and additional devices for adjusting blood glucose levels, especially in cases where the devices are provided by various manufacturers, where the devices communicate wirelessly via various types of communication networks and / or media, and where a specific level of flexibility and / or adaptability is required. SUMMARY OF THE INVENTION

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

[0010] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the first aspect, the one partner device is an automated insulin delivery device or a manual insulin delivery device.

[0011] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the first aspect, the set of configuration parameters includes one or more of a set of wireless connectivity parameters, a set of access control parameters, and a set of analyte data parameters.

[0012] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the first aspect, the system requirements are associated with one of the following: the battery capacity of the one partner device; the accuracy requirements of the one partner device; the communication protocol used by the one partner device; the regulatory requirements to which the one partner device is calibrated; and the expected operating time of the one partner device.

[0013] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the first aspect, the set of wireless connectivity parameters includes the conditions for removing the one partner device from the whitelist maintained for the analyte sensor system. In an example, the analyte sensor system setting the set of configuration parameters or causing the modification of the set of configuration parameters according to the system requirements of the one partner device includes the analyte sensor system setting the conditions such that when the battery level of the one partner delivery device meets a threshold, the one partner device is to be removed from the whitelist.

[0014] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the first aspect, the set of wireless connectivity parameters includes an advertisement structure. In an example, the analyte sensor system setting the set of configuration parameters or causing the modification of the set of configuration parameters according to the system requirements of the one partner device includes the analyte sensor system setting or modifying the advertisement structure using the diabetes management partner interface.

[0015] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the first aspect, the set of access control parameters includes one or more of the following: the number of display devices to which the analyte sensor system can connect; and the level of access or control that the analyte sensor system can grant to one or more of the display devices.

[0016] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the first aspect, the set of analyte data parameters includes the calibration period of the analyte sensor system. In an example, the analyte sensor system setting or causing the modification of the set of configuration parameters according to the system requirements of the one partner device includes the analyte sensor system setting or modifying the calibration period using the diabetes management partner interface.

[0017] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the first aspect, the set of analyte data parameters includes a factory calibration code. In an example, the analyte sensor system receives an indication to use the factory calibration code from the one partner device using the diabetes management partner interface according to the system requirements of the one partner device. The analyte sensor system setting or causing the modification of the set of configuration parameters according to the system requirements of the one partner device can include the analyte sensor system setting or modifying the calibration period to zero or none using the diabetes management partner interface.

[0018] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the first aspect, the set of wireless connectivity parameters includes settings in a remote server. The analyte sensor system setting or causing the modification of the set of configuration parameters according to the system requirements of the one partner device can include configuring the analyte sensor to perform multiple operations using the diabetes management partner interface. Such operations can include using services provided by the remote server. Such operations can include transmitting diabetes management feedback to one or more display devices connected to the analyte sensor system in response to services provided by the remote server. Such operations can include: if the services provided by the remote server become unavailable, prohibiting the use of the services and sending a relevant notification to the display devices connected to the analyte sensor system.

[0019] In certain embodiments of the first aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the first aspect, the set of analyte date parameters includes a bolus calculation parameter. In an embodiment, the analyte sensor system setting the set of configuration parameters or causing the modification of the set of configuration parameters according to the system requirements of the one partner device includes the analyte sensor system providing access to the bolus calculation parameter to the one partner device using the diabetes management partner interface. In an embodiment, the method further includes the analyte sensor system providing a bolus recommendation based on a calculation performed using the bolus calculation parameter.

[0020] A second aspect of the present disclosure includes an analyte sensor system for wireless communication with a plurality of partner devices. The analyte sensor system is configurable by using a diabetes management partner interface. The analyte sensor system includes an analyte sensor for producing analyte information. The analyte sensor system includes a transceiver configured to transmit and receive wireless signals. In addition, the analyte sensor system includes a memory for storing a set of configuration parameters used by the transceiver to transmit and receive wireless signals. The analyte sensor system further includes circuitry operatively coupled to the transceiver and the memory and configured to cause the analyte sensor system to perform a plurality of operations. Such operations include receiving authorization to provide access to a set of configuration parameters to one of the partner devices through the diabetes management partner interface. Such operations include setting the set of configuration parameters or causing a modification of the set of configuration parameters according to the system requirements of the partner device in response to an input received from the one partner device through the diabetes management partner interface.

[0021] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, the one partner device is an automatic insulin delivery device or a manual insulin delivery device.

[0022] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, the set of configuration parameters includes one or more of a set of wireless connectivity parameters, a set of access control parameters, and a set of analyte data parameters.

[0023] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, the system requirements are associated with one of the following: the battery capacity of the one partner device; the accuracy requirements of the one partner device; the communication protocol used by the one partner device; the regulatory requirements configured for the one partner device; and the expected operating time of the one partner device.

[0024] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, the set of wireless connectivity parameters includes conditions for removing the one partner device from a whitelist maintained for the analyte sensor system. In an example, the circuitry is further configured to cause the analyte sensor system to set the conditions according to the system requirements of the one partner such that when the battery level of the one partner delivery device meets a threshold, the device is to remove the one partner device from the whitelist.

[0025] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, the set of wireless connectivity parameters includes an advertisement structure. In an example, the circuitry is further configured to cause the analyte sensor system to set or modify the advertisement structure using the diabetes management partner interface.

[0026] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, the set of access control parameters includes one or more of the following: the number of display devices to which the analyte sensor system can connect; and the level of access or control that the analyte sensor system can give to one or more of the display devices.

[0027] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, the set of analyte data parameters includes a calibration period of the analyte sensor system. In an example, the circuitry is further configured to cause the analyte sensor system to set or modify the calibration period using the diabetes management partner interface.

[0028] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, the set of analyte data parameters includes a factory calibration code. In an example, the circuitry is further configured to cause the analyte sensor system to receive an indication to use the factory calibration code from the one partner device using the diabetes management partner interface according to the system requirements of the one partner device. In an example, the circuitry is further configured to cause the analyte sensor system to set or modify the calibration period to zero or none using the diabetes management partner interface.

[0029] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, the set of wireless connectivity parameters includes settings in a remote server. In an embodiment, the circuitry is further debugged to cause the analyte sensor system to configure the analyte sensor to perform additional operations using the diabetes management partner interface. One such operation is to use a service provided by 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 a service provided by the remote server. One such operation is to disable the service and send a relevant notification to the display device connected to the analyte sensor system if the service provided by the remote server becomes unavailable.

[0030] In certain embodiments of the second aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the second aspect, a set of analyte date parameters includes bolus calculation parameters. In an embodiment, the circuitry is further debugged to cause the analyte sensor system to configure the analyte sensor system to provide access to the bolus calculation parameters to one of the partner devices using the diabetes management partner interface according to the system requirements of the partner device. In an embodiment, the circuitry is further debugged to cause the analyte sensor to provide a bolus recommendation based on calculations performed using the bolus calculation parameters.

[0031] A third aspect of the present disclosure includes a system. The system includes one or more partner devices that are debugged to deliver insulin to a user. The system includes an analyte sensor system that is debugged to generate analyte information. The analyte sensor system includes a set of configuration parameters for transmitting and receiving wireless signals. The configuration parameters can be configured by using a diabetes management partner interface. The system further includes a display device that is capable of connecting to the analyte sensor system and is debugged to display analyte information and provide authorization to the analyte sensor system to provide access to the set of configuration parameters to one of the partner devices through the diabetes management partner interface. The one partner device is debugged to set the set of configuration parameters or cause a modification to the set of configuration parameters using the diabetes management partner interface according to the system requirements of the partner device.

[0032] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, the one partner device is an automatic insulin delivery device or a manual insulin delivery device.

[0033] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, the set of configuration parameters includes one or more of a set of wireless connectivity parameters, a set of access control parameters, and a set of analyte data parameters.

[0034] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, the system requirements are associated with one of the following: the battery capacity of the one partner device; the accuracy requirements of the one partner device; the communication protocol used by the one partner device; the regulatory requirements for commissioning the one partner device; and the expected operating time of the one partner device.

[0035] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, the set of wireless connectivity parameters includes the conditions for removing the one partner device from the whitelist maintained for the analyte sensor system. In an example, the one partner device is further commissioned to use the diabetes management partner interface to set or modify the conditions such that when the battery level of the one partner delivery device reaches a threshold, the one partner device is to be removed from the whitelist.

[0036] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, the set of wireless connectivity parameters includes an advertisement structure. In an example, the one partner device is further commissioned to use the diabetes management partner interface to set or modify the advertisement structure.

[0037] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, the set of access control parameters includes one or more of the following: the number of display devices to which the analyte sensor system can connect; and the level of access or control that the analyte sensor system can grant to one or more of the display devices.

[0038] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, the set of analyte data parameters includes the calibration period of the analyte sensor system. In an example, the one partner device is further commissioned to use the diabetes management partner interface to set or modify the calibration period.

[0039] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, the set of analyte data parameters includes a factory calibration code. In an example, the one partner device is further debugged to use the diabetes management partner interface: provide an indication to use the factory calibration code to the analyte sensor system according to the system requirements of the one partner device; and set or modify the calibration period to zero or none.

[0040] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, the set of wireless connectivity parameters includes settings in a remote server. In an example, the one partner device is further debugged to use the diabetes management partner interface to configure the analyte sensor to perform multiple operations. The one partner device is further debugged to use services provided by the remote server. The one partner device is further debugged to transmit diabetes management feedback to a display device connectable to the analyte sensor system in response to a service provided by the remote server. The one partner device is further debugged to: disable the service if the service provided by the remote server becomes unavailable, and send a relevant notification to the display device connectable to the analyte sensor system.

[0041] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, a set of analyte date parameters includes bolus calculation parameters. In an example, the one partner device is further debugged to configure the analyte sensor system to provide access to the bolus calculation parameters to the one partner device according to the system requirements of the partner device using the diabetes management partner interface. In an example, the one partner device is further debugged to receive a bolus recommendation from the analyte sensor system based on a calculation performed using the bolus calculation parameters using the diabetes management partner interface.

[0042] A fourth aspect of the present disclosure includes a method of 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. For the first wireless communication path, the analyte sensor system provides a first level of access or control of the analyte sensor system to the display device. The method further 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 level of access or control to implement a second level of access or control according to the system requirements of the partner device. The modification is caused in response to an input received from the partner device through the diabetes management partner interface.

[0043] In certain embodiments that are generally applicable to the fourth aspect but also particularly applicable in combination with any other embodiment of the fourth aspect, the modification of the first level of access or control includes using the diabetes management partner interface to set or change a set of configuration parameters implemented by the analyte sensor system according to the system requirements of the partner device.

[0044] In certain embodiments that are generally applicable to the fourth aspect but also particularly applicable in combination with any other embodiment of the fourth aspect, the set of configuration parameters includes one or more of the following: access control parameters for the display device or the partner device, accuracy parameters or calibration parameters of the analyte sensor system, and wireless communication parameters for communication to be exchanged between the analyte sensor system and one or more of the display device and the partner device.

[0045] In certain embodiments that are generally applicable to the fourth aspect but also particularly applicable in combination with any other embodiment of the fourth aspect, using the diabetes management partner interface to set or change the set of configuration parameters includes granting the partner device the permission to configure the accuracy parameters or calibration parameters of the analyte sensor system through the diabetes management partner interface.

[0046] In certain embodiments that are generally applicable to the fourth aspect but also particularly applicable in combination with any other embodiment of the fourth aspect, using the diabetes management partner interface to set or change the set of configuration parameters includes revoking the permission of the display device to configure the accuracy parameters or calibration parameters of the analyte sensor.

[0047] In certain embodiments of the fourth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fourth aspect, the access control parameter includes a whitelist of devices that can be connected to the analyte sensor system. The method may further include using the diabetes management partner interface to set or change the set of configuration parameters, including setting or modifying the amount of time that the partner device is to remain on the whitelist before being removed from the whitelist.

[0048] A fifth aspect of the present disclosure includes an analyte sensor system for wirelessly communicating with one or more of a display device and a partner device. The analyte sensor system can be configured by using a diabetes management partner interface. The analyte sensor system includes a memory for storing a set of configuration parameters used by a transceiver to transmit and receive the wireless signals. The analyte sensor system further includes circuitry operably coupled to the transceiver and the memory and configured to cause the analyte sensor system to perform a plurality of operations. One such operation is to enable a first wireless signal communication path. The first wireless communication signal path is between the analyte sensor system and the display device. For the first wireless communication path, the analyte sensor system provides a first level of access or control of the analyte sensor system to the display device. Another such operation is to enable a second wireless signal communication path. The second wireless signal communication path is between the analyte sensor system and the partner device. The second wireless signal communication path is enabled by modifying the first level of access or control by the analyte sensor system. The modification of the first level of access or control is in response to an input received from the partner device through the diabetes management partner interface. The modification of the first level of access or control is to implement a second level of access or control according to the system requirements of the partner device.

[0049] In certain embodiments of the fifth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fifth aspect, to perform the modification of the first level of access or control, the circuitry is further configured to cause the analyte sensor system to set or change a set of configuration parameters implemented by the analyte sensor system according to the system requirements of the partner device by using the diabetes management partner interface.

[0050] In certain embodiments of the fifth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fifth aspect, the set of configuration parameters includes one or more of the following: access control parameters of the display device or the partner device, accuracy parameters or calibration parameters of the analyte sensor system, and wireless communication parameters of the communication to be exchanged between the analyte sensor system and one or more of the display device and the partner device.

[0051] In certain embodiments of the fifth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fifth aspect, the circuitry is further configured to cause the analyte sensor system to grant the partner device permission to configure the accuracy parameters or calibration parameters of the analyte sensor system via the diabetes management partner interface.

[0052] In certain embodiments of the fifth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fifth aspect, the circuitry is further configured to cause the analyte sensor system to revoke the permission to configure the accuracy parameters or calibration parameters of the analyte sensor from the display device.

[0053] In certain embodiments of the fifth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fifth aspect, the access control parameters include a whitelist of devices that can be connected to the analyte sensor system. In an example, the circuitry is further configured to set or modify the amount of time that the partner device is to remain on the whitelist before being removed from the whitelist.

[0054] A sixth aspect of the present disclosure includes a method of using a diabetes management partner interface of an analyte sensor system 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 method includes the analyte sensor system determining whether a connection request received from one of the remote devices originates from a partner category within the one or more remote devices. The remote devices in the partner category are configured to provide a medicament. The partner category includes the partner device. The method includes: if the connection request originates from the partner category, using the diabetes management partner interface to implement a selection of an operating mode corresponding to the partner category. The operating mode uses a set of configuration parameters of the partner category to support the system requirements of the partner device.

[0055] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, the method includes exchanging the wireless communication with at least one of the remote devices using an operating mode corresponding to the partner class.

[0056] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, exchanging the wireless communication using the operating mode corresponding to the partner category includes transmitting a mode indicator that can be used by at least one of the remote devices to determine the operating mode being used.

[0057] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, the set of configuration parameters for supporting the system requirements of the partner device includes one or more of the following: access control parameters of the display device or the partner device, accuracy parameters or calibration parameters of the analyte sensor system, and wireless communication parameters of the communication to be exchanged between the analyte sensor system and one or more of the remote devices.

[0058] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, the mode indicator can be operated by the analyte sensor system to deactivate access by a set of the remote devices not in the partner class to one or more of the access control parameters, the accuracy parameters or calibration parameters, and the wireless communication parameters using the diabetes management partner interface. In an embodiment, when the analyte sensor system uses an operating mode corresponding to the set of remote devices, access by the set of remote devices to one or more of the access control parameters, the accuracy parameters or calibration parameters, and the wireless communication parameters is activated.

[0059] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, the method further 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 further includes, in response to the determination and further in response to a connection request received from one of the remote devices in a set of the remote devices not in the partner class, selecting an operating mode corresponding to the set of the remote devices not in the partner class. The operating mode corresponding to the set of the remote devices not in the partner class follows a set of configuration parameters specific to the set of the remote devices not in the partner class. In an embodiment, the method further includes removing the partner device from the whitelist.

[0060] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, the method includes the analyte sensor system receiving a value of one of the configuration parameters from the partner device using the diabetes management partner interface. The method further includes the analyte sensor system modifying the one configuration parameter using the value received from the partner device.

[0061] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, the method includes the analyte sensor system sending the value of the configuration parameter to the display device. The value includes one or more of the following: a specified time after which the partner device is to be removed from a whitelist maintained for the analyte sensor system; and a specified time after which the display device is to be removed from the whitelist.

[0062] In certain embodiments of the third aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the third aspect, exchanging the wireless communication using the operating mode corresponding to the partner device includes one or more of the following: modifying a whitelist maintained for the analyte sensor system to turn off time slots of devices other than the partner device; and transmitting an advertisement message only for the partner device.

[0063] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, the method includes: if the connection request does not originate from the partner category, the analyte sensor system selecting an operating mode corresponding to a group of the remote devices that are not in the partner category. The operating mode corresponding to the group of remote devices that are not in the partner category uses a set of configuration parameters specific to the group of the remote devices that are not in the partner category.

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

[0065] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, exchanging the wireless communication using the operation mode corresponding to the partner category includes modifying the advertisement slot to advertise only for the partner device or the partner device controller.

[0066] In certain embodiments of the sixth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the sixth aspect, exchanging the wireless communication using the operation mode corresponding to the partner category includes: in response to a command received through the diabetes management partner interface, the analyte sensor system accepting connection requests received only from the partner device. The command may be received from the partner device.

[0067] 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 operatively coupled to a memory that stores instructions that, when executed, cause the analyte sensor system to perform a plurality of operations. One such operation is to determine whether a connection request received from one of the remote devices originates from a partner category within the one or more remote devices. The remote devices in the partner category are configured to provide a medicament. The partner category includes the partner device. Another such operation is to, if the connection request originates from the partner category, use the diabetes management partner interface to enable selection of an operation mode corresponding to the partner category. To support the system requirements of the partner device, the operation mode uses a set of configuration parameters of the partner category.

[0068] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to exchange the wireless communication with at least one of the remote devices using the operation mode corresponding to the partner category.

[0069] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the seventh aspect, the wireless communication exchanged using the operating mode corresponding to the partner category includes a mode indicator sent from the analyte sensor system to at least one of the remote devices. The mode indicator can be used by at least one of the remote devices to determine the operating mode being used.

[0070] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the seventh aspect, the set of configuration parameters for supporting the system requirements of the partner device includes one or more of the following: access control parameters for the display device or the partner device, accuracy parameters or calibration parameters of the analyte sensor system, and wireless communication parameters of the communication to be exchanged between the analyte sensor system and one or more of the remote devices.

[0071] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the seventh aspect, the mode indicator can be operated by the analyte sensor system to use the diabetes management partner interface to disable access by a set of remote devices not in the partner category to one or more of the access control parameters, the accuracy parameters or calibration parameters, and the wireless communication parameters. 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 parameters or calibration parameters, and the wireless communication parameters when the analyte sensor system uses an operating mode corresponding to the set of remote devices.

[0072] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments 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 to determine that the analyte sensor system has not received wireless communication from the partner device for at least a predetermined amount of time. Another such operation is to select an operating mode corresponding to the set of remote devices not in the partner category 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 category. The operating mode corresponding to the set of remote devices not in the partner category follows a set of configuration parameters specific to the set of remote devices not in the partner category.

[0073] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiment 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.

[0074] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiment 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 to receive, using the diabetes management partner interface, a value of one of the configuration parameters from the partner device. Another such operation is to modify the one configuration parameter with the value received from the partner device.

[0075] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to send the value of the configuration parameter to the display device. The value includes one or more of the following: a specified time after which the partner device is to be removed from the whitelist maintained for the analyte sensor system; and a specified time after which the display device is to be removed from the whitelist.

[0076] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiment 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 to modify the whitelist maintained for the analyte sensor system to close time slots for devices other than the partner device. Another such operation is to transmit an advertisement message only for the partner device.

[0077] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to: if the connection request does not originate from the partner category, select an operating mode corresponding to a set of the remote devices that are not in the partner category, wherein the operating mode corresponding to the set of the remote devices that are not in the partner category uses a set of configuration parameters specific to the set of the remote devices that are not in the partner category.

[0078] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the seventh aspect, the display device is not among the set of remote devices of the partner category, and wherein the memory further stores instructions that, when executed, cause the analyte sensor system to perform additional operations. One such operation is to provide, using the diabetes management partner interface, access to the set of configuration parameters specific to the set of remote devices that are not in the partner category to the display device. 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 category in response to an input received from the display device.

[0079] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to modify the advertising slots to advertise only to the partner devices or partner device controllers.

[0080] In certain embodiments of the seventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the seventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to: in response to a command received through the diabetes management partner interface, accept only connection requests received from the partner devices. The command may be received from the partner devices.

[0081] An eighth aspect of the present disclosure includes a method for the configurability of an analyte sensor system that uses a diabetes management interface to allow wireless communication with one or more of a partner device and a display device. The method includes the analyte sensor system determining that a first connection request has been sent from a remote device among the first class of remote devices. The analyte sensor system determines that a second connection request has been sent from a remote device among the second class of remote devices. The remote device among the second class of remote devices is configured to deliver a medicament. The remote device among 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 among the plurality of operating modes is specific to a first configuration that utilizes the remote devices among the second class of remote devices and does not utilize the remote devices among the first class of remote devices. A second operating mode among the plurality of operating modes is specific to a second configuration that does not utilize the devices among the second class of remote devices. A third operating mode among the plurality of operating modes is specific to a third configuration that utilizes the remote devices among the first class of remote devices and the remote devices among the second class of remote devices.

[0082] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, using the first operating mode of the plurality of operating modes includes providing the remote device in the second type of remote devices with the authority to modify the permissions provided to the remote device in the first type of remote devices using the diabetes management partner interface.

[0083] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, using the first operating mode of the plurality of operating modes further includes the analyte sensor system receiving, from the remote device in the first type of remote devices, authentication for the remote device in the second type of remote devices to communicate with the analyte sensor system.

[0084] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, using the first operating mode further includes: in response to an input received from the remote device in the second type of remote devices through the diabetes management partner device, the analyte sensor system blocking a connection with a device other than the remote device in the second type of remote devices.

[0085] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, blocking the connection includes advertising to the remote device in the second type of remote devices using a first advertising time slot. Blocking the connection also includes advertising to the remote device in the second type of remote devices or a controller of the remote device in the second type of remote devices using a second advertising time slot.

[0086] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, blocking the connection includes the analyte sensor system using the diabetes management partner interface to set an advertising structure or cause a modification to the advertising structure to include a single advertising duration dedicated to the remote device in the second type of devices.

[0087] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, blocking the connection includes the analyte sensor system only accepting connection requests from the remote device in the second type of remote devices.

[0088] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, using the first operating mode of the plurality of operating modes further comprises the analyte sensor system modifying a timeout rule associated with the remote device in the second type of remote device using an input received from the remote device in the second type of remote device via the diabetes management interface.

[0089] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, using the second operating mode of the plurality of operating modes comprises one or more of the following operations: modifying a whitelist to exclude the remote device in the second type of remote device; rejecting a connection request received from the remote device in the second type of remote device; and advertising only to remote devices in the first type of remote device.

[0090] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, using the third operating mode of the plurality of operating modes comprises the analyte sensor system receiving, via the diabetes management interface, an indication from the remote device in the second type of remote device of an access level to be granted to the remote device in the first type of remote device to the analyte sensor system.

[0091] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, the method comprises the analyte sensor system implementing the access level using the diabetes management interface. The method further comprises notifying the remote device in the first type of remote device of the access level.

[0092] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, the remote device in the first type of remote device is capable of receiving analyte data from the analyte sensor system but is not able to access accuracy parameters or calibration parameters of the analyte sensor system for the third operating mode.

[0093] 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 can be configured via a diabetes management partner interface. The analyte sensor system includes circuitry operatively coupled to a memory that stores instructions that, when executed, cause the analyte sensor system to perform a plurality of operations. One such operation is to determine that a first connection request has been sent from a remote device among a first class of remote devices. Another such operation is to determine that a second connection request has been sent from a remote device among a second class of remote devices. The remote device among the second class of remote devices is configured to deliver a medicament. The remote device among the first class of remote devices does not belong to the second class of remote devices. Another such operation is to use any of a plurality of operation modes. A first operation mode among the plurality of operation modes is specific to a first configuration that utilizes the remote device among the second class of remote devices without utilizing the remote device among the first class of remote devices. A second operation mode among the plurality of operation modes is specific to a second configuration that does not utilize the device among the second class of remote devices. A third operation mode among the plurality of operation modes is specific to a third configuration that utilizes the remote device among the first class of remote devices and the remote device among the second class of remote devices.

[0094] In certain embodiments that are generally applicable to the ninth aspect but are also particularly applicable in combination with any other embodiment of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to provide, in the first operation mode among the plurality of operation modes, to the remote device among the second class of remote devices, the authority to modify the permissions provided to the remote device among the first class of remote devices using the diabetes management partner interface.

[0095] In certain embodiments that are generally applicable to the ninth aspect but are also particularly applicable in combination with any other embodiment of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to receive, in the first operation mode among the plurality of operation modes, from the remote device among the first class of remote devices, the authentication for the remote device among the second class of remote devices to communicate with the analyte sensor system.

[0096] In certain embodiments of the ninth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system in the first operating mode of the plurality of operating modes: in response to an input received from the remote device in the second type of remote device via the diabetes management partner device, block connections with devices other than the remote device in the second type of remote device.

[0097] In certain embodiments of the eighth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eighth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system: advertise to the remote device in the second type of remote device using a first advertising time slot; and advertise to the remote device in the second type of remote device or the controller of the remote device in the second type of remote device using a second advertising time slot.

[0098] In certain embodiments of the ninth aspect that are generally applicable but also particularly applicable in combination with any other embodiments 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 set or cause a modification to an advertising structure to include a single advertising duration dedicated to the remote device in the second type of device.

[0099] In certain embodiments of the ninth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to accept connection requests only from the remote device in the second type of remote device.

[0100] In certain embodiments of the ninth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system in the first operating mode of the plurality of operating modes to modify a timeout rule associated with the remote device in the second type of remote device using an input received from the remote device in the second type of remote device via the diabetes management interface.

[0101] In certain embodiments of the ninth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to perform additional operations in the second operating mode among the multiple operating modes. One such operation is to modify the whitelist to exclude the remote device among the second type of remote devices. Another such operation is to reject connection requests received from the remote device among the second type of remote devices. Another such operation is to advertise only to the remote devices among the first type of remote devices.

[0102] In certain embodiments of the ninth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the ninth aspect, the memory further stores instructions, and the memory further stores instructions that, when executed, cause the analyte sensor system to receive, via the diabetes management interface, from the remote device among the second type of remote devices, an indication of an access level to be granted to the analyte sensor system for the remote device among the first type of remote devices in the third operating mode among the multiple operating modes.

[0103] In certain embodiments of the ninth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the ninth aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to: implement the access level using the diabetes management interface; and notify the remote device among the first type of remote devices of the access level.

[0104] In certain embodiments of the ninth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the ninth aspect, the remote device among the first type of remote devices can receive analyte data from the analyte sensor system but cannot access the accuracy parameters or calibration parameters of the analyte sensor system for the third operating mode.

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

[0106] In certain embodiments that are generally applicable to the tenth aspect but are also particularly applicable in combination with any other embodiments of the tenth aspect, establishing the second connection using the diabetes management partner interface occurs after the first connection has been terminated.

[0107] In certain embodiments that are generally applicable to the tenth aspect but are also particularly applicable in combination with any other embodiments of the tenth aspect, the method further includes: in response to the analyte sensor system receiving identification information of 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. 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 to the set of configuration parameters in response to an input received through the diabetes management partner interface. The third modification is performed according to the system requirements of the third partner device.

[0108] In certain embodiments that are generally applicable to the tenth aspect but are also particularly applicable in combination with any other embodiments of the tenth aspect, the identification information of the third partner device is stored in a server system. In an example, the identification information indicates whether the third partner device is authorized to communicate with the analyte sensor system.

[0109] In certain embodiments of the tenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the tenth aspect, the analyte sensor system receiving the identification information of the third partner device comprises the analyte sensor system receiving the identification information of the third partner device from a display device that receives the identification information of the third partner device from the server system.

[0110] In certain embodiments of the tenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the tenth aspect, the method comprises additional operations. One such operation involves using the identification information of the third partner device to determine whether the third partner device is authorized to communicate with the analyte sensor system in response to the analyte sensor system receiving the identification information of the third partner device. Another such operation involves rejecting an 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. Another such operation involves 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.

[0111] In certain embodiments of the tenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments 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 an example, determining that the third partner device is authorized to communicate with the analyte sensor system occurs at a second time. The identification information of the third partner device may be updated on the server system between the first time and the second time.

[0112] In certain embodiments of the tenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the tenth aspect, the system requirements of the third partner device are stored in the server system. The method further comprises causing a fourth modification to the set of configuration parameters in response to an input received through the diabetes management partner interface. The fourth modification is made according to an updated version of the system requirements of the third partner device.

[0113] The eleventh aspect of the present disclosure includes an analyte sensor system that uses a diabetes management interface to facilitate the exchange of wireless communications. The analyte sensor system includes circuitry operatively coupled to a memory that stores instructions that, when executed, cause the analyte sensor system to perform a plurality of operations. One such operation is to establish a first connection between the analyte sensor system and a first partner device using the diabetes management partner interface. Another such operation is to provide access to a set of configuration parameters to the first partner device through the diabetes management interface. Another such operation is to set the set of configuration parameters or cause a first modification to the set of configuration parameters in response to an input received from the first partner device through the diabetes management partner interface. The first modification is made according to the system requirements of the first partner device. Another such operation is to establish a second connection between the analyte sensor system and a second partner device using the diabetes management partner interface. Another such operation is to provide access to the set of configuration parameters to the second partner device through the diabetes management interface. Yet another such operation is to cause a second modification to the set of configuration parameters in response to an input received from the second partner device through the diabetes management partner interface. The second modification is made according to the system requirements of the second partner device.

[0114] In certain embodiments that are generally applicable to the eleventh aspect but are also particularly applicable in combination with any other embodiment of the eleventh aspect, the second connection is established after the first connection has been terminated.

[0115] In certain embodiments that are generally applicable to the eleventh aspect but are also particularly applicable in combination with any other embodiment 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 to receive identification information of a third partner device. Another such operation is to attempt to establish a third connection between the analyte sensor system and the third partner device using the diabetes management partner interface in response to the received identification information of the third partner device. Another such operation is, in response to the third connection established between the analyte sensor system and the third partner device, to cause a third modification to the set of configuration parameters in response to an input received through the diabetes management partner interface. The third modification is made according to the system requirements of the third partner device.

[0116] In certain embodiments of the eleventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eleventh aspect, the identification information of the third partner device is stored in the server system. The identification information indicates whether the third partner device is authorized to communicate with the analyte sensor system.

[0117] In certain embodiments of the eleventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the eleventh aspect, the memory further stores instructions that, when executed, cause the analyte sensor system to receive the identification information of the third partner device from a display device that has received the identification information of the third partner device from the server system.

[0118] In certain embodiments of the eleventh aspect that are generally applicable but also particularly applicable in combination with any other embodiments 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 to use the identification information of the third partner device to determine whether the third partner device is authorized to communicate with the analyte sensor system in response to the received identification information of the third partner device. Another such operation is to reject an attempt to establish the third connection between the analyte sensor system and the third partner device in response to a determination that the third partner device is not authorized to communicate with the analyte sensor system. Another such operation is to establish the third connection between the analyte sensor system and the third partner device using the diabetes management partner interface in response to a determination that the third partner device is authorized to communicate with the analyte sensor system.

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

[0120] In certain embodiments that are generally applicable to the eleventh aspect but are also particularly applicable in combination with any other embodiment of the eleventh aspect, the system requirements of the third partner device are stored in a server system. The memory further stores instructions that, when executed, cause the analyte sensor system to effect a fourth modification to the set of configuration parameters in response to an input received through the diabetes management partner interface. The fourth modification is made in accordance with an updated version of the system requirements of the third partner device.

[0121] A twelfth aspect of the present disclosure includes a method. The method includes an analyte sensor system receiving an indication of an operating mode specific to the 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 an input received from the partner device through a diabetes management partner interface. The input received from the partner device indicates corresponding operating parameters that the partner device will use to communicate with the analyte sensor system using the operating mode. The configuration parameters are configured in accordance with the system requirements of the partner device. The method also includes implementing the operating mode specific to the use of the partner device using the operating parameters of the analyte sensor system such that the system requirements of the partner device are accommodated.

[0122] In certain embodiments that are generally applicable to the twelfth aspect but are also particularly applicable in combination with any other embodiment of the twelfth aspect, the configuration parameters include one or more of the following: a permission parameter for a display device to issue commands or control signals for initiating, stopping, calibrating, or setting the length of a sensor session of the analyte sensor system; battery or power management parameters; connection model parameters; timeout parameters, where one or more of the timeout parameters relate to the length of time for which the partner device is to remain on a whitelist, advertisement timeout, connection establishment timeout, and authorization timeout; alert parameters; configuration settings that control the operating mode of the analyte sensor system; and remote server parameters.

[0123] In certain embodiments that are generally applicable to the twelfth aspect but are also particularly applicable in combination with any other embodiment of the twelfth aspect, the method further includes the analyte sensor system receiving an indication to effect a transition from the operating mode specific to the use of the partner device. Additionally, the method includes the analyte sensor system restoring the configuration parameters to a previous state that existed prior to setting or modifying the configuration parameters in response to the input received from the partner device. Restoring the set of configuration parameters to the previous state may include removing the partner device from the whitelist.

[0124] The 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. The method further includes: if the wireless communication system includes the display device, the analyte sensor system determining whether to connect to the display device using one of an intermittent connection model and a continuous connection model. The method further includes: if the system includes the partner device, the analyte sensor system determining whether to connect to the partner device using one of the intermittent connection model and the continuous connection model. The analyte sensor system determining which of the intermittent connection model or the continuous connection model will be used to connect to one or more of the display device and the partner device includes using configuration parameters that have been set or modified using inputs received from the partner device via a diabetes management partner interface.

[0125] In certain embodiments that are generally applicable to the thirteenth aspect but are also particularly applicable in combination with any other embodiment of the thirteenth aspect, the analyte sensor system determines that connecting to the partner device according to the intermittent connection model is performed using one of the configuration parameters set in response to the power requirements of the partner device.

[0126] In certain embodiments that are generally applicable to the thirteenth aspect but are also particularly applicable in combination with any other embodiment of the thirteenth aspect, the analyte sensor system determines that connecting to the partner device according to the continuous connection model is performed using the determination that the system includes the display device.

[0127] The fourteenth aspect of the present disclosure includes a method. The method includes an analyte sensor application of a display device receiving an interface of 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 dose data. The method further 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 the following: the analyte sensor system is operating; the connection model employed by the analyte sensor system with respect to the partner device or the display device; the configuration parameters used by the analyte sensor system to communicate with one or more of the partner device and the display device.

[0128] In certain embodiments of the fourteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments 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 the information collected by the partner device application.

[0129] In certain embodiments of the fourteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fourteenth aspect, the method also includes the analyte sensor application receiving information about an analyte value from the analyte sensor system. The method also includes the analyte sensor application using the interface to transmit the analyte value to the partner device via the partner device application.

[0130] In certain embodiments of the fourteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fourteenth aspect, the method also includes the analyte sensor application receiving, via the interface, medication delivery information collected by the partner device.

[0131] In certain embodiments of the fourteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fourteenth aspect, the method also includes the analyte sensor application receiving an alert from the partner device via the interface. The alert is related to a functional problem of the partner device.

[0132] In certain embodiments of the fourteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fourteenth aspect, the method also includes the analyte sensor application of the display device causing the alert to be provided via a user interface.

[0133] In certain embodiments of the fourteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiments of the fourteenth aspect, the method also includes the analyte sensor application of the display device causing the alert to be provided via a remote server.

[0134] The fifteenth aspect of the present disclosure includes a method. The method includes establishing a connection between the analyte sensor system and the 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 is related to the operation of the analyte sensor system according to the system requirements of the partner device. The configuration parameter information may include the extent of access to be given to a remote device capable of connecting to the analyte sensor system. The configuration parameter information may include one or more values of a set of configurability parameters for the connection established between the analyte sensor system and the partner device. The one or more values of the set of configurability parameters are selected according to the system requirements of the partner device.

[0135] In certain embodiments that are generally applicable to the fifteenth aspect but are also particularly applicable in combination with any other embodiment of the fifteenth aspect, the set of configurability parameters includes one or more of the following. The set of configurability parameters may include connection information of the remote device. The set of configurability parameters may include a connection model to be used for a specific device capable of connecting to the analyte sensor system. The set of configurability parameters may include connection command-related data to be read by or sent to the remote device. The set of configurability parameters may include information related to not using the partner device. The set of configurability parameters may include security-related parameters or privacy-related parameters. The set of configurability parameters may include information related to power control or battery usage. The set of configurability parameters may include multiple devices that can be connected to the analyte sensor system. The set of configurability parameters may include the device type of each device that can be connected to the analyte sensor system. The set of configurability parameters may include the type of information related to analyte data that can be read by and sent to a remote device capable of connecting to the analyte sensor system.

[0136] In certain embodiments that are generally applicable to the fifteenth aspect but are also particularly applicable in combination with any other embodiment of the fifteenth aspect, the connection command-related data indicates one or more of the following. The connection command-related data may indicate whether the partner device or the remote device is eligible to be included in the whitelist of the analyte sensor system. The connection command-related data may indicate whether the partner device or the remote device is debugged to age off from the whitelist. If the partner device or the remote device is debugged to age off from the whitelist, the connection command-related data may indicate the amount of time before the partner device or the remote device is set to age off from the whitelist.

[0137] In certain embodiments of the fifth aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the fifth aspect, the information related to power control includes a recommendation to deactivate a particular device to extend the battery life of the analyte sensor system.

[0138] In certain embodiments of the fifteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the fifteenth aspect, the information related to power control or battery usage is collected by a control mechanism that balances the battery life of the analyte sensor system and the connection reliability between the analyte sensor system and the partner device or the remote device.

[0139] In certain embodiments of the fifteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the fifteenth aspect, the information related to power control triggers a low-power mode of the analyte sensor system.

[0140] In certain embodiments of the fifteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the fifteenth aspect, the access level is received only after the analyte sensor system has received authorization to modify the access level using the parameter information received from the partner device.

[0141] 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 further includes the display device receiving an indication that the analyte sensor system is connecting to a partner device. The method also includes receiving, after receiving authorization to provide access to a set of configuration parameters to the partner device through a diabetes management partner interface, the configuration parameters of an alert originating from the partner device through the diabetes management partner interface. The method further includes the display providing a user interface device for configuring the alert originating from the analyte sensor system and the alert originating from the partner device. The method further includes using an input received through the user interface to cause a modification to the configuration parameters of the alert originating from the partner device. The modification is made according to the system requirements of the partner device.

[0142] In certain embodiments of the sixteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the sixteenth aspect, a selection of the partner device or a remote device that includes the display device among a plurality of remote devices is received through the user interface, and the remote device is 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.

[0143] In certain embodiments of the sixteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the sixteenth aspect, the method further includes providing the alert on a device external to the primary device when the battery capacity of the primary device drops below a threshold.

[0144] In certain embodiments of the sixteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the sixteenth aspect, the method further includes the display device receiving, via the user interface, a selection of a respective alert type to be provided for the alert from the partner device and the alert from the analyte sensor system.

[0145] In certain embodiments of the sixteenth aspect that are generally applicable but also particularly applicable in combination with any other embodiment of the sixteenth aspect, the method further includes providing the alert via a primary notification device. The method further includes: providing the alert via a secondary notification device if an acknowledgement is not 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 the partner device, the analyte sensor system, and / or the plurality of remote devices.

[0146] The sixteenth aspect of the present disclosure includes a method for monitoring an operability state of a medicament delivery device. Medicament delivery device information related to one or more of the following is received from the medicament delivery device. The medicament delivery device information may relate to reservoir changes. The medicament delivery device information may relate to pump reset. The medicament delivery device information may relate to pump priming. The medicament delivery device information may relate to cannula filling. The medicament delivery device information may relate to fluid pressure. The medicament delivery device information may relate to determining a combination of the medicament delivery device information and analyte data generated using the analyte sensor system. The medicament delivery device information may relate to the analyte sensor system using the combination to determine the operability state of the medicament delivery device. BRIEF DESCRIPTION OF THE DRAWINGS

[0147] Additional aspects of the present disclosure will be more readily understood when the detailed description of the various disclosed embodiments described below is read in conjunction with the accompanying drawings.

[0148] Figure 1 Aspects of an example system that may be used in conjunction with embodiments of the present disclosure are shown.

[0149] Figure 2A Aspects of an example system that may be used in conjunction with embodiments of the present disclosure are shown.

[0150] Figure 2BShows aspects of an example system that can be used in conjunction with embodiments of the present disclosure.

[0151] Figure 3A Is a perspective view of an example housing that can be used in conjunction with embodiments of an analyte sensor system.

[0152] Figure 3B Is a side view of an example housing that can be used in conjunction with embodiments of an analyte sensor system.

[0153] Figure 3C Shows aspects of an example analyte sensor system according to an embodiment of the present disclosure.

[0154] Figure 4 Shows aspects of an example display device according to an embodiment of the present disclosure.

[0155] Figure 5A Shows aspects of an example partner device according to an embodiment of the present disclosure.

[0156] Figure 5B Shows aspects of an example partner device according to an embodiment of the present disclosure.

[0157] Figure 6 Is a timing diagram showing aspects of an advertising message that can be transmitted according to an embodiment of the present disclosure.

[0158] Fig. 7A Is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0159] Figure 7B Is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0160] Figure 7C Is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0161] Fig.7D Shows aspects of an example system that can be used in conjunction with embodiments of the present disclosure.

[0162] Figure 8 Shows aspects of an example system that can be used in conjunction with embodiments of the present disclosure.

[0163] Fig.9A Shows aspects of an example system that can be used in conjunction with embodiments of the present disclosure.

[0164] Fig. 9B Is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0165] Fig. 9CIt is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0166] Fig.9D It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0167] Fig.9E It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0168] Fig.9F It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0169] Figure 9G It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0170] Figure 9H It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0171] Figure 9J It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0172] Figure 9K It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0173] Figure 9L It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0174] Figure 9M It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0175] Figure 9N It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0176] Figure 9P It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0177] Figure 9Q It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0178] Figure 9R It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0179] Figure 9S It is an operation flowchart showing various operations that can be performed according to an embodiment of the present disclosure.

[0180] Fig. 10A Shows aspects of an example system that can be used in conjunction with embodiments of the present disclosure.

[0181] Fig. 10B Shows aspects of an example system that can be used in conjunction with embodiments of the present disclosure.

[0182] Fig.11 Shows an example computing module in accordance with embodiments of the present disclosure.

[0183] These drawings are described in more detail in the following description and examples. The drawings are provided for illustrative purposes only and depict typical or example embodiments of the present disclosure. These drawings are not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. It should also be understood that the present disclosure may be practiced with modifications or variations, and the present disclosure may be limited only by the claims and their equivalents. Detailed Description

[0184] Embodiments of the present disclosure relate to systems, methods, and apparatuses for wirelessly transmitting analyte data, and interfaces for wirelessly transmitting 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. Implementing aspects of the present disclosure (more specifically, including the systems, methods, devices, and apparatuses using the diabetes management partner interface described herein) can improve the flexibility of the analyte sensor system in wireless communication with a display device, one or more partner devices, and / or other (e.g., electronic) devices.

[0185] In addition, implementing aspects of the present disclosure can also allow for improved performance in terms of the reliability, speed, and accuracy of wireless communication (including with respect to partner devices and display devices (e.g., where the foregoing devices may be manufactured by different third parties)), as well as the connection protocols and configurations associated therewith. Further, in some cases, system requirements (such as those related to accuracy, power consumption, or reliability) may be less critical, and in these cases, different configurations and connection modes can be employed to optimize or adjust system performance. Specifically, some aspects of the present disclosure relate to setting or modifying the connectivity parameters of an analyte sensor system based on factors such as the system requirements of a partner device.

[0186] Details of some example embodiments of the systems, methods, and apparatuses of the present disclosure are set forth in this specification, and in some cases, details of some example embodiments of the systems, methods, and apparatuses of the present disclosure are set forth in other parts of the present disclosure. Other features, objects, and advantages of the present disclosure will be apparent to those skilled in the art upon study of the present disclosure, the specification, the drawings, the examples, and the claims. It is intended that all such additional systems, methods, apparatuses, features, and advantages be included in this specification (either explicitly or by reference), be included within the scope of the present disclosure, and be protected by one or more of the appended claims.

[0187] A. System Overview and Example Configuration

[0188] Figure 1 System 100 is depicted that can be used in conjunction with embodiments of the present disclosure and relates to collecting, monitoring, and / or providing information regarding analyte values present in a user's body, including, for example, the user's blood glucose value. System 100 depicts aspects of an analyte sensor system 8 that can be communicatively coupled to display devices 110, 120, 130, and 140, a partner device 136, and / or a server system 134.

[0189] The analyte sensor system 8 in the illustrated embodiment includes a sensor electronics module 12 and a continuous analyte sensor 10 associated with the sensor electronics module 12. The sensor electronics module 12 can communicate wirelessly (e.g., directly or indirectly) with one or more of the display devices 110, 120, 130, and 140. In addition to or alternatively to the display devices 110, 120, 130, and 140, the sensor electronics module 12 can communicate wirelessly (e.g., directly or indirectly) with the partner device 136 and / or the server system 134. Also, in some instances, the display devices 110 - 140 can additionally or alternatively communicate wirelessly (e.g., directly or indirectly) with the partner device 136 and / or the server system 134. Figure 1 The various couplings shown therein can be achieved through a wireless access point 138, as described below.

[0190] In some embodiments, the sensor electronics module 12 includes electronic circuitry related to measuring and processing continuous analyte sensor data, including expected algorithms related to the processing and calibration of the sensor data. The sensor electronics module 12 can be physically connected to the continuous analyte sensor 10 and can be integrated with the continuous analyte sensor 10 (non - releasably attached thereto) or releasably attached to the continuous analyte sensor. The sensor electronics module 12 can include hardware, firmware, and / or software that enables the measurement of analyte levels via a glucose sensor. For example, the sensor electronics module 12 can include a potentiostat, a power source for powering the sensor, other components for signal processing and data storage, and a telemetry module for transmitting data from the sensor electronics module to one or more devices. The electronics can be fixed to a printed circuit board (PCB) or the like and can take various 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).

[0191] The sensor electronics module 12 can 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. Patent Nos. 7,310,544 and 6,931,327 and U.S. Patent Publications 2005 / 0043598, 2007 / 0032706, 2007 / 0016381, 2008 / 0033254, 2005 / 0203360, 2005 / 0154271, 2005 / 0192557, 2006 / 0222566, 2007 / 0203966, and 2007 / 0208245, and these patents and patent publications are incorporated herein by reference in their entirety.

[0192] Further reference Figure 1, the display devices 110, 120, 130, and / or 140 may be configured to display (and / or alert) displayable sensor information that may be transmitted by the sensor electronics module 12 (e.g., in a customized data packet transmitted to the display device based on the respective preferences of the display device). Each of the display devices 110, 120, 130, or 140 may (respectively) include a display (such as touchscreen displays 112, 122, 132, and / or 142) for displaying sensor information and / or analyte data to the user and / or receiving input from the user. For example, for these purposes, a graphical user interface may be presented to the user. In an embodiment, instead of or in addition to the touchscreen display, the display device may include other types of user interfaces (such as a voice user interface) for transmitting sensor information to the user of the display device and / or receiving user input. In an embodiment, one, some, or all of the display devices 110, 120, 130, 140 may be configured to display or otherwise transmit the sensor information (e.g., in a data packet transmitted to the respective display device) without any additional expected processing required for calibration and real-time display of the sensor data when the sensor information is transmitted from the sensor electronics module 12.

[0193] Figure 1 The multiple display devices 110, 120, 130, 140 depicted in [FIGURE REFERENCE] may include customized display devices (e.g., analyte display device 110) that are specifically designed to display certain types of displayable sensor information (e.g., numerical values and / or arrows in an embodiment) associated with analyte data received from the sensor electronics module 12. In an embodiment, one of the multiple display devices 110, 120, 130, 140 includes a smart phone (such as mobile phone 120) based on Android, iOS, or other operating systems and configured to display a graphical representation of continuous sensor data (e.g., including current data and / or historical data). The other display devices 110, 120, 130, 140 may include other handheld devices, such as tablet computers 130, smart watches 140, partner devices 136 (e.g., automatic or manual insulin delivery devices or blood glucose meters), smart refrigerators, vehicles, smart mirrors, smart clocks, smart beverages, implantable insulin delivery devices, and / or desktop or laptop computers.

[0194] Because the display devices 110, 120, 130, 140, etc. are different and one or more partner devices 136 can provide different user interfaces, the content of the data packets of each specific display device 110, 120, 130, 140, etc. and / or one or more partner devices 136 (e.g., the amount, format, and / or type of data to be displayed, alerts, etc.) can be customized (e.g., programmed differently by the manufacturer and / or the end user). Thus, in an embodiment, a plurality of different display devices 110, 120, 130, 140 can communicate directly wirelessly with the sensor electronics module 12 (e.g., a skin sensor electronics module physically connected to the continuous analyte sensor 10) during a sensor session to implement a plurality of different types and / or levels of display and / or functionality associated with the sensor information that can be displayed, which is described in more detail elsewhere herein.

[0195] As further shown and mentioned above in Figure 1 the system 100 may also include a wireless access point (WAP) 138, which can be used to couple one or more of the analyte sensor system 8, the plurality of display devices 110, 120, 130, 140, etc., the server system 134, and the medical device 136 to each other. For example, the WAP 138 may provide WiFi and / or cellular or other wireless connectivity within the system 100. Near field communication (NFC) may also be used between the devices of the system 100. The server system 134 can be used to collect analyte data from the analyte sensor system 8 and / or the plurality of display devices, for example, to perform analysis on it, generate general or personalized models of glucose levels and profiles, provide services or feedback (including services or feedback from individuals or systems remotely monitoring the analyte data), etc.

[0196] Now referring to Figure 2A system 200 is described. System 200 can be used in conjunction with embodiments implementing the disclosed systems, methods, devices, and / or apparatuses, including, for example, the aspects described above in connection with Figure 1 For example, Figure 2A the various components described below in

[0197] As Figure 2AAs shown, 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 in turn includes a server 334a coupled to a processor 334c and a memory 334b. The analyte sensor system 308 may be coupled to the display device 310, the partner device 315, and / or the server system 334 via a communication medium 305. Many details of the analyte sensor system 308, the partner device 315, and / or the display device 310, etc., for processing, collecting, and exchanging data and / or performing actions (such as providing a medicament or related instructions) are described below.

[0198] As will be described in detail herein, the analyte sensor system 308, the display device 310, and / or the partner device 315 may exchange information transceiver (such as control signaling) via the communication medium 305, and the communication medium 305 may also be used to deliver analyte data to the display device 310, the partner device 315, and / or the server system 334. As described above, the display device 310 may include various electronic computing devices, such as, for example, a smart phone, a tablet computer, a laptop computer, a wearable device, etc. The display device 310 may also include an analyte display device 110 customized for displaying and transmitting analyte data and related notifications, etc. The partner device 315 may include medical devices (such as an insulin pump or an insulin pen), connectable devices (such as a smart refrigerator or a smart mirror, a remote control key), and other devices.

[0199] In an embodiment, the communication medium 305 may be based on one or more wireless communication protocols (such as Bluetooth, Bluetooth Low Energy (BLE), ZigBee, WiFi, IEEE 802.11 protocol, infrared (IR), radio frequency (RF), 2G, 3G, 4G, 5G, etc.) and / or wired protocols and media. After studying this disclosure, it will also be understood that the communication medium may be implemented as one or more communication links (in some cases including separate links) between components of the system 200, regardless of whether such links are Figure 2A explicitly shown or mentioned in connection therewith. For 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 via a second link of the communication medium 305 using a cellular communication protocol (such as, for example, 4G LTE).

[0200] In an embodiment, the components of system 200 can be used to perform the operations of the various processes described herein and / or can be used to perform the various operations and / or features described herein with respect to one or more disclosed systems and / or methods. After studying this disclosure, those skilled in the art will understand that system 200 can include a single or multiple analyte sensor systems 308, communication medium 305, and / or server system 334.

[0201] As described above, communication medium 305 can be used to connect or communicatively couple analyte sensor system 308, display device 310, partner device 315, and / or server system 334 to each other or to a network. Communication medium 305 can be implemented in a variety of forms. For example, communication medium 305 can include one or more Internet connections, such as a local area network (LAN), personal area network (PAN), wide area network (WAN), fiber optic network, power line Internet, hardwired connection (e.g., a bus), DSL, etc., or any other type of network connection or communication coupling. Communication medium 305 can be implemented using any combination of routers, cables, modems, switches, fiber optics, wires, radios (e.g., microwave link / RF link, AM link, FM link, etc.), etc. Additionally, communication medium 305 can be implemented using various wireless standards, such as BLE, Wi-Fi, IEEE802.11, 3GPP standards (e.g., 2G GSM / GPRS / EDGE, 3G UMTS / CDMA2000, or 4G LTE / LTE-A / LTE-U, 5G, or a subsequent generation), etc. After reading this disclosure, those skilled in the art will recognize other ways to implement communication medium 305 for communication purposes and will also recognize that communication medium 305 can be used to implement the features of this disclosure using communication protocols that have not yet been developed and that may be deployed in the future.

[0202] Further referring to Figure 2A , server 334a can receive, collect, and / or monitor information (including analyte data, reagent data, and related information) from analyte sensor system 308, partner device 315, and / or display device 310, such as in response to an input of analyte data or reagent data, or in conjunction with an analyte monitoring application running on analyte sensor system 308 or display device 310 (e.g., referring to Figure 4 , analyte application sensor application 425a) or running on display device 310 or partner device 315 (e.g., reagent delivery device 625, referring to Figure 5B) Input received by the pharmaceutical delivery application on. In this way, the server 334a can receive, collect, and / or monitor information (such as information related to providing pharmaceuticals to the user and / or information related to the operation of one or more partner devices 315). The server 334a can also receive, collect, and / or monitor information about the users of the analyte sensor system 308, the display device 310, and / or the partner device 315.

[0203] In an embodiment, the server 334a can be configured to receive such information via the communication medium 305. Such information can be stored in the storage device 334b and processed by the processor 334c. For example, the processor 334c can include an analysis engine capable of performing an analysis on the information that the server 334a has collected, received, etc. via the communication medium 305. In an embodiment, the server 334a, the memory 334b, and / or the processor 334c can be implemented as a distributed computing network, such as Or can be implemented as a relational database, etc. Then, the above information can be processed at the server 334a so that services can be provided to the analyte sensor system 308, the display device 310, and / or the partner device 315 and / or one or more of their users. For example, such services can include diabetes management feedback for the user.

[0204] Server 334a can include, for example, an Internet server, a router, a desktop or laptop computer, a smart phone, a tablet computer, a processor, a module, etc., and can be implemented in various forms, including, for example, an integrated circuit or a collection thereof, a printed circuit board or a collection thereof, or implemented in a discrete housing / enclosure / rack or a plurality thereof. In an embodiment, server 334a at least partially guides communications carried out via communication medium 305. Such communications can include analyte data, reagent data, and / or messaging associated therewith (e.g., advertisements, authentication, commands, or other messaging). For example, server 334a can process and exchange messages related to frequency bands, transmission timing, security / encryption, alerts, notifications, etc. between analyte sensor system 308, display device 310, and / or partner device 315. Server 334a can update information stored on analyte sensor system 308, partner device 315, and / or display device 310, for example, by delivering an application or updating an application to analyte sensor system 308, partner device 315, and / or display device 310 and / or by reconfiguring system parameters or other settings of the analyte sensor system, the partner device, and / or the display device. Server 334a can send / receive information to / from analyte sensor system 308, partner device 315, and / or display device 310 in real time, periodically, sporadically, or on an event-driven basis. In addition, server 334a can implement cloud computing capabilities for analyte sensor system 308, partner device 315, and / or display device 310.

[0205] Turning now to Figure 2B , an embodiment in accordance with the present disclosure depicts system 202, some embodiments of which relate to configuring and / or establishing a mesh network for connecting various devices described herein. As shown, an embodiment of system 202 includes analyte sensor system 308, which is communicatively coupled via communication medium 305 to one or more of display devices 310a, 310b, and / or partner device 315. Display device 310a can also be communicatively coupled to display device 310b via communication medium 305a. As an example, Figure 2BIllustrated is that in an example implementation of the present disclosure, the display device 310a can be connected to the analyte sensor system 308 via a communication medium 305 using a first connection scheme and a first wireless protocol (e.g., BLE). Further, the display device 310a can also be connected to the display device 310b via a communication medium 305a using a second connection scheme and a second wireless protocol (e.g., Wi-Fi, NFC, etc.). In an embodiment, the connection between the display device 310a and the analyte sensor system 308 can be subsequently closed, and the display device 310b can establish a connection with the analyte sensor system 308 while maintaining the connection with the display device 310a. Additionally, for example, the display devices 310a and 310b can exchange analyte data with each other via the communication medium 305a, where any one or each of the display devices 310a, 310b receives analyte data via the communication medium 305, i.e., receives analyte data from the analyte sensor system 308.

[0206] The partner device 315 can also be connected to the display device 310b via the communication medium 305 and / or the communication medium 305b. The partner device 315 can also be connected to the analyte sensor system 308 via the communication medium 305. It should be understood that any number of different connection schemes / protocols can be employed to communicatively couple the components of the system 202. For example, some network connections may be intermittently available, and / or may be unavailable or not preferred in certain situations (due to device capabilities, geographical location, time, system conditions (such as battery life or interference requirements, etc.)). Thus, in some cases, the partner device 315 may not be directly connected to the analyte sensor system 308, but instead may be indirectly connected to the analyte sensor system via the display device 310b that can be connected to the analyte sensor system 308 via the communication medium 305. In some cases, the display device 310b may not be directly connected to the analyte sensor system 308, but instead may be indirectly connected to the analyte sensor system via the partner device 315 that can be connected to the analyte sensor system 308 via the communication medium 305. After studying the entirety of the present disclosure, additional aspects and features represented by Figure 2B will become apparent.

[0207] In an embodiment, the partner device 315 may not support the communication protocol used by the analyte sensor system 308, and / or in other respects it may not be preferred for the partner device 315 to be directly connected to the analyte sensor system 308. Thus, the display device 310 (which in the example supports the communication protocol used by the analyte sensor system 308 and / or may be more preferably used in other respects for connection to the analyte sensor system 308) can be connected to the analyte sensor system 308 and substantially act as a gateway device for the partner device 315. In this way, the partner device 315 can indirectly receive analyte data etc. from the analyte sensor system 308, and / or can exchange information therewith. In some cases, this may be referred to as data sharing. It should also be understood that in some cases, the partner device 315 can act as a gateway device for the display devices 310a, 310b, such that the display devices 310a, 310b can be tethered and can receive analyte data from the analyte sensor system 308 via the partner device 315. It should also be understood that in the example implementation of the system 304, one or more of the display devices 310a, 310b can be connected to the analyte sensor system 308 in parallel with each other and / or in parallel or in series with one or more partner devices 315. Each display device 310a, 310b and / or partner device 315 can also have a chain of display devices 310a, 310b and / or partner devices 315 connected thereto.

[0208] As described above, analyte-related data, reagent-related data, and other messaging or information (e.g., control signal messaging, etc.) can be transmitted and received 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 using a wireless communication protocol. In an embodiment, such wireless protocols can be designed for optimizing a wireless network for periodic and small data transmissions (which can be transmitted at a low rate if necessary) to and from multiple devices in close proximity (e.g., a personal area network). For example, one such protocol can be optimized for periodic data transmission, where the transceiver can be configured to transmit data at shorter time intervals and then enter a low power mode at longer time intervals. The protocol may have low overhead requirements for normal data transmission and for initially establishing a communication channel (e.g., by reducing overhead) to reduce power consumption. In some embodiments, a burst broadcast scheme (e.g., one-way communication) can be used. This can eliminate the overhead required for acknowledgment signals and allow for periodic transmissions with less power consumption. In other embodiments, a proximity-based protocol, either passive or active, can be employed to reduce overhead (e.g., the overhead associated with typical pairing operations) and / or increase security, where NFC is a specific example.

[0209] The protocol can also be configured to establish communication channels with multiple devices while implementing an interference avoidance scheme. In some embodiments, the above example protocol can utilize an adaptive isochronous network topology that defines various time slots and frequency bands for communicating with several devices. Thus, the protocol can modify the transmission window and frequency in response to interference and support communication with multiple devices. Therefore, the wireless protocol can use a time-division and frequency-division multiplexing (TDMA / FDMA)-based scheme. The wireless protocol can also employ direct sequence spread spectrum (DSSS) and frequency hopping spread spectrum schemes. Various networks can be used to support short-range and / or low-power wireless communication, such as peer-to-peer, star, tree, or mesh network topologies, such as WiFi, Bluetooth, and BLE. The wireless protocol can operate in different frequency bands, such as, for example, the open ISM band, such as 2.4 GHz. Additionally, to reduce power consumption, the wireless protocol can adaptively configure the data rate based on power consumption.

[0210] In embodiments related to the configuration shown in Figure 2B the user interface (such as the GUI provided by Figure 4 user interface 435 in

[0211] can present information about the mesh network to the user such that the user can maintain a certain degree of control over and / or input to the configuration of the network. For example, the topology / topologies of the mesh network can be provided, and the user can be enabled to access connection links to change the connection model employed, the connectivity parameters used, and / or the advertising characteristics associated with various connections, etc. Additionally, the user can switch between the display device 310 and / or the partner device 315 based on which device can act as a gateway to other devices. Additionally, the user, the analyte sensor system 308, the display device 315, and / or the partner device 315 can send control signal transmissions to other networked elements to manage the permissions / capabilities of other connected devices and / or manage the number / type of devices that can be connected to the analyte sensor system 308, etc. In an embodiment, the display device 310 and / or the partner device 315 can manage the network topology / configuration in an automated manner based on, for example, the system requirements of the partner device 315. To facilitate such automated or semi-automated management, the partner device 315 can access mesh network configuration information through the diabetes management partner interface as described herein.

[0212] B. Analyte Data

[0213] Reference return Figure 1 As described above, in an embodiment, an analyte sensor system 8 is provided for continuously measuring an analyte in a host or user. Generally and by way of example, the analyte sensor system 8 can be implemented as an encapsulated microcontroller that makes sensor measurements, generates analyte data (e.g., by calculating values of continuous glucose monitoring data), and performs wireless communication (e.g., via Bluetooth and / or other wireless protocols) to send such data to a remote device (e.g., display devices 110, 120, 130, 140, partner device 136, and / or server system 134).

[0214] The analyte sensor system 8 can include: a continuous analyte sensor 10 configured to continuously measure the analyte concentration in a host; and a sensor electronics module 12 that is generally physically connected to the continuous analyte sensor 10 during sensor use. In an embodiment, the 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 produce sensor information that includes, for example, raw sensor data, transformed sensor data, and / or any other sensor data. The sensor electronics module 12 can also be configured to generate sensor information customized for the respective display devices 110, 120, 130, 140, partner device 136, and / or server system 134. The sensor electronics module 12 can be further configured such that different devices can receive different sensor information and can be further configured to wirelessly transmit the sensor information to these display devices 110, 120, 130, 140, partner device 136, and / or server system 134.

[0215] As used herein, the term "analyte" is a broad term and has its ordinary and customary meaning to one of ordinary skill in the art (and is not limited to a special or customized meaning), and further refers to, but is not limited to, substances or chemical components in a biological fluid that can be analyzed (e.g., blood, interstitial fluid, cerebrospinal fluid, lymphatic fluid, or urine). An analyte can include natural substances, artificial substances, metabolites, and / or reaction products. In some embodiments, the analyte measured by the sensor head, device, and method is glucose. However, other analytes are also contemplated, including but not limited to acarbose; acylcarnitine; adenine phosphoribosyltransferase; adenosine deaminase; albumin; alpha-fetoprotein; amino acid profiles (arginine (Krebs cycle), histidine / urocanic acid, homocysteine, phenylalanine / tyrosine, tryptophan); androstenedione, antipyrine; arabinitol enantiomers; arginase; benzoylthreonine (cocaine); biotinidase; biopterin; c-reactive protein; carnitine; carnosinase; CD4; ceruloplasmin; chenodeoxycholic acid; chloroquine; cholesterol; cholinesterase; conjugated 1-hydroxy bile acid; cortisol; creatine kinase; creatine kinase MM isoenzyme; cyclosporine A; d-penicillamine; desethylchloroquine; dehydroepiandrosterone sulfate; DNA (acetylase polymorphism, alcohol dehydrogenase, alpha1-antitrypsin, cystic fibrosis, Duchenne / Becker muscular dystrophy, analyte-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 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 acid / acylglycine; free beta-human chorionic gonadotropin; free erythrocyte protoporphyrin; free thyroxine (FT4); free triiodothyronine (FT3); fumarylacetoacetase; galactose / galactose-1-phosphate; galactose-1-phosphate uridyltransferase; gentamicin; analyte-6-phosphate dehydrogenase; glutathione; glutathione peroxidase; glycocholic acid; glycated hemoglobin; haloalkaloid; hemoglobin variants; hexosaminidase A; human erythrocyte carbonic anhydrase I; 17-alpha-hydroxyprogesterone; hypoxanthine phosphoribosyltransferase; immunoreactive trypsin; lactate; lead; lipoprotein ((a), B / A-1, beta); lysozyme; mefloquine; netilmicin; phenobarbital; phenytoin; phytic acid / inositol hexaphosphate; progesterone; prolactin; prolinase; purine nucleoside phosphorylase; quinine; reverse triiodothyronine (rT3); selenium; serum pancreatic lipase; sisomicin; somatotropin C;Specific antibodies (adenovirus, antinuclear antibody, anti-zeta antibody, arbovirus, Orf virus, dengue virus, Dracunculus medinensis, Echinococcus granulosus, Entamoeba histolytica, enterovirus, Giardia duodenalis, Helicobacter pylori, hepatitis B virus, herpes virus, HIV-1, IgE (atopic diseases), influenza virus, Leishmania donovani, Leptospira interrogans, measles / mumps / rubella, Mycobacterium leprae, Mycoplasma pneumoniae, myoglobin, Onchocerca volvulus, parainfluenza virus, Plasmodium falciparum, specific antigen of poliomyelitis, respiratory syncytial virus, Rickettsia (scrub typhus), Schistosoma mansoni, Toxoplasma gondii, Treponema pallidum, Trypanosoma cruzi / Leschtmania braziliensis, vesicular stomatitis virus, Wuchereria bancrofti, yellow fever virus); specific antigens (hepatitis B virus, HIV-1); succinylacetone; sulfadoxine; theophylline; thyroid stimulating hormone (TSH); thyroxine (T4); thyroxine binding globulin; trace elements; metastasis; UDP-galactose-4-epimerase; urea; uroporphyrinogen I synthase; vitamin A; white blood cells; and zinc protoporphyrin. In certain embodiments, salts, sugars, proteins, fats, vitamins, and hormones that are naturally present in blood or tissue fluid can also constitute analytes. Analytes can be naturally present in biological fluids (such as metabolites, hormones, antigens, antibodies, etc.). Alternatively, analytes can be introduced into the body, such as contrast agents for imaging, radioisotopes, chemical reagents, perfluorocarbon-based synthetic blood, pharmaceuticals or pharmaceutical compositions, including but not limited to: insulin; ethanol; cannabis (marijuana, tetrahydrocannabinol, hashish); inhalants (nitrous oxide, amyl nitrite, butyl nitrite, chlorinated hydrocarbons, hydrocarbons); cocaine (crack cocaine); stimulants (amphetamine, methamphetamine, Ritalin, Cylert, Preludin, Didrex, Fiorinal, Dimetane, Preludin); sedatives (barbiturates, methaqualone, tranquilizers such as Valium, Librium, Miltown, Serax, Equanil, Anacin); hallucinogens (phencyclidine, lysergic acid, mescaline, peyote, psilocybin); narcotics (heroin, codeine, morphine, opium, meperidine, acetaminophen, Vicodin, hydrocodone, fentanyl, Darvon, Talwin, Lomotil); designer drugs (analogs of fentanyl, meperidine, amphetamine, methamphetamine, and phencyclidine, such as ecstasy); anabolic steroids; and nicotine. Metabolites of pharmaceuticals and pharmaceutical compositions are also contemplated analytes. Analytes such as neurochemicals and other chemicals produced in the body can also be analyzed, such as for example ascorbic acid, uric acid, dopamine, norepinephrine, 3-methoxytyramine (3MT), 3,4-dihydroxyphenylacetic acid (DOPAC), homovanillic acid (HVA), serotonin (5HT), and 5-hydroxyindoleacetic acid (5HIAA).;

[0216] C. Analyte Sensor System

[0217] As described above Figure 1 As described above, in an embodiment, the analyte sensor 10 includes a continuous glucose sensor, such as a subcutaneous, transdermal (e.g., percutaneous) or intravascular device. In an embodiment, such a sensor or device can analyze multiple intermittent blood samples. The analyte sensor 10 can use any analyte measurement method, including, for example, glucose measurement, including enzymatic, chemical, physical, electrochemical, spectrophotometric, polarimetric, calorimetric, iontophoretic, radiometric, immunochemical, etc.

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

[0219] The glucose sensor can be any device capable of measuring glucose concentration. According to one example embodiment described below, an implantable glucose sensor can be used. However, it should be understood that the devices and methods described herein can be applied to any device capable of detecting the concentration of an analyte (e.g., glucose) and providing an output signal (e.g., in the form of analyte data) representative of the concentration of the analyte (again, e.g., glucose).

[0220] In an embodiment, the analyte sensor 10 is an implantable glucose sensor as described in reference to U.S. Patent No. 6,001,067 and U.S. Patent Publication No. US-2005-0027463-A1. In an embodiment, the analyte sensor 10 is a transcutaneous glucose sensor as described in reference to U.S. Patent Publication No. US-2006-0020187-A1. In an embodiment, the analyte sensor 10 is configured to be implanted in a host vessel or extracorporeally, as described in U.S. Patent Publication No. US-2007-0027385-A1, co-pending U.S. Patent Publication No. US-2008-0119703-A1, filed on October 4, 2006, U.S. Patent Publication No. US-2008-0108942-A1, filed on March 26, 2007, and U.S. Patent Publication No. US-2007-0197890-A1, filed on February 14, 2007. In an embodiment, the continuous glucose sensor includes a transcutaneous sensor as described in U.S. Patent No. 6,565,509, issued to Say et al. In an embodiment, the analyte sensor 10 is a continuous glucose sensor that includes a subcutaneous sensor as described in reference to, for example, U.S. Patent No. 6,579,690, issued to Bonnecaze et al. or U.S. Patent No. 6,484,046, issued to Say et al. In an embodiment, the continuous glucose sensor includes a refillable subcutaneous sensor as described in reference to U.S. Patent No. 6,512,939, issued to Colvin et al. The continuous glucose sensor can include an intravascular sensor as described in reference to U.S. Patent No. 6,477,395, issued to Schulman et al. The continuous glucose sensor can include an intravascular sensor as described in reference to U.S. Patent No. 6,424,847, issued to Mastrototaro et al.

[0221] Figure 3A and 3BDepicts a perspective view and a side view of a housing 200 that can be used in conjunction with an embodiment of an analyte sensor system 8 in accordance with certain aspects of the present disclosure. In certain embodiments, the housing 200 includes a mounting unit 214 and a sensor electronics module 12 attached thereto. The housing 200 is shown in a functional position, including the mounting unit 214 and the sensor electronics module 12 matingly engaged therein. In an embodiment, the mounting unit 214 (also referred to as a housing or sensor cartridge) includes a base 234 that is adapted to be fastened to a host's or user's skin. The base 234 can be formed of a variety of hard or soft materials and can include a low profile to minimize protrusion of the device from the host during use. In an embodiment, the base 234 is at least partially formed of a flexible material, which can provide a number of advantages over other transcutaneous sensors that unfortunately may suffer from motion-related artifacts associated with host activity when the host uses the device. The mounting unit 214 and / or the sensor electronics module 12 can be located above the sensor insertion location to protect the location and / or provide a minimal footprint (utilizing the surface area of the host's skin).

[0222] In an embodiment, a detachable connection is provided between the mounting unit 214 and the sensor electronics module 12, which can improve 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 more expensive sensor electronics module 12 can be reused with multiple sensor systems. In an embodiment, the sensor electronics module 12 is configured with signal processing (programming) such as being configured to filter, calibrate, and / or perform other algorithms useful for calibration and / or display of sensor information. However, an integrated (non-detachable) sensor electronics module can be similarly configured.

[0223] In an embodiment, the contacts 238 are mounted on or in a subassembly hereinafter referred to as the contact subassembly 236, which is configured to fit within the base 234 and the hinge 248 of the mounting unit 214, and the hinge allows the contact subassembly 236 to pivot relative to the mounting unit 214 between a first position (for insertion) and a second position (for use). As used herein, the term "hinge" is a broad term and is used in its ordinary sense, including but not limited to referring to any of a variety of pivoting, articulating, and / or hinge mechanisms, such as adhesive hinges, sliding joints, etc.; the term "hinge" does not necessarily mean a pivot point or a fixed point for articulation. In an embodiment, the contacts 238 are formed of a conductive elastomeric material (such as carbon black elastomer) through which the sensor 10 extends.

[0224] Further reference Figure 3A and 3B, in an embodiment, the mounting unit 214 is provided with an adhesive pad 208, the adhesive pad being disposed on the rear surface of the mounting unit and the adhesive pad comprising a releasable backing layer. Thus, removing the backing layer and ultimately pressing a portion of the base 234 of the mounting unit 214 against the host skin can adhere the mounting unit 214 to the host skin. Additionally or alternatively, after sensor insertion is complete, the adhesive pad can be placed on some or all of the analyte sensor system 8 and / or the sensor 10 to ensure adhesion and optionally to ensure an airtight or watertight seal around the wound exit site (or sensor insertion site) (not shown). A suitable adhesive pad can be selected and designed to stretch, elongate, conform to, and / or ventilate this area (e.g., the host's skin). Refer to Figure 2A and 2B Certain embodiments described are described in more detail with reference to U.S. Patent No. 7,310,544, which is incorporated herein by reference in its entirety. The configuration and arrangement can provide water resistance, waterproofing, and / or airtight performance related to the mounting unit / sensor electronic module embodiments described herein.

[0225] Various methods and apparatuses suitable for use in connection with aspects of the embodiments described herein are disclosed in U.S. Patent Publication No. US-2009-0240120-A1, which is incorporated herein by reference in its entirety.

[0226] Now turning to Figure 3C , a more detailed functional block diagram of the analyte sensor system 308 (e.g., as discussed above in connection with Figure 2A 2B) is provided. As Figure 3C shown, the analyte sensor system 308 can include an analyte sensor 535 (e.g., which can also be designated by the numeral 10 in Figure 1 ) coupled to sensor measurement circuitry 525 for processing and managing sensor data. The sensor measurement circuitry 525 can be coupled to a processor / microprocessor 530 (e.g., which can be part of item 12 in Figure 1 ). In some embodiments, the processor 530 can perform some or all of the functions of the sensor measurement circuitry 525 for obtaining and processing sensor measurements from the sensor 535.

[0227] The processor 530 can further be coupled to a radio unit or transceiver 510 (e.g., which can be Figure 1a portion of item 12) for sending sensor and other data and receiving requests, commands, and other signals from external devices (such as display device 310), which can be used to display or otherwise provide sensor data (or analyte data) or data derived therefrom to a user, server system 334, and / or partner device 315, and the user, server system, and / or partner device can utilize the sensor data or derived data therefrom in administering a medicament (e.g., insulin) and / or diabetes management guidance to the user. As used herein, the terms "radio unit" and "transceiver" may be used interchangeably and generally refer to a device capable of wirelessly transmitting and receiving data.

[0228] The analyte sensor system 308 may further include a storage device 515 for storing and tracking sensor and other data (e.g., it may be Figure 1 a portion of item 12) and a real-time clock (RTC) 545 (e.g., it may be Figure 1 a portion of item 12). For example, the storage device 515 may store configuration parameters 520. Overall, the configuration parameters 520 relate to the operation of the analyte sensor system 308 and, in embodiments, specifically relate to the operation of the analyte sensor system 308 relative to the partner device 315 and / or the display device 315. In an embodiment, the configuration parameters 520 may be accessed (directly or indirectly) by the partner device 315 using the diabetes management partner interface 550. In this way, the configuration parameters 520 may be set and / or modified according to the system requirements 650 of the partner device 315 (refer to Figure 5B ). For example, the configuration parameters 520 may be modified such that the analyte sensor system 308, the display device 310, and / or the partner device 315 operate in a manner that meets one or more of the system requirements 650 of the partner device 315.

[0229] As described above, further reference is made to Figure 3C, an embodiment of the analyte sensor system 308 includes a Diabetes Management Partner Interface (DMPI) 550. The Diabetes Management Partner Interface 550 may allow a partner device 315 connected to the analyte sensor system 308 to set and / or configure / modify configuration parameters 520 such that the system requirements 650 of the partner device 315 can be met in the operation of the analyte sensor system 308, the display device 310, and / or the partner device 315. The DMPI 550 may provide the partner device 315 with access to the configuration parameters 520 for configuring the DMPI. In the case where 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 in which the configuration parameters 520 of the analyte sensor system 308 can be accessed, set, and / or modified according to the respective system requirements and / or design constraints of the partner device 315 and / or the display device 310. This flexibility can improve the integration and interoperability of such devices, thus forming a more usable and versatile ecosystem. Other aspects of the DMPI 550 will be discussed further below.

[0230] Although not explicitly shown in Figure 3C , an embodiment of the analyte sensor system 308 also includes an interface (different from the partner device 315) dedicated to the display device 310. 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 the configuration parameters 520 of the analyte sensor system to facilitate communication with the analyte sensor system 308. As will be further discussed in connection with Fig. 10A and 10B , this interface may be part of the DMPI 550 (e.g., as the DMPI 750a) or implemented in the DMPI, or may be implemented separately. In an embodiment, the DMPI 550 is reconfigurable to accommodate the characteristics of the display device 310 and / or the partner device 315 that can be connected to the analyte sensor system 308, as well as to accommodate system-wide requirements and dynamics such as those of the system 200 (refer to Figure 2A ).

[0231] Some components of the analyte sensor system 308 may need to be replaced periodically. For example, the analyte sensor system 308 can include an implantable sensor 535 that can be connected to a sensor electronics module that includes sensor measurement circuitry 525. Additionally, the analyte sensor system 308 can include a processor 530, a storage device 515, a transceiver 510, and a battery (not shown). The sensor 535 may need to be replaced periodically (e.g., every 7 to 30 days). The sensor electronics module can be configured to be powered on and operate for a longer period of time than the sensor 535 (e.g., 3 to 6 months or longer) until the battery needs to be replaced. Replacing these components can be difficult and may require the assistance of trained personnel. Reducing the need to replace these components, particularly the battery, can significantly improve the convenience and cost of using the analyte sensor system 308, including for the user. In an embodiment, when the sensor electronics module is first used (or reactivated in some cases once the battery is replaced), it can be connected to the sensor 535, and a sensor session can be established. As will be further described below, when the module is first used or reactivated (e.g., after replacing the battery), there can be a process for initially establishing communication between the display device 310 and the sensor electronics module. Once the display device 310 and the sensor electronics module have established communication, the display device 310 and the sensor electronics module can communicate periodically and / or continuously during the life of several sensors 535 until, for example, the battery needs to be replaced. Each time the sensor 535 is replaced, a new sensor session can be established. The new sensor session can be initiated by a process completed using the display device 310, and the process can be triggered by a notification of the new sensor 535 via communication between the sensor electronics module and the display device 310 that can persist between sensor sessions.

[0232] In an example implementation, the analyte sensor system 308 uses the sensor 535 to collect analyte data and transmit the data or its derivatives to the display device 310, the partner device 315, and / or the server system 334. Data points regarding analyte values can be transmitted and emitted during the life of the sensor 535. New measurements and / or related information can be transmitted frequently enough for a remote device / person to adequately monitor the analyte (e.g., glucose) level.

[0233] It should be understood that many details regarding the processing, collection, and exchange of data by the analyte sensor system 308, the partner device 315, and / or the display device 310, etc., are provided elsewhere herein. After studying this disclosure, it will be understood that the analyte sensor system 308 can contain several references Figure 4 and Figure 5BSimilar components as described, at least for some embodiments herein. Thus, even if not explicitly referenced herein Figure 3C the details and uses of such similar components can be understood with respect to the analyte sensor system 308.

[0234] D. Display device

[0235] By way of example again, reference is made to Figure 1 , aspects of display devices 110, 120, 130, and 140 that can be used in system 100 will now be described. In an embodiment of the present disclosure, the sensor electronics module 12 is configured to search a list of display devices for wireless communication with and / or attempt to wirelessly communicate with a display device. Generally speaking and by way of example, typical display devices 110, 120, 130, 140 can wirelessly communicate with the analyte sensor system 8, including authentication for the display devices 110, 120, 130, 140 and / or the analyte sensor system 8, and an exchange of analyte data and control signal transfer.

[0236] In an embodiment, the sensor electronics module 12 is configured to search and / or attempt to wirelessly communicate with a list of display devices 110, 120, 130, 140, for example, in a predetermined and / or programmable order (e.g., hierarchical and / or escalating), where a failure to communicate and / or attempt to alarm with the first device in the list of display devices 110, 120, 130, 140 triggers an attempt to communicate and / or alarm with the second in the list of display devices 110, 120, 130, 140, etc. In an example embodiment, the sensor electronics module 12 is configured to sequentially search and attempt to alert a host or caregiver using a list of display devices 110, 120, 130, 140 as follows: (1) a default display device (e.g., one of the display devices 110, 120, 130, 140) or a customized analyte monitoring device (e.g., display device 110); (2) a mobile phone (e.g., display device 120) via auditory, tactile, and / or visual means, 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 computer (e.g., display device 130); (4) a smartwatch (e.g., display device 140). Of course, other types of display devices are included and / or described herein, and alerts can be sent additionally or alternatively to the partner device 136 and / or the server system 334.

[0237] According to an embodiment, one or more display devices 110, 120, 130, 140 that receive data packets from the sensor electronic module 12 can be debugged into a "virtual display", where the virtual display displays displayable sensor information received from the sensor electronic module 12 without additional processing (e.g., the expected algorithmic processing that may be required for real-time display of sensor information). In an embodiment, 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 may include software that includes display instructions (software programming that includes instructions configured to display the displayable sensor information and optionally query the sensor electronic module 12 for the displayable sensor information), and the instructions are configured to be able to display the displayable sensor information on the display device. In an embodiment, the display devices 110, 120, 130, 140 are programmed with display instructions at the manufacturer and may include security and / or authentication to avoid piracy of the display devices 110, 120, 130, 140 and / or unauthorized access. In an embodiment, the display devices 110, 120, 130, 140 are configured to display the displayable sensor information through a downloadable program (e.g., a downloadable Java script over the Internet), such that any display device 110, 120, 130, 140 that supports program downloading (e.g., any display device 110, 120, 130, 140 that supports Java applets, such as a mobile phone, tablet computer, PDA, PC, etc.) can thus be configured to display the displayable sensor information.

[0238] In an embodiment, certain display devices 110, 120, 130, 140 may communicate wirelessly directly with the sensor electronics module 12, but intermediate network hardware, firmware, and / or software may be included in the direct wireless communication path. In an embodiment, a repeater (e.g., a Bluetooth repeater) may be used to retransmit the transmitted displayable sensor information to a location further than the direct range of the telemetry module of the sensor electronics module 12, where the repeater is capable of enabling direct wireless communication when the displayable sensor information is not substantially processed. In an embodiment, a receiver / transmitter (e.g., a Bluetooth receiver / transmitter) may be used to retransmit the transmitted displayable sensor information possibly in a different format (e.g., in a text message on a TV screen), where the receiver / transmitter is capable of enabling direct wireless communication when the sensor information is not substantially processed. In an embodiment, the sensor electronics module 12 directly wirelessly transmits the displayable sensor information 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.

[0239] In an embodiment, one or more of the display devices 110, 120, 130, 140 include a built-in authentication mechanism where communication between the sensor electronics module 12 and the display devices 110, 120, 130, 140 may require authentication. In an embodiment, to authenticate data communication between the sensor electronics module 12 and the display devices 110, 120, 130, 140, a challenge-response protocol such as key authentication is provided, where the challenge is a request for a key or a hash value or other value based on or derived from the key, and a valid response is the correct key or a hash value or other value based on or derived from the key, such that pairing of the sensor electronics module 12 with the display devices 110, 120, 130, 140 may be done by the user and / or manufacturer through the key. In some cases, this may be referred to as mutual 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 the user or other entity), and / or may be derived from unique identifying features (e.g., fingerprint information, facial information, or retinal information) or information, etc.

[0240] In an embodiment, one or more display devices 110, 120, 130, 140 are configured to query the sensor electronics module 12 for displayable sensor information, where the display devices 110, 120, 130, 140 act as master devices that request sensor information from the sensor electronics module 12 (e.g., from the device) on demand (e.g., in response to a query). Although in some cases the display devices 110, 120, 130, 140 act as master devices and the sensor electronics module 12 acts as a slave device, in other cases these roles can be reversed. For example, the roles can be reversed depending on the nature of the communication, etc.

[0241] In an embodiment, the sensor electronics module 12 is configured to periodically, systematically, and / or regularly transmit sensor information to one or more display devices 110, 120, 130, 140 (e.g., every 1, 2, 5, or 10 minutes or longer or shorter). In an embodiment, the sensor electronics module 12 is configured to transmit a data packet associated with a triggered alarm (e.g., triggered by one or more alarm conditions). However, any combination of the above data transmission states can be implemented with any combination of paired sensor electronics modules 12 and display devices 110, 120, 130, 140. For example, one or more display devices 110, 120, 130, 140 can be configured to query the sensor electronics module 12 (directly or indirectly) and to receive alarm information triggered by one or more satisfied alarm conditions. Additionally, the sensor electronics module 12 can be configured to periodically transmit sensor information to one or more display devices 110, 120, 130, 140 (the same or different display devices as described in the previous example), whereby the system can include display devices 110, 120, 130, 140 that have different functions in how they obtain sensor information.

[0242] In an embodiment, the display devices 110, 120, 130, 140 are configured to retrieve from a data storage memory in the sensor electronics module 12 (e.g., refer to Figure 3CThe storage device 515) queries for data content of a specific type, including directly querying the memory of the sensor electronic module 12 or a database in the storage device and / or requesting a data content packet that is configured or configurable from the database; that is, the data stored in the sensor electronic module 12 can be configurable, queryable, predetermined, and / or pre-packaged based on the characteristics of the display devices 110, 120, 130, 140 with which the sensor electronic module 12 communicates and / or requests. In additional or alternative embodiments, the sensor electronic module 12 generates displayable sensor information based on information known to the sensor electronic module 12 about which display devices 110, 120, 130, 140 will receive a particular transmission. Additionally, some display devices 110, 120, 130, 140 are capable of obtaining calibration information and wirelessly transmitting the calibration information to the sensor electronic module 12 (such as by manually entering calibration information, automatically delivering calibration information, and / or an integrated reference analyte monitor incorporated into the display devices 110, 120, 130, 140). U.S. Patent Publications No. 2006 / 0222566, No. 2007 / 0203966, No. 2007 / 0208245, and No. 2005 / 0154271 describe systems and methods for providing an integrated reference analyte monitor incorporated into a display device (e.g., display devices 110, 120, 130, 140), and / or other calibration methods that can be implemented with the embodiments disclosed herein, all of which patent publications are incorporated herein by reference in their entirety. In an embodiment, some display devices 110, 120, 130, 140 are capable of transmitting calibration information to one or more partner devices 136.

[0243] Generally speaking, multiple display devices (e.g., customized analyte monitoring devices, which in some cases may also be referred to as analyte display device 110, mobile phone 120, tablet computer 130, smart watch 140, reference analyte monitor, pharmaceutical delivery or pharmaceutical device, medical device, and personal computer, etc.) can be configured to wirelessly communicate with sensor electronics module 12. Multiple display devices 110, 120, 130, 140 can be configured to display at least some displayable sensor information wirelessly transmitted from sensor electronics module 12. The displayable sensor information can include sensor data, such as raw data and / or transformed sensor data, such as, for example, 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 can indirectly receive analyte data from analyte sensor system 8 through another device (e.g., partner device 136 and / or server system 134). In an embodiment, display devices 110, 120, 130, 140 can indirectly send commands or other control / configuration signaling to analyte sensor system 8 through another device (e.g., partner device 136 and / or server system 134). Alarms, warnings, and / or notifications related to analyte data can also be provided (either visually, auditorily, and / or haptically) using display devices 110, 120, 130, 140. Additional types of information that can be received at display devices 110, 120, 130, 140 can include information related to battery life or power consumption, other diagnostics, timing, etc.

[0244] In some cases, display devices 110, 120, 130, 140 that have successfully communicated with the analyte sensor system 8 and successfully completed the authentication process can be considered as approved display devices 110, 120, 130, 140. In some cases, the display devices 110, 120, 130, 140 can be configured in a display-only state, in which the display devices 110, 120, 130, 140 can access analyte data in a read and display manner. In this state, the display devices 110, 120, 130, 140 generally do not send commands related to continuous glucose monitoring (CGM) to the analyte sensor system 8. However, other commands can also be sent in this state. Example CGM commands include commands to start, stop, or calibrate a CGM sensor session, where the analyte sensor system 8 is used to generate analyte data. 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 advertising 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 can generally operate in the display-only state include small devices such as key fobs, where the key fob displays analyte data and associated alerts / warnings / notifications. However, in certain cases, any display device 110, 120, 130, 140 can operate in the display-only state, as will be described herein.

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

[0246] Figure 4 Example aspects of the present disclosure are depicted, which can be used in combination with a display device 310 that can be connected to, for example, an analyte sensor system 308 and / or a partner device 315. It should be understood that many details regarding 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. After studying the present disclosure, it will be understood that the display device 310 can include several reference Figure 3C and Figure 5B described similar components, at least for the embodiments. Thus, even if not referenced herein Figure 4Alternatively, the details and uses of such similar components can be understood with respect to the display device 310.

[0247] As Figure 4 shown, the display device 310 can include a plurality of components for communicatively coupling with the analyte sensor system 308 and / or the partner device 315 via the communication medium 305. The display device 310 can be used to alert the user and / or provide sensor information or analyte data, control signaling, and / or other information (e.g., information related to the partner device 315 and / or drug delivery) to the user and / or the analyte sensor system 308, another display device 310, and / or the partner device 315. The display device 310 can include one or more of the following: a connectivity interface 405 (which in turn includes a transceiver 320); a storage device 415 (which in turn stores the analyte sensor application 425a, the partner device application 425b, and / or additional applications); a processor / microprocessor 430 for processing and managing sensor data and / or other data; a user interface 435 (e.g., a human-machine interface, an audio or visual interface (display, LED, speaker, microphone, etc.), tactile feedback, etc.), which can be used to provide / present information to the user and / or receive input from the user; and a real-time clock (RTC) 445. The various elements of the display device 310 can be interconnected using a bus (not shown here) and data can be transmitted between these elements.

[0248] The transceiver 410 can be used to receive sensor data and / or other data and to send / receive requests, instructions, 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 can employ a communication protocol to send and receive the foregoing information. In an embodiment, when a standardized communication protocol is used for communication with the display device 310 (to / from the display device), a commercially available transceiver circuit incorporating processing circuitry can be utilized in the transceiver 410 to handle low-level data communication functions (such as management of data encoding, transmission frequency, handshake protocol, etc.). In these embodiments, the processor 430 may or may not need to manage these activities, but instead can provide the desired data values for transmission and manage high-level functions such as powering on or off, setting the rate of message transmission, etc. The instructions and data values for performing these high-level functions can be stored in the storage device 415 and provided to the transceiver circuitry via the data bus and the transmission protocol established by the manufacturer of the transceiver 410.

[0249] The connectivity interface 405 can be used to interface the display device 310 with the communication medium 305 such that the display device 310 can be communicatively coupled (directly or indirectly) via the communication medium 305 to the analyte sensor system 308, another display device 310, and / or a partner device 315 (e.g., refer to Figure 2A ). The transceiver 410 of the connectivity interface 405 can include multiple transceiver modules that can operate on different wireless standards and / or frequency bands. The transceiver 410 can be used to send / receive analyte or medicament delivery data and / or associated commands and messages to / from the analyte sensor system 308, as well as to wirelessly communicate with the partner device 315. Additionally, the connectivity interface 405 can in some cases include additional components for controlling radio and / or wired connections, such as a baseband and / or Ethernet modem, an audio / video codec, etc.

[0250] The memory 415 can be used to store the operating system of the display device 310 and / or customized (e.g., proprietary) applications designed for wireless data communication between the remote transceiver and the display device 310. The memory 415 can be a single memory device or multiple memory devices, and can be volatile or non-volatile memory for storing data and / or instructions for software programs and applications. These instructions can 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 memory 415 can include volatile memory (e.g., RAM) and / or non-volatile memory (e.g., flash memory), can include any of EPROM, EEPROM, cache, and / or can include some combination / variation of the memories. In various embodiments, the memory 415 can store user input data and / or other data collected by the display device 310 (e.g., inputs collected from other users through the analyte sensor application 425a and / or the partner device application 425b, and / or information related to the partner device 315, including drug delivery data and related information). The memory 415 can also be used to store a large amount of analyte-related data received from the analyte sensor system 308 and / or a large amount of drug-related data received from the partner device 315 for later retrieval and use, for example, to determine trends and / or trigger alerts. In addition, the memory 415 can store the analyte sensor application 425a and / or the partner device application 425b, and when the stored analyte sensor application and / or the partner device application is executed using the processor 430, for example, it receives inputs (e.g., through traditional hard / soft keys or touchscreens, voice detection, or other input mechanisms or the user interface 435), and allows the user to interact with, for example, analyte-related data and related content, and / or drug-related data and related content, and / or other information (e.g., related to system configuration) through the GUI.

[0251] In an embodiment, a user may interact with the analyte sensor application 425a and / or the partner device application 425b via a GUI, which may be provided by a display of the user interface 435 of the display device 310. For example, the GUI of the display device 310 may perform functions such as accepting user input and displaying menus and information derived from analyte data or reagent data. The GUI may be provided via 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 touch screen display that accepts various gestures as input.

[0252] In an embodiment, the application 425a may process and / or present analyte-related data received by the display device 310 according to the various operations described herein, and present such data via the display of the user interface 435. In addition, the application 425a may be used to obtain, access, display, control analyte data and related messages and processes associated with the analyte sensor system 308 and / or interface with such data and the messages and processes, as described in further detail herein.

[0253] The application 425a can be downloaded, installed, and initially configured / set up on the display device 310. For example, the display device 310 can obtain the application 425a from the server system 334 or from another source (such as an app store, etc.) accessible through the communication medium 305. After installation and setup, the application 425a can be used to access and / or interface with analyte data (e.g., whether stored on the server system 334, from a local storage device 415, or from the analyte sensor system 308). By way of example, the application 425a can present a menu containing various controls or commands that can be executed in conjunction with the operation of the analyte sensor system 308 and one or more display devices 310. The application 425a can also be used to interface with or control other display devices 310 and / or partner devices 315, e.g., to transmit or provide analyte-related data thereto, including, for example, by directly receiving / sending analyte data to / from other display devices 310 and / or partner devices 315, and / or by sending instructions for the analyte sensor system 308 and other display devices 310 and / or partner devices 315 to be connected, as will be described herein. Additionally, in some embodiments, the application 425a can interact with one or more additional applications supported by the display device 310, e.g., to retrieve or provide relevant data. By way of example, such applications can include fitness / lifestyle monitoring applications, social media applications, etc. Such applications can also include applications associated with the partner device 315, including the partner device application 425b, which will be described in detail below.

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

[0255] As will be further described below, the display module can present various screens to the user (e.g., via the display of user interface 435), which screens contain graphical representations of information provided by application 425a. In a further embodiment, application 425a can be used to display to the user various display devices 310 that can be connected to analyte sensor system 308, as well as analyte sensor system 308 itself, and / or partner device 315 and the environment in which the display devices, the analyte sensor system, and / or the partner device interact. Sensor application 425a can include a native application modified with a software design kit (e.g., depending on the operating system) to perform the functions / features described herein.

[0256] Further reference Figure 4 , partner device application 425b can also be included in memory 415 and, when executed using, for example, processor 430, application 425b can be used to receive inputs (e.g., via conventional hard / soft keys or touchscreens, voice detection, or other input mechanisms or user interface 435) and can allow the user to interact with pharmaceutical-related data and related content, for example, via the GUI of user interface 435. Application 425b can process and / or present pharmaceutical-related and other partner device or system data received or sent from display device 310 according to various operations described herein and present such data via the display of user interface 435. In addition, application 425b can be used to obtain, access, display, control pharmaceuticals, analytes, and / or other data, as well as related messages and processes associated with partner device 315, display device 310, and / or server system 334 and / or interface therewith, as described in further detail herein.

[0257] In an embodiment, application 425b can be downloaded, installed, and initially configured / set up on display device 310. For example, display device 310 can obtain application 425b from server system 334, where in some cases, application 425b can be provided by the manufacturer of partner device 315 or obtained from another source (such as an app store, etc.) accessed via communication medium 305. After installation and setup, application 425b can be used to access partner device 315 and / or interface with the partner device, including pharmaceutical-related data (e.g., whether stored on server system 334, from local storage device 415, or from partner device 315 and / or analyte sensor system 308). By way of example, application 425b can cause user interface 435 to present a menu including various controls or commands that can be executed in conjunction with the operation of partner device 315, analyte sensor system 308, and / or one or more display devices 310.

[0258] Application 425b can also be used to interface with or control other display devices 310, and / or interface with or control other display devices in relation to the operation of partner devices 315 in the system / ecosystem described herein, e.g., to receive / transmit or provide agent-related data, including, for example, by receiving agent-related data from partner device 315 and / or analyte sensor system 308, and / or by sending instructions for the analyte sensor system 308 and / or partner device 315 to connect or operate in a particular manner as will be described herein. Additionally, in some embodiments, application 425b can interact with one or more additional applications supported by display device 310, e.g., to retrieve or provide relevant data. For example, such applications can include fitness / lifestyle monitoring applications, social media applications, etc. Such applications can also include applications associated with analyte sensor system 308 and / or display device 310, including analyte sensor application 425a. For example, communication between analyte sensor application 425a and partner device application 425b can facilitate the sharing and coordination of alert information originating from analyte sensor system 308 and / or partner device 315.

[0259] Partner device application 425b can include various code / functional modules, such as a display module, a menu module, a list module, etc., as will become apparent from the description of the various functions herein (e.g., in connection with the disclosed methods). These modules can be implemented individually or in combination. Each module can include a (non-transitory) computer-readable medium having computer-executable code stored thereon such that the code can be operably coupled to and / or executed by processor 430 to perform specific functions related to interfacing with partner device 315, display device 310, server system 334, and / or agent-related or analyte-related data or other information, and / or perform tasks associated therewith, as well as interfacing with other applications / devices.

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

[0261] As Figure 4As shown, the storage device 415 of the display device 310 may further include configuration parameters 420. In an embodiment, the configuration parameters 420 manage aspects of wireless communication between the display device 310, the analyte sensor system 308, and / or the partner device 315. Below, for example, reference will be made to Figure 5B and 8 9A - 9S, 10A, and 10B, etc. for a further detailed description of the configuration parameters 420. The system requirements 450 may also be stored in the storage device 415. The system requirements 450 may pertain to the partner device 315 and will be further described in detail by way of example with reference to Figure 5B and 8 9A - 9S, 10A, and 10B.

[0262] Referring again to Figure 4 , as described above, the display device 310 further includes a processor / microcontroller 430. The processor 430 may include processor sub - modules, including, for example, an application processor that interfaces with and / or controls other elements of the display device 310 (e.g., the connectivity interface 405, applications 425a, 425b, the user interface 435 and its components, the RTC 445, etc.). The processor 430 may include a controller and / or a microcontroller that provides various controls related to device management (e.g., interfaces with virtual buttons / inputs and switches, etc.), such as a list of available or previously paired devices, information related to measurement values, including analytes and pharmaceuticals, information related to network conditions (e.g., link quality, etc.), information related to the timing, type, and / or structure of messages exchanged between the analyte sensor system 308, the display device 310, and / or the partner device 315, information related to the diagnosis of various systems, information related to the 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 collection, such as, for example, the fingerprint of the user (e.g., to authorize user access to data or for the authorization / encryption of data, including analyte data) or other identification information, as well as analyte data and / or pharmaceutical delivery data and / or related information.

[0263] The processor 430 may include circuitry such as logic circuits, memory, batteries and power supplies, and associated management circuitry, as well as other circuit drivers for peripheral components and audio / video components and other components of the display device 310. The display device 310 may include those not shown in Figure 4Other peripheral components shown in detail therein, and the processor 430 can be debugged to drive these peripheral components. The processor 430 and any of its sub-processors can include logic circuitry for receiving, processing, and / or storing received and / or input data to the display device 310 and data transmitted or delivered by the display device 310. The processor 430 can be coupled (e.g., via a bus) to the user interface 435, the connectivity interface 405, and the storage device 415 (including the applications 425a, 425b). Thus, the processor 430 can receive and process electrical signals generated by these respective elements, thereby performing various functions. For example, the processor 430 can access stored content from the storage device 415 under the guidance of the applications 425a and / or 425b and process the stored content for display and / or output by the display or other mechanisms of the user interface 435. Additionally, the processor 430 can process the stored content for transmission to other display devices 310, analyte sensor systems 308, server systems 334, and / or partner devices 315 via the connectivity interface 405 and the communication medium 305.

[0264] In an embodiment, the processor 430 can also acquire, detect, calculate, and / or store data input by the user via the user interface 435 over a period of time, or data received from the analyte sensor system 308 (e.g., analyte sensor data and related messages) and / or data received from the partner device 315 (e.g., medicament delivery data and related data / messages). The processor 430 can use this input to measure the user's physical and / or mental responses to analytes, medicaments, or data and other factors (e.g., time of day, location, etc.). In various embodiments, the user's response or other factors can indicate preferences regarding the use of certain display devices 310 and / or partner devices 315 under certain conditions, preferred dosages under certain conditions, and / or the use of certain connection / transmission schemes under various conditions, as will be described in further detail herein.

[0265] E. Partner Devices

[0266] Referring again to Figure 1 , in an embodiment of the present disclosure, the aforementioned sensor electronic module 12 is configured to search for wireless communication with the partner device 136 and / or attempt wireless communication with the partner device. Generally speaking and by way of example, a typical partner device 136 can communicate wirelessly with the analyte sensor system 8, including authentication for the partner device 136 and / or the analyte sensor system 8, and the exchange of analyte data, medicament data, other data, and / or control signaling. In an exemplary embodiment of the present disclosure, the partner device 136 can include a passive device.

[0267] Figure 5AAn example of the partner device 136 is shown, which, as shown, can 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 (e.g., reference Figure 1 ). One reason for doing so is to provide the insulin pump with the ability to pause / activate insulin administration based on glucose values below / above a threshold. An example solution that allows a passive device (e.g., the partner device 136) to receive analyte data (e.g., glucose values) without being coupled to the analyte sensor system 8 is to include the analyte data in an advertisement message transmitted from the analyte sensor system 8 (as discussed by way of example in reference Figure 7C ). The data included in the advertisement message can be encoded such that only devices with identification information associated with the analyte sensor system 8 can decode the analyte data.

[0268] The partner device 136 can include an input / output portion 136a where, for example, glucose values and other values can be displayed and inputs can be received via buttons, wireless connections, or other mechanisms (including various user interface features). The partner device 136 can also include a connection portion 136b that interfaces with the user to administer insulin, for example, in response to an input received in the input / output portion 136a. In some cases, the attachment portion 136b can provide a sensory alert or other notification to the user based on, for example, an input received in the input / output portion 136a and / or a calculated value. It should be understood that the insulin pump can be implemented in many additional or alternative configurations of the partner device 136.

[0269] More generally, the partner device 136 can include medical devices and other devices configured to use analyte data received from the analyte sensor system 8 for patient treatment and / or guidance. The partner device 136 can generally include a pharmaceutical delivery device, where the delivery of a pharmaceutical to a patient depends on factors such as the characteristics of the analyte data received from the analyte sensor system 8. An example of the partner device 136 is an insulin pump. Another example of the partner device 136 is an insulin pen. The partner device 136 can be configured to run a pharmaceutical delivery application using code or instructions stored in a memory or storage device of the partner device 136, as will be described in more detail herein (e.g., reference Figure 5B ).

[0270] A partner device 136 (such as an insulin pump that automatically delivers a medicament to a patient) can impose requirements on the quality and / or nature of the wireless connection / link through which the partner device 136 receives analyte data for making decisions regarding medicament delivery and on the configuration of the ecosystem in which the partner device 136 operates. Other types of partner devices 136 can likewise impose similar or other requirements. For example, some partner devices 136 may require a more dedicated, robust connection such that, for example, a user or patient relying on the pump for insulin delivery does not miss an insulin dose. In such instances, the connection through which the insulin pump receives analyte data should be relatively secure and reliable and should reduce interference from other devices (such as display devices 110, 120, 130, 140). As another example, the partner device 136 may have certain limitations on battery life, the accuracy of calculations regarding CGM data, etc. The partner device 136 is capable of sending CGM commands and other types of commands to the analyte sensor system 8 and is also capable of controlling the mode of operation of the analyte sensor system 8 in accordance with the system requirements 650 of the partner device 136, as will be described herein (e.g., with reference to Figure 5B ).

[0271] In an example implementation where the partner device 136 is an insulin pump, an insulin pump that receives analyte data from the analyte sensor system 8 and performs automatic insulin delivery can, for example, attempt to prevent other display devices 110, 120, 130, 140 from sending CGM control commands to the analyte sensor system 8. Such CGM control commands can affect the algorithms used to calculate CGM data and, thus, the amount of insulin delivered by the insulin pump, which may be undesirable. To maintain control over the amount of insulin delivered, it may be desirable for the insulin pump to be able to prevent the display devices 110, 120, 130, 140 from sending such CGM control commands. This can be accomplished using the various techniques described herein.

[0272] 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 with respect to wireless communication and other performance aspects. An injection device such as an insulin pen may receive analyte data from the analyte sensor system 8 and use the analyte data to provide a user with instructions or guidance (e.g., graphical, audible, tactile, etc.) as to whether the user should (or should not) administer a medicament (e.g., inject insulin), and may also include dosage or injection timing recommendations. That is, unlike the insulin pump implementation of the partner device 136, an insulin pen may rely on user action / intervention. A smart refrigerator implementation of the partner device 136 may be connected to the analyte sensor system 8, monitor analyte data and the user's food / drink consumption, and provide the user with feedback related to the user's expected or resultant blood glucose level (related to food / drink consumption). A smart mirror implementation of the partner device 136 may be connected to the analyte sensor system 8 and / or the display devices 110, 120, 130, 140, and provide the user with a heads-up display of analyte information and / or other guiding cues for diabetes management or other types of health care advice.

[0273] It will be appreciated that just as many different types of partner devices 136 can be envisioned, there are also a large number of manufacturers that can provide partner devices 136 for operation with the analyte sensor system 8 and / or the display devices 110, 120, 130, 140. Across the range of device types and manufacturers, etc., there is a need for flexibility and adaptability of the system so that interoperability, predictability, and extended use can be maintained and promoted, and the interactions and performance of the various devices can be controlled and / or optimized.

[0274] Turning now to Figure 5B , a more detailed example functional block diagram of the partner device 315 is provided. After studying this disclosure, it will be understood that, at least for some embodiments, with respect to the partner device 315, several similar components are described with reference to Figure 4 and 5B as well as the display device 310 and the analyte sensor system 308, and the details and uses of the applicability of such similar components can be understood with respect to the partner device 315 even if not explicitly described herein with reference to 5B.

[0275] As Figure 5BAs shown, an embodiment of the partner device 315 may include a medicament delivery mechanism 640, which may be used to deliver a medicament (e.g., insulin) to a user, including based on analyte data generated by the analyte sensor system 308 and received at the partner device 315 via the communication medium 305. For example, in the case where the partner device 315 is an insulin pump, the medicament delivery mechanism 640 may include, in an embodiment, an infusion device that can deliver insulin from a cannula or other type of reservoir inside or outside the partner device 315. Alternatively, for example, in the case where the partner device 315 is an insulin pen, the medicament delivery mechanism 640 may include a needle that can be used to inject insulin into the user's body.

[0276] The partner device 315 may further include a processor / microcontroller 630, which may be coupled to a radio unit or transceiver 610 for sending / receiving sensor data, requests, commands, and other signals to / 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 the connectivity interface 605 within the partner device 315 and may also be used to send medicament-related information (including dose, bolus information, alerts / warnings / notifications, etc.) to the analyte sensor system 308, the display device 310, other partner devices 315, and / or the server system 334 (refer to Figure 2A ).

[0277] The partner device 315 may further include a storage device 615 and a real-time clock (RTC) 645 for storing and tracking medicament delivery data, sensor data, and / or other information (such as command / control signaling, link characteristics, user input, etc.). In addition to other information / items, the storage device 615 may also store the medicament 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, as well as to address other requirements of the ecosystem that is debugged to use the partner device 315 in some cases.

[0278] According to the various operations described herein, the pharmaceutical delivery application 625 can process and / or present analyte data, pharmaceutical data, and / or other data received from or sent to a 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), and can present aspects of some such data via the user interface 635. Additionally, the application 625 can be used in conjunction with the user interface 635 to obtain, access, display, control pharmaceutical data, analyte data, and / or other data, as well as related messages and processes associated with the partner device 315, the display device 310, the analyte sensor system 308, and / or the server system 334 and / or interface therewith. For example, the user interface 635 can allow a user to input user information or other information into the partner device 315 to assist in administering a pharmaceutical to the user, authenticating the user (e.g., via fingerprint, face, voice, or security code, etc.), and / or inputting user preferences or an operating plan for the partner device 315 (e.g., planned use or non-use, mode control, etc.), and / or an operating plan for the analyte sensor system 308 (e.g., sensor replacement, expected operating time, etc.), and / or an operating plan for the display device 310 (e.g., permission to access data from the partner device 315). It should also be understood that the application 625 can run on the partner device 315 but may not be visible to the user thereon. For example, while the application 625 can be used to execute instructions for controlling the operation of the partner device 315, the user's interface with the application 625 can be accomplished via the display device 310 (or not at all in some cases).

[0279] The application 625 can be downloaded, installed, and initially configured / set up on the partner device 315. For example, the partner device 315 can obtain the application 625 from the server system 334, where in some cases, the application 625 can be provided by the manufacturer of the partner device 315 or obtained from another source (such as an app store, etc.) accessed via the communication medium 305. After installation and setup, the application 625 can be used to access the partner device 315 and / or interface with the partner device, including pharmaceutical-related data (e.g., whether stored on the server system 334, from the local storage device 615, or from the display device 310 and / or the analyte sensor system 308). By way of example, the application 625 can be used to present a menu of various controls or commands that can be executed in conjunction with the operation of the partner device 315, the analyte sensor system 308, and / or one or more display devices 310 (whether on the display device 310, the analyte sensor system 308, and / or the partner device 315).

[0280] The application 625 can also be used to interface with or control the other display device 310, and / or interface with or control the other display device 315 with respect to the operation of the partner device 315 in the system / ecosystem described herein, e.g., to receive / transmit or provide agent-related data, including, for example, by receiving agent-related data from the partner device 315, the display device 310, and / or the analyte sensor system 308, and / or by sending instructions for the analyte sensor system 308, the display device 310, and / or the partner device 315 to connect or operate in a particular manner (e.g., with reference to Figure 8 and 9A -9S) as described herein. Additionally, in some embodiments, the application 625 can interact with one or more additional applications supported by the display device 310, e.g., to retrieve or provide relevant data. By way of example, such applications can include fitness / lifestyle monitoring applications, social media applications, etc. Such applications can also include applications associated with the analyte sensor system 308 and / or the display device 310, including the analyte sensor application 425a and the partner device application 425b.

[0281] The agent delivery application 625 can include various code modules / functional modules, such as, for example, an agent delivery module, an authentication module, a system configuration module, etc., as will become apparent from the description of the various functions herein (e.g., in connection with the disclosed methods). These modules can be implemented individually and / or in combination. Each module can include a (non-transitory) computer-readable medium having computer-executable code stored thereon such that the code can be operably coupled to and / or executed by the processor 630 to perform specific functions regarding interfacing with the partner device 315 and / or agent-related data, and / or perform tasks associated therewith, as well as interfacing with other applications / devices (e.g., the display device 310, the analyte sensor system 308, etc.).

[0282] As will be further described below, the display module of the display device 310 or the partner device 615 can present to the user (e.g., via the user interface 435 display (reference Figure 4 ), and / or the display of the user interface 635 (reference Figure 5B)) various screens, the screens including graphical representations of information provided by application 625 (e.g., insulin dose information). In additional embodiments, application 625 can be used to display to a user of display device 310 an environment for viewing and interacting with partner device 315. In an embodiment, partner device 315 can include a display as part of user interface 635, in which case application 625 can provide information for direct display on partner device 315 (as opposed to using display device 310). The medicament delivery application 625 can include a native application modified with a software design kit (e.g., depending on the operating system) to perform the functions / features described herein. Such a software design kit can be provided by the manufacturer of partner device 315 or other entity.

[0283] As Figure 5B shown, the partner device 315 optionally includes a partner device controller 645. The partner device controller 645 can be used in conjunction with the partner device 315 to add capabilities to the device controller. For example, in an embodiment, the partner device 315 may not be equipped with radio connectivity hardware / software. In such embodiments, the partner device controller 645 can be a "tethered" hardware that can be coupled to the partner device 315 via a connectivity interface 605 and enhance the operating capabilities of the partner device 315, for example, by providing or adding a transceiver, memory, and / or processing capabilities (including, for example, software code / instructions to support it). Thus, in an example implementation, the partner device controller 645 can 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 an embodiment, the medicament delivery application 625 can at least partially reside on the partner device controller 645. In an embodiment, the user interface 635 can at least partially reside on the partner device controller 645. For example, if the partner device lacks a user interface (such as a display), the partner device controller can be used to add display capabilities to the partner device 315.

[0284] It should be noted that at this point, as Figure 3C , 4 , 5A, 5B, the like-named elements among the display device 310, the analyte sensor system 308, and / or the partner device 315 can in some cases include similar features, structures, and / or capabilities. Thus, with respect to such elements, the descriptions of such elements above with reference to any one of the display device 310, the analyte sensor system 308, and the partner device 315 can in some cases apply to the corresponding or similar elements within any one of the display device 310, the analyte sensor system 308, and the partner device 315.

[0285] F. Advertising Timing and Structure

[0286] Another aspect of the disclosure relates to the order and manner in which various devices (e.g., display device 310 and partner device 315) are connected to the analyte sensor system 308, which can depend on the order, timing, structure, and manner of the advertising messages transmitted to such display device 310 and / or partner device 315. A potential scenario for connection ordering of various devices can be described as follows.

[0287] In an embodiment, the analyte sensor system 308 advertises to and establishes a connection with display devices 310 and / or partner devices 315 that are available for connection (e.g., in range and / or otherwise available). For example, this can be done by sending an advertising message. By way of example, refer to Fig. 7A operation 1005a shown in. On the display device 310 / partner device 315 side, the display device 310 and / or partner device 315 seeking to connect to the analyte sensor system 308 can scan the analyte sensor system 308 or another similar sensor system in an example embodiment to establish a connection therewith. This generally requires receiving and processing advertising messages broadcast by the analyte sensor system 308 et al. to determine if any such messages are being transmitted by a compatible / desired analyte sensor system 308.

[0288] The display device 310 and / or partner device 315 can then respond to the advertising message by sending a connection request back to the analyte sensor system 308. By way of example, refer to Fig. 7A operation 1005b shown in. After receiving the connection request, the analyte sensor system 308 can accept, reject, or simply ignore the request. In an example implementation, the analyte sensor system 308 services only one display device 310 connection or one partner device 315 connection at a time. Thus, one reason to reject or ignore a connection request is that the analyte sensor system 308 is already connected to a display device 310 or partner device 315. If there is no reason to reject or ignore the connection request, the analyte sensor system 308 can accept the request and connect to the display device 310 or partner device 310 that sent the request. For example, operation 1005b shows the analyte sensor system 308 accepting the request by sending signaling to the display device 310 or partner device 315 to indicate that the connection request is granted. Refer to Figure 6 、 7A -7C also shows aspects of advertising and related context by way of example. (See, e.g., operations 1065a, 1095a). A detailed discussion of these figures is included further below.

[0289] Further reference is made to Fig. 7A such that, once the display device 310 (or partner device 315) and the analyte sensor system 308 are connected, messages can be exchanged, including, for example, the analyte sensor system 308 transmitting analyte data to the display device 310 or partner device 315. By way of example, reference is made to Fig. 7A operation 1005d shown in. In an embodiment, in order to prevent the display device 310 or partner device 315 from remaining connected to the analyte sensor system 308 for longer than expected or desired, the analyte sensor system 308 can enforce a timeout, and / or can cause a timeout to be enforced. That is, for example, a predetermined limit can be set on the duration of the connection, and when the limit expires, the connection to the analyte sensor system 308 can be terminated. By way of example, reference is made to Fig. 7A operation 1015 shown in, in which the data connection is closed and, optionally, the transceiver 410 is deactivated. Terminating the connection can allow for a connection or at least a connection attempt to be made to the analyte sensor system 308 and other display devices 310 and / or partner devices 315. The analyte sensor system 308 can maintain a list of display devices 310 and / or partner devices 315 that have most recently been connected to the analyte sensor system 308. In some cases, this may be referred to as a whitelist. The analyte sensor system 308 can use the list to allow only the listed display devices 310 and / or partner devices 315 (i.e., those most recently connected or otherwise listed) to connect to the analyte sensor system 308.

[0290] Figure 6 is a timing diagram showing an example of an advertisement message transmission in accordance with an embodiment of the present disclosure. More specifically, Figure 6 an example of an advertisement duration structure 622 is provided, which can be used to pair or establish a connection between the analyte sensor system 308, the display device 310, and / or the partner device 315. In combination with the above and in accordance with an embodiment of the advertisement duration structure 622, the advertisement message 618 can be sent according to time intervals that occur periodically based on a schedule. This can be referred to herein in some cases as an advertisement window interval 612. The repetition period of the occurrence of the advertisement window interval 612 can be of any duration.

[0291] In an embodiment, the advertisement window interval 612 can be configured or set to vary based on the nature of the operation of the analyte sensor system 308 regarding the collection and processing of analyte data and / or based on the nature of the operation of the partner device 315 regarding the administration of the medicament and / or based on other considerations. In an example implementation, the advertisement window interval 612 can 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 can 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 can be configured or set to vary based on the network topology of the system, where 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, reference Figure 2A ; system 800, reference Figure 8 ; and / or system 900, reference Fig.9A ). For example, the advertisement window interval 1012 can 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 automated insulin delivery device, and / or based on the system requirements 650 of the partner device 315 as an automated insulin delivery device. In one particular instance, the advertisement window interval 612 is about 5 minutes. Thus, in this particular instance, every 5 minutes, there will be a time window for sending the advertisement message 618.

[0292] The time window for the advertisement message 618 can be considered the duration during which the advertisement message 618 can actually be sent. This can also be referred to as the advertisement duration 614 in some cases. By way of example, in some example implementations, the length of the advertisement duration 614 can range from 7 seconds to 22 seconds. However, those of ordinary skill in the art will understand after studying this disclosure that the length (in time) of the advertisement duration 614 can range from 0 to any reasonable amount of time. In some cases, the advertisement duration 1014 is shorter than the advertisement window interval 612. However, this can change based on system configurations / requirements discussed in detail elsewhere herein.

[0293] During the advertisement duration 614, advertisement messages 618 may be sent according to an advertisement message interval 616. In some cases, the advertisement messages may be sent periodically, but this is not required. The advertisement message interval 616 may be considered as the time interval between sequential or consecutive transmissions of advertisement messages 618. A specific example range of the advertisement message interval 616 is between 20 and 90 milliseconds, although it will be understood when studying the present disclosure that the advertisement message interval 616 may be shorter or longer, and / or the length may be adaptively variable, programmable, and / or configurable, depending on the relevant environment, including debugging or (re)configuring the advertisement message interval 616 during the advertisement duration 614.

[0294] In an embodiment, the advertisement message interval 616 may be configured or set to vary according to the nature of the operation of the analyte sensor system 308 regarding collection and processing of analyte data and / or according to the nature of the operation of the partner device 315 regarding medicament administration 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 connectable 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, where 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, reference Figure 2A ; system 800, reference Figure 8 ; and / or system 900, reference Fig.9A ). For example, the advertisement window interval 612 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 the partner device 315 as an automatic insulin delivery device.

[0295] After the advertisement window interval 612 has elapsed, the advertisement messages 1018 may resume transmission, and the advertisement duration structure 622 may repeat (e.g., as advertisement duration structure 622'). It should also be noted that one or more of the advertisement message interval 616, the advertisement duration 1014, and the advertisement window interval 612 may be configured to be between advertisement duration structures 622 and 622' and / or within the respective advertisement durations of advertisement duration structures 622, 622' (e.g., 614, etc.).

[0296] The above features of the advertisement duration structure 622 (including the advertisement window interval 612, the advertisement duration 614, and the advertisement message interval 616) can all vary based on various factors. For example, the values of these parameters can vary based on the type and / or quantity of the display devices 310 present, and / or based on the system requirements of such display devices 310, and / or based on how recently such display devices 310 have been connected to the analyte sensor system 308. As another example, the values of these parameters can vary based on the type and / or quantity of the partner devices 315 present, and / or based on the system requirements 650 and / or other features of such partner devices 315 (e.g., whether automatic insulin delivery is being provided). The values of these parameters can also vary in order to optimize the connection reliability, accuracy, battery life, accelerated connection time, etc. of the display devices 310 and / or the partner devices 315. Any one of a decrease in the advertisement window interval 612, an increase in the advertisement duration 614, and a decrease in the advertisement message interval 616 can 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 devices. However, in an example, changing the parameters in this way may be accompanied by an increase in power consumption.

[0297] It should also be understood that one or more advertisement durations 614 can be specifically allocated to a particular display device 310 or partner device 315 for connection. Thus, by revoking the allocation of the advertisement duration 614 to a particular device, or by not allocating the advertisement duration 614 to these devices in the first place, the establishment of a connection between these devices and the analyte sensor system 308 can be blocked. This can be done, for example, in a situation where a dedicated connection is required between the partner device 315 and the analyte sensor system 308, where such a dedicated connection can be substantially free from potential interference introduced by devices other than the partner device 315 in response to advertisements sent by the analyte sensor system 308.

[0298] Accordingly, aspects of the present disclosure include configuring the advertisement duration structure 622, including configuring the advertisement window interval 612, the advertisement duration 1014, and / or the advertisement message interval 616, as well as other features associated with and / or related to advertisement messaging. Aspects of the present disclosure also include controlling the allocation of the advertisement duration 614 to a particular device (e.g., the display device 310 and / or the partner device 315) in order to create dedicated advertisement time slots for such particular devices.

[0299] The foregoing aspects of the present disclosure can be used to increase the likelihood of successfully establishing a connection with the analyte sensor system 308. Additionally, the allocation of the configured advertisement duration 612 and / or the controlled advertisement duration 614 can also reduce the power consumption involved in connection establishment, as the efficiency of the connection protocol is improved. In this way, the overall reliability of the communication related to analyte data and / or pharmaceutical delivery can be increased, while the power consumption can be reduced. In an embodiment, the foregoing aspects of advertisement messaging can be configured to achieve an intelligent trade-off among reliability, speed, power consumption / efficiency, etc., including where such a trade-off can be dynamically achieved 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.

[0300] It should also be understood here that with respect to the foregoing features of connection establishment and / or advertisement messaging, in addition to the analyte sensor system 308 sending advertisement messages for connection establishment purposes to the display device 310 and / or the partner device 315, the display device 310 and / or the partner device 315 can also send advertisement messages for connection establishment purposes. In such a case, after studying the present disclosure, it will be understood that the foregoing features can be similarly adopted.

[0301] G. Connection Model

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

[0303] In an example implementation, the analyte sensor system 308, the display device 310, and / or the partner device 315 may intermittently, regularly, and / or periodically establish communication channels therebetween, rather than having the transmit and receive circuitry of the analyte sensor system 308, the display device 310, and / or the partner device 315 communicate continuously. Thus, for example, in some cases, the analyte sensor system 308 may communicate with the display device 310 and / or the partner device 315 via wireless transmission at a predetermined time interval. The duration of the predetermined time interval may be selected to be long enough such 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 value or analyte data) to the display device 310 for output (e.g., via a display that is part of the user interface 435) to the user and / or the partner device 315, e.g., for administration of a medicament. Although in some embodiments the predetermined time interval may be, for example, every five minutes, it should be understood that the time interval may vary to any desired length of time (e.g., as discussed above in connection with Figure 6 ).

[0304] In an embodiment, the intermittent connection mode may save power relative to other connection modes. Thus, if battery power is a major concern related to packet loss and / or latency, etc., the intermittent connection model may be superior to the continuous connection model. Additionally, it should be understood that according to the intermittent connection model, the display device 310 and / or the partner device 315 in the example implementations are not simultaneously connected to the analyte sensor system 308. Instead, different display devices 310 and / or partner devices 315 are connected for different limited amounts of time in some cases. Which display devices 310 and / or partner devices 315 may be connected and when these devices may be connected to the analyte sensor system 308 may be controlled, e.g., using a list (such as a whitelist) and / or by modifying the advertisement structure employed, as referenced above in Figure 6 . Thus, in some cases, the intermittent mode may be appropriate and / or preferred. One such case may be if the user preferably uses multiple display devices 310 to monitor analyte values. For example, if the user has type 1 diabetes, monitoring of analyte (e.g., glucose) data may be relatively more critical, and thus, multiple display devices 310 may be employed to achieve greater coverage / redundancy.

[0305] Fig. 7Ais an operational flowchart showing various operations performed in an embodiment implementing a method 700 that can be combined for wirelessly transmitting analyte data between 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. The features of method 700 can also be applied in combination with embodiments of related systems, devices, and apparatuses. More specifically, as Fig. 7A shown, a communication session 720 can involve operations 1005a through 1015, although in an embodiment, not all of these operations must be performed.

[0306] Combined Fig. 7A The various tasks performed in conjunction with the processes shown therein can be performed, for example, by processors 430, 530, and / or 630 executing instructions respectively included in storage devices 415, 515, and / or 615 (which can include, for example, non-transitory computer-readable media). The tasks or operations performed in conjunction with the processes can be performed by hardware, software, firmware, and / or any combination thereof incorporated into one or more computing devices, such as one or more of an analyte sensor system 308, a display device 310, a server system 334, and / or a partner device 315.

[0307] After studying this disclosure, it will be understood that the processes can include any number of additional or alternative tasks or operations. This is generally, but not necessarily always, true for all processes and / or methods described herein. The operations shown by way of example in Fig. 7A need not be performed in the order illustrated, and the processes can be incorporated into more comprehensive processes or processes having additional functions not specifically referenced herein Fig. 7A in detail. Again, this is generally, but not necessarily always, true for all processes and / or methods described herein.

[0308] In some examples described below, the analyte value is a glucose value based on one or more measurements performed by an analyte sensor system 308 and / or a sensor 535 (referenced Figure 3C ). However, after studying this disclosure, it should be understood that in an embodiment, the analyte value can 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 can occur periodically, sometimes separated by an update interval represented as "T interval ", and the update interval can correspond to a transceiver 510 of the analyte sensor system 308 (referenced Figure 3C ), a transceiver 410 of the display device 310 (referenced Figure 4 ), and / or a transceiver 610 of the partner device (referenced Figure 5B ) The duration between consecutive wireless communication sessions. Alternatively or additionally, the update interval can be considered as the period for acquiring and transmitting the most recently measured or generated glucose value, medication-related data, or other data. Sending advertising signals or messages, establishing a data connection (e.g., a communication channel), and requesting and sending data can be carried out during a wireless communication session, with each session lasting for the active time or period represented as "T interval " within the update interval T Active ". It should be noted here that the T interval and / or T Active may vary between different sessions. Between consecutive wireless communication sessions, components of the analyte sensor system 308 (e.g., transceiver 510), display device 310 (e.g., transceiver 410), and / or partner device 315 (e.g., transceiver 610) can enter a low-power mode or a similar mode, such as an inactive or sleep mode, for the inactive period represented as "T Inactive ". This can, for example, save battery life and / or reduce peak voltage requirements.

[0309] Therefore, in some connection schemes for transmitting analyte data, medication data, and / or other data and control signaling, connections can be periodically established between the analyte sensor system 308, display device 310, server system 334, and / or partner device 315. For example, with further reference to Fig. 7A , communication session 720 can implement such a connection scheme (optionally including authentication). More specifically, communication session 720 can be implemented during the time interval T interval . As described above, T interval can include an active part corresponding to T Active and an inactive part corresponding to T Inactive . Generally, during T Active , the analyte sensor system 308 and the display device 310 and / or partner device 315 are connected and actively exchange messages (e.g., according to operation 1005 and / or its sub-operations), although as described above, there may be periods during T Active when the analyte sensor system 308, display device 310, and / or partner device 315 enter a low-power mode, etc.

[0310] In terms of connection, in an example implementation, the analyte sensor system 308 may send one or more advertisement messages during communication session 720 at operation 1005. The advertisement messages may be considered an invitation to the display device 310 and / or the partner device 315 (e.g., via transceiver 510) to establish a data connection with the analyte sensor system 308. According to various aspects of the present disclosure, an example structure of an advertisement message that may be transmitted for the purpose of establishing a connection between two devices is described above in connection with Figure 6 U.S. Provisional Application Nos. 62 / 364,771 and 62 / 409,677, which are incorporated herein by reference in their entirety. The advertisement message sent may then be received at the display device 310 (e.g., via transceiver 410) and / or the partner device 315 (e.g., via transceiver 610).

[0311] As described above, during communication session 720, an authentication process may optionally be performed in conjunction 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 listen or scan until an advertisement message sent 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, as part of operation 1005b, an acknowledgement or other message may be sent to the display device 310 and / or the partner device 315. Then, a data connection may be established between the analyte sensor system 308 and the display device 310 and / or the partner device 315.

[0312] According to operation 1005c, an authentication process can be employed before operation 1005d actually exchanges data. The authentication can involve a one-way or two-way handshake process between the analyte sensor system 308 and the display device 310 and / or the partner device 315 according to each operation 1005c, exchanging various messages, including challenges and hash values and the signaling associated therewith. Once authenticated, the analyte sensor system 308 and the display device 310 and / or the partner device 315 can exchange information to determine how to exchange data (e.g., specific frequency, time slot allocation, encryption, etc.). In addition, the communication session 720 can also include exchanging application keys between the analyte sensor system 308 and the display device 310 and / or the partner device 315. Through the exchange of the challenges and hash values described in connection with operation 1005c, such application keys can be effectively shared between the analyte sensor system 308 and the display device 310 and / or the partner device 315. Thus, in an embodiment, the application key can be used for both authentication and encryption purposes.

[0313] Further referring Fig. 7A , after the optional authentication process is completed according to operation 1005c, the analyte sensor system 308 and the connected display device 310 and / or the partner device 315 can perform data communication in operation 1005d, during which the connected display device 310 and / or the partner device 315 can request and receive desired information (e.g., analyte data, control information, identification information, and / or instructions) from the analyte sensor system 308, and / or can send information containing commands and control signaling or other information, such as, for example, information related to a medicament. When the data communication in operation 1005d is completed, the data connection can be terminated in operation 1015 (e.g., by closing the established communication channel).

[0314] However, in other cases, a continuous connection model may be suitable and / or preferred relative to the intermittent connection model described above. At a high level, the continuous connection model can include an initial pairing between the analyte sensor system 308 and the display device 310 and / or the partner device 315, after which the analyte sensor system 308 and the display device 310 and / or the partner device 315 remain connected, with the connection being essentially not closed or disconnected. That is, the connection and data exchange in the exemplary implementation are not done periodically or intermittently as in the intermittent connection model (e.g., as referenced Fig. 7ARather than being continuously connected (as discussed), the connected devices exchange messages periodically to maintain the connection. Once data is available at the analyte sensor system 308, the data can be transmitted to the display device 310 and / or the partner device 315 near real-time or at least close to real-time. In this way, the overall accuracy and responsiveness of communication related to analyte data can be improved. Another advantage associated with the continuous connection model is that the analyte sensor system 308 can be enabled to better mitigate interference caused by an undesired device (e.g., in some cases, an undesired display device 310) attempting to connect to the analyte sensor system 308. Accordingly, the reliability of data exchange and the robustness of the connection can be increased, which is particularly important in cases where the user relies on the partner device 315 to administer a medicament (e.g., insulin).

[0315] For example, the potential increase in data exchange reliability can be beneficial, e.g., in cases where the partner device 315 is an insulin pump that is configured to automatically deliver insulin to the user based on analyte data generated by the analyte sensor system 308 and transmitted to the partner device 315. In some such cases, the connection reliability / robustness between the analyte sensor system 308 and the partner device 315 may be more critical than the ability to establish a connection with multiple display devices 310, and as described above, connection requests from the display device 310 may interfere with the connection or the establishment of a connection between the partner device 315 and the analyte sensor system 308. The continuous connection model employed, for example, between the analyte sensor system 308 and the partner device 315 can be used as a means for increasing the connection reliability / robustness and is thus preferred for certain embodiments involving the partner device 315 and in other cases described and / or implied herein.

[0316] Accordingly, embodiments of the present disclosure include the adoption of a continuous connection model between certain devices. In some cases, such a connection model can reduce the latency between collecting and / or generating analyte data at the analyte sensor system 308 and transmitting 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 medicament-related data and control signals, while maintaining the power consumption of the analyte sensor system 308 low enough. Additionally, as described above, the continuous connection model can 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.

[0317] In this regard, Figure 7BDisclosed is an exemplary implementation of a method 702 for wirelessly transmitting analyte data between an analyte sensor system 308 and a display device 310 and / or a partner device 315 according to the continuous connection model mentioned above. A communication session 740 can be initiated in conjunction with method 702. More specifically, as Figure 7B shown, communication session 740 can involve operations 1095a to 1095g and / or 1095a', although in an embodiment, not all of these operations need to be performed.

[0318] Similar to Fig. 7A that, various tasks performed in conjunction with the process shown in Figure 7B can be performed, for example, by processors 430, 530, and / or 630 executing instructions respectively included in storage devices 415, 515, and / or 615 (which can include, for example, non-transitory computer-readable media). Tasks or operations that are performed in conjunction with the process and generally in conjunction with all processes, operations, and methods described herein but not necessarily always in conjunction with the process, operations, and methods can be performed by hardware, software, firmware, and / or any combination 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. After studying this disclosure, it will be understood that the process can include any number of additional or alternative tasks or operations. The operations shown by way of example in Figure 7B do not necessarily need to be performed in the illustrated order, and the process can be incorporated into a more comprehensive process or processes having additional functions not specifically referenced herein Figure 7B in detail.

[0319] Regarding the continuous connection model, if the connection between the analyte sensor system 308 and the display device 310 and / or the partner device 315 is not maintained, analyte data may be lost or missed. This may in turn lead to an inappropriate or inaccurate representation of analyte information, such as an estimated glucose value, and in some cases, may result in the administration of a medicament being less accurate or precise than desired. Thus, embodiments herein related to the continuous connection model involve maintaining and / or sustaining the connection established between the analyte sensor system 308 and the display device 310 and / or the partner device 315. Additionally, regarding maintaining the connection, it may sometimes be useful to monitor the connection status to derive and / or provide an indication of the connection status. One way to accomplish this is to use connectivity parameters.

[0320] At operation 1095a, 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, for example, by one or more display devices 310 and / or partner devices 315.

[0321] At operation 1095b, a connection may be established between the analyte sensor system 308 and the display device 310 and / or partner device 315 in response to the advertisement message. As part of operation 1095b, connectivity 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 a set of connectivity parameters upon which aspects of the connection with the analyte sensor system 308 may be based.

[0322] Examples of connectivity parameters include connection intervals (referred to herein as pinging intervals in some cases), latency from, and monitoring timeouts. The analyte sensor system 308 and / or the display device 310 and / or the partner device 315 may use one or more of such connectivity parameters to maintain a connection for continuously exchanging data (e.g., related to analyte levels, medicament delivery, associated control signaling, system configuration signaling, etc.). Additional connectivity 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 according to the embodiments described herein.

[0323] After the connection decision that results 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 the analyte sensor system 308, the display device 310, and / or the partner device 315. With respect to the continuous connection model, operation 1095d may be repeated periodically as data becomes available for transmission (e.g., at irregular intervals in some cases), and / or whenever a request to exchange data is made (e.g., on demand). The data exchange according to operation 1095d may be interleaved with the exchange of other messaging, such as ping messaging or other control-related messaging exchanged with the analyte sensor system 308. In Figure 7B this, this may be represented by way of example using operations that are interposed between operations 1095d and 1095d' (i.e., operations 1095e and 1095f), although certain types of control signaling may not be explicitly shown.

[0324] In an embodiment, agreed connectivity parameters and other configuration aspects in connection with connection establishment (e.g., as part of operation 1095b) may be updated / modified subsequently, e.g., after a connection decision is made. Thus, at operation 1095f, method 702 may include updating one or more connectivity parameters. As shown at operation 1095g, in some cases, the connection to the analyte sensor system 308 may be terminated or lost. This may be due to a variety of reasons. In response to losing the connection at operation 1095g, the analyte sensor system 308 may send an advertisement message according to operation 1095a'. According to an example embodiment of the continuous connection model, once the analyte sensor system 308 and the display device 310 and / or the partner device 315 are disconnected, the analyte sensor system 308 may, in some cases, resume sending advertisement messages at least almost immediately.

[0325] According to operation 1095g, the user of the display device 310 and / or the partner device 315 may not be aware that the connection has been lost. In some cases, this may result in packet loss or data loss. Thus, in some cases, the analyte sensor system 308 may automatically resume advertising without user intervention. Alternatively or additionally, the user may receive a notification that the connection has been lost via the analyte sensor system 308, the display device 310, and / or the partner device 315.

[0326] Figure 7C Illustrated in addition to the intermittent connection model and the continuous connection model, embodiments of the present disclosure also relate to data communication via packet broadcast, where such connection establishment is not required. As will be described more fully herein, packet broadcast may be particularly useful in cases where certain devices (e.g., the display device 310) that can be connected to the analyte sensor system 308 are set to a display-only state, while another connectable device (e.g., the partner device 315) has established a connection to the analyte sensor system 308 and is exchanging data and command / control messaging with the analyte sensor system.

[0327] In Figure 7C connection with embodiments of the present disclosure, method 706 for wirelessly transmitting analyte-related data, reagent-related data, and / or other information between the analyte sensor system 308, the display device 310, and / or the partner device 315 is shown. Example embodiments of method 706 relate to establishing a first connection, e.g., between the analyte sensor system 308 and the display device 310 and / or the partner device 315. This is optional and may be carried out in connection with a communication session 720 corresponding to T interval Thus, 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.

[0328] Method 706 also includes establishing a communication session 760, which can be implemented during a time interval T interval '. The time interval T interval ' can be the same as or different from T interval . T interval ' can include an active portion corresponding to T Active ' and an inactive portion corresponding to T Inactive . During T Active ', the communication session 760 can involve operation 1065 and its sub-operations.

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

[0330] Thus, as part of the communication session 760, the analyte sensor system 308 can send a first advertising message (e.g., operation 1065a). The first advertising message can include at least a first portion of the analyte value. The analyte value may or may not be encrypted (e.g., using an application key) before transmission. In other words, with respect to communication session 760, the analyte sensor system 308 can use one or more advertising messages to transmit encrypted or unencrypted analyte values or analyte data and / or other signals (such as timing information and control information), as well as other information that may be included in the advertising message.

[0331] In some cases, the advertising information can take the form of a data packet. For example, the analyte value (whether encrypted or not) can be included in a reserved field or other field in the advertising message data packet, and / or can be encoded into the packet. The advertising message can also or alternatively include other information, such as a timestamp associated with the analyte value. In an example implementation, method 706 can involve decomposing a payload (which can include (encrypted) analyte values and related data) into multiple parts. The first advertising message can then indicate that a second advertising message includes a second portion of the analyte value and / or related data. The first advertisement can indicate this by marking the first portion of the payload, where the mark indicates that subsequent advertising messages can include the second portion of the payload.

[0332] In other words, according to communication session 760, in order to transmit analyte and / or other data to display device 310 and / or partner device 315, an advertising message can be transmitted in combination with operation 1065a. By using a payload encrypted with an application key, privacy / security can be maintained even if an authentication process is not performed during communication session 760. Similarly, since the payload is included in the advertising message, data connection requests and data transmission processes (e.g., operations 1005b and 1005d with reference to Fig. 7A respectively) can also be bypassed or avoided. In this way, the number of messages exchanged according to communication session 760 (and thus power consumption) can be reduced relative to other communication sessions. Additionally, for example, even if partner device 315 maintains a dedicated connection with analyte sensor system 308 and is the only device allowed to send commands and control signals to analyte sensor system 308 (e.g., calibration commands related to a sensor session), analyte and other data can be provided to display device 310.

[0333] Further referring to Figure 7C , communication session 760 can also include, at operation 1065b, display device 310 and / or partner device 315 confirming receipt of one or more advertising messages sent during operation 1065a by sending an acknowledgement (ACK) message. In some cases, this acknowledgement can trigger a data connection process between analyte sensor system 308 and the confirming display device 310 and / or partner device 315. For example, analyte sensor system 308 can then send an ACK to display device 310 and / or partner device 315 and thereby establish a connection with it. In an example deployment, this data connection process can be used to update the application and / or one or more encryption keys and / or to exchange other data, such as calibration data, timing information, permission exchange, mode control signaling, etc. When the communication at operation 1065 is complete, data transmission can terminate at operation 1075. At this time, transceiver 510 and / or processor 530 of analyte sensor system 308 can be deactivated. In Figure 7C , this generally corresponds to operation 1075 and is denoted as T Inactive '.

[0334] As described above, there may be various trade - offs between the intermittent connection model and the continuous connection model. For example, if the continuous connection model is adopted, in some cases the battery power may be consumed faster, although in some cases the reliability / robustness may increase. Therefore, in some cases, it is preferable to switch to the intermittent connection mode. In another example, due to the presence of multiple connection requests / acknowledgments, operating in the intermittent connection mode may lead to an increased chance of data loss / data loss. Therefore, in some cases, it is preferable to switch to the continuous connection mode. In additional examples, the control / command signaling permission of a particular device may change, for example, due to a change in network topology and / or a change in the operating mode, and in such cases, the connection model may change (including, for example, changing from the advertising broadcast scheme described in reference Figure 7C ).

[0335] Accordingly, embodiments of the present disclosure relate to switching between these connection models in order to provide a flexible and adaptable system optimized for various uses, operating conditions, and user / system preferences. Adaptive switching (either in an automated manner or based on user input, both of which are contemplated herein) can allow for optimization of battery power usage as well as transmission efficiency and data accuracy and connection reliability / robustness. Additionally, according to example embodiments, device performance and behavior can be tracked over time and can be used to develop optimized profiles for situations where various connection models may be preferred.

[0336] In some cases, the connection model can be automatically switched according to various criteria. For example, the connection model can be set according to the type of the display device 310 and / or the partner device 315 connected to the analyte sensor system 308. For example, the connection model can be set based on the number of display devices 310 in use - for example, if a single dedicated device is being used (e.g., for a predetermined amount of time), the system can switch to the continuous connection model. Or, if many display devices 310 are being used, the many display devices 310 can utilize the communication session 740. In another example, the connection model can 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 can also be used to determine whether a switch between connection models is appropriate. In addition, the switch of the connection model can be based on the time of day and / or the location of the analyte sensor system 308, the partner device 315, and / or the display device 310. This switch can be initiated by the display device 310, the partner device 315, and / or the analyte sensor system 308 (e.g., using mode control signaling).

[0337] In an embodiment, the switch may be based on user input or may be semi-automatic. For example, a user may navigate a GUI provided by a user interface 435 of the display device 310 to effect the switch. In another example, the switch may be triggered automatically or without user intervention (e.g., triggered by a partner device 315 or in response to a partner device), thereby triggering a prompt 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 (and thus, the switch may be made semi-automatic). The prompt may provide the user with information about the currently used connection model, the reason for the proposed switch, and in some cases, the consequences of rejecting and / or accepting the proposed switch, including the trade-offs associated therewith. In other examples, the prompt may not be provided to the user.

[0338] Turning now to Fig.7D , embodiments of the present disclosure relate to configuring and / or establishing a mesh network using the various connection models described herein (e.g., referring to Figures 7A-7C ). For example, the display device 310 and / or the partner device 315 (and / or any of the plurality of devices) may be connected to the analyte sensor system 308 using different connection models. Referring to Fig.7D and the illustrative example of the system 304, the analyte sensor system 308 may be connected to the display device 310 and / or the partner device 315 via a communication medium 305 (referring to Figure 2B ). Additionally, the display device 310 and the partner device 315 may be connected to each other via the communication medium 305 (again referring to Figure 2B ). It should be understood that although the communication medium 305 is mentioned herein, additional communication media and / or links may be included in the mesh network described herein, and / or various connection models may be used (e.g., communication media 305a, 305b, etc., referring to Figure 2B ).

[0339] Referring again to Fig.7D , for example, a communication session 740 may be employed between the analyte sensor system 308 and the partner device 315, while a different communication session (e.g., 720, 760, etc.) may be employed between the display device 310 on the one hand and the analyte sensor system 308 on the other hand. Additionally, another communication session may be employed between the display device 310 and the partner device 315. Fig.7D Illustrates that the analyte sensor system 308 in combination with the system 304 may use various communication media (e.g., the communication medium 305) and / or connection models (e.g., an intermittent connection model, a continuous connection model, etc., as represented diagrammatically as connection A and connection B, as referred to in Figures 7A-7Cis further discussed in detail) is connected to the display device 310 and / or the partner device 315. Additionally, the display device 310 and the partner device 315 may be connected to each other via various communication media 305 represented herein by way of illustration as connection C. Certain details of the continuous connection and intermittent connection models are further discussed in U.S. Provisional Applications Nos. 62 / 364,771 and 62 / 409,677, which are incorporated herein by reference in their entirety.

[0340] For example, when the display device 310 and the partner device 315 are within range and connectable to the analyte sensor system 308, the analyte sensor system 308 and the display device 310 may be connected using an intermittent connection model (e.g., connection A), and the partner device 315 may be connected to the analyte sensor system 308 using a continuous connection model (e.g., connection B). By way of example, in the intermittent connection mode, the display device 310 periodically connects to the analyte sensor system 308, exchanges data with it, and then disconnects. By way of example, in the continuous connection model, the partner device 315 and the analyte sensor system 308 establish a connection and then continuously exchange signaling to maintain that connection while exchanging data. As a further example, for the intermittent connection model, between subsequent periodic connections, there may be opportunities for other devices to connect to the analyte sensor system 308 or attempt to connect to the analyte sensor system 308 simultaneously with the display device 310, such that the display device 310 may unsuccessfully reconnect to the analyte sensor system 308 (various other circumstances may also cause this). In contrast, in the continuous connection mode, typically unless a severe event occurs, the connection between the partner device 315 and the analyte sensor system 308 is more likely to be maintained without interruption. In this way, the partner device 315 can maintain a more reliable, prioritized connection to the analyte sensor system 308 and can thus have a better quality of service. Thus, for example, applications critical to a patient, such as the automatic delivery of insulin by the partner device 315, may be a case where the continuous connection model is preferred between the partner device 315 and the analyte sensor system 308.

[0341] Further reference Fig.7D, the partner device 315 and the display device 310 can maintain communication via connection C using any of the connection models described herein. Thus, the partner device 315 can directly share reagent delivery data and other information with the display device 310. It will be further understood herein that the respective connection models used by the display device 310 and the partner device 315 to connect to the analyte sensor system 308 can be switched. It should also be understood that both the display device 310 and the partner device 315 can connect to the analyte sensor system 308 using an intermittent connection model or a continuous connection model. It should also be understood and will be discussed herein that, in an embodiment, one or more of the analyte sensor system 308, the display device 310, and the partner device 315 can use an advertisement broadcast connection scheme for any one of the connections A, B, and / or C in the system 304 for a communication session 760.

[0342] Regardless of the connection model employed between the analyte sensor system 308 on the one hand and the display device 310 and / or the partner device 315 on the other hand, the display device 310 and the partner device 315 can connect to each other using any one of the intermittent connection model, the continuous connection model, and / or the advertisement broadcast connection scheme of the communication session 760 (refer to Figure 7C ). In addition, any communication medium and / or connection model employed (e.g., in connections A, B, and C) can be switched to a different connection model after connection establishment, including in subsequent communication sessions.

[0343] H. Alert Overview

[0344] In certain embodiments, one or more alerts, warnings, and / or notifications (in some cases, simply referred to as "alerts") are associated with the analyte sensor system 308, the display device 310, and / or the partner device 315. For example, an alert can relate to one or more alert conditions indicating when the respective alert is triggered. An alert can be triggered based on characteristics of analyte data generated using the analyte sensor system 308. For example, a hypoglycemia alert can include an alert condition indicating the lowest glucose level. The alert condition can also be based on transformed sensor data (such as trend data), and / or sensor data from multiple different sensors (e.g., an alert can be based on sensor data from a glucose sensor and a temperature sensor). For example, a hypoglycemia alert can include an alert condition indicating the minimum required trend of the host glucose level that must be present before the alert is triggered. The term "trend" as used herein generally refers to data indicating certain attributes of data obtained over time, such as calibrated or filtered data from a continuous glucose sensor. A trend can indicate the magnitude, rate of change, acceleration, direction, etc. of data (such as sensor data), including transformed sensor data or raw sensor data.

[0345] In an embodiment, an alert can be triggered based on an event or condition monitored or detected at a partner device 315. For example, if it is determined (e.g., based on self-diagnostics) that the partner device has a mechanical or other failure, an alert can be triggered. In an example implementation where the partner device 315 is an insulin pump, an alert can be triggered based on a pump failure (e.g., a blockage). In an embodiment, if the partner device 315 does not deliver insulin to the user or does not deliver insulin to the user according to a calculated dose (e.g., based on analyte data), an alert can be triggered.

[0346] In certain embodiments, each alert is associated with one or more actions to be performed in response to the triggering of the alert. Alert actions can include, for example, activating an alert via a user interface of the analyte sensor system 308, such as displaying information on a display of the analyte sensor system 308, or activating an audible or vibratory alert of the analyte sensor system 308. In an embodiment, the alert action includes transmitting data to one or more display devices 310 and / or partner devices 315 such that the alert can be provided via the user interfaces 435 and / or 635 (refer to Figure 4 and Figure 5B ). For any alert action associated with a triggered alert, one or more delivery options can define the content and / or format of the data to be transmitted, the devices to which the data can be transmitted, when the data can be transmitted, and / or the communication protocol that can be used to transmit the data. For example, the propagation of an alert can be prioritized over the partner device 315. However, in an embodiment, due to the number of connected devices that can be employed in connection with the collection and use of analyte data, the user may be inundated with alerts. In such a case, it may be useful to coordinate alerts and notifications across user devices, for example, according to an adaptable escalation scheme that can be predefined based on network topology and / or based on user preferences.

[0347] In some embodiments, multiple alert actions (each having its own delivery option) can be associated with a single alert such that, for example, displayable sensor information or other alert information having different content and formats can be sent to respective display devices 310 and / or partner devices 315 or other devices in response to the triggering of the single alert. For example, a mobile phone can receive a data packet containing minimal displayable sensor information (which can be specially formatted for display on the mobile phone), while a desktop computer can receive a data packet 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 common alert. Advantageously, the sensor electronics module need not be bound to a single display device 310, but can be configured to communicate with multiple different display devices 310 directly, systematically, simultaneously (e.g., by broadcasting), periodically, cyclically, randomly, on demand, in response to a query, based on an alert or warning, etc.

[0348] In an embodiment, the analyte sensor system 308 is configured to provide one or more different alerts directly and / or by transmitting a data packet indicating that an alert should be initiated by one or more display devices 310 (e.g., sequentially and / or simultaneously). In some embodiments, the analyte sensor system 308 provides only a data field indicating the presence of an alert condition, and the display device 310 can decide to trigger an alert after reading the data field indicating the presence of the alert condition. In some embodiments, the sensor electronics module determines which of the one or more alerts to trigger based on the triggered one or more alerts. For example, when an alert trigger indicates severe hypoglycemia, the analyte sensor system 308 can perform multiple actions such as activating an alert on the sensor electronics module, sending a data packet indicating activation of an alert on a monitor device, and sending a data packet as a text message to a care provider.

[0349] In an embodiment, the analyte sensor system 308 is configured to wait for a period of time for the host to respond to a triggered alert (e.g., by pressing or selecting a pause and / or off function and / or button on the analyte sensor system 308 and / or display device 310), after which additional alerts can be triggered (e.g., in an escalating manner) until one or more alerts are 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 (such as an insulin pump) associated with an alert condition (e.g., hypoglycemia), where stopping the insulin delivery by the pump stops the alert triggering. Although the analyte sensor system is mentioned above as being configured to provide and / or trigger alerts, it should be understood that the display device 310 and / or partner device 315 can additionally or alternatively provide and / or trigger alerts.

[0350] I. Connectivity Integration with Partner Devices

[0351] Figure 8 Illustrates system 800, which can be used, for example, in conjunction with wireless analyte (e.g., glucose) monitoring and, in some cases, for diabetes management, including, for example, providing pharmaceuticals. System 800 can involve various components interconnected by one or more wired and / or wireless connections for communication and exchange of information such as analyte data, pharmaceutical delivery data, diabetes management feedback and associated guidance and services, alerts / notifications, control signaling, and other information.

[0352] As illustrated by way of example in Figure 8 Examples of embodiments of system 800 include one or more of the following: analyte sensor system 308; display devices 310a, 310b, and / or 310c; partner device 315; server systems 334a and / or 334b; and / or services 805 that can be provided by 334a and / or 334b. It should be noted here that, in an embodiment, server system 334b can be associated with partner device 315 and / or can be maintained by the manufacturer or provider of partner device 315, and server system 334a can be associated with analyte sensor system 308 and / or can be maintained by the manufacturer or provider of analyte sensor system 308. Additionally, in an embodiment, services 805 can be divided into separate services supported, maintained, facilitated, and / or provided by the manufacturer / provider of analyte sensor system 308 on the one hand and the manufacturer / provider of partner device 315 on the other hand. Thus, either or both of server systems 334a and 334b can provide a gateway for receiving services 805 (e.g., backend cloud services). For services 805 that are supported only by the manufacturer of partner device 315 (e.g., in some cases, information, alerts, fault support, etc. related to an insulin pump), such services 805 can be provided by server system 334b. For services 805 that are supported only by the manufacturer of analyte sensor system 308 (e.g., in some cases, the ability to provide another individual / entity to monitor analyte data for a user of display device 310), such services 805 can be provided by server system 334a in this example. In an embodiment, services 805 can utilize server systems 334a and 334b (e.g., in some cases, the ability to provide another individual / entity to monitor analyte data and insulin administration data for users of display device 310 and partner device 315). Additional aspects of remote services that can be provided by a cloud server (e.g., server systems 334a / 334b) are discussed below.

[0353] Figure 8 Certain of the foregoing components and their features shown in Figure 1, 2A , 2B, 3A-C, 4, 5A, 5B, 6, and 7A-D have been described. The component system 800 can be interconnected by various links 802a-d, 804a-b, 806a-b, 808a-b, and 810, as Figure 8 shown, where these links can be implemented using the communication medium 305 respectively for communication purposes. It should be understood that the links 802a-d, 804a-b, 806a-b, 808a-b, and 810 can be any type of communication link, including, for example, point-to-point, broadcast, multicast, etc. Regarding the embodiments, it should be understood that the elements with the same numbers shown in the system 800 can be implemented in the above manner.

[0354] Fig.9A Depicts a system 900, which can be used, for example, in conjunction with wireless analyte (e.g., glucose) monitoring and, in some cases, for diabetes management, including, for example, providing medications. The system 900 can involve various components interconnected by 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 / or other information. Embodiments of the system 900 include one or more of the following: an analyte sensor 308; a display device 910, including a mobile phone 910a, an analyte display device 910b, and / or a wearable device 910c; a partner device 915, which can 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', which can include a mirror 910d, a vehicle 910e, and / or a keychain 910f. In Fig.9A the example implementation shown, 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 Fig.9A shown, where these links can each be implemented using the communication medium 305 respectively for communication purposes. The PAN 902 can use at least one or more of BLE, wireless networks, etc.

[0355] The system 900 can also include a router 920a coupled to one or more devices within the PAN 920 (e.g., coupled to the mirror 910d via the link 914), although not all possible links are explicitly shown. The router 920a can in turn be coupled to one or more servers 920(b) via the link 922 (e.g., refer to Figure 2Aserver system 334), and the server can further be coupled to a cellular network 920c (e.g., a 4G LTE network, etc.) via a link 924. The cellular network 920c can also be coupled to a cellular-enabled device within the PAN 902, such as a mobile phone 910a, via a link 926. In an embodiment, Fig.9A any device shown in can be cellular-enabled and thus can be directly coupled to the cellular network 920c and / or the WAN 904 or its components. For example, the analyte sensor system 308 can be equipped with cellular or other longer-range radio components and thus can be directly coupled to the cellular network 920c and / or the WAN 904 or its components. As Fig.9A shown, the router 920a, the server 920b, and the cellular network 920c can be configured to be part of a wide area network (WAN) 904. The links 914, 922, 924, and 926 can be implemented using a communication medium 305 (e.g., can be wired or wireless, etc.). The WAN 904 can generally provide cloud services to one or more devices in the PAN 902. Similarly, not all possible links between the devices in the WAN 904 and the devices in the PAN 902 are explicitly shown, but those skilled in the art will understand these links after studying the present disclosure. It should also be understood that in some cases, the components of the WAN 904 can be incorporated into the PAN 902, and vice versa.

[0356] Multiple of the foregoing components and their features of the system 900 have been described above with reference to, for example, Figure 1 , 2A , 2B, 3A-C, 4, 5A, 5B, 6, and 7A-C. Those skilled in the art will recognize, after studying the present disclosure, where and how the above description of these components can be applied herein, whether or not it is explicitly conveyed herein where and how it can be applied.

[0357] Regarding system 900, where system 900 includes partner device 915, two instances can drive specific arrangements and / or implementations for wireless analyte monitoring and / or diabetes management of the above components of system 900. The first instance does not involve the delivery of a medicament (e.g., insulin) through partner device 915 (e.g., through medicament delivery device 915a). In this instance, in an embodiment, system 900 includes analyte sensor system 308, one or more display devices 910, 910' (e.g., mobile 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 remote key 910f) configured to be in a display-only state. In an embodiment, this instance involves display devices 910a and 910b operating in a command / control state (e.g., smart phone 120, etc. and analyte display device 110, refer to Figure 1 ), and one or more display devices 910, 910' operating in a display-only state (e.g., remote key 910f and smart mirror 910d or wearable device 910c, etc.).

[0358] Different from the first instance, the second instance involves the delivery of a medicament (e.g., insulin) by at least one of partner devices 915 (e.g., medicament delivery device 915a). In this instance, the medicament delivery by medicament delivery device 915 can be automatic or not (e.g., automatic insulin pump or non-automatic insulin pen). In this second instance, in the case where medicament delivery device 915a for delivering the medicament is part of system 900, interoperability issues can be introduced regarding which device (e.g., medicament delivery device 915, analyte sensor system 308, and / or display devices 910, 910') can control / manage the generation of analyte data (including, for example, calculating CGM values, etc.).

[0359] Regarding this second instance, in order to flexibly and adaptively support potential changes in various partner devices 915 and prior unknown system requirements 650 from an interoperability perspective (e.g., refer to Figure 5B), where such partner device 915 can be provided by various manufacturers / developers different 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, the medicament delivery device 915a (or a similar partner device 915) should be able to control the data exchange between the analyte sensor system 308 and the display devices 910, 910' via the links 906a-g. Such control can be provided, for example, by a user of the display devices 910, 910 (e.g., a user of the phone 910a, where the mobile phone 910a grants control authority to the medicament delivery device 915 via the link 916).

[0360] In an embodiment, aspects of the communication session and / or the sensor session should also be controlled (e.g., the partner device 915, the analyte sensor system 308, and / or the display devices 910, 910' should be able to limit command / control signaling in some cases, including cases where such signaling is related to analyte data). For example, if the medicament delivery device 915a is used for insulin delivery, the transmission of command signaling to the analyte sensor system 308 can be limited to specific devices within the system 900. Some partner devices 915 may generally be less robust in some cases, e.g., in terms of maintaining accuracy in a relatively high interference environment. In such a case, for example, due to the system requirements 650 of the medicament delivery device 915a, the probability that the medicament delivery device 915a receives inaccurate analyte data from the analyte sensor system 308 can be reduced when the display devices 910, 910' are restricted from sending control / command signals related to, for example, the start, stop, or calibration of the sensor session. For example, such signaling may cause the analyte sensor system 308 to operate in a manner that is incompatible or not optimal or not preferred with respect to the medicament delivery 915a, which can be reflected by, for example, its system requirements 650. In an embodiment, it may be beneficial to authorize the transmission of control signals / command signals only to specific devices within the system 900 based on the device type and / or based on the operating mode of the system 900. In an embodiment, it may be beneficial to flexibly add devices (e.g., partner device 915 and / or display devices 910, 910') to the system 900 or remove devices from the system (whether in the PAN 902 or in the WAN 904) to manage the access of these devices to the analyte sensor system 308 and / or manage how alerts propagate between various such devices and other devices within the system 900.

[0361] In an embodiment, for safety and / or robustness purposes, it can also be beneficial for system 900 (including, for example, for the medicament delivery device 915a) to provide means for controlling alert settings. In an embodiment, it can be beneficial to adaptively modify aspects of system 900 if literally or due to system limitations (such as power, etc.) and / or according to other network conditions / configurations of PAN 902 and / or WAN 904 to be discussed herein, certain links become unavailable (e.g., link 906d between the analyte sensor system 308 and the medicament delivery device 915a, link 922 between the mobile phone 910a and the cellular network 920c, etc.). Additionally, in some cases, it is 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.

[0362] Accordingly, embodiments of the present disclosure provide a more flexible / adaptive system of the analyte sensor system 308, display devices 910, 910' and / or partner devices 915, and methods of using the same, where such flexibility / adaptability can include setting or modifying configuration parameters 520 of the analyte sensor system 308, alerts / warnings that can be propagated through system 900, control capabilities / command capabilities of the display devices 910, 910' and / or partner devices 915, connection models employed between devices in system 900, etc. In an embodiment, the diabetes management partner interface (DMPI) 750 that can be implemented using the analyte sensor system 308 is used at least in part to facilitate flexibility / adaptability. As will be described in further detail, in an embodiment, various devices within system 900 (including, for example, partner devices 915) can utilize the DMPI 750 to access / modify the configuration parameters 520 of the analyte sensor system 308 and (re)configure aspects thereof and / or aspects of, for example, the display devices 910, 910' to operate according to the system requirements 650 of the partner device 915 (e.g., the medicament delivery device 915a). For example, the system requirements 650 can be driven or based on safety and / or regulatory requirements, user experience configurations / settings / limitations, power consumption specifications / limitations, etc. that are debugged into the medicament delivery device 915a. The system requirements 650 can be used to determine the format of data packets sent to the partner device 915 and / or the display devices 910, 910' based on the corresponding preferences / specifications, etc. of the partner device 915 and / or the display devices 910, 910', and the protocol for sending such data packets.

[0363] Further reference Fig.9A, example embodiments involving various partner devices 915 within system 900 will now be described. In the example implementation described below, system 900 may include three partner devices 915, namely, 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 capabilities and performance characteristics, which may be reflected in certain corresponding system requirements 650 of the three partner devices 915 (refer to Figure 5B ), and each of the three partner devices 915 may use the DMPI 750 of the analyte sensor system 308 (by way of example, refer to Fig. 10A ) to modify the configuration parameters 520 of the analyte sensor system 308 according to the corresponding system requirements 650. In this way, the analyte sensor 308 can be tuned for better interoperability with any one of the first and second insulin pumps and the insulin pen, regardless of which partner device 915 is connected to the analyte sensor system 308 and / or within system 900. After studying this disclosure, it will be understood that the description of the first insulin pump 915b, the second insulin pump 915c, and the insulin pen 915d can be equally applied to any instance of the partner device 915, including the medicament delivery device 915a and similar devices.

[0364] For illustrative purposes, more details regarding the corresponding characteristics of the first and second insulin pumps 915b, 915c, and the insulin pen 915d in these example implementations will now be provided. By way of example, the first insulin pump 915b may have a relatively robust medicament delivery algorithm, may have a larger (or greater capacity) battery or power source, and may require a blood glucose calibration every 12 hours. The relatively robust algorithm of the first insulin pump 915b may essentially mean that the algorithm is relatively less susceptible to interference from other devices that may attempt to connect to the analyte sensor system 308 (such as the display devices 910, 910'), including situations where such interference may involve interference during connection establishment or interference with the command signaling sent to the analyte sensor system 308. For example, the algorithm of the first insulin pump 915b is capable of operating better across a wider range of configuration parameters 520 and is capable of better handling calibration and start / stop events initiated by other devices. The 12-hour blood glucose calibration requirement may reflect the precision limitations of the first insulin pump (e.g., may be reflected in the system requirements 650 of the first insulin pump 915b).

[0365] As a further example, the second insulin pump 915c can have a relatively less robust algorithm for use in drug administration, can be less restricted in terms of blood glucose accuracy calibration (e.g., a factory calibration accuracy level can be used), and can support remote services provided by the server 920b (e.g., via a connection / link directly through the cellular network 920c ( Fig.9A the link is not shown therein), indirectly through the router 920a (the link is also not shown) or indirectly, for example, through the mobile phone 910a to the server 920b). The relatively less robust algorithm of the second insulin pump 915c may substantially mean that the second insulin pump 915c is not designed to operate well in a high-interference environment where other devices within the system 900 may compete to establish a connection with the analyte sensor system 308 and / or may send commands / control signals thereto.

[0366] Continuing with the illustrative example, the insulin pen 915d can have hard keys / soft keys for receiving user input and can include a simple user interface, both of which can be represented, for example, by the user interface 635 (refer to Figure 5B ). The insulin pen 915d can be further configured to query the analyte sensor system 308 and share data therewith, such as reading analyte data therefrom and sharing insulin-related information (e.g., dose-related) therewith.

[0367] Given the above example information regarding the first and second insulin pumps 915b, 915c and the insulin pen 915d, example scenarios of how to use the DMPI 750 to flexibly configure the system 900 will now be provided. The first example scenario can 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 the user, powered on, etc.), the user can be requested to authorize the first insulin pump 915b to control the analyte sensor system 308 and start administering the drug to the user. For example, such a request can be provided to the user through the user interface 435 of the mobile phone 910a (refer to Figure 4 ) that can be connected to the analyte sensor system 308 and / or the first insulin pump, through the user interface 635 of the first insulin pump 915b (refer to Figure 5B ), and / or through the user interface of the analyte sensor system 308. If the user authorizes the request, the first insulin pump 915b can use the DMPI 750 to access and set and / or modify the configuration parameters 520 of the analyte sensor system 308 according to the system requirements 650 of the first insulin pump 915b (e.g., refer to Fig. 10A ).

[0368] In this example, in terms of the first insulin pump 915b accessing the configuration parameter 520 via the DMPI 750, the developer of the first insulin pump 915b may have integrated and tested the pump 915b with the analyte sensor system 308 before the product is sold or provided to the user. In this way, the first insulin pump 915b can include instructions, code, or other files in the storage device 615 that enable the first insulin pump 915b to correctly navigate the DMPI 750 and the configuration parameter 520. In an embodiment, such instructions can 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 can obtain such instructions or other information from the server 920b and / or the WAN 904 or its components.

[0369] For example, the first insulin pump 915b can use the DMPI 750 to change one or more wireless connectivity parameters of the configuration parameter 520. The wireless connectivity parameters can include settings related to a database that contains / stores information related to the accessibility of devices maintained by the analyte sensor system 308 (e.g., a whitelist), and the first insulin pump 915b can change such whitelist settings, for example, such that the first insulin pump 915b does not exit the whitelist until the battery level of the first insulin pump 915b drops below a specific threshold (e.g., 5%). The first insulin pump 915b can set the wireless connectivity parameters in this way because, as described above, the first insulin pen 915b has a larger battery (e.g., a higher battery capacity), and for example, if the first insulin pump 915b is disconnected from the analyte sensor system 308 for some reason (e.g., by being out of range), then it may be beneficial for the first insulin pump 915b to seek to re - establish a connection with the analyte sensor system 308 once the opportunity arises.

[0370] The first insulin pump 915b can use the DMPI 750 to set or change additional wireless connectivity parameters (such as a timeout setting for advertising message transmission), for example, such that the analyte sensor system 308 advertises for a total of 1 second before stopping advertising message transmission. That is, in this example, the advertising duration 614 (refer to Figure 6) can be set to 1 second. The first insulin pump 915b can set the wireless connectivity parameters in this way because the first insulin pump 915b can have a relatively precise scanning algorithm (e.g., determined by the developer of the first insulin pump 915b or otherwise), such that the first insulin pump 915b can reliably establish a connection with the analyte sensor system 308 at an appropriate time (e.g., once every advertisement window interval 612, which can be 5 minutes in some cases) without conducting advertisements for a longer duration. By shortening the advertisement window interval 612, battery power can be saved.

[0371] In addition, the first insulin pump 915b can use the DMPI 750 to change one or more access control parameters of the configuration parameter 520. The access control parameters can include, for example, multiple display devices 910, 910' with which the analyte sensor system 308 can maintain a connection, and / or can include, for example, the access or control levels that these display devices 910, 910' can have with respect to the analyte sensor system 308. For example, the first insulin pump 915b can set one or both of these access control parameters such that there are no imposed restrictions. The first insulin pump 915b can set the access control parameters in this way because, as described above, the first insulin pump 915b can have a relatively robust insulin administration algorithm and thus does not need to prevent other devices from sending calibrations, etc. (e.g., because the algorithm of the first insulin pump 915b can handle such external events and adjust accordingly).

[0372] In addition, the first insulin pump 915b in this example can use the DMPI 750 to change one or more analyte data parameters of the configuration parameter 520. The analyte data parameters can include the calibration period of the analyte sensor system 308. For example, according to the above system requirements 650 of the first insulin pump 915b, the first insulin pump 915b can set the calibration period to 12 hours.

[0373] A second example scenario can involve using a second insulin pump 915c together with the analyte sensor 308. Similar to the above example involving the first insulin pump 915b, after setup and authorization, the second insulin pump 915c can, according to the system requirements 650 of the second insulin pump 915c (e.g., with reference to Fig. 10A)Use DMPI 750 to access and set and / or modify the configuration parameter 520 of the analyte sensor system 308. Similar to the previous example, in terms of the second insulin pump 915c accessing the configuration parameter 520 via DMPI 750, the developer of the second insulin pump 915c may have integrated and tested the pump with the analyte sensor system 308 before the product is sold or provided to the user. In this way, the second insulin pump 915c can be debugged to correctly navigate DMPI 750 and the configuration parameter 520. In an embodiment, the second insulin pump may also reconfigure DMPI 750 before accessing the configuration parameter 520.

[0374] Regarding a second example scenario, several situations are envisioned here. In a first case, as an initial matter when deciding to use an insulin delivery device, the user selects the second insulin pump 915c instead of the first insulin pump 915b or the insulin pen 915d. In a second case, the user may have used the first insulin pump 915b or the insulin pen 915d for some time, but then may switch to the second insulin pump 915c. That is, although the first and second insulin pumps 915b and 915c and / or the insulin pen 915d are not necessarily used simultaneously, this example includes the first and second insulin pumps 915b and 915c and / or the insulin pen 915d being used in a tandem manner (e.g., the user decides to use a different pump product, or the first pump product malfunctions, etc.). It should also be understood that any partner device 915 can be used in a tandem manner.

[0375] For example, the second insulin pump 915c can use DMPI 750 to set or change the wireless connectivity parameters of the analyte sensor system 308 (including the timeout setting for transmitting advertisement messages), such that the analyte sensor system 308 can advertise for a total of 5 seconds before stopping to transmit advertisement messages. The second insulin pump 915c can set the wireless connectivity parameters in this way because the second insulin pump 915c may have a relatively less precise scanning algorithm (e.g., determined by the developer of the second insulin pump 915c or otherwise), such that the second insulin pump 915c may not be able to reliably establish a connection with the analyte sensor system 308 at the appropriate time (e.g., once every advertisement window interval 612, which can be 5 minutes in some cases) without advertising for a relatively longer duration.

[0376] In addition, the second insulin pump 915c in this example can use DMPI 750 to change additional wireless connectivity parameters. Such wireless connectivity parameters can be related to, for example, a remote (e.g., cloud-based) service that can be provided by the server 920b (e.g., refer to Figure 8is related to the use of the service 805). For example, the second insulin pump 915c can set wireless connectivity parameters to allow the use of such remote services (e.g., cloud-based support modules), and configure the analyte sensor system 308 to transmit diabetes management feedback received in conjunction with such remote services to display devices 910, 910', which can be within the range of the analyte sensor system 308 and / or connected to the analyte sensor system (e.g., where in some cases the display devices 910, 910' can be in a display-only state / mode). The second insulin pump 915c can set these wireless connectivity parameters in this way because the second insulin pump 915c may have been approved to disseminate such diabetes management feedback to other display devices 910, 910', etc. Additionally, the second insulin pump 915c can set these wireless connectivity parameters such that if the remote service becomes unavailable (e.g., due to the loss of a link (such as link 914, 922, 924, or 926, etc.) to the server 920b), the diabetes management feedback feature can be disabled, and a relevant notification can be sent to display devices 910, 910', etc. that can be within the range of the analyte sensor system 308 and / or connected to the analyte sensor system.

[0377] In addition, the second insulin pump 915c can use the DMPI 750 to change one or more access control parameters of the configuration parameter 520, including, for example, by setting the number of display devices 910, 910' to which the analyte sensor system 308 can be connected to three devices, and by setting the access or control level of these display devices 910, 910' relative to the analyte sensor system 308 such that up to three display devices 910, 910' operate in a display-only state or mode, where these display devices 910, 910' are capable of displaying analyte delivery data and / or insulin delivery data, relevant notifications / alerts, and other information, but cannot send control / command signals to the analyte sensor 308. The second insulin pump 915c can set the access control parameters in this way because, as described above, the second insulin pump 915c may have a relatively less robust insulin administration algorithm and may therefore attempt to prevent other devices from sending calibrations, etc. (e.g., because the algorithm of the second insulin pump 915c may not be able to handle such external events or adjust to these events accordingly).

[0378] In addition, with respect to the analyte data parameters that may be included in the configuration parameter 520, the second insulin pump 915c may not make any changes to the factory calibration parameters (e.g., including the factory calibration period), which may be the default parameters that are off-the-shelf or provided by the manufacturer of the analyte sensor system 308. This may be because, as described above, the second insulin pump 915c may use the factory calibration accuracy level. In this case, the analyte sensor system 308 may not generate a calibration prompt and may simply follow the default calibration schedule.

[0379] A third example scenario may involve using the insulin pen 915d with the analyte sensor system 308. Similar to the above examples involving the first and second insulin pumps 915b, 915c, after setting up and authorizing the use of the insulin pen 915d (including multiple daily injections of insulin that can be performed manually), the insulin pen 915d may use the DMPI 750 to access and set and / or modify the configuration parameter 520 of the analyte sensor system 308 according to the system requirements 650 of the insulin pen 915d (e.g., refer to Fig. 10A ). Similar to the previous instances, in terms of the insulin pen 915d accessing the configuration parameter 520 via the DMPI 750, the developer of the insulin pen 915d may have integrated and tested the pen with the analyte sensor system 308 before the product is sold or provided to the user. In this way, the insulin pen 915d can be debugged to correctly navigate the DMPI 750 and the configuration parameter 520.

[0380] For example, the insulin pen 915d may use the DMPI 750 to change one or more access control parameters of the configuration parameter 520, including, for example, making a choice to establish a direct connection with the analyte sensor system 308, as opposed to indirectly establishing a connection with the analyte sensor system 308 via, for example, the mobile phone 910a. Despite this choice, the mobile phone 910a may still establish a connection with the analyte sensor system 308 and / or the insulin pen 915d and exchange information with them, depending on how the configuration parameter 520 is otherwise set.

[0381] The insulin pen 915d may also use the DMPI 750 to change the wireless connectivity parameters of the analyte sensor system 308, including with respect to the transmission of advertising messages, such that, for example, the analyte sensor system 308 may advertise according to the default settings of the display devices 910, 910', etc., but for the insulin pen 915d, the analyte sensor system 308 may use an extended advertising duration 614 and / or a reduced advertising window interval 612 to advertise (refer to Figure 6)。The insulin pen 615d can set the wireless connectivity parameters in this way because for a device such as the insulin pen 615d, the user may need a more responsive system that can access, for example, the latest glucose data that is easily accessible to the user.

[0382] In addition, the insulin pen 615d can use the DMPI 750 to access the analyte data parameters of the configuration parameter 520 to allow the use of, for example, a bolus calculator that can be implemented by the analyte sensor system 308. For example, the DMPI 750 can provide the insulin pen 915d with access to the bolus calculation parameters that can be maintained by the analyte sensor system 308, such that the analyte sensor system 308 can modify the bolus calculation parameters. In an embodiment of the present disclosure, the analyte sensor system 308 can use the bolus calculation parameters to provide the user with bolus-related recommendations, where the recommendations are based on calculations performed by the analyte sensor system 308 using the bolus calculation parameters (e.g., the bolus calculator of the analyte sensor system 308).

[0383] The insulin pen 915d in this example can also use the DMPI 750 to change one or more additional analyte data parameters of the configuration parameter 520. For example, in some cases, for reasons similar to those discussed above regarding the system requirements 650 of the first insulin pump 915b, the insulin pen 915d can set the calibration period to 12 hours.

[0384] Regarding an example scenario involving the insulin pen 915d, in some cases, the user may want and / or need to administer insulin and can therefore select a bolus value on the insulin pen 915d (e.g., using the user interface 635, refer to Figure 6)。A connection can then be establis...

Claims

1. A method of configuring an analyte sensor system for wireless communication with multiple partner devices using a diabetes management partner interface, the method comprises: The analyte sensor system receives authorization to provide access to a set of configuration parameters to one of the partner devices via the diabetes management partner interface, wherein the set of configuration parameters is stored in the memory of the analyte sensor system, wherein the set of configuration parameters includes a set of analyte data parameters, and the set of analyte data parameters includes bolus calculation parameters; and In response to an input received from the one partner device via the diabetes management partner interface, the analyte sensor system sets the set of configuration parameters or causes a modification to the set of configuration parameters according to the system requirements of the one partner device, wherein the analyte sensor system setting the set of configuration parameters or causing the modification to the set of configuration parameters according to the system requirements of the one partner device includes the analyte sensor system using the diabetes management partner interface to provide the one partner device with access to the bolus calculation parameters.

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

3. The method according to claim 1, wherein the set of configuration parameters further includes one or more of a set of wireless connectivity parameters and a set of access control parameters.

4. The method according to claim 1, wherein the system requirements are associated with one of the following: The battery capacity of the one partner device; The accuracy requirements of the one partner device; The communication protocol used by the one partner device; The regulatory requirements debugged to the one partner device; and The expected operating time of the one partner device.

5. The method according to claim 3, wherein The set of wireless connectivity parameters includes the conditions for removing the one partner device from the whitelist maintained for the analyte sensor system; and The analyte sensor system setting the set of configuration parameters or causing the modification to the set of configuration parameters according to the system requirements of the one partner device includes the analyte sensor system setting the conditions such that when the battery power of the one partner delivery device meets a threshold, the one partner device is to be removed from the whitelist.

6. The method according to claim 3, wherein The set of wireless connectivity parameters includes an advertisement structure; and The analyte sensor system setting the set of configuration parameters or causing the modification to the set of configuration parameters according to the system requirements of the one partner device includes the analyte sensor system using the diabetes management partner interface to set or modify the advertisement structure.

7. The method according to claim 3, wherein the set of access control parameters includes one or more of the following: the number of display devices to which the analyte sensor system can be connected; and the level of access or control that the analyte sensor system can give to one or more of the display devices.

8. The method according to claim 3, wherein the set of analyte data parameters includes a calibration period of the analyte sensor system; and the analyte sensor system setting or causing the modification of the set of configuration parameters according to the system requirements of the one partner device includes the analyte sensor system using the diabetes management partner interface to set or modify the calibration period.

9. The method according to claim 8, wherein the set of analyte data parameters includes a factory calibration code; the analyte sensor system receives an indication to use 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; and the analyte sensor system setting or causing the modification of the set of configuration parameters according to the system requirements of the one partner device includes the analyte sensor system using the diabetes management partner interface to set or modify the calibration period to zero or none.

10. The method according to claim 3, wherein the set of wireless connectivity parameters includes settings in a remote server, and the analyte sensor system setting or causing the modification of the set of configuration parameters according to the system requirements of the one partner device includes configuring the analyte sensor using the diabetes management partner interface to: use services provided through the remote server; in response to services provided through the remote server, transmit diabetes management feedback to one or more display devices connected to the analyte sensor system; and if the services provided through the remote server become unavailable, disable the services and send a relevant notification to the display devices connected to the analyte sensor system.

11. The method according to claim 1, further comprising: the analyte sensor system providing a bolus recommendation based on calculations performed using the bolus calculation parameters.

12. An analyte sensor system for wireless communication with a plurality of partner devices, wherein the analyte sensor system can be configured by using a diabetes management partner interface, the analyte sensor system comprises: an analyte sensor for generating analyte information; a transceiver configured to transmit and receive wireless signals; a memory for storing a set of configuration parameters used by the transceiver to transmit and receive the wireless signals; circuitry operatively coupled to the transceiver and the memory, and configured to cause the analyte sensor system to: Receive authorization to provide access to a set of configuration parameters to one of the partner devices via the diabetes management partner interface, where the set of configuration parameters includes a set of analyte data parameters, and the set of analyte data parameters includes bolus calculation parameters; and in response to an input received from the one partner device via the diabetes management partner interface, set the set of configuration parameters or cause a modification to the set of configuration parameters according to the system requirements of the partner device; The circuitry is further debugged to configure the analyte sensor system to provide access to the bolus calculation parameters to the one partner device using the diabetes management partner interface according to the system requirements of the partner device.

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

14. The analyte sensor system according to claim 12, wherein the set of configuration parameters further includes one or more of a set of wireless connectivity parameters and a set of access control parameters.

15. The analyte sensor system according to claim 12, wherein the system requirements are associated with one of the following: the battery capacity of the one partner device; the accuracy requirements of the one partner device; the communication protocol used by the one partner device; regulatory requirements for the one partner device that are debugged; and the expected operating time of the one partner device.

16. The analyte sensor system according to claim 14, wherein the set of wireless connectivity parameters includes conditions for removing the one partner device from a whitelist maintained for the analyte sensor system; and The circuitry is further debugged to configure the analyte sensor system to set the conditions such that when the battery level of the one partner delivery device meets a threshold, the one partner device is removed from the whitelist according to the system requirements of the one partner device.

17. The analyte sensor system according to claim 14, wherein the set of wireless connectivity parameters includes an advertisement structure; and The circuitry is further debugged to configure the analyte sensor system to set or modify the advertisement structure using the diabetes management partner interface.

18. The analyte sensor system according to claim 14, wherein the set of access control parameters includes one or more of the following: the number of display devices to which the analyte sensor system can connect; and the access or control level that the analyte sensor system can grant to one or more of the display devices.

19. The analyte sensor system according to claim 14, wherein the set of analyte data parameters includes the calibration period of the analyte sensor system; and The circuitry is further debugged to configure the analyte sensor system to use the diabetes The disease management partner interface sets or modifies the calibration period.

20. The analyte sensor system according to claim 19, wherein the set of analyte data parameters includes a factory calibration code; the circuitry is further debugged to cause the analyte sensor system to: receive an indication to use the factory calibration code from the one partner device using the diabetes management partner interface according to the system requirements of the one partner device; and set or modify the calibration period to zero or none using the diabetes management partner interface.

21. The analyte sensor system according to claim 14, wherein the set of wireless connectivity parameters includes settings in a remote server; the circuitry is further debugged to cause the analyte sensor system to configure the analyte sensor using the diabetes management partner interface to: use services provided through the remote server; transmit diabetes management feedback to one or more display devices connected to the analyte sensor system in response to services provided through the remote server; and if the services provided through the remote server become unavailable, disable the services and send a related notification to the display device connected to the analyte sensor system.

22. The analyte sensor system according to claim 12, wherein the circuitry is further debugged to cause the analyte sensor to provide a bolus recommendation based on calculations performed using the bolus calculation parameters.

23. A system for diabetes management, which comprises: one or more partner devices, the one or more partner devices being debugged to deliver insulin to a user; an analyte sensor system, the analyte sensor system being debugged to generate analyte information, the analyte sensor system including a set of configuration parameters for transmitting and receiving wireless signals, wherein the configuration parameters can be configured using a diabetes management partner interface; a display device, the display device being capable of connecting to the analyte sensor system and being debugged to display analyte information and provide authorization through the diabetes management partner interface to provide access to the set of configuration parameters to one of the partner devices in the partner device, wherein the set of configuration parameters includes a set of analyte data parameters, and the set of analyte data parameters includes bolus calculation parameters; and wherein the one partner device is debugged to set the set of configuration parameters or cause a modification to the set of configuration parameters using the diabetes management partner interface according to the system requirements of the partner device; wherein the one partner device is further debugged to configure the analyte sensor system to provide access to the bolus calculation parameters to the one partner device using the diabetes management partner interface according to the system requirements of the partner device.

24. The system according to claim 23, wherein the one partner device is an automatic insulin delivery device or a manual insulin delivery device.

25. The system according to claim 23, wherein the set of configuration parameters further includes one or more of a set of wireless connectivity parameters and a set of access control parameters.

26. The system according to claim 23, wherein the system requirements are associated with one of the following: The battery capacity of the one partner device; The accuracy requirements of the one partner device; The communication protocol used by the one partner device; The regulatory requirements for commissioning the one partner device; and The expected operating time of the one partner device.

27. The system according to claim 25, wherein The set of wireless connectivity parameters includes the conditions for removing the one partner device from the whitelist maintained for the analyte sensor system; and The one partner device is further commissioned to use the diabetes management partner interface to set or modify the conditions such that when the battery level of the one partner delivery device meets a threshold, the one partner device is removed from the whitelist.

28. The system according to claim 25, wherein The set of wireless connectivity parameters includes an advertising structure; and The one partner device is further commissioned to set or modify the advertising structure using the diabetes management partner interface.

29. The system according to claim 25, wherein the set of access control parameters includes one or more of the following: The number of display devices to which the analyte sensor system can connect; and The access or control level that the analyte sensor system can grant to one or more of the display devices.

30. The system according to claim 25, wherein The set of analyte data parameters includes the calibration period of the analyte sensor system; and The one partner device is further commissioned to use the diabetes management partner interface to set or modify the calibration period.

31. The system according to claim 30, wherein The set of analyte data parameters includes a factory calibration code; The one partner device is further commissioned to use the diabetes management partner interface: Provide an indication to the analyte sensor system to use the factory calibration code according to the system requirements of the one partner device; and Set or modify the calibration period to zero or none.

32. The system according to claim 25, wherein The set of wireless connectivity parameters includes settings in a remote server; The one partner device is further commissioned to use the diabetes management partner interface to configure the analyte sensor to: Use the services provided by the remote server; In response to the services provided by the remote server, transmit diabetes management feedback to a display device capable of connecting to the analyte sensor system; and If the service provided by the remote server becomes unavailable, the service is disabled and a relevant notification is sent to the display device capable of connecting to the analyte sensor system.

33. The system according to claim 23, wherein the one partner device is further configured to receive a bolus recommendation from the analyte sensor system based on a calculation performed using the bolus calculation parameter using the diabetes management partner interface.

Images