ES2888048T3 - A method for wireless communication of glucose data - Google Patents

Abstract

Method for wireless communication of glucose data, the method comprising: generating glucose data indicative of glucose concentration in a host using a transcutaneous glucose sensor (10); processing the generated glucose data using a sensor electronics module (12) integral with, or releasably attachable to, the transcutaneous glucose sensor (10) to generate sensor information; authenticating a display device (310) configured to display, or process and display, sensor information transmitted by the sensor electronics module (12), for a first wireless connection by exchanging authentication-related information between the sensor electronics module (12) sensor electronics and display device (310); after authenticating the display device (310), the sensor electronics module (12) periodically exchanging messages with the display device (310) to maintain a continuous connection through the first wireless connection; and transmitting, the sensor electronics module (12), encrypted sensor information to the display device (310) during the time the first wireless connection is maintained.

Description

DESCRIPTION

A method for wireless communication of glucose data

technical field

The present disclosure relates generally to monitoring analyte values received from a sensor. More particularly, the present disclosure relates to systems, methods, apparatus, and devices, for the communication of analyte (eg, glucose) data.

Background

Diabetes mellitus is a disorder in which the pancreas cannot create enough insulin (type I or insulin-dependent) and/or in which insulin is not effective (type 2 or non-insulin-dependent). In the diabetic state, the victim suffers from a high level of blood glucose, which causes a variety of physiological changes (kidney failure, skin ulcers or hemorrhage in the vitreous body of the eye) associated with the deterioration of small blood vessels. A hypoglycemic (low blood glucose) reaction can be induced by an overdose of insulin or after a normal dose of insulin or hypoglycemic agent accompanied by extraordinary exercise or insufficient food intake.

Conventionally, a person with diabetes wears a self-monitoring blood glucose (SMBG) monitor, which may require uncomfortable fingerstick methods. Due to the lack of comfort and convenience, a person with diabetes will typically only test their glucose level two to four times a day. Unfortunately, these time intervals are so far apart that the diabetic will likely be alerted to a hyperglycemic or hypoglycemic state too late, sometimes with dangerous side effects as a result. In fact, not only is a person with diabetes unlikely to take an SMBG value on time, they will also not know whether their BG is rising (high) or falling (low), due to limitations of conventional methods.

Accordingly, a variety of noninvasive, transdermal (eg, transcutaneous), and/or implantable electrochemical sensors are under development for continuously detecting and/or quantifying blood glucose values. These devices typically transmit raw or minimally processed data for further analysis on a remote device, which may include a display element. Transmission to wireless display devices can be wireless.

With respect to the wireless transmission of glucose data and other analytes collected using an implanted sensor, the battery life of the transmitter acting in conjunction with the sensor is typically a concern. In order to conserve battery life or increase the efficiency associated with the transmission of glucose and other analyte data, transmissions may need to be, for example, intermittent. However, the intermittent transmission of monitored data can introduce reliability problems. Therefore, in some cases reliability is sacrificed for battery life in conventional sensor systems.

US 2016/0210099 A1 relates to a continuous glucose monitor for wirelessly transmitting data related to glucose value to a plurality of display elements, as well as systems and methods for limiting the number of display devices that can be used. connect to a continuous glucose transmitter. In addition, security, including cryptographic hash techniques and a changing application key, may be used to provide secure communications between the continuous glucose transmitter and the display elements. The document also relates to a continuous glucose monitor and techniques for authenticating multiple displays, providing secure data transmissions to multiple displays, and coordinating the interaction of commands and data updates between multiple displays.

Summary

The present invention provides a method for wireless communication of glucose data as set forth in claim 1.

Brief description of the drawings

Additional aspects of the present disclosure will be more readily appreciated upon review of the detailed description of the various disclosed embodiments, described below, when taken in conjunction with the accompanying figures.

Figure 1A illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 1B illustrates aspects of an example system that can be used in connection with the implementation of disclosure accomplishments.

Figure 2A is a perspective view of an exemplary enclosure that may be used in connection with implementing embodiments of an analyte sensor system.

Figure 2B is a side view of an exemplary enclosure that may be used in connection with implementing embodiments of an analyte sensor system.

Figure 3A illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 3B illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 3C illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 3D illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 3E illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 3F illustrates aspects of an exemplary user interface according to embodiments of the disclosure.

Figure 3G illustrates aspects of an exemplary user interface according to embodiments of the disclosure.

Figure 4 is a block diagram illustrating aspects of an exemplary analyte sensor system according to embodiments of the disclosure.

Figure 5 is a block diagram illustrating aspects of an exemplary analyte sensor system according to embodiments of the disclosure.

Figure 6 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7A is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7B is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7C is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7D is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7E is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7F is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7G is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7H is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7J is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 7K is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 8 illustrates an exemplary structure for an alert message according to embodiments of the present disclosure. Figure 9 is a timing diagram illustrating the transmission of alert messages according to embodiments of the present disclosure.

Figure 10A illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 10B illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 10C illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 10D illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 10E illustrates aspects of an exemplary system that may be used in connection with implementing embodiments of the disclosure.

Figure 11 illustrates an example calculation module according to embodiments of the present disclosure.

Figure 12A is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 12B is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13A is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13B is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13C is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13D is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13E is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13F is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13G is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13H is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13J is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13K is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13L is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13M is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13N is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13P is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 13Q is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 14 is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 15A is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 15B is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 16A is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 16B is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 16C is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 17 is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 18 is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 19 is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

Figure 20 is an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the disclosure.

The figures are described in more detail in the description and the following examples are provided for illustration purposes only and merely represent typical embodiments or exemplary embodiments of the disclosure. The figures are not intended to be exhaustive or to limit the disclosure to the precise form disclosed. It is also to be understood that the disclosure may be practiced with modification or alteration and that the disclosure may be limited only by the claims and the equivalents thereof.

Detailed description

In a first aspect, a method of identifying a device for connection includes receiving, a display device, an input that identifies an analyte sensor system from among a set of analyte sensor systems. The method further includes selecting the display device, the analyte sensor system for connection, based on the input.

In certain implementations of the first aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the first aspect, the input is identification information associated with the analyte sensor system. The identification information may include a string of numbers associated with the analyte sensor system. In implementations, the entry uniquely identifies the analyte sensor system. In implementations, input is received from a user through a display device GUI.

In certain implementations of the first aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the first aspect, the method further includes displaying, via the GUI, a list of one or more sensor systems of analyte that can be discovered from among the set of analyte sensor systems. In implementations, selecting the display device, the analyte sensor system for connection is done in response to the user manually selecting the analyte sensor system from the list using the GUI and a touch screen interface of the device. display device. In implementations, the list includes respective identification information for one or more of the discoverable analyte sensor systems. In implementations, the identification information includes at least one of a graphic, a symbol, a code, and a character string.

In certain implementations of the first aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the first aspect, the input is based on one of an encoded element and an image. The encoded element can include capacitive ink, a barcode, a QR code, and a sticker. In implementations, receiving the display device input includes scanning the encoded item from the analyte sensor system or product container from the analyte sensor system.

In a second aspect, a mobile device is configured for wireless communication of analyte data. The mobile device includes a touch screen, a camera, a transceiver configured to transmit and receive wireless signals, and a processor operatively coupled to the touch screen, camera, and transceiver. The processor is configured to make the display device perform various operations. One such operation is receiving, via one or more of the touch screen and the camera, an input that identifies an analyte sensor system from among a set of analyte detection systems. Another such operation is to select the analyte sensor system for connection, based on the input.

In certain implementations of the second aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the second aspect, the processor is further configured to cause a display device GUI to present a list of one or more analyte sensor systems discoverable from the set of analyte sensor systems. In implementations, the processor is further configured to cause the touch screen to receive input manually from the user based on the list presented through the display device GUI.

In certain implementations of the second aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the second aspect, the processor is further configured to cause the display device's touch screen or camera to obtain the input from one or more than one encoded element and an image.

In a third aspect, a method of identifying a device for connection includes receiving, a display device, a first signal from one analyte sensor system of a plurality of analyte sensor systems. The first signal is received through a first link. The method further includes determining, the display device, a derivative of the first signal. Additionally, the method includes identifying, the display device, the analyte sensor system for selection, based on the derivative of the first signal

In certain implementations of the third aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the third aspect, identifying the analyte sensor system for selection includes comparing the derivative of the first signal with a first threshold. In implementations, identifying the analyte sensor system for selection further includes determining whether the derivative of the first signal at least meets the first threshold. In implementations, the method further includes selecting the analyte sensor system for connection based on determining that the derivative of the first signal at least meets the first threshold.

In certain implementations of the third aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the third aspect, the method further includes the display device receiving a second signal from the display system. analyte sensor. The signal can be received through a second link. In implementations, the method further includes determining, the display device, a derivative of the second signal. Additionally, the method may include selecting the analyte sensor system for connection based on the derivative of the second signal. In some cases, selecting the analyte sensor system for connection includes comparing the derivative of the second signal to a second threshold. Selecting the analyte sensor system for connection may further include determining whether the derivative of the second signal at least meets the second threshold. In implementations, selection of the analyte sensor system for connection is made in response to determining that the derivative of the second signal at least meets the second threshold.

In certain implementations of the third aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the third aspect, selecting the analyte sensor system for connection further includes comparing the derivative of the first signal with the second threshold; determining if the derivative of the first signal does not meet at least the second threshold. In implementations, selection of the analyte sensor system for connection is made in response to determining that the derivative of the second signal at least meets the second threshold and that the derivative of the first signal does not meet at least the second threshold. second threshold.

In certain implementations of the third aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the third aspect, selecting the analyte sensor system for connection includes comparing the derivative of the second signal with the first threshold. In implementations, selecting the analyte sensor system for connection further includes determining if the derived from the second signal does not meet at least the first threshold. In implementations, selection of the analyte sensor system for connection is made in response to determining that the derivative of the second signal does not meet at least the first threshold.

In certain implementations of the third aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the third aspect, the derivative of the first signal is based on a signal strength of the first signal. In some cases, the derivative of the first signal is a received signal strength indication ("RSSI") associated with the first signal. In some cases, the derivative of the second signal is based on a signal intensity of the second signal. The derivative of the second signal may include an RSSI associated with the second signal.

In certain implementations of the third aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the third aspect, the derivative of the first signal is based on a bit error rate ("BER") ) associated with the first signal. In some cases, the derivative of the second signal is based on a BER associated with the second signal. The derivative of the second signal may include a BER associated with the second signal.

In a fourth aspect, a mobile device is configured for wireless communication of analyte data. The mobile device includes a transceiver configured to transmit and receive wireless signals. The mobile device includes circuitry operatively coupled to the transceiver. In addition, the mobile device includes a non-transient computer-readable medium operatively coupled to the circuitry and storing instructions that, when executed, cause the display device to perform various operations. One such operation is receiving, via a first link, a first signal from one analyte sensor system of a plurality of analyte sensor systems. Another such operation is to determine a derivative of the first signal. Another such operation is to identify the analyte sensor system for selection, based on the derivative of the first signal.

In certain implementations of the fourth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fourth aspect, the non-transient computer-readable medium further stores instructions that, when executed, cause the display device perform additional operations. One such operation is to compare the derivative of the first signal with a first threshold. Another such operation is to determine if the derivative of the first signal at least meets the first threshold. Yet another such operation is to select the analyte sensor system for connection based on a determination that the derivative of the first signal at least meets the first threshold.

In certain implementations of the fourth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fourth aspect, the non-transient computer-readable medium further stores instructions that, when executed, cause the display device perform additional operations. One such operation is receiving a second signal from the analyte sensor system. Another such operation is to determine a derivative of the second signal. Yet another such operation is to select the analyte sensor system for connection, based on the derivative of the second signal. In implementations, another such operation is to compare the derivative of the second signal to a second threshold. In implementations, another such operation is to determine if the derivative of the second signal at least meets the second threshold. The display device may select the analyte sensor system for connection further based on a determination that the derivative of the second signal at least meets the second threshold.

In certain implementations of the fourth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fourth aspect, the non-transient computer-readable medium further stores instructions that, when executed, cause the display device perform additional operations. One such operation is to compare the derivative of the first signal with a second threshold. Another such operation is to determine if the derivative of the first signal does not meet at least the second threshold. In implementations, another such operation is to select the analyte sensor system for connection further based on a determination that the derivative of the first signal does not meet at least the second threshold.

In certain implementations of the fourth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fourth aspect, the non-transient computer-readable medium further stores instructions that, when executed, cause the display device perform additional operations. One such operation is to compare the derivative of the second signal with the first threshold. Another such operation is to determine if the derivative of the second signal does not meet at least the first threshold. Yet another such operation is to select the analyte sensor system for connection further based on a determination that the derivative of the second signal does not meet at least the first threshold.

In a fifth aspect, a method of identifying a device for connection includes receiving, a display device, a first signal from one analyte sensor system of a plurality of analyte sensor systems. The first signal is received through a first link. The method also includes obtaining, the display device, a derivative of the first signal. Further, the method includes identifying, the display device, the analyte sensor system for selection based on the derivative of the first signal meeting or above a lower threshold.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, the method further includes selecting the analyte sensor system for connection based on the derivative of the first signal meets or is above an upper threshold. In implementations, the method further includes the display device receiving a second signal from the analyte sensor system. The second signal can be received through a second link. In implementations, the method also includes obtaining, the display device, a derivative of the second signal. Selecting the analyte sensor system for connection may further be based on the derivative of the second signal being below the lower threshold.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, the method further includes the display device receiving a second signal from the display system. analyte sensor. In implementations, the second signal is received over a second link. In implementations, the second signal is received through the first link. In implementations, the method also includes obtaining, the display device, a derivative of the second signal. The method may also include selecting the display device, the analyte sensor system for connection, based on whether the derivative of the second signal meets or is above an upper threshold. In some cases, selecting the analyte sensor system for connection is further based on the derivative of the first signal not meeting or above the upper threshold.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, the method also includes generating an indication to configure the display according to a second link, based on where the derivative of the first signal is below the upper threshold. In implementations, the indication includes a communication representing an instruction to move the display device closer to the analyte sensor system. The method may also include providing the display device with the indication to a user of the display device. The indication comprises one or more of an audible communication, a visual communication and a tactile communication.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, the method also includes generating an indication to configure the display device according to the second link, based on where the derivative of the first signal meets or is above the upper threshold.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, the method includes the display device receiving a third signal from the sensor system of analyte, in which the third signal is received through a third link. In implementations, the method also includes obtaining, the display device, a derivative of the third signal. In addition, the method may include selecting the display device for the analyte sensor system to be turned on further based on the derivative of the third signal being below the lower threshold.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, the method includes the display device receiving a third signal from the sensor system of analyte, in which the third signal is received through a third link. In implementations, the method also includes obtaining, the display device, a derivative of the third signal. Selecting, the display device, the analyte sensor system for connection may further be based on the derivative of the third signal being below the lower threshold.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, the method also includes the display device receiving a second signal from the display system. analyte sensor, in which the second signal is received via a second link. In implementations, the method further includes obtaining, the display device, a derivative of the second signal. Additionally, the method may include selecting the display device and the analyte sensor system for connection based on a comparison of the derivative of the second signal and the derivative of the first signal. In implementations, selecting the analyte sensor system for connection is further based on the derivative of the first signal meeting or exceeding the upper threshold, where the derivative of the second signal is less than the derivative of the second signal. first sign. In implementations, selecting the analyte sensor system for connection is further based on the derivative of the second signal meeting or exceeding the upper threshold, where the derivative of the first signal is less than the derivative of the second signal.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, the method also includes the display device receiving a third signal from the display system. analyte sensor, in which the third signal is received via a third link. In implementations, the method further includes obtaining, the display device, a derivative of the third signal. Additionally, selecting, the display device, the analyte sensor system for connection may further be based on a comparison of the derivative of the third signal and the derivative of the second signal. In implementations of the method, the derivative of the second signal exceeds the upper threshold and the derivative of the third signal is less than the derivative of the second signal. In implementations of the method, the derivative of the second signal is below the upper threshold and the derivative of the third signal is greater than the derivative of the second signal.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, the method also includes the display device sending a first response signal to the display system. analyte sensor through the first link. In implementations, the method also includes obtaining, the display device, a derivative of the first response signal. Furthermore, identifying, the display device, the analyte sensor system for selection may further be based on a comparison of the derivative of the first signal and the derivative of the first response signal. In implementations, the method also includes the display device receiving the derivative of the first response signal from the analyte sensor system, wherein the derivative of the first response signal is generated by the analyte sensor system. analyte.

In certain implementations of the fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fifth aspect, each of the analyte sensor systems includes a trigger circuit that initiates transmission of warning signals after a predetermined amount of time from when a sensor is connected to a sensor electronics module of the analyte system. In implementations, the predetermined amount of time is common to analyte sensor systems.

In a sixth aspect, a mobile device is configured for wireless communication of analyte data. The mobile device includes a transceiver configured to transmit and receive wireless signals. The mobile device also includes circuitry operatively coupled to the transceiver. Additionally, the mobile device includes a non-transient computer-readable medium operatively coupled to the circuitry and storing instructions that, when executed, cause the display device to perform various operations. One such operation is receiving, via a first link, a first signal from one analyte sensor system of a plurality of analyte sensor systems. Another operation of this type is to obtain a derivative of the first signal. Yet another such operation is to identify the analyte sensor system for selection based on the derivative of the first signal meeting or above a lower threshold.

In certain implementations of the sixth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the sixth aspect, the non-transient computer-readable medium further stores instructions that, when executed, cause the display device perform additional operations. One such operation is to select the analyte sensor system for connection based on the derivative of the first signal meeting or above an upper threshold. One such operation is to receive, via a second link, a second signal from the analyte sensor system. Another such operation is to obtain a derivative of the second signal. Yet another such operation is to select the analyte sensor system for connection further based on whether the derivative of the second signal is below the lower threshold or meets or is above the upper threshold. Another such operation is to generate an indication to configure the display according to the second link, based on a determination that the derivative of the first signal is below the upper threshold. Yet another such operation is to generate an indication to configure the display according to the second link, based on a determination that the derivative of the first signal meets or is above the upper threshold.

In a seventh aspect, a method of identifying a device for connection includes receiving, for an analyte sensor system, a first signal from a display device of a plurality of display devices, wherein the first signal is received through a first link. The method also includes identifying the analyte sensor system and display device for selection based on a derivative of the first signal meeting or above a lower threshold.

In certain implementations of the seventh aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the seventh aspect, the method also includes selecting the display device for connection based on the derivative of the first signal meets or is above an upper threshold. In implementations, the method also includes the analyte sensor system receiving a second signal from the display device. The second signal can be received through a second link. Selecting the display device for connection may further be based on the derivative of the second signal being below the lower threshold.

In certain implementations of the seventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the seventh aspect, the method also includes receiving, the analyte sensor system, a second signal from the display device. The second signal can be received through a second link. The second signal can be received through the first link. In implementations, the method also includes obtaining, the analyte sensor system, a derivative of the second signal. In implementations, the method further includes selecting the analyte sensor system and display device for connection based on whether the derivative of the second signal meets or is above an upper threshold. Selecting the display device for connection may further be based on the derivative of the first signal not meeting or above the upper threshold.

In certain implementations of the seventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the seventh aspect, the method also includes generating an indication to configure the display according to a second link, based on where the derivative of the first signal is below the upper threshold. The indication may include a communication representing an instruction to move the display device closer to the analyte sensor system. In implementations, the method also includes sending the indication to the display device to provide the indication to a user of the display device. The indication may include one or more of an audible communication, a visual communication, and a tactile communication. In implementations, the method also includes generating an indication to configure the display according to the second link, based on the derivative of the first signal meeting or above the upper threshold.

In certain implementations of the seventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the seventh aspect, the method also includes receiving, the analyte sensor system, a third signal from the display device, in which the third signal is received via a third link. The method may also include obtaining, for the analyte sensor system, a derivative of the third signal. Selecting, the analyte sensor system, the display device for connection may further be based on the derivative of the third signal being below the lower threshold.

In certain implementations of the seventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the seventh aspect, the method also includes receiving, the analyte sensor system, a third signal from the display device, in which the third signal is received via a third link. In implementations, the method further includes determining, by the analyte sensor system, a derivative of the third signal. Selecting, the analyte sensor system, the display device for connection may further be based on the derivative of the third signal being below the lower threshold.

In certain implementations of the seventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the seventh aspect, the method also includes receiving, the analyte sensor system, a second signal from the display device. The second signal can be received through a second link. In implementations, the method also includes obtaining, the analyte sensor system, a derivative of the second signal.

In implementations, the method also includes selecting the analyte sensor system and display device for connection based on a comparison of the derivative of the second signal and the derivative of the first signal. Selecting the display for connection may further be based on the derivative of the first signal meeting or exceeding the upper threshold, where the derivative of the second signal is less than the derivative of the first signal. Selecting the display for connection may further be based on the derivative of the second signal meeting or exceeding the upper threshold, where the derivative of the first signal is less than the derivative of the second signal.

In certain implementations of the seventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the seventh aspect, the method also includes receiving, the analyte sensor system, a third signal from the display device. The third signal can be received through a third link. In implementations, the method also includes obtaining, for the analyte sensor system, a derivative of the third signal. Selecting, the analyte sensor system, the display device for connection may further be based on a comparison of the derivative of the third signal and the derivative of the second signal. In implementations, the derivative of the second signal meets or exceeds the upper threshold, and the derivative of the third signal is less than the derivative of the second signal. In implementations, the derivative of the second signal is below the upper threshold, and the derivative of the third signal is greater than the derivative of the second signal.

In certain implementations of the seventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the seventh aspect, the method also includes generating a representation of user input from an accelerometer. In implementations, selecting the display device for your connection is further based on the rendering of user input from the accelerometer. In implementations, the method also includes starting a prompt for the user to provide user input. User input may be based on the user physically coming into contact with the analyte sensor system.

In an eighth aspect, an analyte sensor system is configured for wireless communication of analyte data. The analyte sensor system includes an analyte sensor. The analyte sensor system includes a transceiver configured to transmit and receive wireless signals. The analyte sensor system also includes a processor operatively coupled to the analyte sensor and transceiver and configured to cause the analyte sensor system to perform various operations. One such operation is to receive, via a first link, a first signal from one of a plurality of displays. Another operation of this type is to obtain a derivative of the first signal. Another such operation is to identify the display for selection based on the derivative of the first signal meeting or above a lower threshold.

In certain implementations of the eighth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighth aspect, the processor is further configured to cause the analyte sensor system to perform various additional operations. One such operation is to select the display for connection based on the derivative of the first signal meeting or above an upper threshold. Another such operation is to receive, via a second link, a second signal from the display device. Still another such operation is to obtain a derivative of the second signal. Another such operation is to select the display device for connection further based on whether the derivative of the second signal is below the lower threshold or meets or is above the upper threshold. Another such operation is to generate an indication to configure the display according to the second link, based on a determination that the derivative of the first signal is below the upper threshold. Another such operation is to generate an indication to configure the display according to the second link, based on a determination that the derivative of the first signal meets or is above the upper threshold.

In a ninth aspect, a method of identifying a device for connection includes obtaining, for a display device, a derivative of a first signal received over a first link. The method also includes generating, the display device, an identification for selection based on the derivative of the first signal meeting or above a lower threshold.

In certain implementations of the ninth aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the ninth aspect, the method also includes generating a selection for its connection, based on the derivative of the first signal meets or is above an upper threshold. In implementations, the method further includes obtaining, for the display device, a derivative of a second signal received over a second link. Generating the selection for your connection may further be based on the derivative of the second signal being below the lower threshold.

In certain implementations of the ninth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the ninth aspect, the method also includes obtaining, the display device, a derivative of a second signal. The second signal can be received through a second link. The second signal can be received through the first link. In implementations, the method also includes generating the display device a selection for its connection based on the derivative of the second signal meeting or above an upper threshold. Generating the selection for your connection may further be based on the derivative of the first signal not meeting or above the upper threshold.

In certain implementations of the ninth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the ninth aspect, the method also includes generating an indication to configure the display according to a second link, based on where the derivative of the first signal is below the upper threshold. The indication may include a communication representing an instruction to move the display device closer to the analyte sensor system. In implementations, the method further includes sending the indication to the display device to provide the indication to a user of the display device. The indication may include one or more of an audible communication, a visual communication, and a tactile communication. In implementations, the method also includes generating an indication to configure the display according to a second link, based on the derivative of the first signal meeting or above the upper threshold.

In certain implementations of the ninth aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the ninth aspect, the method also includes obtaining, the display device, a derivative of a third signal received at through a third link. Generating, the display device, the selection for connection may further be based on the derivative of the third signal being below the lower threshold.

In certain implementations of the ninth aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the ninth aspect, the method also includes obtaining, the display device, a derivative of a third signal received at through a third link. Generate, the display device, selection for connection is further based on the derivative of the third signal meeting or above the upper threshold.

In certain implementations of the ninth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the ninth aspect, the method also includes obtaining, the display device, a derivative of a second signal received at through a second link. In implementations, the method also includes generating, the display device, a selection for its connection, based on a comparison of the derivative of the second signal and the derivative of the first signal. In implementations, generate, the display device selection for connection is further based on the derivative of the first signal meeting or exceeding the upper threshold, where the derivative of the second signal is less than the derived from the first signal. In implementations, generate, the display device selection for connection is further based on the derivative of the second signal meeting or exceeding the upper threshold, where the derivative of the first signal is less than the derived from the second signal.

In certain implementations of the ninth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the ninth aspect, the method also includes obtaining, the display device, a derivative of the third received signal at through a third link. Generating the selection for your connection may further be based on a comparison of the derivative of the third signal and the derivative of the second signal. In implementations of the method, the derivative of the second signal meets or exceeds the upper threshold; and the derivative of the third signal is less than the derivative of the second signal. In implementations of the method, the derivative of the second signal is below the upper threshold, and the derivative of the third signal is greater than the derivative of the second signal.

In certain implementations of the ninth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the ninth aspect, the method also includes receiving a representation of user input in an accelerometer. In implementations, generating the selection for your connection is also based on the rendering of user input. In implementations, the method also includes displaying a prompt for the user to provide user input to the analyte sensor system. User input may be based on the user touching the analyte sensor system.

In certain implementations of the ninth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the ninth aspect, the method also includes prompting the display device to physically contact the user with an analyte sensor system in order to trigger the analyte sensor system to send the first signal to the display device.

In a tenth aspect, a mobile device is configured for wireless communication of analyte data. The mobile device includes a transceiver configured to transmit and receive wireless signals. The mobile device also includes circuitry operatively coupled to the transceiver. In addition, the mobile device includes a non-transient computer-readable medium operatively coupled to the circuitry and storing instructions that, when executed, cause the display device to perform various operations. One such operation is to obtain a derivative of a first signal received through a first link. Another such operation is to generate an identification for selection based on a derivative of the first signal meeting or above a lower threshold.

In certain implementations of the tenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the tenth aspect, the non-transient computer-readable medium further stores instructions that, when executed, cause the mobile device perform various additional operations. One such operation is to generate a selection for its connection, based on the derivative of the first signal meeting or above an upper threshold. Another such operation is to derive a derivative of a second signal received through a second link. Yet another such operation is to generate the selection for connection further based on the derivative of the second signal being below the lower threshold or meeting or above the upper threshold. Another such operation is to generate the selection for connection further based on the fact that the derivative of the first signal does not meet or is above the upper threshold. Another such operation is to obtain a derivative of a third signal received through a third link. Yet another such operation is to generate the selection for connection further based on whether the derivative of the third signal meets or is above the upper threshold or is below the lower threshold.

In certain implementations of the tenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the tenth aspect, the non-transient computer-readable medium further stores instructions that, when executed, cause the mobile device perform various additional operations. One such operation is to derive a derivative of a second signal received over a second link. Another such operation is to generate the selection for your connection based on a comparison of the derivative of the second signal with the derivative of the first signal. Another such operation is to obtain a derivative of a third signal received through a third link. Still another such operation is to generate the selection for its connection further based on a comparison of the derivative of the third signal with that of the second signal.

In certain implementations of the tenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the tenth aspect, the non-transient computer-readable medium further stores instructions that, when executed, cause the mobile device perform various additional operations. One such operation is receiving a representation of user input at the accelerometer. Another such operation is to generate the selection for your connection further based on a comparison of the representation of the user input.

In an eleventh aspect, a method of identifying a device for connection includes obtaining, for a display device, a derivative of a first signal received over a first link. The method also includes obtaining, the display device, a derivative of a second signal received through a second link. Additionally, the method includes generating, the display device, a selection for its connection, based on a comparison of the derivative of the first signal with the derivative of the second signal.

In certain implementations of the eleventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eleventh aspect, the method also includes calculating a difference between the derivative of the first signal and the derivative of the second signal. In implementations, the method also includes generating the comparison by comparing the difference to a predetermined value.

In certain implementations of the eleventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eleventh aspect, the method also includes calculating a difference between the derivative of the first signal and the derivative of the second signal. In implementations, the method also includes generating the comparison by comparing an absolute value of the difference to a predetermined value.

In certain implementations of the eleventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eleventh aspect, the method also includes obtaining, the display device, a derivative of a third signal received at through a third link. In implementations, generate, the display device, the selection for its connection is further based on a comparison of the second derivative with the third derivative.

In certain implementations of the eleventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eleventh aspect, the method also includes calculating a first difference between the derivative of the first signal and the derivative of the second signal. In implementations, the method further includes obtaining, for the display device, a derivative of a third signal received through a third link. In implementations, the method includes calculating a second difference between the derivative of the third signal and the derivative of the second signal. In implementations, generate, the display device, the selection for its connection is further based on a comparison of the first difference with the second difference.

In a twelfth aspect, a mobile device is configured for wireless communication of analyte data. The mobile device includes a transceiver configured to transmit and receive wireless signals. The mobile device also includes circuitry operatively coupled to the transceiver. In addition, the mobile device includes a non-transient computer-readable medium operatively coupled to the circuitry and storing instructions that, when executed, cause the mobile device to perform various operations. One such operation is to obtain a derivative of a first signal received through a first link. Another such operation is to derive a derivative of a second signal received through a second link. Yet another such operation is to generate a selection for your connection, based on a comparison of the derivative of the first signal and the derivative of the second signal.

In certain implementations of the twelfth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twelfth aspect, the non-transient computer-readable medium further stores instructions that, when executed, do mobile device to perform various additional operations. One such operation is to compute a difference between the derivative of the first signal and the derivative of the second signal. Another such operation is to generate the comparison by comparing the difference to a predetermined value.

In a twelfth aspect, a method of identifying a device for connection includes establishing, a display device of a set of display devices, a connection with an analyte sensor system of a set of analyte sensor systems. The method further includes generating, the display device, a confirmation for its connection to the analyte sensor system based on a connection duration exceeding a predetermined amount of time.

In a thirteenth aspect, a mobile device of a set of mobile devices is configured for wireless communication of analyte data. The mobile device includes a transceiver configured to transmit and receive wireless signals. The mobile device also includes circuitry operatively coupled to the transceiver. Additionally, the mobile device includes a non-transient computer-readable medium operatively coupled to the circuitry and storing instructions that, when executed, cause the mobile device to perform various operations. One such operation is establishing a connection with one analyte sensor system of a set of analyte sensor systems. Another such operation is to generate a confirmation for its connection to the analyte sensor system based on a connection duration exceeding a predetermined amount of time.

In a fourteenth aspect, a method of identifying a device for connection includes operating in one of a plurality of ways to generate a selection for connection between a display device and an analyte sensor system. Operating in a first mode of the plurality of modes includes receiving an input relating to the analyte sensor system that identifies the analyte sensor system from among a set of analyte sensor systems. Operating in the first mode also includes generating the selection for connection to the analyte sensor system based on the input. Operating in a second mode of the plurality of modes includes obtaining a derivative of a first signal received over a first link. Operating in the second mode also includes generating an identifier for selection based on the derivative of the first signal. Operating in the second mode also includes generating a selection for your connection based on the identification for your selection and one or more than one derived from a second signal and user input. Operating in a third mode of the plurality of modes includes forming a connection between the display device and the analyte sensor system. Operating in the third mode also includes generating an acknowledgment for your connection based on maintaining the connection for at least a predetermined amount of time.

In certain implementations of the fourteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fourteenth aspect, the entry relating to the analyte sensor system that identifies the analyte sensor system includes one de: an identification number for the analyte sensor system; a character identifier for the analyte sensor system; a captured coded element; a captured image; and input selecting the analyte sensor system from a list.

In certain implementations of the fourteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fourteenth aspect, the derivative of the first signal is based on an RSSI of the first signal, and the derivative of the second signal is based on an RSSI of the second signal. In implementations, the method also includes calculating a difference between the derivative of the first signal and the derivative of the second signal. Furthermore, the method includes comparing the difference to a threshold. The method may also include, if the difference exceeds the threshold, confirming the selection for its connection.

In certain implementations of the fourteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the fourteenth aspect, the method also includes presenting an instruction to the user to provide input to a system accelerometer analyte sensor system for the analyte sensor system to initiate transmission of the first signal.

In a fifteenth aspect, a system for identifying a device for connection includes an analyte sensor system. The system also includes a mobile device. The analyte sensor system and the mobile device are configured to operate in one of a plurality of modes to generate a selection for connection between the mobile device and the analyte sensor system. For operation in a first of the plurality of modes, the mobile device is configured to perform various operations. One such operation is receiving an analyte sensor system input that identifies the analyte sensor system from a set of analyte sensor systems. Another such operation is to generate the selection for connection to the analyte sensor system based on the input. For operation in a second mode of the plurality of modes, the mobile device is configured to perform various operations. One such operation is to obtain a derivative of a first signal received through a first link. Another such operation is to generate an ID for selection based on the derivative of the first signal. Yet another such operation is to generate a selection for your connection based on the identification for your selection and one or more than one derived from a second signal and user input. For operation in a third mode of the plurality of modes, the mobile device is configured to perform various operations. One such operation is to form a connection between the display device and the analyte sensor system. Another such operation is to generate an acknowledgment for your connection based on maintaining the connection for at least a predetermined amount of time.

In a sixteenth aspect, a method for wireless communication of analyte data includes establishing a first connection between an analyte sensor system and a display device. The method also includes, during the first connection, exchanging authentication related information between the analyte sensor system and the display device. Information related to authentication includes an application key. The method further includes the analyte sensor system transmitting an encrypted analyte value to the display device. The encrypted analyte value has been generated based on the application key.

In certain implementations of the sixteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the sixteenth aspect, the method also includes modifying the application key in response to one or more of: for a predetermined amount of time; reboot the analyte sensor system or display device; a trigger factor related to another device attempting to connect to the analyte sensor system; and user input.

In certain implementations of the sixteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the sixteenth aspect, the application key was received by the display device from a server. In implementations, for each analyte sensor system, the server associates the application key with identification information for the analyte sensor system. In implementations, the application key is received by the display device from the server in response to the display device providing the server with identification information for the analyte sensor system.

In a seventeenth aspect, an analyte sensor system is configured for wireless communication of analyte data. The analyte sensor system includes an analyte sensor. The analyte sensor system includes a transceiver configured to transmit and receive wireless signals. The analyte sensor system also includes a processor operatively coupled to the analyte sensor and transceiver and configured to cause the analyte sensor system to perform various operations. One such operation is to establish a first connection between the analyte sensor system and a display device. Another such operation is, during the first connection, to exchange authentication related information between the analyte sensor system and the display device, wherein the authentication related information includes an application key. Another such operation is making a determination as to whether authentication was performed during the first interval. Yet another such operation is to transmit an encrypted analyte value to the display device, where the encrypted analyte value was generated based on the application key. In implementations, the application key was received from a server in response to the server being provided with the identification information for the analyte sensor system.

In an eighteenth aspect, a method for wirelessly communicating analyte data includes receiving a proposal for a connection parameter. The proposal includes one or more proposed values for the connection parameter. The method also includes determining whether the proposal is acceptable. The method includes generating a response to the proposal, based on determining whether the proposal is acceptable.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the method also includes modifying a connection between a display device and an analyte sensor system based on an acceptable proposed value of the one or more proposed values, if the response indicates an acceptance of the acceptable proposed value.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the method also includes establishing a connection between a display device and the analyte sensor system based on an acceptable proposed value of the one or more proposed values, if the response indicates an acceptance of the acceptable proposed value.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the eighteenth aspect, the method also includes sending a counterproposal, if the response indicates a preference of a value for the connection parameter other than the proposed values for the connection parameter. The counterproposal comprises one or more counterproposal values for the connection parameter.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the method also includes receiving a response to the counterproposal. In implementations, the method also includes modifying a connection between a display device and an analyte sensor system based on at least one of the counterproposal values, if the response to the counterproposal indicates an acceptance of one or more of the counterproposal values.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the method also includes receiving a response to the counterproposal. In implementations, the method further includes terminating a connection between a display device and an analyte sensor system, if the response to the counterproposal indicates a rejection of the counterproposal values.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the method also includes receiving a response to the counterproposal. In implementations, the method further includes establishing a connection between a display device and an analyte sensor system based on at least one of the counterproposal values, if the response to the counterproposal indicates an acceptance of one or more of the counterproposal values. counter proposal.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the method also includes receiving a response to the counterproposal. In implementations, the method further includes generating a negative connection decision, if the response to the counterproposal indicates a rejection of the counterproposal values.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the connection parameter is one of a connection interval, a slave latency, and a time. waiting for supervision.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the proposal is based on an expected operating time of the analyte sensor system.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the approach is based on a user's glucose level.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the eighteenth aspect, the proposal is based on one or more of a quality of service, a time of day, a location or battery conditions.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the method also includes requesting a connection according to a first connection model. In implementations, the method further includes requesting a connection according to a second connection model, in response to determining that the proposal is not acceptable.

In certain implementations of the eighteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the eighteenth aspect, the method also includes terminating a connection between a display device and an analyte sensor system , in response to determining that the proposal is not acceptable. In implementations, the method also includes providing a notification related to terminating the connection.

In a nineteenth aspect, an analyte sensor system is configured for wireless communication of analyte data. The analyte sensor system includes an analyte sensor. The analyte sensor system includes a transceiver configured to transmit and receive wireless signals. The analyte sensor system includes a processor operatively coupled to the analyte sensor and transceiver and configured to cause the analyte sensor system to perform various operations. One such operation is receiving a proposal for a connection parameter, where the proposal comprises one or more proposed values for the connection parameter. Another such operation is determining whether the proposal is acceptable. Yet another such operation is generating a response to the proposal, based on a determination that the proposal is acceptable.

In certain implementations of the nineteenth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the nineteenth aspect, the processor is further configured to perform various additional operations. One such operation is to modify a connection between a display device and the analyte sensor system based on a value acceptable proposed value of one or more proposed values, if the response indicates an acceptance of the acceptable proposed value. Another such operation is to establish a connection between a display device and the analyte sensor system based on an acceptable proposed value of the one or more proposed values, if the response indicates an acceptance of the acceptable proposed value. Another such operation is to send a counterproposal, if the response indicates a preference for a value for the connection parameter other than the proposed values for the connection parameter. The counterproposal may include one or more counterproposal values for the connection parameter. Another such operation is receiving a response to the counterproposal. Another such operation is to modify a connection between a display device and the analyte sensor system based on at least one of the counterproposal values, if the response to the counterproposal indicates an acceptance of one or more of the counterproposal values. . Another such operation is to terminate a connection between a display device and the analyte sensor system, if the response to the counterproposal indicates a rejection of the counterproposal values. Another such operation is to establish a connection between a display device and the analyte sensor system based on at least one of the counterproposal values, if the response to the counterproposal indicates an acceptance of one or more of the counterproposal values. . Another such operation is requesting a connection according to a first connection model. Another such operation is to request a connection according to a second connection model, in response to a determination that the proposal is not acceptable.

In a twentieth aspect, a method for wireless communication of analyte data includes, in response to input from an application running on a display device, sending the display device to an analyte sensor system a message comprising a value for a connection parameter. The method also includes receiving, the display device, from the analyte sensor system the value for the connection parameter. Additionally, the method includes applying, a display device operating system, the value for the connection parameter, based on a determination that the value is acceptable.

In certain implementations of the twentieth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twentieth aspect, the determination that the value is acceptable is received by the display from the system of analyte sensor.

In a twenty-first aspect, a method for wireless communication of analyte data includes operating in a first mode. Operating in the first mode includes an analyte sensor system periodically exchanging messages with a display device such that the analyte sensor system and the display device remain connected. Operating in the first mode includes, while the analyte sensor system and display device remain connected, the analyte sensor system transmitting the analyte data to the display device. The method also includes operating in a second mode. Operating in the second mode includes periodically establishing a connection between the analyte sensor system and the display device. Operating in the second mode includes, while the connection is established, transmitting the analyte data to the display device.

In certain implementations of the twenty-first aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-first aspect, the method includes switching from operating in the first mode to operating in the second mode or switching from run in the second mode to run in the first mode. In implementations, switching is based on user input. In implementations, switching is based on one or more switching criteria. In implementations, the switch criteria include a type of display device; user information; the availability of display devices for your connection; a priority scheme regarding display devices; quality of service; battery life; time of the day; and a location.

In certain implementations of the twenty-first aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-first aspect, the method further includes receiving an indication related to battery management; wherein the switching is performed based on the indication.

In certain implementations of the twenty-first aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-first aspect, the method also includes presenting a notification to the user related to switching.

In certain implementations of the twenty-first aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-first aspect, while the analyte sensor system and the display device remain connected, transmit, the system From the analyte sensor, the analyte data to the display device is made when the analyte data becomes available for transmission.

In a twenty-second aspect, an analyte sensor system is configured for wireless communication of analyte data. The analyte sensor system includes an analyte sensor. The analyte sensor system includes a transceiver configured to transmit and receive wireless signals. The analyte sensor system includes a processor operatively coupled to the analyte sensor and transceiver and configured to cause the analyte sensor system to perform various operations. One such operation is to operate in a first mode. For operation in the first mode, the analyte sensor system is configured to perform various operations. One such operation for the first mode is to periodically exchange messages with a display device such that the analyte sensor system and the display device remain connected. Another such operation for the first mode is, while the analyte sensor system and the display device remain connected, to transmit the analyte data to the display device. Another such operation is to operate in a second mode. For operation in the second mode, the analyte sensor system is configured to perform various operations. One such operation for the second mode is to periodically establish a connection with a display device. Another such operation for the second mode is, while the connection is established, to transmit the analyte data to the display device. Another such operation is to switch between operation in the first mode and operation in the second mode.

In a twenty-third aspect, a method for wireless communication of analyte data includes an analyte sensor system periodically exchanging messages with a display device such that the analyte sensor system and the display device maintain a connection. . The method also includes the analyte sensor system transmitting the analyte data to the display device while the analyte sensor system and the display device maintain the connection.

In certain implementations of the twenty-third aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-third aspect, the method also includes sending, the analyte sensor system, a proposal for a set of connection parameters to the display device, in response to receiving a connection request from the display device. The set of connection parameters can include a connection interval, slave latency, and monitor timeout. In implementations, the method also includes receiving a connection decision from the display device; in which the connection decision is based on the proposal. In implementations, exchanging messages periodically is done based on the set of connection parameters, in response to the connection decision comprising an acceptance of the proposal.

In certain implementations of the twenty-third aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the twenty-third aspect, the method also includes terminating the connection, based on a violation of one or more of the parameters of connection. In implementations, the method also includes the analyte sensor system transmitting warning messages in response to terminating the connection.

In certain implementations of the twenty-third aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-third aspect, the method also includes requesting to modify one or more of the connection parameters, in response to a violation of one or more of the connection parameters.

In a twenty-fourth aspect, an analyte sensor system is configured for wireless communication of analyte data. The analyte sensor system includes an analyte sensor. The analyte sensor system includes a transceiver configured to transmit and receive wireless signals. The analyte sensor system also includes a processor operatively coupled to the analyte sensor and transceiver and configured to cause the analyte sensor system to perform various operations. One such operation is to periodically exchange messages with a display device such that the analyte sensor system and the display device maintain a connection. One such operation is to transmit the analyte data to the display device while the analyte sensor system and the display device remain connected.

In a twenty-fifth aspect, a method for wireless communication of analyte data includes establishing a connection between an analyte sensor system and a display device. The method also includes receiving a set of features associated with the analyte sensor system. The features are arranged in a sequence. The method also includes sending the analyte sensor system a request to read one or more of the features in a different order of sequence.

In certain implementations of the twenty-fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-fifth aspect, the request to read one or more of the features includes a request to read a glucose value Estimate.

In certain implementations of the twenty-fifth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-fifth aspect, the method also includes performing a feature of the feature set. In implementations, the feature is associated with reading the estimated glucose value. In implementations, the feature is performed without having performed one or more other features preceding the feature in the sequence.

In a twenty-sixth aspect, a mobile device is configured for wireless communication of analyte data. The mobile device includes a transceiver configured to transmit and receive wireless signals. The mobile device includes circuitry operatively coupled to the transceiver. And the mobile device includes a non-transient computer-readable medium operatively coupled to the circuitry and storing instructions that, when executed, cause the mobile device to perform various operations. One such operation is to establish a connection with an analyte sensor system. Another such operation is receiving a set of features associated with the analyte sensor system. The features may be arranged in a sequence. Another such operation is to send to the analyte sensor system a request to read one or more of the features in a different order of sequence.

In a twenty-seventh aspect, a method for wireless communication of analyte data includes obtaining a derivative of a first signal received over a first link. The method also includes generating an identifier for selection based on the derivative of the first signal. The method also includes obtaining a derivative of a second signal received through a second link. Furthermore, the method includes generating a selection for its connection, based on the derivative of the second signal. The method includes establishing a connection between a display device and an analyte sensor system, based on selection for connection. And the method includes periodically exchanging messages to maintain the connection.

In certain implementations of the twenty-seventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-seventh aspect, the method also includes the analyte sensor system transmitting the analyte data to the device while the analyte sensor system and display device maintain connection. In implementations, the method also includes receiving a connection decision from the display device, where the connection decision is based on the proposal.

In certain implementations of the twenty-seventh aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-seventh aspect, the method also includes sending, the analyte sensor system, a proposal for a set of connection parameters to the display device, in response to receiving a connection request from the display device.

In certain implementations of the twenty-seventh aspect, which may be generally applicable but are also particularly applicable to any other implementation of the twenty-seventh aspect, periodically exchanging messages is performed based on the set of connection parameters, in response to the connection decision comprises an acceptance of the proposal.

In a twenty-eighth aspect, a method for wireless communication of analyte data includes authenticating a display device for a first connection by exchanging authentication-related information between an analyte sensor system and the display device. The method also includes, based on authenticating the display device, the analyte sensor system periodically exchanging messages with the display device to maintain the first connection. Further, the method includes the analyte sensor system transmitting encrypted analyte data to the display device during the time the first connection is maintained.

In certain implementations of the twenty-eighth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-eighth aspect, the method also includes terminating the first connection. In implementations, the method also includes establishing a second connection between the analyte sensor system and the display device. In implementations, the method also includes the analyte sensor system periodically exchanging messages with the display device to maintain the second connection. In implementations, the method also includes the analyte sensor system transmitting encrypted analyte data to the display device for as long as the second connection is maintained. For the second connection, in some cases, the periodic exchange of the messages and the transmission of encrypted analyte data is based on authenticating the display device for the first connection.

In a twenty-ninth aspect, a method for wireless communication of analyte data between a display device and one or more analyte sensor systems includes obtaining, the display device, a derivative of a first signal received from a first system from the one or more analyte sensor systems or from one or more of the analyte sensor systems other than the first analyte sensor system. The method further includes generating, the display device, a selection for connection to the first analyte sensor system using the derivative of the first signal and a condition. Furthermore, the method includes establishing a first connection between the display device and the first analyte sensor system using the selection for their connection. The first connection is established if, for an amount of time, the display device does not receive an alert message from one or more analyte sensor systems other than the first analyte sensor system, or the display device does not receive a derivative of a second signal that satisfies the condition. The second signal is received from the one or more analyte sensor systems other than the first analyte sensor system.

In certain implementations of the twenty-ninth aspect, which may be generally applicable but are also particularly applicable in connection with any other implementation of the twenty-ninth aspect, the method also includes obtaining a derivative of a received signal from a second sensor system of one of the one or more analyte sensor systems other than the first analyte sensor system. In implementations, the method also includes establishing a second connection between the display device and the second analyte sensor system using at least the derivative of the signal received from the second analyte sensor system.

In a thirtieth aspect, a method for wireless communication of analyte data includes a display device receiving warning messages from a number of analyte sensor systems. The number is two or more. If the number does not exceed a threshold, the method includes additional operations, as follows. The method may further include obtaining, the display device, respective derivatives of signals received from the number of analyte sensor systems. The method may also include the display device determining whether any one of the derivatives satisfies a condition for an amount of time. Additionally, the method may include, in response to the display device determining that a first derivative of the derivatives satisfies the condition for the amount of time, generating the display device a selection for connection to a first sensor system of analyte from the number of analyte sensor systems. The first analyte sensor system sends the signal used to obtain the first derivative. Furthermore, the method may include establishing a first connection between the display device and the first analyte sensor system using the selection for their connection.

In certain implementations of the thirtieth aspect, which may be generally applicable but are also particularly applicable in relation to any other implementation of the thirtieth aspect, if the number exceeds the threshold, the method includes additional operations, as follows. The method may include providing the display device with an alert to a user of the display device, wherein the alert is related to a connection establishment. The method may further include establishing a second connection between the display device and one of the analyte sensor systems selected for connection using an input received by the display device in response to the prompt.

Embodiments of the present disclosure are a method for wireless communication of analyte data. In various installations described herein, the analyte data is glucose data generated by an analyte sensor system configured to interface with display devices and the like. Implementing aspects of the present disclosure, as described in detail herein, can reduce the power consumption of the analyte sensor system by increasing the efficiency of the analyte sensor system with respect to wireless communications of the analyte sensor system and other devices. Furthermore, implementing aspects of the present disclosure may also allow for reduced power consumption while maintaining and/or improving performance with respect to reliability, speed, and accuracy of wireless communications, as well as the connection protocols associated with wireless communications. themselves. Additionally, in some cases, power consumption may be less critical than other aspects of performance (eg, reliability and/or latency), and in such cases, different connection modes may be employed to increase performance. In particular, aspects of the disclosure relate to, for example, authentication and encryption, connection and synchronization protocols for devices, structure and content of prompt messages, and device pairing.

Details of some exemplary embodiments of the method of the present disclosure are set forth in this description and, in some cases, in other parts of the disclosure. Other features, objects, and advantages of the disclosure will become apparent to one skilled in the art upon examination of the present disclosure, description, figures, examples, and claims. All such additional systems, methods, devices, features, and advantages are intended to be included within this description, be within the scope of this disclosure, and be protected by one or more of the appended claims.

A. Overview

In some implementations, a system for continuous measurement of an analyte in a host is described. The system may include: a continuous analyte sensor configured to continuously measure a concentration of the analyte in the host, and a sensor electronics module physically connected to the continuous analyte sensor during sensor use. In certain implementations, the sensor electronics module includes electronics configured to process a data stream associated with an analyte concentration measured by the continuous analyte sensor, in order to generate sensor information including raw sensor data, data transformed sensor data and/or any other sensor data, for example. The sensor electronics module may be further configured to generate sensor information that is customized for respective displays, such that different displays may receive different sensor information.

The term "analyte" as used herein is a broad term and should be assigned its common and usual meaning to one of ordinary skill in the art (and should not be limited to any special or personalized meaning). and further refers, without limitation, to a chemical substance or constituent in a biological fluid (eg, blood, interstitial fluid, cerebrospinal fluid, lymphatic fluid, or urine) that can be analyzed. Analytes can include naturally occurring substances, man-made substances, metabolites, and/or reaction products. In some embodiments, the analyte for measurement by the sensor heads, devices, and methods is an analyte. However, other analytes are also contemplated, including, but not limited to, acarboxyprothrombin; acylcarnitine; adenine phosphoribosyl transferase; adenosine deaminase; albumin; alpha-fetoprotein; amino acid profiles (arginine (Krebs cycle), histidine/urocanic acid, homocysteine, phenylalanine/tyrosine, tryptophan); androstenedione; antipyrine; arabinitol enantiomers; arginase; benzoylecgonine (cocaine); biotinidase; biopterin; C-reactive protein; carnitine; carnosinase; CD4; ceruloplasmin; chenodeoxycholic acid; chloroquine; cholesterol; cholinesterase; conjugated 1-p-hydroxy-cholic acid; cortisol; creatine kinase; creatine kinase MM isoenzyme; cyclosporin A; d-penicillamine; des-ethylchloroquine; dehydroepiandrosterone sulfate; DNA (acetylator polymorphism, alcohol dehydrogenase, alpha-1-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, sexual differentiation, 21-deoxycortisol); desbutylhalofantrine; dihydropteridine reductase; diphtheria/tetanus antitoxin; erythrocyte arginase; erythrocyte protoporphyrin; esterase D; fatty acids/acylglycines; free p human chorionic gonadotropin; free erythrocyte porphyrin; free thyroxine (FT4); free triiodothyronine (FT3); fumarylacetoacetase; galactose/gal-1-phosphate; galactose-1-phosphate uridyltransferase; gentamicin; analyte-6-phosphate dehydrogenase; glutathione; glutathione peroxidase; glycocholic acid; glycosylated hemoglobin; halofantrine; hemoglobin variants; hexosaminidase A; human erythrocyte carbonic anhydrase 1; 17-alpha-hydroxyprogesterone; hypoxanthine phosphoribosyl transferase; immunoreactive trypsin; lactate; lead; lipoproteins ((a), B/A-1, p); lysozyme; mefloquine; netilmicin; phenobarbitone; phenytoin; phytanic/pristanic acid; progesterone; prolactin; prolidase; purine nucleoside phosphorylase; quinine; reverse tri-iodothyronine (rT3); selenium; serum pancreatic lipase; sisomicin; somatomedin C; specific antibodies (adenovirus, anti-nuclear antibody, anti-zeta antibody, arbovirus, Aujeszky's disease virus, dengue virus, Dracunculus medinensis, Echinococcus granulosus, Entamoeba histolytica, enterovirus, Giardia duodenalisa, Helicobacter pylori, hepatitis B virus , herpes virus, HIV-1, IgE (atopic disease), influenza virus, Leishmania donovani, leptospira, measles/mumps/rubella, Mycobacterium leprae, Mycoplasma pneumoniae, myoglobin, Onchocerca volvulus, parainfluenza virus, Plasmodium falciparum, poliovirus, Pseudomonas aeruginosa , respiratory syncytial virus, rickettsia (Japanese river fever), Schistosoma mansoni, Toxoplasma gondii, Trepenoma pallidium, Trypanosoma cruzi/rangeli, vesicular stomatitis virus, Wuchereria bancrofti, yellow fever virus); specific antigens (hepatitis B virus, HIV-1); succinylacetone; sulfadoxine; theophylline; thyrotropin (TSH); thyroxine (T4); thyroxine binding globulin; trace elements; transferrin; UDP-galactose-4-epimerase; urea; uroporphyrinogen I synthase; Vitamin A; white blood cells and zinc protoporphyrin. Salts, sugar, protein, fat, vitamins, and hormones that occur naturally in the blood or interstitial fluids may also constitute analytes in certain embodiments. The analyte may be naturally present in the biological fluid, for example, a metabolic product, a hormone, an antigen, an antibody, and the like. Alternatively, the analyte may be introduced into the body, for example, an imaging contrast agent, a radioisotope, a chemical agent, a fluorocarbon-based synthetic blood, or a drug or pharmaceutical composition, including, but not limited to , insulin; ethanol; cannabis (marijuana, tetrahydrocannabinol, hashish); inhaled products (nitrous oxide, amyl nitrite, butyl nitrite, chlorohydrocarbons, hydrocarbons); cocaine (crack cocaine); stimulants (amphetamines, methamphetamines, Ritalin, Cylert, Preludin, Didrex, PreState, Voranil, Sandrex, Plegine); depressants (barbiturates, methaqualone, tranquilizers such as Valium, Librium, Miltown, Serax, Equanil, Tranxene); hallucinogens (phencyclidine, lysergic acid, mescaline, peyote, psilocybin); Narcotics (Heroin, Codeine, Morphine, Opium, Meperidine, Percocet, Percodan, Tussionex, Fentanyl, Darvon, Talwin, Lomotil); synthetic drugs (analogs of fentanyl, meperidine, amphetamines, methamphetamines, and phencyclidine, eg, ecstasy); anabolic steroids and nicotine. Metabolic products of drugs and pharmaceutical compositions are also contemplated analytes. Analytes such as neurochemicals and other chemicals generated within the body, such as, for example, ascorbic acid, uric acid, dopamine, norepinephrine, 3-methoxytyramine (3MT), 3,4-dihydroxyphenylacetic acid (Do Pa C ), homovanillic acid (HVA), 5-hydroxytryptamine (5HT), and 5-hydroxyindoleacetic acid (FHIAA).

B. Alerts

In certain embodiments, one or more alerts are associated with a sensor electronics module. For example, each alert may include one or more alert conditions indicating when the respective alert has been triggered. For example, a hypoglycemic alert may include alert conditions indicating a low glucose level. Alert conditions may also be based on transformed sensor data, such as trend data, and/or sensor data from multiple different sensors (for example, an alert may be based on sensor data from both a glucose sensor such as a temperature sensor). For example, a hypoglycemic alert may include alert conditions that indicate a minimum required trend in the host's glucose level that must be present before activating the alert. The term "trend" as used herein generally refers to data indicating some data attribute that is acquired over time, for example, such as data calibrated or filtered from a continuous glucose sensor. A trend may indicate amplitude, rate of change, acceleration, direction, etc., of data, such as sensor data, including raw or transformed sensor data.

In certain embodiments, each of the alerts is associated with one or more actions to be performed in response to the activation of the alert. Alert actions may include, for example, triggering an alarm, such as displaying information on a sensor electronics module display element or triggering an audible or vibrating alarm coupled to the sensor electronics module and/or transmitting data to one. or more external display devices to the sensor electronics module. For any provisioning action that is associated with a triggered alert, one or more provisioning options define the content and/or format of the data to be transmitted, the device to which the data is to be transmitted, when the data is to be transmitted, and/or or a communication protocol for supplying the data.

In certain embodiments, multiple provisioning actions (each having respective provisioning options) may be associated with a single alert such that displayable sensor information having different content and formatting is transmitted, for example, to display devices. in response to the activation of a single alert. For example, a mobile phone may receive a data packet that includes minimal displayable sensor information (which may be specifically formatted for display on the mobile phone), while a desktop computer may receive a data packet that includes the most part (or all) of the displayable sensor information that is generated by the sensor electronics module in response to the activation of a common alert. Advantageously, the sensor electronics module is not tied to a single display device, instead, it is configured to communicate with a plurality of different display devices in a direct, systematic, simultaneous manner (for example, by broadcasting), regular, periodic, random, on demand, in response to a query, based on alerts or alarms and/or the like.

In some embodiments, clinical risk alerts are provided that include alert conditions that combine dynamic and intelligent estimation algorithms that estimate a present or predicted danger more accurately, more timeliness in pending danger, avoidance of false alarms, and less patient discomfort. In general, clinical risk alerts include dynamic and intelligent estimation algorithms based on analyte value, rate of change, acceleration, clinical risk, statistical probabilities, known physiological constraints, and/or individual physiological patterns, thereby providing more appropriate alarms, clinically safe and patient-friendly. US Patent Publication No. 2007/0208246 describes some systems and methods associated with the clinical risk alerts (or alarms) described herein. In some embodiments, clinical risk alerts may be activated for a predetermined period of time to allow the user to manage their condition. Additionally, clinical risk alerts can be turned off when leaving the clinical risk zone so as not to disturb the patient through repeated clinical alarms (eg, visual, audible, or vibrating), when the patient's condition is improving. In some embodiments, the dynamic and intelligent estimation determines a chance for the patient to avoid clinical risk, based on the analyte concentration, rate of change, and other aspects of the dynamic and intelligent estimation algorithms. If there is little or no chance to avoid the clinical risk, a clinical risk alert will be triggered. However, if there is a chance to avoid the clinical risk, the system is configured to wait a predetermined amount of time and re-analyze the chance to avoid the clinical risk. In some embodiments, when there is a potential to avoid clinical risk, the system is further configured to provide goals, therapy recommendations, or other information that can help the patient proactively avoid clinical risk.

In some embodiments, the sensor electronics module is configured to search for one or more display devices within communication range of the sensor electronics module and to wirelessly communicate sensor information (for example, a data packet that includes viewable sensor information, one or more alarm conditions, and/or other alarm information) to it. Accordingly, the display device is configured to display at least some of the sensor information and/or send an alarm to the host (and/or caregiver), where the alarm mechanism is located on the display device.

In some embodiments, the sensor electronics module is configured to provide one or a plurality of different alarms through the sensor electronics module and/or by transmitting a data packet indicating that an alarm should be initiated by one or a plurality of display devices (eg, sequentially and/or simultaneously). In certain embodiments, the sensor electronics module simply provides a data field indicating that an alarm condition exists and the display device, after reading the data field indicating the existence of the alarm condition, may decide to activate an alarm condition. alarm. In some embodiments, the sensor electronics module determines which of the one or more alarms to activate based on one or more alerts that are activated. For example, when an alert activation indicates severe hypoglycemia, the sensor electronics module can take multiple actions, such as triggering an alarm in the sensor electronics module, transmitting a data packet to a monitoring device indicating the activation an alarm on the display element and transmit a data packet as a text message to a healthcare professional. As an example, a text message may appear on a personalized monitoring device, cell phone, pager, and/or the like, that includes displayable sensor information indicating the host's condition (eg, "severe hypoglycemia").

In some embodiments, the sensor electronics module is configured to wait a period of time for the guest responding to a triggered alert (for example, by pressing or selecting a function and/or snooze and/or off button on the sensor electronics module and/or a display device), after which additional alerts are triggered (for example, in an escalating manner) until one or more alerts are responded to. In some embodiments, the sensor electronics module is configured to send control signals (eg, a stop signal) to a medical device associated with an alarm condition (eg, hypoglycemia), such as an insulin pump, where the stop alert triggers a stop of insulin delivery by the pump.

In some embodiments, the sensor electronics module is configured to transmit alarm information directly, systematically, simultaneously (eg, by broadcast), regular, periodic, random, on demand, in response to a query (from the display device), based on alerts or alarms and/or the like. In some embodiments, the system further includes a repeater such that the wireless communication distance of the sensor electronics module can be increased, for example, to 10, 20, 30, 50, 75, 100, 150, or 200 meters or more. , wherein the repeater is configured to repeat a wireless communication from the sensor electronics module to the display device located remotely from the sensor electronics module. A repeater can be helpful for families who have children with diabetes. For example, to allow a parent to carry, or place in a stationary position, a display device, such as in a large house where the parents sleep at a distance from the child.

C. Display Devices

In some embodiments, the sensor electronics module is configured to search for and/or attempt wireless communication with a display device from a list of display devices. In some embodiments, the sensor electronics module is configured to search for and/or attempt wireless communication with a list of display devices in a predetermined and/or programmable (eg, sorted and/or intensified) order, eg. , wherein an unsuccessful attempt to communicate with and/or send an alarm to a first display device triggers an attempt to communicate with and/or send an alarm to a second display device, and so on. In one exemplary embodiment, the sensor electronics module is configured to search for and attempt to send an alarm to a guest or healthcare professional sequentially using a list of display devices, such as: (1) a default display device or a custom analyte monitoring device; (2) a mobile phone through auditory and/or visual methods, such as, text message to the guest and/or healthcare professional, voice message to the guest and/or healthcare professional, and/or 112); (3) a tablet-type computer; (4) a smart watch.

Depending on the embodiment, one or more displays receiving data packets from the sensor electronics module are "dummy displays", in which they display viewable sensor information received from the sensor electronics module no additional processing (eg, prospective algorithmic processing required for real-time display of sensor information). In some embodiments, the displayable sensor information comprises transformed sensor data that does not require processing by the display device prior to display of the displayable sensor information. Some display devices may include software that includes display instructions (software programming comprising instructions configured to display displayable sensor information and optionally querying the sensor electronics module for displayable sensor information) configured to allow display of the sensor information displayable therein. In some embodiments, the display device is programmed with the display instructions at the manufacturer and may include security and/or authentication to prevent plagiarism of the display device. In some embodiments, a display device is configured to display sensor information viewable by a downloadable program (eg, a Java Script program downloadable over the Internet), such that any display device that supports downloading a program (eg, any display device that supports Java applets) may thus be configured to display displayable sensor information (eg, mobile phones, tablet computers, PDAs, PCs, and the like).

In some embodiments, certain display devices may be in direct wireless communication with the sensor electronics module, but intermediate network hardware, firmware, and/or software may be included within the direct wireless communication. In some embodiments, a repeater (eg, a Bluetooth repeater) may be used to retransmit the transmitted displayable sensor information to a location beyond the immediate range of the telemetry module of the sensor electronics module, where the repeater enables direct wireless communication when substantial processing of displayable sensor information does not occur. In some embodiments, a receiver (eg, Bluetooth receiver) may be used to retransmit the transmitted displayable sensor information, possibly in a different format, such as in a text message to a TV screen, where the receiver allows direct wireless communication when no substantial processing of sensor information occurs. In certain embodiments, the sensor electronics module directly wirelessly transmits displayable sensor information to one or a plurality of display devices, such that displayable sensor information transmitted from the sensor electronics module is received by the display device without intermediate processing of displayable sensor information.

In certain embodiments, one or more display devices include built-in authentication mechanisms, where authentication is required for communication between the sensor electronics module and the display device. In some embodiments, to authenticate data communication between the sensor electronics module and the display devices, a challenge-response protocol is provided, such as key authentication, where the challenge is a request for the key or a cryptographic hash or other value based on or derived from the key, and the valid response is the correct key or a cryptographic hash or other value based on or derived from the key, such that the modulus pairing Sensor electronics with display devices can be achieved by the user and/or manufacturer using the key. This may be referred to in some cases as two-way authentication. The key can be either a software-level or a hardware-level key. Additionally, the key may be a password (eg, randomly generated or set by a user or other entity) and/or may be derived from unique identification characteristics (eg, fingerprint or retinal data) or information, etc. .

In some embodiments, one or more display devices are configured to query the sensor electronics module for displayable sensor information, wherein the display device acts as a master device requesting sensor information from the sensor electronics module. sensor (for example, a slave device) on demand, for example, in response to a query. Although in some cases the display device acts as the master and the sensor electronics module acts as the slave, in other cases these roles can be reversed. For example, the roles may be reversed depending on the nature of the communication, and so on. In some embodiments, the sensor electronics module is configured for periodic, systematic, regular, and/or periodic transmission of sensor information to one or more display devices (eg, every 1, 2, 5, or 10 minutes or more). ). In some embodiments, the sensor electronics module is configured to transmit data packets associated with a triggered alert (eg, triggered by one or more alert conditions). However, any combination of the above described states of data transmission can be implemented with any combination of paired sensor electronics module and display device(s). For example, one or more display devices may be configured to query the sensor electronics module database and to receive alarm information triggered by one or more alarm conditions being met. Additionally, the sensor electronics module may be configured for periodic transmission of sensor information to one or more displays (the same or different displays as described in the example above), whereby a system may include display devices that work differently with respect to how sensor information is obtained.

In some embodiments, a display device is configured to query the data storage memory in the sensor electronics module for certain types of data content, including direct queries against a database in the sensor electronics module memory. sensor and/or configured or configurable packet requests for data content therefrom; specifically, the data stored in the sensor electronics module is configurable, queryable, predetermined, and/or prepackaged, based on the display device with which the sensor electronics module is communicating. In some additional or alternative embodiments, the sensor electronics module generates the displayable sensor information based on its knowledge of which display device is to receive a particular transmission. Additionally, some display devices are capable of obtaining calibration information and wirelessly transmitting the calibration information to the sensor electronics module, such as by manual input of calibration information, automatic provision of calibration information, and/or a solidary reference analyte monitor built into the display device. US Patent Publication Nos. 2006/0222566, 2007/0203966, 2007/0208245, and 2005/0154271 describe systems and methods for providing a solidary reference analyte monitor incorporated in a display device and/or other calibration methods that they can be implemented with embodiments disclosed herein.

In general, a plurality of display devices (for example, a personalized analyte monitoring device (which may also be called an analyte display device), a mobile phone, a tablet computer, a smart watch, an analyte monitor reference device, a drug delivery device, a medical device, and a personal computer) may be configured to communicate wirelessly with the sensor electronics module. The plurality of display devices may be configured to display at least some of the displayable sensor information communicated wirelessly from the sensor electronics module. Viewable sensor information may include sensor data, such as raw data and/or transformed sensor data, such as analyte concentration values, rate of change information, trend information, alert information, sensor and/or calibration information, for example.

D.Continuous Sensor

Referring to Figure 1A, in some embodiments, analyte sensor 10 includes a continuous glucose sensor, eg, a subcutaneous, transdermal (eg, transcutaneous), or intravascular device. In some embodiments, such a sensor or device can analyze a plurality of intermittent blood samples. The glucose sensor can use any method of glucose measurement, including enzymatic, chemical, physical, electrochemical, spectrophotometric, polarimetric, calorimetric, iontophoretic, radiometric, immunochemical, and the like.

A glucose sensor may use any known method, including invasive, minimally invasive, and noninvasive sensing techniques (eg, fluorescence monitoring), to provide a data stream indicative of glucose concentration in a host. The data stream is typically a raw data signal, which is converted to a calibrated and/or filtered data stream that is used to provide a useful glucose value to a user, such as a patient or caregiver (eg. , a parent, family member, guardian, teacher, doctor, nurse, or any other individual who has an interest in the welfare of the guest).

A glucose sensor can be any device capable of measuring glucose concentration. According to an exemplary embodiment described below, an implantable glucose sensor may be used. However, it should be understood that the devices and methods described herein can be applied to any device capable of sensing a glucose concentration and providing an output signal representing the glucose concentration (eg, as the form of analyte data). .

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

Figures 2A and 2B are perspective and side views of enclosure 200 that may be used in connection with implementing embodiments of analyte sensor system 8, in accordance with certain aspects of the present disclosure. Enclosure 200 includes a mounting unit 214 and sensor electronics module 12 attached thereto in certain embodiments. Enclosure 200 is shown in an operative position, including mounting unit 214 and sensor electronics module 12 matably engaged therein. In some embodiments, the mounting unit 214, also called a sensor housing or receptacle, includes a base 234 adapted to be attached to the skin of a host or user. Base 234 can be formed from a variety of hard and soft materials and can include a low profile to minimize protrusion of the device from the host during use. In some embodiments, base 234 is at least partially formed from a flexible material, which can provide numerous advantages over other transcutaneous sensors which, unfortunately, can exhibit motion-related artifacts associated with movement of the host when the guest is using the device. Mounting unit 214 and/or sensor electronics module 12 may be located over the sensor insertion site to protect the site and/or provide minimal footprint (use of host skin surface area).

In some embodiments, a releasable connection is provided between the mounting unit 214 and the sensor electronics module 12, which allows for improved ease of manufacture, namely, the possibly relatively inexpensive mounting unit 214 can be discarded when refurbished. or the analyte sensor system 8 is retained, while the relatively more expensive sensor electronics module 12 may be reusable with multiple sensor systems. In some embodiments, sensor electronics module 12 is configured with signal processing (programming), eg, configured to filter, calibrate, and/or execute other algorithms useful for calibration and/or display of sensor information. However, an integral (non-removable) sensor electronics module can be configured.

In some embodiments, there are contacts 238 mounted on or in a subassembly referred to hereinafter as contact subassembly 236 configured to fit within the base 234 of mounting unit 214 and a hinge 248 that allows contact subassembly 236 to be mounted. pivot between a first position (for insertion) and a second position (for use) with respect to mounting unit 214 . The term "hinge" as used herein is a broad term and is used in its usual sense, including, without limitation, to refer to any of a variety of pivoting, articulating, and/or hinge mechanisms, such as an adhesive hinge, slip joint, and the like; the term hinge does not necessarily imply a fulcrum or fixed point around which articulation occurs. In some embodiments, contacts 238 are formed from a conductive elastomeric material, such as carbon black elastomer, through which sensor 10 extends.

With further reference to Figures 2A and 2B, in certain embodiments, the mounting unit 214 is provided with an adhesive pad 208, disposed on the rear surface of the mounting unit, and includes a removable backing layer. Therefore, removing the backing layer and pressing at least a portion of the base 234 of the mounting unit 214 onto the host's skin adheres the mounting unit 214 to the host's skin. Additionally or alternatively, an adhesive pad may be placed over part or all of the analyte sensor system 8 and/or the sensor 10 after sensor insertion is complete to ensure adhesion and optionally to ensure an airtight or watertight seal. to water around the wound exit site (or sensor insertion site) (not shown). Appropriate adhesive pads can be chosen and designed to stretch, elongate, conform to, and/or aerate the region (eg, host skin). The embodiments described with reference to Figures 2A and 2B are described in more detail with reference to US Patent No. 7,310,544. The configurations and arrangements may provide waterproof, waterproof, and/or hermetic sealing properties associated with the sensor electronics module/mounting unit embodiments described herein.

Various methods and devices that are suitable for use in conjunction with aspects of some embodiments are disclosed in US Patent Publication No. US-2009-0240120-A1.

E. Examples of configurations

Referring again to Figure 1A, a system 100 is depicted that may be used in connection with implementing aspects of an analyte sensor system. In some cases, system 100 may be used to implement various systems described herein. In embodiments, system 100 includes analyte sensor system 8 and display devices 110, 120, 130, and 140, in accordance with certain aspects of the present disclosure. Analyte sensor system 8 in the illustrated embodiment includes sensor electronics module 12 and continuous analyte sensor 10 associated with sensor electronics module 12. Sensor electronics module 12 may be in wireless communication (eg, directly or indirectly) with one or more of display devices 110, 120, 130, and 140. In embodiments, system 100 also includes medical device 136 and server system 134. Sensor electronics module 12 may also be in wireless communication (eg, directly or indirectly) with medical device 136 and/or server system 134 . Also, in some examples, display devices 110-140 may also be in wireless communication (eg, directly or indirectly) with medical devices 136 and/or server system 134. Various couplings shown in FIG. 1A can be facilitated with a wireless access point 138, as also mentioned below.

In certain embodiments, sensor electronics module 12 includes electronic circuitry associated with continuous analyte sensor data measurement and processing, including prospective algorithms associated with sensor data processing and calibration. Sensor electronics module 12 may be physically connected to continuous analyte sensor 10 and may be integral with (non-releasably attached to) or releasably attached to continuous analyte sensor 10. Sensor electronics module 12 may include hardware, firmware, and/or software that enables measurement of analyte levels by a glucose sensor. For example, the sensor electronics module 12 may include a potentiostat, a power supply to provide power to the sensor, other useful components for signal processing and data storage, and a telemetry module for transmitting data from the electronics module. from sensor to one or more display devices. The electronics may be attached to a printed circuit board (PCB) or the like, and may take a variety of forms. For example, the electronics may take the form of an integrated circuit (IC), such as an application specific integrated circuit (ASIC), a microcontroller, and/or a processor.

Sensor electronics module 12 may include sensor electronics that are 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 analyte sensor data are described in more detail herein and in US Patent Nos. 7,310,544 and 6,931,327 and US Patent Publication Nos. 2005/0043598, 2007 /0032706, 2007/0016381, 2008/0033254, 2005/0203360, 2005/0154271, 2005/0192557, 2006/0222566, 2007/0203966 and 2007/0208245.

Referring again to Figure 1A, display devices 110, 120, 130 and/or 140 are configured to display (and/or send alarms of) displayable sensor information that may be transmitted by sensor electronics module 12 (for example, in a personalized data packet that is transmitted to display devices based on their respective preferences). Each of the display devices 110, 120, 130, or 140 may include a display element such as a touch screen display element 112, 122, 132/or 142 for displaying sensor information and/or analyte data to a user. user and/or receive entries from of the user. For example, a graphical user interface may be presented to the user for such purposes. In some embodiments, the displays may include other types of user interfaces such as a voice user interface instead of, or in addition to, a touch screen display element for communicating sensor information to the user of the display device and /o receive user input. In some embodiments, one, some, or all of the display devices are configured to display or otherwise communicate sensor information as communicated from the sensor electronics module (for example, in a data packet that is transmitted to respective display devices), with no additional prospective processing required for real-time calibration and display of sensor data.

Medical device 136 may be a passive device in exemplary embodiments of the disclosure. For example, medical device 136 may be an insulin pump for delivering insulin to a user, as shown in FIG. 1B. For a variety of reasons, it may be desirable for such an insulin pump to receive and track glucose values transmitted from the analyte sensor system 8 . One reason is to provide the insulin pump with an ability to suspend/activate insulin delivery based on a glucose value being below/above a threshold value. One solution that allows a passive device (eg, medical device 136) to receive analyte data (eg, glucose values) without being attached to the analyte sensor system 8 is to include the analyte data in the prompt messages. transmitted from the analyte sensor system 8. The data included in the warning messages can be encrypted so that only a device having the identification information associated with the analyte sensor system 8 can decrypt the analyte data. Medical device 136 may include an input/output portion 136a, where, for example, glucose and other values may be displayed and input may be received via buttons, wireless connection, or other mechanisms. Medical device 136 may also include an attachment portion 136b that interfaces with the user, for example, to deliver insulin in response to input received at input/output portion 136a. In some cases, binding portion 136b may provide sensory alerts or other notifications to the user based on, for example, input received and/or values calculated at input/output portion 136a.

With further reference to Figure 1A, the plurality of display devices may include a custom display device specially designed to display certain types of displayable sensor information associated with analyte data received from sensor electronics module 12 (e.g. , a numerical value, and an arrow, in some embodiments). Analyte display device 110 is an example of such a custom device. In some embodiments, one of the plurality of display devices is a smartphone, such as a mobile phone 120 based on Android, iOS, or another operating system, and configured to display a graphical representation of continuous sensor data (eg, including current and historical data). Other display devices may include other wearable devices, such as a tablet computer 130, a smart watch 140, a medical device 136 (for example, an insulin delivery device or blood glucose meter), and/or a computer. desktop or laptop.

Since different display devices provide different user interfaces, the content of the data packets (for example, amount, format, and/or type of data to be displayed, alarms, and the like) can be customized (for example, scheduled automatically). different by the manufacturer and/or by an end user) for each particular display device. Accordingly, in the embodiment of FIG. 1A, a plurality of different display devices may be in direct wireless communication with a sensor electronics module (eg, such as an on-skin sensor electronics module 12 that is physically connected to continuous analyte sensor 10) during a sensor session to enable a plurality of different types and/or levels of display and/or functionality associated with displayable sensor information, which is described in more detail elsewhere in the this document.

As further illustrated in FIG. 1A, system 100 may also include a wireless access point (WAP) 138 that may be used to couple one or more of the analyte sensor system 8, the plurality of display devices, the system server 134 and medical device 136 with each other. For example, WAP 138 may provide WiFi and/or cellular connectivity within system 100. Near field communication (NFC) may also be used between devices in system 100. Server system 134 may be used to collect analyte data from of the analyte sensor system 8 and/or the plurality of display devices, for example, to perform analyzes therewith, generate universal or individualized models for glucose levels and profiles and so on.

Referring now to Figure 3A, system 300 is depicted. System 300 may be used in connection with implementing embodiments of the disclosed systems, methods, and devices. By way of example, the various components described below in Figure 3A can be used to provide wireless glucose data communication, for example between an analyte sensor system and a plurality of display devices, medical devices, servers, and so on. .

As shown in FIG. 3A, system 100 may include an analyte sensor system 308 and one or more display devices 310. Additionally, in the illustrated embodiment, system 300 includes a server system 334, which in turn includes a server 334a coupled to a processor 334c and storage 334b. The analyte sensor system 308 may be coupled to display devices 310 and/or server system 334 via communication means 305 . Many details of data processing, collection, and exchange by analyte sensor system 308 and/or display device 310, etc., are provided, for example, with reference to Figure 6, below.

As will be described in detail herein, the analyte sensor system 308 and display devices 310 may exchange messages via communication means 305, and communication means 305 may also be used to supply analyte data to display devices 310 and/or server system 334 . As mentioned above, display devices 310 can include a variety of electronic computing devices, such as, for example, a smartphone, tablet computer, laptop, wearable device, and the like. Display devices 310 may also include an analyte display device 110 and a medical device 136 . In this case, it will be appreciated that a GUI of display device 310 may perform such functions as accepting user input and displaying menus as well as information derived from analyte data. The GUI may be provided by various operating systems known in the art, such as, for example, iOS, Android, Windows Mobile, Windows, Mac OS, Chrome OS, Linux, Unix, a video game platform OS (for example, Xbox, PlayStation, Wii), etc. In various embodiments, communication means 305 may be based on one or more wireless communication protocols such as Bluetooth, Bluetooth Low Energy (BLE), ZigBee, WiFi, 802.11 protocols, infrared (IR), radio frequency (RF), 2G, 3G, 4G etc and/or wired media and protocols.

In various embodiments, elements of system 300 may be used to perform various procedures described herein and/or may be used to perform various operations described herein with respect to one or more disclosed systems and methods. Upon review of the present disclosure, one skilled in the art will appreciate that system 300 may include multiple analyte sensor systems, communication means 305, and/or server systems 334.

As mentioned, communication means 305 may be used to communicatively connect or couple analyte sensor system 308, display devices 310, and/or server system 334 to each other or to a network, and means 305 communication can be implemented in a variety of ways. For example, the communication medium 305 may include a connection to the Internet, such as a local area network (LAN), a wide area network (WAN), a fiber optic network, Internet over power lines, a wired connection ( for example, a bus) and the like, or any other kind of network connection. Communication medium 305 may be implemented using any combination of routers, cables, modems, switches, optical fibers, cables, radio (eg, microwave/RF links), and the like. Furthermore, the communication medium 305 can be implemented using various wireless standards, such as Bluetooth®, BLE, Wi-Fi, 3g Pp standards (for example, 2G GSM/GPRS/EDGE, 3G UMTS/CDMA2000 or 4G LTE/LTE- U), etc Upon reading this disclosure, one of ordinary skill in the art will recognize other ways to implement communication means 305 for communication purposes.

Server 334a may receive, collect, or monitor information, including analyte data and related information, from analyte sensor system 308 and/or display device 310, such as an input in response to analyte data or a input received in connection with an analyte monitoring application running on the analyte sensor system or display device 310 . In such cases, server 334a may be configured to receive such information via communication medium 305. This information may be stored in storage 334b and may be processed by processor 334c. For example, processor 334c may include an analysis engine capable of performing analysis on information that server 334a has collected, received, etc., via communication medium 305 . In embodiments, server 334a, storage 334b, and/or processor 334c may be implemented as a distributed computing network, such as a Hadoop® network, or as a relational database or the like.

Server 334a may include, for example, an Internet server, router, desktop or laptop computer, smartphone, tablet computer, processor, module, or the like, and may be implemented in a variety of ways, including eg, an integrated circuit or collection thereof, a printed circuit board or collection thereof, or in a discrete housing/package/rack or multiples thereof. In embodiments, server 334a directs, at least partially, communications made through communication medium 305. Such communications include the provision and/or sending of messages (eg, notice, command, or other messages) and analyte data. For example, server 334a may process and exchange messages between analyte sensor system 308 and display devices 310 related to frequency bands, transmission timing, security, alarms, and so on. Server 334a may update information stored in analyte sensor system 308 and/or display devices 310, for example, by serving applications thereto. Server 334a may send/receive information to/from analyte sensor system 308 and/or display devices 310 in real time or sporadically. Additionally, server 334a may implement cloud computing capabilities for analyte sensor system 308 and/or display devices 310.

Figure 3B depicts system 302, which includes examples of additional aspects of the present disclosure that may be used in connection with the implementation of an analyte sensor system. Many details of data processing, collection, and exchange by analyte sensor system 308 and/or display device 310, etc., are provided, for example, with reference to Fig. 6, below. As illustrated in Figure 3B, system 302 may include analyte sensor system 308 . As shown, analyte sensor system 308 may include analyte sensor 375 (for example, which may also be designated 10 in FIG. 1A) coupled to sensor measurement circuitry 370 to process and manage data. sensor data. Sensor measurement circuitry 370 may be coupled to processor/microprocessor 380 (eg, which may form part of element 12 in FIG. 1A). In some embodiments, processor 380 may perform some or all of the functions of sensor measurement circuitry 370 to obtain and process sensor measurement values from sensor 375. Processor 380 may further be coupled to a unit radio or transceiver 320 (for example, which may form part of element 12 in Figure 1A) to send sensor data and receive requests and commands from an external device, such as display device 310, which may be used to displaying or otherwise providing the sensor data (or analyte data) to a user. As used herein, the terms "radio unit" and "transceiver" are used interchangeably and refer generally to a device that can wirelessly transmit and receive data. The analyte sensor system 308 may further include storage 365 (eg, which may be part of element 12 in Figure 1A) and real-time clock (RTC) 380 (eg, which may be part of element 12). in Figure 1A) to store and track sensor data.

As mentioned above, wireless communication protocols may be used to transmit and receive data between analyte sensor system 308 and display device 310 via communication medium 305 . Such wireless protocols may be designed for use in a wireless network that is optimized for small, periodic data transmissions (which can be transmitted at low rates if necessary) to and from multiple devices over short ranges (for example, a wireless network). of personal area (PAN)). For example, such a protocol may be optimized for periodic data transfers where the transceivers may be configured to transmit data for short intervals and then enter low power modes for long intervals. The protocol may have low overhead requirements both for normal data transmissions and for initially establishing communication channels (eg, by reducing overhead) to reduce power consumption. In some embodiments, burst broadcast schemes (eg, one-way communication) may be used. This can eliminate the overhead required for acknowledgment signals and allow low power consuming periodic transmissions. In other embodiments, passive or active proximity-based protocols may be employed to reduce overhead (eg, overhead associated with typical pairing operations) and/or increase security, NFC being a specific example.

Protocols can also be configured to establish communication channels with multiple devices while implementing anti-interference schemes. In some embodiments, the protocol may use adaptive isochronous network topologies that define various time slots and frequency bands for communication with various devices. Therefore, the protocol can modify transmission frequencies and windows in response to interference and to support communication with multiple devices. Therefore, the wireless protocol may use time and frequency division multiplexing (TDMA) based schemes. The wireless protocol may also employ direct sequence spread spectrum (DSSS) and frequency hopping spread spectrum schemes. Various network topologies can be used to support short distance and/or low power wireless communication such as peer, star, tree, or mesh network topologies such as WiFi, Bluetooth, and Bluetooth Low Energy (BLE). The wireless protocol can operate in various frequency bands such as an open ISM band such as 2.4 GHz. In addition, to reduce power usage, the wireless protocol can adaptively configure data rates based on power consumption. power.

With additional reference to FIG. 3B, system 302 may include a display device 310 communicatively coupled with analyte sensor system 308 via communication means 305 . In the illustrated embodiment, display device 310 includes a connectivity interface 315 (which in turn includes a transceiver 320), storage 325 (which in turn stores an analyte sensor application 330 and/or additional applications), a processor/microprocessor 335, a graphical user interface (GUI) 340 which may be presented using a display element 345 of display device 310, and a real time clock (RTC) 350 . A bus (not shown here) may be used to interconnect the various elements of display device 310 and transfer data between these elements.

Display device 310 may be used to alert and provide sensor information or analyte data to a user and may include a processor/microprocessor 335 to process and manage sensor data. Display device 310 may include a display element 345, storage 325, analyte sensor application 330, and real-time clock 350 for displaying, storing, and tracking sensor data. Display device 310 may further include a radio unit or transceiver 320 coupled to other elements of display device 310 via connectivity interface 315 and/or a bus. Transceiver 320 may be used to receive sensor data and to send requests, instructions, and/or data to analyte sensor system 308 . Transceiver 320 may further employ a communication protocol. Storage 325 may also be used to store an operating system for storage device 310. display and/or a custom (eg, private) application designed for wireless data communication between a transceiver and display device 310 . Storage 325 may be a single memory device or multiple memory devices and may be volatile or non-volatile memory for storing data and/or instructions for software programs and applications. Instructions may be executed by processor 335 to control and manage transceiver 320.

In some embodiments, when using a standardized communication protocol, commercially available transceiver circuitry incorporating processing circuitry may be used to manage low-level data communication functions such as managing data scrambling, transmission frequencies , contact protocols and the like. In these embodiments, the processor 335, 380 does not need to manage these activities, but rather provides desired data values for transmission and manages high-level functions such as powering on or off, setting a rate at which to transmit messages, and the like. Instructions and data values to perform these high level functions may be provided to the transceiver circuitry via a data bus and transfer protocol established by the transceiver manufacturer 320, 360.

Components of the analyte sensor system 308 may require replacement periodically. For example, analyte sensor system 308 may include an implantable sensor 375 that may be attached to a sensor electronics module that includes sensor measurement circuitry 370, processor 380, storage 365, and transceiver 360, and a battery (not shown). Sensor 375 may require periodic replacement (eg, every 7 to 30 days). The sensor electronics module may be configured to be on and active for much longer than the 375 sensor (for example, three to six months or more) until the battery needs to be replaced. Replacing these components can be difficult and may require the help of trained personnel. Reducing the need to replace such components, particularly the battery, significantly improves the convenience and cost of use of the analyte sensor system 308, including for the user. In some embodiments, when a sensor electronics module is used for the first time (or is reactivated after a battery has been replaced in some cases), it may be connected to sensor 375 and a sensor session may be established. As will be described further below, there may be a procedure for initially establishing communication between the display device 310 and the sensor electronics module when the module is first used or reactivated (eg, the battery is replaced). Once the display device 310 and the sensor electronics module have established communication, the display device 310 and the sensor electronics module may be in communication periodically and/or continuously throughout the life of the device. various sensors 375 until, for example, the battery needs to be replaced. Each time the 375 sensor is replaced, a new sensor session can be established. The new sensor session may be initiated by a procedure completed using the display device 310 and the procedure may be triggered by notifications of a new sensor through communication between the sensor electronics module and the display device 310 which may be persistent. throughout sensor sessions.

In exemplary implementations, analyte sensor system 308 collects analyte data from sensor 375 and transmits the same to display device 310. Data points regarding analyte values may be collected and transmitted throughout the lifetime of sensor 375 (eg, in the range of 1 to 30 days or more). New measurements can be transmitted frequently enough to adequately monitor glucose levels. Instead of having the transmit and receive circuitry of each of the analyte sensor system 308 and display 310 in continuous communication, the analyte sensor system 308 and display 310 may establish regularly and/or periodically a channel of communication between them. Thus, in some cases the analyte sensor system 308 may communicate via wireless transmission with the display device 310 (eg, a portable computing device, medical device, or private device) at predetermined time intervals. The length of the predetermined time interval can be selected to be long enough so that the analyte sensor system 308 does not consume too much power by transmitting data more often than necessary, but often enough to provide sensor information substantially at different times. real-time data (eg, measured glucose values or analyte data) to the display device 310 for output (eg, via display element 345) to a user. Although the default time interval is every five minutes in some embodiments, it is appreciated that this time interval can be varied to any desired length of time.

Continuing to refer to Figure 3B, as shown, connectivity interface 315 interconnects display device 310 to communication means 305 such that display device 310 can communicatively couple to motion sensor system 308 . analyte through the communication medium 305 . Transceiver 320 of connectivity interface 315 can include multiple transceiver modules that can be operated with different wireless standards. Transceiver 320 may be used to receive analyte data and associated commands and messages from analyte sensor system 308 . Additionally, the connectivity interface 315 may include, in some cases, additional components to control radio and/or cable connections, such as baseband and/or Ethernet modems, audio/video codecs, and so on.

Storage 325 may include volatile memory (for example, RAM) and/or non-volatile memory (for example, flash-type storage), may include any of EPROM, EEPROM, cache, or may include some combination/variation thereof. In various embodiments, storage 325 may store user input data and/or other data collected by display device 310 (eg, input from other users collected by analyte sensor application 330). Storage 325 may also be used to store volumes of analyte data received from analyte sensor system 308 for later retrieval and use, for example, to determine trends and trigger alerts. Additionally, storage 325 may store an analyte sensor application 330 that, when executed using processor 335, for example, receives input (for example, via a conventional hard/soft key or touch screen, voice detection, or other input). input mechanism) and allows a user to interact with the analyte data and related content through the GUI 340, as will be described in more detail herein.

In various embodiments, a user may interact with the analyte sensor application 330 through the GUI 340, which may be provided by the display element 345 of the display device 310. By way of example, display element 345 may be a touch screen display element that accepts various hand gestures as inputs. Application 330 may process and/or display analyte-related data received by display 310, in accordance with various operations described herein, and display such data through display element 345. Additionally, application 330 may be used to obtain, access, display, control, and/or interact with analyte data and related messages and procedures associated with analyte sensor system 308, as described in more detail herein. .

Application 330 may be downloaded, installed, and initially configured/set up on display device 310. For example, display device 310 may obtain application 330 from server system 334 or from another source accessed through a communication medium (eg, communication medium 305), such as an app store or similar. After installation and configuration, application 330 can be used to access and/or interface with analyte data (eg, whether stored on server system 334, locally from storage 325, or from sensor system 308). analyte). By way of illustration, the application 330 may display a menu that includes various controls or commands that may be executed in connection with the operation of the analyte sensor system 308 and one or more displays 310. Application 330 may also be used to interface with or control other display devices 310, for example, to supply or make available the same analyte data, including, for example, receiving/sending analyte data directly to the other device. display 310 and/or sending an instruction to turn on the analyte sensor system 308 and the other display device 310, etc., as will be described herein. Additionally, in some implementations the application 330 may interact with one or more additional applications supported by the display device 310, for example to retrieve or serve relevant data. Such applications may include, by way of example, exercise/lifestyle monitoring applications, social networking applications, and so on.

The analyte sensor application 330 may include various code/functional modules, such as, for example, a display module, a menu module, a list module, and so on as will become apparent upon viewing the description of various functionalities herein (eg, in connection with disclosed methods). These modules can be implemented independently or in combination. Each module may include computer-readable media and have computer-executable code stored therein, such that the code may be operatively coupled to and/or executed by processor 335 (which, for example, may include circuitry for such execution) to perform specific functions (eg, as described herein with respect to various operations and flow charts, etc.) with respect to interfacing with and performing tasks related to analyte data. As will be described further below, a display module may present (for example, via display element 345) various screens to a user, the screens containing graphical representations of information provided by the application 330. In additional embodiments, the display Application 330 may be used to display to the user an environment to view and interact with various display devices that may be connectable to the analyte sensor system 308, as well as the analyte sensor system 308 itself. Sensor application 330 may include a native application modified with a software design kit (eg, depending on the operating system) in order to carry out the functionalities/features described herein.

Referring back to Figure 3B, display device 310 also includes a processor/microcontroller 335. Processor 335 may include processor sub-modules, including, by way of example, an application processor that interfaces with and/or controls other elements of display device 310 (eg, connectivity interface 315, application 330, GUI 340, display element 345, RTC 350, etc.). Processor 335 may include a controller and/or microcontroller that provides various controls (eg, interfaces with buttons and switches) related to device management, such as, for example, lists of available or previously paired devices, information related to values of measurement, information related to network conditions (eg, link quality and the like), information related to the timing, type, and/or structure of messages exchanged between analyte sensor system 308 and display device 310, and so on. Additionally, the controller can include various controls related to the collection of user input, such as, for example, a user's fingerprint (for example, to authorize user access to data or to be used for authorization/encryption of data, including password data). analyte), as well as analyte data.

Processor 335 may include circuitry such as logic circuitry, memory, power and battery circuitry, and other circuitry controllers for peripheral components and audio components. Processor 335 and any subprocessors thereof may include logic circuitry for receiving, processing, and/or storing data received and/or input to display device 310, and data to be transmitted or supplied by display device 310. Processor 335 may be bus coupled to display element 345 as well as connectivity interface 315 and storage 325 (including application 330). Thus, processor 335 can receive and process electrical signals generated by these respective elements and thus perform various functions. By way of example, processor 335 may access stored content from storage 325 as directed by application 330, and process the stored content for display and/or output by display element 345. Additionally, processor 335 may process stored content for transmission through connectivity interface 315 and communication medium 305 to other display devices 310, analyte sensor system 308, or server system 334. Display device 310 may include other peripheral components not shown in detail in Figure 3B.

In additional embodiments, processor 335 may further obtain, detect, calculate, and/or store data entered by a user through display element 345 or GUI 340, or data received from analyte sensor system 308 (e.g. , analyte sensor data, or related messages), over a period of time. Processor 335 may use this input to estimate the user's physical and/or mental response to the data and/or other factors (eg, time of day, location, etc.). In various embodiments, user response or other factors may indicate preferences regarding the use of certain displays 310 under certain conditions and/or the use of certain connection/transmission schemes under various conditions, as will be described in more detail. in the present document.

It should be noted at this point that similarly named elements such as between display device 310 and analyte sensor system 308 may include similar features, structures, and/or capabilities. Thus, with respect to such items, the description of display device 310 above may apply in some instances to analyte sensor system 308 .

Turning now to Figure 3C, system 304 according to embodiments of the present disclosure is depicted. As shown, system 304 includes analyte sensor system 308 communicatively coupled to display devices 310a, 310b via communication means 305a. Display device 310a is also communicatively coupled to display device 310b via communication means 305b. By way of example, Figure 3C illustrates that, in exemplary implementations of the disclosure, display device 310a may connect to analyte sensor system 308 using a first connection scheme and a first wireless protocol (eg, BLE). . In turn, display device 310a may also connect to display device 310b using a second connection scheme and a second wireless protocol (eg, Wi-Fi, NFC, etc.). In embodiments, the connection between the display device 310a and the analyte sensor system 308 may subsequently be closed and the display device 310b may establish a connection with the analyte sensor system 308 while maintaining the connection with the display device 310a. display. Further, for example, the display devices 310a and 310b may exchange analyte data with each other through the communication medium 305b, wherein each display device 310a, 310b received the analyte data through the communication medium 305a, that is, from the analyte sensor system 308. Display device 310c may also be connected to display device 310b via communication means 305c. Additional aspects and features depicted by Figure 3C will become apparent upon review of the entirety of this disclosure, including, by way of example, Figures 3D and 3E.

Figure 3F illustrates an exemplary implementation of the GUI 340 that may be used in accordance with embodiments of the present disclosure. As shown in FIG. 3F, the GUI 340 may be presented through the display element 345 of the display device 310, for example in connection with the sensor application 330. In general terms, the functionality and features of GUI 340 will be described in more detail with reference to systems and methods described herein. By way of illustration, GUI 340 may present interfaces associated with application 330, including, for example, a display manager. Such a display manager can be used to configure aspects of systems involving analyte monitoring, such as systems 300, 302, 304, 306a, and 306b (referring to FIGS. 3A-3E by way of example). For example, the display device manager (and in some cases, more generally, interfaces associated with the application 330) may be used to configure connection parameters for an established (or to be established) connection between the analyte 308 and the device 310, can be used to select a dedicated display 310, can be used to anchor one display 310a to another display 310b, and so on (referencing by way of example FIGS. 3A-3E).

As shown in FIG. 3F, the display manager may include an interface module for each of one or more display devices 310 that may be coupled to the analyte sensor system 308 (see, for example, FIGS. 3A and 3B). Interface module 390a may be used to interface with a first display device of display devices 310 ("display device 1" or "DD1"): interface module 390b may be used to interface with an analyte display device of display devices 310 ("analyte display element"); and interface module 390c may be used to interface with a second display device of display devices 310 ("display device 2" or "DD2"). Each interface module 390a, 390b, 390c may in turn include a configuration menu 395, which may include various buttons (eg, soft touch keys) for configuring various settings for the device being managed. The available buttons of the configuration menu 395 and their functionality can be modified, for example, based on characteristics of the display device being managed as well as other parameters.

As will be described in connection with Figure 3G, configuration menus 395 can be used to access submenus that can be used to select management options specific to the display of interest. Additional buttons that may be included in the GUI 340 are buttons 312a-e. For example, button 312a can be used to add a device to the device manager; button 312b can be used to apply a previously set configuration to the device manager; button 312c may be used to notify the user of an alert or to manage alert settings; button 312d may be used to navigate back to a previous screen displayed in GUI 340 (eg, in connection with application 330); and button 312e can be used as a softkey to return to the home screen of display device 310.

Turning now to Figure 3G, additional aspects are provided that may be implemented in connection with GUI 340. As shown in Figure 3G, embodiments of GUI 340 involve submenus 314a-g of interface modules 390a, 390b, and 390c. . Submenu 314a may be accessed through configuration menu 395 of interface module 390a. In this case, submenu 314a corresponds to a "system" option. In this regard, when selected (for example, by touch gesture on display element 345) submenu 314a presents options 316a for managing and displaying display device 1 battery characteristics, radio settings, and battery measurements. display device 1, and aspects of other devices. Options 316a can be used to select a device to anchor to (eg, via another device option 316a). Referring to Figure 3C by way of specific example, anchoring in this case may involve, for example, connecting two display devices 310a and 310b via communication means 305b. In some cases, the analyte display element and display device 2 may correspond to known devices, while selecting the other device option may initiate a scan for other display devices 310 available for connection. In other examples, the other device option can be used to tether to a known device. It will be appreciated that submenu 314a may be implemented in connection with any other interface module (eg, 390b, etc.).

Submenu 314b corresponds to a "replace/remove" option. In this regard, when selected (eg, by touch gesture on display element 345) submenu 314b presents options 316b, which include options to replace the analyte display element with another display 310, namely the display device 3 ("DD3") or other device. Within options 316b, submenu 314b also presents options for removing the analyte display item from a list of devices (eg, a white list), as will be described further herein (see, for example, example, Fig. 10B). Again in this case, in some cases the display device 3 may correspond to a known device, while selecting the other device option may initiate a scan for other display devices 310 available for connection to the display element of analyte. It will be appreciated that submenu 314b may be implemented in connection with any other interface module (eg, 390a, etc.). For example, the submenu can be used to replace a user's old smartphone with the user's new smartphone for use with the analyte sensor system 308 .

Submenu 314c corresponds to an option of “Param. from config.” or configuration parameters. In this regard, when selected (for example, by touch gesture on display element 345) submenu 314c presents options 316c, which include options for modifying or adjusting various configuration parameters regarding the connection with the communication system 8 . analyte sensor and transmission of data therefrom. Within options 316c, submenu 314c presents options as to whether specific configuration parameters are enabled and then indicates additional options related to configuration parameters that may be specifically controlled by the user. In some examples, these connection parameters may additionally or alternatively be monitored and adjusted without user intervention (eg, by display device 310 and/or analyte sensor system 308), for example by comparing monitored parameter values to thresholds. default and/or configurable/adaptable. In this regard, the user may be able to select which parameters should be monitored/adjusted by the display device 310. In other cases, the selection may be made on the fly based on monitored parameter values and/or other inputs. Therefore, it will be appreciated that, in some cases, the user may not have access or permission with respect to the connection parameters.

Therefore, notwithstanding the foregoing, it will be appreciated that, in embodiments of the GUI 340, various combinations and implementations of configuration 395 (395a, etc.), submenus 314a-g, and options 316a-g, are contemplated, in relation to this disclosure. By way of example, submenu 314c corresponding to “Param. from config.” may be omitted such that the connection parameters may not be visible by default to the user and/or are accessible or changeable by the user. In such examples, connection parameters may be stored in storage 325 of display device 310 and may be in conjunction with establishing and/or maintaining a connection between display device 310 and analyte sensor system 308 (and/or in some cases another display device 310).

In embodiments, a quality option (not shown) may be set by the user to control or interact with configuration parameters related to quality of service (QoS), as will be described further herein. In addition, as mentioned elsewhere herein in more detail, QoS-related parameters may also be monitored/adjusted by the analyte sensor system 308 and/or display device 310, for example based on QoS-related thresholds. link quality and so on. The quality option can be accessed through the preferences 395 setting. The location option may be set by the user to control or interact with location-related configuration parameters, as will be further described herein. The time option may be set by the user to control or interact with configuration parameters related to the time of day, as will be further described herein. The power option can be set by the user to at least indirectly control and/or interact with configuration parameters related to battery power, as will be described further herein. These options can be accessed through preferences settings 395, for example.

Submenu 314d corresponds to a pop-up option related to the device to which interface module 390a belongs (ie, in this example, display device 1 (DD1)). More specifically, submenu 314d indicates, via grayed-out options 316d, whether the device of interest is whitelisted, as will be described further herein. Options 316d in this example are grayed out to indicate that, in some cases, they cannot be selected but rather are used to display information regarding whitelist status. A different submenu ("whitelist/blacklist"), not specifically described with reference to Figure 3G, may be used to add/remove specific devices to/from the whitelist (or to/from a blacklist). It will be appreciated that submenu 314d may be implemented in connection with any other interface module (eg, 390a, etc.).

Submenu 314e corresponds to a "dedicated" option. In this regard, when selected (eg, by touch gesture on display element 345), submenu 314e presents options 316e, which include options for making a display of interest (in this case, the element analyte display device) is a dedicated display device with respect to connecting to and receiving data from and/or exchanging control signaling with the analyte sensor system 308 . Options 316e of submenu 314e present options to indicate yes or no as to whether the analyte display element is a dedicated display device, as will be described further herein. It will be appreciated that submenu 314e may be implemented in connection with any other interface module (eg, 390a, etc.).

Submenu 314f corresponds to a "connection status" option. In this regard, when selected (eg, by touch gesture on display element 345) submenu 314f presents options 316f, including options to adjust or configure a mode of connection as between the display device of interest ( in this case, display device 2) and analyte sensor system 308, for example. Within options 316f, submenu 314f presents options for your connection model, connected and other, relating to the connection, as will be described further herein. By way of example, submenu 314f may provide a user with information regarding the connection model employed without allowing the user to modify the connection model or select a connection model from a set of options. However, in other cases, the user may be able to manually choose a connection model to be used using this option. Additionally, the connected option 316f may indicate to the user whether the display device 2 is currently connected to the analyte sensor system 308 . It will be appreciated that submenu 314f may be implemented in connection with any other interface module (eg, 390a, etc.).

Submenu 314g corresponds to a "pairing" option. In this regard, when selected (eg, by touch gesture on display element 345) submenu 314g presents options 316g, which include options regarding identification, selection, and/or pairing with sensor system 308. analyte and/or display devices 310a, 310b, etc. Within options 316g, submenu 314g presents an ID # option, which refers to information related to identification (eg, regarding analyte sensor system 308); discovered devices, which refers to a set of identified display devices 310a, 310b, etc.; confirmation selection, which can be used by a user to manually confirm a selection for their connection between the analyte sensor system 308 and the display device 310; and interaction level, which can be used to set and/or modify the amount of interaction of the user to be used in connection with the identification and/or selection of devices in connection with the pairing procedure. It will be appreciated that submenu 314f may be implemented in connection with any other interface module (eg, 390a, etc.).

Certain submenus and/or options, etc., disclosed in connection with Figure 3G and the present disclosure have not been described in detail here with reference to Figure 3G, but aspects of embodiments shown in Figure 3G are described further below. below in this document. Additionally, one of ordinary skill in the art will appreciate, upon review of this disclosure, that GUI 340 may present various additional submenus and/or options, and will also appreciate that additional submenus and options are within the scope of this disclosure.

Figure 4 is a block diagram illustrating possible aspects of the analyte sensor system 408 according to embodiments of the present disclosure that, in exemplary implementations, are associated with operation according to the intermittent connection model. Aspects of the analyte sensor system 408 shown in FIG. 4 may be implemented within the subsystem 400 of the analyte sensor system 408 and may be used, in general, to manage a radio interface between the analyte sensor system 408 and any device. display device communicatively coupled thereto via a wireless protocol, such as BLE. For example, an application programming interface (API) 450 may be provided for display devices to communicate with processor 420 (eg, processor 380) via radio 425, which may include a BLE or other transceiver. RF or microwave (for example, transceiver 360). Processor 420 may be used to process analyte data collected by sensor 405 (eg, sensor 375).

As shown, within analyte sensor system 408, subsystem 400 may include sensor 405 (eg, sensor 10), analog front end (AFE) 410 (eg, sensor electronics module 12 ), a battery 415, a processor 420, and a radio 425. The design of the analyte sensor system 408, including with respect to the subsystem 400 as well as related software, allows for the operation and management of multiple chips and, particularly, in wherein such operation and/or management is performed according to power saving principles described herein and may involve implementing system configurations that support/maximize power savings. For example, the design allows for system startup, inter-chip communication, application task scheduling, maximizing battery life in storage as well as active modes, and use of checkpoints and indications via API 450 associated with the radio 425 .

A storage mode may be used for the operation of the analyte sensor system 408 before the analyte sensor system 408 has been inserted into a host. For example, upon detecting that sensor 405 has been inserted into the host, analyte sensor system 408 may automatically exit storage mode and enter an active mode. In storage mode, radio 425 may be at least partially disabled in order to save power. Also, processor 420 may be at least partially disabled, for example by disabling a clock used by processor 420 (eg, RTC 350). Furthermore, it is contemplated that, in the storage mode, the radio 425 may be configured to be in a deep sleep mode. This can advantageously extend/maximize the battery life of the analyte sensor system 408 . It is further contemplated that, in implementations, upon interaction with display device 310, for example via n Fc , analyte sensor system 408 may exit storage mode.

In active mode, a low power mode (LPM) can still be used (for example, to prolong/maximize battery life), but the RTC 350 can be activated/enabled. This may allow the processor 420 to accurately track time and perform other clock-based functions while still allowing power savings. For example, the RTC 350 can be used to perform error recovery using interrupts and time based counters. The following error recovery scenarios are provided for illustration. In one example, if no response message is received from radio 425 for a given amount of time, processor 420 may reset radio 425. In another example, a periodic interrupt may be used where, if the logic If the RTC 350 fails, the analyte sensor system 408 can be reset by hardware logic. In additional implementations, if a message or signal associated with wakeup source 435 (or AFE 410) is not received or fails, an interrupt (eg, RTC interrupt) may be used to bring processor 420 out of LPM and perform wakeup functions. communication.

Processor 420 may act as a system controller for subsystem 400 within analyte sensor system 408 . For example, after initializing, radio 425 may enter a sleep state and await instruction from processor 420. AFE 410 may initialize to a default state and also await configuration instructions/commands from processor 420. Processor 420 may control restarting the AFE 410 and/or radio 425 in the event of errors being detected. Processor 420 may also reset itself if internal error conditions are detected (eg, by using a hardware watchdog).

Subsystem 400 of analyte sensor system 8 may use a multi-chip (or multi-module) design, in which case a hardware communication bus may be used for data exchange between the various chips. (or modules). Examples of viable options for the hardware communication bus include Inter Integrated Circuit (I2C or I2C) and Serial Peripheral Interface (SPI). SPI can be used to achieve a power reduction as well as a speed increase over I2C.

Wake source 435 and raw sensor data 430 may be used to maximize the battery life of analyte sensor system 408 . In examples, AFE 410 may be used as a wake source for components of subsystem 400. However, other wake sources may be used. During normal operation, the AFE 410 may allow the processor 420 to enter an energy efficient low power mode (LPM). Wakeup source 435 may be used to signal processor 420 to exit LPM such that, for example, processor 420 may execute operations that, in examples, may not be available during LPM. Wakeup source 435 may signal processor 420 in this manner periodically and trigger processor 420 to begin processing or executing operations. The analyte sensor system 408 may include multiple processors and, as mentioned below with reference to FIG. 5, staggered task processing may be implemented, in some cases in relation to the wake source 435, such that no all processors are active simultaneously. This technique can reduce power consumption and thus extend battery life. As an example, wakeup source 435 may first signal processor 420 to exit the LPM and begin configuring the relevant hardware and software of analyte sensor system 408 to initiate (analyte) data transfer. of raw sensor from AFE 410.

Raw sensor data 430 may include hardware that transfers sensor data collected by sensor 405 from AFE 410 to processor 420. Such data may be referred to herein as raw sensor data or raw analyte data. Configuration 440 may be a bidirectional interface between processor 420 and AFE 410. In some cases, configuration 440 may be implemented using I2C, but SPI or other interface configuration may also be used. Processor 420 and radio 425 may also use an SPI and/or I2C bus for communication and data transfer. In some cases, additional hardware and software may be used to create an asynchronous interface between processor 420 and radio 425 when using synchronous protocols (eg, SPI and the like).

Turning now to Figure 5, a block diagram is provided illustrating possible aspects of the analyte sensor system 508 according to embodiments of the present disclosure that, in some cases, are associated with operation in the intermittent connection model. Aspects of the analyte sensor system 508 shown in FIG. 5 may be implemented within the subsystem 500 of the analyte sensor system 508 . In particular, the subsystem 500 includes a processor 520 and a radio 525 that can be modified to include an additional general purpose input/output (GPIO) and SPI bus with respect to the communication interface 445 and thus create an additional interface. Asynchronous 545 that couples processor 520 to radio 525. In some cases, the asynchronous 545 interface may be called a message transport layer.

As shown in the example of FIG. 5, asynchronous interface 545 includes a connection 505b that provides a chip select (CS) output 505c of radio 525 to a CS input 505a of processor 520. In addition, interface The asynchronous 545 interface includes a connection 510b that provides an SPI clock output 515c from the radio 525 to a CLK input 510a from the processor 520. The asynchronous 545 interface includes a connection 515b that provides MISO 530a (multiple input single output) from the processor 520 to a MISO input 530c of radio 525. Asynchronous interface 545 further includes a connection 530b that provides a MOSI (multiple output, single input) output 530c of radio 525 to a Mo S i input 530a of radio 525. processor 520. In addition, asynchronous interface 545 includes a connection 535b that provides a request output 535a from processor 520 to a request input 535c from radio 525. Asynchronous interface 545 also includes connection 54 5b providing an ACK/NACK output 540c from radio 525 to an ACK/NACK input 540a from processor 520.

Asynchronous interface 545 may provide an asynchronous communication link between processor 520 (which may be used to process analyte data) and a radio processor within radio 525 (eg, a baseband processor). Furthermore, the asynchronous interface 545 may allow the removal of a master/slave topology from the application layer logic. The asynchronous interface 545 may also allow sending/receiving messages in an interrupted context, such that the 520 processor and/or the radio processor remain in a low power mode until a complete message is ready to communicate over the interface. Interface. In exemplary implementations, messages sent by processor 520 use an ACK/NACK as well as a response packet to confirm/deny receipt of the message. With respect to subsystem 500, staggered task processing may also be employed to limit the execution time of each of processor 520 and a processor within radio 525 so that there is as little execution time overlap as possible. This can reduce stress on battery 415 and minimize asynchronous messaging problems.

Returning again to Figure 4, AFE 410 may sample raw analyte data from sensor 405 over a period of time (eg, 5 minutes). During sampling, processor 420 and a processor (eg, baseband processor) within radio 425 may be kept in low power mode (LPM). Once the AFE 410 completes sampling, the AFE 410 can send a signal to the processor 420 indicating that the Processor 420 must come out of the LPM (that is, it must be reactivated). AFE 410 may then transfer the raw analyte data to processor 420 via configuration 440. Fe 410 may then re-enter the LPM. Processor 420 may then process the raw analyte data (eg, to generate an estimated glucose value) and store the processed analyte data. Processor 420 may then send signals to radio processor 425 via communication interface 445 to communicate the processed analyte data to radio 425. Processor 420 may subsequently enter the LPM while waiting for radio 425 to connects with a display device (eg, display device 310). Once such a connection is made, the processor 420 can exit the PM and the display device and the processor 420 can exchange data, commands and/or messages via the radio 425.

API 450 may be used to interface with devices remote from analyte sensor system 408 via various wireless protocols. An example of such a protocol is BLE. In this regard, API 450 may allow analyte sensor system 408 to be configured by a user of a display device (eg, display device 310) running an application such as, for example, application 330 of analyte sensor. The analyte sensor application 330 may have been developed by the manufacturer of the analyte sensor system 408 and/or display device 310, or may be developed by any individual or entity. In the case where the BLE standard is used to couple a display device to the analyte sensor system 408, the BLE characteristics may be configurable according to system design parameters.

Figure 6 is an operational flow chart illustrating various operations that may be implemented, for example, by analyte sensor system 408, in connection with embodiments of method 600 according to the present disclosure, wherein, in examples, such embodiments are associated with operation according to the intermittent connection model. However, upon review of the present disclosure, it will be appreciated that Figure 6 can be modified for operation in the continuous connection model. For context purposes, Figure 6 includes an analyte sensor system 608 and a subsystem 602. As shown, within subsystem 602, the analyte sensor system 608 may include an AFE 610, a processor 620 (which may used to process CGM data) and a radio 625. The analyte sensor system 608 can be used to perform various operations shown in Figure 6 in order to connect (for example, wirelessly) to a remote device such as a computer. display device (eg, display device 310 or medical device 136). In this way, analyte data can be transmitted to and processed by the display device. In addition, the analyte sensor system 608 and the display device may exchange messages related to the configuration of the communication protocol used for their connection between the analyte sensor system and the display device. In some instances herein, the operations shown in Figure 6 may be described with reference to the BLE protocol, but in any event one skilled in the art will appreciate, after studying this disclosure, that aspects shown in, and described with reference a, Figure 6 can be applied to other communication protocols.

Prior to operation 610a, the analyte sensor system 608 may be in LPM or a related mode in which power consumption is reduced, eg, a "sleep mode." In operation 610a, AFE 610 sends signals to processor 620 to start processing. For example, AFE 610 may signal processor 620 with a wake event that signals processor 620 to exit a low power mode. As mentioned above, AFE 610 may act as a wakeup source, and operation 610a may correspond to wakeup source 435 referred to in FIG. 4. In operation 610b, AFE 610 passes wakeup data. (eg, raw sensor or analyte data) to processor 620. In exemplary implementations where analyte data refers to glucose data, processor 620 may be referred to as a continuous glucose monitor (CGM) processor. .

Having received signals to start processing (eg, at step 610a), processor 620 may process, at step 620a, the sensor data passed to it at step 610b. For example, as mentioned in Figure 6, processor 620 may calculate an estimated glucose value (EGV) from the sensor data. Processor 620 may also store the sensor data and/or other value derived therefrom (eg, EGV) in storage and/or a database (eg, storage 365 shown in FIG. 3B, which, in some cases, is a flash memory). In operation 620b, processor 620 may send signals to radio 625 (which, in some cases, may be a BLE radio) to begin communication. In operation 620c, processor 620 may then enter LPM or a related mode in which power consumption is reduced, eg, a "sleep mode." In embodiments, operation 620c may be skipped such that the processor does not necessarily enter LPM mode, etc. In response to the signal to begin communication sent in step 620b, radio 625 may, in step 625a, page and/or connect to a display device. Examples of warning messages and associated connect/disconnect protocols will be described in more detail herein.

Following the alert/connect according to step 625a, the radio 625 may receive, at step 630a, a request signaling (eg, a command request). The request signaling may be received from a display device and may be a request for the transmission of analyte data and/or may be related to various configuration parameters of the analyte sensor system 608 associated with the warning and/or data transmission.

In response to receiving the signaling, in operation 625b, radio 625 may pass the signaling to processor 620. This may be done using interface 445 or 545 (eg, a message transport layer). Stated another way, radio 625 may be configured to pass such signaling to processor 620 using a message transport layer such that, for example, analyte sensor system 608 does not appear to be a multi-chip system for a display device that sends the signaling. After passing (in operation 625b) the signaling to processor 620, in operation 625c radio 625 may enter LPM or a related mode in which power consumption is reduced, for example, a "sleep mode". . For the continuous connection model, operation 625c can be omitted, such that the sleep mode is not entered but instead the connection is maintained as described herein with reference to Fig. 7J, for example.

In step 625d, after receiving the request signaling from radio 625 (step 625b), processor 620 may process the signaling to generate response signaling (eg, a command response). The response signaling may be passed to radio 625 in operation 620e. This can be done using the 445 or 545 interface (eg, a message transport layer). Stated another way, processor 620 may be configured to pass such signaling to radio 625 using a message transport layer. After receiving the response signaling (sent in step 620e), the radio 625 may exit LPM or related mode (which it entered in step 625c) and send the response signaling to the display device. In summary, by way of example, upon receiving (at step 630a) a request from an analyte data display device, the analyte sensor system 608 may transmit response signaling (at step 625d).

In operation 620f, processor 620 sends signals to radio 625 to stop communication. In this way, after sending the response signaling (in step 625d), the radio 625 can close the connection with the display device and, in step 625e, enter the LPM or the like. Also, processor 620, in operation 620g, may enter LPM or the like after sending signals to radio 625 to stop communication. In embodiments, operation 620g may be skipped such that the processor does not necessarily enter LPM mode, etc. Analyte sensor system 608 may remain in the LPM or the like until AFE 610 subsequently sends signals to processor 620 to restart implementation of various of the operations described above. For the continuous connection model, the 625e operation can be omitted, so that the sleep mode is not entered and/or the connection is not closed, but instead the connection is maintained as described herein with reference to Fig. 7J, for example.

With the foregoing description of aspects of currently disclosed systems and methods for wireless communication of analyte data, several specific improvements will now be provided. One skilled in the art will appreciate, upon review of the present disclosure, that these enhancements can be implemented using features and combinations of features of the exemplary configurations described above, whether or not explicitly referenced thereto. Furthermore, with respect to Figures 4, 5 and 6, although in some instances related embodiments are associated with intermittent connection model operation, one of ordinary skill in the art will appreciate, upon review of the present disclosure, that such embodiments may be modified to operate according to the continuous connection model described herein.

F. Synchronism and notice structure

An additional aspect involves the order and manner in which various devices (eg, display devices 710) connect to the analyte sensor system (eg, analyte sensor system 708), which may depend on the order, timing, structure and manner of warning messages transmitted to such display devices 710. Reference numbers 708 and 710 will be noted here, but the description may apply to any of the analyte sensor systems and/or display devices described herein, as will be appreciated by one of ordinary skill in the art. the art after studying the present disclosure. A possible scheme for the connection order for various devices can be described as follows.

The analyte sensor system 708 alerts and connects to displays 710 that are available for connection, ie, displays 710 within range. This can be done, for example, by transmitting warning messages. By way of example, reference is made to operation 705a shown in FIG. 7A. On the display device side, display devices 710 seeking to connect to analyte sensor system 708 may, in exemplary embodiments, scan for analyte sensor system 708 or another similar sensor system to connect to. This generally involves receiving and processing alert messages that are being broadcast by the analyte sensor system 708, etc., in order to determine if any such messages are being transmitted by a compatible/desirable analyte sensor system 708 .

Display device 710 may then respond to the warning message by sending a connection request back to analyte sensor system 708 . By way of example, reference is made to operation 705b shown in Figure 7A. Upon receiving the connection request, the analyte sensor system 708 may accept, reject, or simply ignore the request. In exemplary implementations, the analyte sensor system 708 only services one display device 710 connection at a time. Thus, a basis for rejecting or ignoring a request connection is that the analyte sensor system 708 is already connected to a display device 710 . If there is no basis to reject or ignore a connection request, the analyte sensor system 708 may accept the request and connect to the display device 710 that sent the request. For example, operation 705b shows analyte sensor system 708 accepting the request by signaling display 710 to indicate that the connection is granted. Warning aspects and related contexts are also illustrated, by way of example, with reference to FIGS. 7B-7K. See, for example, operations 735a, 765a, 795a. Detailed comments on these figures are further included below.

Referring again to FIG. 7A, once display device 710 and analyte sensor system 708 are connected, they can exchange messages, including transmitting analyte sensor system 708 analyte data to display device 710 . display. By way of example, reference is made to operation 705d shown in Figure 7A. In embodiments, in order to prevent display device 710 from remaining connected to analyte sensor system 708 longer than intended or desired, analyte sensor system 708 may implement timeouts and/or may cause implement timeouts. That is, for example, there may be a predetermined limit set regarding the duration of the connection, and upon expiration of the same, the connection to the analyte sensor system 708 may be terminated. By way of example, reference is made to operation 715 shown in Figure 7A. This may allow other display devices 710 to connect or attempt to connect to the analyte sensor system 708 . The analyte sensor system 708 may maintain a list of display devices 710 that have been recently connected to the analyte sensor system 708 . In some cases, this may be known as a whitelist. The analyte sensor system 708 can use this list to allow only listed display devices (ie, recently connected) to connect to the analyte sensor system 708 .

Fig. 9 is a timing diagram illustrating an example of the transmission of warning messages according to the present disclosure. More specifically, FIG. 9 provides an exemplary embodiment of an alert duration structure 935 that may be used in connection with pairing or connecting analyte sensor system 708 to display device 710 and/or display device 110 . of analyte. In connection with the foregoing and according to embodiments of the alert duration structure 935, alert messages 920 may be sent according to a time interval that occurs periodically based on a calendar. This may be known in some cases as a warning window interval 905 . This period of repetition of the appearance of this interval can be any length of time, but in a specific example it is 5 minutes. However, the warning window interval may be configured or set to vary depending on the nature of the operation of the analyte sensor system 708 with respect to analyte data collection and processing. Therefore, every 5 minutes (in this example), there will be a window of time to transmit warning messages. The time window for paging messages can be considered to be a length of time during which paging messages can actually be transmitted. This may also be referred to as a 910 warning duration in some cases. As an example, this window can range from 7 to 22 seconds. However, one of ordinary skill in the art will appreciate, upon review of the present disclosure, that the window for the warning duration can range from 0 to any reasonable amount of time. In some cases, the window duration is shorter than the warning window interval 905 .

During the alert duration window 910, alert messages 920 may be transmitted, in some cases periodically, but not necessarily periodically, depending on the alert message interval 915 . The warning message interval 915 can be thought of as a time interval between successive or sequential warning messages 920 . A specific example of interval for alert interval 915 is between 20 ms and 90 ms, although it will be appreciated, upon review of the present disclosure, that alert message interval 915 may be shorter or longer, and/or may be longer. variable in length or adaptively configurable, depending on the relevant circumstances, including adapting or reconfiguring the message interval 915 during the alert duration window 910 . After the alert window interval has elapsed, transmission of alert messages 920 may resume, and alert duration structure 935 may be repeated (eg, as 935'). It should also be noted that one or more of the alert message interval, alert duration length, and alert window interval may be reconfigured between alert duration structures 935 and 935' and/or within alert duration 935, 935'. respective notice, etc.

For convenience for purposes of the following discussion, the displays will be referred to as displays 710, while the analyte displays will be referred to as analyte displays 110. However, it will be appreciated that elsewhere in this document, the term display devices 710 is broad enough to cover any display device or collection of display devices, including analyte display device 110 and display devices. 136 doctors.

The aforementioned warning window interval 905, warning duration 910, and warning message interval 915 may each vary based on a variety of factors. For example, the values of these parameters may vary based on the type and/or number of display devices 710 present and/or how recently such display devices 710 have been connected to the analyte sensor system 708 . These parameter values can also vary in order to optimize battery life, speed up connection time, etc. Any one of a reduced warning window interval 905, an increased warning duration 910 and a reduced warning message interval 915 can increase the probability that a particular display device 710 will successfully connect to the targeted analyte sensor system 708 . However, in examples, there may be a simultaneous increase in power consumption.

As for connecting to the display devices 710 in a particular order, during a time window corresponding to the warning duration 910, the analyte sensor system 708 may, in some cases, first attempt to connect to the display device. display 710 (eg, a smartphone) and then with the analyte display device 110 (eg, a proprietary device, which may be a device designed for the purpose of receiving and displaying analyte data). One possible problem with this connection protocol, in terms of the order used, is that more notice duration 910 may need to be devoted to connection to display 710 compared to connection to analyte display 110, for example since, being a proprietary display device, analyte display device 110 may be optimized for use with analyte sensor system 708 .

In addition, there may occasionally be difficulties connecting with display device 710. If the display device 710 is not able to connect during a time segment (not shown in FIG. 9) of the warning duration 910 specifically assigned to the display device 710, the analyte display device 110 may still be able to connect. subsequently connecting by sending paging messages 920 during other portions or time segments within the paging duration 910 . But, in some cases, the time slot allocated to display device 710 within warning duration 910 is limited by another time slot dedicated to analyte display device 110, such that it may not be feasible to assign the device 710 display additional time segments in which to connect. Alternatively, if additional time is allocated from warning duration 910 to display 710, there may not be enough time available for analyte display 110 to make a connection.

Accordingly, aspects of the present disclosure also include configuring the connection order for various displays 710, including with respect to analyte display 110, as well as configuring the warning window interval 905, warning duration 910, and the warning message interval 915, and other characteristics associated with and/or related to the warning messages. Configuring the connection order for various displays 710 and analyte display 110 according to the present disclosure can increase the probability of establishing a connection between such displays, including displays 710 and analyte display 110. analyte, on the one hand, and the analyte sensor system 708 on the other hand, while also reducing power consumption due to increased connection protocol efficiency. In this way, the overall reliability of communications related to analyte data is increased, while power consumption is reduced. In this regard, methods for connecting analyte sensor system 708 to analyte display device 110 and display device 710 are provided.

G. Warning messages

Figure 8 illustrates an exemplary structure for an alert message 800 that, in some cases, may be transmitted for purposes of establishing a connection between two devices, in accordance with various aspects of the present disclosure (eg, with reference to Figure 7A, in operation 705 and the like). In some cases, the warning message 800 may be considered to be a packet or a warning packet. In the illustrated example, the advisory message 800 includes rows (fields) 800a-800i and columns 805', 810', and 815'. Although the advisory message 800 is represented in matrix form for visual/organizational convenience, one skilled in the art will appreciate, upon review of the present disclosure, that, as for a digital signal, the advisory message 800 may be represented by a matrix. one-dimensional arrangement of bits or bytes that can be arranged in a predetermined way, for example, according to fields and subfields. Stated another way, if the rows 800a-i of the array format of the prompt message 800 were unstacked and concatenated end-to-end, the message 800 would appear as a one-dimensional array. Each field 800a, 800b, ... 800i may be considered to correspond to a row of the advisory message 800, while a subfield may be considered to correspond to a cell in a particular column within a particular row. Therefore, in exemplary implementations, within field 800a, interval 805a is a subfield or cell corresponding to column 805'.

Column 805' in exemplary embodiments corresponds to address 805. Address 805 includes slots 805a-i, where each slot 805a-i may represent a slot of reserved bytes for the corresponding field. Within each field 800a-i, several bytes may be reserved for each cell. That is, by way of illustration, one byte (address 805a may refer to byte zero "0" as the address of field 800a within message 800) may be used for preamble 810a. The number of bytes need not be the same for each cell in a column across multiple fields 800a-i, but in some cases it may be. That is, by way of illustration, two bytes may be used for each cell 805a-i of address 805 and two bytes may be used for each cell 810a-i of description 810. In addition, a variable number of bytes may be used in the cells 815a-i of the value 815. In other examples, different numbers of bytes may be used and numerous variations are contemplated within the scope of the present disclosure. It will also be appreciated that any number of rows and columns can be used, evidently subject to the laws of physics and, in some cases, standardized communication protocols.

With additional reference to Figure 8, column 805' in this example corresponds to address 805. Cells 805a-i may each contain a value (eg, binary or hexadecimal or the like) representing the length of the field. 800a-i corresponding. Each length may in some cases be represented by a start and end position for the respective field. Column 810' in this example corresponds to description 810. Cells 810a-i may each contain a value representing a description of the corresponding field 800a-i. For example, field 800a in this example is described by the value in cell 810a as the preamble to warning message 800. Column 815' in the illustrated example corresponds to value 815. Cells 815a-i may each contain a value representing the value (eg, as opposed to address or description) of the corresponding field 800a-i. By way of example, cell 815e may contain bytes amounting to a value representing the device name (eg, for analyte sensor system 708). MAC address 810d may include an address for analyte sensor system 708 .

Embodiments of the present disclosure may involve leveraging aspects of message 800 to improve the reliability, speed, and/or efficiencies of aspects related to wireless communication of analyte data. In some cases, the value 815d of the MAC address field 810d may be dynamically configurable to make it specific to a particular display device 710 or set of displays 710 or other remote devices connectable to and targeted by the user. , analyte sensor system 708 . In some cases, analyte data and/or related control signaling and the like, or portions thereof, may be included in reserved slots within advertisement packets (eg, step 765a with reference to FIG. 7E). For example, analyte data and the like may be included in the manufacturing data field 800h. Other slots may be used for similar purposes according to various implementations. Other such embodiments that use aspects of the warning message 800 advantageously will become apparent upon review of the present disclosure.

H. Identification, selection and matching

In exemplary implementations, before connecting the analyte detection system 308 to a device such as the display device 310 (referring to Figure 3A), it may be necessary to identify and/or select the analyte sensor system 308 and/or or the appropriate display device 310. In some example use cases, display device 310 may be presented with more than one analyte sensor system 308 available for connection. Such a use case may occur in a hospital ward, for example, where multiple patient analyte sensor systems 308 are activated. In such a case, in order for each patient's respective display device 310 to be connected to that patient's analyte sensor system 308, techniques for identifying the appropriate analyte sensor system 308 are discussed herein.

In some example use cases, a single analyte sensor system 308 may sometimes be provided opportunities to connect to more than one display device 310 . Such a use case may occur, for example, in a user's home where the user may be in proximity to multiple display devices 310 such as an analyte display device, a smartphone, a desktop computer, etc. tablet type, a watch and a television, among other devices. In such a case, techniques for identifying one or more display devices 310 for connection, as well as determining aspects of the connection that are suitable, are discussed herein.

Once the appropriate system/device is identified and selected, display device 310 and analyte sensor system 308 can be paired and/or joined. Furthermore, in some cases, authentication procedures may be implemented, eg for data security/privacy purposes. Finally, data, such as analyte data and control signaling, may be exchanged between analyte sensor system 308 and display device 310 based on an established connection (either using a continuous connection model or a continuous connection model). intermittent, as discussed later in this document).

In relation to embodiments of the present disclosure, device/system selection may refer to choosing a device to connect to, pairing may refer to exchanging information to make/establish a connection, and bonding may refer to storing pairing information to from previous exchanges in such a way that the stored information can be used in establishing subsequent connections. Furthermore, the term mating, as used herein, may additionally include in some instances identification, selection, and/or binding, and may in some instances be used to refer to one or more of identification, selection, mating, and binding, as will be apparent to one of ordinary skill in the art upon review of the present disclosure.

It will be appreciated that the pairing of analyte sensor system 308 and display device 310 in some cases involves user interaction. For example, a user may provide information, such as information related to an analyte sensor system 308 to be selected. Such information may be provided manually on display device 310 (eg, via GUI 340) in order to initiate and perform aspects of the aforementioned identification, selection, pairing, and authentication procedure. previously. Although this manual procedure has benefits, a more automated selection/identification/matching procedure involving less user interaction may be preferable in some cases. Accordingly, embodiments of the present disclosure involve adjusting the amount of user interaction involved in the selection/identification/matching procedure. For example, the amount of user interaction involved may be adjusted according to layers or levels of user interaction involved in identifying and/or selecting (or pairing with) a display device 310 and/or analyte sensor system 308 for use. Connection.

By way of example, the amount of user interaction involved may be adjusted according to the layers based on user input directly or indirectly related to changing the amount of user interaction involved and/or in the absence of user input. In embodiments, the amount of user interaction may be automatically adjusted (including, for example, on the fly). The automatic adjustment may be based on information that is collected in a file related to previous attempts (successful or not) to identify and select the analyte sensor system 308 and/or 310 according to the layers described below. In some cases, one or more of the approaches described in the following layers may be preferable based on criteria such as time of day, battery life of a device, quality of service, radio environment, location, and/or the like. The suitability of one or more of the layers may be determined and implemented based on these and/or other criteria.

A first layer or level of user interaction involved in the selection/identification procedure may be associated with a higher level of user interaction. For example, the user according to the first layer may manually provide information in order to facilitate selection and/or identification of (or pairing with) the analyte sensor system 308 . This can be done by the user manually entering, for example, an identification number and/or other identification information associated with the analyte sensor system 308 . For example, referring to Figure 3G, the GUI 340 of display device 310 may provide input for identification information associated with analyte sensor system 308 using option 314g. Display 310 may then identify the corresponding analyte sensor system 308, based, for example, on information received from warning messages sent by analyte sensor system 308. Such advisory messages may include identification information (eg, identification number, manufacturing information, etc.).

In exemplary implementations, the amount of user interaction may be reduced or altered by display device 310 receiving identification information related to analyte sensor system 308 (including, for example, an identification number associated with analyte sensor system 308). analyte sensor and/or with a manufacturer thereof) from a remote source, such as, for example, server system 334 (with reference, for example, to FIG. 3A). That is, instead of or in addition to the user manually entering identification information into the display device 310, the display device 310 may receive this information from the server system 334 or other remote source.

One way this can be done is that a manufacturer, retailer, etc. of analyte sensor system 308 can upload or otherwise provide identification information to server system 334, where the information can be received via from server 334a, processed by processor 334c, and/or stored in storage 334b. A user or individual, etc., may then purchase or obtain the analyte sensor system 308. For example, the purchase can be made in a physical store, from an online marketplace, or from a private web marketplace offered by the manufacturer of the analyte sensor system 308. In some cases, at the time of purchase, the user may provide user information associated with the user (for example, one or more of a username, password, email address, telephone number, etc.), for example to the seller or the manufacturer directly or indirectly. This information may then be provided to server system 334 and associated (eg, in a database or pool residing within server system 334) with the identification information of analyte sensor system 308 acquired by the user.

After obtaining the analyte sensor system 308, the user may, for example, obtain and/or launch the application 330 on the user's display device 310 . The user can log into the application 330, after which the display device 310 can communicate with the server system 334. The user may also provide the application 330 with additional information associated with the user. Application 330 may then interface with server system 334 to provide server system 334 with at least some of the user information provided to application 330 by the user. Server system 334 may then use at least some of the received user information to identify identification information for analyte sensor system 308 acquired by the user. The relevant identification information may then be provided to display device 310. In some cases, this information may be transmitted to display device 310 and passed to application 330 through an application program interface. In some cases, the information may be provided to the user by email or other message. Display device 310 may use this identification information to pair with analyte sensor system 308 and/or confirm/validate an identified/selected analyte sensor system 308 .

Alternatively or additionally, the user may scan a code or image using display device 310.

This can provide a check to verify the manually entered identification number. Or, for example, this may allow at least partial automation of the entry of the transmitter identification number. That is, the user does not need to manually enter the identification number, but instead only needs to scan the encrypted identification number. In exemplary implementations, the identification number may be included in one or more of capacitive ink, thermochromic ink, fluorescent ink, a QR or bar code that may, in some cases, employ such inks, and a removable adhesive. Each of these may be included in the packaging of the analyte sensor system 308 or may be provided, in some cases, in another way (eg, by email, text message, in tangible form, etc.). In embodiments, image recognition/matching may facilitate or be used to enter the identification number.

In embodiments, a list of available analyte sensor systems 308 may be provided through the GUI 340 of display device 310. The list may include analyte sensor systems 308 discoverable by display device 310 and may include codes, icons, or other identification information regarding display devices 310. Corresponding codes, icons, etc., may be printed on the analyte sensor systems 308, printed on a piece of paper or the like, or may be provided electronically (eg, by email, etc.). Then the user can match the code/icon/etc. of the desired analyte sensor system 308 with the corresponding item displayed on the display 310 and selecting the desired item. In some cases, the code/icon/etc. it may be formed by applying a cryptographic hash function to identification information associated with the analyte sensor system 308 .

Alternatively or additionally, the provided list may include display devices 310 that may be discovered by the analyte sensor system 308 . These lists can be sorted/filtered based on various factors (eg RSSI, BER, device type, recently connected or otherwise known devices, other identifying information, etc.). The user may then select an analyte sensor system 308 and/or display device 310 for connection. Referring to Figure 3G, for example, option 314g may be used to select display device 310 from a list and/or to confirm selection of display devices 310. In some cases, after a device's identifying information has been scanned (eg, using received prompt messages or otherwise), the user may be prompted to confirm device selection. The display device 310 used to make the selection, including when the selection is facilitated by manually entering information and/or scanning information, may not be the device ultimately connected to the analyte sensor system 308 . Instead, in some cases, a first display 310 may be used to facilitate connection of the analyte sensor system 308 to a second display 310.

Figure 13A is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure, for example in relation to the first layer or level of user interaction. For purposes of illustration, reference is made herein to Figures 10D and 10E and component numbers are shown therein. However, one of ordinary skill in the art will appreciate, after studying the present disclosure, that similar components from other figures in this disclosure may be included within the scope of the present description of Figure 13A.

Embodiments shown in Figure 13A involve aspects of method 1300 for identifying a device for connection. Method 1300 optionally includes, at step 1305A, displaying (eg, via GUI 340) a list of one or more analyte sensor systems 308a, 308b (eg, with reference to FIGS. 10D and 10E). from among a set of analyte sensor systems 308 . In operation 1305B, method 1300 involves receiving, display device 310, input (eg, via GUI 340 and/or via connectivity interface 315 or a subsystem thereof) that identifies a system 308a of analyte sensor systems from among the set of analyte sensor systems 308 . In operation 1305C, method 1300 involves selecting, display device 310, connection analyte sensor system 308a based on received input.

Figure 13B illustrates method 1302, including additional details regarding operation 1305B, mentioned above with reference to Figure 13A. As shown in FIG. 13B, operation 1305B includes, at operation 1310, scanning an encoded item from analyte sensor system 308a or product container from analyte sensor system 308b. Thus, operation 1310 may provide a setup example with respect to receiving an input that identifies analyte sensor system 308a from among a set of analyte sensor systems 308, for example, as the appropriate analyte sensor system for connection to display device 310.

Although for many cases the first layer or level of user interaction is adequate, in some users or use cases less user interaction may be preferable. Accordingly, a second layer or level of user interaction involved in the selection/identification/matching procedure may be associated with a moderate amount of user interaction. For example, the selection/identification/pairing and connection procedure according to the second layer may be semi-automated and, in some cases, the user may manually perform a relatively simple and/or quick task in order to facilitate the selection and/or identification of a particular analyte sensor system 308 and/or display device 310 .

In exemplary embodiments, in connection with a more automated portion of the second layer-related selection/identification/matching procedure, display device 310 may be configured to detect the presence of one or more signals from one or more systems. analyte sensor 308, and may be further configured to monitor such signals to determine if any of the signals meet a set of selection criteria, eg, based on a derivative of the signal or the like. If a signal or a derivative thereof meets one or more selection criteria, the particular analyte sensor system 308 sending the signal, for example, may be initially selected for connection to display 310.

For some detected signals monitored in connection with embodiments of this selection procedure, measurements and/or characterizations may be employed to derive or otherwise generate statistical and/or other derivative measures related to the detected signals. By way of example, such derivatives may include or relate to the strength or quality of a detected signal as determined over a measurement period. For example, signal strength or quality can be inferred from Bit Error Rate (BER) or Received Signal Strength Indication (RSSI), taken over a measurement period (predetermined or adjustable/adaptive) . One or more such measurements or derived information may be compared based on a thresholded detected signal such that decisions may be based on the comparison. For example, the pair of a display 310 and an analyte sensor system 310 with the least amount of distance between them will in some cases be associated with the largest RSSI measurements and thus may be selected for pairing. and/or connection based on a comparison of the RSSi or the like with a threshold value. Also, a field of discoverable displays 310 and/or analyte sensor systems 308 can be narrowed down by filtering out those devices whose RSSI does not exceed a threshold. In another example, the pair of a display device 310 and analyte sensor system 308 having the lowest BER may be selected for pairing.

Either or both of the analyte sensor system 308 or the display device 310 may monitor signals, generate derivatives thereof, and determine whether the signals meet a set of selection criteria that are being used. In some cases, different selection criteria may be used depending on the device monitoring the signal and/or depending on the device sending the signal. With respect to RSSI, both analyte sensor system 308 and display 310 may be used to determine RSSI or a similar derivative of received signals. One or more of the respective RSSI values may then be shared between analyte sensor system 308 and display device 310 and compared. If they match or are within a predetermined range of each other, the RSSI pairing can be confirmed. The determination of whether the RSSI values agree can be made in the analyte sensor system 308, the display 310, or both. By way of illustration, a first RSSI value may be calculated in display device 310 based on a signal received from analyte sensor system 308 . A second RSSI value may be calculated in analyte sensor system 308 based on at least one similar signal received from display 310. The first RSSI value may then be sent to analyte sensor system 308 for comparison with the second RSSI value and/or the second RSSI value may then be sent to display device 310 for comparison with the first RSSI signal. The agreement between the first/second RSSI values can then be used to confirm the match.

Figure 10D illustrates an example of how characteristics of a received or detected signal can be used for functionality related to device identification, selection, and/or pairing. Specifically, Figure 10D shows an arrangement 1020a that includes analyte sensor systems 308a and 308b and displays 310a. Analyte sensor systems 308a, 308b may be connected to display devices 310a, 310b via communication means 305, including using various connection models discussed herein.

Display device 310a may be connected to analyte sensor system 308a via link 1032a (eg, signals may be passed between analyte sensor system 308a and display device 310 via link 1032a). Link 1032a may represent various arrangements and/or configurations described herein. For example, link 1032a may be associated with a distance between analyte sensor system 308a and display device 310a. In some cases, link 1032a may be associated with path or signal conditions (eg, signal strength, fading, etc.) such as between display device 310a and analyte sensor system 308a. Display device 310a may be connected to analyte sensor system 308b via link 1032d (eg, via communication means 305). Again in this case, link 1032d may be associated with distance and/or path or signal conditions. Display device 310b may be connected to analyte sensor system 308a via link 1032b and analyte sensor system 308b via link 1032c.

As further illustrated in FIG. 10D, the arrangement 1020a in this example may result in a measurement profile 1030a. Specifically, with respect to measurement profile 1030a, Figure 10D shows upper and lower thresholds 1024 and 1026, as well as a threshold delta 1028 which, in this example, represents a difference between the upper and lower thresholds 1024 and 1026. Such a difference can be determined by comparing two signals or derivatives of the signals with each other. In addition, measurement values are displayed that correspond to each of links 1032a to 1032d. More specifically, measure values 1034a to 1034d are shown respectively for measures 1022a to 1022d, where measures 1022a to 1022d respectively correspond to links 1032a to 1032d. That is, for example, metric value 1034a for metric 1022a corresponds to link 1032a, and so on. As shown in this particular illustration example, the measure values 1034a and 1034d are within the upper and lower thresholds 1024 and 1026 (e.g., the measure value 1034a meets or is above the first threshold 1026 but is below second threshold 1024), while measurement value 1034b is below lower threshold 1026 and measurement value 1034c is above both upper and lower thresholds 1024 and 1026.

Upper and lower thresholds 1024 and 1026 may be employed in various ways according to embodiments of the present disclosure. For example, referring to both the first and second layers or levels of user interaction, either or both of the upper and/or lower thresholds 1024 and 1026 may be used in connection with an identification, selection, matching and/or identification procedure. or manual or semi-automatic connection. With respect to the more manual procedure discussed above, for example, upper and/or lower thresholds 1024, 1026 may be used to filter out analyte sensor systems 308 and/or display devices 310 from appearing in a list. presentable to the user of devices available for connection (eg, discoverable devices). In this regard, for example with respect to the analyte sensor system 308a, the display 310b may be filtered out since the measurement value 1034b is below the lower threshold 1026 . Alternatively or additionally, the upper and/or lower thresholds 1024, 1026 may be employed to automatically select a particular analyte sensor system 308 and/or display device 310 where information about the selected devices may then be presented to the user for verification. manually (for example, via the GUI 340). With respect to display device 310b, for example, analyte sensor system 308b may be selected given that measurement value 1034c is above upper threshold 1024 .

In embodiments, once a particular analyte sensor system 308 and/or display device 310 is initially selected, then a relatively simple and/or quick input, task, action and/or event can be provided, performed and/or take place to confirm/validate that the selection is appropriate/desirable. For example, after an initial selection, the user may be prompted (eg, via the GUI 340 and/or other means, such as audio and/or haptic feedback) to perform such tasks and/or provide such inputs or Similar. In exemplary implementations involving derivatives of signals where the derivatives are based on RSSI measurements, once display device 310 and analyte sensor system 308 are initially selected for pairing/connection, the user may be prompted to move the display device 310 closer to or further away from the analyte sensor system 308 . Examples of how these features can be used in relation to selection/matching/etc will now be provided. of devices with reference to Figures 10A-10E.

Figure 10A illustrates an arrangement 1000a of the analyte sensor system 308 and display device 310. As shown, analyte sensor system 308 may be connected to display device 310 via communication means 305 and may be connected to display device 310 via link 1012a. Figure 10A also illustrates the measurement profile 1010a that can result from the environment 1000a. In particular, with respect to measurement profile 1010a, Figure 10A includes upper and lower thresholds 1004 and 1006, as well as a threshold delta 1008 which, in this example, represents a difference between upper threshold 1004 and lower threshold 1006. In addition, in measurement profile 1010a, measurement value 1014a for measurement 1002a corresponds to link 1012a between display device 310 and analyte sensor system 308 (for example, where measurement value 1014a may be an RSSI-related derivative such as between analyte sensor system 308 and display device 310). It should be appreciated that measurement values herein may be or represent, or may be used to generate, derivatives of a signal received over a link (eg, link 1012a, etc.).

In the measurement profile 1010a, the measurement value 1014a is within the upper and lower thresholds 1004 and 1006. That is, in this example, the measurement value 1014a meets or exceeds (or is above) the lower threshold 1006 but is below (or is below) the upper threshold 1004. In exemplary implementations, since the measurement value 1014a is at or above the lower threshold 1006, the display device 310 and/or the analyte sensor system 308 may be initially identified/selected. In embodiments, at this point, the user may be prompted (eg, graphically, audibly, haptically, or one or more of these in combination) to bring display device 310 closer to analyte sensor 308 to confirm/verify. the initial selection. Alternatively, the user may be prompted to move display device 310 further from analyte sensor 308 to confirm/verify initial selection. These two situations will be further described in connection with Figures 10B and 10C.

Figure 10B illustrates an arrangement 1000b of the analyte sensor system 308 and display device 310. As shown, analyte sensor system 308 may be connected to display device 310 via communication means 305 and via link 1012b. In exemplary implementations, arrangement 1000b may result from prompting the user to move display 310 closer to analyte sensor 308 relative to arrangement 1000a shown in FIG. 10A. Where applicable, this can be illustrated by the relative representations of the links 1012a/b. Correspondingly shown in metric profile 1010b is a metric value 1014b for metric 1002b (eg, which may be used to generate or derive a derivative of a signal received over link 1012b) corresponding to link 1012b between device display 310 and analyte sensor system 308 . Further shown in the measurement profile 1010b is a measurement value 1014a and measurement delta 1016a which, in this example, represents a difference between measurement values 1014b and 1014a. With respect to the measurement values described herein, in some cases, the user may be prompted to maintain a particular setting for a duration of time so that more accurate measurement values can be obtained. Once the time duration has elapsed and/or an accurate measurement has been obtained, for example, the user may be notified by display device 310 and/or analyte sensor system 308 via audible, visual, and/or haptic feedback.

With respect to the transition from array 1000a to array 1000b, various techniques may be employed in order to confirm/validate an initial selection/identification of display device 310 and analyte sensor system 308. In embodiments, measurement value 1014b may be monitored/determined/obtained and compared to threshold 1004. As such, it may be determined that, although for arrangement 1000a measurement value 1014a was below upper threshold 1004, on/after moving to layout 1000b, the measurement value 1014b meets or is above the upper threshold 1004 . Having crossed the measurement value 1014b the upper threshold 1004 (in a positive or negative sense) can be used to indicate that the initial identification for its selection and/or selection for its connection was adequate/appropriate. As mentioned, in embodiments, the change between measurement values 1014b/a may be negative rather than positive. For example, measure value 1014b may be measured initially, when it does not meet or exceed upper threshold 1004 . The user may then be prompted to move the display 310 further away from the analyte sensor system 308, thereby moving to an arrangement such as arrangement 1000a in which the measurement value 1014a is below the upper threshold 1004 .

Another technique that can be used in exemplary implementations involves comparing the measurement delta 1016a or the like to a threshold value. By way of illustration, a threshold value for a measurement delta may be predetermined such that an initial identification for selection or selection for connection is confirmed if the measurement delta 1016a exceeds the threshold value. In some cases, an absolute value of the measurement delta can be used for comparison purposes, such that movement either closer to or further from the analyte sensor system 308 can be used to indicate that the initial identification/selection was correct. adequate/appropriate. Thus, for example, a user moving display 310 a given distance closer to or farther from analyte sensor system 308, where the distance moved is related in some way to the resulting change in the value of measurement (or one derived from a signal received through the corresponding link), it can confirm/validate that the identification/selection is appropriate. In some cases, using the measurement delta 1016a may be more robust than relying on threshold crossing 1004 for selection validation. In some cases, the measurement delta 1016a may be set to avoid false positive validation based on relatively minor fluctuations in the measurement value 1014a/b (eg, due to noise, reflections, and/or inadvertent motion). In some cases, multiple measurement deltas may be used in order to confirm the match. For example, in addition to using a first measurement delta 1016a relative to first and second arrangements, a second measurement delta may be determined relative to second and third arrangements. The first and second measurement deltas can then be compared and, if they are at least within a predetermined range of one another, the match can be confirmed. The multiple measurement deltas may be used in connection with moving a display 310 closer to and then further away from the analyte sensor system 308 or vice versa.

Figure 10C illustrates an arrangement 1000 of the analyte sensor system 308 and display device 310. As shown, analyte sensor system 308 may be connected to display device 310 via communication means 305 and may be connected to display device 310 via link 1012c. Reference will be made to Figure 10C in connection with various embodiments of the present disclosure involving confirmation/validation of an initial selection or identification of display device 310 and analyte sensor system 308, particularly when considering that an amount moderate user interaction is adequate.

In exemplary implementations, arrangement 1000c may result from prompting the user to move display 310 further from analyte sensor 308 relative to arrangement 1000a shown in FIG. 10A. This is illustrated by the relative representations of links 1012a/c. Correspondingly shown in the metric profile 1010c is the metric value 1014c for the metric 1002c corresponding to the link 1012c (e.g., the metric value 1002 may correspond to a distance between the display device 310 and the sensor system 308). of analyte and/or radio conditions such as a path between display device 310 and analyte sensor system 308). In some cases, the first and second links may be physically the same in terms of distance, transmission, general radio conditions, etc., but may be represented or referred to at different times and thus referred to as the same. the same as different links. For example, a signal may be sent over a first link at first, and it may be mentioned that the signal sent over the same physical link at a second time (for example, in terms of distance, etc.) send via second link due to different timing. In profile 1010c In addition, a measurement value 1014a and measurement delta 1016b are shown in the measurement data, which, in this example, represents a difference between measurement values 1014a and 1014c.

With respect to the transition from array 1000a to array 1000c, various techniques may be employed in order to confirm/validate an initial selection/identification of display device 310 and analyte sensor system 308. In embodiments, the measurement value 1014c may be monitored/determined and compared to the lower threshold 1006. As such, it can be determined that although for layout 1000a the measurement value 1014a was at or above the lower threshold 1006, on/after moving to layout 1000c the measurement value 1014c is below the lower threshold 1006 . lower threshold value 1006. Having crossed the measurement value 1014c the lower threshold 1006 (in a positive or negative sense) can be used to indicate that the initial identification/selection was adequate/appropriate. As mentioned, in embodiments, the change between measurement values 1014c/a may be positive rather than negative. For example, measurement value 1014c may be measured initially, when lower threshold 1006 is not exceeded. The user may then be prompted to move display device 310 closer to analyte sensor system 308, thereby moving to an arrangement such as arrangement 1000a where measurement value 1014a exceeds lower threshold 1006. As described in connection with FIGS. 10A and 10B, a measurement delta can also be used in this case.

With additional reference to FIGS. 10A-10C, additional features of the present disclosure relating to confirmation/validation of an initial selection/identification of display device 310 and analyte sensor system 308 will now be described. In particular, a multi-step procedure can be used for confirmation/validation. For example, it may first be determined that the measurement value 1014a is at or above the lower threshold 1006 but not the upper threshold 1004. The user may then be prompted to move the display device 310 relatively closer to the analyte sensor system 308 . In some cases, the prompt may be to move the display device 310 very close to, or to a defined position with respect to the user's body and/or the analyte sensor system 308, for example to the user's hip or abdomen, etc., or, for example, within six inches or the like of the analyte sensor system 308. This may result in measure value 1014b, which is at or above upper threshold 1004, and may also result in measure delta 1016a.

Next, in response to meeting or exceeding the upper threshold 1004, the user may be prompted to move the display 310 further away from the analyte sensor system 308 . In embodiments, the prompt may be to move the display 310 to approximately an arm's length or the like, or a defined position relative to the user's body, or a specified distance from the home position (eg, 24 inches). . This may result in measure value 1014c, which is below lower threshold 1006, and may result in measure delta 1016c. Thus, the sequence of first crossing the upper threshold 1004 (eg, in a positive direction) and then crossing the lower threshold 1006 (eg, in a negative direction) with respect to measurement values can be used to confirm / validating an initial selection/identification of the display device 310 and the analyte sensor system 308 . Conversely, a sequence involving first crossing the lower threshold 1006 (eg, in a negative direction) and then crossing the upper threshold 1004 (eg, in a positive direction) may equally be employed.

Many variations of the foregoing are contemplated in connection with the present disclosure. For example, in some cases, in an initial arrangement (eg, arrangement 1000b), display device 310 may be positioned relatively close to analyte sensor system 308 such that measurement value 1014b or the like may exceed the threshold 1004 upper. For example, the user may be holding the display device 310 in close proximity to the analyte sensor system 308 . This can happen, for example, if the analyte sensor system 308 is placed on the user's abdomen and the user removes the display device 310 from the user's front pocket near the user's abdomen. In this case, a single measurement or derivative (eg, RSSI measurement based on close proximity of display 310 and analyte sensor system 308) may not be sufficient to make accurate identification/selection. In this case, it may not be feasible for the user to move display 310 closer to analyte sensor system 308 . Thus, the user may first be prompted to move the display 310 away from the analyte sensor system 308, for example far enough that a threshold such as lower threshold 1006 is crossed and a value is obtained. 1014c measure or similar. The user may then be prompted to move display 310 closer to analyte display 310, essentially retrieving array 1000b such that upper threshold 1004 is crossed and measurement value 1014b or the like is obtained.

Therefore, and as described above, examples of solutions involve employing multiple thresholds. For example, if the detected RSSI is at or above the upper threshold value 1004 (for example, when display device 310 and analyte sensor system 308 are relatively close), display device 310 display may be configured to prompt the user to move the display 310 further away from the analyte sensor system 308 . In some cases, the user is prompted to move the display 310 further until the RSSI is below the lower threshold 1006, or vice versa. In some cases, a measurement value that is below the lower threshold 1006 may be referred to as a measurement value that meets the lower threshold 1006. Based on the two measurements, they can Additional operations may be implemented to confirm RSSI matching. For example, the upper and lower thresholds 1004 and 1006 may be compared with each other. Alternatively, a threshold delta 1008 (which may be, for example, an effective difference between the thresholds) may be calculated between the upper and lower thresholds 1004 and 1006. Or both of these operations can be combined. If the measurements or calculations derived from them meet certain requirements, RSSI matching can be confirmed.

With respect to exemplary implementations employing threshold and/or measurement deltas for validation/confirmation purposes, various configurations are contemplated in connection with the present disclosure. In embodiments, as mentioned above, a threshold delta may be used for validation confirmation. For example, referring to Figures 10A and 10B, measurement value 1014a can be obtained in relation to array 1000a. Then, the display device 310 can be arranged in the arrangement 1000b and the measurement value 1014b can be obtained. The measurement delta 1016a can then be compared to a threshold delta, and if the threshold delta is exceeded, the match can be confirmed.

In embodiments, the threshold delta may be set in conjunction with the manufacturing procedure and/or configuration of the analyte sensor system 310. For example, the threshold delta may be initially set based on a predicted or averaged delta in a measurement value. With respect to RSSI-based pairing techniques, the threshold delta may be set based on intended use cases for the pairing of display device 310 and analyte sensor system 308 . An example of an intended use case is that the user removes the display device 310 from the user's pocket or other typical location and holds the display device 310 for viewing or the like. Such an action by a typical user may result in a position change of display 310 of approximately 16 inches, by way of example. Accordingly, an initial value for the threshold delta can be set to the predicted change in RSSI corresponding to a position change of approximately 16 inches. In some specific examples for illustration purposes, the RSSI change may be approximately 20 dBm (for example, 20 dBm if devices are moved closer to each other or -20 dBm if devices are moved farther from each other) . In embodiments, the initial value for the threshold delta may be determined based on the nature of aspects of the analyte sensor system 308 . For example, if aspects of analyte sensor system 308, such as sensor 10, are made variable (eg, in size) based on characteristics of an intended user, the value initially set for the threshold delta it can also be made to vary (eg, to accommodate a predicted position change based on a difference in user size). In some cases, the threshold delta may be based on the device type of the display 310.

However, it will be appreciated that other display devices 310 may be in range of the analyte sensor system 308 and may be changing position relative to it, thus possibly generating RSSI changes that may satisfy the established threshold delta. To zero in on the appropriate/suitable display device 310 for your match, additional features may be used in conjunction with the threshold delta. For example, upper threshold 1004 may be used to determine if, at a closer position, the measurement value (eg, measurement value 1014b) exceeds upper threshold 1004 . In another example, a determination may be made as to whether the upper threshold 1004 and/or lower threshold 1006 is crossed as a result of otherwise arranging the display 310. Alternatively or additionally, various measurement values may be compared with each other and the largest value may be chosen (eg, in conjunction with a threshold delta determination or otherwise). The characteristics or set of criteria applied may be tailored based on environmental conditions, such as the number of displays 310 in range of the analyte sensor system and/or the measured values detected for one or more displays 310 .

In exemplary implementations, the initially set threshold delta may be adapted and/or reprogrammed/recalibrated after installation of the analyte sensor system 308 . By way of illustration, during setup of the analyte sensor system 308, user information/characteristics may be determined (eg, based on an input received by the analyte sensor system 308), including with respect to the size of the user, for example. This information can be used to tailor the initial threshold delta for the user, for example, based on the size of the user or intended use of the device. In embodiments, a profile may be established based on analyzing validation/confirmation cases over time, and the profile may then be used to adjust the initially established threshold delta. For example, when the initially set threshold delta may have been set to 16 inches, the user may most frequently store remote display 310 on the user's desktop. After storing/analyzing information regarding validation/confirmation events over time, the threshold delta can be modified based on actual user behavior and/or device confirmation, such that, for example, the threshold delta can be increased up to 20 inches.

The following is a specific example of operations that can be used to confirm/validate an initial identification/selection using a measure such as RSSI. First, the user may connect the analyte sensor 10 to the sensor electronics module 12 of the analyte sensor system 308 (referring, for example, to FIGS. 2A, 2B). Thereafter, the analyte sensor system 308 may begin sending warning messages (referring, for example, to Figure 7A and/or Figure 7J). Next, display device 310 receives a warning message from analyte sensor system 308 . This may occur, for example, in connection with arrangement 1000a (with reference to Fig. 10A). By way of illustration, the measurement value 1014a, corresponding in this case to RSSI, may be approximately -20 dBm. For example, measurement value 1014a may be a derivative of a signal received via link 1012a.

Display 310 may then, based on measurement value 1014a exceeding lower threshold 1006, notify the user that there is a discoverable analyte sensor system 308 available for connection. A user notification from display device 310 may include, for example, one or more visual indicators such as a light or screen effect/display element, banner or pop-up message; an auditory indicator such as a beep or other sound; and/or haptic feedback. The notification may originate from the analyte sensor system 308, the display device 310, or both. Display 310 may then prompt the user to, for example, move display 310 closer to analyte sensor system 308 .

The user may then move the display device 310 closer to the analyte sensor system 308 . In embodiments, this may entail changing the position of display device 310 or analyte sensor system 308 or both. This may result, for example, in arrangement 1000b (with reference to Figure 10B). By way of illustration, the measurement value 1014b, corresponding in this case to a derivative of an RSSI-based signal, may be approximately 0 dBm. Based on the measurement value 1014b exceeding the upper threshold 1004 (or, for example, the measurement delta 1016a exceeding a threshold delta), the display device 310 may validate/confirm the identification/selection and notify the user accordingly. same.

In embodiments, the identification/selection may be confirmed/validated with a moderate amount of user interaction and based on various factors in addition to, or alternatively to, the RSSI measurement values. For example, it may be determined that display device 310 has previously identified and/or connected to analyte sensor system 308 (e.g., via the above steps for RSSI pairing or via other operations described herein with respect to identification/selection) and validation/confirmation may be based on this determination. It will also be appreciated that the foregoing examples of operations can be used to connect display device 310 with a desired analyte sensor system 308, even in the case where there are multiple analyte sensor systems 308 within range of display device 310 . display and/or even in the case where there are multiple display devices 310 within range of the analyte sensor system 308 .

Referring again to Figure 10D, layout 1020a and measurement profile 1030a are illustrated. In some cases, multiple analyte sensor systems 308a, 308b may attempt to connect to a single display device (eg, display device 310a). For example, in a physician's office, two patients may be wearing respective analyte sensor systems 308a and 308b and be in relatively close proximity to one another, and both patients may have respective display devices 310a and 310b. Due to the proximity of the analyte sensor systems 308a, 308b to the displays 310a, 310b, both analyte sensor systems 308a, 308b may attempt to connect to one of the displays 310a and 310b. In particular, with reference to layout 1020a and measurement profile 1030a, all measurement values 1034a, 1034c, and 1034d may initially be identified as indicating connections that can be made, for example, due to the proximity of display 310a to the analyte sensor system 308a (eg, corresponding to measurement value 1034a) and analyte sensor system 308b (eg, corresponding to measurement value 1034d) and from display device 310b to analyte sensor system 308b ( for example, corresponding to the measurement value 1034d). While each of these measurement values exceeds threshold 1006, measurement value 1034b is below threshold 1006 and thus analyte sensor system 308a may not be identified as available for connection to measurement device 310b. display. In such circumstances, it may be more difficult for one of the display devices 310a, 310b to determine which analyte sensor system 308a, 308b is appropriate for its connection and, due to the proximity of multiple devices, a single RSSI measurement may be difficult. insufficient for pairing.

Accordingly, in embodiments of the present disclosure, for example, display device 310a may determine measurement values 1034a and 1034d (eg, based on RSSI) for signals received from each of systems 308a and 308b. analyte sensor and distinguishing between the two analyte sensor systems 308a and 308b based on one of the measurement values exceeding a predetermined, adjustable, programmable, or adaptive threshold, such as upper threshold 1024 and/or lower threshold 1026. Alternatively, for example, display device 310a may compare the two measurement values (eg, RSSI or a derived signal received over links) with each other and select the analyte sensor system 308a associated with the higher of the two. values (in this case, the measure value 1034a, which may be an RSSI value).

In some cases, for example, both measurement values 1034a and 1034d (for example, which may be RSSI values) exceed lower threshold 1026 and/or may be relatively close in magnitude, and therefore display 310a may not being able to easily distinguish between the analyte sensor systems 308a and 308b based on measurements from an array alone. Also, in some cases, the analyte sensor system 308a may not be able to distinguish between display devices 310a, 310b using measurements for a single array of devices.

One way to distinguish between devices involves moving one or more devices, as mentioned above in connection with Figures 10A-10C. Referring to Figures 10D and 10E, for example, in arrangement 1020b, display 310a has been moved relatively close to analyte sensor system 308a compared to arrangement 1020a. As a result, the measurement value 1034a' has increased according to the measurement delta 1036a related to the change in distance between the links 1032a' and 1032a. The measurement delta 1036a may be compared to a threshold delta and, based on the comparison, it may be determined that the display device 310a is validated/confirmed for pairing. Furthermore, although the measurement value 1034d' has also increased relative to the measurement value 1034d, this increase is relatively small and can be distinguished by comparison with a threshold delta. In embodiments, additional comparisons with additional thresholds described herein may be employed. In embodiments, if no condition that can confirm/validate a selection/identification is satisfied, one or more of the thresholds (including threshold deltas) may be adjusted and measurements retaken.

In embodiments, as mentioned above, a threshold delta may be employed such that matching is confirmed when the display 310 and analyte sensor system are brought closer together such that the delta of threshold is met by, or exceeded by, the change in measurement values, and then the display 310 and analyte sensor system are moved further away from each other such that the threshold delta is again met. meets, or is exceeded by, the change in measurement values. In this case, an absolute value of the threshold delta can be used. In some cases, instead of being based on the threshold delta being exceeded in both directions, the match may be based on the threshold delta being within a range or margin of error. For example, this may represent that the distance moved in a first direction (eg closer) is close to or equal to a distance moved in the negative direction (eg further away). Movement closer and then farther or vice versa can be detected by deriving derivatives of signals received on the links corresponding to the closer array and the farther array and determining, for example, that an upper threshold (in one direction) was crossed first. positive) and then a lower threshold was crossed (in a negative direction). The opposite can also be used. Alternatively or additionally, movement closer then further away or vice versa can be detected by obtaining derivatives of signals received on the links corresponding to the closest array and the furthest array and determining, for example, that a first difference between the derivatives (resulting moving closer) at least meets a positive threshold delta and then a second difference in derivatives (resulting from moving farther) meets at least a negative threshold delta. The opposite can also be used. In some cases, when a threshold is being used to determine whether a derivative of a signal or derivatives of signals has crossed the threshold in a negative direction, a derivative below the threshold may be considered to meet, or exceed, the threshold. threshold (for example, in the negative direction).

Another way to distinguish between the analyte sensor systems 308a, 308b is as follows. In embodiments, display device 310a may scan and detect identification information (eg, identification numbers or the like) for each of the analyte sensor systems 308a, 308b and provide the available analyte sensor systems 308a, 308b. , etc. and their respective identification information to the user. The user can then use the display device GUI 340 to select the analyte sensor system 308a, 308b with the desired identification information.

Another possible problem involved in selecting/identifying analyte sensor systems such as analyte sensor system 308 arises from the possibility that, in some cases, not all analyte sensor systems 308a, 308b, etc. ., are reactivated or become active a uniform amount of time after the analyte sensor 10 is coupled to the sensor electronics module 12 of the analyte sensor system 308 . That is, there may be a non-uniform time delay between the physical/electrical connection of the sensor electronics module 10 and the analyte sensor 12, and the powering up of the sensor electronics module 12 and the transmission of warning messages. As mentioned, this time delay may vary between analyte sensor systems 308a, 308b, etc.

This variation may result, for example, in display device 310 seeking to connect to the first analyte sensor system 308a that has become active or reactivated, even though the appropriate analyte sensor system 308b for its connection is the second analyte sensor system 308b that has not yet become active or has been reactivated. As such, display device 310 may be connected to less than preferred analyte sensor system 308a rather than preferred analyte sensor system 308b.

Accordingly, embodiments of the present disclosure involve a wakeup circuit that can be employed in the analyte sensor system 308 to implement a smooth wakeup time or smooth time delay that occurs between the physical/electrical connection of the electronics module 12 and analyte sensor 10, and powering up sensor electronics module 12 and transmitting warning messages (eg, at step 795a with exemplary reference to FIG. 7J). The time delay can be variable or programmable and can be set to a very small value or zero, such that reactivation occurs almost immediately after connecting the analyte sensor 10 to the sensor electronics module 12. Or the time delay can be relatively larger. Regardless of the actual value of the time delay, the control circuit reactivation can be used to apply a uniform value throughout the analyte sensor systems 308a, 308b, etc. In this way, for example, the first and second analyte sensor systems 308a, 308b wake up or become active at approximately the same time and the display 310 can select and connect to the appropriate analyte sensor system 308b, for example. example as described above in relation to various matching techniques involving various amounts of user interaction.

Yet another possible problem involved in the selection/identification of the analyte sensor system 308 arises from secondary lobes that may be present in antennas of the analyte sensor systems 308. These secondary lobes can create interference between signals and affect the calculation of RSSI and other measurements, thereby possibly hampering the semi-automated measurement-based matching techniques described above (eg, including techniques involving RSSI).

In embodiments of the present disclosure, and in some cases particularly where a plurality of analyte sensor systems 308 are in geographic proximity to one another, out-of-band matching by display 310 may be used for selection/identification of system 308a. of the plurality of analyte sensor systems 308a, 308b, etc. For example, near field communications (NFC) may be used to select/connect to analyte sensor system 308a and initiate pairing/connection therewith by display 310a.

In embodiments, other techniques for selection/identification of analyte sensor system 308a from among the plurality of analyte sensor systems 308a, 308b, etc. may be employed. Such techniques may include one or more of display device 310a taking a photograph of information carried on analyte sensor system 308a that is desired to be selected/identified, scanning a barcode or QR from analyte sensor system 308a or related container, using invisible ink in the analyte sensor system 308a and/or product container thereof and using thermal ink in the analyte sensor system 308a and/or container.

In embodiments, the analyte sensor system 308 and/or display device 310 may include an accelerometer, optical or infrared detector, microphone, or other sensor that can be used to help select/identify the analyte sensor system 308 and /or display device 310. For example, display device 310 may prompt the user to touch analyte sensor system 308 one or more times. This can cause the analyte sensor system to start sending warning messages. Subsequently, the user may initiate the selection/identification of the analyte sensor system 308 using RSSI or another of the previously described techniques. Alternatively or additionally, input to the accelerometer, optical or infrared detector, microphone, or other sensor that can be used to confirm/validate that the selected/identified analyte sensor system (eg, via RSSI matching) is the preferred device . In some embodiments, display device 310 may pair by selecting/identifying analyte sensor system 308a from the plurality of analyte sensor systems 308a, 308b, etc., jointly authenticating analyte sensor system 308a and the application. and additionally exchanging keys for data encryption, secure connection or links, and device privacy. In such embodiments, display device 310 may initially generate and exchange short-term keys using modulated signals (eg, modulated infrared signals) and analyte sensor system 308a may employ a photodetector, light pipe, or emitter. of IR to receive and decode or demodulate such signals. Following this, a final key exchange can be performed between the display device and the analyte sensor system over a BLE link that is encrypted using the short-term key.

In embodiments, gestures may be performed by the user holding the display device 310 in order to confirm/validate a selected/identified analyte sensor system and/or display device. For example, by moving a device in a figure eight shape or the like, the user can confirm/validate a selection/identification. In embodiments, auditory input (eg, voice recognition) may be used for confirmation/validation of a device. In embodiments, the user may also be prompted to touch or shake the analyte sensor 308 and/or display device 310 in order to trigger validation/confirmation. Such accelerometer-based gestures/events can trigger prompts that may be time-bound to detect and possibly limit collisions caused by prompts.

With respect to the features described above related to a moderate amount of user interaction, it should be appreciated that, in some cases, the techniques described may be used for the purposes of initially identifying/selecting devices and not simply to confirm/validate a initial identification/selection.

Figures 13C to 13P provide operational flow charts illustrating various operations that may be performed in accordance with embodiments of the present disclosure, for example in relation to the second layer or level of user interaction described above. For purposes of illustration, reference is made herein to Figures 10A to 10E and component numbers shown therein. However, one of ordinary skill in the art will appreciate, after studying the present disclosure, that similar components from other figures in this disclosure may be included within the scope of the present description of figures 13C to 13P.

Embodiments shown in Figure 13C involve aspects of method 1304 to identify a device for connection. In operation 1315A, method 1304 involves display device 310a receiving a first signal from analyte sensor system 310a of a set of analyte detection systems 310a, 310b, and so on. The first signal is received over a first link (eg, link 1032a). Operation 1315B involves the display device determining a derivative of the first signal (eg, resulting in measurement value 1034a). Operation 1315C involves display 310a identifying analyte sensor system 308a for selection based on the derivative of the first signal.

Turning now to Figure 13D, embodiments involving aspects of method 1306 are shown, including additional details regarding operation 1315C, mentioned above with reference to Figure 13C. As shown in FIG. 13D, step 1315C may include, in step 1320A, comparing the derivative of the first signal to a first threshold. Additionally, operation 1315C may include, at operation 1320B, determining whether the derivative of the first signal at least meets the first threshold. In operation 1320C, method 1306 may involve selecting analyte sensor system 308a for connection based on determining that the derivative of the first signal at least meets the first threshold.

Referring again to FIG. 13C, in operation 1315D, method 1304 may include display 310a receiving a second signal from analyte sensor system 308a (e.g., via first link 1032a or the second link 1032a'). Operation 1315E involves display 310a determining a derivative of the second signal. In operation 1315F, method 1304 may include selecting analyte sensor system 310a for connection based on the derivative of the second signal.

Figure 13E illustrates embodiments involving aspects of method 1308, including additional details regarding operation 1315F, mentioned above with reference to Figure 13C. As shown in FIG. 13E, step 1315F may include, in step 1325A, comparing the derivative of the second signal to a second threshold. Additionally, operation 1315F may include, at operation 1325B, determining whether the derivative of the second signal at least meets the second threshold. In operation 1325C, operation 1315F optionally includes comparing the derivative of the first signal to the second threshold. In operation 1325D, operation 1315F may include determining whether or not the derivative of the second signal meets at least the second threshold.

Figure 13F illustrates embodiments involving aspects of method 1312, including additional details regarding operation 1315F, mentioned above with reference to Figure 13C. As shown in FIG. 13F, step 1315F may include, in step 1330A, comparing the derivative of the second signal to the first threshold. Additionally, operation 1315F may include, at operation 1330B, determining whether or not the derivative of the second signal at least meets the first threshold.

Embodiments shown in FIG. 13G involve aspects of method 1314 for identifying a device for connection. In operation 1335A, method 1314 involves display 310a receiving a first signal from analyte sensor system 308a of a set of analyte sensor systems 308a, 308b, and so on. The first signal is received over a first link (eg, link 1032a). Operation 1335B involves the display device obtaining a derivative of the first signal (eg, measurement value 1034a). Method 1314 optionally includes, at step 1335C, sending display device 310a a first response signal to analyte sensor system 308a over the first link. In operation 1335D, method 1314 may include obtaining, for display 310a (eg, from analyte sensor system 308a), a derivative of the first response signal. The derivative of the first response signal may be generated by and received from the analyte sensor system 308a. In operation 1335E, the method 1314 includes identifying the analyte sensor system 310a for connection based on whether the derivative of the first signal meets or is above a lower threshold (eg, lower threshold 1026 ). Identification in operation 1335E may also be based on a comparison of the derivative of the first signal with the derivative of the first response signal. In operation 1335F, method 1314 optionally includes generating an indication to configure display 310a according to a second link (eg, link 1032a' in arrangement 1020b). Operation 1315C involves identifying, display device 310a, analyte sensor system 308a for selection, based on the derivative of the first signal. Operation 1335G involves providing display device 310a and/or analyte sensor system 308a with indication to the user of display device 310a.

In operation 1335H, method 1314 may include display 310a receiving a second signal from analyte sensor system 308a (eg, via a second link such as link 1032a'). Operation 1335J involves display 310a obtaining a derivative of the second signal (e.g., display 310a may generate the derivative itself or may receive the derivative from analyte sensor system 308a or another source). remote). In operation 1335K, method 1314 may include display 310a receiving a third signal from analyte sensor system 308a (eg, received via a third link). In some cases, the third link may be the same as, similar to, or within a predetermined window of values with respect to the first link. Operation 1335L involves obtaining, display 310a, a derivative of the third signal. In operation 1335M, method 1314 may include selecting, display device 310a, analyte sensor system 308 for connection, based on one or more of the derivatives of the first, second and third signals. For example, display device 310a may select analyte sensor system 308 for connection based on one or more of: the derivative of the first signal meets or is above an upper threshold (eg, threshold 1024 upper); the derivative of the first signal does not meet or is above the upper threshold; the derivative of the second signal meets or is above the upper threshold; the derivative of the third signal is below the lower threshold (eg, threshold 1026); a comparison of the derivative of the second signal with the derivative of the first signal or vice versa; the derivative of the first signal meets or exceeds the upper threshold and the derivative of the second signal is less than the derivative of the first signal; the derivative of the second signal meets or exceeds the upper threshold and the derivative of the first signal is less than the derivative of the second signal; a comparison of the derivative of the third signal and the derivative of the second signal; etc.

Embodiments shown in FIG. 13H involve aspects of method 1316 to identify a device for connection. In operation 1340A, method 1314 involves receiving, analyte sensor system 308a, a first signal from display 310a of one of a set of displays 310a, 310b, etc. The first signal is received over a first link (eg, link 1032a). In operation 1340B, method 1316 optionally includes obtaining, analyte sensor system 308a, a derivative of the first signal (eg, measurement value 1034a). In operation 1340C, method 1316 may include sending analyte sensor system 308a a response signal. In operation 1340D, method 1316 may include obtaining, for analyte sensor system 308a, a derivative of the response signal (eg, from display 310a). The derivative of the response signal can be used in a similar manner as described in connection with Figure 13G. In operation 1340E, method 1316 includes selecting, analyte sensor system 308a, display 310a for selection, based on the derivative of the first signal meeting or above a lower threshold (for example, the lower 1026 threshold). This selection may be further based on the derivative of the response signal, similar to the manner described above with respect to FIG. 13G.

In operation 1340F, method 1316 may include generating an indication to configure display 310a according to a second link (eg, link 1032a'). The indication may be generated based on the derivative of the first signal being below an upper threshold (eg, threshold 1024). This indication may be based, in some cases, on the derivative of the first signal meeting or above an upper threshold (eg threshold 1024). Method 1316 may include, in operation 1340G, sending the indication to display device 310a to provide the indication to a user of display device 310a. In embodiments, the analyte sensor system 308a may provide the indication directly to the user (eg, visually, audibly, and/or haptically, etc.).

In operation 1340H, method 1316 optionally includes receiving, analyte sensor system 308a, a second signal from display device 310a (eg, via the first or second link). Operation 1340J involves obtaining, analyte sensor system 308a, a derivative of the second signal. In operation 1340K, method 1316 may include receiving, analyte sensor system 308a, a third signal from display device 310a (see, for example, the description of the third link set forth above in connection with FIG. 13G). . Operation 1340L involves obtaining, analyte sensor system 308a, a derivative of the third signal. Embodiments of method 1316 include, in operation 1340M, generating a representation of user input from an accelerometer.

In operation 1340N, method 1316 optionally includes selecting display device 310a for connection. This selection may be based on one or more of: the derivative of the first signal meets or is above the upper threshold; the derivative of the second signal is below the lower threshold; the derivative of the second signal meets or is above the upper threshold; the derivative of the first signal does not meet or is above the upper threshold; the derivative of the third signal is below the lower threshold; a comparison of the derivative of the second signal with the derivative of the first signal; the derivative of the first signal meets or exceeds the upper threshold and the derivative of the second signal is less than the derivative of the third signal or vice versa; a comparison of the derivative of the third signal and the derivative of the second signal; rendering of user input from the accelerometer; etc.

Embodiments shown in FIG. 13J involve aspects of method 1318 to identify a device for connection. In operation 1345A, method 1318 optionally includes prompting, display device 310a, a user to physically contact analyte sensor system 308a in order to trigger analyte sensor system 308a to send a message. first signal to display device 310a. In operation 1345B, method 1318 includes obtaining, display 310a, a derivative of a first signal received over a first link (eg, first link 1032a). Operation 1345C involves generating, display device 310a, an identification for selection. This generation may be based on the derivative of the first signal meeting or above a lower threshold (eg, lower threshold 1026 ).

Method 1318 optionally includes, in operation 1345D, generating an indication to configure display 310a according to a second link (eg, link 1032a' in arrangement 1020b). Is generation may be based on the derivative of the first signal being below an upper threshold (eg, upper threshold 1024 ). Alternatively, this generation may be based on the derivative of the first signal meeting or above the upper threshold. The prompt may include, for example, an instruction for the user to move the display 310a closer to the analyte sensor system 308a. In operation 1345E, method 1318 may include sending the indication to display device 310a to provide the indication to a user of display device 310a (eg, via GUI 340).

In operation 1345F, embodiments of method 1318 include obtaining, display 310a, a derivative of a second signal (eg, received over the second link or the first link). In operation 1345G, method 1318 may include obtaining, display 310a, a derivative of a third signal. The third signal may be received via a third link, which may be substantially similar in nature to the third link described above.

In operation 1345H, method 1318 may include displaying a prompt for the user to provide user input to an accelerometer (eg, by touching the accelerometer of a device that hosts the accelerometer, such as analyte sensor system 308a and/or or display device 310a). In operation 1345J, method 1318 may include receiving a representation of user input in the accelerometer.

Method 1318 may include, in operation 1345K, generating display device 310a a selection for its connection. This generation may be based on one or more of: the derivative of the first signal meets or is above the upper threshold; the derivative of the second signal is below the lower threshold; the derivative of the second signal meets or is above the upper threshold; the derivative of the first signal does not meet or is above the upper threshold; the derivative of the third signal meets or is above the upper threshold; a comparison of the derivative of the second signal and the derivative of the first signal; the derivative of the first signal meets or exceeds the upper threshold and the derivative of the second signal is less than the derivative of the first signal or vice versa; a comparison of the derivative of the third signal and the derivative of the second signal; the derivative of the second signal meets or exceeds the upper threshold and the derivative of the third signal is greater than the derivative of the second signal or vice versa; etc.

Embodiments shown in FIG. 13K involve aspects of method 1322 to identify a device for connection. In operation 1350A, method 1322 includes obtaining, display 310a, a derivative of a first signal received over a first link (eg, first link 1032a). Operation 1350B involves display 310a obtaining a derivative of a second signal received over a second link (eg, link 1032a'). In operation 1350C, method 1322 optionally includes calculating a difference between the derivative of the first signal and the derivative of the second signal. Operation 1350C involves generating a comparison of the derivative of the first signal and the derivative of the second signal, eg, comparing the difference or an absolute value of the difference to a predetermined value (eg, a threshold delta). In operation 1350E, method 1322 optionally includes obtaining, display 310a, a derivative of a third signal received over a third link. In operation 1350F, method 1322 may include calculating a difference between the derivative of the third signal and the derivative of the second signal. In such cases, a comparison can be generated between the difference between the derivative of the third signal and the derivative of the second signal (for example, a second difference), and the difference between the derivative of the first signal and the derivative of the second signal. signal (for example, a second difference).

Operation 1350G involves display device 310a generating a selection for its connection. This generation may be based on one or more of: comparing the derivative of the first signal and the derivative of the second signal; comparing the derivative of the second signal and the derivative of the third signal; the comparison of the first and second differences; etc.

In summary, with respect to the second user interaction layer, many combinations of the features described above may be employed depending on the applicable use case.

A third layer or level of user interaction involved in the selection/identification of the analyte sensor system 308 and/or display device 310 may be associated with a minimal amount of user interaction. In one example, an application (eg, analyte sensor application 330) may be downloaded or resident on display device 310 and/or in some cases on analyte sensor system 308 . Application 330 may monitor the duration of a connection established between display device 310 and analyte sensor system 308 and determine which analyte sensor system 308 is preferred based on the duration of the connection. For example, if the display device 310 and analyte sensor system 308 remain connected for more than a predetermined, adjustable, adaptive, or programmable amount of time (for example, 1 hour), then the application 330 may determine that the device Display 310 has selected/identified the appropriate analyte sensor system 380 for connection.

Figure 13L provides an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the present disclosure, for example in connection with the third layer or level of user interaction described above. For purposes of illustration, reference is made in this case to Figures 10A to 10E. and component numbers shown therein. However, one of ordinary skill in the art will appreciate, after studying the present disclosure, that similar components from other figures in this disclosure may be included within the scope of the present description of Figure 13L.

Embodiments shown in FIG. 13L involve aspects of method 1324 for identifying a device for connection. In operation 1355A, method 1334 includes establishing, display device 310a of a set of display devices 310a, 310b, etc., a connection to analyte sensor system 308a of a set of sensor systems 308a, 308b. of analyte, etc. In operation 1355B, the method 1334 includes generating, display device 310a, a confirmation for its connection to analyte sensor system 308a based on a connection duration exceeding a predetermined, programmable, adaptive and/or predetermined amount of time. variable.

A fourth layer or level of user interaction involved in the selection/identification procedure may be associated with an adjustable, variable and/or hybrid amount of user interaction. In one example, application 330 may be downloaded or resident on display device 310. Operation under the fourth layer of user interaction may involve employing combinations of the various techniques described above with respect to layers one through three. In a specific example, the layer one search and select method may be used and combined with the RSSI matching described in layer two and/or another of the techniques described in connection with layers two and three. In addition, the applicable amount of user interaction can be adjusted on the fly if, for example, no discoverable devices are paired successfully, connections are dropped unexpectedly, or more often than expected, based on usage input, based on on performance characteristics inferred over time periods and from multiple systems, etc.

Some embodiments related to the layers or levels of user interaction involved in the selection/identification procedure will now be described. In this regard, embodiments include scanning, display device 310, to search for analyte sensor systems 308a, 308b, etc. in the vicinity of, or discoverable by, display device 310 and monitoring systems 308a, 308b, analyte sensor etc. to determine if and how to connect with them.

By way of example, display device 310 may receive warning messages from analyte sensor 308a, when one or more analyte sensor systems 308a, 308b, etc. they may be in the vicinity of, or discoverable by, the display device 310 . Warning messages may also be received from the analyte sensor system 308b, etc. in certain situations. Display 310 may then obtain a derivative (eg, RSSI) of a first signal received from any of the analyte sensor systems 308a, 308b, etc., and use the derivative and a condition (eg, , a threshold for the derivative) to identify and generate a selection for your connection. In embodiments, the received signal may be the warning messages sent by sensor systems 308a, 308b, etc. Based on certain conditions, the display device 310 may identify and then establish a first connection with the analyte sensor system 308a using the selection for its connection. For example, the first connection may be established if, for an amount of time (which, for example, may be predetermined, adjustable, adaptive, programmable, variable, etc.), the display device 310 does not receive a warning message to from analyte sensor systems 308b, etc. other than the analyte sensor system 308a or the display device 310 has not derived a derivative of a second signal that satisfies the condition, wherein the second signal is sent by analyte sensor systems 308b, etc. other than analyte sensor system 308a.

Stated another way, in this example, if, for an amount of time, only one analyte sensor system 308a is present in the vicinity of display 310 or can be otherwise discovered or identified by display 310, this may trigger connection establishment between analyte sensor system 308a and display device 310 . Alternatively or additionally, when additional analyte sensor systems are present in the vicinity of display 310 or otherwise discoverable by display 310, if, for an amount of time, only analyte sensor system 308a sends a signal for which the derivative satisfies a threshold, this may cause the display device to identify analyte sensor system 308a as the preferred analyte sensor system to pair with and then trigger connection establishment with sensor system 308a of analyte. In specific cases, this may indicate that the connection must be established between analyte sensor system 308a and display device 310 because no other sensor system 308b, etc. has established a strong enough signal (for example, based on RSSI) for the amount of time to be adequate/correct for your connection. It is contemplated that pairing and subsequent data connections may be established based on various methods and procedures described herein.

In some embodiments, display device 310 may continue to monitor various conditions (eg, signal over a period of time) and derive a derivative of a signal from one of the other analyte sensor systems 308b, etc. . while connected to the analyte sensor system 308a and identifying and establishing a second connection between the display device and itself using the derivative. For example, this may make it easier for display device 310 to identify and then connect to display system 308b, 308c. analyte sensor, etc. most suitable or correct, when the first connection established with the analyte sensor system 308a as described above was not or was perhaps not the most suitable or the most correct.

In another example, it may be the case that a number of analyte sensor systems 308a, 308b, etc. present in the vicinity of, or sending warning messages to, the display device 310 exceeds a predetermined number of display devices 310. In such a case, the derivative and the amount of time alone may not be sufficient for identification and connection establishment purposes. As such, by way of example, display device 310 may provide a prompt to a user of display device 310, where the prompt is related to identification of the analyte sensor system and subsequent connection establishment. In one example, connection may be established between display device 310 and one of analyte sensor systems 308a, 308b, etc. based on an input received at display 310 in response to the prompt for identification. Such input may be, but is not limited to, any of the various forms described above in connection with the first user interaction layer.

Embodiments shown in FIG. 13M involve aspects of method 1326 for identifying a device for connection, including with respect to one or more of the first, second, third, and fourth layers or levels of user interaction described above. In operation 1360A, the method 1326 optionally includes presenting an instruction (eg, through the GUI 340 of the display device 340 or through the analyte sensor system 308a, including, for example, visually, audibly, and/or or haptic) to a user to provide input to an accelerometer housed in analyte sensor system 308a and/or display device 310a, where the input initiates the transmission of signals (eg, prompts, pilot signals, etc.). In operation 1360B, method 1326 includes operating in one of a plurality of modes to generate a selection for connection between display device 310a and analyte sensor system 308a. The plurality of modes may correspond to the first, second, third, and so on, user interaction layers.

Figure 13N illustrates embodiments involving aspects of method 1328, including additional details regarding operation 1360B, mentioned above with reference to Figure 13M. As shown in FIG. 13N, embodiments of operation 1360B involve operating in a first of the plurality of modes. The first mode may be associated with a first layer or level of user interaction. With respect to operating in the first mode, operation 1360B includes operation 1365A, which involves receiving an input regarding analyte sensor system 308a that identifies analyte sensor system 308a from among a set of sensor systems 308a, 308b of analyte, etc. In operation 1365B, operation 1360B may include generating the selection for connection to analyte sensor system 308a based on received input. The input may be received at one or both of the analyte sensor system 308a and the display device 310a.

Figure 13P illustrates embodiments involving aspects of method 1332, including additional details regarding operation 1360B, mentioned above with reference to Figure 13M. As shown in FIG. 13P, embodiments of operation 1360B involve operating in a second of the plurality of modes. Operating in the second mode may be associated with a second layer or level of user interaction. With respect to operating in the second mode, operation 1360B includes operation 1370A, which involves taking a derivative of a first signal received over a first link (eg, link 1032a). This acquisition may be accomplished by either or both of the analyte sensor system 308a and the display device 310a. In operation 1370B, method 1332 includes generating an identifier for selection based on the derivative of the first signal. In operation 1370C, method 1332 optionally includes taking a derivative of a second signal received over a second link (eg, link 1032a'). Method 1332 further includes, in step 1370D, generating a selection (eg, of analyte sensor system 308a and/or display device 310a) for connection based on the identification for its selection and one or more of the derived from the second signal and user input.

In embodiments, operating in the second mode according to method 1332 further includes, in operation 1370E, calculating a difference between the derivative of the first signal and the derivative of the second signal. In operation 1370F, method 1332 may include comparing the difference to a threshold (eg, predetermined, adaptive, variable, programmable, etc.). If the difference meets or exceeds the threshold, method 1332 may include confirming the selection for its connection, in operation 1370G.

Figure 13Q illustrates embodiments involving aspects of method 1334, including additional details regarding operation 1360B, mentioned above with reference to Figure 13M. As shown in FIG. 13Q, embodiments of operation 1360B involve operating in a third of the plurality of modes. The third mode of operation may be associated with a third layer or level of user interaction. With respect to operating in the third mode, operation 1360B includes operation 1375A, which involves forming a connection between display device 310a and analyte sensor system 308a. In operation 1375B, the method 1334 includes generating a connection confirmation based on maintaining the connection for at least a predetermined, adaptive, variable, and/or programmable amount of time.

Thus, by flexibly employing the previously described layers of user interaction, including in some cases combinations thereof, embodiments of the present disclosure may be optimally configured across various use cases, network and battery conditions and situations, user preferences and/or characteristics, and so on.

I. Authentication and encryption

In situations involving two devices connecting over a network (wireless or otherwise), authentication may be used in an attempt to prevent unauthorized devices from making a connection. For example, when sensitive data is being exchanged, authentication may be used in an attempt to prevent unauthorized devices or entities from gaining access to the data. In this regard, authentication protocols may be employed to establish or validate the identity of connecting devices. In some cases, the authentication techniques may vary depending on the connection model being used. For example, if an intermittent connection model is being used, a different authentication technique may be implemented than if a continuous connection model is being used.

Figure 7A is an operational flow chart illustrating various operations that may be performed in connection with embodiments of method 700 for wireless communication of analyte data between analyte sensor system 708 and display device 710, as well as in connection with with embodiments of related systems, apparatus and devices. In some cases, method 700 may be used in connection with authentication of display device 710 and/or analyte sensor system 708 (for example, in two-way authentication), such that analyte data may be exchanged under conditions. authorized.

The various tasks performed in connection with the method illustrated in Figure 7A may be performed, for example, by a processor executing instructions implemented in non-transient computer readable medium. The tasks or operations performed in connection with the method may be performed by hardware, software, firmware, or any combination thereof embedded in one or more computing devices, such as one or more of the analyte sensor system 708 and measurement devices 710 . display. It will be appreciated upon review of the present disclosure that the method may include any number of additional or alternative tasks or operations. The exemplary operations shown in Figure 7a need not be performed in the illustrated order, and the procedure may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein with specific reference to Figure 7A.

In some examples described below, the analyte values are glucose values based on one or more measurements made by the analyte sensor 10 (referring to FIGS. 1A, 2A, and 2B) and/or sensor 405 (referring to FIGS. Figure 4) for illustration purposes. However, it should be understood, after studying the present disclosure, that the analyte values can be any other analyte value described herein. Wireless data communication between the analyte sensor system 708 and one or more of the display devices 710 may occur periodically, at times separated by an update interval designated "Tinterval" which may correspond to a length of time between two sessions. consecutive wireless communications between transceiver 360 of analyte sensor system 708 and transceiver 320 of display device 710 (referring to Fig. 3B). Alternatively or additionally, the update interval can be considered as a period of obtaining and sending a newly measured glucose value. Transmitting messages or warning signals, establishing a data connection (for example, a communication channel), and requesting and sending data may occur during wireless communication sessions that each last for an active period or time designated “TActive” within an update interval Tinterval. One point to keep in mind in this case is that Tinterval and/or TActive may vary between sessions. Between two consecutive wireless communication sessions, components of the analyte sensor system 708 (eg, transceiver 360) may enter LPM or a similar mode, such as an inactive or sleep mode for an inactive period designated "TInactive." This can allow battery life conservation and/or reduce peak voltage requirements, for example.

Therefore, in some authentication and connection schemes used for analyte data communication, analyte sensor system 708 may periodically connect to display device 710 . For example, communication session 720 may implement such a connection and authentication scheme. More specifically, as shown in FIG. 7A, the communication session 720 may be implemented during a time interval Tinterval. As mentioned above, Tinterval may include an active portion corresponding to TActive and an inactive portion corresponding to TInactive. Generally speaking, during TActive, analyte sensor system 708 and display device 710 are connected and actively exchanging messages (eg, based on operation 705 and/or sub-operations thereof), although there may be periods during TActive during which the analyte sensor system 708 enters LPM or the like, as described above.

As for the connection, in exemplary implementations, the analyte sensor system may transmit one or more warning messages in operation 705 during communication session 720. An advisory message can be thought of as an invitation for display device 710 to establish a data connection with analyte sensor system 708 (eg, via transceiver 360). Figure 8 illustrates an example structure for the advisory message 800 which, in some cases, may be transmitted for purposes of establishing a connection between two devices, in accordance with various aspects of the present disclosure (eg, with reference to Figure 7A, at step 705 and the like). The transmitted warning messages may then be received at displays 710 (eg, via transceiver 320). For authentication purposes, the analyte sensor system may share an identification number with the display device, wherein the identification number is associated with the analyte sensor system.

In some embodiments illustrated by way of example in Figure 7A, the analyte sensor system 708 is supposed to participate in an initial system configuration because, for example, the analyte sensor system 8 has recently been powered on for the first time. and/or is not currently paired with any display device 710. By way of illustration, a user of display device 710 can identify a new or never used analyte sensor system 708 to pair with display device 710 by entering identification information (eg, a serial number). associated with analyte sensor system 708 via a custom application (eg, application 330) running on display 710 using a GUI 340 that may be presented on display element 345 (eg, a display element). touch screen display).

As mentioned above, during the communication session 720, an authentication procedure may need to be performed in connection with a data connection procedure corresponding to operation 705b and/or a data transmission procedure corresponding to operation 705d. To establish a data connection with the analyte sensor system 708, the display device 710 may continuously listen or scan until an alert message transmitted by the analyte sensor system 708 is received. Once the analyte sensor system begins transmitting alert messages in operation 705a, one, two, or more alert messages may be required for display device 710 to receive and respond to an alert message. In some embodiments, the analyte sensor system 708 stops sending additional alert messages once one of the display devices 710 receives and responds to an alert message, for example, by acknowledging and/or sending a connection request (eg, as part of operation 705b). In other embodiments, the analyte sensor system may continue to send additional alert messages even after receiving a response from one display device 710, so that another of the display devices 710 may receive and respond to one of the messages. additional warning messages.

Accordingly, operation 705b may involve the analyte sensor system receiving a connection request from display device 710 and responding thereto by granting or denying the request. If the analyte sensor system 708 grants the connection request, an acknowledgment or other message may be transmitted to the display device 710 as part of operation 705b. Thereafter, a data connection may be established between analyte sensor system 708 and display device 710 . However, according to operation 705c, an authentication procedure may be employed before actually exchanging data in operation 705d. Authentication may involve the exchange of various messages, including cryptographic hash and challenge values and signaling related thereto, between the analyte sensor system and the display device, according to a one-way or two-way handshake procedure.

For example, as part of operation 705c, display 710 may request a challenge value from analyte sensor system 708 . In response to the request, the analyte sensor system 708 sends a challenge value to the display 710. The display device may then generate a cryptographic hash value based on both the challenge value received from the analyte sensor system 708 and identification information associated with the analyte sensor system 708 . As yet another part of operation 705c, the display device may then transmit the cryptographic hash value to the analyte sensor system 708 . Display device 710 may also transmit additional information (eg, information related to the type of display device 710, whether the display device is a medical device or a personal electronic device, for example).

The analyte sensor system 708 (eg, via transceiver 360) receives the crypto hash value from the display 710, decodes the identifying information from the crypto hash value, and verifies that the identifying information received matches identification information associated with the analyte sensor system 708, which may have been previously stored in the storage 365 of the analyte sensor system 708, such as during the manufacture/configuration of the analyte sensor system 708. The analyte sensor system 708 may also validate the crypto hash value received from the display 710 by comparing the received hash value with a mirror crypto hash value that was generated by the analyte sensor system 708 (e.g. , based on the previously sent challenge value). Upon verification, analyte sensor system 708 may send a signal confirming successful authentication to display device 710 . Once authenticated, the analyte sensor system 8 and display device 110, 120, 130, 140 may exchange information to determine how the data will be exchanged (eg, a specific frequency, time slot assignment, encryption, etc.). .). Figure 12C also illustrates aspects of the previously described handshake procedure.

The procedure described above can be considered as a one-way authentication procedure. During a two-way authentication procedure (not specifically shown in Figure 7A, but see, eg, Fig. 12B), additional operations may take place as part of operation 705c. For example, in addition to the cryptographic hash value transmitted from display device 710 to analyte sensor system 708, display device 710 may also send a new challenge value to analyte sensor system 708 . The analyte sensor system 708 may then generate an additional crypto hash value using the new challenge value received from display 710 and transmit the additional crypto hash value back to display 710. Upon receiving the additional hash value, display device 710 may validate the additional hash value. In exemplary implementations, validation of the additional crypto hash value received from the analyte sensor system 708 may be performed by the display 710 by comparing the received additional hash value to a mirror hash value that generated the display device 710 (eg, based on the previously sent new challenge value). In this manner, two-way authentication between analyte sensor system 708 and display device 710 can be performed. Upon authentication, data may be exchanged with the understanding that the data is being received by and from a valid (or approved) device. It will be appreciated that many varieties of operation 705c and secondary operations thereof are contemplated in the present disclosure. For example, analyte sensor system 708 and display device 710 may reverse roles with respect to operation 705c. That is, operation 705c may be initiated by requesting, analyte sensor system 708, a challenge value from display 710, thereby activating the operations described above but in reverse between analyte sensor system 708 and display device 710.

In addition, communication session 720 may also include exchanging an application key between analyte sensor system 708 and display device 710 . For example, in the aforementioned authentication procedure, the identification information associated with the analyte sensor system 708 may be used as an application key for the purpose of encrypting data and other signaling transmitted between the analyte sensor system 708 and the user. display device 710. Through the exchange of cryptographic hash and challenge values described in connection with operation 705c, such an application key can be efficiently shared between analyte sensor system 708 and display device 710 . Thus, in embodiments of the present disclosure, the application key may be used for both authentication and encryption purposes. The application key can be a random number in some cases. In some cases, the application key may be literally exchanged (either encrypted or unencrypted) between the analyte sensor system 708 and the display device 710 (eg, as a challenge value, etc.). In other cases, the actual application key is not exchanged, but by exchanging the challenge and crypto digest values, the application key may be derived respectively by the analyte sensor system 708 and by the display 710. As such, the application key may be used, for example, by the analyte sensor system 708 to encrypt analyte data for transmission to display device 710, and the application key may be used by display device 710 to decrypt the data. received analyte data. Of course, other exchanged information can also be encrypted.

In exemplary installations, the application key may be generated at a software/application level of the analyte sensor system 708 and/or the display device 710. In some such installations, only the application key may be exchanged (ie, no cryptographic digest exchange and challenges) and then used for authentication and encryption. The application key can be, for example, a randomly generated number. Alternatively, the software-generated application key may be exchanged in addition to the hash/challenge values, for authentication and encryption purposes. Encryption, eg as described above, may be performed simultaneously during authentication or after authentication or both, in various embodiments.

The application key, in exemplary embodiments, may be obtained from server system 334. In some such embodiments, storage 334b may include identification information associated with analyte sensor system 708 (eg, an identification number) and the application key. The identification information may simply be mapped to the application key, and/or the identification information may be hashed or otherwise combined with the application key in some cases. Display device 710 may request such information by sending a message to server system 334, where the message includes at least some of the identification information. By way of example, display device 710 may send an alert message to server system 334 that includes an identification number for a specific analyte sensor system 708 (this identification number may have been received through at least partial pairing). with the analyte sensor system 708). In response, the server system 334 may provide the display device 710 with the application key for the relevant analyte sensor system 708 . Upon receiving the application key, the display device 710 can use the key to authenticate/communicate with the analyte sensor system 708 and decrypt encrypted information received from it (and also encrypt information being sent to it).

In some cases, analyte sensor system 708 may contain mapping (eg, in storage 365) that associates particular application keys with particular display devices 710 based on identification information from analyte sensor system 708 . As such, authentication may be performed based on the application key received by display device 710 from server system 334 and the application key may be used for encryption/decryption of analyte data sent by the analyte sensor system 708 . In this manner, authorization regarding communications (including encrypted data sharing) between analyte sensor 708 and a given display device 710 can be managed/established. In other cases, for example when the application key is associated with an identification number of the analyte sensor system 708, the analyte sensor system 708 may derive an expected application key based on the identification number and compare the key application key with information regarding the application key as received from display device 710, in order to determine that data exchange with display device 710 is authorized.

Alternatively or additionally, application key exchange may be performed directly between analyte sensor system 708 and display device 710 using WiFi or NFC. Exchanging the application key may involve sharing the application key between analyte sensor system 708 and display device 710 in an isolated and/or secure area (such as at a user's home) to prevent interception by an attacker. foreign or unknown device. Additionally, the application key can itself be encrypted with an additional key for added security. The characteristics of the key may be based on one or more of the type of data to be encrypted; the network environment; and user settings. By way of example, the encryption method applied using the application key may be based on Advanced Encryption Standard 128 (AES). Alternatively or additionally, a private encryption method may be used. Such an encryption method may be executed on display device 710, including in some cases in an application (eg, application 330) running on display device 710.

The complexity of the encryption scheme employed may be based on the level of security desired. For example, different levels of complexity may be used for different types of data. A more complex encryption scheme may be employed for the exchange of analyte data (eg, estimated glucose values) compared to, for example, calibration data or time-synchronized data. Characteristics of the application key can also be made to vary in different situations. By way of example, the length of the application key may be chosen based on the amount of security desired and/or the encryption scheme or protocol being employed. The encryption scheme may in some cases employ salts that may be used in connection with the exchange of cryptographic hash values, and the salts may be encrypted and exchanged between the analyte sensor system 708 and the display 710.

The application key may also be changed from time to time, for example, in an event-triggered, random and/or periodic manner. This may be done in response, for example, to the passage of a predetermined amount of time; restarting the analyte sensor system 708 of a subsystem thereof or the display device 710; a trigger factor related to another device (eg, a rogue device) attempting to connect to the analyte sensor system 708; and/or user input. For example, the application key may be set to expire after a predetermined amount of time has elapsed and may be refreshed or renewed after that. Alternatively or additionally, if the analyte sensor system 708 and/or display device 710 reboots or experiences an outage, a new application/encryption key may be generated and shared between the analyte sensor system 708 and device 710. display. In some cases, the application key may be changed according to a key rotation scheme. Furthermore, the frequency with which the application key can be changed can be made to vary according to the level of security desired (eg, more frequent change corresponding to an increased level of security).

With additional reference to FIG. 7A, after the authentication procedure is completed according to operation 705c, the analyte sensor system 708 and connected display device 710 participate in data communication at operation 705d, during which device 710 The connected display device may request and receive desired information (eg, analyte data, control information, identification and/or instruction information) from the analyte sensor system 708 . When the data communication is completed in operation 705d, the data connection may be terminated in operation 715 (eg, by closing the established communication channel). At this point, the transceiver 360 and/or the processor 380 of the analyte sensor system 708 (or with reference to FIG. 4, the radio 425 and the processor 420) may be turned off. This can be done, for example, by causing the transceiver 360 and/or processor 380 (etc.) to enter an LPM or similar mode, eg, a sleep or sleep mode. In some embodiments, transceiver 360 (or radio 425) is completely powered off during a sleep mode. In other embodiments, transceiver 360 is in a low power mode using only a small fraction (eg, 1-10%) of normal current/power. In FIG. 7A, this period which generally corresponds to operation 715 is designated TInactive.

Figure 7B provides, by way of illustration, an example of typical intermittent communications schemes between analyte sensor system 708 and display device 710, according to method 702 for wireless communication of analyte data between analyte sensor system 708 . analyte sensor and display device 710 . As shown in FIG. 7B, method 702 involves multiple occurrences of communication session 720. Communication session 720 having a time length of Tinterval occurs. Subsequently, communication session 720' occurs, having a time length of Tinterval', which may be equal to or different from Tinterval, in various embodiments described herein.

Thus, it will be appreciated that, in typical intermittent communications schemes between analyte sensor system 708 and display devices 710, the aforementioned connection and authentication procedure may be repeated periodically (eg, according to a designated time Tinterval). for each subsequent data communication. For example, the method may involve the exchange of up to 20 or more messages before reporting any data (eg, analyte values). In addition, the procedure can be restarted if the exchanged messages fail or packets are dropped. This can result in a battery depletion of the analyte sensor system 708 .

Accordingly, aspects of the present disclosure include an improved authentication scheme. The enhanced authentication scheme of the present disclosure reduces the number of messages exchanged between the analyte sensor system 708 and the display device 710 that connects to it, while maintaining a sufficient level of security for analyte and other data. data communicated between analyte sensor system 708 and display device 710 . In this way, the complexity and network load involved with communications between the analyte sensor system 708 and the display device 710 can be reduced, thereby increasing the overall reliability and power consumption involved with such communications. Generally, the enhanced authentication scheme involves stepping through the aforementioned authentication procedure of the communication session 720 (eg, in operation 705c) using at least one application key for authentication and connection between the system analyte sensor 708 and display device 710, as well as for data encryption in embodiments, and then bypassing the authentication procedure on subsequent connections and/or communication sessions.

Thus, it will be appreciated that, in some intermittent communications schemes employing the intermittent connection model between the analyte sensor system 708 and display devices 710, the aforementioned connection and authentication procedure may be repeated periodically (e.g. , according to a time designated by Tinterval) for each subsequent data communication. For example, the method may involve the exchange of up to 20 or more messages before any data (eg, analyte values) are reported. In addition, the procedure can be restarted if the exchanged messages fail or packets are dropped. This can result in a battery depletion of the analyte sensor system 708 .

Also, it will be appreciated that in some continuously connected communication schemes employing the continuous connection model between analyte sensor system 708 and display device 710, the connection and authentication procedure may be repeated, for example, if the connection is lost and reacquired later, if the connection parameters are updated, if the connection model is changed from the intermittent connection model to the continuous connection model, etc. Briefly referring to Figure 7J for purposes of illustration, the method 722 for communicating analyte data in a continuous connection model includes various messages that may be communicated before any data is exchanged. For example, advertisement messages may be sent in step 795a, then data connection messages and connection parameters may be exchanged in step 795b, and then authentication/encryption related messages may be exchanged in step 795c.

Therefore, for various connection models, there is a need to optimize the authentication procedure in order to reduce, or in some cases eliminate, the repetition of the authentication procedure at regular intervals or when it can be avoided otherwise, while Adequate levels of security and data protection are still maintained.

Accordingly, aspects of the present disclosure include improved authentication schemes for both the intermittent connection model and the continuous connection model. The enhanced authentication schemes of the present disclosure reduce the number of messages exchanged between the analyte sensor system 708 and the display device 710 that connects to it, while maintaining a sufficient level of security for analyte data and data. other data communicated between analyte sensor system 708 and display device 710. In this way, the complexity and network load involved with communications between the analyte sensor system 708 and the display device 710 can be reduced, thereby increasing the overall reliability and power consumption involved with such communications.

Generally, the enhanced authentication scheme involves stepping through the aforementioned authentication procedure of either the communication session 720 (eg, in operation 705c) or the communication session 780 (eg, in operation 795c) that uses at least one application key for an authentication and connection between the analyte sensor system 708 and the display device 710, as well as for data encryption in embodiments, and then bypassing the authentication procedure in connections, communication sessions and /or subsequent data exchanges. For example, and as will be described herein, for the intermittent connection model and/or the continuous connection model, the authentication procedure may be bypassed on subsequent connections and/or communication sessions. And, in some cases, for example, for the continuous connection model, repeating the authentication procedure can be avoided by maintaining an authenticated connection after the start authentication. With respect to both intermittent and continuous connection models, an application key used for authentication purposes may also be used for encryption/scrambling of subsequently exchanged data.

Referring now to FIG. 7C, method 704 for wireless communication of analyte data between analyte sensor system 708 and display device 710 is illustrated in connection with implementations of the aforementioned enhanced authentication scheme. Method 704 includes establishing a first connection between analyte sensor system 708 and display device 710 . This may occur in connection with communication session 720. As such, establishing the first connection may include performing two-way authentication between analyte sensor system 708 and display device 710 (eg, based on the exchange of application key-related information, in operation 705c, for example). example).

Method 704 also includes establishing a second connection between the analyte sensor system and display device 710 . As shown in FIG. 7C, in embodiments, this may occur in connection with communication session 725. More specifically, as shown in Figure 7C, the communication session 725 may be implemented during a time interval Tinterval', which may be equal to or different from Tinterval. Tinterval' may include an active portion corresponding to TActive' and an inactive portion corresponding to TInactive'. During TActive', communication session 725 may involve operation 735 and child operations thereof.

In this case, it should be noted that, in the communication session 725, the second connection need not be established to include the authentication procedure that may be included in the communication session 720 (eg, in operation 705c). Instead, in operations 735a and 735b, the alert and connection may occur, and after establishing the second connection in this manner, method 704 includes the transmission of data in operation 735d. More specifically, in operation 735d, analyte sensor system 708 may transmit, for example, encrypted analyte values and other data to display device 710, in response to a data request sent by display device 710. The encrypted analyte value may have been encrypted using the application key used for authentication in the authentication procedure in the communication session 720, and/or may involve the use of encryption key. Encrypting the transmissions using an application key can maintain privacy/security even in the absence of performing authentication procedures during the communication session 725 . In other words, in the communication session 725, the authentication procedure described above, including two-way authentication, can be bypassed. In this way, the number of messages exchanged in the establishment of the second connection (and therefore the power consumption) can be reduced. In addition, the application key may also be used to decrypt encrypted data exchanged between analyte sensor 708 and display device 710 . For example, during operation 735d, display device 710 may decrypt encrypted data (eg, encrypted analyte data, which may include encrypted glucose data) received from analyte sensor 708 and vice versa.

When the data communication is complete in operation 735d, the data connection may be terminated in operation 745. At this point, the transceiver 360 and/or the processor 380 of the analyte sensor system 708 (or, with reference to Figure 4, radio 425 and processor 420). In FIG. 7C, this period generally corresponding to operation 745 is designated TInactive'.

At this point, it should be noted that regardless of the connection model employed or which of the communication sessions described above is used, the application key may be updated and/or shared between devices at predetermined, configurable, variable, programmable and/or intervals. or adaptable. In some cases, during or after connection establishment, display device 710 and analyte sensor system 708 may negotiate an interval at which the application key has to be shared and/or updated.

Figure 7D illustrates an exemplary implementation of method 706 for wireless communication of analyte data between analyte sensor system 708 and display device 710 in relation to implementations of the enhanced authentication scheme discussed above. As shown in FIG. 7D, method 706 involves communication session 720. Communication session 720 occurs, having a time length of Tinterval. Subsequently, an instance of communication session 725 occurs, having a time length of Tinterval', which may be equal to or different from Tinterval, in various embodiments described herein. Then, an instance of communication session 725' occurs, having a time length of Tinterval", which may be equal to or different from Tinterval', in various embodiments described herein. Communication session 725' may be substantially similar to communication 725, apart from possibly having a different interval length.

By following communication session 720 with one or more communication instances 725, 725', etc., the overall number of messages exchanged during analyte data communication (and thus power consumption) can be reduced. However, in this case it will be appreciated that, in some cases, method 706 may involve returning to communication session 720 after implementing communication session 725, 725', etc. for one or more connections. This may be done adaptively or based on user input, and may be done for security purposes based on network conditions or triggered events (eg, a malicious device trying to connect). In other words, returning to the communication session 720 from time to time, for example to exchange information regarding a new/modified application key, as discussed above, may allow for increased security.

Referring now to FIG. 7E, method 712 for wireless communication of analyte data between analyte sensor system 708 and display device 710 is illustrated in relation to implementations of the aforementioned enhanced authentication scheme. Method 712 includes establishing a first connection between analyte sensor system 708 and display device 710 . This may occur in connection with the communication session 720 corresponding to Tinterval. As such, establishing the first connection may include performing two-way authentication between analyte sensor system 708 and display device 710 .

The method 712 also includes establishing the communication session 740 which may be implemented during a time interval Tinterval', which may be equal to or different from Tinterval. Tinterval' may include an active portion corresponding to TActive' and an inactive portion corresponding to TInactive'. During TActive', communication session 740 may involve operation 765 and child operations thereof.

In this case, it should be noted that communication session 740 may not include establishing a second connection between analyte sensor system 708 and display device 710. For example, communication session 740 as illustrated does not include the data connection aspects of operation 735b shown in FIG. 7C in connection with communication session 725. Communication session 740 as illustrated also does not include the authentication procedure that may be included in communication session 720 (eg, in operation 705c). Instead, in operation 765a, method 712 involves sending one or more warning messages to display device 710.

As such, as part of the communication session 740, the analyte sensor system 708 may transmit a first warning message (eg, during operation 765a). The first warning message may include at least a first portion of the analyte value. The analyte value may have been encrypted (eg using an application key) prior to transmission, but need not be. In other words, with respect to the communication session 740, the analyte sensor system 708 may use one or more prompt messages to transmit encrypted or unencrypted analyte values or analyte data and/or other signaling (such as , for example, timing and control information) as well as other information that may be included in warning messages.

In some cases, as will be described in more detail with reference to Figure 8, for example, an advisory message may take the form of a packet. By way of example, the analyte value (whether encrypted or not) may be included in a reserved field in the warning message packet. Specifically, in some cases, a manufacturing data or other slot in the packet may include a reserved field of 1 byte or more. This reserved field is an example of how analyte data or another form of payload can be included in the warning message. As mentioned above, in addition to or instead of the analyte value, the warning message may also include a timestamp associated with the analyte value.

However, in some exemplary implementations, there may be insufficient space in the warning message/packet for both the analyte value and the associated timestamp. In some such cases, method 712 may involve dividing the payload, which may include the (encrypted) analyte value and associated data, into multiple parts. The first warning message may then indicate that a second warning message includes a second portion of the analyte value and/or associated data. The first alert may indicate this by tagging the first portion of the payload, where the tag indicates to the display device 710 receiving the alert message that a subsequent alert message may include a second portion of the payload.

The aforementioned tagging of the first portion of the payload can take various forms. For example, a relatively simple tag may only indicate that a subsequent warning message includes a second portion of the payload. A relatively more complex tag may additionally indicate the type of content to be included in the second portion of the payload or how the payload has been divided or distributed among warning messages. The first portion may include, for example, an encrypted analyte value, and the applied tag may indicate that the subsequent warning message will include the associated timestamp.

In other words, depending on the communication session 740, advisory messages may be transmitted during operation 765a for the purposes of communicating analyte data to displays 710. With the payload encrypted using an application key, privacy/security can be maintained even in the absence of performing authentication procedures during the communication session 740 . In other words, in the communication session 740, the authentication procedure described above, including two-way authentication, can be bypassed. Also, since the payload is included in the advertisement messages, the data connection request and data transmission procedures (eg, operations 735b and 735d, respectively) may also be bypassed or skipped. In this way, the number of messages exchanged according to the communication session 740 (and thus the power consumption) can be reduced with respect to other communication sessions.

Returning to Figure 7E, communication session 740 may also include, in operation 765b, giving display 710 acknowledgment of the warning message(s) sent during operation 765a, sending an acknowledgment message (ACK). In some cases this acknowledgment may trigger a data connection procedure between the analyte sensor system 708 and the display device 710 that acknowledges the data. receipt. For example, analyte sensor system 708 may in turn send an ACK to display device 710 and thereby form a connection. The data connection procedure established in connection with operation 765b, in exemplary installations, may be used to renew the application and/or encryption key(s) and/or to exchange other data, such as, for example , calibration data, timing information, and the like. When communications are complete in operation 765, data transmission may be terminated in operation 775. At this point, transceiver 360 and/or processor 380 of analyte sensor system 708 (or, with reference to FIG. 4, the radio 425 and the processor 420). In FIG. 7E, this period generally corresponding to operation 775 is designated TInactive'.

Figure 7F illustrates an exemplary implementation of method 714 for wireless communication of analyte data between analyte sensor system 708 and display device 710 in relation to implementations of the enhanced authentication scheme discussed above. As shown in FIG. 7F, method 714 involves communication session 720. Communication session 720 occurs, having a time length of Tinterval. Subsequently, an instance of communication session 740 occurs, having a time length of Tinterval', which may be equal to or different from Tinterval, in various embodiments described herein. Then, an instance of communication session 740' occurs, having a time length of Tinterval", which may be equal to or different from Tinterval', in various embodiments described herein. Communication session 725' may be substantially similar to communication 725, apart from possibly having a different interval length.

By following communication session 720 with one or more instances of communication sessions 740, 740', etc., the overall number of messages exchanged during analyte data communication (and thus power consumption) can be reduced. However, in this case it will be appreciated that, in some cases, method 714 may involve returning to communication session 720 after implementing communication session 740, 740', etc. for one or more connections. This may be done adaptively or based on user input, and may be done for security purposes based on network conditions or triggered events (eg, a malicious device trying to connect). In other words, returning to the communication session 720 from time to time may allow for increased security.

Figure 7G illustrates an exemplary implementation of method 716 for wireless communication of analyte data between analyte sensor system 708 and display device 710 in relation to implementations of the enhanced authentication scheme discussed above. As shown in FIG. 7G, method 716 involves communication session 760. In exemplary installations of method 716, communication session 760 involves the exchange of information related to pairing, application keys, and timing parameters related to possible communications between analyte sensor system 708 and display device 710 using a first wireless protocol. But such an exchange can be optimized using certain types of wireless protocols. By way of example, the first wireless protocol may be WiFi or Near Field Communication (NFC). In other examples, the first wireless protocol may use RFID, another proximity-based wireless connection, or the like.

In this way, authentication can be circumvented, such as can occur using BLE (eg, according to operation 705c with reference to FIG. 7A), along with the normally associated exchange of numerous messages. By way of illustration, NFC may be used between analyte sensor system 708 and display device 710 for the purpose of exchanging information such as pairing, encryption information (eg, application key information and/or scheme), alert parameters (including, for example, frequency/period, duration, timing, and/or nature of alerts), connection interval information, and information related to display device 710 (for example, type of display device, preferences , etc.). The exchanged information can then be used by display device 710 to receive and decipher (where applicable) analyte values transmitted by analyte sensor system 708 . Using NFC to exchange authentication-related information in this way can extend the battery life of analyte sensor system 708 and increase the reliability of communications between analyte sensor system 708 and display device 710 .

As shown in FIG. 7G, after using the communication session 760 to exchange information, the communication session 740, which has a time length of Tinterval, occurs. In some installations, communication session 740, including, for example, establishing connection and transmitting analyte values, may be carried out using a second wireless protocol different from the first wireless protocol used in connection with communication session 760. The second wireless protocol can be Bluetooth Low Energy (BLE), for example. Communication session 740 occurs, having a time length of Tinterval', which may be equal to or different from Tinterval, in various embodiments described herein. Thereafter, an instance of communication session 740' may occur, having a time length of Tinterval", which may be equal to or different from Tinterval', in various embodiments described herein.

With further reference to Figure 7G, by continuing to use communication session 760 prior to one or more instances of communication sessions 740, 740', etc., the overall number of messages exchanged for communication of analyte data can be reduced. (and thus power consumption), particularly with regard to the procedure described above and to the exchange of pairing information and the like. However, in this case it will be noted that, in some cases, method 716 may involve returning to communication session 760 after implementing communication session 740, 740', etc. for one or more connections. This may be done adaptively or based on user input, and may be done for security purposes based on network conditions or triggered events (eg, a malicious device trying to connect). In other words, returning to the communication session 760 from time to time may allow for increased security.

Figure 7H illustrates an exemplary implementation of method 718 for wireless communication of analyte data between analyte sensor system 708 and display device 710 in relation to implementations of the enhanced authentication scheme discussed above. In some respects, method 718 is substantially similar to method 716. One difference is that, after implementing communication session 760, method 718 involves implementing communication session 725 instead of communication session 740. Subsequently, an instance of communication session 725' may occur, having a time length of Tinterval", which may be equal to or different from Tinterval', in various embodiments described herein. However, it will be appreciated that various of the communication sessions described above (eg, 720, 725, 740, 760) may be mixed according to the methods described above.

Enhanced authentication schemes may also be provided by the user of a remote service or cloud server, including, for example, aspects of the server system 334 with reference to FIG. 3A. In this regard, Figure 14 is an operational flow diagram illustrating various operations that may be performed in accordance with embodiments of the present disclosure, for example in connection with methods for wireless communication of analyte data. For purposes of illustration, reference is made here to Figures 3A and 7A to 7K, Figure 10D, as well as component numbers shown therein. However, one of ordinary skill in the art will appreciate, after studying this disclosure, that similar components from other figures in this disclosure may be included within the scope of this description of Figure 14.

Embodiments shown in Figure 14 involve aspects of method 1400 for wireless communication of analyte data. Method 1300 includes, in step 1405A, establishing a first connection between analyte sensor system 308 and display device 310, wherein analyte sensor system 308 is one of a set of analyte sensor system 308a, 308b. analyte sensor, etc. (see, for example, Figure 10D). In operation 1405B, method 1400 optionally includes associating, server system 334, for each analyte sensor system (eg, 308) of the set of analyte sensor systems (eg, 308a, 308b, etc., referring to Figure 10D), an application key with identification information for the analyte sensor system 308 . In operation 1405C, method 1400 optionally includes display device 308 receiving the application key from server system 334 associated with identification information for analyte sensor system 308 . For example, the application key may be received by display device 310 from server system 334 in response to display device 310 providing server system 334 with identification information for analyte sensor system 308 .

In operation 1405D, method 1400 includes, during the first connection, exchanging authentication-related information between analyte sensor system 308 and display device 310. Information related to authentication includes the application key. In step 1405E, method 1400 includes transmitting, analyte sensor system 308, an encrypted analyte value to display device 310, wherein the encrypted analyte value has been generated based on the application key. In operation 1405F, method 1400 may include modifying the application key in response to one or more of: the lapse of a predetermined, adaptive, variable, and/or programmable amount of time; restarting analyte sensor system 308 and/or display device 310 or cycling through sleep or power off/off mode; a trigger factor related to another device (eg, a rogue device) attempting to connect to the analyte sensor system 308; and user input.

J. Intermittent connection type

As mentioned above, aspects of the present disclosure also include various connected models for communications between the analyte sensor system 708 and the displays 710. A connection model for communications may be called an intermittent/periodic connection model or an on/off connection model. Depending on an intermittent or on/off scheme, communications between analyte sensor system 708 and display device 710 may be periodic or intermittent in nature, following a defined schedule or event-based/asynchronous. For example, display device 710 may establish connection with analyte sensor system 708 periodically (eg, once every five minutes) in order to receive analyte and other data from analyte sensor system 708 . and/or for the purpose of transmitting data to it.

However, it may be the case that, even if display device 710 successfully connects to analyte sensor system 708 (which is not guaranteed in itself), analyte sensor system 708 may not have data ready to display. be transferred. In such a case, the length of time between successive receptions of data by the display device 710. In some cases, this may result in outdated measurement data, such as analyte data or values, being received by and displayed on display 710 . However, in some use cases, the intermittent connection model can result in power savings over other connection models. Therefore, if battery power is a primary concern with respect to packet loss and/or latency, then the continuous connection model may be preferable to the intermittent connection model. Additionally, it will be appreciated that, according to the intermittent connection model, two displays 710 in the exemplary implementations are not connected to the analyte sensor system 708 at the same time. Instead, different display devices 710 are connected in some cases for different limited amounts of time. Which display devices 710 can be connected and when such devices can be connected to the analyte sensor system 708 can be controlled, for example, using a list such as a white list.

K. Continuous connection model

In some situations, the intermittent model may be appropriate and/or preferable. One such situation may be if a user prefers to monitor an analyte value using multiple displays. For example, if the user has type 1 diabetes, monitoring of analyte data (eg glucose) may be relatively more critical and therefore multiple displays may be employed for greater coverage/redundancy. However, in other circumstances, a continuous connection model may be appropriate and/or preferable. For example, a user may prefer or be limited to using a single display device (for example, for convenience purposes or if the user is traveling or if other display devices have become unavailable, for example, if devices are broken, battery depleted, lost or unable to connect/function, or are being used primarily for other purposes). Other circumstances may also include, for example, that the user has type 2 diabetes and therefore glucose monitoring data may be relatively less critical such that multiple displays need not be employed for redundancy/ coverage.

In still further circumstances, an analyte sensor system such as analyte sensor system 708 may be used for a relatively short amount of time (eg, two weeks). In such a case, the analyte sensor system 708 may be less sensitive to battery/power consumption constraints and may instead impose a higher priority on reliability and/or latency. The continuous connection model, as described in more detail herein, may be generally preferable in such cases. Additionally, attempting to connect to and/or disconnect from a display device such as display device 710 after a relatively long amount of time can be somewhat annoying to analyte sensor system 708 (for example, as to power consumption or computing/processing/radio resources). The continuous connection model may be provided as a way to reduce and/or eliminate the charges that may be associated with such connection/disconnection.

Accordingly, the present disclosure includes employing a continuous connection model. Such a connection model can reduce, in some cases, the latency between the collection of analyte data in the analyte sensor system 708 and the transmission of such data to displays 710 that are connected thereto, by while maintaining a sufficiently low power consumption for the analyte sensor system 708 . Furthermore, the continuous connection model can increase the reliability and predictability of the connection between the analyte sensor system 708 and the display device 710. At a high level, the continuous connection model may involve an initial pairing between the analyte sensor system 708 and display 710, after which the analyte sensor system 708 and display 710 remain connected, essentially without closing the connection or disconnecting. That is, the connection and data exchange are not performed periodically or intermittently as with the intermittent connection model (for example, as discussed with reference to Figs. 7A-7D, etc.), but instead, instead, the connected devices periodically exchange messages to maintain the connection. Once data is available at analyte sensor system 708 (eg, collected by sensor 405 and/or processed by processor 420, noting that Figure 4, as shown, refers primarily to the intermittent connection model but may be modified as described hereinabove to also refer to the continuous connection model), the data may be transmitted to the display device 710 at least in near real time. In this way, the overall accuracy and responsiveness of communications related to analyte data can be increased. An additional advantage associated with the continuous connection model is that the analyte sensor system 708 may be allowed to better mitigate against interference caused by unwanted devices (eg, in some cases, unwanted displays 710) seeking to connect. with the analyte sensor system 708. Therefore, the data exchange reliability can be increased.

In this connection, FIG. 7J illustrates exemplary implementations of method 722 for wireless communication of analyte data between analyte sensor system 708 and display device 710 according to exemplary implementations of the aforementioned continuous connection model.

Communication session 780 may be initiated in connection with method 722. More specifically, as shown in FIG. 7J, communication session 780 may involve operations 795a through 795g and 795a', although, in embodiments, not all of these operations are performed. With respect to the continuous connection model, analyte data may be dropped or lost if the connection between the display device and the analyte sensor system is not maintained. In turn, this can lead to inappropriate or inaccurate representation of analyte information, such as estimated glucose values. Thus, embodiments herein related to the continuous connection model involve holding and/or maintaining an established connection between the analyte sensor system 708 and the display 710. Also, with respect to maintaining the connection, it may sometimes be useful to monitor the connection status to derive and/or provide an indication regarding it. One way this can be done is by using connection parameters, as will be described further herein with reference to Figure 7J.

In operation 795a, method 722 may involve activating a transmitter of analyte sensor system 708 and/or transmitting warning messages. This transmission of warning messages may be substantially similar to operation 705a described above. The warning messages transmitted in operation 795a may be received by one or more displays 710.

In operation 795b a connection may be established between the analyte sensor system and a responsive display device 710 . As shown in FIG. 7J, typically in response to receiving one or more alert messages, display 710 may request a connection to analyte sensor system 708 as part of operation 795b. Also as part of operation 795b, connection parameters may be exchanged between analyte detection system 708 and display device 710 in response to the connection request being sent. In this regard, the analyte sensor system 708 and/or the display device 710 may propose and establish a set of connection parameters on which aspects of a connection between the analyte sensor system 708 and the device may be based. 710 display.

Examples of connection parameters include a connection interval (sometimes referred to herein as connection check interval), slave latency, and monitor timeout. The analyte sensor system 708 and/or display device 710 may use one or more such connection parameters to maintain a connection that lasts as long as desired to continuously monitor analyte levels, as well as to modify characteristics of the analyte. the connection depending on various criteria, such as, for example, criteria related to the analyte sensor system 708, the display device 710, the connection between the two devices (eg, link quality), and/or user preferences or feedback. As shown in FIG. 7J, connection parameters may be exchanged and determined, by way of example, in conjunction with connection establishment (eg, in connection with operation 795b) with respect to analyte sensor system 708 and the display device 710. In connection with operation 795b, the analyte sensor system 708 and display device 710, in exemplary implementations, negotiate and ultimately agree (or not agree) on aspects of the connection parameter set.

For example, with reference to operation 795b, if display device 710 requests a data connection with analyte sensor system 708, connection parameters may be sent from analyte sensor system 708 and proposed to display device 710 , or vice versa. In other examples, connection parameters may be sent/proposed regardless of whether or not a data connection request has been received. Thereafter, display device 710 (or analyte sensor system 708) may, for example, either accept or reject the proposed connection parameters. If the display device 710 (or the analyte sensor system 708) accepts or approves the proposed connection parameters, then the proposed conditions related to the connection parameters can be applied to the connection ultimately established between the sensor system 708 of analyte and display device 710. Such connection parameters may include, by way of example, a connection (or connection check) interval, a slave connection latency parameter, and a monitor timeout parameter. The conditions specified for each of these connection parameters may involve values, ranges of values for the connection parameters, and/or a set of rules or guidelines for one or more of the connection parameters.

Aspects of the connection interval parameter will now be described. In embodiments employing the continuous connection model, the connection between, eg, analyte sensor system 708 and display device 710, may be maintained through the periodic exchange of messages (eg, connection check messages). This is illustrated in Figure J by operation 795e, for example. In operation 795e, messages are periodically exchanged between analyte sensor system 708 and display device 710 in order to maintain a connection. For example, such messages may be transmitted to/from the analyte sensor system 708 simply to indicate that the transmitting device is still connected to the receiving device (eg, a connection check ("ping")). This can be done periodically based on a predetermined connection interval (for example, once every 2 seconds or any amount of time) as defined by the connection parameters. In some case, the set period may be selected/varyed based on criteria such as network parameters or conditions, the type or other characteristic of the display device 710 connected to the analyte sensor system 708, the frequency with which data is transmitted or generated /collected by the analyte sensor system 708, and so on.

Through the periodic exchange of messages, the connection can be maintained between the sensor system 708 analyte and display device 710, thereby allowing the collected analyte data to be exchanged at least in near real time. The connection can be maintained for as long as necessary, including in some instances throughout the useful life of the analyte sensor system 708 . Although the connection is maintained, the analyte sensor system 708 in some examples does not send warning messages. Rather, the connection may continue unless it becomes necessary to issue a disconnect command or until certain criteria are not met, as will be described herein.

In other words, the analyte sensor system 708 (and/or the display device 710) can send a connection check message to the display device 710 (and/or the analyte sensor system 708) according to an interval of time (for example, periodically). In response, the receiving device, for example display device 710 (and/or analyte sensor system 708) may then respond by sending an acknowledgment (ACK) message that acknowledges receipt of the acknowledgment message. connection check. Alternatively, the receiving device, eg, display device 710 (and/or analyte sensor system 708), may send a negative acknowledgment (NACK) indicating that no connection verification message was received. A NACK may be sent, for example, if a connection check message was not received when expected based on the connection interval set (for example, within a predetermined amount of time). In this manner, the messages exchanged may indicate to the analyte detection system 708 and/or display 710 that the connection is maintained and still in progress (for example, if an ACK is sent in operation 795e), or not. it remains as expected (for example, if a NACK is sent or no response is sent in operation 795e). As will be described in more detail herein, if no response is provided to a sent connection check message, and/or if a NACK message is sent, this may indicate that an established connection should be terminated and/or that other action(s) should be taken.

With respect to the connection interval, as previously mentioned, a value or range of values may be set in conjunction with the connection establishment with respect to the analyte sensor system 708 and display device 710 . For example, in some embodiments, every connection interval, the analyte sensor system 708 may send and/or receive a connection check message and then receive and/or send a response thereto in order to maintain the connection according to operation 795e, as mentioned above. A shorter connection interval with more frequently exchanged connection check messages may reduce packet loss between analyte sensor system 708 and display device 710, while a longer connection interval may allow more packet loss. Each connection check message may be configured, in some cases, to indicate when the next connection check message will be sent (eg, the planned amount of time between the sequential exchange of connection check messages).

The device that proposes this connection parameter in conjunction with operation 795b (which may be analyte sensor system 708 or display device 710), may propose a value and/or range of values for the connection interval that can be based on on various factors. For example, the value or range for the on interval may be based on the expected duration of the analyte sensor system 708 . The expected duration may be a suggested length of use, for example, as determined by the manufacturer of the analyte sensor system 708, and/or this value may be programmed into the analyte detection system 708 as part of the manufacturing process. . In another example, the user may determine and/or adjust this value during product configuration or at another time. Additionally, display device 710 may also be subject to power, computational, memory and/or data constraints or other factors that make a particular value and/or range of values suitable for the connection interval. Accordingly, in exemplary implementations, the connection interval may be based on factors drawn from one or both of the analyte sensor system 708 and the display 710.

As mentioned, in exemplary embodiments, the expected life of the analyte sensor system 708 and/or the expected battery life of the analyte sensor system 708 may play a role in determining the value and/or range. of values for the connection interval. In embodiments, for example, the on interval may be proportional to the expected duration of the analyte sensor system 708 . That is, a higher value for the connection interval (for example, connection check messages sent less frequently) may use less battery life, and therefore a longer expected duration may be more likely to be maintained. Also, a lower value for the connection interval (for example, connection check messages sent more frequently) may use more battery life and therefore a longer expected duration may be more likely to be maintained. If, for example, the expected duration for the analyte sensor system 708 was 14 days, the analyte sensor system 708 may wish to set the on interval to between 2 and 10 seconds. It will be appreciated that these numbers are given by way of illustration only.

In some cases, the value and/or range of onset intervals to be employed may be negotiated such as between analyte sensor system 708 and display device 710 . However, it should be noted that in some cases the analyte sensor system 708 may control the negotiation. For example, if the analyte detection system 708 proposes a value and/or range for the connection interval, the display device 710 can accept the proposed value, it can choose a value for the connection interval according to the range provided by the analyte sensor system 708, or you can simply reject the range. Alternatively or additionally, device 710 of display can respond in ways other than accepting or denying the range provided. For example, display device 710 may indicate that its battery will run out soon and therefore will not accept the connection interval range or accept connection to analyte sensor system 708 . In this regard, display device 710 and/or analyte sensor system 708 may include power management circuitry to monitor local battery conditions. The power management circuitry may provide an input that may be used to set, propose and/or update values for connection parameters. For example, a processor (eg, processor 335 or 380, referring to FIG. 3b ) may use an input of the power management circuitry as a trigger point to adjust, modify, or update connection parameters. In exemplary embodiments, display device 710 may provide a counter response that includes a different range of connection intervals based on various conditions, as will be described below. In this case, it will be appreciated that the proposal for the connection interval or other connection parameters could also be provided by the display device 710 to the analyte sensor 708, and that the response to the proposal could be provided from the analyte sensor system 708 . to display device 710.

Furthermore, the on-off interval as proposed and/or counter-proposal may be based on various factors, including for example the current analyte value and/or a trend in the analyte value. For example, the analyte sensor system 708 and/or the display 710 may monitor the analyte value and/or a trend of the analyte (derivative, second derivative, etc.) and request a shorter connection interval when the value is outside a given threshold window. This can provide a more responsive connection during critical times (eg, as defined by the analyte value). In exemplary embodiments, the value/range for the connection interval may be based on information derived about the user, either based on user input or collected based on user monitoring over time. For example, the value/range may be based on the user's physical characteristics, health status, and/or medical history (including, for example, historically measured analyte values).

With respect to the slave latency connection parameter, this connection parameter can be related to the number of abandoned connection check messages or packets (for example, to be sent in operation 795e according to the connection interval described above) that it is allowed before the connection can be terminated or considered terminated, or before a condition related to connection termination is triggered. In embodiments, slave latency may be employed such that, for example, even if a certain number of packets or connection check messages are lost/abandoned, the connection may still be considered active. This connection parameter may be exchanged during connection establishment in conjunction with operation 795b and/or may be modified later (eg in conjunction with operation 795f). Slave latency may be based on or modified depending on various factors, such as quality of service (QoS), time of day, location of analyte sensor system 708, location and/or type of display 710, battery power of the analyte sensor system 708 and/or display device 710, expected lifetime of the analyte sensor system 708, current and/or historical analyte values or trends therein, user characteristics, etc.). A slave latency proposal/counterproposal may be made in conjunction with connection establishment as a value and/or range of values, and may be defined in some cases according to a set of rules. One or both of the analyte detection system 708 and display device 710 may define and/or update the slave latency.

In some cases, if slave latency kicks in (for example, a sufficient number of packets or connection check messages are lost), the response may be to modify one or more connection parameters in an attempt to prevent slave latency from continuing. which is activated. For example, the system may adapt connection parameters on the fly in order to maintain the connection between analyte sensor system 708 and display device 710 . Such a response may be based on a predetermined set of conditions (eg, QoS, time of day, location of analyte sensor system 708, location and/or type of display device 710, battery power of display system 708). analyte sensor and/or display device 710, expected lifetime of analyte sensor system 708, current and/or historical analyte values or trends therein, user characteristics, etc.), in exemplary embodiments.

With respect to the monitor wait parameter, this parameter can be used to determine how strict the slave latency should be implemented. For example, a longer watchdog timeout will allow a more favorable exchange of null packets to maintain the connection. For example, the watchdog timeout may monitor slave latency and may allow slave latency violations to be ignored in some cases, based on various factors, eg, power considerations and/or radio conditions, etc. In other words, in some cases, even if enough connection check messages are lost such that slave latency is triggered, the monitor timeout can be used to effectively override the consequences (for example, disconnection). of analyte sensor system 708 and display device 710, etc.). As with other connection parameters, a proposal/counterproposal of the watchdog timeout parameter may be made in conjunction with connection establishment in operation 795b as a value and/or range of values, and may be defined in some cases based on a set of rules. One or both of the analyte sensor system 708 and display device 710 may define and/or update (eg, at step 795f) the monitor timeout parameter. As with other connection parameters, the watchdog timeout may in some cases be managed by the system without user intervention, including without user visibility therein, or in other instances may be managed by or at least be visible to the user.

In some cases, the watchdog timeout can be modified (for example, in conjunction with the 795f operation) to try to prevent the slave latency from being activated from continuing. For example, the system may adapt the connection monitoring timeout parameter on the fly in order to manage the connection between the analyte sensor system 708 and the display device 710 . Such a response may be based on a predetermined set of conditions (eg, QoS, time of day, location of analyte sensor system 708, location and/or type of display device 710, battery power of display system 708). analyte sensor and/or display device 710, expected lifetime of analyte sensor system 708, current and/or historical analyte values or trends therein, user characteristics, etc.), in exemplary embodiments.

Referring further to Figure 7J, a connection decision may be made as a further aspect of operation 795b by either analyte sensor system 708 or display 710 or both, and thus the connection may be established. Connection. In other cases, as mentioned above, if along with the connection establishment, the analyte sensor system 708 and the display device 710 do not agree on a set of connection parameters, it may be the case that they do not agree. connection is established. That is, the connection decision may be not to establish a connection between the analyte sensor system 708 and the display device. In other cases, the connection decision may be for the analyte sensor system 708 and display device 710 to connect using a connection model other than the continuous connection model (eg, connect using the intermittent connection model). In such a case, communication session 780 may be terminated and another communication session (eg, communication session 720 or 725) may be initiated.

Following a connection decision that results in establishing a connection of the analyte sensor system 708 and the display device 710, in operation 795c, the method 722 may involve authentication. For example, the authentication may include the exchange of cryptographic hash and/or challenge values, and may be one-way or two-way authentication, similar to operation 705c described with respect to FIG. 7A. Additionally, it should be noted in this case that authentication may be prevented or not otherwise performed in some cases. Display device 710, for example, may have already been authenticated to exchange data with analyte detection system 708 . As such, in some cases, data may be exchanged between analyte sensor system 708 and display device 710 under conditions of trust, and/or with encryption applied (eg, using an application key known to system 708). analyte sensor sensor and display device 710), in operation 795d without authentication being performed within communication session 780 .

In operation 795d, embodiments of method 722 include exchanging data between analyte sensor system 708 and display device 710 . For example, display device 710 may request data from analyte sensor system 708 and, in response, analyte sensor system 708 may send data. The requested/sent data may be analyte data (eg glucose values) and/or control signaling. The exchanged data can be encrypted in some cases, for example using an application key. The application key may have been shared between analyte sensor system 708 and display device 710 in conjunction with operation 795c and/or may have been received using other means (eg, from a cloud server).

With respect to the continuous connection model, operation 795d may be repeated periodically, as data becomes available for transmission (for example, in some cases aperiodically), and/or whenever data is requested to be exchanged (for example, example, on demand). The data exchange according to operation 795d may be interspersed with the exchange of other messages, such as, for example, connection check messages, exchanged between the analyte sensor system 708 and the display device 710. In FIG. 7J, this is shown by way of example using the intermediate steps between steps 795d and 795d'.

In embodiments, agreed connection parameters may be subsequently updated/modified in conjunction with connection establishment (eg, as part of operation 795b), eg, after a connection decision is made. Therefore, in operation 795f, method 722 may involve updating one or more of the connection parameters. Updating connection parameters may involve analyte detection system 708 and/or display device 710 proposing or requesting a change to an existing connection parameter. In another example, a value for a connection parameter that has not previously been set may be proposed/requested in conjunction with operation 795f. The proposal/request may result in various outcomes, including, for example, denial, acceptance, or counterproposal.

Additionally, operation 795f may involve a negotiation between analyte sensor system 708 and display device 710 regarding updating connection parameters. As described in connection with exchanging connection parameters in conjunction with operation 795b, connection parameters etc. may be proposed/requested. in the form of ranges and/or values. It will also be appreciated that various aspects of operation 795b may apply with respect to operation 795f. Various situations are possible in this regard. For example, one or both of the analyte sensor system 708 and display device 710 may propose and/or request a modification to/of one or more of the connection parameters. A counter proposal for a connection parameter value (or range) may be provided in response to the proposal/request. In some cases, if the proposal/request or counterproposal is denied, the connection may be maintained/continued based on previously established connection parameters. Acceptances and denials may be transmitted in the form of ACK/NACK messages, as shown in operation 795f, where, for example, an ACK represents an acceptance of the proposal/request and a NACK represents a denial and/or denial. counter proposal. In this regard, the NACK may contain or be accompanied by additional information such as the counterproposal. In some cases, the counterproposal may include a range of acceptable values for the connection parameter. Once the analyte sensor system 708 and display device 710 agree on a set of modified or unmodified connection parameters, the connection can be resumed, including steps 795d, 795e, and 795d'.

However, if analyte sensor system 708 and display 710 cannot agree on modified values or ranges for connection parameters and/or do not agree to maintain a connection based on previously established connection parameters, display system 708 analyte sensor and display device 710 may terminate the connection or may switch from the continuous connection model to another connection model such as, for example, the intermittent connection model. For example, display device 710 may receive a notification that analyte sensor system 708 is available for a new or changed connection based on certain connection parameter values to be used with the continuous connection model, but these Values may result in a shorter shelf life (for example, 6 days instead of 14 days). Therefore, the analyte sensor system 708 may suggest that the intermittent connection model can be used to extend the useful life. In some but not all cases with respect to the intermittent connection model, the values for connection parameters are not updated or modified throughout the lifetime of the analyte sensor system 708 . In other cases, however, the connection parameters may be updated/modified, eg, in a manner substantially similar to that described in connection with operation 795f. Furthermore, once the connection is established according to the new or modified connection parameters, the connection parameters may be maintained/modified later (eg, according to operation 795f, as described above).

With respect to updating connection parameters according to operation 795f, in some cases, an application running on display device 710 (eg, application 330) may not have access to the connection parameters in order to perform modifications to them. For example, access to these connection parameters may reside in the operating system of display device 710 rather than in the application. In such cases, however, the application may cause display 710 to request analyte sensor system 708 to request connection parameters pertaining to display 710 to be updated. In embodiments, this request may be made by display device 710 by sending a value for a connection parameter (eg, in a message or packet) to analyte sensor system 708 . The analyte sensor system 708 may then send a message to the display 710 to update and/or apply the value for the connection parameter(s), and the connection parameter(s) may updated accordingly (eg, via the operating system of display device 710). In this way, the application can be used to configure the connection parameters. In implementations, the analyte sensor system 708 makes a determination as to whether the proposed value for the connection parameter is acceptable, and sends the update message to the display 710 that responds to the determination that the proposed value is acceptable. . In this case, reference is made to Figure 15B described in detail elsewhere herein. Alternatively or additionally, the analyte sensor system 708 may reject the proposed value and indicate so, or it may provide a counterproposal for the value. Display 710 may accept the counterproposal value as standard, or may make a further determination as to whether the counterproposal value is acceptable (eg, based on various criteria discussed herein). In exemplary embodiments, GUI control may be provided to a user through display device 710 of GUI 340, thereby allowing the user to attempt manual configuration and/or update of connection parameters. As shown in Figure 3G, for example, access to connection parameters may be provided through option 314c.

As shown in operation 795g, in some cases, the connection between analyte sensor system 708 and display device 710 may be terminated or lost. There can be various causes for this. For example, and as mentioned above, it may be that analyte sensor system 708 and display device 710 cannot agree on a proposed or modified set of connection parameters (for example, in conjunction with operations 795b and/or 795f), or connection check messages are not responded to in such a way that, for example, slave latency is violated. For example, if display device 710 moves out of range of analyte sensor system 708, ACK messages in response to connection check messages cannot be received. In another example, display device 710 may be powered off, or the link to display device 710 may be temporarily or permanently degraded such that the exchange of messages according to operation 795e is infeasible.

In response to the loss of connection in operation 795g, the analyte sensor system 708 may send warning messages in accordance with operation 795a'. According to exemplary embodiments of the continuous connection model, after the analyte sensor system 708 and display device 710 are disconnected, the analyte sensor system 708 analyte may resume sending warning messages in some cases at least almost immediately. A faster paging pattern may be employed, for example, during a limited window in order to reacquire the connection to display 710. By way of illustration, with reference to FIG. 9, the alert message interval 915 can be reduced such that alert messages 920 are sent more frequently during the alert duration 910 .

Furthermore, the user may not be aware that there has been a disconnect according to operation 795g. This can lead in some cases to packet drop or data loss. Thus, in some cases, the analyte sensor system 708 may automatically resume alerting without user intervention. Alternatively or additionally, the prompt may be resumed based on an activation provided via NFC by the user. For example, the user may be notified via the GUI 340 that the connection has been lost. The notification may prompt the user to bring the display device 710 into relatively close proximity with the analyte sensor system 708, such that signaling with NFC can be exchanged. Other techniques may be used to manually trigger the resumed prompt. For example, the user may be prompted to touch the analyte sensor system 708 . In other examples, alternatively or in addition to NFC and accelerometer based triggers, the user may be prompted to bring display device 710 into relatively close proximity to the analyte sensor system such that RSSI based triggers can resume. warning messages. Once resumed, the warning can be made to occur for an indefinite amount of time and for relatively long windows of duration.

In some cases, when the alert is resumed, a very short alert period (or alert message interval 915, with reference to FIG. 9) may be employed for a first alert duration 910 and then a shorter alert period (or interval 915) may be employed. alert message) longer for a second alert duration (eg, in relation to alert duration structure 935', with reference to FIG. 9). If there is not yet an established connection to display 710, analyte sensor system 708 may then choose, for example, to switch to the intermittent connection model, as will be described in more detail below. Alternatively, the analyte sensor system 708 may end the alert and remain offline. In such a case, the analyte sensor system 708 may send a message to the display 710 causing the user to be prompted to provide a trigger for the analyte sensor system 708 to resume the prompt (for example, in the operation 795a'). As mentioned, such an activation can be provided in the form of NFC, for example. Upon receiving the trigger, the analyte sensor system 708 may resume the alert with a short alert message period to increase the chances of connection to the display device 710 . Such an alert scheme may also be employed when the analyte sensor system 708 is first activated, in order to connect to the display 710. Alternatively or additionally, the analyte sensor system 708 may advertise its connection to other known display devices 710 in the hope that they will form a more reliable connection.

According to embodiments of the continuous connection model, when the display device 710 is not connected to the analyte sensor system 708 (for example, when the connection has been terminated or otherwise), the display device 710 continuously scans for searching for the analyte sensor system 708 (eg, searching for warning messages sent by the analyte sensor system 708). In such cases, the analyte sensor system 708 may warn to the extent permitted under the circumstances. For example, the analyte sensor system 708 may employ a smaller warning message period, whereby warning messages are sent more frequently. In this manner, the analyte sensor system 708 can attempt to rapidly acquire or reacquire connection with the display device 710 previously connected to the analyte sensor system 708, or another display device 710 . The length or intensity of warning may be limited in some instances, however, based on battery constraints of the analyte sensor system 708 . Therefore, the analyte sensor system 708 may send alert messages according to periodic alert windows (for example, as may be used in connection with the intermittent connection model), as described herein with reference to figure 9.

In some cases, the continuous connection model can be considered to be state-based. That is, for example, if display 710 attempts to read an analyte value from analyte sensor system 708, display 710 will only receive the analyte data when a new or updated value is available. Some examples of the continuous connection model, however, may be only partially based on states. That is, in some cases, bidirectional communication may take place. For example, display device 710 may request analyte data or other information, such as sensor information, or may send data to analyte sensor system 708 . Based on the data requested/sent, the analyte sensor system 708 may provide new analyte data along with updated calibration data and updated sensor data, etc. In other examples, as mentioned above, the analyte sensor system 708 may send data when new data becomes available (eg, if battery power is low). That is, the analyte sensor system 708 can function in more than one way BASED on states.

With respect to the continuous connection model further, Figure 18 provides an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the present disclosure. For purposes of illustration, reference is made herein to Figure 7J, as well as reference numbers from components shown on it. However, one of ordinary skill in the art will appreciate, after studying this disclosure, that similar components from other figures in this disclosure may be included within the scope of this description of Figure 18.

Embodiments shown in FIG. 18 involve aspects of the method 1800 for wireless communication of analyte data, including, to operate according to a continuous connection model as described in instances herein. In this regard, method 1800 includes in operation 1805a that analyte sensor system 708 periodically exchange messages with display device 710 such that analyte sensor system 708 and display device 710 maintain a connection. In this case, reference is made by way of example to operation 795e shown in FIG. 7J.

In operation 1805B, method 1800 may involve receiving a connection request from display device 710. In this case, reference is made by way of example to operation 795b shown in FIG. 7J. Method 1800 optionally includes in operation 1805C for analyte sensor system 708 to send a proposal for a set of connection parameters to display device 710, in response to receiving the connection request. Here again by way of example reference is made to step 795b, and also to step 795f. In operation 1805D, method 1800 may include receiving a connection decision from display 710, based on the proposal. Here again by way of example reference is made to step 795b, and also to step 795f.

It should be understood that operations 1805B through 1805D may be performed prior to, after, and/or during the periodic message exchange of operation 1805A. For example, operations 1805B through 1805D may be executed in connection with establishing a connection that is maintained according to operation 1805A. Alternatively or additionally, operations 1805B through 1805D may be performed in connection with modifying a connection held in accordance with operation 1805A. In this regard, periodically exchanging messages in operation 1805A may be performed based on the set of connection parameters proposed in operation 1805C, in response to the connection decision received in operation 1805D including an acceptance of the proposal and/or a connection that is established. Operation 1805E involves establishing a connection between the analyte sensor system 708 and display device 710 based on the connection decision received in operation 1805D. Therefore, the 1805E operation can precede the 1805A operation in some cases. For example, referring to Fig. 7J, see steps 795b and 795e. In operation 1805F, method 1800 includes analyte sensor system 708 transmitting analyte data to the display while analyte sensor system 708 and display 710 maintain the connection. Reference is here made by way of example to operation 795d in FIG. 7J.

In operation 1805G, method 1800 may include requesting that one or more of the connection parameters be modified, in response to a violation of one or more of the connection parameters (eg, connection interval, slave latency, and timeout). supervision standby). In this case, reference is made by way of example to operation 795f. In operation 1805H, method 1800 may include terminating the connection, based on a violation of one or more of the connection parameters. In operation 1805J, method 1800 optionally includes providing a notification related to terminating the connection (eg, visual, audible, and/or haptic). In operation 1805K, method 1800 may include the analyte sensor system 708 transmitting warning messages, in response to terminating the connection in operation 1805H. In this case, reference is made to operation 795a' in Fig. 7J.

With respect to the continuous connection model further, Figure 19 provides an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the present disclosure. For purposes of illustration, reference is made herein to Figure 7J and Figures 10A to 10E, as well as component reference numbers shown therein. However, one of ordinary skill in the art will appreciate, after studying the present disclosure, that similar components from other figures in this disclosure may be included within the scope of the present description of figure 19.

Embodiments shown in FIG. 19 involve aspects of the method 1900 for wireless communication of analyte data, including, to operate according to an identification and/or selection of a device for connection according to the continuous connection model as described in instances in This document. In this regard, method 1900 includes in operation 1905A obtaining a derivative of a first signal received over a first link (eg, link 1032a). In operation 1905B, the method 1900 includes generating an ID for selection based on the derivative of the first signal. Operation 1905C involves taking a derivative of a second signal received over a second link (eg, 1032a'). Operation 1905D involves generating a selection for your connection, based on the derivative of the second signal.

In operation 1905E, method 1900 optionally includes receiving a connection request from display device 710. In this case, reference is made by way of example to operation 795b in FIG. 7J. Method 1900 may include in operation 1905F that analyte sensor system 710 send a proposal for a set of connection parameters to display device 710, in response to receiving the connection request. In this case, reference is made by way of example to steps 795b and 795f in Fig. 7J. In the operation 1905G, the method 1900 may include receiving a connection decision from the display device 710, based on the proposal. Reference is here made by way of example to steps 795b and 795f/795g in Fig. 7J.

In operation 1905H, method 1900 includes establishing a connection between display device 710 and analyte sensor system 708, based on the connection selection and/or connection decision. For example, the connection may be established in response to the connection decision that includes an acceptance of the proposal for the set of connection parameters sent in operation 1905F. Reference is here made by way of example to steps 795b and 795f in Fig. 7J. The 1905J operation involves periodically exchanging messages to maintain the connection, for example based on the set of connection parameters. Reference is here made by way of example to operation 795e in FIG. 7J. In operation 1905K, method 1900 includes analyte sensor system 710 transmitting analyte data to display device 710 while analyte sensor system 708 and display device 710 maintain the connection.

With respect to the continuous connection model further, Figure 20 provides an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the present disclosure. For purposes of illustration, reference is made herein to Figures 7C and 7J, as well as component reference numbers shown therein. However, one of ordinary skill in the art will appreciate, after studying this disclosure, that similar components from other figures in this disclosure may be included within the scope of this description of Figure 20.

Embodiments shown in FIG. 20 involve aspects of the method 2000 for wireless communication of analyte data, including, for implementing an enhanced authentication scheme in conjunction with operation under a continuous connection model as described in instances herein, for example, in order to reduce the number of messages exchanged before analyte data can be securely transmitted (eg, encrypted between authenticated devices).

In this regard, in operation 2005A, method 2000 includes authenticating display device 710 for a first connection (eg, with analyte sensor system 708) by exchanging authentication-related information between analyte sensor system 710 and display device 708. In this case, reference is made by way of example to operation 795c in FIG. 7J. In operation 2005B, method 2000 optionally includes establishing the first connection between display device 710 and analyte sensor system 708 . In this case, reference is made by way of example to operation 795b in FIG. 7J. In operation 2005C, method 2000 includes analyte sensor system 708 periodically exchanging messages with display device 710 to maintain the first connection. Periodically exchanging the messages in operation 2005C is in this case based on the authentication in operation 2005A. In this case, reference is made by way of example to operation 795e in FIG. 7J. In operation 2005D, method 2000 includes analyte sensor system 708 transmitting encrypted analyte data to display device 710 during the time the first connection is maintained. Reference is made in this case for example to operations 795d and 795d' in Fig. 7J.

Embodiments of method 2000 include in operation 2005E terminating the first connection. For purposes of illustration, reference is made to operation 795g in Figure 7J. In operation 2005F, method 2000 optionally includes establishing a second connection between analyte sensor system 708 and display device 710 . Operation 2005G involves analyte sensor system 708 periodically exchanging messages with display device 710 to maintain the second connection. In operation 2005H, method 2000 may include analyte sensor system 708 transmitting encrypted analyte data to display device 710 during the time the second connection is maintained. For the second connection, exchanging messages periodically in operation 2005G and transmitting encrypted analyte data in operation 2005H are based on the authentication of display device 710 for the first connection in operation 2005A. Thus, in connection with these aspects of method 2000, authentication may not be repeated when earlier authentication may be used to reduce the number of messages exchanged prior to transmission of analyte data.

L. Switching between connection models

As mentioned above, there are various embodiments in which the intermittent connection model and/or the continuous connection model can be implemented. Also, in some embodiments, various parameters such as battery power of the analyte sensor system and/or display device, reliability and availability of wireless connections, etc. may be taken into account. during the implementation of one or more of the connection models.

Accordingly, embodiments of the present disclosure involve switching between these connection models in order to provide a flexible and adaptable system that can be optimized for a variety of use cases, operating conditions, and user/system preferences. Switching adaptively (either automated or based on user input, both of which are contemplated herein) can enable optimization of battery power usage as well as transmission efficiency and data accuracy. In addition, the behavior and performance of the device, according to exemplary embodiments, can be tracked over time and used to develop an optimization profile regarding circumstances in which various connection models may be preferred.

As mentioned above, in some cases, the connection model can be automatically switched based on various criteria. For example, the connection pattern can be adjusted depending on the type of display device that is connected to the analyte sensor system (eg, smartphone vs. medical device). In another example, the connection model can be adjusted based on the number of display devices being used, for example, if a single dedicated device is being used (for example, for a predetermined amount of time), then the system can switch to the continuous connection model. In another example, the connection pattern may be switched based on current or projected battery life. Signal quality can also be used to determine if a switch between connection models is appropriate. In addition, a switch in connection patterns may be based on the time of day and/or the location of the analyte sensor system 708 and/or display device 710. Switching could be initiated by display device 710 and/or analyte sensor system 708 .

In embodiments, the switching may be based on user input or may be semi-automatic. For example, a user may navigate to a GUI, such as GUI 340, to implement the switch. In particular, referring to FIG. 3G, the user may select connection status option 314f ("connection status") to vary the connection model employed. In some cases, different buttons 316f may be presented through the GUI 340, where each button (or softkey) corresponds to a different connection model. In other cases, as shown in Figure 3G, a single button may be used to select between connection models. In some such cases, a drop down menu may be provided so that the user can select between different connection models. In other cases, a number or letter or other character may be used to indicate the desired pattern of connection. In another example, the switch may be automatically triggered, in turn triggering a prompt to be presented to the user on the display device 710 via the GUI 340. The user may then approve or deny the switch (thus, the switch may be made semi-automatic). The notice may provide the user with information regarding the connection model currently employed, the reason for the proposed switch, and, in some cases, the consequences of rejecting and/or accepting the proposed switch, including commitments related thereto.

Figure 7K illustrates by way of example, embodiments involving the use of various connection models, as well as features related thereto. Specifically, method 724 includes the use of various connection models that are used in an example sequence. As shown, at Tinterval, communication session 720 may occur. Communication session 720 implies that the intermittent connection model is employed, and with reference to Figure 7A, may involve features such as prompting in operation 705a, authentication in operation 705c, and data transmission in operation 705d. Figure 7K also illustrates, in the Tinterval' operation, that communication session 725 occurs, which involves the intermittent connection model. Referring to Figure 7C, communication session 725 may involve features such as announcement in operation 735a, and data transmission in operation 735d. Particularly, embodiments of communication 725 may not include authentication, for example when authentication was previously performed in conjunction with communication 720, or in other situations where authentication may be skipped or avoided, as described herein. Referring again to Fig. 7K, it is shown that communication 725' to "Tinterval" occurs, in which the intermittent connection model can again be employed. Tinterval' may be the same as or different from Tinterval, in various embodiments described herein. Likewise, Tinterval” may be the same as or different from Tinterval and Tinterval' in various embodiments described herein.

Following communication 725' in FIG. 7K, communication 780 is shown to occur. Referring to FIG. 7J, communication 780 implies that the continuous connection model is employed. It should be noted in this case that less than all of the operations or aspects of the communication session 780 as shown in FIG. 7J may occur in connection with certain instances of the communication session 780. For example, referring to Fig. 7K, authentication may already have been previously performed in conjunction with the communication session 720 . As a result, no authentication may occur in operation 795c of communication 780. Also, in some cases, connection parameters may have been previously established in conjunction with one or more of the communication sessions 720, 725, 725', etc. Or, for example, connection parameters may have been established in conjunction with a previous instance of communication session 780 or another communication session employing the continuous connection model or otherwise involving connection parameters. In such cases, the connection parameters established in making a connection decision in operation 795b may be used, such that the exchange of connection parameters described with respect to operation 795b need not occur. This may allow faster connection establishment with reduced signalling.

With further reference to Fig. 7K, after the communication session 780 has been active for an indefinite amount of time, disconnection may occur, a new communication session may be initiated, and/or the connection model employed may be changed. For example, as shown in the operation 795g (referring to Fig. 7J), the connection may be lost for various reasons, such as user preference/input, network or power conditions, and so on. In the illustrated example of FIG. 7K, the analyte sensor system 708 and the display device 710 are disconnected for some time, after the communication session 725" is initiated during Tinterval'" and the connection model is used. intermittent. However, it will be appreciated that disconnection need not occur in order to switch between connection patterns. Rather, in embodiments, the communication session 780 involves the exchange of messages while in the connected state, where the messages signal that a transition from the continuous connection model to, for example, the intermittent connection model should occur. . Such signaling can occur at almost any point during communication session 780, an example being along with operation 795f. Similarly, similar signaling may be exchanged in conjunction with a communication session involving the intermittent connection model in order to initiate a transition to the continuous connection model.

In embodiments, one of the continuous connection model is employed, in which analyte data may be exchanged after or shortly after the data is available for transmission, or the intermittent connection model, in response to an indication such as, for example, eg, an indication of a usage preference related to display device 710 . The indication may be communicated to/from the analyte sensor system 708 at various points. In example cases, the indication may be communicated before the connection is established. For example, advisory messages transmitted from the analyte sensor system 708 (eg, at steps 705a, 735a, and/or 795a) may contain signaling indicating that it is preferred that the continuous connection model should be used, or is required, or that there is no preference for a particular connection model. By way of illustration, this can be done by using a flag in an advertisement packet (eg, packet 800 with reference to FIG. 8) or by otherwise modifying the information carried in the advertisement packets. In response, the request for the data connection (eg, at operation 705b, 735b, and/or 795b) may then indicate whether the connection model indication is correct.

Alternatively or additionally, the indication may be exchanged in response to prompt messages that are received at display 710, eg, in conjunction with a connection request/grant (eg, at steps 705b, 735b, and/or 795b). or other message related to connection establishment. In such examples, subsequent messages such as the grant of a data connection (for example, in operation 705c, 735c and/or 795c), authentication messages (the request for data connection (for example, in operation 705b and/or or 795b), etc. can then indicate whether the indication regarding the connection model is correct.

As another example, the indication may be exchanged in conjunction with a data request or transmission (eg, at steps 705d, 735d, and/or 795d). With respect to the communication session 780, the indication may be exchanged along with messages used to maintain the connection (eg, in operation 795e) and/or along with messages used to update connection parameters (eg, in operation 795f). ). In some embodiments, indication may be exchanged at other points during or outside of a connection between analyte sensor system 708 and display device 710 . For example, the indication may be sent in real time or at least near real time, or at other predetermined times not mentioned heretofore.

With respect to generating the indication, in an exemplary situation, the user of display device 710 may indicate that the continuous connection model is preferred over the connection/disconnection model, or vice versa. For example, if the user prefers a first display device 710 (eg, a smartphone) such that, for example, it is the only display device 710, the user will be using it to capture analyte data, then the analyte sensor system 708 may operate in the continuous connection mode according to the communication session 780 after connecting to the preferred display device 710 . The user preference may be manually indicated by the user (for example, through the GUI 340 and the "Dedicated," "Priority," or Preferences options), or may be derived from data related to the use of the first display device 710 as well. such as other display devices, for example, as described in detail herein. Deriving the user's preference may be performed based on data relating to the user's data on analyte values/trends, time of day, location, radio link conditions (including, for example, RSSI), packet loss rates, and network parameters, eg.

In some embodiments, a prioritization scheme may be configured with respect to multiple displays 710. In order to implement the priority scheme for a particular display device 710, the communication session 780 for that particular display device 710 may be used. In some cases, for example, if packet loss increases above a threshold, the keep-alive model can be used in order to decrease packet loss. In some cases, the continuous connection model or the intermittent connection model may serve as the default connection model, and the corresponding communication session may be used by default (eg, 720, 725, 740, 780). The default model may be selectable, eg, based on user input or adaptively based on various of the parameters/criteria described above.

To illustrate, the analyte sensor system 708 and a first display device 710 may be communicating analyte data using the intermittent connection model as described above (eg, with respect to FIGS. 7A, 7B, and 7E). In this situation, the first display device 710 can be, for example, a user's smartphone. The analyte sensor system 708 may also be, depending on the on/off model, communicating analyte data with a second display device 710, which may be, for example, a medical device (for example, an insulin pump, medical device 136, or the like) or a registered display device (e.g., a device designed specifically for communication of analyte data, such as display device 110, with reference to Figure 1A; examples of which also are sometimes referred to herein as analyte display device). The user may then provide, for example through the GUI 340, an indication that the user will only be using the smartphone and not the medical device. As mentioned, this may be done through the GUI 340 provided on the smartphone in connection with an application, such as application 330, which may be related to communication of analyte data. For example, referring to Figure 3G, the user may select one of options 316e to indicate that a display device 710 should be dedicated or non-dedicated, or another option (not specifically shown/listed) that devices are preferred. or not (for example, “Priority” and/or “Preferences”).

The smartphone (or other type of display device 710) in this example may then transmit the user's prompt to the analyte sensor system 708, which upon receipt of the prompt may initiate operation with the always-on model according to session 780 of communication, since the user selected that the device be dedicated. Referring to FIG. 7J, the user prompt may be transmitted from display device 710 to analyte sensor system 708 at step 795b, in the form of a request message. Although other display devices 710 (including, for example, a medical device such as medical device 136) may listen to (i.e., receive messages from) analyte sensor system 708 in this situation, only display device 710 preferred display, in this example the smartphone, is operating in the connected model and thus potentially exchanging analyte data relatively more frequently.

In embodiments, the continuous connection model is employed, eg, based on communication session 780, adaptively. For example, depending on the time of day, there may be an advantage to operating on the continuous connection model based on the communication session 780 (as opposed to, for example, employing the intermittent connection model or using another form of communication session described herein) for some users and/or the display devices 710. Individual users may experience more intense glucose level variations during certain times of the day. Such variations, for example, may be faster and/or larger in magnitude at certain times. In some instances, such variations may not be ideally addressed by the analyte sensor system 708 operating on the intermittent connection model depending on communication sessions 720, 725, and/or 740, for example, since values of analyte in some cases relatively less frequently. Thus, during hours when glucose level variations are typically strong, the analyte sensor system 708 and/or display device 710 may initiate operation in the connected model according to the communication session 780 . Accordingly, the used connection model can be adaptively changed/alternated/switched.

In another example, network parameters, network conditions, radio link quality (eg, RSSI etc.), number of display devices 710 seeking a connection to or in communication with motion sensor system 708 analyte, and/or a prioritization scheme (eg, as determined by a user or otherwise), may serve as the basis for operating with the continuous connection model (eg, per communication session 780) or the intermittent connection model adaptively. With respect to network parameters or conditions, and/or with respect to the quality of the radio link, a degradation may result in packet loss. Such packet loss, as mentioned above, may be more critical for analyte data exchange with the intermittent connection model, since data is in some cases not exchanged as frequently relative to the continuous connection model. . Accordingly, in order to mitigate degradation of network parameters or conditions, and/or radio link quality, when such degradation is detected, analyte sensor system 708 and display device 710 may initiate operation. with the continuous connection model according to the communication session 780. As mentioned above, analyte sensor system 708 and/or display device 710 may monitor network parameters, network conditions, and/or radio link quality. These measurements can then be compared to thresholds such that switching of the connection model employed (eg, between various communication sessions) can be done adaptively in response to the threshold being crossed.

With respect to the number of devices seeking a connection to, and/or being in communication with, the analyte sensor system 708, the adaptation of the operating mode/connection model can be described as follows. A large number of display devices 710 may be in range of the analyte sensor system 708, and attempting to connect to them may result in interference and thus packet loss and/or increased power consumption. To avoid such packet loss and increased power consumption, even in the face of numerous displays 710 seeking a connection, the analyte sensor system 708 may initiate operation in the continuous connection model with a preferred display 710 .

This can be done by the analyte sensor system 708 which keeps a count of the number of devices of the display device 710 seeking a connection thereto, and signaling that a preferred display device 710 goes into operation with the continuous connection model if the count exceeds a threshold. Such signaling may be implemented in conjunction with various communication session operations described herein, for example. Alternatively or additionally, packet loss may be monitored (eg, in display device 710 and/or analyte sensor system 708). Furthermore, the source of such packet loss may be determined, or estimated/approximated, for example, in the display device 710 and/or the analyte sensor system 708 . If the source of the packet loss is determined to be interference (due, for example, to numerous displays 710 attempting to connect to the analyte sensor system 708), operation with the continuous connection model may be initiated.

In this case, the preferred display device 710 can also be determined instantly or nearly so, can be determined on the fly, and can be determined without user intervention. For example, the preferred display device 710 may be determined based on frequency of use, a predetermined prioritization scheme, radio link or connection quality (e.g., based on signal strength, channel loss, rate of transmission). bit errors, RTT, RSSI, etc.), available battery life and/or processing power, time of day, etc. Alternatively or additionally, the user may be queried through the GUI 740, eg, as part of the application 330 running on the display device 710, regarding the preferred display device 710 .

With respect to terminating the connection established and maintained according to the communication session 780, various techniques may be employed. As mentioned above, operation 795e may involve exchanging messages based on a connection interval. Such messages can be thought of as "connection check" messages.

Sequential exchange of such messages may involve a first message and a second message being transmitted successively with respect to the first message, and so on with respect to the third, fourth and fifth messages, etc. The first such message may be configured to include a connection interval indicating when the next message in the sequence will be exchanged between analyte sensor system 708 and display device 710, or in other words may include an amount of time. scheduled between the sequential exchange of the first and second connection check messages.

This connection interval can be varied between the messages exchanged in operation 795e. If the display device 710 does not receive the second message within the expected connection interval, the connection between the display device 710 and the analyte sensor system 708 may be terminated at step 795g. In another instance, the connection may be terminated if a NACK is received over the proposed connection interval or is otherwise rejected, eg, at step 795b or step 795f. That is, if the analyte sensor system 708 and display device 710 do not agree on a connection interval, the connection may be closed/terminated. An ACK/NACK may also be sent after each connection check message (for example, multiplexed ACK/NACK) or after a predetermined or adaptively varied number of such messages (for example, grouped ACK/NACK), for example, in the 795e operation.

In embodiments, one or more messages exchanged in operation 795e may include a timeout value. As mentioned above, monitoring timeout and related techniques may also be employed with respect to the continuous connection model. For example, after the timeout value has expired, if a second check connection message has not been received, method 722 may involve terminating the connection in operation 795g. When the connection is terminated, the communication session 780 may end. At this point, the transceiver 360 and/or the processor 380 of the analyte sensor system 708 may be disabled in some cases. Alternatively, as mentioned above, the analyte detection system 708 may initiate a warning at step 795a'. In some cases, the decision to disable or warn may be based on an obvious reason that the connection was terminated. For example, if the connection is terminated simultaneously with interference events, degraded radio conditions, or loss of battery power, the analyte sensor system 708 may initiate an alert by operation 795a' in order to reacquire the device 710 from preconnected display or other display device 710 .

Generally, an instance of a communication session 780, in which the analyte sensor system 708 and display device 710 continuously connect, may ultimately continue until the connection is closed or terminated or lost for various reasons. the potential reasons described above. A request to modify the connection model (eg, send according to operation 795f) may result in terminating the connection established as part of communication session 780, and activating a different connection model, for example, by initiating communication. 725” communication session. In some cases, the connection model employed may be manually controlled through the GUI 340. Referring to Figure 3G, a user may be presented with a submenu 314f that allows selection of a connection model using options 316f, starting with both a switch in the connection model used. Method 722 thus provides a highly flexible and adaptable technique for reporting analyte data.

With respect to the connection models described herein, in embodiments of the present disclosure, different connection models may be used for different connected devices (for example, the display devices 710). Referring to Fig. 3C, for example, communication session 780 may be employed as between display devices 310a and 310b, while a different communication session (eg, 720, 725, 740, etc.) may be employed at the same time. .) as between display devices 310a and/or 310b, on the one hand, and analyte sensor system 708 on the other hand. In embodiments, one of display devices 310a and 310b may not be connected to analyte sensor system 708 but may nonetheless receive analyte data therefrom through another display device 310b or 310a that is connected to system 708. of analyte sensor. In some cases, this may be referred to as anchoring. Such settings can be implemented, for example, using submenu 314a presented by GUI 340, with reference to Figures 3F and 3G.

Turning now to Figures 3C-3E, embodiments of the present disclosure involve configuring and/or establishing a mesh network class using various connection models described herein. For example, two or more displays 310a and 310b may be connected to the analyte sensor system 308 using different connection patterns. Referring to Figure 3C and illustrated system 304, analyte sensor system 308 may be connectable to display devices 310a and 310b via communication means 305a. Furthermore, the display devices 310a and 310b may be connectable to each other through the communication means 305b. It will be appreciated that although two displays 310a and 310b are shown in Figures 3C-3E, more than two displays may be included in the mesh networks described herein and/or using various connection models.

Figure 3D shows that relative to system 306a, analyte sensor system 308 may be connectable to display devices 310a and 310b, respectively, using various communication means (eg, communication medium 305) and/or or connection models (eg, intermittent connection model, continuous connection model, etc.), represented for illustration as connections A and B. Additionally, displays 310a and 310b may be connectable to each other using various communication means and/or connection patterns, illustratively represented here as connection C. For example, when two display devices 310a and 310b are in range of the analyte sensor system 308, the sensor system 308 of analyte and display device 310a can be connected using the continuous connection model. Display device 310b may then be connected to analyte sensor system 308 using the intermittent connection model. In this manner, with display device 310b connected to display device 310a, display device 310a can essentially act as a gateway device for display device 310b. In some other embodiments, the analyte sensor system 308 can be simultaneously connected to both the display device 310a and the display device 310b through the continuous connection model. (for example, both connection A and connection B can use the continuous connection model). It is contemplated that multiple display devices can be simultaneously connected to the analyte sensor system using the continuous connection model.

It will be appreciated in this case that the respective connection patterns used by display devices 510a and 510b can be switched. It will also be appreciated that both display devices 310a and 310b can be connected to the analyte sensor system using the intermittent connection model. Regardless of the connection models employed between the analyte sensor system 306a on the one hand and the display devices 310a, 310b on the other hand, the display devices 310a, 310b can be connected to each other using either the connection model intermittent or continuous connection model. In addition, any of the communication means and/or connection models used (eg, in connections A, B, and C) may be switched to a different connection model subsequent to connection establishment.

Turning now to Figure 3E, another example of configuring and/or establishing a mesh network using various of the connection models described herein is illustrated. As shown in connection with system 306b, analyte sensor system 308 may be connectable to a number of displays 310a, 310b, 310c, employing various connection patterns and/or communication means 305 for each of these. the respective connections. It will be appreciated that any of the connection models described herein may be used for connections D, E and/or F etc. Also, any of the connection models used (eg, connections D, E, and F) can be switched to a different connection model after connection establishment. It will also be appreciated that in exemplary implementations of system 306b, one or more displays may be connected to analyte sensor system 308 in parallel to displays 310a, 310b, and 310c. Each display device may also have a chain of displays connected to it, as shown with respect to displays 310a, 310b, and 310c.

In embodiments relating to the configurations shown in Figures 3C to 3E, a user interface such as GUI 340, with reference to Figures 3F and 3G, may present user information regarding the mesh network, such that the user can maintain a certain level of control and/or input in its configuration. For example, the topography of the mesh network could be provided, and the user could be enabled to access connection links to alter the connection model used or the connection parameters used, warning characteristics, etc. associated with the various connections. Also, the user can switch between display devices 310a, 310b, etc. in that the device can act as a gateway for other devices.

Referring now to Figures 15A and 15B, some embodiments of the present disclosure related to the connection parameters described above will now be described. In this regard, Figures 15A and 15B provide operational flow charts illustrating various operations that can be performed in accordance with embodiments of the present disclosure, for example in relation to setting and/or modifying connection parameters in accordance with various connection models described in the this document. For purposes of illustration, reference is made herein to Figures 7J, as well as component reference numbers shown therein. However, one of ordinary skill in the art will appreciate, after studying the present disclosure, that similar components from other figures in this disclosure may be included within the scope of the present description of Figure 15A and 15B. It will also be noted at this juncture that while the setting, negotiation and/or modification of connection parameters may be related in some cases to switching between connection models, in other cases the setting, negotiation and/or modification of parameters Connection patterns may be related to operating according to a single connection pattern for a given amount of time. However, discussion of these features is included in this part of the disclosure for the convenience of the reader.

Embodiments shown in FIG. 15A involve aspects of the method 1500 for wireless communication of analyte data including, for example, the exchange, negotiation, and adjustment of connection parameters and related features. In this regard, the method 1500 may include in operation 1505A requesting a connection according to a first connection model. For example, display device 710 may request a connection to analyte sensor system 708 in conjunction with operation 795b shown in FIG. 7J. The first connection model can be an intermittent connection model or a continuous connection model. In operation 1505B, method 1500 includes receiving a proposal for a connection parameter. The proposal includes one or more proposed values for the connection parameter. Proposals for multiple connection parameters may be sent simultaneously or nearly so in some cases. The proposal may be received at the analyte sensor system 708 and/or the display device 710. In operation 1505C, method 1500 includes determining whether the proposal is acceptable. Operation 1505D involves generating a response to the proposal, based on determining whether the proposal is acceptable.

In operation 1505E, method 1500 optionally includes sending a counterproposal, if the response generated in operation 1505E indicates a preference for a value for the connection parameter other than the proposed values for the connection parameter. The counterproposal may include one or more counterproposal values for the connection parameter. Embodiments of method 1500 also include receiving a response to the counterproposal in operation 1505F. Based on the response received to the Securities Proposal and/or the Counter Securities Proposal, various actions may be taken.

In operation 1505G, method 1500 may include establishing a connection between display device 710 and analyte detection system 708 based on one or more of: an acceptable default value of the one or more default values, if the response indicates an acceptance of the acceptable proposed value; at least one of the counterproposal values, if the response to the counterproposal indicates an acceptable one of one or more of the counterproposal values. In operation 1505H, the method 1500 may include generating a negative connection decision, if the response to the counterproposal indicates a rejection of the counterproposal values. In some cases, a negative connection decision may also be generated in operation 1505H based on a rejection of at least one of the proposed values. In operation 1505J, the method 1500 optionally includes modifying a connection between display device 710 and analyte sensor system 708 based on one or more of: an acceptable proposed value of the one or more proposed values, if the response indicates an acceptance of the acceptable proposed values; and at least one of the counterproposal values, if the response to the counterproposal indicates an acceptance of one or more of the counterproposal values.

In operation 1505K, method 1500 may include terminating a connection between display 710 and analyte sensor system 708, for example: if the response to the counterproposal indicates a rejection of the counterproposal values; if the response to the proposal indicates a rejection of at least one of the proposed values; and in response to determining that the proposal is not acceptable. In operation 1505L, embodiments of method 1500 include providing a notification related to terminating the connection (eg, in operation 1505K). In embodiments, the method 1500 includes requesting a connection according to a second connection model (eg, that is different from the first connection model), in response to determining that the proposal and/or counterproposal is not acceptable.

Figure 15B illustrates embodiments of the present disclosure related to aspects of method 1502 for wireless communication of analyte data, including, for example, the exchange, negotiation, and adjustment of connection parameters and related features. In this regard, method 1502 may include in operation 1510A, in response to input from an application running on display device 710 (eg, application 330 with exemplary reference to FIG. 3B) , display device 710 sending analyte sensor system 708 a message that includes a value for a connection parameter. In operation 1510B, method 1502 includes display device 710 receiving from analyte sensor system 708 the value for the connection parameter.

In operation 1510C, method 1502 may include obtaining an indication of whether the value is acceptable. This achievement can be accomplished, for example, by display 710 receiving from analyte sensor system 708 a determination of whether the value is acceptable. In operation 1510D, method 1502 includes a display device 710 operating system (eg, as may be stored in storage 325 and executed/controlled at least partially by processor 335, with reference to exemplary FIG. 3B) applying the value for the connection parameter, based on a determination that the value is acceptable. For example, the value may apply to an established or to be established connection between analyte sensor system 708 and display device 710 .

With regard to additionally switching between connection models, Figures 16A-16C provide operational flow charts illustrating various operations that may be performed in accordance with embodiments of the present disclosure. For purposes of illustration, reference is made herein to Figures 7A through Figure 7K, as well as component reference numbers shown therein. However, one of ordinary skill in the art will appreciate, after studying the present disclosure, that similar components from other figures in this disclosure may be included within the scope of the present description of figures 16A to 16C.

Embodiments shown in Figure 16A involve aspects of method 1600 for wireless communication of analyte data, including, for example, switching between operating according to different connection models described herein. In this regard, method 1600 includes operation 1605A in operating in a first mode. Additionally, in operation 1605B, method 1600 includes operating in a second mode. Figures 16B and 16C illustrate additional details regarding operations 1605A and 1605B. Figure 16B illustrates embodiments involving aspects of method 1602, including additional details regarding operation 1605A, mentioned above with reference to Figure 16A. As shown, operation 1605A includes in operation 1610a that the analyte sensor system 708 periodically exchange messages with the display 710 such that the analyte sensor system 708 and display 710 remain connected. In this case, reference is made by way of example to operation 795e shown in FIG. 7J. Operation 1610B involves, while analyte sensor system 708 and display 710 remain connected, analyte sensor system 708 transmits analyte data to display 710.

Figure 16C illustrates embodiments involving aspects of method 1604, including additional details regarding operation 1605B, mentioned above with reference to Figure 16A. As shown, operation 1605B includes operation 1615A to periodically establish a connection between analyte sensor system 708 and display device 710 . In this case, reference is made by way of example to Figures 7A and 7B (eg, communication sessions 720 and 720' and operation 705b). Operation 1615B involves, while the connection is established, transmitting analyte data to display device 710.

Referring again to FIG. 16A, in operation 1605C, method 1600 may include receiving an indication related to one or more switching criteria (for example, such criteria may be related to battery conditions and/or management as described below). described in this document). In operation 1605D, method 1600 optionally includes switching from operating in the first mode to operating in the second mode or switching from operating in the second mode to operating in the first mode. Switching in operation 1605C may be based on user input and/or one or more switching criteria. In operation 1605E, method 1600 may include presenting a notification to the user related to the switch.

M. Reading data using a feature-based profile

By way of background, some profiles described herein may be control-based, linear, and employ multiple features that may be configured in a sequence. In some cases, after going through various features in sequence (eg, read sync time, authentication, etc.), display device 710 may request EGV values from analyte sensor system 708 . That is, some example profiles request and/or require a particular sequence of commands and operations to be followed and executed before swapping e Gv .

According to embodiments of the present disclosure, profiles based on characteristics are provided. That is, to read or receive EGV data by the display device 710 while operating according to the continuous connection model or the intermittent connection model (eg, as described above), a feature-based profile may be implemented. This may allow display 710 to read CGM data directly, as opposed to first performing various communications-related features or operations before reading CGM data. Direct reading of CGM data can be at least partially facilitated by the authentication scheme described above because no additional authentication is required after an initial authentication. Therefore, in some cases, the disclosed profiles may include an increased number of features without the need to exchange an increased number of messages prior to data exchange. One such feature may be used for or in some cases dedicated to encrypted EGVs. As such, display device 710 can jump directly to the EGV feature and read encrypted EGVs, instead of going through all other features first (as may be required by existing control-based profiles). This can result in power savings as well as increases in reliability and responsiveness.

A typical EGV data readout sequence according to embodiments of the feature-based profiles disclosed herein may be as follows. When different measures can be taken depending on the connection model used (for example, the continuous connection model or the intermittent connection model), they are indicated in the following description. First, the analyte sensor system 708 and display device 710 can establish a connection. The analyte sensor system 708 may then indicate to the display 708 which and how many features are included in the applicable profile (eg, the analyte sensor system 708 may indicate that it has three or four features). For the intermittent connection model, the analyte sensor system 708 may then turn off and/or go to sleep for a period of time before reactivating. Alternatively or additionally, for the continuous connection model, the connection is maintained after the analyte sensor system 708 indicates the number of features to the display 710 . The display device 710 may then request at any time during the connection, for example, to read a specific feature from the analyte sensor system 708 regardless of whether the features may be arranged in a sequence. For example, the request can be made according to feature numbers. Thus, for example, display device 710 may request to read feature numbers one and three, which may be encrypted and time-synchronized EGVs, for example.

That is, in the profiling implementation described above, EGVs (encrypted) can be read directly without stepping through other features (eg, feature number two in this example) that may be unnecessary (at least at the moment). Accordingly, the number of messages/communications exchanged between analyte sensor system 710 and display device 708 prior to EGV reading (encryptions) can be reduced.

Figures 12A and 12B show by way of example, embodiments involving the use of feature profiles, as well as features related thereto. Specifically, the method 1200 includes the communication session 1202 and the use of the feature profile 1205 that is used in an example sequence, namely features 1205a, 1205b, 1205c, and so on. Feature profile 1205 may include features 1205a, 1205b, etc., which may involve, for example, advertising in conjunction with features 1205a and/or 1205e, establishing a connection in conjunction with feature 1205b, authentication in conjunction with feature 705c , and data transmission along with the 1205d feature. It will be appreciated that these features are provided by way of illustration only, and that fewer or additional features may be included in the feature profile 1205 .

As mentioned above, the analyte sensor system 708 and display device 710 can establish a connection. the analyte sensor system 708 can then indicate to the display 708 which and how many features are included in the feature profile 1205 . As depicted in FIG. 12B, display device 710 may request to read a feature 1205d (eg, read an encrypted estimated glucose value) from analyte sensor system 708 without performing each of the features in the sequence shown. in Figure 12A, for example, according to feature profile 1205. It will be appreciated at this juncture that communication sessions 1202 and/or 1204 may employ an intermittent connection model, a continuous connection model, or both.

With respect to feature-based profiles additionally, Figure 17 provides an operational flow chart illustrating various operations that may be performed in accordance with embodiments of the present disclosure. For purposes of illustration, reference is made herein to Figures 12A and 12B, as well as component reference numbers shown therein. However, one of ordinary skill in the art will appreciate, after studying the present disclosure, that similar components from other figures in this disclosure may be included within the scope of the present description of figure 17.

Embodiments shown in FIG. 17 involve aspects of the method 1700 for wireless communication of analyte data, including, for employing feature profiling aspects. In this regard, method 1700 includes step 1705A establishing a connection between analyte sensor system 708 and display device 710 . In operation 1705B, method 1700 includes receiving a set of features associated with analyte sensor system 708 . The features may be arranged in a sequence. In embodiments, method 1700 includes operation 1705C, which involves sending analyte sensor system 708 a request to read one or more of the features in a different order of sequence. In operation 1705D, method 1700 optionally includes performing a feature of the feature set without having performed one or more other features that precede the performed feature in sequence.

N. Additional embodiments

One skilled in the art will appreciate, after studying the present disclosure, that various additional embodiments do not explicitly described herein are within the scope of this disclosure.

Figure 11 illustrates an example compute module 1100, which may in some instances include a processor/microprocessor/controller resident in a computer system (eg, in connection with server system 334, any of the display devices described in herein (for example, display devices 120, 130, 140, 310(a,b), 710(a,b), as well as analyte display device 110 and medical device 136), and/or analyte sensor system 8, 308, 708, etc. Compute module 1100 may be used to implement various features and/or functionality of embodiments of the systems, devices, apparatus, and methods disclosed herein. previously described embodiments set forth herein in the context of the systems, devices, apparatus, and methods described with reference to the various figures of this disclosure, including the rea izations of analyte sensor system 708, analyte display device 110, display devices 710a, 710b etc., server system 334 and components thereof, etc., one skilled in the art will appreciate variations and additional details regarding the functionality of these embodiments that can be carried out by the calculation module 1100. In this context, one of skill in the art will also appreciate that features and aspects of the various embodiments (eg, systems, devices and/or apparatus, and the like) described herein may be implemented with respect to other embodiments (eg, methods, procedures and/or operations, and the like) described herein without departing from the scope of the disclosure.

As used herein, the term "module" may describe a given unit of functionality that may be realized in accordance with one or more embodiments of the present application. As used herein, a module can be implemented using any form of hardware, software, or a combination thereof. For example, one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logic components, software routines, or other mechanisms may be implemented to make up a module. In implementation, the various modules described herein may be implemented as discrete modules or the functions and features described may be shared in whole or in part among one or more modules. In other words, as will be apparent to one of ordinary skill in the art after reading this description, the various features and functionality described herein may be implemented in any given application and may be implemented in one or more separate or shared modules. various combinations and permutations. Although various features or elements of functionality may be individually described or claimed as separate modules, it will be understood by one of ordinary skill in the art that these features and functions may be shared between one or more common elements of software and hardware, and such description shall not require or imply that use separate hardware or software components to implement such features or functionality.

Where application components or modules are implemented in whole or in part using software, in one embodiment, these software elements may be implemented to function with a computing or processing module that can perform the functionality described with respect to them. . One such example calculation module is shown in Figure 11. Various embodiments are described as to the example calculation module 1100 . After reading this description, it will be apparent to a person skilled in the relevant art how to implement the application using other architectures or compute modules.

Referring now to Figure 11, compute module 1100 may represent, for example, compute or processing capabilities found within mainframe computers, supercomputers, workstations, or servers; desktop, laptop, portable or tablet computers; handheld computing devices (tablet computers, PDAs, smartphones, mobile phones, pocket PCs, etc.); other displays, application-specific devices, or other electronic devices, and the like, depending on the application and/or environment for which the calculation module 1100 is specifically intended.

Compute module 1100 may include, for example, one or more processors, microprocessors, controllers, control modules, or other processing devices, such as a processor 1110, and such may be included in circuitry 1105. Processor 1110 may be implemented using a special purpose processing engine such as, for example, a microprocessor, controller, or other control logic. In the illustrated example, processor 1110 connects to bus 1155 via circuitry 1105, although any means of communication may be used to facilitate interaction with other components of compute module 1100 or to communicate externally.

Compute module 1100 may also include one or more memory modules, referred to herein simply as main memory 1115 . For example, random access memory (RAM) or other dynamic memory may be used to store information and instructions to be executed by processor 1110 or circuitry 1105. Main memory 1115 may also be used to store temporary variables or other information intermediated during the execution of instructions to be executed by processor 1110 or circuitry 1105. Compute module 1100 may also include a read-only memory (ROM) or other static storage device coupled to bus 1155 for storing static information and instructions for processor 1110 or circuitry 1105.

Compute module 1100 may also include one or more various forms of information storage devices 1120, which may include, for example, a media drive 1130 and a storage drive interface 1135. Media drive 1130 may include a drive or other mechanism to support fixed or removable storage media 1125 . For example, a hard disk drive, floppy disk drive, magnetic tape drive, optical disk drive, CD or DVD (R or RW) drive, or other removable or fixed media drive may be provided. Accordingly, removable storage media 1125 may include, for example, a hard drive, a floppy disk, magnetic tape, cartridge, optical disc, a CD or DVD, or other fixed or removable media that is read by, writes to, or accesses by the 1130 media unit. As these examples illustrate, removable storage media 1125 may include a computer-usable storage medium that has data or computer software stored thereon.

In alternate embodiments, information storage devices 1120 may include other similar instrumentality to allow computer programs or other instructions or data to be loaded into calculation module 1100 . Such instrumentalities may include, for example, fixed or removable storage unit 1140 and storage unit interface 1135. Examples of such removable storage drives 1140 and storage drive interfaces 1135 may include a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, a PCMCIA slot and card, and other fixed or removable storage drives 1140 and storage drive interfaces 1135 that allow software and data to be transferred from the removable storage drive 1140 to the compute module 1100.

Calculation module 1100 may also include a communications interface 1150. Communications interface 1150 may be used to allow software and data to be transferred between calculation module 1100 and external devices. Examples of communications interface 1150 include a modem or soft modem, a network interface (such as an Ethernet, network interface card, WiMedia, IEEE 802.XX, or other interface), a communications port (such as for example, a USB port, IR port, Bluetooth® interface with RS232 port, or other port), or other communications interface configured to work with the communications media described herein. Software and data transferred across communications interface 1150 may be exemplified in signals, which may be electronic, electromagnetic (including optical), or other signals that may be exchanged over a given communications interface 1150. These signals may be provided to/from communications interface 1150 via channel 1145. Channel 1145 may carry signals and may be implemented using a wired or wireless communication medium. Some non-limiting examples of channel 1145 include a telephone line, a cellular or other radio link, an RF link, an optical link, a network interface, a local or wide area network, and other wireless or wireless communications channels. by cable.

In this document, the terms “computer program medium” and “computer usable medium” and “computer readable medium”, as well as variations thereof, are used to refer generally to transient or non-transient media such as, for example , main memory 1115, storage unit interface 1135, removable storage media 1125, and/or channel 1145. These and various other forms of computer program media or computer usable/readable media may be involved in leading to carry out one or more sequences of one or more instructions in a processing device for execution. Such instructions embodied in the medium may be referred to generally as "computer program code" or "computer program product" or "instructions" (which may be grouped as computer programs or other groupings). When executed, such instructions may enable compute module 1100, related circuitry, and/or a processor therein or connected thereto to perform features or functions of the present disclosure discussed herein (for example, in relation to methods described above and/or in the claims), including for example when they are incorporated into a system, apparatus, device and/or the like.

Various embodiments have been described with reference to specific exemplary features thereof. However, it will be apparent that various modifications and changes may be made thereto without departing from the broadest scope of the various embodiments set forth in the appended claims. The specification and figures are therefore to be considered in an illustrative rather than a restrictive sense. It will be appreciated that, for purposes of clarity, the above description has described embodiments with reference to different functional units. However, it will be apparent that any suitable distribution of functionality between different functional units may be used without prejudice to the invention. For example, the illustrated functionality to be performed by separate switching devices may be performed by the same computing device. Also, the illustrated functionality to be performed by a single computing device may be distributed among multiple computing devices. Thus, references to specific functional units should only be taken as references to means suitable for providing the described functionality, rather than as indicative of a strict logical or physical structure or organization.

Although described above as to various exemplary embodiments and implementations, it is to be understood that the various features, aspects, and functionalities described in one or more of the individual embodiments are not limited in their applicability to the particular embodiment with which they are described, but in his Instead they may apply, alone or in various combinations, to one or more of the other embodiments of the present application, whether or not such embodiments are described and whether or not such features are presented as being part of a described embodiment. Therefore, the breadth and scope of the present application should not be limited by any of the exemplary embodiments described above.

The terms and expressions used in this application, and variations thereof, unless otherwise expressly stated, are to be construed as open-ended as opposed to limiting. As examples of the foregoing: the term “including” should be read to mean “including, without limitation” or the like; the term "example" is used to provide illustrative instances of the item under discussion, not an exhaustive or limiting list thereof; the terms “a(o)” or “an” should be read to mean “at least one”, “one or more” or the like; the term "set" should be read as including one or more objects of the type included in the set; and adjectives such as "conventional", "traditional", "normal", "usual", "well-known" and terms of similar meaning should not be construed as limiting the item described to a given time period or to an item available from now on. a given time, but rather should be read as encompassing conventional, traditional, normal or customary technologies that may be available or known now or at any time in the future. Similarly, the plural can be recognized in some cases as applying to the singular and vice versa. Also, when this document refers to technologies that will be apparent or known to one of ordinary skill in the art, such technologies encompass those that are apparent or known to one of ordinary skill in the art now or at any time in the future.

The presence of broadening terms and expressions such as "one or more", "at least", "but not limited to" or other similar expressions in some cases shall not be read as meaning that the narrower case is intended or required in instances where such extension expressions may be absent. Use of the term "module" does not imply that the components or functionality described or claimed as part of the module are all configured in a common package. In effect, any or all of the various components of a module, whether control logic, circuitry, or other components, may be combined into a single package or kept separately and may further be distributed in multiple groupings or packages or across from multiple locations.

Additionally, the various embodiments disclosed herein are described in terms of block diagrams, flow charts, and other exemplary illustrations. As will be apparent to one of ordinary skill in the art upon reading this document, the illustrated embodiments and their various alternatives may be implemented without limitation to the illustrated examples. For example, the block diagrams and their accompanying description should not be construed as requiring a particular architecture or configuration. In addition, the operations and secondary operations of various methods described herein are not necessarily limited to the order described or shown in the figures, and one skilled in the art will appreciate, after studying this disclosure, variations of the order of operations described herein. herein that are within the scope of the disclosure. It will be understood that each block in the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be implemented by executing computer program instructions. These computer program instructions can be loaded into a computer or other programmable data processing apparatus (such as a controller, microcontroller, microprocessor, or the like) in a sensor electronics system to produce a machine, such that the instructions that are executed on the computer or other programmable data processing apparatus create instructions to implement the functions specified in the flowchart block(s). These computer program instructions may also be stored in computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular way, such that the instructions stored in the computer-readable memory produce a item of manufacture that includes instructions that implement the function specified in the flowchart block(s). Computer program instructions may also be loaded into a computer or other programmable data processing apparatus to cause a series of operational steps to be performed in the computer or other programmable data processing apparatus to produce a computer-implemented method in such a manner that instructions executed in the computer or other programmable data processing apparatus provide steps to implement the functions specified in the flowchart block(s) presented herein.

It should be appreciated that all of the methods and procedures disclosed herein can be used in any continuous or intermittent glucose or other analyte monitoring system. It should be further appreciated that the implementation and/or execution of all methods and procedures may be performed by any suitable device or system, whether local or remote. Furthermore, any combination of devices or systems can be used to implement the present methods and procedures.

In addition, the operations and secondary operations of methods described herein may be carried out or implemented, in some cases, by one or more of the components, elements, devices, modules, circuitry, processors, etc. of computing systems, apparatus, devices, environments and/or modules described in this document and referred to in various figures of this disclosure, as well as one or more subcomponents, elements, devices, modules, processors, circuitry, and the like depicted therein and/or described with respect thereto. In such instances, the description of the methods or aspects thereof may refer to the corresponding component, element, etc., but regardless of whether reference is made explicitly, one skilled in the art will recognize from a study of this disclosure when the corresponding component, element, etc. may be used. Furthermore, it will be appreciated that such references do not necessarily limit the methods described to the particular component, element, etc. to which reference is made. Therefore, it will be appreciated by one skilled in the art that aspects and features described above in relation to (sub)components, elements, devices, modules and circuitry, etc., including variations thereof, can be applied to the various operations. described in connection with methods described herein, and vice versa, without departing from the scope of this disclosure.

Claims (15)

i. Method for wireless communication of glucose data, the method comprising: generating glucose data indicative of glucose concentration in a host using a transcutaneous glucose sensor (10); processing the generated glucose data using a sensor electronics module (12) integral with, or releasably attachable to, the transcutaneous glucose sensor (10) to generate sensor information; authenticating a display device (310) configured to display, or process and display, sensor information transmitted by the sensor electronics module (12), for a first wireless connection exchanging authentication-related information between the sensor electronics module (12) sensor electronics and display device (310); after authenticating the display device (310), the sensor electronics module (12) periodically exchanging messages with the display device (310) to maintain a continuous connection through the first wireless connection; Y the sensor electronics module (12) transmitting encrypted sensor information to the display device (310) during the time the first wireless connection is maintained. 2. The method of claim 1, further comprising terminating the first wireless connection. 3. Method according to claim 2, further comprising: establishing a second wireless connection between the sensor electronics module (12) and the display device (310); the sensor electronics module (12) periodically exchanging messages with the display device (310) to maintain a continuous connection through the second wireless connection; and transmitting, the sensor electronics module (12), encrypted sensor information to the display device (310) during the time the second wireless connection is maintained; wherein, for the second wireless connection, the periodic exchange of the messages and the transmission of encrypted sensor information is based on authenticating the display device (310) for the first wireless connection. 4. Method according to claim 2, wherein: the sensor electronics module (12) sends a proposal for a set of connection parameters to the display device (310), in response to receiving a connection request from the display device (310), the set of parameters comprising connection a connection interval, slave latency, and monitoring timeout; the sensor electronics module (12) receives a connection decision from the display device (310), where the connection decision is based on the proposal; the periodic exchange of messages is performed based on the set of connection parameters, in response to the connection decision comprising an acceptance of the proposal; Y the connection is terminated based on a violation of one or more of the connection parameters. The method of claim 2, further comprising switching from operating in a continuous connection mode to an intermittent connection mode, the intermittent connection mode comprising: periodically establishing a connection between the sensor electronics module (12) and the display device (310); Y while the connection is established, transmitting the analyte data to the display device (310); wherein the switching is based on one or more switching criteria, the switching criteria comprising: a type of display device (310); user information; the availability of display devices for your connection; a priority scheme relating to display devices (310); quality of service; battery life; time of the day; Y a location. 6. A method according to any preceding claim, wherein: the authentication related information comprises an application key; the sensor electronics module (12) transmits the encrypted sensor information to the display device (310), where the encrypted sensor information has been generated based on the application key; Y the method further comprises modifying the application key in response to one or more of: the passage of a predetermined amount of time; resetting the analyte sensor system or display device (310); a trigger factor related to another device attempting to connect to the analyte sensor system; Y user input. A method according to any preceding claim, wherein the display device (310) is one display device of a set of display devices, and the method further comprises identifying the display device (310) for connection by: the sensor electronics module (12) receiving a first signal from the display device (310) wherein the first signal is received via a first link; identifying, the sensor electronics module (12), the display device (310) for selection, based on a derivative of the first signal meeting or above a lower threshold. The method of claim 7, further comprising selecting the display device (310) for connection based on the derivative of the first signal meeting or above an upper threshold. 9. A method according to claim 8, further comprising: the sensor electronics module (12) receiving a second signal from the display device (310), wherein the second signal is received via a second link; wherein selecting the display device (310) for connection is further based on the derivative of the second signal being below the lower threshold. 10. A method according to claim 7, further comprising: the sensor electronics module (12) receiving a second signal from the display device (310); obtaining, the sensor electronics module (12), a derivative of the second signal; Y select, the sensor electronics module (12), the display device (310) for its connection, on the basis that the derivative of the second signal meets or is above an upper threshold. The method of claim 10, wherein selecting the display device (310) for connection is further based on the derivative of the first signal not meeting or above the upper threshold. 12. The method according to claim 10, further comprising: generating an indication to configure the display device (310) according to a second link, based on the derivative of the first signal being below the upper threshold; or generating an indication to configure the display device (310) according to the second link, based on the derivative of the first signal meeting or above the upper threshold. 13. A method according to claim 10, further comprising: the sensor electronics module (12) receiving a third signal from the display device (310), wherein the third signal is received via a third link; obtaining, the sensor electronics module (12), a derivative of the third signal; in which to select, the sensor electronics module (12), the display device (310) for connection is further based on the derivative of the third signal being below the lower threshold. 14. A method according to claim 7, further comprising: the sensor electronics module (12) receiving a second signal from the display device (310), wherein the second signal is received via a second link; obtaining, the sensor electronics module (12), a derivative of the second signal; Y selecting, the sensor electronics module (12), the display device (310) for connection, based on a comparison of the derivative of the second signal and the derivative of the first signal. 15. A method according to claim 14, further comprising: the sensor electronics module (12) receiving a third signal from the display device (310), wherein the third signal is received via a third link; obtaining, the sensor electronics module (12), a derivative of the third signal; in which to select, the sensor electronics module (12), the display device (310) for connection is further based on a comparison of the derivative of the third signal and the derivative of the second signal.